Avaya one-x TM Quick Edition Release 2.0 Release Notes

Transcription

1 Avaya one-x TM Quick Edition Release 2.0 Release Notes These release notes provide a high level description of new features as well as lists of resolved and existing issues in Avaya One-X Quick Edition Release 2.0 GA. Information for upgrading to Quick Edition Release 2.0 can be found at Contents Contents...1 Contents for Release 2.0 GA...1 New Features in Release 2.0 GA...2 Issues Resolved in Release 2.0 GA...3 Known Issues in Release 2.0 GA...4 Known Issues When Connecting Quick Edition to CM and SES...5 Known Issues in the Multisite Provisioning Tool...5 Appendix A. Noise on External Calls through a G Appendix B. Network Recommendations...7 Appendix C. Compatible L2 switches...9 Appendix D. IP Multicast information...10 Contents for Release 2.0 GA Avaya 4610 firmware Avaya 4610 bootloader Avaya 4621 firmware Avaya 4621 bootloader Avaya G10 PSTN gateway firmware

2 New Features in Release 2.0 GA More details on the new features in Release 2.0 GA can be found in the Release 2.0 documentation available at Call Park, Page and Retrieve The Call Park-Page-Retrieve feature lets you put an active call on hold, page users, and then allows for the call to be retrieved from any other Quick Edition IP telephone in the one-x TM Quick Edition network. SES-CM Connectivity SES-CM Connectivity provides the ability for an Avaya one-x TM Quick Edition equipped small branch office to connect to a headquarters site over the Wide Area Network. This provides an ideal branch solution for an enterprise served by a Communication Manager (CM) and Converged Communications Server running SIP Enablement Services (SES). Connectivity between SES/CM and one-x TM Quick Edition is based on standard SIP signaling without proprietary extensions. Teleworker The teleworker feature allows single workers at home or remote offices to have access to the corporate directory, call forwarding, 3 digit dialing and other features and services that are available to everyone who uses the one-x TM Quick Edition system. The teleworker feature extends the one-x TM Quick Edition network to any location that has high-speed access to the Internet. To use the teleworker feature, an external VPN appliance is required. Enhanced Voic with Attachment This feature adds the ability to attach voic messages to the notification feature, providing a user with a single inbox for both voic and (in MS Outlook for example). When enabled, this feature attaches a WAV file to the . A plug-in is required for Windows Media player to properly play the Voic attachment. Note: Only Microsoft s Windows Media Player with the plug-in will play back the voic attachment. The plug-in can be downloaded from Personalized Ringing This feature provides the ability to choose one of five ring tones to alert you to incoming calls. You can listen to each ring tone before deciding which one to select. This is particularly useful to distinguish multiple phones in smaller locations. Priority Value Tagging (for Quality of Service) Avaya one-x TM Quick Edition devices now support IEEE 802.1p (priority value tagging), within the framework of the IEEE 802.1Q Virtual Bridged Local Area Networks standard. The feature allows you to assign priority levels to one-x TM Quick Edition voice and data traffic in order to ensure QoS at OSI Layer 2. Multisite Provisioning Tool The Multisite Provisioning Tool can be used to simultaneously configure one or more one-x TM Quick Edition systems from a single location. Any individual one-x TM Quick Edition systems, a subset of selected systems, or all systems known to the Multisite Provisioning Tool can be configured at once. 2

3 Issues Resolved in Release 2.0 GA 4001: Echo present in the first few seconds of a PSTN call through the G10 gateway. 4887: Delay when taking a call off hold, or calls slow to come off hold (QQ: ). 4897: LEDs on G10 gateway may stop functioning properly after a while. 5080: Noticeable delay establishing audio path on calls to a group (QQ: , , ). 5098: In Direct Inward Line (DIL) configuration, external caller hear 2-3 rings before Quick Edition telephone(s) ring (QQ: ). In Release 1.0, the G10 waited for the caller ID information or the second ring to arrive before delivering the call and the caller ID to a Quick Edition telephone. In Release 2.0, the G10 delivers the call to an extension immediately, then delivers the caller ID if/when it is available. 5312: A telephone may reset if a user places a call on hold and then immediately hangs-up the handset (QQ: , ). 5755: Occasional G10 gateway reset (QQ: , , ). Under certain circumstances, a G10 PSTN Gateway running Avaya one-x Quick Edition Release 1.0 (6.0.3) can crash or hang due to bugs in low-level string reading code and flash writing code. In the case of a crash, the G10 will reboot on its own. This may result in dropped or missed calls. In the case of a "hang", the G10 will stop responding to new requests. Existing calls will continue, but no new incoming or outgoing calls will be possible. This condition has been resolved. See PSN #799U at for more details. 3

