Web Manager: Configuration Menus |
User |
This menu displays a list of all the phone user extensions supported by the system.
Phone User List
This table lists all the extension users on the system. For any user, the View Details button can be clicked to access the user's Details.
The list includes phantom extensions, that is user extensions that do not have a matching physical extension port. These are indicated by a # after the extension number. The system automatically creates a user entry for all users that it could support, regardless of the number of actual extensions.
• | Name The extension user name. |
• | Extension The extension number. A # indicates a phantom extension. |
• | Groups The groups to which the user belongs. These can be edited through the Groups menu. |
This menu is accessed by clicking on View Details in the Phone User List. If shows specific settings for an individual telephone user.
The following settings are shown in this panel:
• | Name: Default = Blank. Phone Based Admin = Yes. Use this field to enter the extension user's full name. The recommended format is <first name><space><last name>. When set, the Name is used for display by phones during calls and within these menus, otherwise ExtnXXX is shown. Only alphanumeric characters and spaces are supported in this field. Do not use punctuation characters such as #, ?, /, -, _ , ^, > and ,. The entry in this field should not start with a space or number. The name is also used by the auto attendant Dial by Name function. |
• | Extension: Information field, not editable. This is the extension number of the user. |
• | Email: Default = Blank. When the user has a new message they can be emailed with an alert or a copy of the message. This is called voicemail email. Use this field to enter their email address in the format name@domain. This option requires the system to have been configured with SMTP server settings. |
• | Calling Line Identity: Default = Blank. This setting in only available on PBX mode systems. Where supported by the line provider, the value is sent on outgoing calls. This setting is not used with analog or SIP trunks. |
• | Changing the calling party number may not be supported by the line provider or may be an additional chargeable service. It will also be subject to restrictions on what numbers can be used. It is normally a requirement that the calling party number used must be a valid number for return calls to the same trunk. Use of an invalid number may cause the call to be dropped or the number to be replaced by a default value. |
• | Call Forwarding: Default = No. If selected, the user is able to forward calls to external numbers. |
• | Give System Access: Default = No. This setting can only be changed when logged in using the BusinessPartner account. It is greyed out for other accounts. |
• | If changed to Yes, a IP Office Web Manager service user account for the user is automatically created in the Service Users menu. The name used for the user's account is ExtnXX where XX is the extension number and the default password is password. These can be changed through the Service Users menu if necessary. |
• | If the control is already set to Yes, it indicated that a service user account for IP Office Web Manager and associated with the extension already exists. |
• | Changing the setting to No will delete the associated service user account. |
The following settings are shown in this panel:
• | Automatic VMS Cover: Default = Not Assigned. Phone Based Admin = Yes. If Assigned, voicemail is used to answer calls to the user that have rung for the VMS Cover Ring time. This setting is ignored for any extension configured as a loudspeaker paging extension. |
• | Voicemail Code: Default = Blank, Range = Blank or 1 to 15 digits. Phone Based Admin = Yes. This code is used to control access to the user's mailbox to collect messages. The mailbox user can change the code themselves after they enter their mailbox. |
• | Send to Email: Default = Off. This setting is used if an email address for the user has been set above and the system is configured with voicemail email operation. It sets whether the user receives an email when they have a new voicemail message. |
• | Off Switches off the use of email for new message alerts. |
• | Copy Send an email to the user's email address with the voicemail message attached. The method leaves the original message in the user's voicemail mailbox. |
• | Forward Send an email to the user's email address with the voicemail message attached. This method deletes the original message from the user's voicemail mailbox |
• | Alert Send an email alert about the new message but do not attach the message to the email. |
The following settings are shown in this panel:
• | List in Directory: Default = Off If selected, the user is not included in the directory of users displayed on phones. |
• | Calls Barred: Default = Off. Phone Based Admin = Yes. If selected, the extension user cannot make any outgoing external calls except to numbers in the Emergency Numbers List and any Allowed Lists of which they are a member. |
• | Language: Phone Based Admin = Yes. The language entered here will affect the language of prompts displayed on the user's extension and the prompts played to the user when they access their voicemail mailbox. Possible languages are: |
• | Arabic, Brazilian Portuguese, Canadian French, Cantonese, Danish, Dutch, Finnish, French, German, Italian, Korean, Mandarin, Norwegian, Portuguese, Russian, Spanish, Spanish (Argentinean), Spanish (Latin), Spanish (Mexican), Swedish, UK English, US English. |
This menu allows you to see and change a user's current do not disturb status and to edit their do not disturb exception numbers. Users can switch do not disturb on/off using a programmed key on their phone or an option in their phone's menus.
Do not disturb prevents the user from receiving calls.
• | Only calls from numbers in the user's Do Not Disturb Exceptions list are treated normally. |
• | The user is not included in hunt group and page calls. |
• | Calls direct to the user's extension number hear busy tone or are diverted to voicemail if enabled. |
• | All the users call forwarding, follow me and call coverage settings are ignored. |
This menu is accessed by selecting User in the menu bar, selecting a user and clicking View Details and then clicking on edit icon in the Do Not Disturb Exceptions panel.
• | Select User Select the user whose current do not disturb settings are displayed. |
• | Do Not Disturb: Default = Off When checked the user's extension is considered busy, except for calls coming from sources listed in their Do Not Disturb Exception List. When a user has do not disturb in use, their normal extension will give alternate dial tone when off hook. Users with DND on are indicated as 'busy' on any BLF indicators set to that user. |
• | Calls to a hunt group of which the user is a member do not use the Do Not Disturb Exceptions list. |
Most Avaya phones have buttons to which functions can be assigned. For some phones, additional buttons can also be added by attaching a button module to the phone.
Default Buttons and Button Numbering
The default button assignment depends on whether the system's Mode is set as Key or PBX.
• | Key Mode |
• | 01-02: Intercom Buttons The first two buttons are used as Intercom 1 and Intercom 2 buttons for internal calls. This function is automatically assigned to the buttons by the system and cannot be overridden by the system administrator or extension user. |
• | 03+: Line Buttons Buttons 03 and upwards up to the system's Number of Lines setting are used as line appearance buttons for external calls. These cannot be overridden by the extension user. |
• | Other Buttons Any additional buttons can be used for additional functions. These buttons can be programmed by the system administrator and, for some functions, the extension user. |
• | Button Numbering All buttons are numbered from 01, from left to right, starting from the bottom row up. |
• | PBX Mode |
• | 01-03 (ETR 01-02): Call Appearance Buttons The first three buttons (two only on ETR phones) are used call appearance buttons for making and answering calls. They can be used for both internal and external calls. This function is automatically assigned to the buttons by the system and cannot be overridden by the system administrator or extension user. |
• | Other Buttons Any additional buttons can be used for additional functions. These buttons can be programmed by the system administrator and, for some functions, the extension user. |
• | Button Numbering All buttons are numbered from 01, from left to right, starting from the bottom row up. However for 1400, 9400 and 9500 Series telephones, buttons are numbered from 01 from left to right, starting from the top row downwards. |
The menu can operate in either of two ways, depending on whether the phone type is known or not. If the phone type is known, for 1400 Series phones a picture of the phone is used. If the phone type is not known and for non-1400 Series phones, a list of buttons is used.
Program Buttons
This table displays the list of features programmed on each of the user's buttons.
• | Select Handset If the type of telephone connected to the user's extension is known, it is shown here and the menu displays a picture of the phone buttons. If the telephone type is not known, the field display Default and a list of the current button settings. You can use the selector to choose whether you want to program the buttons using the picture or list mode. |
• | Button No The button to which the feature is programmed. The position of the button will vary depending on the type of phone. |
• | Label If the phone displays text labels next to each button, you can enter the text that should be displayed. To enter the label, click on the label space after having selected the action for the button. |
• | Action: Phone Based Admin = Yes. This is the action performed by the button when pressed. To select the action place your cursor in the box, right click and select Assign a Feature from the drop menu. This will display a menu from which you can select the feature required. |
• | Action Data For some actions, when selecting the action you are asked to enter action data. |
This table displays the list of features programmed on each of the user's buttons.
• | Select Handset If the type of telephone connected to the user's extension is known, it is shown here and the menu displays a picture of the phone buttons. If the telephone type is not known, the field display Default and a list of the current button settings. You can use the selector to choose whether you want to program the buttons using the picture or list mode. |
• | Button No The button to which the feature is programmed. The position of the button will vary depending on the type of phone. |
• | Label If the phone displays text labels next to each button, you can enter the text that should be displayed. To enter the label, click on the label space after having selected the action for the button. |
• | Action: Phone Based Admin = Yes. This is the action performed by the button when pressed. To select the action place your cursor in the box, right click and select Assign a Feature from the drop menu. This will display a menu from which you can select the feature required. |
• | Action Data For some actions, when selecting the action you are asked to enter action data. |
This panel displays the setting of the currently selected button. To change the currently selected button, click on a button on the telephone picture or click on a row in the list of buttons.
To change the buttons action, click on the Assign Feature button. For a summary of the possible features, see Programming Features, System Features and Line Assignment.
Automatic line selection is used to select which available line is used when the extension goes off hook to make a call without the user first pressing a specific line or intercom button, for example if the user just lifts the handset or presses the speaker button. By default all analog line buttons (lowest to highest) and the two intercom buttons are used in that order.
• | Modify ALS Programming: Default = Off. Phone Based Admin = Yes. If Modify ALS Programming is selected, the order of line selection is displayed and can be edited. |
This menu allows a range of individual functions to be assigned to the button.
Making Calls
• | Auto Dial - Outside: Action Data = Telephone number to dial. A button set to this feature dials the stored number using the first available line appearance in the user's automatic line selection setting. |
• | Auto Dial - ICM: Action Data = User extension number. A button set to this function can be used to make an intercom call to the configured extension. It will also indicate when that user is idle or active. |
• | Auto Dial - ICM Page: Action Data =User extension number. A button set to this function can be used to page the configured extension. |
• | Group Calling - Page: Action Data = Calling group 1 to 4 A button set to this function can be used to make a page call to the available members of the configured calling group. |
• | Group Calling - Ring: Action Data = Calling group 1 to 4. A button set to this function can be used to make a call to the available members of the configured calling group. |
• | Group Hunting - Page: Action Data = Hunt group 1 to 6. A button set to this function can be used to make a page call to the available members of the configured hunt group. |
• | Group Hunting - Ring: Action Data = Hunt group 1 to 6. A button set to this function can be used to make a call to the available members of the configured hunt group. |
• | Last Number Redial: Action Data = None. A button set to this function redials the last outgoing external number dialed by the user. |
• | Loudspeaker Paging: Action Data = None A button set to this functions makes a page call to the system's designated loudspeaker extension port. |
• | Save Number Redial: Action Data = None. A button set to this function allows the user to save the number dialed during a call and to redial that number when idle. This can be used when the number dialed does not answer. |
• | Simultaneous Page: Action Data = None. A button set to this function allows the user to make a page call to both the loudspeaker extension and the extensions in first calling group, 71. |
• | Hot Dial: Action Data = None. A button set to this function allows the user to turns hot dialing on or off. When on, the extension user is able to begin dialing without going off-hook. For ETR extensions hot dial is off by default. For DS and TCM digital stations, hot dial is on by default and cannot be changed. |
Answering Calls
• | Call Log: Action Data = None. A button set to this function allows the user to access the system call log. The user must also be one of the 3 extensions configured for Log All Caller ID Calls for Users. |
• | Call Pickup: Action Data = Extension number. A button set to this function performs a call pickup from the target extension. If the target has parked calls, a parked call is retrieved in preference to any ring call at the target. Extension users can park calls by transferring the call their own extension number. Parked calls will recall after 3 minutes. |
• | Caller ID Inspect: Action Data = None. When off hook on a call, pressing this button allows the user to then press another active line appearance or intercom button to view caller number information for that call. |
• | Call ID Name - Display: Action Data = None. On some phones, after the call is answered the call display is not able to show both the caller ID name and number. This function allows the user on such phones to toggle between the name and the number. If the user has this feature enabled, removing this button will turn the feature off. |
• | Call Screening: Action Data = None. A button set to this function is used to enable or disable call screening. While enabled, when a caller is presented to the user's voicemail mailbox, if the user's phone is idle they will hear through the phone's handsfree speaker the caller leaving the message and can select to answer or ignore the call. |
• | Direct Line Pickup - Active: Action Data = None. A button set to this function allows the user to pickup a ringing, held or connected call on the specified line. Users can also dial intercom 68LL where LL is the line number. |
• | Direct Line Pickup - Idle: Action Data = None. A button set to this function allows the user to seize and make a call using the specified line if that line is idle. Users can also dial intercom 8LL where LL is the line number. |
• | Group Pickup: Action Data = Pickup Group number 1 to 4. A button set to this function allows the user to pickup the longest ringing call at the specified group. |
• | VMS Transfer: Action Data = None. A button set to this function allows the user to transfer a call directly into the voicemail mailbox of another user. |
Other
• | Account Code Entry: Action Data = None. A button set to this feature allows the user to enter a voluntary account code to be associated with the current call or with the call made after entry of the account code. Not supported by POTS phones. |
• | Conference Drop: Action Data = None. A button set to this function acts as a call drop button. On Avaya digital stations, a list of conference parties is displayed from which the user can select which call to drop. On ETR phones, the last added external party is dropped. |
• | Contact Closure 1/Contact Closure 2: Action Data = None. A button set to this function Allows the user to activate the phone system's contact closure 1 or contact closure 2 switch. The user must also be a member of the appropriate Contact Closure Group. While the contact is on, the button lamp is green at the user's extension and red at any other users configured for the same contact closure. The duration and type of closure is configured in the Contact Closure Group settings. |
• | Do Not Disturb: Action Data = None. A button set to this function allows the user to redirect all call to them while still being able to make calls. Incoming calls follow voicemail coverage if on, else they receive busy. Do not disturb overrides call forwarding. If the user has this feature enabled, removing this button will turn the feature off. |
• | Privacy: Action Data = None. A button set to this function allows the user to switch call privacy on or off during a call. When on, other users with line appearances for the same line are not able to join the call using that button. If the user has this feature enabled, removing this button will turn the feature off. |
• | Recall: Action Data = None. A button set to this function allows the user to send a recall or hook flash signal. |
• | Station Lock: Action Data = None. A button set to this function allows the user to lock their extension by entering a 4 digit code. When locked, the extension can only be used to make emergency calls and dial marked speed dials. To unlock the phone the same 4 digit code must be used. |
• | Station Unlock: Action Data = None. A button set to this function allows the system administrator extensions (the first two extensions in the system) to unlock any extension without knowing the 4 digit code that was used to lock the extension. |
• | Blank When selected, this option removes all programming from the button. |
Coverage
• | Call Coverage: Action Data = XX-YY where if XX is the source extension and YY is the destination extension. A button set to this function allows the user to turn call coverage on or off. If the user has this feature enabled, removing this button will turn the feature off. |
• | Call Forwarding: Action Data = XX-YY where if XX is the source extension and YY is the destination extension. A button set to this function allows the user to turn call forwarding on or off. If the user has this feature enabled, removing this button will turn the feature off. |
• | VMS Cover: Action Data = None. A button set to this function allows the user to turn voicemail coverage of their calls on or off. |
Messaging
• | Absent Text: Action Data = None A button set to this function allows the user to set or clear an absence text message. When set, the message is displayed on their extension and also on other extensions when they call the user. If the user has this feature enabled, removing this button will turn the feature off. |
• | Voicemail Collect: Action Data = None. A button set to this function allows the user to access the voicemail to collect messages. |
• | Message Alert Notification: Action Data = A button set to this function allows the user to inspect the current state of another user's message waiting lamp. It can only be used in conjunction with other users for which this user has Auto Dial - ICM buttons configured. |
This tab and its button functions are only for the first extension in the system. These features are linked to the usage of the System Password as they affect the operation of the phone system for all users and trunks.
• | Night Service: Action Data = None. A button set to this function allows the user to switch night service on or off. The System Password, if set, is required to use this feature. If the user has this feature enabled, removing this button will turnthe feature off. |
• | Wake Up Service: Action Data = None. It allows the user to set an alarm call to occur another extension in the next 24-hours. When the alarm occurs, if the call is answered the targeted user will hear music on hold if available. If the call is not answered another attempt is made 5 minutes later, however only 2 attempts are made. Only one alarm can be set against each user at any time. Setting another alarm will override any existing alarm. |
• | Blank When selected, this option removes all programming from the button. |
This menu enables you customize lines by setting the programmable button as a line appearance button to make and answer calls on a particular line.
For systems operating in PBX mode, buttons can also be selected for ARS selector group numbers. Those can be used to make calls but not to receive calls. When pressed, an available line in the ARS selector group is seized.
• | Note that for systems running in Key mode, a number of each users programmable buttons are automatically configured as line appearance buttons according to the system Number of Lines setting. If the system setting Number of Lines is changed, it may overwrite all or some of the current button programming. |
Lines
Select the line with which the button will be associated. For systems operating in Key mode, the ARS Selector group numbers are also listed.
• | Ringing Options: Phone Based Admin = Yes. Select whether the phone should provide audible alerting when a call is waiting to be answered on the line. Not used for buttons assigned to ARS Selectors. |
• | Immediate Provide audible alerting as normal. |
• | Delayed Ring Only provide audible alerting after approximately 15 seconds. |
• | No Ring Do not provide any audible alerting. |
• | Blank When selected, this option removes all programming from the button. |
This menu is accessed by clicking the Advanced button on the System menu.
Advanced System Parameters
The following settings are shown in this panel:
• | Ring on Transfer: Default = Active. Phone Based Admin = Yes. If selected, callers being transferred hear ringing during the transfer process. If not selected, the caller will hear music on hold. |
• | Hold Reminder Time: Default = 60 seconds, Range = 0 (Off) to 180 seconds. Phone Based Admin = Yes. This setting controls how long calls remain on hold before recalling to the user who held the call. Note that the recall only occurs if the user has no other connected call. Recalled calls will continue ringing and do not follow forwards or go to voicemail. |
• | Recall Timer Duration: Default = 500, Range = 25 to 800 milliseconds. Phone Based Admin = Yes. This is the flash pulse width used for analog trunks and T1 trunks. |
• | Transfer Return Ring: Default = 4 (20 seconds), Range 1 to 180 seconds. Phone Based Admin = Yes. Sets the delay after which any call transferred by a user that remains unanswered, should return to the user. A return call will continue ringing and does not follow any forwards or go to voicemail. Transfer return will occur if the user has an available call appearance button. Transfer return is not applied if the transfer is to a hunt group. |
• | Outside Conference Denial: Default = Allowed. Phone Based Admin = Yes. When set to the Allowed, more than one outside line can be added to a conference. When set to the Disallowed, a second outside line can not be added to a conference. This feature does not change based on the type of outside line. The intent of this feature is to minimize toll fraud. For example, if set to disallowed, this would prevent someone from accepting an outside call at an extension, conferencing in another outside party, and then walking away allowing the two parties to converse. |
• | Toll Call Prefix: Default = 0 or 1 Required Before Area Code. Phone Based Admin = Yes. Allows selection between 0 or 1 Required Before Area Code or Area Code and Number Only. |
STUN Settings for Network
These settings are used if SIP trunks are added to the phone system's configuration using the SIP Trunk Administration menu. These settings are necessary to allow SIP connections from the network on which the phone system is attached to reach the public network on which the SIP provider is located.
The following fields can be completed either manually or the phone system can attempt to automatically discover the appropriate values. To complete the fields automatically, only the STUN Server IP Address is required. STUN operation is then tested by clicking Run STUN. If successful the remaining fields are filled with the results.
• | Enable STUN: Default = Off This field is used to select whether STUN is used or not. |
• | STUN Server IP Address: Default = Blank This is the IP address of the line providers SIP STUN server. The phone system will send basic SIP messages to this destination and from data inserted into the replies can try to determine the type ITSP NAT changes being applied by any firewall between it and the ITSP. |
• | STUN Port: Default = 3478 Defines the port to which STUN requests are sent if STUN is used. |
• | Firewall/NAT Type: Default = Unknown The settings here reflect different types of network firewalls. |
• | Blocking Firewall Allow outgoing TFTP WRQ. Typically this will be the case. It has been observed that the Avaya corporate firewall permits outgoing TFTP RRQ. |
• | Symmetric Firewall SIP packets are unchanged but ports need to be opened and kept open with keep-alives. If this type of NAT is detected or manually selected, a warning ‘Communication is not possible unless the STUN server is supported on same IP address as the ITSP will be displayed as part of the manager validation. |
• | Open Internet No action required. If this mode is selected, STUN lookups are not performed. |
• | Symmetric NAT A symmetric NAT is one where all requests from the same internal IP address and port, to a specific destination IP address and port, are mapped to the same external IP address and port. If the same host sends a packet with the same source address and port, but to a different destination, a different mapping is used. Furthermore, only the external host that receives a packet can send a UDP packet back to the internal host. SIP Packets need to be mapped but STUN will not provide the correct information unless the IP address on the STUN server is the same as the ITSP Host. If this type of NAT/Firewall is detected or manually selected, a warning ‘Communication is not possible unless the STUN server is supported on same IP address as the ITSP’ will be displayed as part of the manager validation. |
• | Full Cone NAT A full cone NAT is one where all requests from the same internal IP address and port are mapped to the same external IP address and port. Furthermore, any external host can send a packet to the internal host, by sending a packet to the mapped external address. SIP packets need to be mapped to NAT address and Port; any Host in the internet can call in on the open port, that is the local info in the SDP will apply to multiple ITSP Hosts. |
• | Restricted Cone NAT A restricted cone NAT is one where all requests from the same internal IP address and port are mapped to the same external IP address and port. Unlike a full cone NAT, an external host (with IP address X) can send a packet to the internal host only if the internal host had previously sent a packet to IP address X. SIP packets needs to be mapped. Responses from hosts are restricted to those that a packet has been sent to. So if multiple ITSP hosts are to be supported, a keep alive will need to be sent to each host. If this type of NAT/Firewall is detected or manually selected, no warning will be displayed for this type of NAT. |
• | 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. If this type of NAT/Firewall is detected or manually selected, no warning will be displayed for this type of NAT. However, some Port Restricted have been found to be more symmetric in behavior, creating a separate binding for each opened Port, if this is the case the manager will display NATs a warning ‘Communication is not possible unless the STUN server is supported on same IP address as the ITSP’ as part of the manager validation. |
• | Unknown Use this setting if the other settings are unsuitable |
• | Static Port Block Use the RTP port range 49152 to 53246. |
• | Binding Refresh Time (seconds): Default = 0 (Never), Range = 0 to 3600 seconds. Having established which TCP/UDP port number to use, either through automatic or manual configuration, the phone system can send recurring ‘SIP Options requests’ to the remote proxy terminating the trunk. Those requests will keep the port open through the firewall. Requests are sent every x seconds as configured by this field. If a binding refresh time has not been set you may experience problems receiving inbound SIP calls as they are unable to get through the Firewall. In these circumstances make sure that this value has been configured. |
• | Public IP Address: Default = 0.0.0.0 This value is either entered manually or discovered by the Run STUN process. If no address is set, the phone system IP address is used. |
• | Public Port: Default = 0 This value is either entered manually or discovered by the Run STUN process. |
• | Run STUN This button tests STUN operation between the phone system and the STUN Server IP Address set above. If successful the results are used to automatically fill the remaining fields with the discovered values. Before using Run STUN the SIP trunk must be configured. |
SMTP Server Configuration
Email can be used to provide users with an alert when they have a new voicemail message. This feature is called voicemail email. This requires the system to be configured with details of an SMTP email server account which is used to forward the messages to the user's email address.
• | IP Address: Default = 0.0.0.0 This field sets the IP address of the SMTP server being used to forward emails. |
• | Port: Default = 25, Range = 0 to 65534. This field sets the destination port on the SMTP server. |
• | Send Email From: Default = Blank This field sets the sender address to be used for emails from the system. Depending of the authentication requirements of the SMTP server, this may need to be a valid email address hosted by that server. Otherwise the SMTP email server may need to be configured to allow SMTP relay of this address. |
• | Server Authentication: Default = On This field should be selected if the SMTP server being used requires authentication to allow the sending of emails. When selected, the User Name and Password fields become available. |
• | User Name: Default = Blank This field sets the user name to be used for SMTP server authentication. |
• | Password: Default = Blank This field sets the password to be used for SMTP server authentication |
• | Enable CRAM-MD5: Default = Off. This field should be selected if the SMTP server uses CRAM-MD5. |
© 2011 AVAYA - Issue 01.i.- 08:28, 24 November 2011 (user.htm) Performance figures, data and operation 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 at its own discretion. The publication of information in this document does not imply freedom from patent or any other protective rights of Avaya or others. All trademarks identified by (R) or TM are registered trademarks or trademarks respectively of Avaya Inc. All other trademarks are the property of their respective owners. Last Modified: 14/11/2011 |