Cambridge SoundWorks 3620 manual Planning the Configuration Files, Typical configuration plans

Page 9

Avaya, Inc.

Avaya Configuration Cradle

 

Administrator Guide

4.Planning the Configuration Files

Each configurable option may be categorized as one of three types: System (Sys), Group (Grp) or User (Usr). System level options should be those that are stable across the entire system. DHCP vs. Static IP addressing would be an example of a System option. Options that are designated as Group type should be those that change by category of user. PTT Allow/Disallow and PTT Channel are examples. A unique extension number is assigned to each handset by the system administrator and would be a User type. The remaining User types should be reserved for options that are normally set by the end user. For Standby menu options such as Ring Type and Noise Mode, default values may be entered with the expectation that the user may change them.

4.1Typical configuration plans

Because the specific options that are available depend on the software version and License Option, the typical plan options for your facility may be different than those listed here.

Typical System file settings:

System file settings typically do not change across an installation. These are typical Sys categories:

License Option

Network Config

IP Addressing

ESSID

Security

IP Office Flag

Typical Group file settings:

If certain groups of people require different access to functions, such as PTT, these options would be stored as Group files. Several different Group files can be established and the handsets can be configured by group. Typical Grp categories are:

Push-to-talk options on both Admin and Standby menus

Typical User file settings:

If a setting can be changed by the user in the Standby menu, then it would typically be stored in a User file. These can be the default settings or whatever your system requires. Typical Usr categories are:

Extension

Static IP address

Ring Options

Phone Options

such as security or ESSID. These settings can be moved to a Group file or you may set up two System files.You may have zones in your facility that require different System settings,

21-300630, Issue 1, July 2005

Page 9

Image 9
Contents Avaya Configuration Cradle 2005, Avaya Inc Important Safety Information Avaya, Inc Table of Contents Questions? Icons and conventions About This DocumentAvaya Configuration Cradle Overview Installing the Avaya Configuration Cradle Typical configuration plans Planning the Configuration FilesConfiguration Cradle Window Configuration Cradle toolbarInitial window Gray file up to date. The settings have been saved Creating Your Configuration Plan Sample configuration window Plan category Filename Configuration planning worksheetDownloading and Uploading Configuration Plans Downloading a configuration plan to a handsetUploading a configuration plan from a handset Software Maintenance