4 Known Issues in Release 2.0 GA 5829: TFTP server may be unresponsive during upgrade using the Release 2.0 Upgrade CD. On some PCs, the TFTP server may be unresponsive after starting from the Release 2.0 Upgrade Wizard from the CD. Workaround: Copy the contents of the CD to a folder on the local hard drive and run the Avaya_one-X_QE_R2.0_Wizard.exe from there. 4985: You can not change the SMTP port in the system to a 5 digit number. The help text shows that the valid Port Numbers for SMTP mail is 25, or in the range The system allows the entry of a 5 digit port number, but strips the fifth digit when the port number is subsequently displayed. Workaround: Set your SMTP server to use a port numbered less than : Caller ID not available on DIL (direct inward line) calls from PSTN if forwarded or answered before the Caller ID is made available from the PSTN. Workaround: Answer or forward calls after the PSTN has provided the Caller ID information. This is typically received from the PSTN between the 1 st and 2 nd rings. 5286: Call forwarding fails for a group with only one member. If a group is created with only 1 member, and all calls to that group are forwarded to another extension, the forwarding will not be successful for calls received from an external source (i.e. not on the same Quick Edition network). Workaround: If a group with only one member requires forwarding of the group calls to another extension, add the other extension to the group. 5741: "Upgrade in progress" message is missing during software downgrade from Release 2.0 to Release 1.0. Workaround: there is no workaround, you must wait until the downgrade completes (may be as long as 2-5 minutes). 5812: Audio heard on handset and speaker after lifting handset. After changing your personal ring settings, or after adjusting the ringer volume, audio may be heard from both the handset and speaker after lifting the handset. Workaround: Activating the speakerphone or receiving a call will correct the problem. 5507: Create Dialing Rule help text contains erroneous characters. The online help text for the WebAdmin create dialing rules contains erroneous characters. The two described rules should read: * allows any string or combination to follow? is a wildcard and allows any character to fill this position Workaround: there is no workaround. 4

5 Known Issues When Connecting Quick Edition to CM and SES 5207: CM trunks used to connect to Quick Edition systems must have Direct IP-IP Media Shuffling disabled. If Direct IP-IP Media Shuffling is not disabled, there can be cases where there is an extended delay (up to one minute) in opening the audio path on calls forwarded from CM sets to Quick Edition Sets. Workaround: Disable Direct IP-IP Media Shuffling on CM trunks used to connect to Quick Edition systems. 4699: If you call the autoattendant on a Quick Edition system connected to SES from a phone connected to CM, you will not hear ring-back when the autoattendant transfers you to the extension you specified. Workaround: We recommend that every Quick Edition phone should have a SIP identity registered with SES so that it can be directly dialed from any phone or trunk connected to CM. If you do call the autoattendant from CM and then dial an extension, however, you will hear the hold tones. 5121: If a Service Provider Identity is configured with a Domain Name different from the Proxy Host, outgoing INVITE messages will use 'user@proxy' in the To and From URIs instead of user@domain. Workaround: The domain name of the registrar and proxy must be the same. 5855, 5891: Cannot call-forward to an external number via SIP. This applies to calls forwarded from a single user set or from a group extension. Workaround: There is no work around. Known Issues in the Multisite Provisioning Tool 5476: The Enterprise Service Provider inbound proxy IP address cannot be set from the MPT. Workaround: Use the WebAdmin to set the proxy. 5359: When creating a new Site Group in the MPT with invalid characters in the name, the group is created with the invalid characters removed from the name. A group name can only contain number, letters, spaces and dashes. If you use any other characters in the group name, those characters are discarded when the 'Save Settings...' button is pressed. There is no warning to the user that this has occurred. Workaround: Only use numbers, letters, spaces and dashes when naming a group in MPT. 5

