B5800 Branch Gateway FP1 Avaya Branch Gateway Manager 10.
© 2012 AVAYA All Rights Reserved. Notices While reasonable efforts have been made to ensure that the information in this document is complete and accurate at the time of printing, Avaya assumes no liability for any errors. Avaya reserves the right to make changes and corrections to the information in this document without the obligation to notify any person or organization of such changes.
Contents Contents 1. Branch Gateway Manager 1.1 Installing Branch ..................................................................... Gateway Manager 1.2 Starting Branch ..................................................................... Gateway Manager 1.3 Opening a ..................................................................... Configuration 1.4 Changing the ..................................................................... Branch Gateway Manager Language 1.5 Web Control ....................
5.3.3............................................................................ LAN2 5.3.4............................................................................ DNS 5.3.5............................................................................ Voicemail 5.3.6............................................................................ Telephony 5.3.7............................................................................ Directory Services 5.3.8.................................................
Contents 6. Short Codes 6.1 Short Code ..................................................................... Fields and Characters 6.2 User Dialing ..................................................................... 6.3 Application ..................................................................... Dialing 6.4 Secondary ..................................................................... Dial Tone 6.5 ? Short Codes ..................................................................... 6.6 Short Code ..
.8.105 ............................................................................ Relay Off 6.8.106 ............................................................................ Relay Pulse 6.8.107 ............................................................................ Resume Call 6.8.108 ............................................................................ Retrieve Call 6.8.109 ............................................................................ Ring Back When Free 6.8.110 ...........
Contents 7.3.59 ............................................................................ Dial Inclusion 7.3.60 ............................................................................ Dial Intercom 7.3.61 ............................................................................ Dial Paging 7.3.62 ............................................................................ Dial Physical Extn by Number 7.3.63 ............................................................................
.5.3............................................................................ How are Line Appearances Treated? 8.5.4............................................................................ Button Indication 8.6 Other Appearance ..................................................................... Controls 8.6.1............................................................................ Selected Button Indication 8.6.2............................................................................
Contents 11.21 Hungary ..................................................................... 11.22 Iceland..................................................................... 11.23 India ..................................................................... 11.24 Italy ..................................................................... 11.25 Korea ..................................................................... 11.26 Kuwait ..................................................................... 11.
Chapter 1. Branch Gateway Manager Avaya Branch Gateway Manager 10.
Branch Gateway Manager: 1. Branch Gateway Manager Branch Gateway Manager is an application for viewing and editing an Avaya Branch Gateway system's configuration. It is a tool for system installers and maintainers. Branch Gateway Manager runs on a Windows PC and connects to the system via Ethernet LAN or WAN connections. · WARNING - Password Changes Required New systems use default security settings. These settings must be changed to make the system secure.
1.1 Installing Branch Gateway Manager In addition to Branch Gateway Manager, the Admin suite includes options to install the following applications: · System Monitor This is a tool for system installers and maintainers. Interpreting the information output by System Monitor requires detailed data and telecoms knowledge. · System Status Application This is a Java application that can be used to monitor the status of the system such as extension, trunks and other resources.
Branch Gateway Manager: Installing Branch Gateway Manager Installing Branch Gateway Manager Note: This installation process will install Windows .NET2 if not already present. The installation of .NET2 may require some systems to restart and the installation process to then be restarted. 1. If installing from the Admin DVD, insert the DVD and when the page is displayed click on the link for the Admin suite. This will open a file windows showing the installation files for the suite.
1.2 Starting Branch Gateway Manager No name or password is required to start Branch Gateway Manager. A name and password is only required when connecting with a system. When started, by default Branch Gateway Manager will attempt to discover any systems on the network. If it finds any it will display a list from which you can select the system required. 1. Select Start and then Programs or All Programs depending on the version of Windows. Select the IP Office program group. 2. Select run. Manager.
Branch Gateway Manager: Starting Branch Gateway Manager · Read a Configuration from a File Avaya Branch Gateway Manager 10.
1.3 Opening a Configuration The initial IP address ranges in which Branch Gateway Manager searches for systems are set through the Branch Gateway Manager preferences (File | Preferences | Discovery 102 ). By default it scans the local network of the Branch Gateway Manager PC. 1. Start Branch Gateway Manager. If Branch Gateway Manager is already started and a configuration is open in it, that configuration must be closed first.
Branch Gateway Manager: Opening a Configuration Login Messages While attempting to login to a system, various additional messages may be displayed. Configuration Not Loaded Messages · Access Denied This is displayed as the cause if the service user name/password were incorrect, or the service user has insufficient rights to read the configuration.
1.4 Changing the Branch Gateway Manager Language The Branch Gateway Manager application can run in US English, UK English, Chinese (Simplified), French, German, Brazilian Portuguese, Dutch, Italian, Russian and Mexican Spanish. By default it tries to use the best match to the PC's regional location settings, otherwise it will use UK English. The process below can be used to run Branch Gateway Manager in one of its supported languages. However it does not change the language used for help file content. 1.
Branch Gateway Manager: Web Control Avaya Branch Gateway Manager 10.
Chapter 2. Configuration Mode Avaya Branch Gateway Manager 10.
Configuration Mode: 2. Configuration Mode This section of the documentation covers the operation of Branch Gateway Manager when being used to edit the configuration of a system running in IP Office Essential Edition, IP Office Preferred Edition or IP Office Advanced Edition modes. This section is divided as follows. The Configuration Mode Interface 22 This part details the screen elements of Branch Gateway Manager's configuration mode interface.
2.1 The Configuration Mode Interface When Branch Gateway Manager is in configuration mode, the screen elements shown are available. Some of these elements can be customized, moved and hidden. Branch Gateway Manager Configuration Mode Screen Elements · Title Bar 24 In addition to the application name, when configuration settings are loaded from a system, the title bar displays the user name used to load the settings and the operator view applied.
Configuration Mode: The Configuration Mode Interface 2.2 Security Settings Access to system settings is controlled by Service Users and Rights Groups. stored in the control unit's security settings. These are stored separately from the system's configuration settings. All actions involving communications between Branch Gateway Manager and the system require a service user name and password. That service user must be a member of a Rights Group with permissions to perform the required action.
2.3 Title Bar The Branch Gateway Manager title bar shows several bits of information. · The Branch Gateway Manager application version. · The system name of the system from which the currently loaded configuration was received. · The software level of the system's control unit. Avaya Branch Gateway Manager 10.
Configuration Mode: Title Bar 2.4 The Menu Bar Details of all the options that may be available within the Menu Bar drop downs are contained in the section Menu Bar Commands 96 . The commands are context sensitive. Commands are grayed out when not usable. For some commands, an symbol indicates that there are sub-commands from which a selection can be made. The following menu options are available: File Open Configuration... 98 Close Configuration 98 Save Configuration 98 Save Configuration As...
2.5 Toolbars A number of toolbars can be displayed by Branch Gateway Manager. These are: · Main Toolbar 26 · Navigation Toolbar · Details Toolbar 28 28 Showing or Hiding Toolbars The different toolbars can be hidden if not required. 1. Select View and then Toolbars. Those toolbars currently shown are indicated by a tick mark. 2. To show or hide a toolbar, click on its name. Moving Toolbars The position of the Branch Gateway Manager toolbars can be moved.
Configuration Mode: Toolbars · Standalone Voice Mail Client 118 Launch the Standalone Voice Mail client if also installed on the Branch Gateway Manager PC. Avaya Branch Gateway Manager 10.
2.5.2 The Navigation Toolbar This toolbar provides drop down lists which can be used to navigate to particular records in the configuration settings. The selected options in the navigation pane, group pane and the details pane are synchronized with the navigation toolbar and vice versa. This toolbar is particularly useful if you want to work with the group pane 30 and or navigation pane 29 hidden in order to maximize the display space for the details pane.
Configuration Mode: Toolbars 2.6 Using the Navigation Pane This pane shows icons 135 for the different types of record that the configuration can contain. Each type is followed by the number of records of that type already in the configuration. When Branch Gateway Manager is used in security mode, this pane is also used by Branch Gateway Manager in security mode 59 to display records for security settings.
2.7 Using the Group Pane This pane lists all the records that match the type selected in the navigation pane or navigation toolbar. The list can be sorted by clicking on a column heading. Selecting a record in this pane displays its details in the details pane. The icons used in the pane may vary according to the state of the record. For example, some of the users shown in this example have been configured for hot desking.
Configuration Mode: Using the Group Pane Adding a New Record The group pane can be used to add a new record of the type currently displayed. 1. Right-click on the pane and select New. · A arrow symbol next to New indicates that you can select a particular type of new record to create. Click the arrow and select an option from the list. 2. Use the details pane to configure the new record. 3. Click OK in the details pane. Deleting an Record 1. Select the record to be deleted by clicking on it. 2.
2.8 Using the Details Pane Whenever a selection is made through the group pane or the navigation toolbar, the settings for the matching record are shown in the details pane. This pane is also used by Branch Gateway Manager in security mode 59 to display records for security settings. The details are grouped into tabs. The tabs available may vary depending on what particular type of record is being viewed. For example, for extension records the Analog tab is only shown for analog extensions.
Configuration Mode: Using the Details Pane Editing an Record 1. The method of entering a record varies as different fields may use different methods. For example text record boxes or drop down lists. 2. By default when changes are made, they are validated once another field is selected. See File | Preferences | Validation 106 . 3. Clicking on OK at the base of the details pane to accept the changes or click on Cancel to undo the changes. Adding a New Record 1. Click at the top-right of the details pane.
2.9 Using the Error Pane Validation is a process where Branch Gateway Manager checks configuration records for errors or for values for which it regards as requiring a warning. The results of this checking are shown by icons next to the field that caused the error or warning, All errors and warnings are also listed in the Error Pane. By default validation is performed automatically whenever a configuration file is opened and when any field is edited.
Configuration Mode: Using the Error Pane Showing or Hiding the Error Pane The error pane is automatically displayed if a configuration containing errors or warnings is loaded into Branch Gateway Manager. However it can be manually shown or hidden using either of the following methods. 1. From the main toolbar, use the icon. or 1. Select View. Those panes currently shown are indicated by a tick mark. 2. To show or hide the error pane, click on its name. Avaya Branch Gateway Manager 10.
2.10 Altering the Interface The Branch Gateway Manager configuration settings interface can be customized in a number of ways. These changes are remembered the next time Branch Gateway Manager is started. Resizing the Branch Gateway Manager Window When the Branch Gateway Manager window is not maximized or minimized, it size can be adjusted. 1. Place the cursor over the edge of the current window. 2. When the cursor changes to a double-headed arrow, click and hold the cursor. 3.
Configuration Mode: Altering the Interface Changing the Position of the Details Pane When the group pane is visible, the details pane is shown either below it or to its right. This position can be adjusted. 1. Select View and then Details Pane. 2. The current position setting is indicated by a tick mark. 3. To select a position, click on it. Changing the Size of Configuration Icons The size of the icons used on the navigation pane and details pane can be adjusted. 1. Select File and then Preferences. 2.
2.11 The Status Bar The status bar at the base of the Branch Gateway Manager screen is used to display icons and messages about communications between Branch Gateway Manager and systems. If the Branch Gateway Manager is also acting as a BOOTP and TFTP server it will also show BOOTP and TFTP messages. A padlock icon is displayed whenever the Branch Gateway Manager communications settings are set to secure.
Configuration Mode: The Status Bar 2.12 Editing Configuration Settings Before editing the system's configuration settings, it is important to understand how those settings are stored and used by the system. · The control unit holds copies of its configuration in both its internal non-volatile and RAM memory. A copy is also held on the System SD card. · The copies in non-volatile memory and System SD card, are retained even if power to the control unit is removed.
Avaya Branch Gateway Manager 10.
Configuration Mode: Editing Configuration Settings 2.12.1 Mergeable Settings The table below shows the configuration records for which changes can be merged and those that require a system reboot. The Send Configuration menu shown when sending a configuration to the system automatically indicates when the configuration is mergeable.
2.12.2 Configuration Size The maximum size configuration file that can be loaded into a control unit is 2.0MB. · When you attempt to save a configuration that is too large, you will be prompted and the save is canceled. · During normal operation, additional configuration records can be added to the configuration without using Branch Gateway Manager (for example call log records and directory records made from phones).
Configuration Mode: Editing Configuration Settings 2.12.3 Setting the Discovery Addresses By default, when or File | Open configuration is selected, Branch Gateway Manager's Select B5800 menu appears. It performs a UDP broadcast to the address 255.255.255.255. This broadcast will only locate systems that are on the same network subnet as the PC running Branch Gateway Manager. The process above is called discovery. A UDP broadcast will not be routed to other networks and subnets.
Changing the Initial Discovery Settings The Discovery tab of the Preferences menu can be used to set the UDP and TCP addresses used by the discovery process run by the Select B5800 menu. 1. Select File | Preferences menu. 2. Select the Discovery tab. · TCP Discovery: Default = On. This setting controls whether Branch Gateway Manager uses TCP to discover systems. The addresses used for TCP discovery are set through the IP Search Criteria field below. · NIC IP/NIC Subnet This area is for information only.
Configuration Mode: Editing Configuration Settings 2.12.4 Opening a Configuration from a System The initial IP address ranges in which Branch Gateway Manager searches for systems are set through the Branch Gateway Manager preferences (File | Preferences | Discovery 102 ). By default it scans the local network of the Branch Gateway Manager PC. 1. Start Branch Gateway Manager. If Branch Gateway Manager is already started and a configuration is open in it, that configuration must be closed first.
Login Messages While attempting to login to a system, various additional messages may be displayed. Configuration Not Loaded Messages · Access Denied This is displayed as the cause if the service user name/password were incorrect, or the service user has insufficient rights to read the configuration.
Configuration Mode: Editing Configuration Settings 2.12.6 Known System Discovery The Select B5800 menu normally displays systems discovered by Branch Gateway Manager using either UDP broadcast and or TCP requests (see Setting the Discovery Addresses 43 ). Branch Gateway Manager can be configured to also record details of discovered units and then display a list of those previously discovered ('known') systems.
2.12.7 Creating New Records There are a number of ways in which you can add new records to the configuration currently loaded in Branch Gateway Manager. Adding a New Record Using the Details Pane 1. Use the navigation pane, groups pane or navigation toolbar, select an existing record of the type required. 2. Click at the top-right of the details pane. 3. Select the type of record required. For example, with extensions you can select from H.323 Extension or SIP Extension. 4.
Configuration Mode: Editing Configuration Settings 2.12.8 Validation of Records Validation is a process where Branch Gateway Manager checks configuration records for errors or for values for which it regards as requiring a warning. The results of this checking are shown by icons next to the field that caused the error or warning, All errors and warnings are also listed in the Error Pane. By default validation is performed automatically whenever a configuration file is opened and when any field is edited.
Showing or Hiding the Error Pane The error pane is automatically displayed if a configuration containing errors or warnings is loaded into Branch Gateway Manager. However it can be manually shown or hidden using either of the following methods. 1. From the main toolbar, use the icon. or 1. Select View. Those panes currently shown are indicated by a tick mark. 2. To show or hide the error pane, click on its name. Avaya Branch Gateway Manager 10.
Configuration Mode: Editing Configuration Settings 2.12.9 Creating an Offline Configuration Branch Gateway Manager can be used to create a new configuration without connecting to a system. This allows the creation of a configuration prior to installation of the real system and so can be used to speed up the installation process. · The configuration created must match the physical equipment in the system into which the configuration will be loaded.
2.12.10 Importing and Exporting Settings Branch Gateway Manager can import configuration settings created elsewhere. This can be useful when setting up a new system or sharing common settings such as a directory between systems. · The system supports LDAP records (LDAP Version 2). 171 (System | Directory Services | LDAP · The system also supports HTTP records.
Configuration Mode: Editing Configuration Settings Exporting Settings 1. Select File | Import/Export... from the menu bar. 2. Select Export. 3. Select the type of file. The list of exportable record types will change to match the file type. 4. Select the types of items that should be exported. 5. Use the Save In path to select the location for the exported files.
2.12.11 Copying and Pasting Branch Gateway Manager supports the normal Windows methods of cutting, copying, pasting and deleting records and settings. These can be accessed through the Edit menu in the menu bar or using the standard Windows keyboard shortcuts for those actions. They can also be accessed by selecting a record or text field and then right-clicking. Copy and paste can be used with the navigation and group panes to create a new record with the same settings as the original.
Configuration Mode: Editing Configuration Settings 2.12.13 Sending a Configuration The current configuration settings open within Branch Gateway Manager can be sent to the system. Sending an Individual System Configuration 1. The first steps of this process depend on whether you are sending a configuration received from the system or sending one opened offline/created new. · A Configuration Opened from a System Click in the main toolbar or select File | Save Configuration from the menu bar.
2.12.14 Erasing the Configuration The system configuration settings can be erased. During this process, the system is rebooted and starts with a set of default settings 57 . This process does not erase the security settings of the system. Erasing the Configuration 1. Select File | Advanced | Erase Configuration (Default). 2. Enter a valid user name and password. 3. The system will be rebooted. Avaya Branch Gateway Manager 10.
Configuration Mode: Editing Configuration Settings 2.12.15 Default Settings The following applies to new systems and those defaulted using the Erase Configuration 56 command. They also apply to IP500 and IP500 V2 control units defaulted using the reset button on the rear of the unit (refer to the Installation manual for details of using the reset button). For B5800 Branch Gateway only the Avaya Branch Gateway SD card should be used.
Chapter 3. Security Mode Avaya Branch Gateway Manager 10.
Security Mode: 3. Security Mode These menus are used to edit the security settings of a system. The security settings are stored on the system and are separate from the system's configuration settings. To change a system's security settings, Branch Gateway Manager must first be switched to security mode by selecting File | Advanced | Security Settings from the menu bar. Avaya Branch Gateway Manager 10.
3.1 Security Settings Access to system settings is controlled by Service Users and Rights Groups. stored in the control unit's security settings. These are stored separately from the system's configuration settings. All actions involving communications between Branch Gateway Manager and the system require a service user name and password. That service user must be a member of a Rights Group with permissions to perform the required action.
Security Mode: Security Settings 3.2 Default Security Users This section lists the default Rights Groups and Service Users. · WARNING: Change Passwords These settings must be changed to make the system secure. At minimum you must change the default passwords of the Security Administrator and the default service users. Failure to do so will render the system unsecure.
Default Rights Groups Rights Administrator Group Description These groups are intended for users using the Branch Gateway Manager application to configure the system.
Security Mode: Default Security Users Web Security Services Read All – – – – – – Security Write All – – – – – – – – – – – – – Config Read All – – – – Config Write All – – – – Backup – – – Restore – – – Upgrade – Security Write Own Passwor d – Avaya Branch Gateway Manager 10.
3.3 The Security Mode Interface Branch Gateway Manager can be switched to security mode. This mode it is used to load and edit the security settings of a system. How the controls operate is similar to Branch Gateway Manager in configuration mode. Switching Branch Gateway Manager to Security Mode 1. Select File | Advanced | Security Settings. Switching Branch Gateway Manager Back to Configuration Mode 1. Select File | Configuration.
Security Mode: The Security Mode Interface 3.4 Security Administration This section also covers a basic introduction to security principles and the security mechanisms. · NOTE: If administration security is of no concern, the default settings allow modification of all system features without restriction. It is recommended as a minimum that default passwords are changed. 1.
3. Encryption Encryption ensures that all data sent by either the system or Branch Gateway Manager cannot be ‘read’ by anyone else, even another copy of Branch Gateway Manager. Encryption is the application of a complex mathematical process at the originating end, and a reverse process at the receiving end.
Security Mode: Security Administration 4. Message Authentication Message authentication ensures that all data sent by either the system or Branch Gateway Manager cannot be tempered with (or substituted) by anyone else without detection. This involves the originator of the data producing a signature (termed a hash) of the data sent, and sending that as well. The receiver gets the data and the signature and check both match.
5. Identity The identity of the equipment or person at each end of the link is achieved by the used of digital certificates – more specifically X.509 v3 certificates. Digital certificates are the preferred mechanism for the majority of internet-based applications including e-commerce and email, and can be thought of as a credential, just like a passport or drivers’ license. A digital certificate contains at least three things: · A public key.
Security Mode: Security Administration 6. Windows Certificate Store Usability The certificate store that is used by the Branch Gateway Manager to save X509 certificates to and retrieve certificates from is the default one provided by the Windows operating system. This may be accessed for maintenance purposes by a user with sufficient permission via the use of a ‘snap-in’. · WARNING Avaya accept no responsibility for changes made by users to the Windows operating system.
Branch Gateway Manager only accesses some of the certificate sub folder: Certificates (Local Computer) Folder Branch Gateway Manager Use Personal | Certificates · Folder searched by Branch Gateway Manager 1st for matching certificate to send to the system when requested. Certificate matched by the subject name contained in File | Preferences | Security | Certificate offered to the system. · Folder accessed whenever ‘Local Machine certificate store’ used for Security Settings.
Security Mode: Security Administration 8. Windows Certificate Store Import In order to use certificates – either for security settings or Branch Gateway Manager operation – they must be present in the windows certificate store. Certificates may be placed in the store by the Certificate Import Wizard or the Certificate MMC snap-in The Certificate Import Wizard can be used whenever a certificate is viewed.
10.2. Minimum Security A minimum security scenario could be where configuration data is open, but the security settings are constrained: Any individual with the correct service user name and password can access the configuration from any PC installation of Branch Gateway Manager, no logging of access: Passwords can be simple, and will never age. · Change all default passwords of all service users and Security Administrator · Set the system Security Administration service security level to Secure, Low.
Security Mode: Security Administration 10.4. Maximum Security A maximum security scenario could be where both configuration and security settings are constrained and a full level of logging is required: Certified individuals with the correct service user name and password can access the configuration from specific PC installations of Branch Gateway Manager: Passwords cannot be simple, and will age: Branch Gateway Manager can managed specific systems.
3.5 Editing Security Settings Security settings can only be loaded directly from a system. These settings cannot be saved as a file on the local PC, nor do they appear as a temporary file at any time. By default Branch Gateway Manager and the system will always attempt to use the original, unsecured link. When secure communications mode is selected a padlock icon is present on the Branch Gateway Manager status bar.
Security Mode: Editing Security Settings Editing Security Settings Editing security settings differ from editing configuration settings in a number of ways: 1. Editing of security settings may only be done online to a system. No offline saving or editing is allowed for security purposes. 2. No errors in the security settings are allowed to persist. This prevents the system becoming inaccessible through operator error. 3.
3.5.1 General Settings These settings are displayed when General is selected in the navigation pane. · Security Administrator The security administrator is a special service user who does not belong to any Rights Groups. The security administrator is able to access the system's security settings but cannot access its configuration settings. By default they are the only service user able to access to the security settings.
Security Mode: Editing Security Settings · High The password characters used must include characters from at least 3 of the 'code point sets' listed above. For example a mix of lower case, upper case and numbers. In addition, there should not be any adjacent repeated characters of any type. · Previous Password Limit (Entries): Default = 0. Range = 0 (Off) to 10 records. The number of previous password to check for duplicates against when changing the password.
3.5.2 System 3.5.2.1 System Details This tab is accessible when System is selected in the navigation pane. · Base Configuration · Services Base TCP Port: Default = 50804. Range = 49152 to 65526. This is the base TCP port for services 84 provided by the system. It sets the ports on which the system listens for requests to access those services, using its LAN1 IP address. Each service uses a port offset from the base port value.
Security Mode: Editing Security Settings Service Method Port Used Changing its setting will affect applications Secure other than just the DECT R4. The default Service Security Level is Secure + Unsecure, meaning both http and https can be used. – Default Port Service Security Level 443 · Unsecure = HTTP port 80 available. This is used for phone files, embedded file manager, system file upgrade, one-X Portal directory services, DECT R4 provisioning, IPO softphone provisioning.
3.5.2.2 Unsecured Interfaces This tab is accessible when System is selected in the navigation pane. These features relate to applications that access the system configuration settings using older security methods. · System Password: Default = 'password'. Range = 0 to 31 characters. This password is required by some legacy applications such as Monitor and Call Status. It is also used for control unit software upgrades. · VM Pro Password: Default = Blank. Range = 0 to 31 characters.
Security Mode: Editing Security Settings 3.5.2.3 Certificates Services 84 between the system and applications may, depending on the settings of the service being used for the connection, require the exchange of security certificates. The system can either generate its own certificate or certificates provided from a trusted source can be loaded.
· Pasted from clipboard in PEM format, including header and footer text. · View View the current certificate. The certificate (not the private key) may also be installed into the local PC certificate store for export or later use when running the manager in secured mode. · Delete Delete the current certificate. When sent to the system, the system will generate a new certificate when next required. This can take up to 5 minutes to generate. During this time, normal system operation is suspended.
Security Mode: Editing Security Settings · Activity: Default = Off. · Request Interval: Default = 120 seconds. Range = 5 to 3600 seconds. · SCEP Server IP/Name: Default = Blank. · SCEP Server Port: Default = 80 for HTTP and 443 for HTTPS. · SCEP URI: Default = /ejbca/publicweb/apply/scep/pkiclient.exe · SCEP Domain Cert Name: Default = Blank. · SCEP Password: Default = Blank. Avaya Branch Gateway Manager 10.
3.5.3 Services Settings This tab is accessible when Service is selected in the navigation pane. It shows details of the services that the system runs to which service users can communicate. · Name The name of the service. This is a fixed value for indication purposes only. · Host System This field shows the system's name. This is a fixed value for indication purposes only. · Service Port This is the port on which the system listens for attempts to access the service.
Security Mode: Editing Security Settings Service Method Port Used Default Port Service Security Level · Secure = HTTPS port 443 available. This can be used for DECT R4 provisioning, IPO softphone provisioning. · Service Security Level: Sets the minimum security level the service will support. See File | Preferences | Security 104 for the corresponding Branch Gateway Manager application setting, which must be changed to match the appropriate service access security settings.
3.5.4 Rights Groups The Rights Groups to which a service user 93 belongs define what the service user is able to do after that login to the system. The maximum number of rights groups that can be created is 32. Rights Administrator Group Description These groups are intended for users using the Branch Gateway Manager application to configure the system.
Security Mode: Editing Security Settings Description These groups are used by SMGR users for web service access to the system. Web Security Services Read All – – – – – – Security Write All – – – – – – – – – – – – – Config Read All – – – – Config Write All – – – – Backup – Restore – Upgrade – Security Write Own Passwor d – – – – – – – – – · Administrator Group/Manager Group/ Operator Group: These default groups are used for configuration access.
3.5.4.1 Group Details These settings are displayed when Rights Group. Rights Groups is selected in the navigation pane. This tab sets the name of the Avaya Branch Gateway R6.2 creates the SMGRAdmin rights group with full access to all Web Services. The maximum number of rights groups is 32. · Name: Range = Up to 31 characters The name for the Rights Group should be unique. Avaya Branch Gateway Manager 10.
Security Mode: Editing Security Settings 3.5.4.2 Configuration These settings are displayed when Rights Groups is selected in the navigation pane. This tab sets the configuration settings access for service user's who are members of this Rights Group. · IP Office Service Rights This setting controls what action on the system can be performed by members of the Rights Group.
3.5.4.3 Security Administration These settings are displayed when Rights Groups is selected in the navigation pane. This tab sets the security settings access for Service user's who are members of this Rights Group. These settings are ignored and greyed out if a Unique Security Administrator has been enabled in General Settings 76 . · Read all security settings Members of the Rights Group can view the system's security settings.
Security Mode: Editing Security Settings 3.5.4.5 Enhanced TSPI These settings are displayed when Rights Groups is selected in the navigation pane. This tab sets whether members of the group can access the system using the Enhanced TSPI application interface. · Enhanced TSPI Access If selected, applications in this rights group are able to use the system's Enhanced TSPI interface. This interface is not currently used by Avaya Branch Gateway. 3.5.4.
· Security Write All If selected, the rights group members can change system security settings. · Security Write Own Password If selected, members of the Rights Group can change their own password when requested to do so by the system. That request may be the result of a Password Change Period 76 , Force new password 93 or Account Expiry 93 . The new password change is requested automatically at login time. · Config Read All If selected, the rights group members can view system configuration settings.
Security Mode: Editing Security Settings 3.5.5 Service Users These settings are displayed when selected in the group pane. Service Users is selected in the navigation pane and a particular service user is In Avaya Branch Gateway R6.2, a service user SMGRAdmin with the default password SMGRAdmin01 is created during a Avaya Branch Gateway R6.2 installation. This service user is assigned the SMGRAdmin rights group. For R6.1 to R6.
· Locked - Idle This status indicates the account has been locked by passing the number of days set for the Account Idle Time on the security General Settings 76 tab without being used. The account can be enabled manually by setting the Account Status back to Enabled. · Locked - Expired This status indicates the account has been locked after passing the Account Expiry date set below.
Chapter 4. Menu Bar Commands Avaya Branch Gateway Manager 10.
4. Menu Bar Commands The commands available through the Branch Gateway Manager's menu bar change according to the mode in which Branch Gateway Manager is running. Commands may also be grayed out if not currently applicable. The following sections outline the functions of each command. The Edit and Help menus are not included. Advanced View Configuration Mode The following menu options are available: File Open Configuration... 98 Close Configuration 98 Save Configuration 98 Save Configuration As...
Menu Bar Commands: Security Mode File Open Security Settings 130 Close Security Settings 130 Save Security Settings 130 Reset Security Settings 130 Preferences 130 Configuration 130 Exit 130 View Toolbars 124 Navigation Pane Group Pane 124 Details Pane 124 124 Embedded File Management File Open File Settings 114 Close File Settings 114 Refresh File Settings 132 Upload File 114 Upload System Files 132 Backup System Files 132 Restore System Files 132 Upgrade Binaries 132 Upgrade Configuration 132 Uploa
4.1 Configuration Mode: File Menu 4.1.1 Open Configuration This command displays the Select B5800 menu used to receive a systems configuration settings. See Loading a Configuration 45 . The same action is performed by the icon in the Main Toolbar. The Select B5800 menu is also used for other actions such as reboot and sending a configuration. If the unit required is not found, the Unit/Broadcast Address can be changed and then Refresh clicked.
Menu Bar Commands: Configuration Mode: File Menu · Working Directory (.cfg files) Sets the directory into which Branch Gateway Manager saves .cfg files. By default this is the Branch Gateway Manager application's program directory. · This folder location is also used for the Recreate IP Office SD Card 116 command. It uses sub-folders of the \Memory Cards folder at the specified locations.
4.1.6 Preferences This command displays a menu for configuring various aspects of Branch Gateway Manager's operation. The menu is divided into a number of tabs. · Preferences · Directories 100 101 · Visual Preferences · Discovery 102 · Validation 106 · Security 103 104 4.1.6.1 Preferences This tab is accessed through File | Preferences and then selecting the Preferences sub-tab. · Edit Communication Port: Default = On. This field shows or hides the base communication port settings.
Menu Bar Commands: Configuration Mode: File Menu 4.1.6.2 Directories This tab is accessed through File | Preferences and then selecting the Directories sub-tab. These fields set the default location where Branch Gateway Manager will look for and save files. This tab is also accessed by the File | Change Working Directory command. · Working Directory (.cfg files) Sets the directory into which Branch Gateway Manager saves .cfg files.
4.1.6.3 Discovery This tab is accessed through File | Preferences and then selecting the Discovery sub-tab. These settings affect the Select B5800 menu used by Branch Gateway Manager to discovery systems. · TCP Discovery: Default = On. This setting controls whether Branch Gateway Manager uses TCP to discover systems. The addresses used for TCP discovery are set through the IP Search Criteria field below. · NIC IP/NIC Subnet This area is for information only.
Menu Bar Commands: Configuration Mode: File Menu 4.1.6.4 Visual Preferences This tab is accessed through File | Preferences and then selecting the Visual Preferences sub-tab. · Icon size Sets the size for the icons in the navigation pane between Small, Medium or Large. · Multiline Tabs: Default = Off. In the details pane, for record types with more than two tabs, Branch Gateway Manager can either use buttons to scroll the tabs horizontally or arrange the tabs into multiple rows.
4.1.6.5 Security This tab is accessed through File | Preferences and then selecting the Security sub-tab. Controls the various security settings of Branch Gateway Manager. To control the security settings of the system, see Security Mode 59 . All settings, except Secure Communications, can only be changed when a configuration has been opened using a user name and password with Administrator rights or security administration rights.
Menu Bar Commands: Configuration Mode: File Menu · Secure Communications: Default = On. When selected, any service communication from Branch Gateway Manager to the system uses the TLS protocol. This will use the ports set for secure configuration and secure security access. It also requires the configuration and or security service within the system's security configuration settings to have been set to support secure access.
4.1.6.6 Validation This tab is accessed through File | Preferences and then selecting the Validation sub-tab. By default Branch Gateway Manager validates the whole configuration when it is loaded and individual fields whenever they are edited. This tab allows selection of when automatic validation should be applied to configuration files loaded into Branch Gateway Manager. · Validate configuration on open Automatically validate configuration files when they are opened in Branch Gateway Manager.
Menu Bar Commands: Configuration Mode: File Menu 4.1.8 Advanced 4.1.8.1 Erase Configuration This command returns the configuration settings of a system back to their default values system's security settings or audit trail record. 57 . It does not affect the When this command is used, the Select B5800 menu is displayed. Once a system is selected, a valid configuration user name and password are required to complete the action. 4.1.8.
· When shutdown, the LEDs shown on the system are as follows. Do not remove power from the system or remove any of the memory cards until the system is in this state: · LED1 on each IP500 base card installed will also flash red rapidly plus LED 9 if a trunk daughter card is fitted to the base card. · The CPU LED on the rear of the system will flash red rapidly. · The System SD and Optional SD memory card LEDs on the rear of the system are extinguished.
Menu Bar Commands: Configuration Mode: File Menu 4.1.8.4 Upgrade This command starts the Upgrade Wizard tool. This tool is used to compare the software level of the control unit and modules within systems against the software level of the .bin binary files Branch Gateway Manager has available. The Upgrade Wizard can then be used to select which units to upgrade. · WARNING Incorrect use of the upgrade command can halt system operation and render units in the system unusable.
· Restart IP Phones For Branch Gateway Manager 8.1 and higher the Restart IP Phones option can be used. This will cause those phone to load any upgrade phone firmware included in the system upgrade (if using the system's memory card as their firmware file source). Searching for Particular Systems The default address used by the Upgrade Wizard is the address shown in the Branch Gateway Manager title bar, which is selected through File | Preferences 102 .
Menu Bar Commands: Configuration Mode: File Menu 4.1.8.5 Change Mode This command is not used with Avaya Branch Gateway systems. Avaya Branch Gateway Manager 10.
4.1.8.6 Audit Trail The audit trail lists the last 16 actions performed on the system from which the configuration loaded into Branch Gateway Manager was received. It includes actions by service users such as getting the configuration, sending a configuration back, reboots, upgrades and default the system. Audit trail events can be output to a Syslog server through the system's System | System Events settings. The last failed action is always recorded and shown in red.
Menu Bar Commands: Configuration Mode: File Menu Avaya Branch Gateway Manager 10.
4.1.8.7 Security Settings This command is used to switch the Branch Gateway Manager application to security mode. In that mode, Branch Gateway Manager is used to edit the security settings of a system. 4.1.8.8 Erase Security Settings (Default) This command returns the security settings of a system back to their default values. This action does not affect the system's configuration or audit trail record. When this command is used, the Select B5800 menu is displayed.
Menu Bar Commands: Configuration Mode: File Menu 4.1.8.10 Format IP Office SD Card This command allows suitable SD cards to be formatted by the Branch Gateway Manager PC. The system supports SD cards with the following format: SDHC minimum 4GB FAT32 format (Single partition, SDHC, class2+, FAT32, SPI & SD bus). Non-Avaya supplied cards of the same format can be used a system's Optional SD slot for additional actions such as backup.
4.1.8.11 Recreate IP Office SD Card This command can be used with the System SD cards used by IP500 V2 control units. It allows Branch Gateway Manager to copy all the files and folders used by a system when starting onto the card that has been place into the card slot of the PC running Branch Gateway Manager. It updates the card with the version of those files installed with the Branch Gateway Manager application. It includes the binary files for the system, external expansion modules and phones.
Menu Bar Commands: Configuration Mode: File Menu · A-Law or U-Law PCM (Pulse Code Modulation) is a method for encoding voice as data. In telephony, two methods of PCM encoding are widely used, A-Law and U-Law (also called Mu-Law or µ-Law). Typically U-Law is used in North America and a few other locations while A-Law is used elsewhere.
4.1.8.12 Launch Voicemail Pro Client If the Standalone Voice Mail client is installed on the same PC as Branch Gateway Manager, this link can be used to launch the Standalone Voice Mail client. This can also be done by clicking on the toolbar. icon in the Branch Gateway Manager 4.1.8.13 System Status System Status is an application that can be used to monitor and report on the status of a system.
Menu Bar Commands: Configuration Mode: File Menu 4.1.8.14 LVM Greeting Utility This command launches a utility that can be used to convert .wav files to the formats used by Embedded Voicemail. The source file must be in the standard format used for all system applications: PCM, 8kHz 16-bit, mono. The resulting named greeting files can then be transferred to the Embedded Voicemail memory card and selected as auto attendant greetings.
· SNMP trap destination 1 from System Manager IP address · All SNMP traps active · WebLM client active · WebLM service address from System Manager IP address · Remove all default extension users, leaving “NoUser” and “RemoteManager” Avaya Branch Gateway Manager 10.
Menu Bar Commands: Configuration Mode: File Menu 4.1.8.16 Memory Card Command These commands are used with the memory cards installed in IP Office Aura Edition control units. 4.1.8.16.1 Shutdown This command can be used to shutdown operation of IP Office Aura Edition memory cards. This action or a system shutdown 107 must be performed before a memory card is removed from the unit. Removing a memory card while the system is running may cause file corruption.
4.1.10 Import/Export 4.1.10.1 Export This command allows you to export the selected parts of the configuration to either a set of CSV text files (.csv) or a single binary file (.exp). The display shows those exportable record types for which the configuration contains records. The File Type and the Save In path can be selected at the base. The default location used is sub-directory of the Branch Gateway Manager application directory based on system name of the currently loaded system.
Menu Bar Commands: Configuration Mode: File Menu 4.1.10.2 Import This command allows you to import configuration settings. Two formats are supported. Binary files (.exp) are settings previously exported from a system using File | Import /Export | Export 122 . CSV text files (.csv) can also be exported from a system or can be created using a plain text editor. For the selected File Type and the Look In path, the window displays the file or files found.
4.2 Configuration Mode: View Menu 4.2.1 Toolbars This command allows selection of which toolbars should be shown or hidden in configuration mode. A tick mark is displayed next to the name of those toolbars that are currently shown. 4.2.2 Tooltip This setting control whether additional tooltips are displayed when Branch Gateway Manager is running in simplified view 124 mode. 4.2.3 Navigation Pane This command shows or hides the Navigation Pane.
Menu Bar Commands: Configuration Mode: View Menu 4.2.10 TFTP Log This command displays the TFTP Log window. This window shows TFTP traffic between Branch Gateway Manager and devices that uses TFTP to send and receive files. For example, the TFTP Log below shows an Avaya IP phone requesting and then being sent its software files. Avaya Branch Gateway Manager 10.
4.3 Configuration Mode: Tools Menu 4.3.1 Export | User During a Avaya Branch Gateway R6.1 to R6.2 upgrade, users are not automatically created in System Manager. Before an R6.1 to R6.2 upgrade, Avaya Branch Gateway users must be exported to a file and then the file must be imported to System Manager. This feature allows you to export all users or selected users from a loaded configuration to an XML file that is then imported in System Manager. The default filename is _Users.xml.
Menu Bar Commands: Configuration Mode: Tools Menu 4.3.5 MSN/DID Configuration This menu can be used to populate the Incoming Call Route table with a range of MSN or DID numbers. In the example above, the customer has ten DID numbers starting at 01505392201 with the central office exchange passing through 3 digits for each. Having selected the number of presentation digits (3), set the range (10) and selected the first destination (201); clicking Add created the ten incoming call routes (201 to 210).
4.3.6 Print Button Labels This option is only enabled if a version of DESI software is also installed on the same PC as Branch Gateway Manager. It can then be used when a system configuration is loaded in Branch Gateway Manager. DESI software can be obtained from the Avaya support web site (http://support.avaya.com) or from DESI (http//www. desi.com). Currently, though all users are shown, only 1400 and 1600 phones are supported by DESI templates.
Menu Bar Commands: Configuration Mode: Tools Menu 4.3.7 Import Templates Branch Gateway Manager can be used to import and use trunk templates 190 . SIP trunk templates can be used to add SIP trunks. Analog trunk templates can also be applied to existing analog trunks. The templates need to be stored in a specific Branch Gateway Manager sub-folder \Templates. Some templates may be supplied with the Branch Gateway Manager application and will be automatically installed to the correct location.
4.4 Security Mode These commands are available when the Branch Gateway Manager is in security configuration mode. 4.4.1 Open Security Settings This command displays the Select B5800 menu to select and load a system's security settings. This requires entry of a user name and password with rights to access security settings of the selected system.
Menu Bar Commands: Security Mode 4.5 Embedded File Management For control units with a memory card installed, the contents of the card can be viewed using Branch Gateway Manager. This view can also be used to add and remove files from the card. This may be useful when the memory card is being used to store Music on Hold or IP phone firmware files. For Linux based systems access to the /opt/ipoffice folder is provided.
4.5.1 Open File Settings Select a system and display the contents of its memory cards if any are present and in use. 4.5.2 Close File Settings Close the current memory card contents listing without exiting embedded file management mode. 4.5.3 Refresh File Settings This command can be used to request a file update from the system. 4.5.4 Upload File This command can be used to select and upload a file to the memory card in the system. 4.5.
Menu Bar Commands: Embedded File Management 4.5.11 Upload Phone Files For IP Office Aura Edition control units, use Upload System Files 132 . 4.5.12 Copy System Card This command is available for IP500 V2 systems that have an Optional SD card installed in addition to the mandatory System SD card. When this command is selected, the system will copy the folders and files on its System SD card to the Optional SD card. Any matching files and folders already present on the Optional SD card are overwritten.
Chapter 5. Configuration Settings Avaya Branch Gateway Manager 10.
Configuration Settings: 5. Configuration Settings This following sections detail the various configuration settings provided for different record types within the system configuration. Depending on the type and locale of the system some settings and tabs may be hidden as they are not applicable. Other settings may be grayed out. This indicates that the setting is either for information only or that another setting needs to be enabled first.
· Firewall Profile 371 Use to control the types of data traffic that can cross into or out of the system. · IP Route 376 These records are used to determine where data traffic on the system should be routed. · Account Code 378 Used for call logging and to control the dialing of certain numbers. · Tunnel 382 Used to created IPSec and L2TP data tunnels. · User Rights 389 Provide templates to control the settings applied to associated users.
Configuration Settings: 5.1 BOOTP BOOTP is protocol used by devices to request software when restarting. It is used when upgrading the control unit within a system or when the core software within the control unit has been erased. When running, Branch Gateway Manager can respond to BOOTP requests and, if it finds a matching BOOTP record for the system, provide the software file indicated by that record.
5.2 Operator These settings are not used for Avaya Branch Gateway systems. Avaya Branch Gateway Manager 10.
Configuration Settings: Operator 5.3 System There is one System record for each system being managed. The following tabs are part of the System form: · System 140 General settings for the system. · LAN1 145 Network settings for the RJ45 Ethernet LAN port on the control unit. · LAN2 153 Network settings for the RJ45 Ethernet WAN port on the control unit. · DNS 154 Specify the Domain Name Server addresses to use for address resolution. · Voicemail 155 Details the type and location of the voicemail server.
5.3.1 System Usability Mergeable: These settings are mergeable. However, changes to Locale, License Server IP Address or Favor RIP Routes over Static Routes require a reboot. These settings are mergeable. However, changes to Locale or Favor RIP Routes over Static Routes require a reboot. Configuration Settings · Name: Default: = System MAC Address. A name to identify this system. This is typically used to identify the configuration by the location or customer's company name.
Configuration Settings: System · On systems with an Avaya memory card, the LAN1 IP Address can be entered to specify that memory card as the TFTP file source. The files required for download must be transferred onto the card using either TFTP from the PC command line (see File Writer IP Address below) or through Embedded File Management 114 . · 1100, 1200, 1600 and 9600 Series IP phones do not support TFTP and require an HTTP Server IP Address (see below) to be specified.
· Local Number Length: Default = Blank (Off). Range = Blank (Off) or 3 to 15. Set the default length for extension numbers for extensions, users and hunt groups. Entry of an extension number of a different length will cause an error warning within Branch Gateway Manager. This field is intended for B5800 Branch Gateway systems where fixed length extension numbering is a requirement. Note that the Branch Prefix and the Local Number Length must not exceed 15 digits. · Proactive: Default = 60 seconds.
Configuration Settings: System · Time Offset: Default = 00:00 This value is not normally set as any time changes, including daylight saving changes, that occur on the PC will be matched by the system. · If you are running Branch Gateway Manager when the voicemail server starts, voicemail does not start as a time server. It is therefore recommended that you have no copy of Branch Gateway Manager running when you start or restart the voicemail server.
· Favour RIP Routes over Static Routes: Default = Off RIP 377 can be enabled on the system LAN1 145 and LAN2 153 interfaces, and on specific Services 336 . When this setting is on, the RIP route to a destination overrides any static route to the same destination in the system's IP Routes 376 , regardless of the RIP route's metric. The only exception is RIP routes with a metric of 16 which are always ignored.
Configuration Settings: System 5.3.2 LAN1 This tab is used to configure the behavior of the services provided by the system's first LAN interface. Depending in the control unit, up to 2 LAN's (LAN1 and LAN2) can be configured. The relationship between the physical RJ45 Ethernet ports and LAN1 and LAN2 within the system configuration varies as follows: · IP Office Aura Edition The control unit has 2 RJ45 Ethernet ports, marked as LAN and WAN. These form a full-duplex managed layer-3 switch.
5.3.2.1 LAN Settings This form is used to set the general LAN settings for the LAN interface such as the IP address mode. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · IP Address: Default = 192.168.42.1 or DHCP client. See Default Settings 57 . This is the IP address of the Control Unit on LAN1.
Configuration Settings: System 5.3.2.2 VoIP This form is used to set the system defaults for VoIP operation on the LAN interface. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · H.323 Gatekeeper Enable: Default = On This settings enables gatekeeper operation. · SIP Trunks Enable: Default = On This settings enables support of SIP trunks. · SIP Registrar Enable: Default = On.
· DSCP Mask (Hex): Default = FC (Hex)/63 (decimal). Range = 00 to FC (Hex)/0 to 63 (decimal) Allows a mask to be applied to packets for the DSCP value. · SIG DSCP (Hex): Default = 88 (Hex)/34 (decimal). Range = 00 to FC (Hex)/0 to 63 (decimal) This setting is used to prioritize VoIP call signaling. · DHCP Settings · Primary Site Specific Option Number (SSON): Default = 176. Range = 128 to 254. A site specific option number (SSON) is used as part of DHCP to request additional information.
Configuration Settings: System 5.3.2.3 Network Topology STUN (Simple Traversal of UDP through NAT) is a mechanism used with overcome the effect of NAT firewalls. The network address translation (NAT) action performed by this type of firewall can have negative effects on VoIP calls. Test packets are sent by the system to the address of the external STUN server, those packets crossing the firewall in the process. The STUN server replies and includes copies of the packets it received in the reply.
· Port Restricted Cone NAT A port restricted cone NAT is like a restricted cone NAT, but the restriction includes port numbers. Specifically, an external host can send a packet, with source IP address X and source port P, to the internal host only if the internal host had previously sent a packet to IP address X and port P. SIP packets needs to be mapped. Keep-alives must be sent to all ports that will be the source of a packet for each ITSP host IP address.
Configuration Settings: System 5.3.2.4 SIP Registrar This tab is used to set the system parameters for the system acting as a SIP Registrar to which SIP endpoint devices can register. Separate SIP registrars can be configured on LAN1 and LAN2. SIP endpoints are also still subject to the extension capacity limits of the system. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system.
5.3.2.5 DHCP Pools DHCP pools allows the configuration of up to 8 ranges of IP addresses for allocation by the system when acting as a DHCP server. By default the DHCP settings (IP Address, IP Mask and Number of DHCP IP Addresses) set on the LAN Settings 146 tab are reflected by the first pool here. · For support of PPP Dial In address requests, at least one of the pools must be on the same subnet as the system's LAN.
Configuration Settings: System 5.3.3 LAN2 This set of tabs is used to configure the system's second LAN interface. Usability · · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings The fields available for LAN2 are the same as for LAN1 145 except for the following additional field: · Firewall: Default = (No firewall) Allows the selection of a system firewall to be applied to traffic routed from LAN2 to LAN1.
5.3.4 DNS DNS is a mechanism through which the URL's requested by users, such as www.avaya.com, are resolved into IP addresses. These requests are sent to a Domain Name Server (DNS) server, which converts the URL to an IP address. Typically the internet service provider (ISP) will specify the address of the DNS server their customers should use. WINS (Windows Internet Name Service) is a similar mechanism used within a Windows network to convert PC and server names to IP addresses via a WINS server.
Configuration Settings: System 5.3.5 Voicemail The following settings are used to set the system's voicemail server type and location. Fields are enabled or grayed out as appropriate to the selected voicemail type. Refer to the appropriate voicemail installation manual for full details. Usability Mergeable: Pre-3.2 , 3.2+ (Changes to Voicemail Type require a reboot). Configuration Settings · Voicemail Type: Default = Embedded Voicemail Sets the type of voicemail system being used.
· Incoming Call Route Locale: The incoming call route locale, if set, is used if caller is external. · User Locale: The user locale, if set, is used if the caller is internal. · System Locale: If no user or incoming call route locale is set, the system locale is used unless overridden by a short code locale. · Add/Display VM Locales: Release 6.2+. For new IP500 V2 SD cards and cards recreated using Branch Gateway Manager, the following Embedded Voicemail languages set are placed onto cards by default.
Configuration Settings: System · The capability to turn this feature off is provided because there may be networks where the DTMF digits may not correctly reach the messaging system due to a provider’s network characteristics. When this feature is turned Off (check box is not selected), the DTMF digits are not automatically sent. Instead, the caller will dial the user’s mail box number to manually send the required DTMF digits to access the mailbox.
· Retries – the range is 0 to 5. The default setting is 0. · Retry Timeout – provided in the format M:SS (minute:seconds). The range can be set in 15-second increments. The minimum setting is 15 seconds and the maximum setting is 5 minutes. The default setting is 15 seconds · SIP Settings These settings are used for calls made or received on a SIP line where any of the line’s SIP URI fields are set to use internal data. · SIP Name: Default = Blank on Voicemail tab/Extension number on other tabs.
Configuration Settings: System 5.3.6 Telephony This tab is used to set the default telephony operation of the system. Some settings shown here can be overridden for individual users through their User | Telephony 281 tab. The settings are split into a number of sub-tabs. 5.3.6.1 Telephony This form is used to configure a wide range of general purpose telephony settings for the whole system. Usability Mergeable: a reboot. These settings are mergeable.
· Ring Delay: Default = 5 seconds. Range = 0 to 98 seconds. This setting is used when any of the user's programmed appearance buttons is set to Delayed ringing. Calls received on that button will initially only alert visually. Audible alerting will only occur after the ring delay has expired. This setting can be overridden by a ring delay set for an individual user (User | Telephony | Multi-line Options | Ring Delay 285 ). · Call Priority Promotion Time (secs): Default = Disabled.
Configuration Settings: System · Media Security (H.323): Default = Disable. Release 6.x+ This setting defines the Media Security setting for all H.323 extensions whose Media Security field is set to the value System Default. Note that Secure RTP (SRTP) is not supported on H.323 lines. When a new H.323 extension is added, the default setting in its Media Security field is System Default, for which the operation is determined by the setting that is defined here. The Media Security (H.
· When this option is on (checked), an incoming SIP invite with SIPS URI if targeted to a SIP trunk (SM line or SIP line) is rejected if the target trunk is not configured with SIPS in the URI Type field. Avaya Branch Gateway Manager 10.
Configuration Settings: System 5.3.6.2 Tones and Music This page is used to configure the various tones and music on hold sources used by the system. Usability Mergeable: Pre-3.2 , 3.2+ Changes to Busy Tone Detection. require a reboot. On pre-Release 6.x systems, changes to the hold music System Source require a reboot. Deleting any of the hold music Alternate Sources also requires a reboot. Configuration Settings · Conferencing Tone: Default = Entry & Exit Tones.
· Busy Tone Detection: Default = System Frequency (Tone defined by system locale) Allows configuration of the system's busy tone detection settings on lines that do not provide reliable disconnect signalling. In that case, the system will use tone disconnect clearing to disconnect such lines after 6 seconds of continuous tone. The default tone (frequency and on/off cadence) detection used is defined by the system locale 796 . The settings should not be adjusted unless advised by Avaya Technical Support.
Configuration Settings: System 5.3.6.3 Call Log The system can store a centralized call log 723 for users. Each users' centralized call log can contain up to 30 call records for user calls. When this limit is reached, each new call records replaces the oldest previous record. On Avaya phones with a fixed Call Log or History button (1400, 1600, 9500 and 9600 Series), that button can be used to display the user's centralized call log. The centralized call log is also used for M-Series and T-Series phone.
5.3.7 Directory Services Directory services can be used to import directory records (names and numbers) from external sources. These sets of records are regularly re-imported. For systems, the directory records can come from the following sources: · LDAP Import 171 The system can import up to 5000 LDAP records for use within directories shown by user phones and applications. LDAP import is configured through the System | Directory Services | LDAP 171 form. The LDAP used is LDAP Version 2.
Configuration Settings: System Avaya Branch Gateway Manager 10.
Use of Directory Records Directory records are used for two types of function: · Directory Dialing Directory numbers are displayed by user applications such as SoftConsole. Directory numbers are viewable through the Dir 596 function on many Avaya phones (Contacts or History). They allow the user to select the number to dial by name. The directory will also contain the names and numbers of users and hunt groups on the system.
Configuration Settings: System Directory Special Characters The following characters are supported in directory records. They are supported in both system configuration records and in imported records. · ? = Any Digit Directory records containing a ? are only used for name matching against the dialed or received digits on outgoing or incoming. They are not included in the directory of numbers to dial available to users through their phones or applications.
Imported Records · Imported directory records are temporary until the next import refresh. They are not added to the system's configuration. · They cannot be viewed or edited using Branch Gateway Manager or edited by a system phone 742 user. · The temporary records are lost if the system is restarted. However the system will request a new set of imported directory records after a system restart. · The temporary records are lost if a configuration containing Directory changes is merged.
Configuration Settings: System 5.3.7.1 LDAP The system supports LDAP Version 2. LDAP (Lightweight Directory Access Protocol) is a software protocol for enabling anyone to locate organizations, individuals, and other resources such as files and devices in a network, whether on the Internet or on a corporate intranet. LDAP is a "lightweight" (smaller amount of code) version of DAP (Directory Access Protocol), which is part of X.500, a standard for directory services in a network.
Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · LDAP Enabled: Default = Off This option turns LDAP support on or off. The system uses LDAP Version 2. If the server being queried is an LDAP Version 3 server, support for LDAP Version 2 requests may need to be enabled on that server (all LDAP Version 3 servers support LDAP Version 2 but do not necessarily have it enabled by default).
Configuration Settings: System Search Base: cn=users,dc=acme,dc=com Search Filter: (&(memberof=cn=group1,cn=users,dc=acme,dc=com)(telephonenumber=*)) · Number Attributes: Default = see below Enter the number attributes the server should return for each record that matches the Search Base and Search Filter. Other records could be ipPhone, otherIpPhone, facsimileTelephoneNumber, otherfacsimileTelephone Number, pager or otherPager. The attribute names are not case sensitive.
5.3.7.2 HTTP The system can use HTTP to import the directory records held by another system. Note that support for HTTP can be disabled. The Avaya HTTP Clients Only 140 setting (System | System 140 ) can restrict a system from responding to HTTP requests. The system's Unsecured Interface 80 security settings also included controls for HTTP access (HTTP Directory Read and HTTP Directory Write). Usability · Mergeable: These settings are mergeable.
Configuration Settings: System 5.3.8 System Events The system supports a number of methods by which events occurring on the system can be reported. These are in addition to the real-time and historical reports available through the System Status Application (SSA). · SNMP Reporting Simple Network Management Protocol (SNMP) allows SNMP clients and servers to exchange information. SNMP clients are built into devices such as network routers, server PC's, etc.
5.3.8.1 Configuration This form is used for general configuration related to system alarms. For email alarms the SMTP 180 tab is also used. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · SNMP Enabled: Default = Off Enables support for SNMP. This option is not required if using SMTP or Syslog. · Community (Read-only): Default = public The SNMP community name to which the system belongs.
Configuration Settings: System 5.3.8.2 Alarms This form is used to configure what can cause alarms to be sent using the different alarm methods. · Up to 5 alarm traps can be configured for use with the SNMP settings on the System | System Events | Configuration 176 tab. · Up to 3 email alarms can be configured for the sending using the systems System | SMTP destination is set as part of the alarm configuration below. 180 settings.
Type Events Event State Message Clock source changed 8kHz clock source changed. Details will be provided. Logon failed Logon failure reason will be provided. No free channels available No free channels were available. Outgoing group ID: . Hold music file failure Failed to load Hold Music source file. All resources in use The following system resources are all in use: will be provided.
Configuration Settings: System Type Events Event State Message Non-primary location boot alarm System running backup software. Invalid SD Card Incompatible or Invalid (System or Optional) SD Card fitted. Network link failure Network Interface name (ip address) has been disconnected. Network link operational Network Interface name (ip address) has been connected. System warm start System has been restarted (warm start). System cold start System has restarted from power fail (cold start).
5.3.9 SMTP SMTP can be used as the method of sending system alarms. The email destination is set as part of the email alarms configured in System | System Events | Alarms 177 . SMTP can be used with Embedded Voicemail for Voicemail Email Voicemail Email 274 address. 274 . The voicemail destination is set by the user's Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · IP Address: Default = 0.0.0.
Configuration Settings: System 5.3.10 SMDR Using a specified IP address, the system can send a call record for each completed call. Usability Mergeable: Pre-3.2 , 3.2+ . Configuration Settings · Output: Default = No Output. Select the type of call record that the system should output via IP. · No Output · SMDR Only: Send call records using the SMDR settings below. SMDR Configuration Settings These settings are shown if SMDR Only is selected as the Output.
5.3.11 Twinning These settings are used with Mobile Twinning, see the User | Mobility 295 tab for further details. · Outgoing CLI Warning Changing the outgoing CLI for calls requires the line provider to support that function. You must consult with your line provider before attempting to change the outgoing CLI, failure to do so may result in loss of service.
Configuration Settings: System 5.3.12 VCM This form allows adjustment of the operation of any Voice Compression Modules (VCM's) installed in a control unit. · The options for IP400 VCM controls are supported on IP400 systems from the Release 3.2/4.0 Q2 2007 Maintenance Releases onwards. · The same controls are supported for IP400 VCM cards in IP500 systems from Release 4.1 Q1 2008 Maintenance Release onwards. · The options for IP500 VCM controls are supported from Release 4.2 onwards.
· In order use T38 Fax connection, the Equipment Classification of an analog extension connected to a fax machine can be set Fax Machine. Additionally, the short code feature Dial Fax is available. Avaya Branch Gateway Manager 10.
Configuration Settings: System Measuring Channel Usability The System Status Application can be used to display voice compression channel usage. Within the Resources section it displays the number of channel in use. It also displays how often there have been insufficient channels available and the last time such an event occurred. These settings should only be adjusted under the guidance of Avaya support. Usability · Mergeable: These settings are mergeable.
5.3.13 CCR Not supported by Avaya Branch Gateway. Avaya Branch Gateway Manager 10.
Configuration Settings: System 5.3.14 Codecs This tab is used to set the codecs available for use with all IP (H.323 and SIP) lines and extensions and the default order of codec preference. · Avaya H.323 telephones do not support G.723 and will ignore it if selected. · For systems with H.323 lines and extensions, one of the G.711 codecs must be selected and used. · G.723 is not supported by Linux based systems.
5.4 Line The line settings shown in the system configuration will change according to the types of trunk cards installed in the control unit or added using external expansion modules. · WARNING: Changing Trunk Cards Changing the trunk card installed in an control unit will result in line settings for both the previous trunk card and the currently installed trunk card. In order to change the trunk card type in a particular card slot, the configuration must be defaulted.
Configuration Settings: Line Clock Quality Calls between systems using digital trunks (for example E1, E1R2, T1 PRI and BRI) require an common clock signal. The system will try to obtain this clock signal from an exchange through one of its digital trunks. This is done by setting the Clock Quality setting of that Line to Network. If there are multiple trunks to public exchanges, another trunk can be set as Fallback should the primary clock signal fail. Other trunks should be set as Unsuitable.
5.4.1 Trunk Templates The system supports the use of trunk templates. You can use SIP trunk templates to create new SIP trunks. You can use analog trunk templates to update the settings of existing analogue trunks. Avaya service providers can create templates from existing trunks. These templates are stored in a specific Branch Gateway Manager sub-folder \Templates. · Tested SIP Trunk Templates The SIP trunk services from selected SIP providers are tested as part of the Avaya DevConnect program.
Configuration Settings: Line 4. Use the Country and Service Provider drop-downs to select the required template. If Display All is selected, the Country selection changes to All Countries. 5. Click on Create New SIP Trunk. Avaya Branch Gateway Manager 10.
5.4.1.4 Applying a Template to an Analog Trunk You can apply an analogue trunk template to existing analogue trunks. · Note: This process will require the system to be rebooted for any changes to the trunk settings to be applied. 1. In the navigation or group pane, right click on the analogue trunk. 2. Select Copy Setting from Template. 3. The template and trunk selection menu is displayed. 4. Use the Country and Service Provider drop-downs to select the required template.
Configuration Settings: Line 5.4.1.5 Exporting Trunk Templates In addition to being used to import and apply templates, Branch Gateway Manager can be used to export the setting of an existing trunk as a template. · Templates exported using Branch Gateway Manager in IP Office Server Edition mode are saved by default on the IP Office Server Edition Primary Server. This means they are available to other administrators regardless of from which PC they are using IP Office Server Edition Branch Gateway Manager.
5.4.1.6 SIP Trunk Template Notes SIP trunk templates can be used with IP Office systems running all IP Office Essential Edition/IP Office Preferred Edition/IP Office Advanced Edition and IP Office Basic Edition - PARTNER® Mode modes.
Configuration Settings: Line Rel100 Supported Yes Yes — — T38 Fax Version Yes — Transport Yes — Low Speed Yes — High Speed Yes — TCF Method Yes — Max Bit Rate Yes — Eflag Start Timer Yes — Eflag Stop Timer Yes — Use Default Values Yes — Scan Line Fixup Yes — TFOP Enhancement Yes — Disable T30ECM Yes — Disable Eflags For First DIS Yes — DisableT30MR Compression Yes — NSF Override Yes — User Name — — Authentication Name — — Contact — — Password — —
5.4.2 Analog Line Analog trunks can be provided within the systems in the following ways. In all cases the physical ports are labeled as Analog. For full details of installation refer to the Avaya Branch Gateway Installation manual. · Using ICLID The system can route incoming calls using the ICLID received with the call. However ICLID is not sent instantaneously.
Configuration Settings: Line 5.4.2.1 Line This tab covers general settings for an analog line. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Line Number This parameter is not configurable, it is allocated by the system. · Card/Module: Indicates the card slot or expansion module being used for the trunk device providing the line. 1 to 4 match the slots on the front of the control unit from left to right.
5.4.2.2 Analog Options This tab covers analog line specific settings. The system wide setting CLI Type (System | Telephony | Tones & Music 163 ) is used for to set the incoming CLI detection method for all analogue trunks. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Channel: Set by the system. Shown for information only.
Configuration Settings: Line · Automatic: Default = Yes. (ATM4Uv2 card only) When set to Yes, the Default value is used. The value used for Default is set by the system Locale. When set to No, the Impedance value can be manually set. The Impedance field contains a list of possible values. · Automatic Balance Impedance Match: These controls can be used to test the impedance of a line and to then display the best match resulting from the test.
· Inter-Digit Pause: Default = 500ms. Range = 0 to 2550ms. Sets the pause between digits transmitted to the line. · Ring Detection · Ring Persistency: Default = Set according to system locale. Range = 0 to 2550ms. The minimum duration of signal required to be recognized. · Ring Off Maximum: Default = Set according to system locale. Range = 0 to 25500ms. The time required before signaling is regarded as ended.
Configuration Settings: Line 5.4.3 BRI Line BRI trunks are provided by the installation of a BRI trunk card into the control unit. The cards are available in different variants with either 2 or 4 physical ports. Each port supports 2 B-channels for calls. For full details of installation refer to the Avaya Branch Gateway Installation manual. Point-to-Point or Multipoint BRI lines can be used in either Point-to-Point or Point-to-Multipoint mode.
5.4.3.1 BRI Line Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Card/Module: Indicates the card slot or expansion module being used for the trunk device providing the line. 1 to 4 match the slots on the front of the control unit from left to right. Expansion modules are numbered from 5 upwards, for example trunks on the module in Expansion Port 1 are shown as 5.
Configuration Settings: Line · Voice Channels: Default = 2. Range = 0 to 2. The number of channels available for voice use. · Data Channels: Default = 2. Range = 0 to 2. The number of channels available for data use. If left blank, the value is 0. · Clock Quality: Default = Network Refer to the Avaya Branch Gateway Installation Manual for full details. This option sets whether the system should try to take its clock source for call synchronization and signalling from this line.
5.4.3.2 Channels This tab allows settings for individual channels within the trunk to be adjusted. To edit a channel either double-click on it or click the channel and then select Edit. To edit multiple channels at the same time, select the required channels using Ctrl or Shift and then click Edit. When editing multiple channels, fields that must be unique such as Line Appearance ID are not shown. Usability · Mergeable: These settings are not mergeable.
Configuration Settings: Line 5.4.4 E1 Line PRI trunks are provided by the installation of a PRI trunk card into the control unit. The IP500 PRI-U trunk card can be configured (see below) to one of those line types. The cards are also available with either 1 or 2 physical ports. The number of B-channels supported by each physical port depends on the line type of the card. · E1: 30 B-channels and 1 D-channel per port. · T1: 24 B-channels per port. · US PRI: 23 B-channels and 1 D-channel per port.
5.4.4.1 PRI Line Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Line Number This parameter is not configurable; it is allocated by the system. · Line Sub Type: Select to match the particular line type provided by the line provider. E1 PRI trunks support ETSI, ETSI CHI, QSIG A or QSIG B. · ETSI CHI is used to send the channel allocation ID (CHI) in the call setup signalling.
Configuration Settings: Line · Outgoing Channels This defines the number of channels available, on this line, for outgoing calls. This should normally be the same as Number of Channels field, but can be reduced to ensure incoming calls cannot be blocked by outgoing calls. Only available when the Line Sub Type is set to ETSI. · Voice Channels The number of channels available for voice use. Only available when the Line Sub Type is set to ETSI. · Data Channels The number of channels available for data use.
This field allows a trunk to be taken out of service if required for maintenance or if the trunk is not connected. The following fields are shown for a US T1 trunk card set to ETSI or QSIG operation. These cards have the same settings E1 PRI trunk cards set to ETSI or QSIG but only support 23 channels. · CSU Operation Tick this field to enable the T1 line to respond to loop-back requests from the line. · Haul Length: Default = 0-115 feet Sets the line length to a specific distance.
Configuration Settings: Line 5.4.4.2 Short Codes For some types of line, Line short codes can be applied to any digits received with incoming calls. The line Short Code tab is shown for the following trunk types which are treated as internal or private trunks: QSIG (T1, E1, H.323), BRI S0, H.323, . Incoming calls on those types of trunk are not routed using Incoming Call Route settings. Instead the digits received with incoming calls are checked for a match as follows: · Extension number.
5.4.4.3 Channels This tab allows settings for individual channels within the trunk to be adjusted. To edit a channel either double-click on it or click the channel and then select Edit. To edit multiple channels at the same time, select the required channels using Ctrl or Shift and then click Edit. When editing multiple channels, fields that must be unique such as Line Appearance ID are not shown. Usability · Mergeable: These settings are not mergeable.
Configuration Settings: Line 5.4.5 E1R2 Line PRI trunks are provided by the installation of a PRI trunk card into the control unit. The IP500 PRI-U trunk card can be configured (see below) to one of those line types. The cards are also available with either 1 or 2 physical ports. The number of B-channels supported by each physical port depends on the line type of the card. · E1: 30 B-channels and 1 D-channel per port. · T1: 24 B-channels per port. · US PRI: 23 B-channels and 1 D-channel per port.
5.4.5.1 E1-R2 Options (Line) Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Card/Module: Indicates the card slot or expansion module being used for the trunk device providing the line. 1 to 4 match the slots on the front of the control unit from left to right. Expansion modules are numbered from 5 upwards, for example trunks on the module in Expansion Port 1 are shown as 5.
Configuration Settings: Line 5.4.5.2 Channels This tab allows settings for individual channels within the trunk to be adjusted. To edit a channel, select the required channel or channels and click Edit. Usability 5.4.5.3 MFC Group These tabs show the parameter assigned to each signal in an MFC group. The defaults are set according to the Country (Locale) on the Line tab. All the values can be returned to default by the Default All button on the Advanced tab.
5.4.6 T1 Line PRI trunks are provided by the installation of a PRI trunk card into the control unit. The IP500 PRI-U trunk card can be configured (see below) to one of those line types. The cards are also available with either 1 or 2 physical ports. The number of B-channels supported by each physical port depends on the line type of the card. · E1: 30 B-channels and 1 D-channel per port. · T1: 24 B-channels per port. · US PRI: 23 B-channels and 1 D-channel per port.
Configuration Settings: Line 5.4.6.1 Line Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Line Number: Allocated by the system. · Card/Module: Indicates the card slot or expansion module being used for the trunk device providing the line. 1 to 4 match the slots on the front of the control unit from left to right.
· CSU Operation: Tick this field to enable the T1 line to respond to loop-back requests from the line. · Enhanced Called Party Number: Default = Off This option is not supported for systems set to the United States locale. Normally the dialed number length is limited to 15 digits. Selecting this option increases the allowed dialed number length to 30 digits. · Admin: Default = In Service. This field allows a trunk to be taken out of service if required for maintenance or if the trunk is not connected.
Configuration Settings: Line 5.4.6.2 Channels The settings for each channel can be edited. Users have the option of editing individual channels by double-clicking on the channel or selecting and editing multiple channels at the same time. Note that the Line Appearance ID cannot be updated when editing multiple channels. When editing a channel or channels, the settings available are displayed on two sub-tabs; T1 Edit Channel and Timers. Usability · Mergeable: These settings are not mergeable.
Timers Sub-Tab Settings This sub-tab allows various timers relating to operation of an individual channel to be adjusted. These should only be adjusted to match the requirements of the line provider. The following is a list of the default values. To reset a value, click on the current value and then right click and select from the default, minimize and maximize options displayed. · Outgoing Seizure: 10. · Wink Signal: 200. · Wink Start: 5000. · Incoming Dial Guard: 50. · Wink Validated: 80.
Configuration Settings: Line 5.4.7 T1 PRI Line PRI trunks are provided by the installation of a PRI trunk card into the control unit. The IP500 PRI-U trunk card can be configured (see below) to one of those line types. The cards are also available with either 1 or 2 physical ports. The number of B-channels supported by each physical port depends on the line type of the card. · E1: 30 B-channels and 1 D-channel per port. · T1: 24 B-channels per port. · US PRI: 23 B-channels and 1 D-channel per port.
5.4.7.1 Line Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Line Number: Allocated by the system. · Card/Module: Indicates the card slot or expansion module being used for the trunk device providing the line. 1 to 4 match the slots on the front of the control unit from left to right. Expansion modules are numbered from 5 upwards, for example trunks on the module in Expansion Port 1 are shown as 5.
Configuration Settings: Line · If no clock source is available, the system uses its own internal 8KHz clock source. · In scenarios where several systems are network via digital trunk lines, care must be taken to ensure that all the systems use the same clock source. The current source being used by a system is reported within the System Status Application. · CSU Operation Tick this field to enable the T1 line to respond to loop-back requests from the line.
5.4.7.2 Channels This tab allows settings for individual channels within the trunk to be adjusted. This tab is not available for trunks sets to ETSI or QSIG mode. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Channel Allocated by the system. · Incoming Group ID: Default = 0, Range 0 to 99999.
Configuration Settings: Line 5.4.7.3 TNS This tab is shown when the line Provider is set to AT&T. It allows the entry of the Network Selection settings. These are prefixes for alternative long distance carriers. When a number dialed matches an entry in the table, that pattern is stripped from the number before being sent out. This table is used to set field in the TNS (Transit Network Selection) information element for 4ESS and 5ESS exchanges. It is also used to set fields in the NSF information element.
5.4.7.5 Call By Call This tab is shown when the line Provider is set to AT&T. Settings in this tab are only used when calls are routed via a channel which has its Service set to Call by Call. It allows short codes to be created to route calls to a different services according to the number dialed. Call By Call reduces the costs and maximizes the use of facilities. Call By Call chooses the optimal service for a particular call by including the Bearer capability in the routing decision.
Configuration Settings: Line 5.4.8 S0 Line These settings are used for S0 ports provided by an S08 expansion module connected a control unit. For full details of installation refer to the Avaya Branch Gateway Installation manual. Though displayed as lines, these BRI ports are used for connection of ISDN2 devices such as video conferencing units or ISDN PC cards. · Calls received on IP, S0 and QSIG trunks do not use incoming call routes.
5.4.8.2 Short Codes For some types of line, Line short codes can be applied to any digits received with incoming calls. The line Short Code tab is shown for the following trunk types which are treated as internal or private trunks: QSIG (T1, E1, H.323), BRI S0, H.323, . Incoming calls on those types of trunk are not routed using Incoming Call Route settings. Instead the digits received with incoming calls are checked for a match as follows: · Extension number. · Line short codes (excluding ? short code).
Configuration Settings: Line 5.4.8.3 Channels This tab allows settings for individual channels within the trunk to be adjusted. For So channels this form is not used. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Line Appearance ID Not used with So lines. Avaya Branch Gateway Manager 10.
5.4.9 H323 Line These lines are added manually. They allow voice calls to be routed over data links within the system. They are therefore dependent on the IP data routing between the system and the destination having being configured and tested. · Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on incoming number received as if dialed on-switch. Line short codes on those trunks can be used to modify the incoming digits.
Configuration Settings: Line 5.4.9.1 Line Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Line Number: Default = 0. Range = 1 to 249. Enter the line number that you wish. Note that this must be unique. · Telephone Number: Used to remember the telephone number of this line. For information only. · Network Type: Default = Public.
5.4.9.2 Short Codes For some types of line, Line short codes can be applied to any digits received with incoming calls. The line Short Code tab is shown for the following trunk types which are treated as internal or private trunks: QSIG (T1, E1, H.323), BRI S0, H.323, . Incoming calls on those types of trunk are not routed using Incoming Call Route settings. Instead the digits received with incoming calls are checked for a match as follows: · Extension number. · Line short codes (excluding ? short code).
Configuration Settings: Line 5.4.9.3 VoIP This form is used to configure the VoIP setting applied to calls on the H.323 line. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings The VoIP settings available for an H.323 trunk depend on the Supplementary Services setting: · Standard H.
5.4.9.3.1 Standard H323 The following settings are applicable to trunks with their Supplementary Services set to H450, QSIG or None. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Gateway IP Address: Default = Blank Enter the IP address of the gateway device at the remote end. This address must not be shared by any other IP line (H.323, SIP, SES or IP DECT).
Configuration Settings: Line · DTMF Support: Default = Out of Band DTMF tones can be sent to the remote end either as DTMF tones within the calls audio path (In Band) or a separate signals (Out of Band). Out of Band is recommended for compression modes such as G.729 and G.723 compression modes where DTMF in the voice stream could become distorted.
5.4.10.2 Gateway This form is used to configure aspects of information exchange between the Avaya Branch Gateway and IP DECT systems. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Auto-Create Extension: Default = Off. If enabled, subscription of a handset with the DECT system causes the auto-creation of a matching numbered extension within the system configuration if one does not already exist.
Configuration Settings: Line 5.4.10.3 VoIP This form is used to configure the VoIP setting applied to calls on the IP DECT line. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. · Gateway IP Address: Default = Blank Enter the IP address of the gateway device at the remote end. This address must not be shared by any other IP line (H.323, SIP, SES or IP DECT).
5.4.11 SIP Line Use of SIP requires the following: 1. SIP Service Account An account or accounts with a SIP internet service provider (ITSP). The method of operation and the information provided will vary. The key requirement is a SIP URI, a web address of the form name@example.com. This is the equivalent of a SIP telephone number for making and receiving calls via SIP. 2.
Configuration Settings: Line SIP URIs Calls across SIP require URI's (Uniform Resource Identifiers), one for the source and one for the destination. Each SIP URI consists of two parts, the user part (for example name) and the domain part (for example example.com) to form a full URI (in this case name@example.com). SIP URI's can take several forms: · name@117.53.22.2 · name@example.com · 012345678@example.com Typically each account with a SIP service provider will include a SIP URI or a set of URI's.
5.4.11.1 Incoming Call Routing Incoming SIP calls are routed using Incoming Call Routes 348 in the same way as call arriving on other external trunks. The following Incoming Call Route fields are used to determine which route is the best match for a call. · Line Group ID This field is matched against the Incoming Group settings of the SIP URI (Line | SIP URI). This must be an exact match. · Incoming Number This field can be used to match the called details (TO) in the SIP header of incoming calls.
Configuration Settings: Line 5.4.11.2 SIP Line Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Line Number: Default = Automatically assigned. By default a value is assigned by the system. This value can be changed but it must be unique. · ITSP Domain Name: Default = Blank. This field is used to enter the domain part of the SIP URI provided by the ITSP. For example, in the SIP URI name@example.
· By Source IP Address This option uses the source IP address and port of the incoming request for association. The match is against the configured remote end of the SIP line, using either an IP address/port or the resolution of a fully qualified domain name. · "From" header hostpart against ITSP domain This option uses the host part of the From header in the incoming SIP request for association. The match is against the ITSP Domain Name above.
Configuration Settings: Line · URI Type: Default = SIP. Release 6.2+ When SIP or SIPS is selected in the drop-down box, the SIP URI format is used (for example, name@example.com). When Tel is selected in the drop-down box, the Tel URI format is used (for example, +1-425-555-4567). This affects the From field of outgoing calls. The To field for outgoing calls will always use the format specified by the short codes used for outgoing call routing.
SIP Prefix Operation The prefix fields Prefix, National Prefix, Country Code and International Prefix are available with the SIP Line settings. These fields are used in the following order: 1. If an incoming number (called or calling) starts with the + symbol, the + is replaced with the International Prefix. 2. If the Country Code has been set and an incoming number begins with that Country Code or with the International Prefix and Country Code, they are replaced with the National Prefix. 3.
Configuration Settings: Line 5.4.11.3 Transport Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. · ITSP Proxy Address and Calls Route via Registrar are mergeable. Configuration Settings · ITSP Proxy Address: Default = Blank This is the SIP Proxy address used for outgoing SIP calls.
Behaviour during Service unavailable A proxy server is considered Active once the system has received a response to an INVITE, REGISTER or OPTIONS. In the case of the proxy server responding with 503 - Service Unavailable, it should be considered Active - In Maintenance.
Configuration Settings: Line 5.4.11.4 SIP URI Having setup the SIP trunk to the SIP ITSP, the SIP URI's registered with that ITSP are entered on this tab. A SIP URI (Uniform Resource Identifier) is similar to an internet email address, for example name@example.com, or 01555326978@example.com and represents the source or destination for SIP connection. The URI consists of two parts, the user part (eg. name) and the host part (eg. example.com).
· PAI: Default = None. You can enable P-Asserted-Identity (PAI) headers to assert the identity of users in outgoing SIP requests or response messages. Use this setting to select the source of the user identity information or enter a value manually. The selectable options are: · None When selected, the P-Preferred-Identity header is used instead of the P-Asserted-Identity, in order to ensure compatibility with legacy networks.
Configuration Settings: Line 5.4.11.5 VoIP This form is used to configure the VoIP settings applied to calls on the SIP trunk. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Codec Selection: Default = System Default This field defines the codec or codecs offered during call setup. · The available codecs in default preference order are: G.711 A-Law, G.711 U-Law, G.729 and G.723.1.
· Encryptions: Default = RTP This setting allows selection of which parts of a media session should be protected using encryption. The default is to encrypt just the RTP stream (the speech). · Authentication: Default = RTCP This setting allows selection of which parts of the media session should be protected using authentication. The default is authenticate just the RTCP stream (call control signals). · Replay Protection: Displays the options for the SRTP window size. Currently not adjustable.
Configuration Settings: Line 5.4.11.6 T38 Fax The settings on this tab are only accessible if Re-invite Supported and Fax Transport Support are selected on the VoIP 262 tab. Fax relay cards. 727 is only supported on IP Office Aura Edition systems with IP500 VCM, IP500 VCM V2 and or IP500 Combo Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Use Default Values: Default = On.
5.4.11.7 SIP Credentials It is used to enter the ITSP username and password for the SIP account with the ITSP. If you have several SIP accounts going to the same ITSP IP address or domain name, you can enter up to 30 sets of ITSP account names and passwords on this tab. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings Use the Add..., Edit...
Configuration Settings: Line 5.4.12 SM Line This type of line can only be added in the configuration of an Avaya Branch Gateway system fitted with an B5800 Branch Gateway System SD card. This type of line is used to create a SIP connection between an B5800 Branch Gateway system and the Avaya Aura® Session Manager in the Avaya Aura® network.
· Send Port: When Network Configuration is set to TLS, the default setting is 5061. When Network Configuration is set to TCP, the default setting is 5060. · Listen Port: When Network Configuration is set to TLS, the default setting is 5061. When Network Configuration is set to TCP, the default setting is 5060. Avaya Branch Gateway Manager 10.
Configuration Settings: Line 5.4.12.2 VoIP Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Gateway IP Address: Default = Blank Enter the IP address of the gateway device at the remote end. This address must not be shared by any other IP line (H.323, SIP, SES or IP DECT). · Codec Selection: Default = System Default This field defines the codec or codecs offered during call setup.
· VoIP Silence Suppression: Default = Off When selected, this option will detect periods of silence on any call over the line and will not send any data during those silent periods. This feature is not used on IP lines using G.711 between systems. On trunk's between networked systems, the same setting should be set at both ends. · Fax Transport Support: Default = Off. This option is only available if Re-Invite Supported is selected.
Configuration Settings: Line 5.4.12.3 T38 Fax The settings on this tab are only accessible if Re-invite Supported and Fax Transport Support are selected on the VoIP 262 tab. Fax relay cards. 727 is only supported on IP Office Aura Edition systems with IP500 VCM, IP500 VCM V2 and or IP500 Combo Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Use Default Values: Default = On.
5.5 Control Unit The Control Unit form gives details of the system and some devices connected to or within the system. This includes some modules within the control unit as well as external expansion modules. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Device Number This is automatically allocated by the system. · Unit Type The name of the device. · Version The version of software running on each unit.
Configuration Settings: Control Unit 5.6 Extension By default, each extension is normally associated with a user and uses that user's directory number and other setting. Users with a log in code can move between extensions by logging in and out, so the directory number is not a fixed property of the extension. Non-IP Extensions Physical extension ports are either integral to the control unit or added by the installation of an analog or digital phone expansion module.
5.6.1 Extn This tab contains settings applicable to most types of extension. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Extension ID The physical ID of the extension port. Except for IP extensions, this settings is allocated by the system and is not configurable. · Base Extension: Range = 2 to 15 digits. This is the directory number of the extension's default associated user.
Configuration Settings: Extension · SIP extensions report the type of SIP phone registered or Unknown SIP device if no SIP device is currently registered as that extension. · Module This field indicates the external expansion module on which the port is located. BP indicates an analog phone extension port on the base or control unit. BD indicates a digital station (DS) port on the control unit. For an IP Office Aura Edition control unit, BD and BP is also followed by the slot number.
5.6.2 Analog This tab contains settings that are applicable to analog extensions. These extensions are provided by ports marked as POT or PHONE on control units and expansion modules. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Equipment Classification: Default = Standard Telephone Only available for analog extension ports. Changes to this setting are mergeable.
Configuration Settings: Extension · Hook Persistency: Default = 100ms. Range = 50 to 255ms. Defines the time frame (in milliseconds) in which the system will wait before determining that the phone is off-hook. · Flash Hook Pulse Width The following options are only available for analog extension ports. They define the length of loop break that will be considered a time break recall (TBR) signal. · Use System Defaults: Default = Selected (On) Use the default values appropriate to the system's locale.
5.6.3 VoIP This tab is only available for H.323 and SIP extensions. The settings available will vary depending on the extension type: · H.323 IP Extension · SIP Extension 262 264 5.6.3.1 H323 Extension These settings are shown for a H.323 IP extension. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · IP Address: Default = 0.0.0.0 The IP address of the phone.
Configuration Settings: Extension · Prefer – Media security is preferred. Attempt to use secure media first, and if unsuccessful fall back to non-secure media. This option is not available for H.323 extensions. · System Default – Use the system-wide default setting specified in the system Media Security (SIP) field ( System | Telephony | Telephony 160 ). · Advanced You are able to select this button when the Media Security field is set to Enforce or Prefer.
5.6.3.2 SIP Extension There settings are shown for SIP IP extensions. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · IP Address: Default = 0.0.0.0 The IP address of the phone. The default setting accepts connection from any address. If an address is entered, registration is only accepted from a device with that address.
Configuration Settings: Extension · System Default – Use the system-wide default setting specified in the system Media Security (SIP) field ( System | Telephony | Telephony 160 ). · Advanced You are able to select this button when the Media Security field is set to Enforce or Prefer. When selected, the Advanced Media Security Options are displayed. · Encryptions: Default = RTP This setting allows selection of which parts of a media session should be protected using encryption.
5.6.4 T38 Fax The settings on this tab are only accessible if Re-invite Supported and Fax Transport Support are selected on the VoIP 262 tab. Fax relay cards. 727 is only supported on IP Office Aura Edition systems with IP500 VCM, IP500 VCM V2 and or IP500 Combo Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Use Default Values: Default = On.
Configuration Settings: Extension 5.6.5 IP DECT This tab is displayed for IP DECT extensions. These are created manually after an IP DECT configuration or added automatically as DECT handsets subscribe to the DECT system. 233 line has been added to the Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system.
5.7 User Users are the people who use the system. They do not necessary have to be an extension user, for example users are used for RAS dial in data access. In addition, more users can be created than there are extensions, with users logging in to an extension when they want to receive calls. By default, a user is automatically created to match each extension. They are numbered from 201 upwards and the first 16 are placed in the hunt group Main (200), which is the default destination for incoming calls.
Configuration Settings: User Avaya Branch Gateway Manager 10.
Creating a User Right Based on an Existing User 1. Select User Rights. 2. In the group pane, right-click and select New User Rights from a User. 3. Select the user and click OK. Associating User Rights to a User 1. Select User Rights or User. 2. In the group pane, right-click and select Apply User Rights to Users. 3. Select the user rights to be applied. 4. On the Members of this User Rights sub tab select the users to which the user rights should be applied as their Working Hours User Rights. 5.
Configuration Settings: User 5.7.1 User Users are the people who use the system or are Dial In users for data access. A system User may or may not have an Extension Number that physical exists - this is useful if users do not require a physical extension but wish to use system features, for example voicemail, forwarding etc. NoUser is used to apply settings to extensions which have no associated user. Remote Manager is used as the default settings for dial in connections.
· When the system routes a call to the voicemail server it indicates the locale for which matching prompts should be provided if available. The locale sent to the voicemail server by the system is determined as show below. If the required set of prompts is not available, the voicemail will fallback to another appropriate language and finally to English (refer to the appropriate voicemail installation manual for details).
Configuration Settings: User Avaya Branch Gateway Manager 10.
5.7.2 Voicemail If a voicemail server application is being used on your system, each user has use of a voicemail mailbox. You can use this form to enable this facility and various user voicemail settings. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings: User · Voicemail Help Default = Off This option controls whether users retrieving messages are automatically given an additional prompt "For help at any time press 8." If switched off, users can still press 8 for help. For voicemail systems running in Intuity emulation mode, this option has no effect. On those systems the default access greeting always includes the prompt "For help at any time, press *4" (*H in the US locale).
· The Park & Page feature is supported when the system voicemail type is configured as Embedded Voicemail or Standalone Voice Mail. Park & Page is also supported on systems where Avaya Aura Messaging, Modular Messaging over SIP, or CallPilot (for IP Office Aura Edition with CS 1000 deployments) is configured as the central voice mail system and the local Embedded Voicemail or Standalone Voice Mail provides auto attendant operation.
Configuration Settings: User 5.7.3 DND Do not disturb prevents the user from receiving hunt group and page calls. Direct callers hear busy tone or are diverted to voicemail if available. It overrides any call forwarding, follow me and call coverage settings. A set of exception numbers can be added to list numbers from which the user still wants to be able to receive calls when they have do not disturb in use.
5.7.4 Short Codes Short codes entered in this list can only be dialed by the user. They will override any matching user rights or system short code. See Short Codes 425 for details. User and User Rights short codes are only applied to numbers dialed by that user. For example they are not applied to calls forwarded via the user. · WARNING User dialing of emergency numbers must not be blocked by the addition of short codes.
Configuration Settings: User 5.7.5 Source Numbers This form is used to enter values that have special usages. These are entered using the Add, Edit and Remove buttons. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system.
· ProgressEndsOverlapSend See Line | VoIP 231 . · SIP_OPTIONS_PERIOD=X (X = time in minutes) The system sends SIP options messages periodically to determine if the SIP connection is active. See Options Operations 242 for information on when SIP options messages are sent. The rate at which the messages are sent is determined by the combination of the Binding Refresh Time (in seconds) set on the Network Topology 149 tab and the SIP_OPTIONS_PERIOD parameter (in minutes).
Configuration Settings: User 5.7.6 Telephony This form allows you to set telephony related features for the user. These override any matching setting in the System | Telephony 159 tab. The settings are grouped into a number of sub-tabs. 5.7.6.1 Call Settings For details of the ringing tones, see Ring Tones Telephony 159 tab. 739 . DefaultRing uses the system default setting set through the System | Usability · Mergeable: These settings are mergeable.
· Busy on Held: Default = On If on, when the user has a call on hold, new calls receive busy treatment. They will follow the user's forward on busy setting or are diverted to voicemail. Otherwise busy tone (ringing for incoming analog calls) is played. This overrides call waiting when the user has a call on hold. The use of Busy on Held for users with multiple call appearance buttons is deprecated and Branch Gateway Manager will prompt whether it should switch off the feature off for such a user.
Configuration Settings: User 5.7.6.2 Supervisor Settings These settings relate to user features normally only adjusted by the user's supervisor. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings A symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is associated using the Working Hour User Rights 271 and Out of Hours User Rights 271 settings.
· Force Login: Default = Off If checked, the user must log in using their Login Code to use any extension including an extension to which they are the default associated user (Base Extension). For example, if Force Login is ticked for user A and user B has logged onto A's phone, when B logs off user A is not automatically associated with their normal phone and instead must log back on. If Force Login was not ticked, A would be automatically logged back in.
Configuration Settings: User 5.7.6.3 Multi-line Options Multi-line options are applied to a user's phone when the user is using an Avaya phones which supports appearance buttons (call appearance, line appearance, bridged and call coverage). See Appearance Button Operation 653 . Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system.
· Reserve Last CA: Default = Off. Used for users with multiple call appearance buttons. When selected, this option stops the user's last call appearance button from being used to receive incoming calls. This ensures that the user always has a call appearance button available to make an outgoing call and to initiate actions such as transfers and conferences.
Configuration Settings: User 5.7.6.4 Call Log The system can store a centralized call log 723 for users. Each users' centralized call log can contain up to 30 call records for user calls. When this limit is reached, each new call records replaces the oldest previous record. On Avaya phones with a fixed Call Log or History button (1400, 1600, 9500 and 9600 Series), that button can be used to display the user's centralized call log. The centralized call log is also used for M-Series and T-Series phone.
5.7.7 Forwarding This form can be used to check and adjust a user's call forwarding and follow me settings. Follow Me is intended for use when the user is present to answer calls but for some reason is working at another extension. For example; temporarily sitting at a colleague's desk or in another office or meeting room. As a user, you would use Follow Me instead of Hot-Desking if you don't have a log in code or you don't want to interrupt you colleague also receiving their own calls.
Configuration Settings: User · Forward Internal Calls: Default = On. This option, when checked, sets that internal calls should be also be forwarded immediately when forward unconditional is active. · Forward On Busy: Default = Off When checked and a forward number is set, external calls are forwarded when the user's extension is busy. The number used is either the Forward Number set for Forward Unconditional or if set, the separate Forward Number set under Forward On Busy.
5.7.8 Dial In Use this dialogue box to enable dial in access for a remote user. An Incoming Call Route and RAS service must also be configured. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Dial In On: Default = Off When enabled, dial in access into the system is available via this user. · Dial In Time Profile: Default = Select the Time Profile 369 applicable to this User account.
Configuration Settings: User 5.7.9 Voice Recording Avaya Branch Gateway R6.2 does not support voice recording. Avaya Branch Gateway Manager 10.
5.7.10 Button Programming This tab is used to assign functions to the programmable keys provided on many Avaya telephones. For full details of button programming refer to the section Button Programming 507 . Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings: User 5.7.11 Menu Programming These menus control a range of options that are specific to different types of phones. The functions become accessible when the user logs in on the appropriate type of phone. 5.7.11.1 T3 Telephony Not used for a Avaya Branch Gateway system. 5.7.11.2 Huntgroup Avaya 1400, 1600, 9500 and 9600 Series phone users can control various settings for selected hunt groups. Usability · Mergeable: These settings are mergeable.
5.7.11.3 1400/1600 This menu applies to 1400, 1600, 9500 and 9600 Series phones. Usability Configuration Settings · Include Forwarding in Menu: Default = On. This setting controls whether the user is able to view and use options to control their forwarding within the phone's menus. 5.7.11.4 4400/6400 4412, 4424, 4612, 4624, 6408, 6416 and 6424 phones have a Menu key, sometimes marked with an icon. When Menu is pressed, a number of default functions are displayed.
Configuration Settings: User 5.7.12 Mobility (Twinning) These settings relate to twinning features. These are where a user has a main or primary extension but also regularly answer calls at a secondary or twinned phone. These features are intended for a single user, they are not aimed at two users answering calls presented to a single primary extension. Twinning Twinning allows a user's calls to be presented to both their current extension and to another number.
5.7.12.1 Internal Twinning Internal twinning can be used to link two system extensions to act as a single extension. Typically this would be used to link a users desk phone with some form of wireless extension such as a DECT or WiFi handset. Internal twinning is an exclusive arrangement, only one phone may be twinned with another. When twinned, one acts as the primary phone and the other as the secondary phone.
Configuration Settings: User Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Internal Twinning: Select this option to enable internal twinning for a user. Internal Twinning cannot be selected for a user if they already have Mobility Features selected. · Twinned Handset: Default = Blank. For internal twinning, the drop-down list can be used to select an available user as the twinned calls destination.
5.7.12.2 Mobile Twinning This method of twinning can be used with external numbers. Calls routed to the secondary remain under control of the system and can be pulled back to the primary if required. If either leg of an alerting twinned call is answered, the other leg is ended. A number of controls are available in addition to those on this tab. · Button Programming Actions The Emulation | Twinning action can be used to control use of mobile twinning.
Configuration Settings: User Avaya Branch Gateway Manager 10.
Avaya Branch Gateway Manager 10.
Configuration Settings: User Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings A symbol indicates that the setting can also be set and locked within a set of user rights 389 with which the user is associated using the Working Hour User Rights 271 and Out of Hours User Rights 271 settings. The user rights applied can be controlled by a time profile 369 selected as the user's Working Hours Time Profile 271 setting.
· If there are any calls alerting or in progress through the system to the twin the user status is shown as alerting or in-use as appropriate. This includes the user showing as busy/in-use if they have such a call on hold and they have Busy on Held enabled. · If the user enables DND through Mobile Call Control or one-X Mobile client their status will show as DND/busy.
Configuration Settings: User 5.7.13 Phone Manager Options Not supported on Avaya Branch Gateway systems. 5.7.14 Hunt Group Memberships This tab displays the hunt group of which the user has been made a member. The tick boxes indicate whether the user's membership of each of those groups is currently enabled or disabled. Avaya Branch Gateway Manager 10.
5.7.15 Announcements Announcements are played to callers waiting to be answered. This includes callers being presented to hunt group members, ie. ringing, and callers queued for presentation. · The system supports announcements using Standalone Voice Mail or Embedded Voicemail. · If no voicemail channel is available for an announcement, the announcement is not played. · In conjunction with Standalone Voice Mail, the system allows a number of voicemail channels to be reserved for announcements.
Configuration Settings: User Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Announcements On: Default = Off. This setting enables or disables announcements. · Wait before 1st announcement: Default = 10 seconds. Range = 0 to 9999 seconds. This setting sets the time delay from the calls presentation, after which the first announcement should be played to the caller.
5.7.16 SIP This tab is available when a SIP trunk with a SIP URI 245 record has been added to the configuration. Various fields within the URI settings used by SIP trunks can be set to Use Internal Data. When that is the case, the values from this tab are used inserted into the URI when the user makes or receives a SIP call. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system.
Configuration Settings: User 5.7.17 Personal Directory Each user is able to have up to 100 personal directory records, up to the overall system limit of 10800. The overall system limit is 10800 record. Users are able to view and edit their personal directory through their phone. Directory records are used for two types of function: · Directory Dialing Directory numbers are displayed by user applications such as SoftConsole.
Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Index: Range = 01 to 99 or None. Not used for B5800 Branch Gateway. · Name: Range = Up to 31 characters. Enter the text to be used to identify the number. · Number: Range = Up to 31 digits plus * and #. Enter the number, without spaces, to be dialed. Wildcards are not supported in user personal directory records.
Configuration Settings: User 5.8 Hunt Group A hunt group is a collection of users accessible through a single directory number. Calls to that hunt group can be answered by any available member of the group. The order in which calls are presented can be adjusted by selecting different group types and adjusting the order in which group members are listed. · Call Presentation The order in which the available members of the hunt group are used for call presentation is selectable.
5.8.1 Hunt Group This tab is used to define the name, extension number and basic operation of the hunt group. It is also used to select the hunt group members. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Name: Range = Up to 15 characters The name to identify this hunt group. This field is case sensitive and must be unique. · Names should not start with a space.
Configuration Settings: Hunt Group · The Avaya Branch Gateway hunt group should be configured consistently with the hunt group administration at the core feature server that serves the survivable branch endpoints in normal mode. · Members included in the Avaya Branch Gateway hunt group should be only those members that are in the local branch, even if the core feature server hunt group includes additional members from other branches (that is, centralized users). · DDI Numbers: Default = Blank.
5.8.2 User List/Select Members The hunt group Select Members form is used to add and remove users from the hunt group. For hunt group's with a Ring Mode of Sequential or Rotary it is also used to set the order of use for the members of the hunt group. The filters section at the top of the form can be used to filter the users shown. To sort either table, click on the column header that should be used for the sort the table.
Configuration Settings: Hunt Group 5.8.3 Queuing When is a Call Queued? Any calls waiting to be answered at a hunt group are regarded as being queued. The Normalise Queue Length control allows selection of whether features that are triggered by the queue length should include or exclude ringing calls. · Additional Calls Once one call is queued, any further calls are also queued. When an available hunt group member becomes idle, the first call in the queue is presented.
Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Queuing On: Default = On This settings allows calls to this hunt group to be queued. The normal icon is replaced . · Queue Limit: Default = No Limit. Range = No Limit, 1 to 999 calls. This setting can be used to limit the number of calls that can be queued. Calls exceeding this limit are passed to voicemail if available or otherwise receive busy tone.
Configuration Settings: Hunt Group Hunt Group Queue Controls Hunt Group Queue Settings Manager Hunt group queuing is enabled using the Queuing On option on the Hunt Group | Queuing enabled, the Controls 313 tab. When icon is used for the hunt group. The following short code features/button programming actions can be used: Feature/Action Short Code Default Button Group SoftConsole SoftConsole can display up to 7 hunt group queues (an eight queue is reserved for recall calls).
5.8.4 Overflow Overflow can be used to expand the list of group members who can be used to answer a call. This is done by defining an overflow group or groups. The call is still targeted to the original group and subject to that group's settings, but is now presented to available members in the overflow groups in addition to its own available members. What Group Settings are Applied to Overflowing Calls? · Overflow calls still use the settings of the original target group.
Configuration Settings: Hunt Group Avaya Branch Gateway Manager 10.
Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Overflow Time: Default = Blank. Range = Off or 1 to 3600 seconds. For a group using queuing 313 , the Overflow Time sets how long a call queues before being presented to available agents in the group's Overflow Group List.
Configuration Settings: Hunt Group 5.8.5 Fallback Fallback settings can be used to make a hunt group unavailable and to set where the hunt group's calls should be redirected at such times. Hunt groups can be manually placed In Service, Out of Service or in Night Service. Additionally using a time profile, a group can be automatically placed in Night Service when outside the Time Profile settings.
Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Time Profile: Default = (No automatic night service) This field allows selection of a previously created Time Profile 369 . That profile then specifies the times at which it should use the manually selected Service Mode settings. Outside the period defined in the time profile, the hunt group behaves as if set to Night Service mode.
Configuration Settings: Hunt Group Hunt Group Fallback Controls Hunt Group Fallback Branch Gateway Manager Hunt group fallback selection is done through the Hunt Group | Fallback Controls The following short code features/button programming actions can be used: 319 tab. A time profile if required is set through the Time Profile | Time Profile tab. Feature/Action Set Hunt Group Night Service Short Code Clear Hunt Group Night Service Set Hunt Group Out of Service Default *20*N# 494 452 - Toggles.
5.8.6 Voicemail The system supports voicemail for hunt groups in addition to individual user voicemail mailboxes. · When is voicemail used? If voicemail is available and enabled for a hunt group, it is used in the following scenarios. · Voicemail Answer Time A call goes to voicemail when this timeout is reached, regardless of any announcement, overflow, queuing or other settings. The default timeout is 45 seconds.
Configuration Settings: Hunt Group Usability Release: 1.0+. · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Voicemail On Default = On When on, the mailbox is used by the system to answer the any calls to the group that reach the Voicemail Answer Time. Note that selecting off does not disable use of the group mailbox. Messages can still be forward to the mailbox and recordings can be placed in it.
· UMS Web Services: Default = Off. This option is used with Standalone Voice Mail. If enabled, the hunt group mailbox can be accessed using either an IMAP email client or a web browser. Note that the mailbox must have a voicemail code set in order to use either of the UMS interfaces. · Voicemail Email: Default = Blank (No voicemail email features) This field is used to set the user or group email address used by the voicemail server for voicemail email operation.
Configuration Settings: Hunt Group 5.8.7 Voice Recording Avaya Branch Gateway R6.2 does not support voice recording. Avaya Branch Gateway Manager 10.
5.8.8 Announcements Announcements are played to callers waiting to be answered. This includes callers being presented to hunt group members, ie. ringing, and callers queued for presentation. · The system supports announcements using Standalone Voice Mail or Embedded Voicemail. · If no voicemail channel is available for an announcement, the announcement is not played. · In conjunction with Standalone Voice Mail, the system allows a number of voicemail channels to be reserved for announcements.
Configuration Settings: Hunt Group Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Announcements On: Default = Off. This setting enables or disables announcements. · Wait before 1st announcement: Default = 10 seconds. Range = 0 to 9999 seconds. This setting sets the time delay from the calls presentation, after which the first announcement should be played to the caller.
5.8.9 SIP Each hunt group can be configured with its own SIP URI information. For calls received on a SIP line where any of the line's SIP URI fields are set to Use Internal Data, if the call is presented to the hunt group that data is taken from these settings. This form is hidden if there are no system multi-site network lines in the configuration or no SIP lines with a URI set to Use Internal Data. Usability · Mergeable: These settings are mergeable.
Configuration Settings: Hunt Group 5.8.10 Hunt Group Operation 5.8.10.1 Hunt Types At its most basic, a hunt groups settings consist of a hunt group name, an extension number, a list of hunt group members and a hunt type selection. It is the last two settings which determine the order in which incoming calls are presented to hunt group members. The available hunt types are; Collective, Sequential, Rotary and Longest Waiting.
5.8.10.2 Call Presentation Summary: Calls are presented to each available hunt group member in turn. If having been presented to all the available members, none answers, the call is redirected to voicemail if available, otherwise it continues to be presented to the next available member. In addition to the summary, options exist to have calls queued or to have calls also presented to agents in an overflow 316 group or groups.
Configuration Settings: Hunt Group 5.8.10.3 Member Availability Summary: Details when a hunt group member is seen as being available to be presented a hunt group call. The Hunt Group settings within Branch Gateway Manager list those users who are members of the hunt group and therefore may receive calls directed to that hunt group. However there are a range of factors that can affect whether a particular hunt group member is available to take hunt group calls at any time.
Hunt Group Member Availability Settings Branch Gateway Manager Forwarding and do not disturb controls for a user are found on the User | Forwarding 277 tabs. Controls The following short code features/button programming actions can be used: and User | DND Enabling and disabling a users hunt group membership is done by ticking or unticking the user entry in the hunt group's extensions list on the Hunt Group | Hunt Group 310 tab.
Configuration Settings: Hunt Group 5.8.10.4 Example Hunt Group The follow are simple examples of how a department might use the facilities of a hunt group. 1. Basic Hunt Group Scenario Actions The Sales department want all sales related calls to be presented first to Jane, then Peter and finally Anne. 1. Create a hunt group named Sales and assign it an extension number. 2. Set the Hunt Type to Sequential. 3. Add Jane, Peter and Ann to the User List in that order. 4.
5. Using a Night Service Time Profile Scenario Actions Outside their normal business hours, the Sales department want their group calls automatically sent to voicemail. This can be done using a time profile and leaving the Night Service Fallback Group setting blank. 1. Create a Time Profile called Sales Hours and in it enter the times during which the Sales department are normally available. 2. Open the Sales hunt group settings and select the Fallback tab. 3. In the Time Profile field select Sales Hours.
Configuration Settings: Hunt Group 5.9 Short Code This form is used to create System Short Codes. System short codes can be dialed by all system users. However the system short code is ignored if the user dialing matches a user or user rights short code. For full details on short code usage and parameter see the section Short Codes 425 . · ! WARNING User dialing of emergency numbers must not be blocked. If short codes are edited, the users ability to dial emergency numbers must be tested and maintained.
5.10 Service Services are used to configure the settings required when a user or device on the LAN needs to connect to a off-switch data service such as the Internet or another network. Services can be used when making data connections via trunk or WAN interfaces. Once a service is created, it can be used as the destination for an IP Route record. One service can also be set as the Default Service. That service will then be used for any data traffic received by the system for which no IP Route is specified.
Configuration Settings: Service 5.10.1 Normal, WAN or Intranet Services 5.10.1.1 Service Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Service Name The name of the service. It is recommended that only alphanumeric characters be used. · Account Name The user name that is used to authenticate the connection. This is provided by the ISP or remote system.
5.10.1.2 Bandwidth These options give the ability to make ISDN calls between sites only when there is data to be sent or sufficient data to warrant an additional call. The calls are made automatically without the users being aware of when calls begin or end. Using ISDN it is possible to establish a data call and be passing data in less that a second. Note: the system will check Minimum Call Time first, then Idle Period, then the Active Idle Period. Usability · Mergeable: These settings are mergeable.
Configuration Settings: Service · Outgoing Incoming Uses both methods but bandwidth is first added using outgoing calls. · Incoming Outgoing Uses both methods but bandwidth is first added using incoming BACP calls. Avaya Branch Gateway Manager 10.
5.10.1.3 IP The fields in this tab are used to configure network addressing for the services you are running. Depending on how your network is configured, the use of Network Address Translation (NAT) 786 may be required. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · IP Address: Default = 0.0.0.
Configuration Settings: Service 5.10.1.4 Autoconnect Fields in this tab enable you to set up automatic connections to the specified Service. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Auto Connect Interval (mins): Default = 0 (disabled). Range = 0 to 99999 minutes. This field defines how often this Service will automatically be called ("polled").
5.10.1.5 Quota Quotas are associated with outgoing calls, they place a time limit on calls to a particular IP Service. This avoids excessive call charges when perhaps something changes on your network and call frequency increases unintentionally. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Quota Time (mins): Default = 240 minutes. Range = 0 to 99999 minutes. Defines the number of minutes used in the quota.
Configuration Settings: Service 5.10.1.6 Fallback These options allow you to set up a fallback for the Service. For example, you may wish to connect to your ISP during working hours and at other times take advantage of varying call charges from an alternative carrier. You could therefore set up one Service to connect during peak times and another to act as fallback during the cheaper period.
5.10.1.7 DialIn Only available for WAN and Intranet Services. This tab is used to define a WAN connection. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. To define a WAN connection 1. Select Add. 2. Enter WAN if the service is being routed via a WAN port on a WAN3 expansion module. Avaya Branch Gateway Manager 10.
Configuration Settings: Service 5.10.2 SSL VPN Service This type of service provides a secure tunnel between the Avaya Branch Gateway system at a customer site and an Avaya VPN Gateway (AVG) installed at a service provider site. This secure tunnel allows service providers to offer remote management services to customers, such as fault management, monitoring, and administration. SSL VPN Services are supported by IP500 V2 and Linux based IP Office systems only, except B5800 Branch Gateway.
5.11 RAS A Remote Access Server (RAS) is a piece of computer hardware which sits on a corporate LAN and into which employees dial on the public switched telephone network to get access to their email and to software and data on the corporate LAN. This form is used to create a RAS service that the system offers Dial In users. A RAS service is needed when configuring modem dial in access, digital (ISDN) dial in access and a WAN link.
Configuration Settings: RAS 5.11.1 PPP PPP (Point-to-Point Protocol) is a Protocol for communication between two computers using a Serial interface, typically a personal computer connected by phone line to a server. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · CHAP Challenge Interval (secs): Default = 0 (disabled). Range = 0 to 99999 seconds. The period between successive CHAP challenges.
5.12 Incoming Call Route Incoming call routes are used to determine the destination of voice and data calls received by the system. On systems where a large number incoming call routes need to be setup for DID numbers, the MSN/DID Configuration 127 tool can be used. Select Tools | MSN Configuration. · Calls received on IP, S0 and QSIG trunks do not use incoming call routes. Routing for these is based on incoming number received as if dialed on-switch.
Configuration Settings: Incoming Call Route Example 3 In the following example, the 677 record is used as the match for 77 as it has more matching digits than the 7 record and no non-matching digits. Line Group Incoming Number Destination 0 677 Support 0 7 Services 0 blank Main Example 4 In this example the digits 777 are received. The 677 record had a non-matching digit, so it is not a match. The 7 record is used as it has one matching digit and no non-matching digits.
5.12.1 Standard Incoming call routes are used to match call received with destinations. Routes can be based on the incoming line group, the type of call, incoming digits or the caller's ICLID. If a range of MSN/DID numbers has been issued, this form can be populated using the MSN Configuration tool (see MSN Configuration 127 ). · Default Blank Call Routes By default the configuration contains two incoming calls routes; one set for Any Voice calls (including analog modem) and one for Any Data calls.
Configuration Settings: Incoming Call Route · X = Single Digit Wildcard Use X's to enter a single digit wild card character. For example 91XXXXXXXX will only match DID numbers of at least 10 digits and starting with 91, -91XXXXXXXX would only match numbers of exactly 10 digits starting with 91. Other wildcard such as N, n and ? cannot be used.
Call Setting Fields For calls routed using this Incoming Call Route, the settings of the following fields are applied to the call regardless of the destination. · Locale: Default = Blank (Use system setting) This option specifies the language prompts, if available, that voicemail should use for the call if it is directed to voicemail. · When the system routes a call to the voicemail server it indicates the locale for which matching prompts should be provided if available.
Configuration Settings: Incoming Call Route 5.12.2 Voice Recording Avaya Branch Gateway R6.2 does not support voice recording. Avaya Branch Gateway Manager 10.
5.12.3 Destinations The system allows multiple time profiles to be associated with an incoming call route. For each time profile, a separate Destination and Fallback Extension can be specified. When multiple records are added, they are resolved from the bottom up. The record used will be the first one, working from the bottom of the list upwards, that is currently 'true', ie. the current day and time or date and time match those specified by the Time Profile.
Configuration Settings: Incoming Call Route 5.13 WAN Port These records are used to configure the operation of system WAN ports and services. Creating a Virtual WAN Port WAN services can be run over a T1 PRI trunk connection. This requires creation of a virtual WAN port. For full details refer to Using a Dedicated T1/PRI ISP Link 788 in Appendix A. 1. Select 2. Click WAN Port. and select PPP. 3. In the Name field, enter either LINEx.y where: · LINE must be in uppercase. · x is the line number.
5.13.1 WAN Port Use this form to configure the leased line connected to the WAN port on the Control Unit. Normally this connection is automatically detected by the control unit. If a WAN Port is not displayed, connect the WAN cable, reboot the Control Unit and receive the configuration. The WAN Port configuration form should now be added. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system.
Configuration Settings: WAN Port 5.13.2 Frame Relay This tab is only available for Frame Relay records. These show SyncFrameRelay as the Mode on the WAN Port tab. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Frame Management Type This must match the management type expected by the network provider.
5.13.3 DLCIs This tab is only available for Frame Relay records. These show SyncFrameRelay as the Mode on the WAN Port 356 tab. The tab lists the DLCIs created for the connection. These can be edited using the Add, Edit and Remove buttons. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Frame Link Type: Default = PPP Data transfer encapsulation method.
Configuration Settings: WAN Port Example: Adjusting the Tc Setting G.729 VoIP creates a 20 byte packet every 20ms. Adding typical WAN PPP headers results in a 33 byte packet every 20ms. For a Committed Information Rate (CIR) of 14Kbps, with the Time Constant (Tc) set to 10ms; we can calculate the Committed Burst size: Bc = CIR x Tc = 14,000 x 0.01 = 140 bits = 17.5 bytes. Using 10ms as the Tc, a full G.729 VoIP packet (33 bytes) cannot be sent without exceeding the Bc.
5.13.4 Advanced The settings on this tab are used for Frame Relay connections. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Address Length The address length used by the frame relay network. The network provider will indicate if lengths other than two bytes are to be used.
Configuration Settings: WAN Port 5.13.5 PPP Fields in this tab enable you to configure Point to Point Protocol (PPP) in relation to this particular service. PPP is a protocol for communication between two computers using a Serial interface. Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Chap Challenge Interval (secs): Default = 0 (disabled). Range = 0 to 99999 seconds. The period between CHAP challenges.
· BACP: Default = Off Enables the negotiation and use of BACP/BCP protocols. These are used to control the addition of B channels to increase bandwidth. · Incoming traffic does not keep link up: Default = On When enabled, the link is not kept up for incoming traffic only. · Multilink/QoS: Default = Off Enables the negotiation and use of Multilink protocol (MPPC) on links into this Service.
Configuration Settings: WAN Port 5.14 Directory This section is used to edit directory records that are stored in the system's configuration. Directory records can also be manually imported from a CSV file 52 . The system can also use Directory Services 166 to automatically import directory records from an LDAP server at regular intervals. A system can also automatically import directory records from another system.
Directory Record Capacity A maximum of 2500 directory records are supported in the system configuration. When using a 1400, 1600, 9500 or 9600 Series phone, system phone 742 users can also edit the configuration directory records. Number of Directory Records Configuration LDAP Import HTTP Import Total Number of Directory Records 2500 5000 5000 5000 Avaya Branch Gateway Manager 10.
Configuration Settings: Directory Avaya Branch Gateway Manager 10.
5.14.1 Directory This tab is used to configure system directory 363 records that are stored in the system configuration. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Index: Range = 001 to 999 or None. Not used for B5800 Branch Gateway. · Name Enter the text, to be used to identify the number. Names should not begin with numbers. · Number Enter the number to be matched with the above name.
Configuration Settings: Directory 5.15 Time Profile Time Profiles are used by different services to change their operation when required. In most areas where time profiles can be used, not setting a time profile is taken as meaning 24-hour operation. · Time profiles consist of recurring weekly patterns of days and times when the time profile is in effect. · Time profiles can include time periods on specified calendar days when the time profile is in effect.
Avaya Branch Gateway Manager 10.
Configuration Settings: Time Profile 5.15.1 Time Profile For a time profile with multiple records, for example a week pattern and some calendar records, the profile is valid when any entry is valid. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Name: Range = Up to 31 characters This name is used to select the time profile from within other tabs.
5.16 Firewall Profile The system can act as a firewall, allowing only specific types of data traffic to start a session across the firewall and controlling in which direction such sessions can be started. · Static NAT 374 The system supports Static NAT address translation by a firewall profiles. If the Firewall Profile contains any Static NAT records, all packets received by the firewall must match one of those static NAT records to not be blocked.
Configuration Settings: Firewall Profile 5.16.1 Standard By default, any protocol not listed in the standard firewall list is dropped unless a custom firewall entry for that protocol. 372 is configured Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Name: Range = Up to 31 characters Enter the name to identify this profile.
5.16.2 Custom The tab lists custom firewall settings added to the firewall profile. The Add, Edit and Remove controls can be used to amend the settings in the list. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Notes For information only. Enter text to remind you of the purpose of the custom firewall record. · Remote IP Address The IP address of the system at the far end of the link.
Configuration Settings: Firewall Profile Example Custom Firewall Records Example: Dropping NetBIOS searches on an ISPs DNS We suggest that the following filter is always added to the firewall facing the Internet to avoid costly but otherwise typically pointless requests from Windows machines making DNS searches on the DNS server at your ISP.
5.16.3 Static NAT The Static NAT table allows the firewall to perform address translation between selected internal and external IP addresses. Up to 64 internal and external IP address pairs can be added to the Static NAT section of a Firewall Profile. This feature is intended for incoming maintenance access using applications such as PC-Anywhere, Branch Gateway Manager and the Standalone Voice Mail Client.
Configuration Settings: Firewall Profile 5.17 IP Route The system acts as the default gateway for its DHCP clients. It can also be specified as the default gateway for devices with static IP addresses on the same subnet as the system. When devices want to send data to IP addresses on different subnets, they will send that data to the system as their default gateway for onward routing. The IP Route table is used by the system to determine where data traffic should be forwarded.
5.17.1 IP Route This tab is used to setup static IP routes from the system. These are in addition to RIP if RIP is enabled on LAN1 and or LAN2. Up to 100 routes are supported. ! WARNING The process of 'on-boarding' (refer to the IP Office SSL VPN Solutions Guide) may automatically add a static route to an SSL VPN service in the system configuration when the on-boarding file is uploaded to the system. Care should be taken not to delete or amend such a route except when advised to by Avaya.
Configuration Settings: IP Route 5.17.2 RIP Routing Information Protocol (RIP) is a protocol which allows routers within a network to exchange routes of which they are aware approximately every 30 seconds. Through this process, each router adds devices and routes in the network to its routing table. Each router to router link is called a 'hop' and routes of up to 15 hops are created in the routing tables.
5.18 Account Code Account codes are commonly used to control cost allocation and out-going call restriction. The account code used on a call is included in the call information output by the system's call log. Incoming calls can also trigger account codes automatically by matching the Caller ID stored with the account code. Once a call has been completed using an account code, the account code information is removed from the user's call information.
Configuration Settings: Account Code Avaya Branch Gateway Manager 10.
5.18.1 Account Code This tab is used to define an individual account code. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Account Code Enter the account code required. It can also include wildcards; ? matches a single digit and * matches any digits. · Caller ID A caller ID can be entered and used to automatically assign an account code to calls made to or received from caller ID.
Configuration Settings: Account Code 5.18.2 Voice Recording Avaya Branch Gateway R6.2 does not support voice recording. Avaya Branch Gateway Manager 10.
5.19 Tunnel Tunneling allows additional security to be applied to IP data traffic. This is useful when sites across an unsecure network such as the public internet. The system supports two methods of tunneling, L2TP and IPSec. Once a tunnel is created, it can be used as the destination for selected IP traffic in the IP Route 376 table. The use of tunnels is not supported by Linux based systems.
Configuration Settings: Tunnel 5.19.1 L2TP Tunnel 5.19.1.1 Tunnel Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Name: Default = Blank. A unique name for the tunnel. Once the tunnel is created, the name can be selected as a destination in the IP Route table. · Local Configuration The account name and password is used to set the PPP authentication parameters.
5.19.1.2 L2TP Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Shared Secret/Confirm Password User setting used for authentication. Must be matched at both ends of the tunnel. This password is separate from the PPP authentication parameters defined on the L2TP|Tunnel 383 tab. · Total Control Retransmission Interval: Default = 0. Range = 0 to 65535. Time delay before retransmission.
Configuration Settings: Tunnel 5.19.1.3 PPP Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · CHAP Challenge Interval (secs): Default = 0 (Disabled). Range = 0 to 99999 seconds. Sets the period between CHAP challenges. Blank or 0 disables repeated challenges. Some software (such as Windows 95 DUN) does not support repeated challenges. · Header Compression: Default = None Select header compression.
5.19.2 IP Security Tunnel 5.19.2.1 Main Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Name: Default = Blank. A unique name for the tunnel. Once the tunnel is created, the name can be selected as a destination for traffic in the IP Route 376 table.
Configuration Settings: Tunnel 5.19.2.2 IKE Policies Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Shared Secret/Confirm Password The password used for authentication. This must be matched at both ends of the tunnel. · Exchange Type: Default = ID Prot Aggressive provides faster security setup but does not hide the ID's of the communicating devices.
5.19.2.3 IPSec Policies Usability · Mergeable: These settings are not mergeable. Changes to these settings will require a reboot of the system. Configuration Settings · Protocol: Default = ESP ESP (Encapsulated Security Payload) or AH (Authentication Header, no encryption). · Encryption: Default = DES Select the encryption method used by the tunnel. The options are: DES CBC, 3DES or Any. · Authentication: Default = HMAC MD5 The method of password authentication. Options are: HMAC MD5, HMAC SHA or Any.
Configuration Settings: Tunnel 5.20 User Rights User Rights act as templates for selected user settings. The settings of a user rights template are applied to all users associated with that template. The use of a template can also be controlled by a time profile 369 to set when the template is used for a particular user. For most setting in a user rights template, the adjacent drop down list is used to indicate whether the setting is part of the template or not.
Copy User Rights Settings over a User's Settings This process replaces a user's current settings with those that are part of the selected user rights. It does not associate the user with the user rights. 1. Select User Rights or User. 2. In the group pane, right-click and select Copy user rights values to users. 3. Select the user rights to be applied. 4. Click OK. Default User Rights For defaulted systems, the following user rights are created as a part of the default configuration.
Configuration Settings: User Rights 5.20.1 User This tab is used to set and lock various user settings. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Name The name for the user rights . This must be set in order to allow the user rights to be selected within the User Rights drop down list on the User | User 271 tab of individual users.
5.20.2 Short Codes This tab is used to set and lock the user's short code set. The tab operates in the same way as the User | Short Codes tab. User and User Rights short codes are only applied to numbers dialed by that user. For example they are not applied to calls forwarded via the user. · ! WARNING User dialing of emergency numbers must not be blocked. If short codes are edited, the users ability to dial emergency numbers must be tested and maintained.
Configuration Settings: User Rights 5.20.3 Button Programming This tab is used to set and lock the user's programmable button set. When locked, the user cannot use Admin or Admin1 buttons on their phone to override any button set by their user rights. Buttons not set through the user rights can be set through the user's own settings 292 . When Apply user rights value is selected, the tab operates in the same manner as the User | Button Programming 292 tab.
5.20.4 Telephony This tab allows various user telephony settings to be set and locked. These match settings found on the User | Telephony 281 tab. These settings are divided in to a number of sub-tabs: · Call Settings 394 · Supervisor Settings · Multi-line Options · Call Log 395 396 396 5.20.4.1 Call Settings For details of the ringing tones, see Ring Tones Telephony 159 tab. 739 .
Configuration Settings: User Rights 5.20.4.2 Supervisor Settings These settings relate to user features normally only adjusted by the user's supervisor. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Can Intrude: Default = Off Check this option if the User can interrupt other user's calls.
5.20.4.3 Multi-line Options Multi-line options are applied to a user's phone when the user is using an Avaya phones which supports appearance buttons (call appearance, line appearance, bridged and call coverage). See Appearance Button Operation 653 . Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Individual Coverage Time (secs): Default = 10 seconds, Range 1 to 99999 seconds.
Configuration Settings: User Rights 5.20.5 Phone Manager Not supported on Avaya Branch Gateway systems. Avaya Branch Gateway Manager 10.
5.20.6 User Rights Membership The tabs display the users associated with the user rights and allows these to be changed. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Members of this User Rights This tab indicates those users associated with the user rights.
Configuration Settings: User Rights 5.20.7 Voicemail The tabs display the users associated with the user rights and allows these to be changed. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Voicemail On Default = On When on, the mailbox is used by the system to answer the user's unanswered calls or calls when the user's extension returns busy.
· When Park & Page is selected for a DTFM breakout, the following drop-down boxes appear: · Paging Number – displays a list of hunt groups and users (extensions). Select a hunt group or extension to configure this option. · Retries – the range is 0 to 5. The default setting is 0. · Retry Timeout – provided in the format M:SS (minute:seconds). The range can be set in 15-second increments. The minimum setting is 15 seconds and the maximum setting is 5 minutes.
Configuration Settings: User Rights 5.21 Auto Attendant The IP Office Aura Edition control unit can support Embedded Voicemail. This uses the System SD memory card installed in the control unit to provide message storage. It is enabled by selecting Embedded Voicemail as the Voicemail Type on the System | Voicemail 155 tab. · This tab and its settings are hidden unless the system has been configured to use Embedded Voicemail on the System | Voicemail 155 tab.
5.21.1 Auto Attendant This tab is used to define the name of the auto attendant service and the time profiles that should control which auto attendant greetings are played. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Name: Range = Up to 12 characters This field sets the name for the auto-attendant service.
Configuration Settings: Auto Attendant 5.21.2 Actions This tab defines the actions available to callers dependant on which DTMF key they press. To change an action, select the appropriate row and click Edit. When the key is configured as required click OK. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · Key The standard telephone dial pad keys, 0 to 9 plus * and #.
· Destination Sets the destination for the action: · Destination can be a user, a hunt group or a short code. · If the destination field is left blank, callers can dial the user extension number that they require. Note however that no prompt is provided for this option so it should be included in the auto attendant Menu Options greeting. Avaya Branch Gateway Manager 10.
Configuration Settings: Auto Attendant 5.22 ARS When a dialed number matches a short code that specifies that the number should be dialled, there are two methods by which the routing of the outgoing call can be controlled. · Routing Calls Directly to a Line Every line and channel belongs has an Outgoing Group ID setting. Several lines and channels can have belong to the same Outgoing Group ID.
Example ARS Operation The simplest example for ARS operation are the settings applied to a defaulted system. These vary between U-Law systems and A-Law systems. A-Law Systems This set of defaults is applied to A-Law systems, typically supplied to locales other than North America. The defaults allow any dialing that does not match an internal number to be routed off-switch as follows: 1. System Short Code - ?/Dial/.
Configuration Settings: ARS 5.22.1 ARS Each ARS form contains short codes which are used to match the result of the short code that triggered use of the ARS form, ie. the Telephone Number resulting from the short code is used rather than the original number dialed by the user. Usability · Mergeable: These settings are mergeable. Changes to these settings do not require a reboot of the system. Configuration Settings · ARS Route ID This value is automatically assigned and cannot be edited.
· Only short codes using the following features are supported within ARS: Dial, Dial Emergency, Dial Speech, Dial 56K, Dial64K, Dial3K1, DialVideo, DialV110, DialV120 and Busy. · Multiple short codes with the same Code field can be entered so long as they have differing Telephone Number and or Line Group ID settings. In this case when a match occurs the system will use the first match that points to a route which is available. · Alternate Route Priority: Default = 3. Range = 1 (low) to 5 (high).
Configuration Settings: ARS 5.22.2 Cause Codes and ARS ARS routing to digital trunks can be affected by signalling from the trunk. The response to cause codes received from the line is as follows: · Reroute with ARS The following cause codes cause ARS to no longer target the line group (unless it is specified by an alternate ARS route). Code Cause Code 1 Unallocated Number. 2 No route to specific transit network/(5ESS) Calling party off hold. 3 No route to destination.
5.22.3 ARS Operation The diagram below illustrates the default ARS routing applied to systems defaulted to the United States system locale. In summary: · Any dialing prefixed with 9 will match the default system short code 9N. · That short code routes calls to the default ARS form 50:Main. · The short codes in that ARS form route all calls to an available line that has its Outgoing Group ID set to 0.
Configuration Settings: ARS 5.22.3.1 ARS Short Codes The short codes in the default ARS form have the following roles: Code Feature Telephone Number Line Description Group ID 11 Dial 911 Emergenc y 0 911 Dial 911 Emergenc y 0 0N; Dial 3K1 0N 0 Matches international numbers. 1N; Dial 3K1 1N 0 Matches national numbers. XN; Dial 3K1 N 0 Matches 7 digit local numbers. XXXXXXXXX Dial 3K1 XN; N 0 Matches 10 digit local numbers. These two short codes are used to route emergency calls.
5.22.3.2 Simple Alternate Line Example Using the default ARS settings 410 , despite having several short codes in the ARS form, all outgoing calls are actually routed the same way using the same trunks. However, by having separate short codes for different call types present, it is easy to change the routing of each call type if required. For this example, the customer has separate sets of lines for local calls and for national/international calls.
Configuration Settings: ARS 5.22.3.3 Simple Call Barring All ARS short codes use one of the Dial short code features. The exception is the Barred short code feature. This can be selected for ARS short codes that match dialing that is not allowed. In the example below, any user dialing an international number will be routed to the Barred short code. This prevents the dialing of external numbers prefixed with 0.
5.22.3.4 User Priority Escalation User priority can be used to alter call routing when the required route is not available. In this example, international calls are initially targeted to seize a line in outgoing line group 1. However an alternate route has been defined which will be used if no line in line group 1 is available. The fallback ARS form allows international calls to seize a line from line group 0.
Configuration Settings: ARS 5.22.3.5 Time Base Routing Time profiles can be used to switch call routing from one ARS form to another. In the example below, a time profile has been define that sets the hours for normal operation. Outside the times set in the time profile, the other ARS form is used. This other ARS form only allows local and emergency calls. Avaya Branch Gateway Manager 10.
5.22.3.6 Account Code Restriction The short codes within an ARS form can be individually set to require an account code before allowing any call that matches it to proceed. In the example below, the short code for international calls has been set to require the user to enter an account code. A valid account code must be dialed to continue with the call. · If a user should always enter an account code to make any external call, the user option Force Account Code should be used.
Configuration Settings: ARS 5.22.3.7 Tiered ARS Forms It is possible for an ARS short code in one form to have another ARS form as its destination. Dialing that matches the short code is then subject to further matching against the short codes in the other ARS form. In the example below, the user wants different routing applied to international calls based on the country code dialed.
5.22.3.8 Planning ARS Using the methods shown in the previous examples, it is possible to achieve ARS that meets most requirements. However the key to a good ARS implementation is planning. A number of questions need to be assessed and answered to match the system's call routing to the customer's dialing. · What What numbers will be dialed and what needs to be output by the system. What are the different call tariffs and the dialing codes. · Where Where should calls be routed.
Configuration Settings: ARS 5.23 PLDS License B5800 Branch Gateway systems use the Avaya Product Licensing and Delivery System (PLDS) to manage license files. A PLDS License option appears in the left navigation pane when Branch Gateway Manager has loaded the configuration from an Avaya Branch Gateway. When you select PLDS License in the left navigation pane, the PLDS License screen appears. This screen is read-only.
The following are the license types used by an B5800 Branch Gateway system: · Avaya Branch Gateway System Software This is the mandatory license for B5800 Branch Gateway operation. It must be present and it must match the specific level of B5800 Branch Gateway software being used. This license does not enable any trunks or extensions. · Maximum Native Stations This type of license is required for all configured users with analog, digital, H.
Configuration Settings: PLDS License 5.24 E911 System This section is only for U-Law systems with their system Locale set to United States. When the central office receives and emergency call, it routes the call to a dedicated emergency network. The call is then distributed to the correct emergency operator using either the automatic line identification information (ALI) received with the call or the registered billing address of the line on which the call was made.
5.24.1 E911 Adjunct The settings on this tab relate to the use of an E911 adjunct if installed. Dial Emergency calls routed to the E911 adjunct include the extension ID of the extension on the system. This is used to lookup information stored in a database on the E911 Adjunct and then send that information to the central office. The extension ID of each extension is shown on the Extension | Extn 258 tab.
Configuration Settings: E911 System 5.24.2 Zones Zones are used for Dial Emergency calls on US systems when a trunk to the E911 adjunct cannot be seized or the E911 adjunct is indicating an alarm through its alarm station being off-hook (busy). Zones allow extensions in the same location to be grouped and to have the external trunks registered to the same location associated with them.
Chapter 6. Short Codes Avaya Branch Gateway Manager 10.
Short Codes: 6. Short Codes The system uses short codes to match the number dialed to an action. The number dialed or part of the number dialed can be used as parameter for the feature. · ! WARNING User dialing of emergency numbers must not be blocked. If short codes are edited, the users ability to dial emergency numbers must be tested and maintained. The short method for describing short codes in this manual, for example 9N/Dial/.
6.1 Short Code Fields and Characters Each short code, regardless of its type, has the following fields: · Short Code: Default =Blank. Range = Up to 31 characters. The digits which if matched trigger use of the short code. Characters can also be used to create short codes which cannot be dialed from a phone but can be dialed from application speed dials. However some characters have special meaning, see the table below. · Telephone Number: Default = Blank. Range = Up to 32 characters.
Short Codes: Short Code Fields and Characters Telephone Number Field Characters · A - Allow Outgoing CLI Allow the calling party number sent with the call to be used. This character may be required by service providers in some locales. · C - Use Called Number Field Place any following digits in the outgoing call's Called number field rather than the Keypad field. · D - Wait for Connect Wait for a connect message before sending any following digits as DTMF.
· W - Withhold Outgoing CLI Withhold the sending of calling ID number. Operation is service provider dependent. · Y - Wait for Call Progress Message Wait for a Call Progress or Call Proceeding message before sending any following digits as DTMF. For example, the Y character would be necessary at a site where they have signed up with their telephone service provider to withhold international dialing until a DTMF pin/account number is entered that initiates the call progress/ proceeding message.
Short Codes: Short Code Fields and Characters 6.2 User Dialing Summary: Looks at how the system looks for possible short code matches to user dialing. The following system settings influence user dialing. · Dial Delay Count: Default = 0 (US/Japan), 4 (ROW) This value sets the number of digits dialed before the system looks for a short code match. · Dial Delay Time: Default = 4 seconds (US/Japan), 1 second (ROW) This value sets the maximum allowed interval between the dialing of each digit.
6.3 Application Dialing Numbers speed dialed by system applications such as SoftConsole are treated differently. Since the digits are received en bloc as a single group, they can override some short code matches. The same applies to short codes used within system configuration settings such as Incoming Call Route destinations.
Short Codes: Application Dialing 6.4 Secondary Dial Tone Some locales prefer to provide users with secondary dial tone once they have started dialing external calls. This dial tone is heard by the user until they have completed dialing and a trunk is seized at which point call progress tones are provided by the trunk, or camp on/busy tone is provided by the system if the required trunk cannot be seized.
6.5 ? Short Codes The ? character can be used in short codes in the following ways: · Default Short Code Matching ? short codes are used in short code matching in the following way. If no user or system short code match is found, the system will then look for a ? short code match. It will look first for a user ? short code and then, if not found, a system ? short code. · Example: On systems outside North America, the system short code ?/Dial/./0 is added as a default short code.
Short Codes: ? Short Codes 6.6 Short Code Matching Examples The following examples are not meant as practical examples. However they are simple to implement and test on real system without conflicting with its normal operation. They illustrate the interaction between different short codes in resolving which short code is an exact match. They assume that extension numbers are in the 200 to 299 range.
Scenario 4 Short Code 1 = 60;/Dial Extn/203 Short Code 2 = 601/Dial Extn/210 Dial Delay Count = 3. Dial Delay Time = 4 seconds. Test Dialing Effect 1 8 Insufficient digits to trigger matching. The system waits for additional digits or for Dial Delay Time to expire. When Dial Delay Time expires, no possible match is found so incompatible is returned. 2 6 Insufficient digits to trigger matching. The system waits for additional digits or for the interdigit Dial Delay Time to expire.
Short Codes: Short Code Matching Examples Scenario 6 Short Code 1 = 601/Dial Extn/203 Short Code 2 = 60N/Dial Extn/210 Short Code 3 = 60X/Dial Extn/207 Dial Delay Count = 0. Dial Delay Time = 4 seconds. Test Dialing Effect 1 6 No exact match but there are potential matches so the system waits for additional dialing. If the Dial Delay Time expires, no exact match has occurred so incompatible is returned. 2 60 Potential match to all short codes. System waits for additional dialing.
6.7 Default System Short Code List Most control units are available in A-Law and U-Law models. Typically U-Law models are supplied to North American locales, A-Law models are supplied to the rest of the world. In addition to the using different default companding for digital lines and phone, A-Law and U-Law models support different default short codes. The following table lists the default system short codes present in a system's configuration.
Short Codes: Default System Short Code List Short Code Telephone Number Feature A-Law *47 Blank Conference Add *48 Blank Voicemail Ringback On *49 Blank Voicemail Ringback Off 505 *50 Blank Forward Huntgroup On 474 *51 Blank Forward Huntgroup Off 474 *52 Blank Cancel or Deny *53*N# N Call Pickup Members *55 Blank Stamp Log *57*N# N Forward On Busy Number *70 Blank Call Waiting Suspend *70*N# N Dial Physical Extn by Number *71*N# N Dial Physical Extn by Id *9000* "
6.8 Short Code Features This following section details the available system short code features.
Short Codes: Short Code Features 6.8.1 Acquire Call See Call Steal 447 . 6.8.2 AOC Previous Call Not used for Avaya Branch Gateway. Details · Telephone Number: · Default Short Code: · Programmable Button Control: 6.8.3 AOC Reset Total Not used for Avaya Branch Gateway. Details · Telephone Number: · Default Short Code: · Programmable Button Control: 6.8.4 AOC Total Not used for Avaya Branch Gateway. Details · Telephone Number: · Default Short Code: · Programmable Button Control: 6.8.
6.8.6 Break Out Not supported by Avaya Branch Gateway. Details · Telephone Number: The IP Address or Name of the system, using * characters in place of . characters. · Default Short Code: · Programmable Button Control: BkOut 565 Example On a system, to break out via a system called RemoteSwitch with the IP Address 192.168.42.3, either of the following short codes could be used.
Short Codes: Short Code Features 6.8.9 Call Intrude This feature allows you to intrude on the existing connected call of the specified target user. All call parties are put into a conference and can talk to and hear each other. A Call Intrude attempt to a user who is idle becomes a Priority Call 488 .
6.8.10 Call Listen This feature allows you to monitor another user's call without being heard. Monitoring can be accompanied by a tone heard by all parties. Use of the tone is controlled by the Beep on Listen 163 setting on the System | Telephony | Tones & Music 163 tab. The default for this setting is on. If enabled, this is the only indication of monitoring given to the monitored user. There is no phone display indication of monitoring.
Short Codes: Short Code Features 6.8.11 Call Park Parks the user's current call into the specified park slot number. The call can then be retrieved by other extensions (refer to the appropriate telephone user guide). While parked the caller hears music on hold if available. The 'Unpark Call 502 ' feature can be used to retrieve calls from specific park slots. Park Timeout 159 (System | Telephony | Telephony 159 ) controls how long a call will remain parked.
Example This short code is a default within the system configuration. N represents the specific extension. For example, if a user dials *32*201#, they will pick up the call coming into extension 201. · Short Code: *32*N# · Telephone Number: N · Feature: CallPickupAny Avaya Branch Gateway Manager 10.
Short Codes: Short Code Features 6.8.14 Call Pickup Group Pick up a call ringing any hunt group of which the user is a member. The user can use this feature even if their membership of the group is currently set as disabled. Details · Telephone Number: · Default Short Code: *31 · Programmable Button Control: · See also: Call Pickup Any Pickup User 446 .
6.8.16 Call Pickup Members This feature can be used to pick up a ringing or queuing call at an extension that is a member of the Hunt Group specified. The call picked up does not have to be a hunt group call. The function includes group members even if their membership of the group is currently disabled. Details · Telephone Number: Group number or "Group name". · Default Short Code: *53*N# · Programmable Button Control: · See also: Call Pickup Any Pickup User 446 .
Short Codes: Short Code Features 6.8.18 Call Queue Queue the current call to the destination phone, even when the destination phone is busy. This is the same as a transfer except it allows you to transfer to a busy phone. Details · Telephone Number: Target extension number. · Default Short Code: *33*N# · Programmable Button Control: Queue 575 Example Below is an example of the short code setup. N represents the extension the caller wishes to queue for.
6.8.20 Call Waiting On Enables call waiting on the user's extension. When on, if the user receives a second calls when already on a call, they hear a call waiting tone in the speech path. Call waiting settings are ignored for users with multiple call appearance buttons. In this case the appearance buttons are used to indicate additional calls. Call waiting is automatically applied for users with 'internal twinned' phones.
Short Codes: Short Code Features 6.8.23 Cancel All Forwarding This feature cancels all forms of forwarding on the user's extension including "Follow Me" and "Do Not Disturb". Details · Telephone Number: · Default Short Code: *00 · Programmable Button Control: FwdOf 577 · See also: Forward On Busy On 476 , Forward On Busy Off 476 , Forward On No Answer On 477 , Forward On No Answer Off 477 , Forward Unconditional On 478 , Forward Unconditional Off 478 , Do Not Disturb On 467 , Do Not Disturb Off 467 .
6.8.26 Change Login Code Allows a user to change their log in code. Details · Telephone Number: The user's current and new log in codes separated by a *, see the examples below. · Default Short Code: · Programmable Button Control: Example The user has a Login Code of 1234 and wants to change it to 5678. To use the short code below below, the user must dial *60*1234*5678#. · Short Code: *60*N# · Telephone Number: N · Feature: Change Login Code.
Short Codes: Short Code Features 6.8.27 Clear After Call Work Not supported by B5800 Branch Gateway. 6.8.28 Clear Call This feature can be used to end the current call. Details · Telephone Number: · Default Short Code: *52 · Programmable Button Control: Clear 579 Example Below is a sample of the short code setup. This example could be used in a situation where you are doing a supervised transfer and the party to be transferred to does not want to take the call.
6.8.30 Clear Hunt Group Night Service This feature changes the specified hunt group from Night Service 319 mode to In Service mode. · Setting and clearing hunt group night service can be done using either manual controls or using a system time profile. The use of both methods to control the night service status of a particular hunt group is not supported. · This function is currently not supported between systems in a multi-site network.
Short Codes: Short Code Features 6.8.32 Clear Quota This feature refreshes the time quota for all services or a specific service. Details · Telephone Number: "Service name" or "" (all services). · Default Short Code: · Programmable Button Control: Quota 582 6.8.33 Coaching Intrusion This feature allows the you to intrude on another user's call and to talk to them without being heard by the other call parties to which they can still talk. For example: User A is on a call with user B.
6.8.35 Conference Meet Me Conference meet-me refers to features that allow a user or caller to join a specific conference by using the conference's ID number (either pre-set in the control or entered at the time of joining the conference). · ! Note Conference Meet Me features can create conferences that include only one or two parties. These are still conferences that are using resources from the host system's conference capacity.
Short Codes: Short Code Features 6.8.36 CW Pick up the waiting call. This feature provides same functionality as pressing the Recall or Hold key on the phone. Unlike the Clear CW feature, this feature does not disconnect you from the existing call when the second call is picked up. Details · Telephone Number: · Default Short Code: · Programmable Button Control: Avaya Branch Gateway Manager 10.
6.8.37 Dial This short code feature allows users to dial the number specified to an outside line. Details · Telephone Number: Telephone number. · Default Short Code: Various depending on locale and system type. · Programmable Button Control: · See also: Dial Direct 458 , Dial Dial Emergency 588 459 , Dial Extn 459 , Dial Inclusion 460 , Dial Paging 460 .
Short Codes: Short Code Features 6.8.38 Dial 3K1 Sets the ISDN bearer capabilities to 3.1Khz audio call. Details · Telephone Number: Telephone number. · Default Short Code: · Programmable Button Control: D3K1 588 6.8.39 Dial 56K Sets the ISDN bearer capabilities to 56Kbps data call. Details · Telephone Number: Telephone number. · Default Short Code: · Programmable Button Control: D56K 588 6.8.40 Dial 64K Sets the ISDN bearer capabilities to 64Kbps data call.
6.8.42 Dial Direct Automatic intercom 743 functions allow you to call an extension and have the call automatically answered on speaker phone after 3 beeps. The extension called must support a handsfree speaker. If the extension does not have a handsfree microphone then the user must use the handset if they want to talk. If the extension is not free when called, the call is presented as a normal call on a call appearance button if available.
Short Codes: Short Code Features 6.8.44 Dial Emergency Dials the number specified regardless of any call barring applicable to the user. On all systems, regardless of locale; system and or ARS short codes using the Dial Emergency 459 feature should be created for any required emergency service numbers. Those short codes should be usable by all users from all extensions. Those short codes should route the calls to suitable lines.
6.8.46 Dial Fax This feature is used to route fax calls via Fax Relay 727 . Details · Telephone Number: Fax destination number. · Default Short Code: · Programmable Button Control: Example In this example, the line group ID matches the URI configured on a SIP line that has been configured for Fax Relay. · Short Code: 6N · Telephone Number: N"@192.16.42.5" · Line Group ID: 17 · Feature: Dial Fax 6.8.47 Dial Inclusion This feature allows you to intrude on another user's call to talk to them.
Short Codes: Short Code Features Paging Limit: A maximum of 64 parties in a paging group is recommended. When paging, always use only one codec (the preferred). It is the system administrator's responsibility to ensure all the phones in the paging group support the codec. Avaya Branch Gateway Manager 10.
6.8.49 Dial Physical Extension By Number Dial a specified extension number regardless of the current user logged in at that extension and any forwarding, follow me or do not disturb settings applied by the current extension user. Note that the extension number used is the Base Extension number set against the extension configuration settings. Details · Telephone Number: Base Extension number.
Short Codes: Short Code Features 6.8.51 Dial Speech This feature allows a short code to be created to force the outgoing call to use the Speech bearer capability. Details · Telephone Number: Telephone number. · Default Short Code: · Programmable Button Control: DSpch 592 6.8.52 Dial V110 Sets the ISDN bearer capabilities to V110. The call is presented to local exchange as a "Data Call". Details · Telephone Number: Telephone number.
6.8.55 Disable ARS Form This feature can be used to put an ARS form out of service. It can be used with ARS forms for which an Out of Service Route has been configured in Branch Gateway Manager. The short code feature Enable ARS Form can be used to return an ARS form to in service. Details · Telephone Number: ARS form number. · Default Short Code: · Programmable Button Control: · See also: Enable ARS Form 467 6.8.
Short Codes: Short Code Features 6.8.58 Disable Internal Forward Busy or No Answer This feature turns off the forwarding of internal calls for the user. It applies to Forward on Busy and Forward on No Answer.
6.8.60 Do Not Disturb Exception Add This feature adds a number to the user's "Do Not Disturb Exception Numbers List". This can be an internal extension number or external ICLID. Calls from that number, except hunt group calls, will ignore the user's Do Not Disturb setting. For further details see Do Not Disturb (DND). 745 Details · Telephone Number: Telephone number or ICLID. Up to 31 characters. For ICLID numbers any prefix added by the system must also be included.
Short Codes: Short Code Features 6.8.62 Do Not Disturb On This feature puts the user into 'Do Not Disturb' mode. When on, all calls, except those from numbers in the user's exception list hear busy tones or are redirected to voicemail if available. For further details see Do Not Disturb (DND) 745 .
6.8.65 Enable Internal Forwards This feature turns on the forwarding of internal calls for the user. It applies to Forward Unconditional, Forward on Busy and Forward on No Answer.
Short Codes: Short Code Features 6.8.68 Extn Login Extn Login allows a user who has been configured with a Login Code 283 (User | Telephony | Supervisor Settings 283 ) to take over ownership of any extension. That user's extension number becomes the extension number of the extension while they are logged. When used, the user will be prompted to enter their extension number and then their log in code. Login codes of up to 15 digits are supported with Extn Login buttons.
· Feature: ExtnLogout Avaya Branch Gateway Manager 10.
Short Codes: Short Code Features 6.8.70 Flash Hook This feature sends a hook flash signal to the currently connected line if it is an analog line. Details · Telephone Number: Optional The telephone number field can be used to set the transfer destination number for a Centrex Transfer 765 . In this case the use of the short code Forced Account Code and Forced Authorization Code are not supported and the Line Group Id must match the outgoing line to the Centrex service provider.
6.8.72 Follow Me Here Causes calls to the extension number specified to be redirected to the extension initiating the 'Follow Me Here'. If the redirected call receives a busy tone or is not answered, then the call behaves as though the User's extension had failed to answer. For further details see Follow Me. 747 · The use of Follow Me features is not supported between systems in a multi-site network. Details · Telephone Number: Extension to redirect to the dialing extension.
Short Codes: Short Code Features 6.8.73 Follow Me Here Cancel Cancels any Follow Me set on the specified extension. This action can only be performed at the extension to which the Follow Me Here is targetted. For further details see Follow Me. 747 · The use of Follow Me features is not supported between systems in a multi-site network. Details · Telephone Number: Extension being redirected to the dialing extension.
6.8.75 Forward Hunt Group Calls On Forward the user's hunt group calls (internal and external) to their forward number when the user has Forward Unconditional active. For further details see Forward Unconditional. 749 This option is only applied for calls to Sequential and Rotary type hunt groups. Calls from other types of hunt group types are not presented to the user when they have Forward Unconditional active. Note also that hunt group calls cannot be forwarded to another hunt group.
Short Codes: Short Code Features 6.8.77 Forward Number Sets the number to which the user's calls are redirected. This can be an internal or external number. The number is still subject to the user's call barring settings. For further details see Forward Unconditional. 749 This feature does not activate forwarding; it only sets the number for the forwarding destination.
6.8.79 Forward On Busy On This feature enables forwarding when the user's extension is busy. It uses the Forward Number destination or, if set, the Forward on Busy Number destination. If the user has call appearance buttons programmed, the system will not treat them as busy until all the call appearance buttons are in use. Forward Internal (User | Forwarding) can also be used to control whether internal calls are forwarded.
Short Codes: Short Code Features 6.8.81 Forward On No Answer On This feature enables forwarding when the user's extension is not answered within the period defined by their No Answer Time. It uses the Forward Number destination or, if set, the Forward on Busy Number destination. Forward Internal (User | Forwarding) can also be used to control whether internal calls are forwarded.
6.8.83 Forward Unconditional On This feature enables forwarding of all calls, except group calls, to the Forward Number set for the user's extension. To also forward hunt group calls, Forward Hunt Group Calls On must also be used. For further details see Forward Unconditional 749 . Forward Internal (User | Forwarding) can also be used to control whether internal calls are forwarded.
Short Codes: Short Code Features 6.8.85 Group Listen Off Disables the group listen function for the user’s extension. See Group Listen On 479 . Details · Telephone Number: · Default Short Code: · Programmable Button Control: GroupListenOn 610 Example Below is a sample short code using the Group Listen Off feature. · Short Code: *27 · Feature: GroupListenOff 6.8.
6.8.87 Headset Toggle Toggles between the use of a headset and the telephone handset. Details · Telephone Number: · Default Short Code: · Programmable Button Control: HdSet 612 Example Below is a sample short code using the Headset Toggle feature. This short code can be used to toggle the feature on/off. If an Avaya supported headset is connected to your telephone, this short code can be used to toggle between using the headset and the telephone handset. · Short Code: *55 · Feature: HeadsetToggle 6.8.
Short Codes: Short Code Features 6.8.89 Hold CW This uses the Q.931 Hold facility, and "holds" the incoming call at the ISDN exchange, freeing up the ISDN B channel. The Hold CW feature "holds" the current call to an exchange slot and answers the call waiting. The current call is always automatically placed into slot 0 if it has not been placed in a specified slot. Only available if supported by the ISDN exchange. Details · Telephone Number: Exchange slot number or blank (slot 0).
6.8.91 Hunt Group Disable This feature disables the user's membership of the specified hunt group. They will no longer receive call to that hunt group until their membership is enabled again. To use this feature, you must already belong to the hunt group. See also Hunt Group Enable 482 . Details · Telephone Number: Group number. · Default Short Code: · Programmable Button Control: · See also: Hunt Group Enable HGDis 615 482 .
Short Codes: Short Code Features 6.8.93 Last Number Redial This feature allows an extension to redial the last number they dialed. Details · Telephone Number: · Default Short Code: · Programmable Button Control: 6.8.94 MCID Activate This feature should only be used in agreement with the ISDN service provider and the appropriate local legal authorities.
6.8.96 Off Hook Station Enables or disables whether the user's extension acts as a fully handsfree unit. For more details see Off Hook Station 281 (User | Telephony | Call Settings 281 ). Details · Telephone Number: "Y" for on or "N" for off.
Short Codes: Short Code Features 6.8.97 Outgoing Call Bar Off Allows a user to switch off their outgoing call bar status. The short code user must enter their log in code, if set, in order to be successful. · If you add a short code using this feature to a system it is recommended that you also assign a login code to the No User 743 user to prevent the short code being used to change the status of that user. Details · Telephone Number: · System phone 742 The user's log in code.
6.8.99 Private Call Not supported. Avaya Branch Gateway Manager 10.
Short Codes: Short Code Features 6.8.100 Private Call Off Short codes using this feature turn off private call status for the user if set. The short code features Private Call Private Call On 487 can be used to turn private call on. 486 and When on, any subsequent calls cannot be intruded on 731 until the user's private call status is switched off. The exception is Whisper Page 651 which can be used to talk to a user on a private call.
6.8.102 Priority Call This feature allows the user to call another user even if they are set to 'do not disturb'. Priority calls to a user without DND will follow forwarding and follow me settings but will not go to voicemail. Details · Telephone Number: Extension number. · Default Short Code: · Programmable Button Control: PCall · See also: DialPhysicalExtensionByNumber 620 462 , DialPhysicalNumberByID 462 .
Short Codes: Short Code Features Analog Modem Control On systems with an analog trunk card in the control unit, the first analog trunk can be set to answer V.32 modem calls. This is done by either selecting the Modem Enabled option on the analog line settings 198 or using the default short code *9000* to toggle this service on or off. This short code uses the RelayOn feature with the Telephone Number set to "MAINTENANCE".
6.8.106 Relay Pulse This feature closes the specified switch in the system's external output (EXT O/P) port for 5 seconds and then opens the switch. This feature is not supported by Linux based systems. Details · Telephone Number: Switch number (1 or 2). · Default Short Code: *41 (Switch 1), *44 (Switch 2) · Programmable Button Control: · See also: Relay On 488 , Relay Off Relay 623 489 . Example This short code is a default within the system configuration.
Short Codes: Short Code Features 6.8.108 Retrieve Call Retrieves a call previously held to a specific ISDN exchange slot. Details · Telephone Number: Exchange hold slot number. · Default Short Code: *25*N# (A-Law only) · Programmable Button Control: · See also: Hold Call Retriv 624 480 . Example Below is sample short code using the Retrieve Call feature. N represents the exchange slot number from which the call has been placed on hold.
6.8.111 Set Absent Text This feature can be used to select the user's current absence text. This text is then displayed to internal callers who have suitable display phones or applications. It doesn't changes the users status. The absence text message is limited to 128 characters. Note however that the amount displayed will depend on the caller's device or application. The text is displayed to callers even if the user has forwarded their calls or is using follow me.
Short Codes: Short Code Features 6.8.112 Set Account Code This short code feature is used to allow system users to enter a valid account code prior to making a phone call. Once this short code is set up, any existing account code 378 in the system configuration can be used in conjunction with it. This short code feature is essential for allowing analog phone users to enter account codes as they cannot enter account code through the phone during a call or after dial a number.
6.8.114 Set Hunt Group Night Service This feature puts the specified hunt group into Night Service 319 mode. · Setting and clearing hunt group night service can be done using either manual controls or using a system time profile. The use of both methods to control the night service status of a particular hunt group is not supported. · This function is currently not supported between systems in a multi-site network.
Short Codes: Short Code Features 6.8.115 Set Hunt Group Out Of Service This feature manually puts the specified hunt group into Out of Service to control hunt group night service, the action may vary: 319 mode. If a time profile has also been defined · Pre-Release 4.0: Set Hunt Group Out of Service cannot be used to override a hunt group put into night service by a time profile. · Release 4.
6.8.116 Set Inside Call Seq This feature allows the user to select the ringing used on their analog extension for internal calls. The number entered corresponds to the ring pattern required. This is 0 for Default Ring, 1 for RingNormal, 2 for RingType1, etc. For more information on selectable ringing patterns, see Ring Tones 739 . Use of this short code function is applicable to analog phone users only. The distinctive ringing pattern 739 used for other phones is set by the phone type.
Short Codes: Short Code Features 6.8.117 Set Mobile Twinning Number This short code feature can be used to set a mobile twinning number. The destination can be any external number the user is able to dial normally. It should include any prefix if necessary. Details · Telephone Number: Twinning destination. · Default Short Code: · Programmable Button Control: · See also: Set Mobile Twinning On 497 , Set Mobile Twinning Off 497 , Mobile Twinned Call Pickup 483 . 6.8.
6.8.120 Set No Answer Time This short code feature allows the user to change their No Answer Time 281 (User | Telephony | Call Settings 281 ). Details · Telephone Number: Time in seconds. · Default Short Code: · Programmable Button Control: · See also: Set Wrap Up Time NATim 634 499 . Example This short code allows a user to change the length of time they have to answer the phone before it goes to divert or voicemail. N represents the number of seconds.
Short Codes: Short Code Features 6.8.122 Set Ringback Seq This feature allows the user to select the ringing used on their analog extension for ringback calls. The number entered corresponds to the ring pattern required. This is 0 for Default Ring, 1 for RingNormal, 2 for RingType1, etc. For more information on selectable ringing patterns, see Ring Tones 739 . Use of this short code function is applicable to analog phone users only.
6.8.124 Shutdown Embedded Voicemail Allows the Embedded Voicemail service provided by an Avaya memory card in a control unit to be shut down. To restart the service, a Startup Embedded Voicemail short code should be used. The short code has the following effects: 1. Immediately disconnect all current users within Embedded Voicemail. This is not a polite shutdown. 2. Mark the Embedded Voicemail as inactive so that it will not receive any new calls.
Short Codes: Short Code Features Details · Telephone Number: Exchange slot number or blank (slot 0). · Default Short Code: *28*N# (A-Law only) · Programmable Button Control: · See also: Resume Call SusCW 638 490 . Example Sample short code using the Suspend CW feature. · Short Code: *28*N# · Feature: Suspend CW Avaya Branch Gateway Manager 10.
6.8.129 Start After Call Work Not supported by B5800 Branch Gateway. 6.8.130 Toggle Calls This feature cycles through each call that the user has on hold on the system. This feature is useful when a user with a single-line telephone has several calls on hold and needs to respond to each one in turn. Details · Telephone Number: · Default Short Code: *29 · Programmable Button Control: Toggl 641 Example Below is sample short code using the Toggle Calls feature.
Short Codes: Short Code Features 6.8.132 Voicemail Collect This feature connects to the voicemail system. Normally the telephone number field is used to indicate the name of the mailbox to be accessed, for example "?Extn201" or "#Extn201". · ? indicates 'collect messages'. · # indicates 'leave a message'. It also instructs the voicemail server to give a brief period of ringing before connecting the caller.
6.8.133 Voicemail Node Similar to Voicemail Collect but used for calls being directed to a Standalone Voice Mail Short Codes start point. Useful if you have set up a short code start point with Standalone Voice Mail and want to give direct internal access to it. Details · Telephone Number: Standalone Voice Mail Short Code start point name without quotation marks. · Default Short Code: · Programmable Button Control: · See also: Voicemail Collect 503 .
Short Codes: Short Code Features 6.8.136 Voicemail Ringback On This feature enables voicemail ringback to the user's extension. Voicemail ringback is used to call the user when they have new voicemail messages. The ringback takes place each time the extension is used. This feature is useful for users who do not have voicemail light/button indicators on their telephone.
Chapter 7. Button Programming Avaya Branch Gateway Manager 10.
Button Programming: 7. Button Programming This section covers the system actions that can be assigned to programmable buttons on Avaya phones. This assignment can be done through the system configuration using Branch Gateway Manager and for some functions using the phone itself. · Appearance Functions The functions Call Appearance, Bridged Appearance, Coverage and Line Appearance are collectively known as "appearance functions".
7.1 Programming Buttons 7.1.1 Programming Buttons with Manager Using Branch Gateway Manager, if only button programming changes are required, the configuration changes can be merged back to the system without requiring a reboot. · Appearance Functions The functions Call Appearance, Bridged Appearance, Coverage and Line Appearance are collectively known as "appearance functions". For full details of their operation and usage refer to the Appearance Button Operation 653 section. 1.
Button Programming: Programming Buttons 7.1.2 Interactive Button Menus For display phones where the a button has been configured without a specific number, the menu for number entry. The menu includes a Dir option for selecting a number from the directories held by the system. Functions that use the interactive menu are: Feature Automatic Intercom 564 Acquire Call/Call Steal Call Forwarding All Call Intrude 558 567 568 Call Park To Other Extension 572 Directory lists... Feature Directory lists...
7.2 Phone Details The following types of phone are supported by B5800 Branch Gateway systems. Native Extensions B5800 Branch Gateway supports the following phones as local/native extensions. The system requires a Maximum Native Stations license for the required number of extensions. These phones connect to DS ports fitted to the system. · 1400 Series: 1403 513 , 1408 513 , · 2400 Series: 2402D 517 , 2410D · 5400 Series: 5402D 526 , 5410 1416 518 , 527 , 514 . 2420 5420 519 . 528 .
Button Programming: Phone Details 7.2.1 1100 Series They are currently only supported when using the system as the file server for phone firmware and other files. Expansion modules providing an additional 18 programmable buttons per module are supported. Up to 3 such modules are supported per phone. 1120E SIP Telephone Avaya Branch Gateway Manager 10.
7.2.2 1200 Series They are currently only supported when using the system as the file server for phone firmware and other files. Expansion modules providing an additional 12 programmable buttons per module are supported. Up to 7 such modules are supported per phone. 1220 SIP Telephone 1230 SIP Telephone Avaya Branch Gateway Manager 10.
Button Programming: Phone Details 7.2.3 1400 Series 7.2.3.1 1403 Branch Gateway Manager is able to pass user button information to a DESI application on the same PC. This allows printing of labels using the label text set within the system configuration. Currently only 1400 and 1600 phonesphones are supported by DESI. 01 02 03 As these phones only have 3 programmable buttons, those buttons should only be used for call appearance buttons. 7.2.3.
7.2.3.3 1416 For 1416 phones, additional buttons can be added using DBM32 modules. Branch Gateway Manager is able to pass user button information to a DESI application on the same PC. This allows printing of labels using the label text set within the system configuration. Currently only 1400 and 1600 phonesphones are supported by DESI. 01 02 03 04 05 06 07 08 The appearance buttons on these phones must be programmed as a continuous block starting from button 1.
Button Programming: Phone Details 7.2.4 1600 Series 7.2.4.1 1603 Branch Gateway Manager is able to pass user button information to a DESI application on the same PC. This allows printing of labels using the label text set within the system configuration. Currently only 1400 and 1600 phonesphones are supported by DESI. 01 02 03 As these phones only have 3 programmable buttons, those buttons should only be used for call appearance buttons. 7.2.4.
7.2.4.3 1616 For 1616 phones, additional buttons can be added using a BM32 module. The use of a BM32 requires the phone to be powered by a 1600 Series power supply unit rather than PoE. Branch Gateway Manager is able to pass user button information to a DESI application on the same PC. This allows printing of labels using the label text set within the system configuration. Currently only 1400 and 1600 phonesphones are supported by DESI.
Button Programming: Phone Details 7.2.5 2400 Series 7.2.5.1 2402D These phones only have two physical programmable buttons with no display text labels. Display icons are used for status indication with a * used for current selected appearance button indication. For appearance functions, these only display active, alerting, held here and current selected button. They do not display in use elsewhere and on hold elsewhere.
7.2.5.2 2410 These phones have 6 physical display keys that provide 12 programmable buttons arranged in two pages. The keys are used to switch the display between different button display pages as shown below. Avaya Branch Gateway Manager 10.
Button Programming: Phone Details 7.2.5.3 2420 These phones have 8 physical display keys and 24 programmable buttons. The display between different button display pages as shown below. and keys are used to switch the These phones support two modes of button display, selected by the user through the phone (press Option | Display Mode | Call Center Mode). Avaya Branch Gateway Manager 10.
Normal Mode Call Center Mode In this mode, several of the programmable button position are repeated and replace the normal functions on the base on the phone display. Avaya Branch Gateway Manager 10.
Button Programming: Phone Details 7.2.6 3600 Series 7.2.6.1 3616, 3620, 3626 These phones support 6 programmable buttons. These are accessed by pressing LINE and then 1 to 6 when the phone is off hook. The FCN options are not re-programmable. system Button 3616/3626 Button 1 LINE + 1 2 LINE + 2 3 LINE + 3 4 LINE + 4 5 LINE + 5 6 LINE + 6 The following should be noted with these phones: · 'In use' is indicated by the button number being shown.
7.2.6.2 3641, 3645 These phones support up to 12 programmable buttons (the system option within the phone menu must be selected, otherwise only 6 programmable buttons are provided). These are accessed by pressing LINE or FCN and then 1 to 6 when the phone is off hook.
Button Programming: Phone Details 7.2.7 3700 Series The 3700 Series phones are a range of DECT handsets. · The 3701 and 3711 are supported with the Avaya IP DECT system. They can also be used with the Avaya DECT R4 system but only as GAP compatible handsets. · The 3720 and 3725 are supported with the Avaya DECT R4 system. · The 3740 and 3749 are supported with the Avaya DECT R4 system. 7.2.8 4600 Series (New Style) 7.2.8.1 4602, 4602SW These phones only have two programmable buttons.
7.2.8.2 4610SW This phone has 6 physical display keys that provide 24 programmable buttons arranged in 4 pages. The are used to switch the display between different button display pages as shown below. Avaya Branch Gateway Manager 10.
Button Programming: Phone Details 7.2.8.3 4620, 4620SW, 4621, 4625 These phones have 12 physical display keys that provide 24 programmable buttons arranged in two pages. The keys are used to switch the display between different button display pages as shown below. and By default appearance actions use a full screen width display line and can be accessed by the display key on either side. The numbering of buttons and the number of display pages available is adjusted accordingly up 4 pages.
7.2.9 5400 Series 7.2.9.1 5402D These phones only have two physical programmable buttons with no display text labels. For systems running system 3.0 or higher (excluding 3.0DT) these buttons should only be used for call appearance buttons. Display icons are used for status indication with a * used for current selected appearance button indication. For appearance functions, these only display active, alerting, held here and current selected button. They do not display in use elsewhere and on hold elsewhere.
Button Programming: Phone Details 7.2.9.2 5410 These phones have 6 physical display keys that provide 12 programmable buttons arranged in two pages. The keys are used to switch the display between different button display pages as shown below. and · 5410: system 3.0+. Avaya Branch Gateway Manager 10.
7.2.9.3 5420 These phones have 8 physical display keys and 24 programmable buttons. The display between different button display pages as shown below. and keys are used to switch the These phones support two modes of button display, selected by the user through the phone (press Option | Display Mode | Call Center Mode). · 5420: system 3.0+. Avaya Branch Gateway Manager 10.
Button Programming: Phone Details Normal Mode Call Center Mode In this mode, several of the programmable button position are repeated and replace the normal functions on the base on the phone display. Avaya Branch Gateway Manager 10.
7.2.10 5600 Series 7.2.10.1 5601 This phone has two programmable buttons, each with a single red lamp. For systems running system 3.0 or higher (excluding 3.0DT), these buttons should only be used for call appearance buttons. 1 Avaya Branch Gateway Manager 10.
Button Programming: Phone Details 7.2.10.2 5602, 5602SW These phones only have two programmable buttons. Display icons are used for status indication with a * used for current selected appearance button indication. These only display active, alerting, held here and current selected button. They do not display in use elsewhere and on hold elsewhere. 1 2 Avaya Branch Gateway Manager 10.
7.2.10.3 5610SW This phone has 6 physical display keys that provide 24 programmable buttons arranged in 4 pages. The are used to switch the display between different button display pages as shown below. Avaya Branch Gateway Manager 10.
Button Programming: Phone Details 7.2.10.4 5620, 5620SW, 5621 These phones have 12 physical display keys that provide 24 programmable buttons arranged in two pages. The keys are used to switch the display between different button display pages as shown below. and By default appearance actions use a full screen width display line and can be accessed by the display key on either side. The numbering of buttons and the number of display pages available is adjusted accordingly up 4 pages.
7.2.11 9500 Series 7.2.11.1 9504 The phones provide 4 physical buttons with red and green LEDs. These can be used for up to 12 programmable features. 7.2.11.2 9508 The phones provide 8 physical buttons with red and green LEDs. These can be used for up to 24 programmable features. The phones support the addition of up to 3 BM12 button modules supporting an additional 24 programmable features (using 12 buttons) per module.
Button Programming: Phone Details 7.2.12 9600 Series 7.2.12.1 9608 · The voice activated dialing and USB features are not supported. · The use of the IP Office control unit as the HTTP file server for these phones is not supported. A third-party HTTP file server must be used. · These phones are supported as local extensions when they use H.323 firmware. They are supported as survivable extensions when they use SIP 6.0 firmware. The phones supports 24 programmable buttons.
7.2.12.2 9611 · The voice activated dialing and USB features are not supported. · The use of the IP Office control unit as the HTTP file server for these phones is not supported. A third-party HTTP file server must be used. · These phones are supported as local extensions when they use H.323 firmware. They are supported as survivable extensions when they use SIP 6.0 firmware. The phones supports 24 programmable buttons. These can be used for call appearance functions and other system features.
Button Programming: Phone Details 7.2.12.3 9620C, 9620L · The voice activated dialing and USB features are not supported. · These phones are supported as local extensions when they use H.323 firmware. They are supported as survivable extensions when they use SIP 2.6 firmware. The 9620 variants supported are the 9620L and the 9620C. The phones support 12 programmable buttons but with no physical button keys.
7.2.12.4 9621 · The voice activated dialing and USB features are not supported. · The use of the IP Office control unit as the HTTP file server for these phones is not supported. A third-party HTTP file server must be used. · These phones are supported as local extensions when they use H.323 firmware. They are supported as survivable extensions when they use SIP 6.0 firmware. The phones support 24 programmable buttons which are displayed as touchscreen options.
Button Programming: Phone Details 7.2.12.5 9630G · The voice activated dialing and USB features are not supported. · These phones are supported as local extensions when they use H.323 firmware. They are supported as survivable extensions when they use SIP 2.6 firmware. The phones support 24 programmable buttons. These can be accessed by scrolling the display and selecting the required button function using one of the 6 button to the right of the display.
7.2.12.6 9640, 9640G · The voice activated dialing and USB features are not supported. · These phones are supported as local extensions when they use H.323 firmware. They are supported as survivable extensions when they use SIP 2.6 firmware. The phones support 24 programmable buttons. These can be accessed by scrolling the display and selecting the required button function using one of the 6 button to the right of the display. This phone can be used with up to 3 x SBM24 button module.
Button Programming: Phone Details 7.2.12.7 9641 · The voice activated dialing and USB features are not supported. · The use of the IP Office control unit as the HTTP file server for these phones is not supported. A third-party HTTP file server must be used. · These phones are supported as local extensions when they use H.323 firmware. They are supported as survivable extensions when they use SIP 6.0 firmware. The phones support 24 programmable buttons which are displayed as touchscreen options.
7.2.12.8 9650, 9650C · The voice activated dialing and USB features are not supported. · These phones are supported as local extensions when they use H.323 firmware. They are supported as survivable extensions when they use SIP 2.6 firmware. The phones support 24 programmable buttons. These can be accessed by scrolling the display and selecting the required button function using one of the 3 button to the right of the display.
Button Programming: Phone Details 7.2.13 B100 Series This is a series of high quality conference phones intended to support calls with multiple users speaking and listening via the same conference phone. All the models support local call recording onto a SD card of up to 2GB capacity (not SDHC). Additional microphones can be added to each model. · B149 Conference Phone Conference phone for personal office use and small and medium sized conference rooms.
7.2.14 D100 The D100 SIP Wireless Terminal is a cordless phone system that is adapted for IP Office. The D100 solution delivers the productivity-boosting benefits of IP and wireless communications across multiple offices in a convenient, lightweight handset. It provides businesses with a highly functional wireless solution with the ability to scale to support large numbers of users. A single base station can support up to eight (8) handsets, each of which can support up to five (5) simultaneous calls.
Button Programming: Phone Details 7.2.15 T-Series M-Series and T-Series phones can access a range of functions by pressing the phone's Feature key and dialing the required feature code. Function Feature Code Description Speed Dial 0 636 This feature code can be used to dial a stored number. · If Feature 0 is followed by a 3-digit index number in the range 000 to 999, the system directory 366 record with the matching index is dialed.
Function Feature Code Description Any user can unpark the call by entering that park slot number. Not supported on phones without a display except the T7000 which supports a single park slot XXX0. Not supported on phones on DECT systems. Call Unpark #74 call. 642 Not supported on phones without a display.
Button Programming: Phone Details Administration Functions The following feature codes can be used to edit phone settings. Some functions may request a security code after the feature code is entered. When this occurs, enter your phone login code and press #. Function Feature Code Description Button Inspect *0 After selecting this function, pressing any programmable button will display the function currently assigned to that button.
Button Programming The process below can be used to assign functions to programmable buttons on T-Series and M-Series phones. Existing button can be overwritten except buttons set to appearance functions. 1. Press Feature *3. If a security code is requested, enter your phone login code and press #. 2. Use one of the processes below. Press * to switch between processes (or More if displayed). On T7000 phones, only the first process is supported. a. Select Button and then Function i.
Button Programming: Phone Details 7.2.15.1 Audio Conferencing Unit Avaya M-Series and T-Series phones are supported by Release 7.0 and higher on an IP500 V2. They can be connected to digital station ports provided by an IP500 TCM8 base card (IP500 V2 only) or on a DS16A/DS30A external expansion module (IP500 V2 only). These phones use virtual call appearances 562 . set by programming Call Appearance buttons on buttons 1 to 3 of the user's Button Programming setting.
7.3 Actions The following sections provide details for each of the button actions supported by system. Note that this does not include buttons on phones on a system running in Partner Edition mode. For each the following details are listed: · Action Indicates the selection path to the action from within the list of actions displayed in Branch Gateway Manager. · Action Data Indicates the type of data required by the action. For some actions no data is required while for others action data may be optional.
Button Programming: Actions Action Action Data Short Label Long Label None. Stats – None. Count – Mark – Wait – None. Sfunc – None. Spres Suppress Digits None. AutCB Auto Callback User number or name. Iauto Auto Intercom Any number or blank for entry when pressed. CFrwd Call Forward All Park slot ID (alphanumeric) or blank for menu of slots in use. CPark Call Park Call Park To Other Extension 572 User number. RPark Call Park to Other Call Pickup None.
Action Call List 568 Call Listen 569 Call Pickup Any 573 Call Pickup Group 574 Call Pickup Members Call Queue Call Steal 574 575 575 Action Data Category Short Label Long Label None. Call LIST – User number. Call Listn Listen None. Call PickA Pickup Any None. Call PickG Pickup Group Group number or name. Call PickM Pickup Members User number. Call Queue Queue User number or blank for last call transferred. Call Steal – Call Waiting Off 576 None.
Button Programming: Actions Action Action Data Category Short Label Long Label Do Not Disturb Off 598 None. Do Not Disturb DNDOf – Do Not Disturb On 598 None. Do Not Disturb DNDOn Do Not Disturb None. Extension Login Login None. Extension Logof Logout None. Miscellaneous Flash Flash Hook User number. Follow Me Here+ Follow Me Here User number or blank for entry when pressed. Follow Me Here- Follow Me Here- User name or user number or blank for entry when pressed.
Action Action Data Category Short Label Long Label Set Hunt Group Out Of Service 632 Group number. Set HGOS+ HG Out of Service Set Inside Call Seq Value 0 to 10. Set ICSeq – Group number. Set SetNSG HG NS Group 633 Set Night Service Group 633 Set No Answer Time 634 Time in seconds (range 6 to 99999). Set NATim No Answer Time Set Outside Call Seq 635 Value 0 to 10. Set OCSeq – Set SetOOSG HG OS Group Value 0 to 10. Set RBSeq – Time in seconds (range 0 to 99999).
Button Programming: Actions 7.3.1 Abbreviated Dial This function allows quick dialing of a stored number. Details · Action: Emulation | Abbreviated Dial. · Action Data: · Full Number The number is dialled. · Partial Number The partial number is dialled and the user can then complete dialing the full number. · Default Label: AD or Abbreviate Dial. · Toggles: . · Status Indication: · User Admin: 627 . .
7.3.3 Abbreviated Dial Program Not supported. Provided for CTI emulation only. Allows a user to program abbreviated dialing numbers against other programmable buttons. This function cannot be used to overwrite call appearance buttons. Details · Action: Emulation | Abbreviated Dial Program. · Action Data: None. · Default Label: Prog. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
Button Programming: Actions Avaya Branch Gateway Manager 10.
7.3.6 ACD Agent Statistics Not supported. Provided for CTI emulation only. Details · Action: Emulation | ACD Agent Statistics. · Action Data: None. · Default Label: Stats. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
Button Programming: Actions · Analog: · 1400 Series: · 1600 Series: [1] · 2400 Series: · 3700 Series: [1] [1] · 4600 Series: · 5400 Series: · 5600 Series: [1] · 9500 Series: · 9600 Series: [1] 1. Not 1403, 1603, 4601, 4602, 5601 and 5602. 7.3.10 AD Special Function Mark Not supported. Provided for CTI emulation only. Allows a user to enter a mark character when programming abbreviated dial. Details · Action: Emulation | AD Special Function Mark. · Action Data: None. · Default Label: Mark.
7.3.12 AD Suppress Suppresses the display of dialed digits on the telephone display. Dialed digits are replaced with an s character. Details · Action: Emulation | AD Suppress. · Action Data: None. · Default Label: Spres or Suppress Digits. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also · Analog: · 2400 Series: [1] [1] · 1400 Series: · 3700 Series: · 1600 Series: [1] dependant on the system software level.
Button Programming: Actions 7.3.13 After Call Work This action is not supported for Avaya Branch Gateway. Avaya Branch Gateway Manager 10.
7.3.14 Appearance Creates a call appearance button 654 . This can be used to answer and make calls. Users with multiple call appearance buttons can handle multiple calls. Call appearance functions, assigned to buttons that do not have status lamps or icons, are automatically disabled until the user logs in at a phone with suitable buttons. Appearance buttons can be set with a ring delay if required or to not ring. This does not affect the visual alerting displayed next to the button.
Button Programming: Actions 7.3.15 Automatic Callback Sets a ringback on the extension being called. When the target extension ends its current call, the ringback user is rung (for their set No Answer Time) and if they answer, a new call is made to the target extension. Ringback can also be cleared using the Cancel Ring Back When Free 577 function. Details · Action: Emulation | Automatic Callback. · Action Data: None. · Default Label: AutCB or Auto Callback. · Toggles: .
7.3.16 Automatic Intercom Automatic intercom 743 functions allow you to call an extension and have the call automatically answered on speaker phone after 3 beeps. The extension called must support a handsfree speaker. If the extension does not have a handsfree microphone then the user must use the handset if they want to talk. If the extension is not free when called, the call is presented as a normal call on a call appearance button if available.
Button Programming: Actions 7.3.17 Break Out Not supported by Avaya Branch Gateway. On phones with a multi-line display, if the target system is not specified in the button settings, a menu of the available systems in the network is displayed from which a selection can be made. Avaya Branch Gateway Manager 10.
7.3.18 Bridged Appearance Creates an appearance button that follows the state of another user's call appearance button. The bridged appearance can be used to make and answer calls on behalf of the call appearance user. The bridged appearance button user must also have at least one call appearance button programmed. Bridged appearance functions, assigned to buttons that do not have status lamps or icons, are automatically disabled until the user logs in at a phone with suitable buttons.
Button Programming: Actions 7.3.19 Busy Not used. 7.3.20 Busy On Held When on, busy on held returns busy to new calls while the user has an existing call on hold. While this feature can be used by users with appearance keys, it is not recommended as this overrides the basic call handling intent of appearance keys. Details · Action: Advanced | Busy | Busy on Held. · Action Data: 1 for on, 0 for off. · Default Label: BusyH. · Toggles: . · Status Indication: · User Admin: 627 . .
7.3.22 Call Intrude This feature allows you to intrude on the existing connected call of the specified target user. All call parties are put into a conference and can talk to and hear each other. A Call Intrude attempt to a user who is idle becomes a Priority Call 488 .
Button Programming: Actions 7.3.24 Call Listen This feature allows you to monitor another user's call without being heard. Monitoring can be accompanied by a tone heard by all parties. Use of the tone is controlled by the Beep on Listen 163 setting on the System | Telephony | Tones & Music 163 tab. The default for this setting is on. If enabled, this is the only indication of monitoring given to the monitored user. There is no phone display indication of monitoring.
7.3.25 Call Log Not used for Avaya Branch Gateway. Details · Action: Advanced | Call | Call Log. · Action Data: None. · Default Label: Call Log. · Toggles: . · Status Indication: · User Admin: . . 627 · Phone Support This function is only supported on M-Series and T-Series phones with a display. Not supported on phones on a DECT systems. 510 Avaya Branch Gateway Manager 10.
Button Programming: Actions 7.3.26 Call Park Allows the user to park and unpark calls. The button can be used in two ways, either associated with a specified park slot number or unspecified. · When associated with a specific park slot number, the button will park and unpark calls from that park slot and indicate when a call is parked in that park slot. Similarly the Park buttons within application (for example SoftConsole) can be used to park, retrieve and indicate parked calls.
7.3.27 Call Park To Other Extension Allows the user to park their current call against another user's extension. The parked call indication on that extension is then activated according to the telephone type. If the target extension has a Call Park button with no specific park slot number, the parked call will be indicated by that button and can be unparked from the list of parked calls shown when that button is pressed.
Button Programming: Actions 7.3.29 Call Pickup Any Pick up the first available ringing call on the system. Details · Action: Advanced | Call | Call Pickup Any. · Action Data: None. · Default Label: PickA or Pickup Any. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also · Analog: · 2400 Series: [1] [1] · 1400 Series: · 3700 Series: · 1600 Series: [1] dependant on the system software level.
7.3.30 Call Pickup Group Pick up a call ringing any hunt group of which the user is a member. The user can use this feature even if their membership of the group is currently set as disabled. Details · Action: Advanced | Call | Call Pickup Group. · Action Data: None. · Default Label: PickG or Pickup Group. · Toggles: . · Status Indication: · User Admin: 627 . .
Button Programming: Actions 7.3.32 Call Queue Transfer the call to the target extension if free or busy. If busy, the call is queued to wait for the phone to become free. This is similar to transfer except it allows you to transfer calls to a busy phone. Details · Action: Advanced | Call | Call Queue. · Action Data: User number. · Default Label: Queue. · Toggles: . · Status Indication: · User Admin: 627 . .
7.3.34 Call Waiting Off Switches call waiting off for the user. This button function is obsolete. The Call Waiting On off and indicates current status. 576 button function toggles on/ Details · Action: Advanced | Call | Call Waiting Off. · Action Data: None. · Default Label: CWOff. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
Button Programming: Actions 1. Not 1403, 1603, 4601, 4602, 5601 and 5602. 7.3.37 Cancel All Forwarding Cancels forward unconditional, forward on busy, forward on no answer, follow me and do not disturb if any of those are active on the user's extension. Details · Action: Advanced | Call | Cancel All Forwarding. · Action Data: None. · Default Label: FwdOf or Call Forward Off. · Toggles: . · Status Indication: · User Admin: 627 . .
· Analog: · 1400 Series: · 1600 Series: [1] · 2400 Series: · 3700 Series: [1] [1] · 4600 Series: · 5400 Series: · 5600 Series: [1] · 9500 Series: · 9600 Series: [1] 1. Not 1403, 1603, 4601, 4602, 5601 and 5602. Avaya Branch Gateway Manager 10.
Button Programming: Actions 7.3.40 Channel Monitor For Avaya use only. Details · Action: Advanced | Call | Channel Monitor. · Action Data: Channel. · Default Label: ChMon. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
1. Not 1403, 1603, 4601, 4602, 5601 and 5602. Avaya Branch Gateway Manager 10.
Button Programming: Actions 7.3.43 Clear Hunt Group Night Service Changes the specified hunt group from Night Service 319 mode to 'In Service' mode. This button function is obsolete. The Set Hunt Group Night Service 631 function can be used to toggle a group in/out of service and provides lamp status indication. · Setting and clearing hunt group night service can be done using either manual controls or using a system time profile.
7.3.44 Clear Hunt Group Out Of Service Changes the specified hunt groups status from Out of Service 319 mode to 'In Service' mode. This button function is obsolete. The Set Hunt Group Out Of Service 632 function can be used to toggle a group in/out of service and provides lamp status indication. · This function is currently not supported between systems in a multi-site network. It can only be used by a user currently logged onto the same system as hosting the hunt group.
Button Programming: Actions · ! WARNING The use of features to listen to a call without the other call parties being aware of that monitoring may be subject to local laws and regulations. Before enabling the feature you must ensure that you have complied with all applicable local laws and regulations. Failure to do so may result in severe penalties. The system support a range of other call intrusion methods 731 in addition to this feature. Details · Action: Advanced | Call | Coaching Intrusion.
7.3.47 Conference This function is not supported for Avaya Branch Gateway. 7.3.48 Conference Add Conference add controls can be used to place the user, their current call and any calls they have on hold into a conference. When used to start a new conference, the system automatically assigns a conference ID to the call. This is termed ad-hoc (impromptu) conferencing. If the call on hold is an existing conference, the user and any current call are added to that conference.
Button Programming: Actions 7.3.49 Conference Meet Me Conference meet-me refers to features that allow a user or caller to join a specific conference by using the conference's ID number (either pre-set in the control or entered at the time of joining the conference). · ! Note Conference Meet Me features can create conferences that include only one or two parties. These are still conferences that are using resources from the host system's conference capacity.
Details · Action: Advanced | Call | Conference Meet Me. · Action Data: Conference number. This can be an alphanumeric value up to 15 characters. · User Personal Conference Number For Release 6.2+, each user's own extension number is treated as their own personal conference number. Only that user is able to start a conference using that number as the conference ID. Any one else attempting to start a conference with that number will find themselves in a conference but on hold until the owner also joins.
Button Programming: Actions 7.3.50 Consult Not supported. Provided for CTI emulation only. Details · Action: Emulation | Consult. · Action Data: None. · Default Label: Cnslt. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
7.3.52 Dial This action is used to dial the number contained in the Telephone Number field. A partial number can be enter for the user to complete. On buttons with a text label area, Dial followed by the number is shown. Details · Action: Dial. · Action Data: Telephone number or partial telephone number. · Default Label: Dial. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
Button Programming: Actions 1. Not 1403, 1603, 4601, 4602, 5601 and 5602. 7.3.55 Dial 64K The call is presented to local exchange as a "Data Call". Details · Action: Advanced | Dial | Dial 64K. · Action Data: Telephone number. · Default Label: D64K or Dial 64K. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
· User Admin: 627 . · Phone Support Note that support for particular phone models is also dependant on the system software level. · Analog: · 1400 Series: · 1600 Series: [1] · 2400 Series: · 3700 Series: [1] [1] · 4600 Series: · 5400 Series: · 5600 Series: [1] · 9500 Series: · 9600 Series: [1] 1. Not 1403, 1603, 4601, 4602, 5601 and 5602. 7.3.58 Dial Emergency Dials the number specified regardless of any outgoing call barring applicable to the user.
Button Programming: Actions 1. Not 1403, 1603, 4601, 4602, 5601 and 5602. 7.3.60 Dial Intercom Automatic intercom 743 functions allow you to call an extension and have the call automatically answered on speaker phone after 3 beeps. The extension called must support a handsfree speaker. If the extension does not have a handsfree microphone then the user must use the handset if they want to talk.
7.3.62 Dial Physical Extn by Number Call the specified extension using its Base Extension number setting. This is regardless of the current user logged in at that extension and any forwarding, follow me or do not disturb settings applied by the extension user. This function requires the extension to be assigned a default extension number in the system configuration. If the extension does not have a default extension number, Dial Physical Extn by Id 592 should be used.
Button Programming: Actions [1] · 1400 Series: · 1600 Series: · 3700 Series: · 5400 Series: · 5600 Series: [1] · 9600 Series: [1] 1. Not 1403, 1603, 4601, 4602, 5601 and 5602. 7.3.65 Dial V110 The call is presented to local exchange as a "Data Call". Details · Action: Advanced | Dial | Dial V110. · Action Data: Telephone number. · Default Label: DV110 or Dial V110. · Toggles: . · Status Indication: · User Admin: 627 . .
7.3.67 Display Msg Allows the sending of text messages to digital phones on the local system. Details · Action: Advanced | Dial | Display Msg. · Action Data: The telephone number takes the format N";T" where: · N is the target extension. · T is the text message. Note that the "; before the text and the " after the text are required. · Default Label: Displ. · Toggles: . · Status Indication: · User Admin: 627 . .
Button Programming: Actions · Analog: · 1400 Series: · 1600 Series: [1] · 2400 Series: · 3700 Series: [1] [1] · 4600 Series: · 5400 Series: · 5600 Series: [1] · 9500 Series: · 9600 Series: [1] 1. Not 1403, 1603, 4601, 4602, 5601 and 5602. Avaya Branch Gateway Manager 10.
7.3.70 Directory A Dir button provides access to various directories and allows telephone number selection by dialed name matching. The directories available for searching depend on the phone type, see User Directory Access 704 . Once they user has selected a directory, dialing on the dial pad letter keys is used to display matching names, with controls for scrolling through the matching names and for calling the currently displayed name.
Button Programming: Actions 7.3.71 Do Not Disturb Exception Add Adds a number to the user's "Do Not Disturb Exception List". This can be the number of an internal user or a number to match the CLI of a particular external caller.Calls from that number, except hunt group calls, will ignore the user's Do Not Disturb setting. For further details see Do Not Disturb (DND). 745 Details · Action: Advanced | Do Not Disturb | Do Not Disturb Exception Add. · Action Data: Telephone number or CLI.
7.3.73 Do Not Disturb Off Cancels the user's 'do not disturb' mode if set. This button function is obsolete as the do not disturb on toggles on/off and indicates the button status. 598 function · Action: Advanced | Do Not Disturb | Do Not Disturb Off. · Action Data: None. · Default Label: DNDOf. · Toggles: . · Status Indication: · User Admin: 627 . .
Button Programming: Actions 7.3.75 Drop This action is supported on phones which do not have a permanent Drop button. · For a currently connected call, pressing Drop disconnects the call. When drop is used to end a call, silence is returned to the user rather than dial tone. This is intended operation, reflecting that Drop is mainly intended for use by call center headset users.
7.3.76 Extn Login Extn Login allows a user who has been configured with a Login Code 283 (User | Telephony | Supervisor Settings 283 ) to take over ownership of any extension. That user's extension number becomes the extension number of the extension while they are logged. When used, the user will be prompted to enter their extension number and then their log in code. Login codes of up to 15 digits are supported with Extn Login buttons.
Button Programming: Actions 7.3.77 Extn Logout Logs out a user from the phone. The phone will return to its normal default user, if an extension number is set against the physical extension settings in the configuration. Otherwise it takes the setting of the NoUser user. This action is obsolete as Extn Login 600 can be used to log out an existing logged in user.
7.3.79 Follow Me Here Causes calls to the extension number specified, to be redirected to this user's extension. User's with a log in code will be prompted to enter that code when using this function. · The use of Follow Me features is not supported between systems in a multi-site network. Details · Action: Advanced | Follow Me | Follow Me Here. · Action Data: User name or user number.
Button Programming: Actions 7.3.81 Follow Me To Leaving the extension blank prompts the user to enter the extension to which their calls should be redirected. User's with a log in code will be prompted to enter that code when using this function. · The use of Follow Me features is not supported between systems in a multi-site network. Details · Action: Advanced | Follow Me | Follow Me To. · Action Data: User name or user number or blank for number entry when pressed 509 .
· Default Label: FwdH+ or Fwd HG Calls. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level. · Analog: · 1400 Series: · 1600 Series: [1] · 2400 Series: · 3700 Series: [1] [1] · 4600 Series: · 5400 Series: · 5600 Series: [1] · 9500 Series: · 9600 Series: [1] 1. Not 1403, 1603, 4601, 4602, 5601 and 5602. 7.3.
Button Programming: Actions 7.3.85 Forward On Busy Number Sets the number to which calls are forwarded when using 'Forward on Busy' and/or 'Forward on No Answer'. Forwarding to an external number is blocked if Inhibit Off-Switch Transfers is selected within the system configuration. Details · Action: Advanced | Forward | Forward on Busy Number. · Action Data: Telephone number.
7.3.87 Forward On Busy On Enables forwarding when the user's extension is busy. For users with call appearance buttons, they will only return busy when all call appearance buttons are in use. Uses the Forward Number as its destination unless a separate Forward on Busy Number is set. Forward Internal (User | Forwarding) can also be used to control whether internal calls are forwarded. Details · Action: Advanced | Forward | Forward on Busy On. · Action Data: None. · Default Label: FwBOn or Fwd Busy.
Button Programming: Actions 7.3.89 Forward On No Answer On Switches forward on no answer on/off. The time used to determine the call as unanswered is the user's no answer time. Uses the Forward Number as its destination unless a separate Forward on Busy Number is set. Forward Internal (User | Forwarding) can also be used to control whether internal calls are forwarded. Details · Action: Advanced | Forward | Forward on No Answer On. · Action Data: None. · Default Label: FwNOn or Fwd No Answer.
7.3.91 Forward Unconditional On This function is also known as 'divert all' and 'forward all'. It forwards all calls, except hunt group and page calls, to the forward number set for the user's extension. To also forward hunt group calls to the same number 'Forward Hunt Group Calls On 603 ' must also be used. Forward Internal (User | Forwarding) can also be used to control whether internal calls are forwarded.
Button Programming: Actions 7.3.92 Group Monitors the status of a hunt group queue. This option is only supported for hunt groups with queuing enabled. The user does not have to be a member of the group. Depending on the users button type, indication is given for when the group has alerting calls and queued calls (queued in this case is defined as more calls waiting than there are available group members). · Pressing a Group button answers the longest waiting call.
7.3.93 Group Listen On Using group listen allows callers to be heard through the phone's handsfree speaker but to only hear the phone's handset microphone.
Button Programming: Actions 7.3.94 Group Paging Makes a paging call to an extension or group specified. If no number is specified, this can be dialed after pressing the button. The target extension or group members must be free and must support handsfree auto-answer in order to hear the page. On Avaya phones, a paged user can convert the page call into a normal call by pressing the Conference button. Details · Action: Emulation | Group Paging. · Action Data: User number or name or group number or name.
7.3.95 Headset Toggle This function is intended for use with Avaya phones that have separate handset and headset sockets but do not provide a dedicated Headset button, for example older style 4400 Series and 4600 Series phones. On phones without a headset socket or with a dedicated headset button this control will have no effect. Details · Action: Miscellaneous | Headset Toggle. · Action Data: None. · Default Label: HdSet. · Toggles: . · Status Indication: · User Admin: 627 . .
Button Programming: Actions 7.3.97 Hold CW Place the user's current call on hold and answers the waiting call. This function is not supported on phones which have multiple call appearance buttons set. Details · Action: Advanced | Hold | Hold CW. · Action Data: None. · Default Label: HoldCW. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
7.3.99 Hunt Group Enable An individual users membership of any particular hunt groups is programmed through the system configuration. This control allows the user to enable or disable that membership. While enabled, the user can receive hunt group calls when logged in. In addition to the lamp indication below, phones display G when any group membership is enabled. Details · Action: Advanced | Hunt Group | Hunt Group Enable.
Button Programming: Actions 7.3.100 Hunt Group Disable This function is obsolete, the Hunt Group Enable 614 function being able to toggle membership between enabled and disabled and providing lamp indication of when membership is enabled. An individual user's membership of any particular hunt groups is programmed through the system configuration. This control allows the user to disable that membership. They will no longer receive calls to that hunt group until their membership is enabled again.
7.3.101 Inspect Not supported. Provided for CTI emulation only. Allows users on display phones to determine the identification of held calls. Allows users on an active call to display the identification of incoming calls. Details · Action: Emulation | Inspect. · Action Data: None. · Default Label: Inspt. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
Button Programming: Actions 7.3.103 Last Number Redial This function is not supported for B5800 Branch Gateway. 7.3.104 Leave Word Calling Not supported. Provided for CTI emulation only. Leaves a message for the user associated with the last number dialed to call the originator. Details · Action: Emulation | Leave Word Calling. · Action Data: None. · Default Label: LWC. · Toggles: . · Status Indication: · User Admin: 627 . .
7.3.106 Manual Exclude Not supported. Provided for CTI emulation only. Details · Action: Emulation | Manual Exclude. · Action Data: None. · Default Label: Excl. · Toggles: . · Status Indication: · User Admin: . . 627 · Phone Support Note that support for particular phone models is also dependant on the system software level. · Analog: · 1400 Series: · 1600 Series: [1] · 2400 Series: · 3700 Series: [1] [1] · 4600 Series: · 5400 Series: · 5600 Series: [1] · 9500 Series: · 9600 Series: [1] 1.
Button Programming: Actions 7.3.108 Off Hook Station Enables the user's extension to be controlled by an application, for example SoftConsole. Calls can then be answered and cleared through the application without having to manually go off or on hook. Requires the phone to support full handsfree operation. Details · Action: Advanced | Miscellaneous | Off Hook Station. · Action Data: None. · Default Label: OHStn. · Toggles: . · Status Indication: · User Admin: 627 . .
7.3.109 Priority Call This feature allows the user to call another user even if they are set to 'do not disturb'. A priority call will follow forward and follow me settings but will not go to voicemail. Details · Action: Advanced | Call | Priority Call. · Action Data: User number or name. · Default Label: PCall or Priority Call. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
Button Programming: Actions · Phone Support 510 Note that support for particular phone models is also dependant on the system software level. · Analog: · 1400 Series: · 1600 Series: · · 2400 Series: · 3700 Series: · 4600 Series: · 5400 Series: · 5600 Series: * · 9500 Series: · 9600 Series: * *Not 1603, 4602, 5601 and 5602. Avaya Branch Gateway Manager 10.
7.3.112 Relay Off Opens the specified switch in the system's external output port (EXT O/P). This feature is not supported by Linux based systems. Details · Action: Advanced | Relay | Relay Off. · Action Data: Switch number (1 or 2). · Default Label: Rely-. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
Button Programming: Actions 7.3.114 Relay Pulse Closes the specified switch in the system's external output port (EXT O/P) for 5 seconds and then opens the switch. This feature is not supported by Linux based systems. Details · Action: Advanced | Relay | Relay Pulse. · Action Data: Switch number (1 or 2). · Default Label: Relay or Relay Pulse. · Toggles: . · Status Indication: · User Admin: 627 . .
7.3.115 Resume Call Resume a call previously suspended to the specified ISDN exchange slot. The suspended call may be resumed from another phone/ISDN Control Unit on the same line. Details · Action: Advanced | Call | Resume Call. · Action Data: ISDN Exchange suspend slot number. · Default Label: Resum. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
Button Programming: Actions 7.3.117 Ring Back When Free Sets a ringback on the extension being called. When the target extension ends its current call, the ringback users is rung (for their set No Answer Time) and if they answer, a new call is made to the target extension. Ringback can be cleared using the Cancel Ring Back When Free 577 function. Details · Action: Advanced | Miscellaneous | Ring Back When Free. · Action Data: None. · Default Label: AutCB or Auto Callback. · Toggles: .
7.3.118 Ringer Off Switches the phone's call alerting ring on/off. Details · Action: Emulation | Ringer Off. · Action Data: None. · Default Label: RngOf or Ringer Off. · Toggles: . · Status Indication: · User Admin: 627 Required. . · Phone Support Note that support for particular phone models is also dependant on the system software level.
Button Programming: Actions 7.3.119 Self-Administer Allows a user to program features against other programmable buttons themselves. Details · Action: Emulation | Self-Administer. · Action Data: See below. Value Other Phones None If no value is set, the button allows user programming of the following emulation actions. Abbreviated Dial. 555 Call Park To Other Extension. Abbreviated Dial Program. Call Pickup. 572 556 Directed Call Pickup. 594 Account Code Entry. 556 Directory. 596 AD Suppress. 560 Drop.
7.3.120 Send All Calls Sets the user's extension into 'Do Not Disturb' mode. Callers, other than those on the user's do not disturb exception list, receive busy or are diverted to the users voicemail mailbox. Note that with a call already connected and other calls already alerting, enabling Do Not Disturb will not affect those calls already existing. For full details of see Do Not Disturb 745 . When on, most phones display an N on the display. This function and the Do Not Disturb On ie.
Button Programming: Actions 7.3.121 Set Absent Text This feature can be used to select the user's current absence text. This text is then displayed to internal callers who have suitable display phones or applications. It doesn't changes the users status. The absence text message is limited to 128 characters. Note however that the amount displayed will depend on the caller's device or application. The text is displayed to callers even if the user has forwarded their calls or is using follow me.
7.3.122 Set Account Code Dials an account code and then returns dial tone for the user to dial a number. Can also be used to enter an account code after a call has been connected. Details · Action: Advanced | Set | Set Account Code.. · Action Data: Account code or blank. If blank, the user is prompted to dial an account code after pressing the button. · Default Label: Acct or Account Code. · Toggles: . · Status Indication: · User Admin: 627 . .
Button Programming: Actions 7.3.123 Set Hunt Group Night Service Puts the specified hunt group into Night Service 319 mode. Calls to a group set to night service, receive busy or are diverted to voicemail if available or are diverted to the group's night service fallback group if set. · Setting and clearing hunt group night service can be done using either manual controls or using a system time profile. The use of both methods to control the night service status of a particular hunt group is not supported.
7.3.124 Set Hunt Group Out Of Service Puts the specified hunt group into Out of Service 319 mode. Calls to a group set to out of service receive busy or are diverted to voicemail if available or are diverted to the group's out of service fallback group if set. · This function can be used to used to override hunt groups already set to night service mode by an associated time profile. · This function is currently not supported between systems in a multi-site network.
Button Programming: Actions 7.3.125 Set Inside Call Seq This feature allows the user to select the ringing used on their analog extension for internal calls. The number entered corresponds to the ring pattern required. This is 0 for Default Ring, 1 for RingNormal, 2 for RingType1, etc. For more information on selectable ringing patterns, see Ring Tones 739 . Use of this short code function is applicable to analog phone users only.
7.3.127 Set No Answer Time Allows the user to change their no answer time setting. This is the time calls ring before going to voicemail or following the user's divert on no answer setting if set on. In situations where call coverage is also being used, the user's no answer time must be greater than their individual coverage time for coverage to occur. Details · Action: Advanced | Set | Set No Answer Time. · Action Data: Time in seconds. · Default Label: NATim or No Answer Time. · Toggles: .
Button Programming: Actions 7.3.129 Set Outside Call Seq This feature allows the user to select the ringing used on their analog extension for external calls. The number entered corresponds to the ring pattern required. This is 0 for Default Ring, 1 for RingNormal, 2 for RingType1, etc. For more information on selectable ringing patterns, see Ring Tones 739 . Use of this short code function is applicable to analog phone users only.
7.3.131 Set Wrap Up Time Allows users to change their Wrap-up Time 281 (User | Telephony | Call Settings 281 ) setting. · Other phones or applications monitoring the user's status will indicate the user as still being busy (on a call). · Hunt group calls will not be presented to the user. · If the user is using a single line set, direct calls also receive busy treatment. If the user is using a mutli-line set (multiple call appearances), direct calls to them will ring as normal.
Button Programming: Actions 7.3.133 Stamp Log The stamp log function is used to insert a line into any System Monitor trace that is running. The line in the trace indicates the date, time, user name and extension plus additional information. The line is prefixed with LSTMP: Log Stamped and a log stamp number. When invoked from a Avaya phone with a display, Log Stamped# is also briefly displayed on the phone.
7.3.135 Suspend Call Uses the Q.931 Suspend facility. Suspends the incoming call at the ISDN exchange, freeing up the ISDN B channel. The call is placed in exchange slot 0 if a slot number is not specified. Only available when supported by the ISDN exchange. Details · Action: Advanced | Suspend | Suspend. · Action Data: Exchange slot number or blank (slot 0). · Default Label: Suspe. · Toggles: . · Status Indication: · User Admin: 627 . .
Button Programming: Actions 7.3.137 Time of Day Displays the time and date on the user's telephone. This function is ignored on those Avaya phones that display the date/ time by default. Details · Action: Emulation | Time of Day. · Action Data: None. · Default Label: TmDay. · Toggles: . · Status Indication: · User Admin: 627 . .
7.3.138 Timer Starts a timer running on the display of the user's extension. The timer disappears when the user ends a call. · This function can be used on Avaya phones (except 9600 Series) that display a call timer next to each call appearance. The button will temporarily turn the call timer on or off for the currently selected call appearance. The change only applies for the duration of the current call. Details · Action: Emulation | Timer. · Action Data: None. · Default Label: Timer. · Toggles: .
Button Programming: Actions 7.3.139 Transfer This function is not supported for Avaya Branch Gateway. 7.3.140 Toggle Calls Cycle between the user's current call and any held calls. Details · Action: Advanced | Call | Toggle Calls.. · Action Data: None. · Default Label: Toggl. · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
7.3.141 Twinning This action can be used by user's setup for mobile twinning. This action is not used for internal twinning. · While the phone is idle, the button allows the user to set and change the destination for their twinned calls. It can also be used to switch mobile twinning on/off and indicates the status of that setting. · When a call has been routed by the system to the user's twinned destination, the Twinning button can be used to retrieve the call at the user's primary extension.
Button Programming: Actions Avaya Branch Gateway Manager 10.
7.3.143 User Monitors whether another user's phone is idle or in use. The Telephone Number field should contain the users name enclosed in double quotes. The button can be used to make calls to the user or pickup their longest waiting call when ringing. On buttons with a text label, the user name is shown. The actions performed when the button is pressed will depend on the state of the target user and the type of phone being used. Phone Action/Options Idle Call the user.
Button Programming: Actions Details · Action: User. · Action Data: User name enclosed in "double-quotes". · Default Label: . · Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level. · Analog: · 1400 Series: · 1600 Series: [1] · 2400 Series: · 3700 Series: [1] [1] · 4600 Series: · 5400 Series: · 5600 Series: [1] · 9500 Series: · 9600 Series: [1] 1.
7.3.144 Visual Voice This action provides the user with a display menu for access to their mailbox. The menu provide the user with options to listening to messages, leaving messages and managing the mailbox. If pressed when a call is connected, the button allows entry of an extension number for direct to voicemail transfer of the connected call.
Button Programming: Actions Using the Visual Voice Button for Voicemail Transfer If pressed when you have a call is connected, the MESSAGE button allows entry of an extension number for direct to voicemail transfer of the connected call. Avaya Branch Gateway Manager 10.
7.3.145 Voicemail Collect Connects to the voicemail server. The telephone number must indicate the name of the Voicemail box to be accessed, eg. "?Extn201" or "#Extn201". The ? indicates "collect Voicemail" and the # indicates "deposit Voicemail". This action is not supported by voicemail using Intuity emulation mode. When used with Standalone Voice Mail, names of specific call flow start points can also be used to directly access those start points via a short code.
Button Programming: Actions 7.3.146 Voicemail Off Disables the user's voicemail box from answering calls that ring unanswered at the users extension. This does not disable the user's mailbox and other methods of placing messages into their mailbox. This button function is obsolete as the Voicemail On 649 function toggles on/off. Details · Action: Advanced | Voicemail | Voicemail Off. · Action Data: None. · Default Label: VMOff. · Toggles: . · Status Indication: · User Admin: 627 . .
7.3.148 Voicemail Ringback Off Disables voicemail ringback to the user's extension. This button function is obsolete as the Voicemail Ringback On function toggles on/off. 651 Details · Action: Advanced | Voicemail | Voicemail Ringback Off. · Action Data: None. · Default Label: VMRB· Toggles: . · Status Indication: · User Admin: 627 . . · Phone Support Note that support for particular phone models is also dependant on the system software level.
Button Programming: Actions 7.3.149 Voicemail Ringback On Enables voicemail ringback to the user's extension. Voicemail ringback is used to call the user when they have new voicemail messages in their own mailbox or a hunt group mailbox for which they have been configured with message waiting indication. The ringback takes place when the user's phone returns to idle after any call is ended. Details · Action: Advanced | Voicemail | Voicemail Ringback On. · Action Data: None.
Chapter 8. Apperance Button Operation Avaya Branch Gateway Manager 10.
Apperance Button Operation: 8. Apperance Button Operation Many Avaya phones supported on system have a programmable keys or buttons (the terms 'key' and 'button' mean the same thing in this context). Various actions can be assigned to each of these keys, allowing the phone user to access that action. Many of the phones also have indicator lamps next to the programmable buttons. These lamps are used to indicate the status of the button, for example 'on' or 'off'.
8.2 Call Appearance Buttons Call appearance buttons are used to display alerts for incoming calls directed to a user's extension number or to a hunt group of which they are a member. Call appearance buttons are also used to make outgoing calls. By having several call appearance buttons, a user is able to be alerted about several calls, select which call to answer, switch between calls and take other actions.
Apperance Button Operation: Call Appearance Buttons 8.2.1 Example 1 In this example, the user has multiple call appearance buttons. 1. Phone Idle The phone is currently idle. 2. First Call Alerts A call arrives. It alerts against the first available call appearance button. Pressing that button will answer the call. 3. Call Answered The call is now connected. 4. Second Call Alerts A second call arrives whilst the first is still connected. It alerts against the next available call appearance button.
8.2.2 Example 2 In this example, the user will use their call appearances to make two calls and start a conference between those calls. 1. Initial Call The user has a call in progress, shown on their first call appearance button. It is decided to conference another user into the call. 2. Make Conference Enquiry Pressing the CONFERENCE button on the users phone automatically places the current call on hold and takes the phone off hook on the next available call appearance. 3.
Apperance Button Operation: Call Appearance Buttons 8.2.3 How are Call Appearance Buttons Treated? For incoming calls · Call Waiting settings are ignored except for hunt group call waiting where the call waiting tone is replaced by an alert on a call appearance button if available. · Follow Me, Forward Unconditional and Forward Hunt Group Calls are used when set. · If Do Not Disturb is set, only calls from numbers in the user's Do Not Disturb Exception list will alert if a call appearance is available.
8.2.4 Button Indication On phones with a text display area next to the button, by default a=, b= and so on is displayed. This can be replaced by another label if required. When the user is not connected to a call, the button indicated as selected is the button that will be used if the user goes off hook without pressing an appearance button. When a user is connected to a call, that call is the selected button.
Apperance Button Operation: Call Appearance Buttons 8.3 Bridged Appearance Buttons A bridged appearance button shows the state of one of another user's call appearance buttons. It can be used to answer or join calls on that user's call appearance button. It can also be used to make a call that the call appearance user can then join or retrieve from hold. · When the user's call appearance button alerts, any associated bridged appearance buttons on other user's phones also alert.
8.3.1 Example 1 In this example, one user is able to see the status of the other user's call appearances, and when necessary answer calls for the other user. Both users have Ringing Line Preference and Auto Hold on. Call Appearance User Bridged Appearance User 1. Both Phone Idle Our user has bridged appearance buttons that match a colleague's call appearances buttons. 2. First Call The colleague has a call alerting on their first call appearance button.
Apperance Button Operation: Bridged Appearance Buttons 8.3.2 Example 2 In this example, the bridged appearance user makes a call on behalf of the call appearance user. Once the call is connected, they put it on hold. The call appearance user is able to take the call off hold using their call appearance button. Both users have Ringing Line Preference and Auto Hold on. Call Appearance User Bridge Appearance User 1.
8.3.3 Example 3 In this example, a call is passed from the call appearance user to the bridged appearance user. Both users have Ringing Line Preference and Auto Hold on. Bridged Appearance User 1. Call on Colleague's Phone The call appearance user has answered a call on one of their call appearances. The bridged appearance user's matching bridged appearance shows 'in use elsewhere'. 2. Call Held by Colleague The call appearance user has put the call on hold and called the bridged appearance user.
Apperance Button Operation: Bridged Appearance Buttons 8.3.4 How are Bridged Appearances Treated? Bridged appearance buttons operate in parallel with their matching call appearance button. · Whose user settings control the call? Until answered on a bridged appearance button, calls alerting on a bridged appearance button follow the settings of the user or hunt group to which the call was originally directed. · If the call appearance is in use, any matching bridged appearance will indicate the same.
8.3.5 Button Indication On phones with a text display area next to the button, the name of the bridged user and the label from the bridged user's call appearance key are displayed. The following table shows how the different states of bridged appearance buttons (alerting, held, etc) are indicated. This is a general table, not all phone button types are covered. The ring that accompanies the visual indication can be delayed or switched off. See Ring Delay 683 .
Apperance Button Operation: Bridged Appearance Buttons 8.4 Call Coverage Buttons Call coverage allows a user to be alerted when another user has an unanswered call. The user being covered does not necessarily have to be a key and lamp user or have any programmed appearance buttons. Their Individual Coverage Time setting (default 10 seconds) sets how long calls will alert at their extension before also alerting on call coverage buttons set to that user.
8.4.1 Example 1 In this example, the covering user is able to answer their colleagues call when it rings unanswered. Both users have Ringing Line Preference and Auto Hold on. Covered User Covering User 1. Both Phones Idle Our user has a call coverage button to cover their colleague. 2. Call to Covered User A call arrives for the covered user. 3. Call Alerts to Coverage After ringing for the covered user's Individual Coverage Time, the call also begins alerting on the call coverage button . 4.
Apperance Button Operation: Call Coverage Buttons 8.4.3 How is Call Coverage Treated? Whose user settings control the call? · Until answered, calls alerting on a call coverage button follow the settings of the user to which the call was originally directed. · Once answered, the call follows the user settings of the user who answered it. Coverage is applied to: · Internal calls dialed to the covered user's extension number. · External calls routed to the covered user by a incoming call route.
8.4.4 Button Indication On phones with a text display area next to the button, the name of the covered user is displayed followed by the word Cover. When the user is not connected to a call, the button indicated as selected is the button that will be used if the user goes off hook without pressing an appearance button. When a user is connected to a call, that call is the selected button.
Apperance Button Operation: Call Coverage Buttons 8.5 Line Appearance Buttons Line appearance buttons allow specific individual line to be used when making calls or answered when they have an incoming call. It also allows users to bridge into calls on a particular line. Incoming call routing is still used to determine the destination of all incoming calls. Line appearance buttons allow a call on a specific line to alert the button user as well as the intended call destination.
8.5.1 Example 1 In this example, the user is able to answer a call alerting on a particular line. 1. Line Goes Active A call is active on the line with line ID number 601. This is indicated as 'in use elsewhere'. · For an incoming call, the line will show active but will not alert until call routing has been determined. On analog ICLID lines, alerting is delayed until the ICLID that might be used to do the call routing has been received. 2.
Apperance Button Operation: Line Appearance Buttons 8.5.2 Example 2 In this example, two users exchange a call using line appearance buttons set to the same line. Note that this requires that the user who first answers the call to have Cannot be Intruded off. Both users have Ringing Line Preference and Auto Hold on. 1. Idle The two users has line appearances for the same line. 2. Call Alerts A call arrives. Either user can answer it by pressing the alerting line appearance 3.
8.5.3 How are Line Appearances Treated? Incoming Calls · Until answered using a line appearance button, incoming calls alerting on a line appearance, follow the settings of the incoming call route's destination group or user. They do not follow the settings of any line appearance user. · If an incoming calls destination is voicemail, or once the incoming call has passed from its destination to voicemail, it cannot be answered or bridged into using a line appearance button.
Apperance Button Operation: Line Appearance Buttons 8.5.4 Button Indication On phones with a text display area next to the button, the label Line and the line number are displayed. When the user is not connected to a call, the button indicated as selected is the button that will be used if the user goes off hook without pressing an appearance button. When a user is connected to a call, that call is the selected button.
8.6 Other Appearance Controls 8.6.1 Selected Button Indication During appearance button usage, one of the user's appearance buttons may be indicated as the user's current selected button. This is the appearance button already in use, or if idle, the appearance button that will be used if the user goes off hook by lifting the handset. · On phones with a display area next to each button, the current selected button is indicated by either an _ underscore of the button label, a * star or a shaded background.
Apperance Button Operation: Other Appearance Controls 8.6.2 Idle Line Preference Idle Line Preference determines the user's currently selected button as the first available idle call/line appearance button. Selected button indication 674 is applied to that button and if the user goes off-hook, for example by lifting their handset, an outgoing call is started on that button. · Idle Line Preference is overridden by Ringing Line Preference if also on for the user.
Idle Line Preference Example 1 In this example, only Idle Line Preference has been programmed for the user. Ringing Line Preference has not been programmed. 1. Phone Idle The phone is idle. The current selected button determined by Idle Line Preference is the first available idle call appearance button. This is shown by the _ underscore of the button text. 2. First Call to User A call for the user arrives. It alerts on the first available call appearance button.
Apperance Button Operation: Other Appearance Controls Idle Line Preference Example 3 In this example, both Idle Line Preference and Ringing Line Preference are set for the user. 1. Phone Idle The phone is idle and Idle Line Preference has assigned current selected button to the first call appearance. 2. Call Alerting A call has arrived and Ringing Line Preference keeps the current selected button at the first call appearance. 3.
8.6.3 Ringing Line Preference Ringing Line Preference determines the user's currently selected button as the button which has been alerting the longest. Selected button indication 674 is applied to that button and if the user goes off-hook, for example by lifting their handset, the alerting call on that button is answered. Ringing Line Preference includes calls alerting on call appearance, line appearance, bridged appearance and call coverage buttons.
Apperance Button Operation: Other Appearance Controls Ringing Line Preference Example 1 In this example, both Ring Line Preference and Idle Line Preference have been set for the user. They also have Ringing Line Preference on and Auto Hold is on. Answer Pre-Select is off. 1. Phone Idle The phone is idle. The current selected button has been determined by Idle Line Preference as the first available idle call appearance button. This is shown by the _ underscore next to that button. 2.
Ringing Line Preference Example 2 In this example, the user has both Ring Line Preference and Idle Line Preference programmed. They also have Ringing Line Preference on and Auto Hold is on. Answer Pre-Select is off. 1. First Call to User A call for the user arrives. It alerts on the first available call appearance button. Ringing Line Preference uses this as the currently selected button as it is the only alerting call. 2.
Apperance Button Operation: Other Appearance Controls 8.6.4 Answer Pre-Select On some phones, only the details of the call alerting or connected on the current selected button are shown. The details of calls alerting on other buttons are not shown or only shown briefly when they are first presented and are then replaced again by the details of the call on the current selected button. By default, pressing any of the other alerting buttons will answer the call on that button.
8.6.5 Auto Hold Auto Hold is a system wide feature that affects all appearance button users. This feature determines what happens when a user, who is already on a call, presses another appearance button. The options are: · If Auto Hold is off, the current call is disconnected. · If Auto Hold is on, the current call is placed on hold. Auto Hold Example 1 In this example, the user has two calls currently shown on call appearance buttons. Answer Pre-Select is off. 1.
Apperance Button Operation: Other Appearance Controls 8.6.6 Ring Delay Ring delay can be applied to appearance buttons. This option can be used with all types of appearance buttons and can be selected separately for each appearance button a user has. Using ring delay does not affect the buttons visual alerting through the display and display icons or button lamps. Ring delay is typically used with line appearance buttons for lines which a user wants to monitor but does not normally answer.
Ring Delay Example 1 In this example, the user has a line appearance button set but configured to no ring. 1. Phone Idle The phone is idle. The current selected button has been determined by Idle Line Preference as the first available call appearance button. This is shown by the _ underscore next to that button. 2. Incoming Call Alerting on the Line An incoming call arrives on the line and begin to alert somewhere on the system.
Apperance Button Operation: Other Appearance Controls 8.6.7 Delayed Ring Preference When a call is alerting at an idle phone, by default Ringing Line Preference button and if the user then goes off-hook they will answer that call. 678 sets the call as the currently selected In most situations this is acceptable as the user hears ringing which informs them that there is a call waiting to be answered.
Delayed Ring Preference Example 2 This is similar to the previous example except that the user and the line has been configured for a 15 second ring delay. This informs the users that the line has not been answered for some reason and allows them to answer it by just going off-hook. 1. Phone Idle The phone is idle. The current selected button has been determined by Idle Line Preference as the first available call appearance button. This is shown by the _ underscore next to that button. 2.
Apperance Button Operation: Other Appearance Controls 8.6.8 Collapsing Appearances This topic covers what happens when a user with several calls on different appearance buttons, creates a conference between those calls. In this scenario, the call indication will collapse to a single appearance button and other appearance buttons will return to idle. The exception is any line appearance buttons involved which will show 'in use elsewhere'.
8.6.9 Joining Other Calls (Bridging) Appearance buttons can be used to "join" existing calls and create a conference call. A user can join calls that are shown on their phone as 'in use elsewhere'. · This feature is often referred to as 'bridging into a call'. However this causes confusion with Bridged appearance buttons and so the term should be avoided.
Apperance Button Operation: Other Appearance Controls Joining Example 1: Joining with a Bridged Appearance In this example, the user joins a call using a bridged appearance button. Answer Pre-Select is off. 1. User with Bridged Appearance Buttons The user has bridged appearance buttons that match their colleagues call appearance buttons. 2. Call on Bridged Appearance The colleague has a call in progress on their first call appearance. This is matched on the first bridged appearance button. 3.
8.6.10 Multiple Alerting Buttons In some scenarios, it is may be potentially possible for the same call to alert on several appearance buttons. In this case the following apply: · Line appearance buttons override call and bridged appearance buttons In cases where a call on a line goes directly to the user as the incoming call route's destination, the call will only alert on the line appearance. In this scenario the ring delay settings used is that of the first free call appearance button.
Apperance Button Operation: Other Appearance Controls 8.6.11 Twinning Twinning is a mechanism that allows an user to have their calls alert at two phones. The user's normal phone is referred to as the primary, the twinned phone as the secondary. By default only calls alerting on the primary phone's call appearance buttons are twinned. For internal twinning, the system supports options to allow calls alerting on other types of appearance buttons to also alert at the secondary phone.
8.6.14 Logging Off and Hot Desking Users can be setup to log in and log out at different phones, this is called 'hot desking'. All the users settings, including their extension number, are transferred to the phone at which the user is logged in. This includes their key and lamp settings and appearance buttons.
Apperance Button Operation: Other Appearance Controls 8.7 Programming Appearance Buttons This section covers the programming of appearance buttons for users into existing system configurations. · Appearance Functions The functions Call Appearance, Bridged Appearance, Coverage and Line Appearance are collectively known as "appearance functions". For full details of their operation and usage refer to the Appearance Button Operation 653 section.
Programming Appearance Buttons Using Branch Gateway Manager If only button programming changes are required, the configuration changes can be merged back to the system without requiring a reboot. 1. Start Branch Gateway Manager and load the current configuration from the system. 2. Locate and select the user for whom appearance buttons are required. 3. Select Button Programming.
Apperance Button Operation: Programming Appearance Buttons 8.7.1 System Settings System settings are applied to all users and calls. The system settings that affect appearance operation are found on the System | Telephony 159 tabs and are: · Auto Hold: Default = On. Used for users with multiple appearance buttons. When on, if a user presses another appearance button during a call, their current call is placed on hold.
8.7.2 User Settings User settings are applied separately to each individual user. In addition to button programming, the following user settings are applicable to appearance button operation: · Cannot be Intruded: Default = On. This feature controls whether other users can use their appearance buttons to join the users call. It applies when the user is the longest present internal party already within the call. · Individual Coverage Time (secs): Default = 10 seconds, Range 1 to 99999 seconds.
Apperance Button Operation: Programming Appearance Buttons 8.7.3 Line Appearance ID Numbers Line appearances are supported for analog, E1 PRI, T1, T1 PRI, and BRI PSTN trunks. They are not supported for E1R2, QSIG and IP trunks. Note that setting and changing line settings including line appearance ID numbers requires the system to be rebooted. Automatic Renumbering 1. Select Tools | Line Renumber. 2. Select the starting number required for line numbering and click OK. 3.
8.7.4 Outgoing Line Programming Assigning line ID numbers to lines and associating line appearance buttons to those lines is sufficient for answering incoming calls on those lines. However, to use line appearance buttons for outgoing calls may require further programming. Short Codes and Outgoing Line Appearance Calls Once a line has been seized using a line appearance button, short code matching is still applied to the number dialed. That can include user, system and ARS short codes.
Apperance Button Operation: Programming Appearance Buttons Avaya Branch Gateway Manager 10.
Chapter 9. Telephone Features Avaya Branch Gateway Manager 10.
Telephone Features: 9. Telephone Features This section provides descriptions of the following telephony functions provided by the system.
9.1 Date and Time The control unit contains a battery backed clock which is used to maintain system time during normal operation and when mains power is removed. For files stored on memory cards the system uses the UTC time. For other activities such as call logs, SMDR records, time display on phones; the local time (UTC + any offsets) is used. The time can be set in a number of ways list below.
Telephone Features: Date and Time Manually Setting the System Time For systems without access to a time server, a number of methods to manually set the system time exist. In both cases the user's login code, if set, is used to restrict access to the time and date settings. 1400, 1600, 9500 and 9600 Phones Phones in these series (excluding the 1403/1603 models) can set the system time and date when the extension user is configured with System Phone Rights 742 .
9.2 User Directory Access On Avaya phones with suitable displays, the various system directories can be accessed. The user can then select which directory they want to search and then search that directory by dialing part of the required name and selecting from the displayed matches. · On phones with a Contacts button, that button can be used to access the system directories plus the users own centralized personal directory.
Telephone Features: User Directory Access 9.3 Mobile Call Control Mobile call control is only supported on digital trunks including SIP trunks. It allows a user receiving a call on their twinned device to access system dial tone and then perform dialing action including making calls and activating short codes. After answering a twinned call, the Mobile Call Control user can dial ** (within 1 second of each other) to place that call on hold and instead get dial tone from the system.
Enabling Outgoing Mobile Call Control 1.Configure the user for Mobile Twinning and Mobile Call Control On the User | Mobility 295 tab do the following: · Enable Mobility Features for the user. · Set the Twinned Mobile Number for the user's twinned calls destination. · Digits are matched from right to left. · The match must be at least 6 digits. If either the CLI or the Mobile Twinned Number is less than 6 digits no match will occur. · Matching is done for up to 10 digits. Further digits are ignored.
Telephone Features: Mobile Call Control 9.3.1 Mobile Direct Access (MDA) For a Mobile Call Control or one-X Mobile client user, FNE32 immediately redials on switch the DDI digits received with the call rather than returning dial tone and waiting for DTMF digits as with FNE31. This is called Mobile Direct Access (MDA). MDA requires the user's external telephony provider to provide a direct trunk with DDI to the system (ie. an ISDN or SIP trunk).
9.3.2 Mobile Callback Mobile callback 708 allows the user to call the system and then hang up. The system will then make a call to the user's CLI and when answered, provide them with dial tone from the system to make calls. Mobile callback is subject to all the normal trunk type and user licensing restrictions of mobile call control the user must have the Mobile Callback (User | Mobility)setting enabled in the system configuration. 705 .
Telephone Features: Mobile Call Control 9.3.3 one-X Mobile Client The system is configured to route incoming calls on those DID numbers to short codes for each feature. The caller's incoming CLI is then checked for a match against the mobile twinning and forwarding numbers of those users configured for one-X Mobile operation. If a match is found access to the one-X feature is allowed using the identity of that user as if they were now dialing from an extension on the system.
Restrictions · Supported Phones and Phone Client Software Avaya one-X Mobile Client on mobile cell phones that run Windows Mobile V5/V6 and Symbian Single-Mode (V4.0). For the regularly updated list refer to the Avaya one-X Mobile section of the Avaya support website (support. avaya.com). This same site is also the location of the client software files that need to be installed on the phone and how to transfer those files to the phone. · Each phone requires a settings file.
Telephone Features: Mobile Call Control Feature Name Extension (FNE) Services The one-X Mobile client accesses system features using DID numbers routed to system short codes set to the FNE service. The number set in the short code indicates the particular FNE service required. The table below lists the FNE services supported by system. The settings file tag is the string used in the phone software settings file to associate a feature with a DID number.
Example Configuration Overview In this example, two DID numbers are going to be used to allowed one-X Mobile Users to access the FNE functions 00, 01 and 26. This will allows those users respectively to obtain system dial tone, to acquire a call alerting on their normal extension and to transfer a call. The DID numbers requested were 555 76769900, 555 76769901 and 555 76769926 with 4 digits being passed by the provided to the system, ie. 9900, 9901 and 9926.
Telephone Features: Mobile Call Control one-X Mobile Client Configuration File During installation of the one-X Mobile software, a settings files is installed on the phone. For Windows phones, the file is called settings.ini file, for Symbian single-mode phones the file is called setting.1xme file. For some phones, once the software has been installed, the settings file values can be changed through the phone interface. Example Settings Files Windows Mobile 'settings.ini' Symbian 'settings.
Configuration File Fields · LOCATION_NAME = ; for example LOCATION_NAME = Boston; This is a required tag for Windows Mobile .ini settings file only. It is not present or required for a Symbian configuration file. The string defines the location name of the one-X Mobile server and it will be displayed in the Avaya one-X Mobile menu on the mobile phone. If you have multiple locations, each location must have a unique LOCATION_NAME value. · PRE_IMS = ; This tag is not used.
Telephone Features: Mobile Call Control 9.4 Advice of Charge The system supports advice of charge (AOC) on outgoing calls to ISDN exchanges that provide AOC information. It supports AOC during a call (AOC-D) and at the end of a call (AOC-E). This information is included in the SMDR output. AOC is only supported on outgoing ISDN exchange calls. It is not supported on incoming calls, reverse charge calls, QSIG and non-ISDN calls.
Avaya Branch Gateway Manager 10.
Telephone Features: Advice of Charge 9.5 Centralized System Directory Directory services can be used to import directory records (names and numbers) from external sources. These sets of records are regularly re-imported. For systems, the directory records can come from the following sources: · LDAP Import 171 The system can import up to 5000 LDAP records for use within directories shown by user phones and applications. LDAP import is configured through the System | Directory Services | LDAP 171 form.
Avaya Branch Gateway Manager 10.
Telephone Features: Centralized System Directory Use of Directory Records Directory records are used for two types of function: · Directory Dialing Directory numbers are displayed by user applications such as SoftConsole. Directory numbers are viewable through the Dir 596 function on many Avaya phones (Contacts or History). They allow the user to select the number to dial by name. The directory will also contain the names and numbers of users and hunt groups on the system.
Directory Special Characters The following characters are supported in directory records. They are supported in both system configuration records and in imported records. · ? = Any Digit Directory records containing a ? are only used for name matching against the dialed or received digits on outgoing or incoming. They are not included in the directory of numbers to dial available to users through their phones or applications.
Telephone Features: Centralized System Directory Imported Records · Imported directory records are temporary until the next import refresh. They are not added to the system's configuration. · They cannot be viewed or edited using Branch Gateway Manager or edited by a system phone 742 user. · The temporary records are lost if the system is restarted. However the system will request a new set of imported directory records after a system restart.
9.6 Centralized Personal Directory Each system user is able to have up to 100 personal directory records stored by the system unless their home system limit has been reached (10800 total records). A user's personal directory is also usable with 1400, 1600, 9500 and 9600 Series phones with a CONTACTS button. The user can view these records and use them to make calls. 1400, 1600, 9500 and 9600 Series phone users can edit their personal directory records through the phone.
Telephone Features: Centralized Personal Directory 9.7 Centralized Call Log The system can store a centralized call log 723 for users. Each users' centralized call log can contain up to 30 call records for user calls. When this limit is reached, each new call records replaces the oldest previous record. On Avaya phones with a fixed Call Log or History button (1400, 1600, 9500 and 9600 Series), that button can be used to display the user's centralized call log.
Controlling Centralized Call Logging The following controls exist for which users have their calls included in the centralized call log and which calls are included. User Setting The user centralized call log settings can be set through the user configuration (User | Telephony | Call Log through their associated user rights (User Rights | Telephony | Call Log 396 ).
Telephone Features: Centralized Call Log Call Scenarios This is not a comprehensive list. However it summarizes how the user call log is used in some common call scenarios. Scenarios User Call Log Notes Authorization/Accou Account and authorization codes used as part of a call are not included in user call logs. nt Codes Automatic Callback If answered, they will show as an outgoing call to the target.
9.8 Coverage Groups For users with a Coverage Group selected, coverage group operation is applied to all external calls that are targeted to the user. For external calls: · In scenarios where an external call would normally have gone to voicemail, it instead continues ringing and also starts alerting the members of the coverage group. · The follow me settings of Coverage Group members are used, the forwarding settings are not.
Telephone Features: Coverage Groups 9.9 Fax Relay Group 3 Fax is the common standard for fax transmission over analog and digital (TDM) phone lines. However, the sending of fax calls over IP lines is not normally possible or proves unreliable due to the distortion caused during encoding of the audio signal. However some SIP line providers support fax using specific codecs. For a system with an IP500 VCM. IP500 VCM V2 or IP500 Combo cards, T38 or G.711 can be selected for fax over SIP lines.
9.10 Malicious Call Tracing (MCID) MCID (Malicious Caller ID) is an ISDN feature. It is supported on BRI and PRI trunks to ISDN service provider who provide MCID. When used, it instructs the ISDN exchange to perform a call trace on the user's current call and to keep a record of the call trace at the exchange for the legal authorities. Trace information is not provided to or displayed by the system or system phones. The use of MCID is subject to local and national legal requirements that will vary.
Telephone Features: Malicious Call Tracing (MCID) 9.11 Call Barring Call barring can be applied in a range of ways. · Barring a User From Making Any External Calls For each user, Outgoing Call Bar 283 (User | Telephony | Supervisor Settings user from making any outgoing calls. 283 ) can be selected to stop that · Barring Particular Numbers/Number Types System short codes are used to match user dialing and then perform a specified action.
9.12 Caller Display Caller display displays details about the caller and the number that they called. On internal calls, the system provides this information. On external calls it uses the Incoming Caller Line Identification (ICLID) received with the call. The number is also passed to system applications and can be used for features such as call logging, missed calls and to make return calls.
Telephone Features: Caller Display 9.13 Call Intrusion The system supports several different methods for call intrusion. The method used affects which parties can hear and be heard by other parties following the intrusion. In the scenarios below, user A is on a call with B who may be internal or external. User C invokes one of the call intrusion methods targeting user A.
Feature Description Privacy Settings User Coaching Intrusion Call Appearance 654 Bridged Appearance Can Intrude Cannot Be Intruded Private Call Used Used Used Not Used Used Used Not Used Used The Can Intrude setting of the user is not used. The Cannot Be Intruded setting of the longest present internal party in the call is used.
Telephone Features: Call Intrusion 9.14 Call Tagging Call tagging associates a text string with a call. That string remains with the call during transfers and forwards. On Avaya display phones, the text is shown whilst a call is alerting and is then replace by the calling name and number when the call is connected. On analog phones with a caller ID display, the tag text replace the normal caller information. Applications such as SoftConsole display any call tag associated with a call.
9.15 Private Calls This feature allows users to mark a call as being private. When on, any subsequent calls cannot be intruded on 731 until the user's private call status is switched off. The exception is Whisper Page 651 which can be used to talk to a user on a private call. Note that use of private calls is separate from the user's intrusion settings. If the user's Cannot be Intruded (User | Telephony | Supervisor Settings 283 ) setting is enabled, switching private calls off does not affect that status.
Telephone Features: Call Pickup 9.17 Call Waiting Call waiting allows a user who is already on a call to be made aware of a second call waiting to be answered. User Call Waiting Call waiting is primarily a feature for analog extension users. The user hears a call waiting tone and depending on the phone type, information about the new caller may be displayed. The call waiting tone varies according to locale 798 .
9.18 Parking Calls Parking a call is an alternative to holding a call. A call parked on the system can be retrieved by any other user if they know the system park slot number used to park the call. When the call is retrieved, the action is known as Unpark Call or Ride Call. While parked, the caller hears music on hold if available. Each parked call requires a park slot number. Attempting to park a call into a park slot that is already occupied causes an intercept tone to be played.
Telephone Features: Parking Calls 9.19 Ring Back When Free Also called 'callback' and 'automatic callback'. If the user called is busy, setting a ringback allows you to hang up and wait until they are free. When set, once the busy extension becomes free, the system will ring your telephone when also idle and, when answered, call the original target extension. Note · If the extension called has multiple call appearance buttons, you will not receive busy until all its call appearance buttons are in use.
9.20 Message Waiting Indication Message waiting indication (MWI) or a message lamp is supported for a wide variety of phones. It is used to provide the user with indication of when their voicemail mailbox contains new messages. It can also be configured to provide them with indication when selected hunt group mailboxes contain new messages. Avaya digital and IP phones all have in-built message waiting lamps.
Telephone Features: Message Waiting Indication 9.21 Ring Tones Ring tones can be defined in the following terms: · Distinctive Ringing - Inside, Outside and Ringback A distinctive ring tone can be given for each of the different call types: an internal call, an external call and a ringback calls (voicemail calls, ringback when free calls, calls returning from park, hold or transfer). · The distinctive ringing patterns used for most non-analog phones are as follows: · Internal Call: Repeated single-ring.
9.22 Music On Hold (MOH) Each system can provide music on hold (MOH) from either internally stored files or from externally connected audio inputs.Up to 4 different hold music sources are supported. Legal Requirements You must ensure that any MOH source you use complies with copyright, performing rights and other local and national legal requirements. System Source The first source is called the System Source. This source is numbered source 1.
Telephone Features: Music On Hold (MOH) External Inputs A system can accept external audio input. This option is not supported on Linux based systems. · AUDIO Port If the System Source is set to External, the audio input to the 3.5mm port marked AUDIO on the back of the control unit is used following a reboot. · Analog Extension Port The audio input from an analog extension port can also be used as any of the 3 alternate sources.
9.23 System Phone Features The user option System Phone Rights (User | User 271 ) can be used to designate a user as being a system phone user. System phone users can access a number of additional function not available to other phone users. Note that if the user has a login code set, they will be prompted to enter that code in order to access these features. · None The user cannot access any system phone options.
Telephone Features: System Phone Features 9.24 The 'No User' User It is possible to have an extension which has no default associated user. This can occur for a number of reasons: · The extension has no Base Extension setting associating it with a user who has the same setting as their Extension to indicate that they are the extension's default associated user 9.
Notes · Retrieving Externally Forwarded Calls Where a call is forwarded to an external destination and receives busy or is not answered within the forwarding user's No Answer Time, the system will attempt to retrieve the call. If forwarded on a trunk that does not indicate its state the call is assumed to have been answered, for example analog loop start trunks. · Off-Switch Forwarding Restrictions User forwarding is subject to the same restrictions as transferring calls.
Telephone Features: Forwarding Calls 9.26.1 Do Not Disturb Summary: Redirect all calls to busy tone or to voicemail if available except those in your DND exceptions list. Do Not Disturb (DND) is intended for use when the user is present but for some reason does not want to be interrupted. Instead calls are sent to voicemail if available, otherwise they receive busy tone. · Exceptions Specific numbers can be added to the user's Do Not Disturb Exception List. Calls from those numbers override DND.
Do Not Disturb Controls Do Not Disturb Branch Gateway Manager A user's DND settings can be viewed and changed through the User | DND configuration settings. Controls The following short code features/button programming actions can be used: Feature/Action Short Code Do Not Disturb On 467 *08 Do Not Disturb Off 467 *09 Do Not Disturb Exception Add Cancel All Forwarding 449 tab within the system Button - Toggles.
Telephone Features: Forwarding Calls 9.26.2 Follow Me Summary: Have your calls redirected to another user's extension, but use your coverage, forwarding and voicemail settings if the call receives busy tone or is not answered. Follow Me is intended for use when a user is present to answer calls but for some reason is working at another extension such as temporarily sitting at a colleague's desk or in another office or meeting room.
Follow Me Controls Follow Me Branch Gateway A user's Follow Me settings can be viewed and changed through the User | Forwarding 288 tab within Manager the system configuration settings. Note that on this tab, entering a Follow Me Number also enables Follow Me.
Telephone Features: Forwarding Calls 9.26.3 Forward Unconditional Summary: Have your calls redirected immediately to another number including any external number that you can dial. · Priority This function is overridden by DND and or Follow Me if applied. Forward Unconditional overrides Forward on Busy and Forward on No Answer. · Destination The destination can be any number that the user can dial.
Forward Unconditional Controls Forward Unconditional Branch Gateway Manager A user's forwarding settings can be viewed and changed through the User | Forwarding the system configuration settings.
Telephone Features: Forwarding Calls 9.26.4 Forward on Busy Summary: Have your calls redirected when you are busy to another number including any external number that you can dial. The method by which the system determines if a user is 'busy' to calls depends on factors such as whether they have multiple calls appearance buttons or Call Waiting and or Busy on Held set. See Busy 755 . · Priority This function is overridden by DND and or Forward Unconditional if applied.
Forward on Busy Controls Forward on Busy Software Level A user's forwarding settings can be viewed and changed through the User | Forwarding the system configuration settings. Controls tab within The following short code features/button programming actions can be used: Feature/Action Forward Number Short Code Forward on Busy On 476 Forward on Busy Off 476 Disable Internal Forwards Enable Internal Forwards Button *57*N# 475 *03 - Toggles.
Telephone Features: Forwarding Calls 9.26.5 Forward on No Answer Summary: Have your calls redirected another number if it rings without being answered. · Priority This function is overridden by DND and Forward on Busy if applied. It can be applied after a Follow Me attempt. Forward Unconditional overrides Forward on Busy and Forward on No Answer. · Destination The destination can be any number that the user can dial.
Forward on No Answer Controls Forward on No Answer Branch Gateway Manager A user's forwarding settings can be viewed and changed through the User | Forwarding the system configuration settings. Controls The following short code features/button programming actions can be used: Feature/Action Forward Number Short Code Button *57*N# 475 Forward on No Answer On 477 *05 Forward on No Answer Off 477 *06 Enable Internal Forwards Disable Internal Forwards - Toggles.
Telephone Features: Forwarding Calls 9.26.6 Determining a User's Busy Status Various system features allow users to handle more than one call at a time. Therefore the term "busy" has different meanings. To other users it means whether the user is indicated as being busy. To the system it means whether the user is not able to receive any further calls. The latter is used to trigger 'busy treatment', either using a user's Forward on Busy settings or redirecting calls to voicemail or just returning busy tone.
9.26.7 Chaining and Loops Chaining is the process where a call forward to an internal user destination is further forwarded by that user's own forwarding settings. · Follow Me Calls Follow Me calls are not chained. They ignore the forwarding, Follow Me and Do Not Disturb settings of the Follow Me destination. · Voicemail If the call goes to voicemail, the mailbox of the initial call destination before forwarding is used.
Telephone Features: Forwarding Calls 9.27 Transferring Calls The following are some of the methods usable to transfer calls. · Supervised Transfer This is a transfer where the user waits for the transfer destination to answer and talks to that party before completing the transfer, this is referred to as a consultation call. They then either complete the transfer or drop the call and return to the held for transfer call.
9.27.1 Off-Switch Transfer Restrictions Users cannot transfer calls to a destination that they cannot normally dial. This applies to manual transfers and also to automatic transfers (forwarding). In addition to call barring applied through short codes, the following system settings may restrict a users ability to transfer calls. User Specific Controls · Outgoing Call Bar: Default = Off (User | Telephony | Supervisor Settings 283 ) When enabled, this setting stops a user from making any external calls.
Telephone Features: Transferring Calls 9.27.2 Context Sensitive Transfer For Release 6.x and higher, there has been a change to telephone behaviour for call transfers and how a call put on hold pending transfer is indicated. These new behaviours apply to 1400, 1600, 9500 and 9600 Series telephones.
9.27.3 Dial Tone Transfer A user who is not able to make external calls to any or some external numbers, can be transferred to dial tone by a user who is able to make external calls. 1. The restricted user wanting to make the external call, dials the unrestricted user and requests dial tone. 2. The unrestricted user initiates a transfer and dials the prefix for an ARS form configured to provide secondary dial tone. · The prefix is a short code set up to access the required ARS form.
Telephone Features: Transferring Calls Account and Authorization Codes If the restricted user enters an account or authorization code while calling the unrestricted user to request dial tone, that value is not carried forward with their external call once they have been provided with secondary dial tone. If the unrestricted user enters an account or authorization code while dialing the ARS form, that value remains associated with the call made by the restricted user.
9.27.4 Handsfree Announced Transfers This feature allows the enquiry call part of a supervised transfer to be answered handsfree. In addition the system can be optionally configured to allow both the enquiry call and completed transfer call to be auto-answered. Example 1. User 201 answers a call that they then want to transfer to user 203. 2. They press TRANSFER to put the call on hold pending transfer. 3. They then press a Dial Direct button and dial 203. 4.
Telephone Features: Transferring Calls Avaya Branch Gateway Manager 10.
9.27.5 One Touch Transferring This feature allows selected users to transfer calls to each other using a reduced number of key presses. · With this option, a call can be transferred by simply selecting the transfer destination and then hanging up (or pressing Transfer if working handsfree). · Without this option the normal sequence is to press Transfer, dial the destination and then hanging up (or pressing Transfer if working handsfree).
Telephone Features: Transferring Calls 9.27.6 Centrex Transfer Centrex Transfer is a feature provided by some line providers on external analog lines. It allows the recipient of a calls on such a line to transferred that call to another external number. The transfer is then performed by the line provider and the line is freed. Without Centrex Transfer, transferring an external call to another external number would occupy both a incoming and outgoing line for the duration of the call.
9.28 Conferencing The Avaya Branch Gateway system supports a number of conference features and allows multiple simultaneous conferences. Conference Types There are 2 types of conference supported by the system: · Ad-Hoc Conferencing An ad-hoc conference is one created on the fly, typically by holding an existing call, making another call and then pressing a conference key on the phone. Other people can be added to the conference by repeating the process.
Telephone Features: Conferencing 9.28.1 Conference Phones The system does not restrict the type of phone that can be included in a conference call. · Use Mute When not speaking, use of the mute function helps prevent background noise from your location being added to the conference call. This is especially important if you are attempting to participate handsfree.
9.28.2 Ad-Hoc Conferencing Conference add controls can be used to place the user, their current call and any calls they have on hold into a conference. When used to start a new conference, the system automatically assigns a conference ID to the call. This is termed ad-hoc (impromptu) conferencing. If the call on hold is an existing conference, the user and any current call are added to that conference. This can be used to add additional calls to an ad-hoc conference or to a meet-me 768 conference.
Telephone Features: Conferencing 9.28.3 Meet Me Conferencing Conference meet-me refers to features that allow a user or caller to join a specific conference by using the conference's ID number (either pre-set in the control or entered at the time of joining the conference). · ! Note Conference Meet Me features can create conferences that include only one or two parties. These are still conferences that are using resources from the host system's conference capacity.
Avaya Branch Gateway Manager 10.
Telephone Features: Conferencing 9.28.4 Routing External Callers Internal users can access Meet Me conferencing using short code and buttons. Additional methods need to be provided for external callers. Typically this is done using a system short code to which the external call is then directed by one of the options below. This has the advantage that internal users can also dial the same short code to access the same conferences.
9.28.5 Context Sensitive Conferencing For Release 6.x and higher, on 1400, 1600, 9500 and 9600 Series telephones there have been changes to the display and handling of calls put on hold pending transfer. See Context Sensitive Transfer 759 . For those phones there have also been changes to which calls are conferenced when a Conference button or Conf display option is pressed on the telephone. Previously, pressing Conference would put the user's current call and all held calls into a conference.
Telephone Features: Conferencing 9.29 Hot Desking Hot desking allows users to log in at another phone. Their incoming calls are rerouted to that phone and their user settings are applied to that phone. There are a number of setting and features which affect logging in and out of system phones. · In order to hot desk, a user must be assigned a Login Code the system configuration. 283 (User | Telephony | Supervisor Settings 283 ) in · By default, each system extension has an Base Extension setting.
9.29.1 Call Center Agents On systems with a call center application such as Compact Contact Center (CCC) or Compact Business Center (CBC), logging in and logging out is a key part of tracking and reporting on call center agents. It also controls call distribution as, until the agent logs in, their hunt group membership is seen as disabled. For CCC, CBC and Delta Server, an agent is defined as being a user with a Login Code and set to Forced Login. Those users consume a CCC agent license.
Telephone Features: Hot Desking 9.29.2 Hot Desking Examples The following are example of different ways that the hot desking settings can be used. Scenario 1: Occasional Hot Desking In this scenario, a particular user, for this example extension 204, needs to occasionally work at other locations within the building. 1. A Login Code is added to the user's configuration settings, for this example 1234. 2. The user can now log in when needed at any other phone by dialing *35*204*1234#.
9.29.3 Automatic Log Off Normally a user can either log themselves out or be logged out by another user logging in. The following methods can be used by the system to automatically log out a user. A remote hot desking user whose home system can no longer be seen by the remote system at which they are logged in is automatically logged out after 24 hours. The following methods only apply to users with a Login Code and set to Forced Login.
Telephone Features: Hot Desking 9.30 Paging Paging Scenario Paged Device Connects to... Short Code/ Button Feature Phone to Phone 777 Simple paging to other system extensions. Digital Station and Avaya H.323 Phones Dial Paging Mixed Paging 778 This refers to simultaneous paging to phones and a paging speaker. Analog Extension (Paging Speaker) Dial Paging Paging Interface Device 778 Analog Extension This refers to paging to a paging interface device such as (IVR Port) a UPAM.
Mixed Paging · Uses an amplifier connected to an analog extension port via a 600ohm isolating transformer. Some amplifiers include an integral transformer. · Avaya/Lucent branded amplifiers are designed for connection to special paging output ports not provided on systems. They are not suitable for supporting mixed paging. · The transformer and amplifier must be connected when the system is restarted.
Telephone Features: Paging 9.30.1 Paging Via Standalone Voice Mail Standalone Voice Mail can be used to deliver pre-recorded announcements. This can be useful when the same announcement is repeated frequently. This method requires the paging port to be an analog extension. This method also removes the feedback loop that can occur on some sites as the page is first recorded and then played. Example 1 1. In Standalone Voice Mail, a new Module was added and named Page. 2.
Example 2 This example builds on example 1 by allowing the user to select which message is played from a menu. In this example the user can press 1, 2 or 3 for different messages. They can also re-record the message associated with option 3 by pressing #. A Play List action was added and in this example set to record pagemsg3.wav. Note that just the file name was specified as this action saves files relative to the Voicemail Server's WAVS folder. In the Post Dial action that plays back pagemsg3.
Telephone Features: Paging 9.31 Voice over IP Features 9.31.1 Wide Band Audio Support Avaya Branch Gateway Release 6.2 systems support the G.722 64K codec for wide band audio. G.722 can be used with H.323 and SIP trunks. If can also be used with some SIP and H.323 IP telephones (see below). G.722 uses a higher speech sample rate (16KHz) than is used by most other audio codecs (8KHz). G.722 is only supported by systems that are using IP500 VCM, IP500 VCM V2 and or IP500 Combination cards.
9.31.2 Secure VoIP (SRTP) Secure Real-Time Transport Protocol (SRTP) refers to the application of additional encryption and or authentication to VoIP calls (SIP and H.323). SRTP can be applied between telephones, between ends of an IP trunk or in various other combinations. This option is supported from Release 6.x though fields for configuring this feature were visible in earlier releases.
Telephone Features: Voice over IP Features Avaya Branch Gateway Support SRTP is supported on Avaya Branch Gateway systems fitted with IP500 VCM, IP500 VCM V2 and or IP500 Combination cards. SRTP is only supported when also using TLS or VPN tunnels for connections between systems. This must be end to end TLS or VPN if the VoIP calls transit multiple systems. The Avaya Branch Gateway supports encryption, authentication and replay attack protection. It does not support rekeying.
Avaya Branch Gateway Manager 10.
Chapter 10. Data Routing Avaya Branch Gateway Manager 10.
10. Data Routing The system is a network router. In this role it can connect users on its LAN to remote services by using WAN links and telephone trunk connections. It can also allow users to dial-in and then act as if they were using a PC on the LAN. As well as being a network router, the system is a telephone system. These dual roles allow it to support a range of functions that involve traffic between the network and telephony interfaces. These functions use internal data channels.
Data Routing: DHCP 10.3 Examples 10.3.1 Simple ISDN Internet Connection In this example, we want all non-local data traffic to be routed to the Internet. The Internet Service Provider (ISP) has provided the account details required. Using the system's Network Address Translation 786 (NAT), a single account can be used for all users. 1. Select Service and add a normal service. Change the following settings and click OK. · Name: Internet · Account Name: As provided by the ISP.
10.3.2 Using a Dedicated T1/PRI ISP Link This section shows an example of a dedicated WAN PPP link to an Internet Service Provider (ISP) over a set of T1 or T1 PRI line channels. The ISP must support this mode of connection and will need to provide details of the required settings. If multiple channels are to be used, then the ISP must support Multilink PPP. 1. Create a New WAN Service A service is used to define connection settings such as name, password, bandwidth, etc. 1.
Data Routing: Examples 3. Create an IP Route By creating an IP route with blank IP address details, it becomes the default route for outgoing IP traffic. 1. Select IP Route to display existing routes. 2. Click on and select IP Route. 3. Leave the IP Address and IP Mask fields blank. 4. In the Destination field, select the WAN service. 5. Leave the Metric at default value of 1. 6. Click OK. 4. Configure the Line Channels This stage of the process differs according to the type of trunk being used. 5.
10.3.3 Remote Access The system support remote access for incoming data calls on trunks. To do remote access, an incoming call is passed through the following elements of the system configuration. · Incoming Call Route A Incoming Call Route is used to match incoming remote access calls and pass them to a RAS service as the destination. · RAS Service The RAS service defines settings relating to the data traffic methods usable with the call.
Data Routing: Examples ISDN Remote Access Example 1. Create a User The required details are: · In the User tab: Enter a Name and Password. The system is case sensitive. Remember to take care with passwords as this is a remote access link into your network. · In the Dial In tab: Ensure that Dial In On is ticked. The Firewall Profile and Time Profile are optional. 2. Create a RAS Record · In the RAS tab: Enter the same name as the user that you created earlier. Again, remember this is case sensitive. 3.
Analog Remote Access Example Configuration for a connection from an analog modem call is very similar to the ISDN example. However the system must be able to answer modem calls. This can be done in the following ways; · Analog Trunk Modem Mode On systems with an analog trunk card in the control unit, the first analog trunk can be set to answer V.32 modem calls.
Data Routing: Examples 10.3.4 WAN PPP A VoIP link across a leased line requires the Control Unit at both ends to have a Voice Compression Module installed. These provide for a fixed number of channels to use VoIP at any time. They are used to compress voice down to either 6k3 (G.723) or 8k (G.729) and provide echo cancellation. Both ends must using the same version of software and configured to use the same speed and compression. At Site A on IP address 192.168.42.1 1.
10.3.5 WAN Frame Relay To create a VoIP link via the WAN port using frame relay, the first step is to attach a WAN cable and reboot the Control Unit. After this, receive a copy of the configuration. Both ends must using the same version of software and configured to use the same speed and compression. At Site A 1.Create a WAN Service: · On the Service Tab: The Name is "FR_link". The Account Name should be "FR_Link" and all password fields (both Password and Incoming Password) should be left blank.
Chapter 11. Appendix: Locale Settings Avaya Branch Gateway Manager 10.
11. Appendix: Locale Settings The system Locale sets factors such as the default ringing tones and caller display settings. The locale also controls the default language that the system voicemail server will use for prompts. Users and incoming call routes can also be set to a locale. That locale will then override the system settings for calls to voicemail. This following table indicates locale settings used for different functions.
Appendix: Locale Settings: · All Voicemail For calls to voicemail, the locale that is passed to voicemail to determine the prompt languages to play (if available). If the required set of prompts is not available, the voicemail will fallback to another language. Embedded voicemail supports simple fallback based on the first two letters of the locale TLA. Standalone Voice Mail employs multiple fallback always ending in UK or US English (refer to the Voicemail Pro documentation).
11.1 Locale Defaults A Locale being covered in this document does not imply approvals or availability. · Tones The table below describes the different system tones. The tones used are determined by the system locale setting. Note that in some locales, the same tone sound may be used for several purposes, for example for Busy and Fast Busy may be the same. Tone Description Dial Tone Normal dial tone. Alternate Dial Tone This tone is also known as 'interrupted', 'broken' or 'stutter' dial tone.
Appendix: Locale Settings: Locale Defaults Disconnect Tone The tone used when disconnect indication is provided to an extension. Disconnect Method Indicates whether the locale uses Busy tone disconnect or disconnect clear operation on analog trunks. Display Language The default language used for messages sent to extensions. Feature Phone Clearing The locale specific action applied to digital and IP phones when the far end of a call disconnects.
11.2 Phone Display Language Sets and Fallback The phone display strings loaded by the system are based on the system Locale setting of the system. These are the languages used for display information sent to the phone from the system. Individual phones may have support for differing languages through the phones own menus.
Appendix: Locale Settings: Phone Display Language Sets and Fallback 11.3 Argentina Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (2.0/4.0) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 480+620 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 440/620 (0.25/0.25) alternating tones. Ring Tone 440+480 (1.0/3.0) on/off. Call Waiting Tone 480+620 (0.06/0.25/0.06/5.0) on/off.
11.4 Australia Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+440 Continuous. Alternate Dial Tone 350+440 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 400 (0.375/0.375) on/off. Fast Busy Tone 400 (0.375/0.375) on/off. Intercept Busy Tone 400 Continuous. Ring Tone 400+450 (0.4/0.2/0.4/2.0) on/off. Call Waiting Tone 400 (0.1/30) on/off. Number Unobtainable Tone 400 Continuous. Analog Phone Settings Ring Current Frequency 25Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Australia 11.5 Bahrain Tone Frequency (Hz) Cadence (seconds) Dial Tone 440 Continuous. Alternate Dial Tone 440 (1.0/0.5) on/off. Secondary Dial Tone 440+350 Continuous. Busy Tone 400 (0.375/0.375) on/off. Fast Busy Tone 400 (0.4/0.35/0.225/0.525) on/off. Intercept Busy Tone 400 Continuous. Ring Tone 400+450 (0.4/0.2/0.4/2.0) on/off. Call Waiting Tone 400 (0.1/30.0) on/off. Number Unobtainable Tone 425 Continuous.
11.6 Belgium - Flemish Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.5/0.5) on/off. Fast Busy Tone 425 (0.5/0.5) on/off. Intercept Busy Tone 425 (0.5/0.5) on/off. Ring Tone 425 (1.0/3.0) on/off. Call Waiting Tone 400 (0.08/0.175/0.08/10.0) on/off. Number Unobtainable Tone 425 Continuous. Analog Phone Settings Ring Current Frequency 25Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Belgium - Flemish 11.7 Belgium - French Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.5/0.5) on/off. Fast Busy Tone 425 (0.5/0.5) on/off. Intercept Busy Tone 425 (0.5/0.5) on/off. Ring Tone 425 (1.0/3.0) on/off. Call Waiting Tone 400 (0.08/0.175/0.08/10.0) on/off. Number Unobtainable Tone 425 Continuous.
11.8 Brazil Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (2.0/4.0) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.25/0.25) on/off. Fast Busy Tone 425 (0.25/0.25) on/off. Intercept Busy Tone 425 (0.1/0.1/0.1/0.1) on/off. Ring Tone 425 (1.0/4.0) on/off. Call Waiting Tone 425 (0.06/0.25/0.06/5) on/off. Number Unobtainable Tone 425 (0.25/0.25/0.75/0.25) on/off.
Appendix: Locale Settings: Brazil 11.9 Canada Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+440 Continuous. Alternate Dial Tone 350+440 (0.25/0.25) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 480+620 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 440/620 (0.25/0.25) alternating tones. Ring Tone 440+480 (2.0/4.0) on/off. Call Waiting Tone 480+620 (0.0/0.1/0.2/1200) on/off. Number Unobtainable Tone 480+620 Continuous.
11.10 Chile Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (2.0/4.0) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 480+620 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 440/620 (0.25/0.25) alternating tones. Ring Tone 480+620 (1.0/3.0) on/off. Call Waiting Tone 480+620 (0.06/0.25/0.06/5.0) on/off. Number Unobtainable Tone 480+620 Continuous.
Appendix: Locale Settings: Chile 11.11 China Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (0.4/0.04) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 440 (0.35/0.35) on/off. Fast Busy Tone 440 (0.7/0.7) on/off. Intercept Busy Tone 440 (0.1/0.1/0.1/0.1/0.1/0.1/0.4/0.4) on/off. Ring Tone 440 (1.0/4.0) on/off. Call Waiting Tone 440 (0.4/4.0) on/off. Number Unobtainable Tone 440 Continuous.
11.12 Colombia Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (2.0/4.0) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 480+620 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 440/620 (0.25/0.25 alternating tones. Ring Tone 440+480 (1.0/3.0) on/off. Call Waiting Tone 480+620 (0.06/0.25/0.06/5.0) on/off. Number Unobtainable Tone 480+620 Continuous.
Appendix: Locale Settings: Colombia 11.13 Customize On the System | System tab, the Locale can be set to Customize. This option is intended for those locales which use a mix of telephony equipment from a range of other locales. Testing and use of this locale option is entirely the responsibility of the installer. The Customize locale matches the Saudi Arabia 837 locale but with the following additional controls: · Tone Plan: Default = Tone Plan 1 The tone plan controls dial and ringing tone.
11.14 Denmark Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.25/0.25) on/off. Fast Busy Tone 425 (0.25/0.25) on/off. Intercept Busy Tone 425 (0.25/0.25) on/off. Ring Tone 425 (0.75/7.5) on/off. Call Waiting Tone 425 (0.08/10.0) on/off. Number Unobtainable Tone 425 Continuous. Analog Phone Settings Ring Current Frequency 25Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Denmark 11.15 Egypt Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone 440+350 Continuous. Busy Tone 400 (0.375/0.375) on/off. Fast Busy Tone 425+450 (0.5/0.5) on/off. Intercept Busy Tone 425+450 Continuous. Ring Tone 425+450 (2.0/1.0) on/off. Call Waiting Tone 425+450 (0.1/30.0) on/off. Number Unobtainable Tone 425+450 Continuous.
11.16 Finland Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.25/0.25) on/off. Fast Busy Tone 425 (0.25/0.25) on/off. Intercept Busy Tone 425 (0.25/0.25) on/off. Ring Tone 425 (1.0/5.0) on/off. Call Waiting Tone 425 (0.08/120.0) on/off. Number Unobtainable Tone 425 Continuous. Analog Phone Settings Ring Current Frequency 25Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Finland 11.17 France Tone Frequency (Hz) Cadence (seconds) Dial Tone 330 Continuous. Alternate Dial Tone 330 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 440 (0.5/0.5) on/off. Fast Busy Tone 440 (0.5/0.5) on/off. Intercept Busy Tone 440 (0.5/0.5) on/off. Ring Tone 440 (1.5/3.5) on/off. Call Waiting Tone 440 (0.1/8.0) on/off. Number Unobtainable Tone 440 Continuous.
11.18 Greece Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous Alternate Dial Tone 425 (0.5/1.0) on/off Secondary Dial Tone 425 (0.2/0.3/0.7/0.8) on/off Busy Tone 425 (0.3/0.3) on/off Fast Busy Tone 425 (0.15/0.15) on/off Intercept Busy Tone 425 (0.1/0.1/0.2/0.2) on/off Ring Tone 425 (1.0/4.0) on/off Call Waiting Tone 425 (0.3/8.0) on/off Number Unobtainable Tone 425 (0.1/0.2) on/off Analog Phone Settings Ring Current Frequency 25Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Greece 11.19 Germany Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 (0.16/0.16/0.16/0.16/0.16/0.8) on/off. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone 425 Continuous Busy Tone 425 (0.48/0.48) on/off. Fast Busy Tone 425 (0.48/0.48) on/off. Intercept Busy Tone 425 (0.48/0.48) on/off. Ring Tone 425 (0.945/4.05) on/off. Call Waiting Tone 425 (0.08/0.2/0.08/10) on/off. Number Unobtainable Tone 425 Continuous.
11.20 Hong Kong Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+440 Continuous. Alternate Dial Tone 350+440 (0.25/0.25) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 480+620 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 480/620 (0.25/0.25) on/off. Ring Tone 440/620 (2.0/4.0) on/off. Call Waiting Tone 480+620 (0.06/0.25/0.06/5.0) on/off. Number Unobtainable Tone 480+620 Continuous.
Appendix: Locale Settings: Hong Kong 11.21 Hungary Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.5/0.5) on/off. Fast Busy Tone 425 (0.5/0.5) on/off. Intercept Busy Tone 425 (0.5/0.5) on/off. Ring Tone 425 (1.0/4.0) on/off. Call Waiting Tone 425 (0.15/0.15/0.15/10.0) on/off. Number Unobtainable Tone 425 Continuous.
11.22 Iceland Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+450 Continuous. Alternate Dial Tone 350+450 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 400 (0.375/0.375) on/off. Fast Busy Tone 400 (0.375/0.375) on/off. Intercept Busy Tone 400 Continuous. Ring Tone 400+450 (0.4/0.2/0.4/2.0) on/off. Call Waiting Tone 400 (0.1/30.0) on/off. Number Unobtainable Tone 400 Continuous. Analog Phone Settings Ring Current Frequency 25Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Iceland 11.23 India Tone Frequency (Hz) Cadence (seconds) Dial Tone 400 Continuous. Alternate Dial Tone 400 (0.25/0.25/0.25/3.25) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 400 (0.75/0.75) on/off. Fast Busy Tone 400 (0.25/0.25) on/off. Intercept Busy Tone 400 (0.75/0.75) on/off. Ring Tone 400 (0.4/0.2/0.4/2.0) on/off. Call Waiting Tone 400 (0.2/0.1/0.2/7.5) on/off. Number Unobtainable Tone 400 (2.8/0.2) on/off.
11.24 Italy Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+425 Continuous. Alternate Dial Tone 350+425 (1.0/0.5) on/off. Secondary Dial Tone 425 (0.2/0.2/0.6/1.0) on/off. Busy Tone 400 (0.5/0.5) on/off. Fast Busy Tone 425 (0.5/0.5) on/off. Intercept Busy Tone 425 (0.5/0.5) on/off. Ring Tone 425 (1.0/4.0) on/off. Call Waiting Tone 400 (0.1/4.9) on/off. Number Unobtainable Tone 400 (0.1/0.1) on/off.
Appendix: Locale Settings: Italy 11.25 Korea Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+440 (1.0/0.25) on/off. Alternate Dial Tone 350+440 (0.25/0.25) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 480+620 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.3/0.2) on/off. Intercept Busy Tone 480+620 (0.125/0.025/0.125/1.5) on/off. Ring Tone 440+480 (1.0/2.0) on/off. Call Waiting Tone 480+620 (0.06/0.25/0.06/5.0) on/off. Number Unobtainable Tone 480+620 Continuous.
11.26 Kuwait Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone 440+350 Continuous. Busy Tone 425 (0.375/0.375) on/off. Fast Busy Tone 425 (0.25/0.25) on/off. Intercept Busy Tone 425 Continuous. Ring Tone 425 (1.0/4.0) on/off. Call Waiting Tone 425 (0.1/4.0) on/off. Number Unobtainable Tone 425 Continuous. Analog Phone Settings Ring Current Frequency 20Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Kuwait 11.27 Mexico Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (2.0/4.0) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 480+620 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 440/620 (0.25/0.25) alternating tones. Ring Tone 440+480 (1.0/3.0) on/off. Call Waiting Tone 480+620 (0.06/0.25/0.06/5.0) on/off. Number Unobtainable Tone 480+620 Continuous.
11.28 Morocco Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone 440+350 Continuous. Busy Tone 425 (0.375/0.375) on/off. Fast Busy Tone 425 (0.5/0.5) on/off. Intercept Busy Tone 425 Continuous. Ring Tone 425 (1.7/3.3) on/off. Call Waiting Tone 425 (0.1/30.0) on/off. Number Unobtainable Tone 425 Continuous. Analog Phone Settings Ring Current Frequency 20Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Morocco 11.29 Netherlands Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.48/0.48) on/off. Fast Busy Tone 425 (0.48/0.48) on/off. Intercept Busy Tone 425 (0.48/0.48) on/off. Ring Tone 425 (0.945/4.05) on/off. Call Waiting Tone 400 (0.08/10.0) on/off. Number Unobtainable Tone 425 Continuous.
11.30 New Zealand Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+350 Continuous. Alternate Dial Tone 350+350 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 400 (0.375/0.375) on/off. Fast Busy Tone 400 (0.375/0.375) on/off. Intercept Busy Tone 400 Continuous. Ring Tone 400+450 (0.4/0.2/0.4/2.0) on/off. Call Waiting Tone 400 (0.1/30.0) on/off. Number Unobtainable Tone 400 (0.075/0.1/0.075/0.1/0.075/0.1/0.075/0.4) on/off.
Appendix: Locale Settings: New Zealand 11.31 Norway Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.5/0.5) on/off. Fast Busy Tone 425 (0.5/0.5) on/off. Intercept Busy Tone 425 (0.5/0.5) on/off. Ring Tone 425 1.0/1.5/(1.0/4.0) on/off. Call Waiting Tone 425 (0.08/0.6/0.08/10.0) on/off. Number Unobtainable Tone 425 Continuous.
11.32 Oman Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone 440+350 Continuous. Busy Tone 425 (0.375/0.375) on/off. Fast Busy Tone 425 (0.4/0.35/0.225/0.525) on/off. Intercept Busy Tone 425 Continuous. Ring Tone 425 (0.4/0.2/0.4/2.0) on/off. Call Waiting Tone 425 (0.3/10.0) on/off. Number Unobtainable Tone 425 Continuous. Analog Phone Settings Ring Current Frequency 20Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Oman 11.33 Pakistan Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone 440+350 Continuous. Busy Tone 425 (0.375/0.375) on/off. Fast Busy Tone 400 (0.25/0.25) on/off. Intercept Busy Tone 400 Continuous. Ring Tone 400 (1.0/2.0) on/off. Call Waiting Tone 400 (0.1/30.0) on/off. Number Unobtainable Tone 400 Continuous.
11.34 Peru Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (2.0/4.0) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 480+620 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 440/620 (0.25/0.25) alternating tones. Ring Tone 440+480 (1.0/3.0) on/off. Call Waiting Tone 480+620 (0.06/0.25/0.06/5.0) on/off. Number Unobtainable Tone 480+620 Continuous.
Appendix: Locale Settings: Peru 11.35 Poland Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.5/0.5) on/off. Fast Busy Tone 425 (0.5/0.5) on/off. Intercept Busy Tone 425 (0.5/0.5) on/off. Ring Tone 425 (1.0/4.0) on/off. Call Waiting Tone 425 (0.15/0.15/0.15/10.0) on/off. Number Unobtainable Tone 425 Continuous.
11.36 Portugal Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+450 Continuous Alternate Dial Tone 350+450 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 400 (0.375/0.375) on/off. Fast Busy Tone 400 (0.375/0.375) on/off. Intercept Busy Tone 400 Continuous Ring Tone 400+450 (0.4/0.2/0.4/2.0) on/off. Call Waiting Tone 400 (0.1/30.0) on/off. Number Unobtainable Tone 400 Continuous Analog Phone Settings Ring Current Frequency 25Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Portugal 11.37 Qatar Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+440 Continuous. Alternate Dial Tone 350+440 (1.0/0.5) on/off. Secondary Dial Tone 440+350 Continuous. Busy Tone 400 (0.375/0.375) on/off. Fast Busy Tone 400 (0.4/0.35/0.22/0.52) on/off. Intercept Busy Tone 400 Continuous. Ring Tone 400+450 (0.38/0.25/0.38/2.0) on/off. Call Waiting Tone 400 (0.2/0.6/0.2/5.0) on/off. Number Unobtainable Tone 400 Continuous.
11.38 Russia Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 Continuous. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.35/0.35) on/off. Fast Busy Tone 425 (0.2/0.2) on/off. Intercept Busy Tone 425 (0.35/0.35) on/off. Ring Tone 425 (1.0/4.0) on/off. Call Waiting Tone 425 (0.2/5.0) on/off. Number Unobtainable Tone 425 Continuous. Analog Phone Settings Ring Current Frequency 25Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Russia 11.39 Saudi Arabia Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+440 Continuous. Alternate Dial Tone 350+440 (0.25/0.25) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 480+620 (0.25/0.25/0.25/0.25) on/off. Ring Tone 440+480 (2.0/4.0) on/off. Call Waiting Tone 480+620 (0.1/0.2/1200.0) on/off. Number Unobtainable Tone 480+620 Continuous.
11.40 Singapore Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone 440+350 Continuous. Busy Tone 425+50 (1.0/4.0) on/off. Fast Busy Tone 450 (0.5/0.5) on/off. Ring Tone 425+50 (2.0/1.0) on/off. Call Waiting Tone 400 (0.1/30.0) on/off. Number Unobtainable Tone 400 Continuous. Intercept Busy Tone Analog Phone Settings Ring Current Frequency 20Hz Minimum Flash Hook Time 0.300s Maximum Flash Hook Time 1.
Appendix: Locale Settings: Singapore 11.41 South Africa Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+450 Continuous. Alternate Dial Tone 350+450 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 400 (0.375/0.375) on/off. Fast Busy Tone 400 (0.375/0.375) on/off. Intercept Busy Tone 400 Continuous. Ring Tone 400+450 (0.4/0.2/0.4/2.0) on/off. Call Waiting Tone 400 (0.1/30.0) on/off. Number Unobtainable Tone 400 Continuous.
11.42 Spain Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.25/0.25) on/off. Fast Busy Tone 425 (0.25/0.25) on/off. Intercept Busy Tone 425 (0.25/0.25) on/off. Ring Tone 425 (1.5/3.0) on/off. Call Waiting Tone 425 (0.15/0.15/0.15/30.0) on/off. Number Unobtainable Tone 425 Continuous. Analog Phone Settings Ring Current Frequency 25Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Spain 11.43 Sweden Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.25/0.25) on/off. Fast Busy Tone 425 (0.25/0.25) on/off. Intercept Busy Tone 425 (0.25/0.25) on/off. Ring Tone 425 (1.0/5.0) on/off. Call Waiting Tone 425 (0.08/120) on/off. Number Unobtainable Tone 425 Continuous.
11.44 Switzerland Tone Frequency (Hz) Cadence (seconds) Dial Tone 425 Continuous. Alternate Dial Tone 425 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 425 (0.5/0.5) on/off. Fast Busy Tone 425 (0.5/0.5) on/off. Intercept Busy Tone 425 (0.2/0.2) on/off. Ring Tone 425 (1.0/4.0) on/off. Call Waiting Tone 425 (0.2/0.2/0.2/4.0) on/off. Number Unobtainable Tone 425 (0.2/0.2) on/off. Analog Phone Settings Ring Current Frequency 25Hz Minimum Flash Hook Time 0.
Appendix: Locale Settings: Switzerland 11.45 Taiwan Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+440 Continuous. Alternate Dial Tone 350+440 (0.1/0.1) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 480+620 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 480/620 (0.25/0.25)/(0.25/0.25) on/off. Ring Tone 440+480 (1.2/2.0) on/off. Call Waiting Tone 350+440 (0.25/0.25/0.25/5.25) on/off. Number Unobtainable Tone 480+620 Continuous.
11.46 Turkey Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+440 Continuous. Alternate Dial Tone 350+440 (0.25/0.25) on/off. Secondary Dial Tone 350+440 Continuous. Busy Tone 450 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 480+620 Continuous. Ring Tone 440+480 (2.0/4.0) on/off. Call Waiting Tone 480+620 (0.0/0.1/0.2/1200) on/off. Number Unobtainable Tone 480+620 (0.1/0.2) on/off. Analog Phone Settings Ring Current Frequency 25Hz.
Appendix: Locale Settings: Turkey 11.47 United Arab Emirates Tone Frequency (Hz) Cadence (seconds) Dial Tone 440 Continuous. Alternate Dial Tone 440 (1.0/0.5) on/off. Secondary Dial Tone 440+350 Continuous. Busy Tone 425 (0.375/0.375) on/off. Fast Busy Tone 400 (0.4/0.35/0.225/0.525) on/off. Intercept Busy Tone 400 Continuous. Ring Tone 400+450 (0.4/0.2/0.4/2.0) on/off. Call Waiting Tone 400 (0.1/30.0) on/off. Number Unobtainable Tone 400 Continuous.
11.48 United Kingdom Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+450 Continuous. Alternate Dial Tone 350+450 (1.0/0.5) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 400 (0.375/0.375) on/off. Fast Busy Tone 400 (0.375/0.375) on/off. Intercept Busy Tone 400 Continuous. Ring Tone 400+450 (0.4/0.2/0.4/2.0) on/off. Call Waiting Tone 400 (0.1/30) on/off. Number Unobtainable Tone 400 Continuous. Analog Phone Settings Ring Current Frequency 25Hz Ring Current Cadence (0.
Appendix: Locale Settings: United Kingdom 11.49 United States Tone Frequency (Hz) Cadence (seconds) Dial Tone 350+440 Continuous. Alternate Dial Tone 350+440 (0.25/0.25) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 480+620 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 440/620 (0.25/0.25) alternating tone. Ring Tone 440+480 (2.0/4.0) on/off. Call Waiting Tone 480+620 (0.0/0.1/0.2/1200) on/off. Number Unobtainable Tone 400 Continuous.
11.50 Venezuela Tone Frequency (Hz) Cadence (seconds) Dial Tone Tone 425 Continuous. Alternate Dial Tone 425 (2.0/4.0) on/off. Secondary Dial Tone Use Dial Tone. Busy Tone 480+620 (0.5/0.5) on/off. Fast Busy Tone 480+620 (0.25/0.25) on/off. Intercept Busy Tone 440/620 (0.25/0.25) alternating tone. Ring Tone 440+480 (1.0/3.0) on/off. Call Waiting Tone 480+620 (0.06/0.25/0.06/5.0) on/off. Number Unobtainable Tone 480+620 Continuous.
Chapter 12. Appendix: SMDR Avaya Branch Gateway Manager 10.
12. Appendix: SMDR The control unit is able to send SMDR (Station Message Detail Reporting) records to a specified IP address and port. Typically an SMDR record is output for each call between two parties (internal and or external) that is handled by the system. In some scenarios, for examples transfers, where a call involves multiple parties then multiple SMDR records may be output for each part of the call. See SMDR Examples 854 .
Appendix: SMDR: 12.1 SMDR Fields The SMDR output contains the following fields. Note that time values are rounded up to the nearest second. 1.Call Start Call start time in the format YYYY/MM/DD HH:MM:SS. For all transferred call segment this is the time the call was initiated, so each segment of the call has the same call start time. 2.Connected Time Duration of the connected part of the call in HH:MM:SS format. This does not include ringing, held and parked time.
Type Party Device Party Name Line T<9000+line number> Line . Other V<8000+device number> U . Unknown/Tone V8000 U1 0.0 13.Party1Name The name of the device – for an extension or agent, this is the user name. 14.Party2Device The other party for the SMDR record of this call segment. See Party1Device above. 15.Party2Name The other party for the SMDR record of this call segment. See Party1Name above. 16.
Appendix: SMDR: SMDR Fields 30.External Targeted Number This field is used for forwarded, Incoming Call Route targeted and mobile twin calls to an external line. It shows the external number called by the system as a result of the off switch targeting where as other called fields give the original number dialled. Avaya Branch Gateway Manager 10.
12.2 SMDR Examples The following are examples of system SMDR records for common call scenarios. Basic Examples Lost incoming Call In this record, the Call duration is zero and the Continuation field is 0, indicating that the call was never connected. The Ring Time shows that it rang for 9 seconds before ending. 2008/06/28 09:28:41,00:00:00,9,8004206,I,4324,4324,,0,1000014155,0,E4324,Joe Bloggs,T9161,LINE 5.1,0,0,,,,,,,,,,,,, Call Answered by Voicemail In this example, 215 has made a call to 211.
Appendix: SMDR: SMDR Examples Conference Using Conference Add Short Code In this example 2101 has made a call and put put it on hold (record 2), then made another call and put it on hold (record 1) and then dialled the default short code *47 to conference all their held calls (record 3). The records for the first two calls have the Continuation field set as 1 indicating that the calls continued in further records.
Call Pickup The first record shows a call from 2122 to 2124 with a Connected Time of zero but a Ring Time of 8. The Continuation field indicates that the call has further records. The second record has the same Call ID but the Party 2 Device and Party 2 Name details show that the call has been answered by 2121.
Appendix: SMDR: SMDR Examples Transferred Manually In this example the internal user transfers a call to an external number. The External Targeting Cause in the first record indicates that this external call is the result of a user (U) transfer proposal (XfP) call. The Continuation field indicates that another record with the same Call ID will be output. The additional records are output after the transferred call is completed. The first relates to the initial call prior.
Mobile Twinned Call Answered at the Mobile Twin This is the same scenario as the example above except that the call is answered at the external mobile twinning destination. Unlike the previous example the external call record has a non-zero Call Time showing that the call was also answered externally. … 16:17:04,00:00:06,9,,O,9416,9416,,0,1000026,0,E203,Extn203,T9005,Line 5.
Appendix: SMDR: SMDR Examples Avaya Branch Gateway Manager 10.
Index A AA 402 AA Number 402 Abbreviated Dial 555, 556, 558, 559 Abbreviated Dial Pause 555 Abbreviated Dial Program 556 Abbreviated Dial Stop 556 Abbreviated Ring 281 Absnt 492, 629 Accept Collect Calls 281 access 65, 100 Hunt Group Messages 322 Queue 313 Service 90 Service User's 89 Specific Voicemail Pro Module 503 Time 112 Access Control 65 access greeting 322 Access Mode 788 Access Type 112 according Client 78 Client Certificate Checks 78 Country 213 account 10 76 required unlock 45 Service User 45 tim
Index Alarm Ignore 313 SMTP email 175 Syslog 175 Alarm Destinations Editing 175 Alarm Station 423 Alarms Sub-Tab Settings 175 A-Law 491 A-LAW systems 405 A-Law/Mu-Law 806 Alerting Line 683, 685 All 452 cancels forwarding 478 Certificate Stores 65 All Call Appearances Alerting 675 All Calls 715 all dialing 335 All Forwarding 449, 577 All Group Settings 213 All Internet Traffic Routing 372 All Programs 14 allocating IP 56 TEI's 202 Allow 204 ringback 737 Allow Analog Trunk Trunk Connect 198 Allow Direct Media
Appearances Alerting 675 Appearances Example Collapsing 687 Appearances Treated 663, 672 appears 124 Appendix 65 appendix covers 65 Application Controls 80 Application Options 533 Application Support list 80 Applications 12 Applications Controls 80 applied during 271 applies even 730 Apply 127 Call Cost Markup 715 appropriate 394 System Locale 258 appropriate greeting 402 Aquire 558 ara 837 Argentina 206 arp receiving 376 ARP request 376 ARS 405, 698 return 464 take 407 ARS Features 405 ARS finds 405 ARS fo
Index Avaya H.323 IP 145 Avaya Intuity Audix 155 Avaya IP 267 shows 125 Avaya IP DECT 234, 267 Avaya IP DECT Mobility Manager 234 Avaya phones 507, 585, 598, 612, 616, 628, 653 Avaya T3 Classic 631 Avaya Technical Support 159 Avaya use 579 Avaya Voice Priority Processor 140 avpots16.
Broadcast 479 broadcast address LAN 786 Broadcast IP Address 102 Browser/FTP 338 browsing internet 786 Non-Standard 372 Non-Standard Port Numbers 372 BT Relate 1100 258 BT SIN 227 conforming 258 BT X25 159 BtnVu 637 Bundled/Multilinked 347 Busy 466, 567, 575, 598, 606, 628, 631, 632, 644, 649, 657, 666, 667, 691, 698 exchange gives 159 set 271 Turning 440 Busy Controls 751 Busy Not Available 776 Busy on Held 567, 691 busy signal 159 user 440, 567 Busy Subscriber 206 Busy Tone 330 Busy Tone Detection 140 Bus
Index Call Pickup Group 445, 574 Call Pickup Line 445 Call Pickup Members 446, 574 Call Pickup User 446 Call Presentation 304 Call Proceeding 426 Call Progress 431 call progress signalling 288 Call Put on Hold 661 Call Queue 575 Call Queued 447 Call Record 439 Call Redirection During Fallback 319 Call Route 353 Call Sequence corresponding 496 Call Status 80, 692 Call Steal 447 Call Steal user 558 Call Tagging 733 Call Taken Off Hold 661, 662 call timing 688 Call Tracing User 728 Call Types Blocked 745 Call
CCC consume 774 CCP 347 CD Insert 12 open 12 CDR receiving 181 type 181 CDR Records internal 181 CE 777 Center Mode 519 Central System 310 Centralized Voicemail 198 Centrex service 601 Centrex Transfer 601 complete 765 performs 765 Centrex Transfer Button Operation 765 Centrex Transfer Operation Analog Extensions 765 Centrex Transfer Short Code Operation 765 cer 78 Certificate Authorities 65 Certificate Checks 65 Certificate Import Wizard 65 Certificate MMC 65 Certificate Offered 104 certificate store 104 a
Index Client 338 according 78 Client Certificate Checks 65 according 78 Client Certificate Store 78 Clock Quality 225 Close Configuration 98 Close Configuration/Security Settings After 100 Close Configuration/Security Settings After Send 100 Close Security Settings 130 closing 130 ClrCW 451, 579 cn 171 CnfMM 585 CnfRV 454, 585 CnLWC 577 Cnslt 587 CO 220 Code 204 Telephone Number 52 Code Features 295 Code Field Characters 426 Code Fields 407 Code Matching Examples 433 Code Toggles 479 codes beginning 431 Col
Connecting Avaya Branch Gateway 51 WAN 356 Consult 587 consume 220 CCC 774 Contact Internet 372 Windows 2000 Server Active Directory 171 Contact Information 45 Contact Information Check 45 ContactStore 353 contains 338 Continue 330 continue dialing 429 continue ringing 281 control outgoing external 135 Control Unit IP Address 794 selected 145 timeouts 338 type 786 Voice Compression Card 793 Control Unit checks 338 Control Unit IP including 145 Control Unit on LAN1 145 Control Unit's LAN1 56 converts 225 URL
Index dB 217 D-channels 220 DCLIs 794 DCW 457, 589 DDI 693 De 358 deciding TEI's 206 DECT 267 DECT Line ID 267 de-DE 18 Dedicated T1/PRI ISP Link 788 Default All button Advanced 213 Default Blank Call Routes 350 default companding 436 Default Currency 159 Default Message Waiting 829 Default No Answer Time 159, 696 Default Ring 739 selecting 496 default ringing tones 739 Default Route 788 Default Service 65 Default Value 788 occurs 354 DefaultRing 281 defaults MWI 260 define 338 ICLID 790 WAN 344 Definity 46
Dial Video 594 Dial/0 426 DialCW 457 DialDirect 458 DialDirectHotLine 458, 698 DialExtn 459 DialIn 344 DialIn window 344 DialInclusion 460 Dialing Prefix 366 Adding 730 Dialling Timeout 798 DialP 462, 592 DialPhysicalExtnByNumber 462 DialPhysicalNumberByID 462 DID 204, 693 result 446, 574 DID call 446 DID routing 127 differing Telephone Number 407 DiffServ 145 DiffServ Code Point 145 DiffServ QoS 139 DiffServe 145 Digital Station 258 Digital Station V2 137 Digital56 361 Digital64 788 Digits 204 Matching 198
Index Do Not Disturb 462, 577, 592, 597, 598, 620, 628, 657, 663, 667, 672 selecting 331 Do Not Disturb Exception 466 Do Not Disturb Exception Add 466, 597 Do Not Disturb Exception Delete 466, 597 Do Not Disturb Exception list 466, 597, 598, 628, 657, 667 Do Not Disturb Exception Numbers List 466 Do Not Disturb On 598 Domain Name Server 154 Domain Name Server addresses 139 Domain Name System 171 Done 319 Dongle Serial Number 140 DoNotDisturbExceptionAdd 466 DoNotDisturbExceptionDel 466 DoNotDisturbOff 467 D
Enable SNMP 175 Enable Time Server 100 deselecting 140 Enable User AOC Display 715 Enable VoIP sets 303 enable/disable 347, 616 Enabled' Software 291 Encapsulated Security Payload 388 Encryption 782 End 338, 369 Conferences 766 Outgoing 217 PVC 358 VoIP 426 end prompts 361 End Time 369 Ends Overlap Send 231 eng 796 English 796 Enhanced 215 Enhanced Called Party Number 215 Enquiry Call Between Colleagues 662 ens 839 Entry 155 Deleting 32 Editing 32 Validating 32 Entry List 369 Entry Types 26 entry/exit 695 e
Index Extension 204 User Restriction/Rights 52 Extension | Analog 260 Extension | Extn 422 extension clicking 26 Extension ID 354 Extension ID's 423 extension initiating 472 Extension List 331 Ann 333 Extension Number 452 extension number sharing 231 extension number specified 472 Extension Number*Login Code 469 extension specified 459 Extension*Login Code 469 extension/VCM 51 Extensions Renumber 126 External 466 automatic recording 325 External Call 743 Making 366 External Calls 657, 688 External Dialing P
Follow Me 462, 577, 592, 602, 603, 620, 629, 657, 667 set 473 Follow Me Calls 756 Follow Me Controls 747 Follow Me Here 472, 602 Follow Me Here Cancel 473, 602 Follow Me Number 747 Follow Me To 603, 747 Follow Me To Number set 747 following firewall 372 Incoming Call Route 238 Microsoft 104 T1 788 T1 PRI 788 toolbars 26 Follow-Me 798 FollowMeHere 472 FollowMeHereCancel 473 FollowMeTo 473 FollowTo 747 FolTo 473, 603 Force Authorization 335 Force Authorization Code 335 Force New Password 93 Forced Account Cod
Index FwBOn 476, 606 Fwd 753 Fwd on Busy 751 Fwd on No Answer 753 FwdH 331, 603 FwdNo 475, 604 FwdOf 449, 577 FwNOf 477, 606 FwNOff 606 FwNOn 477, 607 FwUOf 478, 607 FwUOn 478, 608 G G.729 Simple 234 G.729 VoIP 358 G.
HGNS 452, 581, 631 HGNS+200 631 HGOS 452, 582, 632 HGOS+200 632 Hgroupname adding 322 hide 26 Error Pane 124 Group Pane 124 ID's 387 Navigation Pane 124 Service Base TCP Port 100 Hide Options 303 Hide/Show Error Pane 36 Hide/Show Group Pane 36 Hide/Show Navigation Pane 36 HIDE_CALL_STATE 279 Hiding 384 Hiding Panes 36 Hiding Toolbars 26 High 78, 407 Minimum Password Complexity 65 HMAC MD5 388 HMAC SHA 388 HMain 279 Hold 453, 612, 613, 624, 653, 655, 656, 657, 658, 661, 662, 663, 664, 668, 671, 673, 674, 675
Index Idle Line Preference 674, 675, 678, 681, 683, 685, 687, 688, 696 Idle Line Preference Example 675 Idle Period 338 ID's hide 387 ie 598, 628, 678 IGMP 371 Ignore 225 Alarm 313 ignored during 52 ignored during import 52 IKE 387 IKE Policies 387 IMM Dial Guard Outgoing 217 Immediate 145, 653, 696 set 683, 690 Immediate Overflow 316 immediate ringing 281 Implementation 65 Import/Export 122 IMPORTANT 11 Importing 122 Settings 52 IMS 322 In Firewall Profile 290 In On 775 In Queue Alarm 313 In Queue Threshol
Internet Service Provider 154 Internet Time 140 Internet” 788 Internet01 337 internet-based 65 interoperate 171 interoperation 171 intra-switch 181 Intru 441, 568 Intruded 558, 568, 569, 590, 620, 671, 688, 696, 731 Intuity 503, 646, 648 Intuity Emulation 503 Intuity Emulation Mailbox Mode 322 Intuity Emulation Mode 503 Inwats 224 IP 102, 453 allocates 56 creating 788 Except 258 includes 786 names 154 obtain 145 outgoing 788 uses 56 IP 500 500 IP Address 154, 440 255.255.255.
Index K KAR 596 Karl 596 KBytes 388 keep-alives 145 Kerberos 171 Key Server 12 Key Server PC 140 Keys 293 Know System Discovery 47 Know Units 47 Known System Discovery 47 Known Systems CSV file 47 Known Units File 47, 101 kor 823 Korea 212 Korean 796 L L2TP 385 numbers 384 originating 383 L2TP peer 383 L2TP|Tunnel 384 Label 153 Line Appearance 197 Lamp Manual 197, 562, 566, 587, 617 Lamp Operation 653, 692, 731 Lamp Operation Manual 507 LAN address 786 broadcast address 786 PC 786 LAN1 140, 145 LAN2 153 s
Line Preference Order Ringing 678, 690 Line Programming Outgoing 698 Line Renumber 126, 697 Line Retrieved 671 Line Reversal 738 Line Settings 697 Line Signaling 220 Line Signaling Timers 213 Line SubType 220 line/trunk 217 Linear 329 Linear Group 329 lines 127 Charge Unit 715 lines dedicated 198 LINEx.
Index making DNS 372 External Calls 366 SIP 245 Manager 507, 692, 696 mandatory recording 155 Mandatory Voice Recording 155 Manual 319 manual editing 104 Manual Exclude 618 Manual Recording Mailbox 291 Manual Renumbering 697 Manual Transfer 757 Manual Transfer Methods 757 Manually Controlling Service State 319 Manually Entered Options 354 Manually Setting System Time 702 mask 145 IP Address 376 match 596, 642 CLI 597 Match Data 372 match exists 429 Match Length 372 Match Mask 372 Match Offset 372 matches 65
Minimum Password Complexity 65, 76 Low 65 Medium 65 Minimum Password Length 65, 93 Minimum Security 84 Minimum Width 260 Mins 342 minute 342 Miscellaneous 577, 601, 612, 618, 619, 625 misconfiguration 32 Missed 385 MMC 65 Mobile 369 set 295 Mobile Direct Access 705 Mobile Twinned Call Pickup 295 Mobile Twinning 369 Calling Party Information 182 Send Original Part Information 182 Send Original Party Information 182 mobile twinning destination 295 Mobile Twinning license 497 mobile twinning number 497 Mobile
Index NET2 12 NetBIOS Dropping 372 Netherlands 827 Network 342 set 225 network address 171 services 340 Network Address Translation 786 Network Selection 223 Network Selection table 223 number 224 Network Time Protocol 702 Network Tone 407 Network Topology Settings 145 Networking Features 440 NetworkMgmt 357 New Configuration Creating 51 New Entry 54 Adding 32 New WAN Service Create 788 New Zealand 279 New/Delete 89 News Transfer Protocol 371 Next 330 Next Available Members 288 Next Entry 32 NI2 220 NIC 102
O objectClass 171 Obtain 171 IP 145 IP Address Automatically 790 Occasional Hot Desking 775 occurs 155 Default Value 354 OCSeq 498, 635 Off Software 696 Software Level 696 Off Hook 521, 522, 619, 747 Off Hook Station 484, 619 offer Manager 104 Offer Server Certificate 78 Offhook Station 281 Off-Hook Timer 433 OffHookStation 484 offline 51 send 106 offline editing 52 offline/created 55 Offset 372 Off-Switch 743 Off-Switch Forwarding Restrictions 743 Off-Switch Transfer Restrictions 758 OHStn 619 On Hold 517,
Index Over 338 Taking 447 Overflow 313, 316 Overflow Calls 313 Overflow Group List 310 Overflow Groups 330 Overflow Time 331 groups 310 Overview Data Routing 786 Manager 11 Security Settings 59 P P917325559876 279 pagemsg3.
plan ISDN 426 Play Configuration Menu 753 Play List 779 plk 833 Point 206 Multipoint 202 Multi-Point 206 Point Protocol 361 sharing 206 Point Protocol Point 361 Point Tunneling Protocol 371 points 338 Base specifies 171 NT 154 Point-to-Multipoint sharing 202 Point-to-Point 347 Point-to-Point Protocol 347 Poland 738 Polling Verification Timer 360 POP3 371 Port 100 Port Number 145 Port Restricted Cone NAT 145 Port Restricted NAT's 145 Portugal 834 Portuguese 796 position Changing 32 Manager toolbars 26 Post D
Index Proxy ARP 376 ptb 806 pt-Br 18 ptg 834 Public Port 145 Pulse Dial Break Outgoing 217 Pulse Dial Inter Digit Outgoing 217 Pulse Dial Make Outgoing 217 Pulse Dial Pause Outgoing 217 Pulse Dialing 213 Pulse Metering Bit 213 Pulse Width Off 198 Pulse Width On 198 Putonghua 796 PVC ends 358 Q Q.931 500 Q.931 Hold 612 uses 480 Q.
Recording Hunt Group Announcement 326 Mailbox 353 Name 402 Recording Name 402 Recurrence Pattern 369 red/green 198 Reduce Bandwidth 338 Reduce BW Threshold 338 Refer SHOW_LINEID_NOT_OUTSIDE 673 Refresh 342 Refresh Time Binding 145 Regedt32.
Index Revalidating Configuration Settings 34 RFC 1490 358 RFC 3164 175 RFC1490 set 358 RFC1490+FRF12 357 RFC1779 171 RFC2254 171 RFC2474 145 RFC2507 347 RFC2508 347 RFC2509 347 RFT 12 Ride Call 736 right 65 Group Pane 124 Right clicking 47 Rights Group Membership 61 Rights Groups existing 64 set 93 Rights Membership 398 Rights View 24 Rights/User Restrictions Short Codes 425 Ring Back Sequence 281 Ring Back When Free 159, 577, 625 sets 737 Ring Delay 281, 562, 566, 587, 616, 617, 653, 672, 678, 683, 685, 69
Sales call 333 Open 333 Sales Hours 333 Saudi Arabia 738 Save 130 Configuration 54 Configuration onto PC 54 Configuration Received 54 Save As 65 Save Configuration 100 Save Configuration As 54 Save Configuration File After Load 100 Save File As dialog 98 Save In 65 Saving Security Settings 130 Saving Sent Configurations 54 SBC 145 scan 98 WAN3 256 SCN 629, 653, 692 SCN User Extension 230 Screen Pop 303 Screen Pop Options 303 SDN 224 SDP 145 Search Base 171 Search Filter 171 SEC 371 Second Call 655, 660, 681
Index Send Original Party Information Mobile Twinning 182 send outgoing SIP 239 send recurring 145 sender address 175 Sequential 145 calls 603 Sequential Group 329 Serial 100 Serial Communication Enable Port 100 Serial Number 140 Series 51 Series IP 145 Series IP Phones 262 Series/4400 Series 836 Series/5400 Series 836 Series/5600 Series 836 Server 338 set 790 Server Certificate 78 Server IP Address 702 server PC's 175 Server Port 171 Server Private Key 78 server providing 140 Server Requires Authentication
setting stops user 758 Settings 204, 653, 657, 663, 667, 672, 683, 690, 691, 692, 693, 695, 696, 697 Exporting 52 Importing 52 settings control call 663, 667 settings cover 78 settings including 697 Setup 453 Set-up Packet 426 setup signalling 206 setup.
Index SoftConsole's Send Message 281 Software 460, 696 Software Level 330, 460 software running on 256 Sorting List 109 Source 225 source address tunnel 383 Source Number 691 Source Numbers 691, 696 SourceNumbers 743 South Africa 839 SP2 12 SP4 12 Spain 840 Spanish 796 Speak ETA 326 Speak Position 326 SPEAKER 479 Paging 260 pressing 675 SPEAKER button 258 Speakerphone 258 Special 335 Special Access 220 special meaning 426 Specific Mailbox Record Message 503 Specific Option Number 145 Specific tab 779 Specif
Symmetric NAT 145 Sync PPP 588, 589, 594 set 361 SyncFrameRelay 794 synchronization 225 Synchronize 22 Synchronize Calls 326 SyncPPP 788 Syslog alarms 175 Syslog Reporting 175 System 507, 508, 517, 530, 531, 565, 569, 571, 572, 573, 585, 593, 596, 597, 604, 605, 613, 622, 623, 627, 632, 633, 635, 642 System | Telephony 683, 695, 696 System Alarms Enabling 175 system attempts 347 System Currency Set 715 System Defaults 739 System Details 78 System Discovery 78 system during upgrade 109 System Locale 271 appr
Index terminate 385 LDAP 171 Test Number 220 Test SIP 145 Text Labels 562, 588, 644 Textphone 796 TFTP 80 TFTP Configuration Write 80 TFTP Log 125 TFTP Log window 125 TFTP Server 234 TFTP Server IP Address 140 This configuration 51 Those toolbars 124 Though Manager 21 Tick SNMP Enabled 175 TIE 217 Tie Automatic 213 Tie Delay Dial 213 Tie Immediate Start 213 Tie Wink Start 213 til 492 TIME 371, 581, 582, 607, 627, 631, 632, 634, 636 Access 112 Day 639, 702 Time Constant 358 Time Entries 369 Time Entry 369 Ti
Turning Busy 440 Turns CRC 220 Twin 653, 674, 683, 691 Twin Bridge Appearances 295 Twin Coverage Appearances 295 Twin Line Appearances 295 Twinned Call Pickup 295 Twinned Calls 182 Maximum Number 295 Twinned Handset 295 Twinned Line/Bridge/Coverage Appearances 653 Twinned Mobile Number 295 twinning 182 Destination 295 on/off 642 Time Profile 295 Type 295 Twinning action 295 Twinning tab 295 Twinning Type 295 Tx 217 Tx Gain 217 type 330 Avaya Branch Gateway 51 CDR 181 Control Unit 786 NAT 145 NAT/Firewall 14
Index Use Elsewhere 657, 658, 660, 661, 662, 664, 670, 672, 673, 687, 688 Use External Music 159 selecting 740 Use External Music on Hold 159 Use Here 658, 664, 668, 673, 688 Use Hiding 384 Use Network Topology 239 Use Network Topology Info 239 Use Port 153 Use System Defaults 260 Use User Data set 306 User | Button Programming tab 702 User Answers Call 681 Covering 666 User A's 473 user attempts set 758 User Button Enabling 702 User Call Barring 407 User Call Waiting 735 User Data 245 User dialing 335 User
Visual Preferences 32 selecting 103 Visual Voice 279, 646 VJ 361 VLAN routing 234 sets 234 VLAN ID 234 VLAN marking 234 VM 80 VM Lite 796 VM Pro 80 VM Pro Password 80 VM Ringback 753 VM_TRUNCATE_TIME adding 279 VMCol 503, 648 VMOff 504, 649 VMOn 504, 649 VMRB 505, 650, 651 Voice 353 Voice Call 361 Voice Channels 225 Voice Compression Card Control Unit 793 Voice Compression Channels 766 Voice Mail Lite 12 Voice Networking 231 Voice Payload Size 231 Voice Recording 369 Voice Recording Library 353 voice record
Index WAN Port Using Frame Relay 794 WAN Port Using PPP 793 WAN PPP 788 WAN PPP link 788 WAN Service Create 794 WAN_MODE_OVERRIDE 279 WAN3 137 excluding 51 scan 256 WAN3 10/100 137 WANPort 793 WanPort Tab 794 WARNING 65 WARNINGS 777 Wats 224 wav 322 WAV file 402 Week 369 Weekly 369 Weekly Time Pattern 369 When Free 739 Widths 30 WiFi 295 Window Size 36 Windows 385 Create 18 Windows 2000 12 Windows 2000 Professional 12 Windows 2000 Server 171 Windows 2000 Server Active Directory Contacts 171 Windows 2003 SBS
Avaya Branch Gateway Manager 10.
Performance figures and data quoted in this document are typical, and must be specifically confirmed in writing by Avaya before they become applicable to any particular order or contract. The company reserves the right to make alterations or amendments to the detailed specifications at its discretion. The publication of information in this document does not imply freedom from patent or other protective rights of Avaya or others.