6 Appendix A. Noise on External Calls through a G10 A person using a Quick Edition telephone to talk with someone via the G10 and the PSTN can hear what can be described as static or white noise during what should be periods of silence. In some cases the person may hear a constant buzz or 60 Hz hum. The ultimate cause is 60Hz noise on the analog lines connecting the G10 to the CO switch. Hum is generally due to the introduction of AC power supply noise into the analog line connecting the G10 to the CO switch. Typical causes are wiring running too close to power transformers or power lines, leaky power supplies (typically "wall bricks") and common mode noise (i.e., a signal between both T & R and ground) due to poor grounding. The cause of the static or white noise is also the 60 Hz hum. During an active call, a certain amount of comfort noise is generated by the gateway so that the user does not assume far-end party has disconnected during silent periods of the conversation. The volume of this comfort noise is based on the ambient noise on the line. When excessive noise at 60Hz and its harmonics is present, the volume of the comfort noise can be perceived as quite loud. Since the user can easily distinguish between the comfort noise and the hum, he perceives it as bursts of white noise when the other person is not speaking. There are three possible remedies for this problem: 1. Ground the gateway properly. a. Connect the grounding lug on the back of the G10 gateway to EARTH GROUND. Use a 24 AWG ( in. or mm) or thicker solid copper wire. An earth ground connection can be made in one of several ways follow local electrical codes to ground the G10 PSTN gateway. b. Use a grounded power supply such as Phihong model PSA-18U-120 or PSA- 31U-120. For a list of vendors from which these power supplies can be purchased, see the Phihong web site, 2. Ensure that the loop length is correctly provisioned on all lines of all G10 PSTN Gateways in the system. Incorrect provisioning of loop length can result in echo, or excessive noise on external calls through the G10 PSTN Gateway. Consult the one- X TM Quick Edition System Administrator Guide for details on how to provision the loop length. 3. Download and install the one-x TM Quick Edition patch load or one-x TM Quick Edition Release 2.0. Following the installation process, start the Avaya one-x TM QE Gateway Tuner and set comfort noise level to low for any affected G10 PSTN Gateway Lines. This will allow you to reduce the level of comfort noise heard during otherwise silent periods, even when no 60Hz noise is perceptible. For details on how to download and install Release or Release 2.0, please go to click on Product Support Notice and read the PSN titled White noise and hum on PSTN calls from Quick Edition phones. To download Release or Release 2.0, go to and click on Downloads. 6

7 Appendix B. Network Recommendations To ensure optimum performance, the following LAN operating parameters are recommended. Cabling Supply RJ45 Category 5 (Cat5) or better (for example, Cat5e) Ethernet cabling to connect equipment such as Avaya one-x TM Quick Edition G10 PSTN Gateways to the LAN. Power Avaya one-x TM Quick Edition Telephones, and G10 PSTN Gateways support 802.3af PoE (Power over Ethernet). If you want to connect Avaya one-x TM Quick Edition equipment to a switch that does not support 802.3af, you can use an Avaya PoE injector (Part # 1151B1) to power the telephone. IP Multicast Multicast IP traffic must be permitted on the LAN. The default multicast address used by the Avaya one-x TM Quick Edition System is This is a limited-scope address that is not routable over the public network (Internet). Connecting all Avaya one-x TM Quick Edition devices to the same network segment their IP addresses must belong to the same network address space, will help ensure IP multicast can be passed between the devices. However, certain high-end network devices do provide the ability to pass multicast traffic between IP segments if configured to do so. VLAN tagging and QoS VLAN tagging or QoS methods are not required by the network device being used to connect Avaya one-x TM Quick Edition. The network element (switch, router) used to connect Quick Edition can be a simple unmanaged device which supports IP multicast traffic. Certain networks will not require a QoS strategy as network bandwidth usage may not be great enough for QoS to come into effect. Avaya one-x TM Quick Edition devices do support IEEE 802.1p (priority value tagging), within the framework of the IEEE 802.1Q Virtual Bridged Local Area Networks standard. The feature allows you to assign priority levels to one-x TM Quick Edition voice and data traffic in order to ensure QoS at OSI Layer 2. Specifying a priority such as 5 for voice traffic and 3 for data ensures that one-x TM Quick Edition voice traffic has priority over data. Your LAN administrator must determine the required settings. If your network does include VLANs, include all Quick Edition devices in the same VLAN. If you are experiencing performance degradation with the Avaya one-x TM Quick Edition System due to the traffic load on your network, you may either physically segment the voice network from the data network, or manually configure QoS on the network switches, routers, etc. It is not recommended to connect a network server PC (for example, a web server, file server, or database server) or a network printer to the PC port on an Avaya one-x TM Quick Edition Telephone. If your voice network equipment is capable of full-duplex transmission, select full-duplex instead of half-duplex transmission. Full-duplex devices enable callers on both ends of the connection to speak simultaneously. IGMP The Avaya one-x TM Quick Edition System supports IGMP v2. A number of higher-end Layer 2 switches support IGMP snooping by default. If the Avaya one-x TM Quick Edition devices making up the network cannot communicate with each other, turning off IGMP snooping on the switch may resolve the problem if the switch requires an IGMP querier to be present on the network but an IGMP querier is not available. 7

8 STP If any Avaya one-x TM Quick Edition devices are connected to a switch that runs the Spanning Tree Protocol (STP), configure the communications switch connections with Portfast (also known as spantree start-forwarding on a Cisco 1900XL). Portfast enables the switch to go into a forwarding state almost immediately after it is powered on. A Word about IP Addresses If a DHCP (Dynamic Host Configuration Protocol) server is connected to the Avaya one-x TM Quick Edition System network, the Avaya one-x TM Quick Edition Telephones and G10 PSTN Gateways will request network addresses from the DHCP server. On networks without a DHCP server, Avaya one-x TM Quick Edition Telephones and G10 PSTN Gateways assign themselves unique addresses in the /16 (Zeroconf) network address space with a network mask of If required, you may assign fixed network addresses to Avaya one-x TM Quick Edition Telephones or G10 Gateways through Network Options settings. Once assigned, the settings persist until they are either changed manually, or another device having the same IP address is detected at boot time. To re-enable automatic IP Address assignment for telephones or G10 PSTN Gateways which previously had manually assigned IP addresses, you must reset the telephone or G10 PSTN Gateway IP address to

9 Appendix C. Compatible L2 switches An up-to-date list can be found at If you find the Quick Edition is not working properly with your switch, ensure that the switch and network follow the network recommendations in Appendix B. Specifically, make sure the switch ports are configured to be on the same VLAN. If they are on the same VLAN yet the telephones display the message No peers available, then try disabling IGMP snooping on the L2 switch. More on this behavior and alternative solutions can be found in Appendix D. 9

10 Appendix D. IP Multicast information The Avaya one-x TM Quick Edition system (telephones sets and G10 PSTN gateway) use IP multicasts to discover each other and detect when a peer is down. The multicast IP address that the Quick Edition uses is Each peer multicast s a hello message to the rest of the system saying they are alive. If the system detects that a peer has not sent 3 of the hello messages in a row, it will flag that peer as being down. The Quick Edition also uses IP multicast to stream MOH (Music On Hold) and when paging a group of sets. The handling of IP multicast packets is not identical between all the Layer 2 switch vendors. Most unmanaged switches simply broadcast IP multicast packet out every port which is not a problem for the Quick Edition. The problem arises when a managed switch requires an IGMP querier to be present on the network to forward IP multicast packets to other ports, but one is not present. Symptoms of this are that the Quick Edition sets will display No Peers Available and that set to set calls or set to G10 calls will fail with an audible fast busy. The IGMP querier would typically be a router which has an interface in the same subnet that the Quick Edition. This router needs to be properly configured to also route IP multicast. Because not all IP multicast implementations required that they be routed across multiple subnets, some vendors have added the option to have their managed L2 switch do the querying. When the Quick Edition is installed on such a switch (with no IGMP querier present on the network), four options can be implemented to resolved the issue: Disable IGMP snooping Statically program the membership of the ports that have a Quick Edition device to be part of the multicast group ( ) Add an IGMP querier (either configure the switch to do it or a router) Disabling IGMP snooping on a switch means that the switch will no longer snoop the IP packets to see what ports are part of a particular multicast group. This has the affect of broadcasting IP multicast packets out to every port. This is the recommended solution because of its simplicity. Statically programming the membership of the ports to a particular IP multicast group is an alternative that requires more administration. Changing the query interval timer is yet another alternative but remember that when the timer expires, the Quick Edition system will no longer see each other. Adding an IGMP querier is an alternative to disabling IGMP snooping if the broadcast of the Quick Editon IP multicast packets poses a problem. Like mentioned above, there are two method to implement this; configuring the L2 switch to be the IGMP querier (if supported by the switch) or add a router (L3) and configure it appropriately Avaya Inc. All Rights Reserved. Avaya and the Avaya Logo are trademarks of Avaya Inc. and may be registered in certain jurisdictions. All trademarks identified by the, SM or TM are registered trademarks, service marks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. 10