Avaya Solution & Interoperability Test Lab Configuring Avaya IP Telephones, Softphones, and Access Points With Matsushita MNO PoE Switches- Issue 1.0 Abstract These Application Notes present a sample configuration for Avaya IP telephones, softphones, and access points using Matsushita MNO PoE Switches. Configurations for Quality of Service and Power over Ethernet are covered. 1 of 17
1. Introduction Figure 1 shows an Avaya VoIP infrastructure in a local area network (LAN). The Cisco Catalyst 6509 functions as a backbone switch for L2 switching and L3 routing. The MNO M12PWR and M24PWR switches function as edge switches and can provide inline power to the Avaya IP telephones. The Avaya S8500 Media Server and Avaya G650 Media Gateway are connected to the Cisco Catalyst 6509. A DHCP server is used for the Avaya IP telephones and PCs. The TFTP server is used for the Avaya IP telephones. The MNO M12PWR switch comes with 12 PoE ports and one 1000 BaseT uplink while the M24PWR switch comes with 24 PoE ports and 2 1000 BaseT/BaseX uplinks. DHCP/TFTP Server IP: 10.10.20.5 VLAN 10: 10.1.1.1/24 VLAN 110: 10.10.10.1/24 VLAN 120: 10.10.20.1/24 IP: 10.10.10.2 IP Softphone Avaya 4620SW IP Telephone Cisco Catalyst 6509 (L2/L3) Port 1 PC Avaya S8500 Media Server 4/44 4/25 4/26 MNO M12PWR VLAN 110: Voice-VLAN VLAN 120: Data-VLAN Avaya 4620SW IP Telephone PC IP: 10.1.1.20 4/45 4/46 4/47 Avaya 6400 Series Digital Phone Avaya G650 Media Gateway IPSI: 10.1.1.21 C-LAN: 10.10.10.10 MEDPRO: 10.10.10.11 Port 26 MNO M24PWR IP: 10.10.10.3 Port 1 IP Softphone Avaya 4610SW IP Telephone PC Figure 1: Avaya IP Telephones and Softphones with MNO PoE Switches and Cisco Catalyst 6509 Figure 2 is the configuration for Power over Ethernet used in these Application Notes. The following Avaya products are directly connected to the M12PWR and M24PWR switches: Avaya 4602, 4602SW and 4610 SW IP telephones Avaya 4602SW SIP telephones Avaya 4620 IP telephone with and without EU24 Avaya 4620SW IP telephone with and without EU24 Avaya 4630SW IP telephone Avaya Gen-1 4612 and 4624 IP telephones with Avaya 30A switch bases Avaya Gen-2 4606, 4612, and 4624 IP telephone Avaya wireless AP-4/5/6 access point 2 of 17
Avaya H.323/SIP VoIP Infrastructure Avaya 4602SW SIP Telephone M12PWR M24PWR EU24 Avaya 4630SW IP Telephone Avaya 4620/4620SW IP Telephone with and without EU24 Avaya 4610SW IP Telephone Avaya 4602 /4602SW IP Telephone Avaya Gen-2 4606 IP Telephone Avaya Gen-1 4612/4624 IP Telephone 30A Base Avaya Gen-2 4612/4624 IP Telephone Avaya Wireless AP-4/5/6 Access Point Wireless Laptop (Avaya 802.11b) with Avaya IP Softphone Figure 2: PoE Configuration for Avaya 4600 Series IP Telephones and Wireless Access Point with MNO M12PWR and M24PWR Switches 2. Equipment and Software Validated The following equipment and software were used for the sample configuration provided: Network Component Avaya Communication Manager Avaya S8500 Media Server 2.1 Load 411.7 Avaya G650 Media Gateway IPSI TN2312AP C-LAN TN799DP Medpro TN2302AP Software Version FW09 FW11 FW92 Avaya 4602SW SIP Telephone 1.01 Avaya 4602/4602SW IP Telephones 1.8.2 Avaya 4610SW/4620/4620SW Telephones 2.1 Avaya Gen-1/Gen-2 4606/4612/4624 IP Telephones 1.82 Avaya 4630SW IP Telephone 1.696 Avaya AP4/5/6 2.4.5 Avaya IP Softphone 5.1.4.6 Microsoft 2000 DHCP Server 5.00.2195 (SP4) Avaya TFTP Server 3.6.1 Matsushita MNO M12PWR/M24PWR 1.0.4.78 Cisco 6509 Catalyst L2 L3 8.2(1) 12.1(13)E6 Table 1 - Network Component Software Versions 3 of 17
3. Configuring Avaya S8500 Media Server With Avaya G650 Media Gateway Follow the procedures in reference [1] to configure the following IP address on the S8500 Media Server and the IP address of the IPSI interface on the Avaya G650 Media Gateway for the sample configuration: S8500 Media Server: 10.1.1.20 IPSI (G650): 10.1.1.21 Use the command add ip-interface to add and configure the C-LAN and the Media Processor of the Avaya G650 Media Gateway with the following parameters: C-LAN IP address: 10.10.10.10 Media Processor IP: 10.10.10.11 VLAN ID: n Network region: 1 It is recommended to configure the C-LAN and the Media Processor of the Avaya G650 Media Gateway to 100 BaseT/Full duplex to avoid any auto negotiation problem with the Cisco Catalyst 6509. VLAN tagging is disabled for the C-LAN and Media Processor of the Avaya G650 Media Gateway in the sample configuration. Use the command display ip-interface <board #> to verify the configuration. display ip-interface 01A10 IP INTERFACES Type: C-LAN Slot: 01A10 Code/Suffix: TN799 D Node Name: TEST-CLAN IP Address: 10.10.10.10 Subnet Mask: 255.255.255.0 Gateway Address: 10.10.10.1 Enable Ethernet Port? y Network Region: 1 VLAN: n ETHERNET OPTIONS Auto? n Speed: 100Mbps Duplex: Full Number of CLAN Sockets Before Warning: 400 4 of 17
display ip-interface 01A11 IP INTERFACES Type: MEDPRO Slot: 01A11 Code/Suffix: TN2302 Node Name: TEST-MPRO IP Address: 10.10.10.11 Subnet Mask: 255.255.255.0 Gateway Address: 10.10.10.1 Enable Ethernet Port? y Network Region: 1 VLAN: n ETHERNET OPTIONS Auto? n Speed: 100Mbps Duplex: Full In the sample configuration, all the IP telephones and softphones will register to the C-LAN of the Avaya G650 Media Gateway and will be assigned to network region 1 by default. The Avaya IP telephones and softphones will receive the QoS parameters from network region 1 upon their successful registration. DiffServ DSCP 48 and 802.1p priority 6 are used in the sample configuration. The C-LAN and Media Processor also use these QoS parameters because they are configured to this network region. Avaya IP softphones use DiffServ for QoS. 802.1Q/p priority was not used because the NIC of the PC running the IP softphone does not support 802.1Q/p. The following shows the network region 1 configuration. Codec Set 1 is configured for the calls in network region 1. display ip-network-region 1 Page 1 of 19 IP NETWORK REGION Region: 1 Location: Home Domain: Name: Intra-region IP-IP Direct Audio: yes AUDIO PARAMETERS Inter-region IP-IP Direct Audio: yes Codec Set: 1 IP Audio Hairpinning? y UDP Port Min: 2048 UDP Port Max: 3028 RTCP Reporting Enabled? y RTCP MONITOR SERVER PARAMETERS DIFFSERV/TOS PARAMETERS Use Default Server Parameters? y Call Control PHB Value: 48 Audio PHB Value: 48 802.1P/Q PARAMETERS Call Control 802.1p Priority: 6 Audio 802.1p Priority: 6 AUDIO RESOURCE RESERVATION PARAMETERS H.323 IP ENDPOINTS RSVP Enabled? n H.323 Link Bounce Recovery? y Idle Traffic Interval (sec): 20 Keep-Alive Interval (sec): 5 Keep-Alive Count: 5 5 of 17
To achieve high voice quality in the LAN, Codec 1 is configured to G711MU: display ip-codec-set 1 Page 1 of 2 Codec Set: 1 IP Codec Set Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n 2 20 2: 4. Configuring MNO M12PWR And M24PWR Switches Sections 4.1 to 4.2 show the configuration on the M24PWR switch. A similar configuration applies to the M12PWR switch. 4.1. MNO M24PWR Switch Layer Two Configuration Connect a COM port on a computer to the console port of the M24PWR switch and log in with the proper user name and password. Follow [B]asic Switch Configuration... System [I]P Configuration to configure the system IP address on the M24PWR. The following screen shows the configuration. Basic Switch Configuration -> System IP Configuration Menu MAC Address: 00:C0:8F:0E:A2:44 IP Address: 10.10.10.3 Subnet Mask: 255.255.255.0 Default Gateway: 10.10.10.1 DHCP Mode: Disabled -------------------------------- <COMMAND> --------------------------------- Set [I]P Address Set Subnet [M]ask Set Default [G]ateway Set [D]HCP Status Set DHCP [R]enew [Q]uit to previous menu It is recommended to configure different VLANs for an Avaya IP telephone and the attached PC. In the sample configuration, VLAN 110 is configured as the Voice VLAN and VLAN 120 is configured as the data VLAN. VLAN 120 is configured as a native VLAN while VLAN 110 is configured as a tagged VLAN on all PoE ports. VLAN 110 and VLAN 120 must be configured 6 of 17
as tagged VLANs on uplink ports 25 and 26 so that 802.1p priority can be transmitted to the Cisco Catalyst 6509. Note that VLAN 1 is configured as the native VLAN on the uplink ports. Follow [A]dvanced Switch Configuration... [V]LAN Management C[o]nfig VLAN Member to verify the configuration. The following screens show VLAN 1, VLAN 110 and VLAN 120 configuration on the M24PWR. VLAN Management -> VLAN Modification Menu VLAN ID : 110 VLAN Name : Voice-VLAN Port Members : 1-26 Untagged Ports : -------------------------------- <COMMAND> --------------------------------- Set VLAN [N]ame Select [P]ort Member [A]pply [Q]uit to previous menu VLAN Management -> VLAN Modification Menu VLAN ID : 120 VLAN Name : Data-VLAN Port Members : 1-26 Untagged Ports : 1-24 -------------------------------- <COMMAND> --------------------------------- VLAN Management -> VLAN Modification Menu VLAN ID : 1 VLAN Name : VLAN 1 Port Members : 25-26 Untagged Ports : 25-26 -------------------------------- <COMMAND> --------------------------------- 7 of 17
Follow [A]dvanced Switch Configuration... [V]LAN Management C[o]nfig VLAN Member [S]et Port Config to change the native VLAN configuration for a port. The native VLAN for all PoE ports should be configured to VLAN 120 while the native VLAN for the uplink ports should be VLAN 1. VLAN Management -> VLAN Port Configuration Menu Port PVID Acceptable Frame Type ---- ---- --------------------- 1 120 Admit All 2 120 Admit All 3 120 Admit All 4 120 Admit All 5 120 Admit All 6 120 Admit All 7 120 Admit All 8 120 Admit All -------------------------------- <COMMAND> --------------------------------- [N]ext page [P]revious Page Set Port [V]ID Set [F]rame Type [Q]uit to previous menu 4.2. QoS Configuration on MNO M24PWR Switch By default, QoS is disabled. Enable QoS by following [A]dvanced Switch Configuration... Quality of Service [C]onfiguration [T]raffic Class Configuration [S]et QoS status. Quality of Service Configuration -> Traffic Class Configuration Menu QoS Status: Enabled Priority Traffic Class -------- ------------- 0 0 1 0 2 1 3 1 4 2 5 2 6 3 0: Lowest 7 3 3: Highest -------------------------------- <COMMAND> --------------------------------- [S]et QoS status Set Priority-Traffic Class [M]aping [Q]uit to previous menu 8 of 17
The M12PWR and M24PWR switches support four hardware queues. By default, CoS values 0-1 are mapped to queue 1, CoS values 2-3 to queue 2, CoS values 4-5 to queue 3 and CoS 6-7 values to queue 4. When QoS is enabled, the M12PWR and M24PWR switches support QoS based on CoS values. Note that the M12PWR and M24PWR decide CoS values based on 802.1p priorities. For example, 802.1p priorities 0 to 7 correspond to CoS values 0 to 7. To avoid any potential QoS issue for VoIP traffic, it is recommended to configure voice VLAN 110 to a high priority with CoS 6, and then re-mark the packets in VLAN 110 with DSCP 48 for consistency. Since the IP softphones do not use 802.1p for QoS, it is recommended to map DSCP 48 (used by the IP softphones) to CoS 6. Follow [A]dvanced Switch Configuration... Quality of Service [C]onfiguration [D]ifferentiated Service Configuration to create and configure [C]lassifier, [I]n-Profile Action, Port [L]ist and [P]olicy. The following screen shows the classifier index 10 configuration for the IP telephones. Note that classifier index 10 includes all the IP packets on voice VLAN 110. Classifier Configuration -> Show Detailed Entry Information Menu Detailed Classifier Information : -------------------------------- Classifier Index : 10 Source MAC Address Destination MAC Address VLAN ID : 110 Source IP Address Source IP Address Mask Length Destination IP Address Destination IP Address Mask Length Dscp Protocol Source Layer 4 Port Destination Layer 4 Port 9 of 17
The following screen shows the classifier index 11 configuration for the IP softphones. Note that classifier index 11 includes all the IP packets with DSCP 48. Classifier Configuration -> Show Detailed Entry Information Menu Detailed Classifier Information : -------------------------------- Classifier Index : 11 Source MAC Address Destination MAC Address VLAN ID Source IP Address Source IP Address Mask Length Destination IP Address Destination IP Address Mask Length Dscp : 48 Protocol Source Layer 4 Port Destination Layer 4 Port The following screen shows two in-profile actions. Index 20 is used to mark matched packets to CoS 6 while index 21 to mark matched packets to DiffServ 48. Differentiated Service Configuration -> In-Profile Action Configuration Menu In-Profile Action: Total Entries : 2 Index Action Value ----- ------------------- ----- 20 policed-cos 6 21 policed-dscp 48 The following screen shows Port List configuration. Port List Index 21 includes all the PoE ports on the M24PWR switch. Differentiated Service Configuration -> Port List Configuration Menu Port List: Total Entries : 1 Index Port List --- ---------------------------------------------------------------- 21 1-24 10 of 17
The following screen shows the policy configuration. Policy index 10 and 100 correspond to In- Profiles 20 and 21 for the IP telephones and policy index 111 corresponds to In-Profile 20 for the IP softphones. Differentiated Service Configuration -> Policy Configuration Menu Policy : Total Entries : 2 Index Classifier Sequence In-Profile No-Match Out-Profile PortList Status ----- ---------- ---------- ---------- -------- ----------- -------- -------- 10 10 1 20 --- --- 21 Enabled 100 10 2 21 --- --- 21 Enabled 111 11 3 20 --- --- 21 Enabled 4.3. PoE Configuration On MNO M12PWR and M24PWR Switches IEEE 802.3af defines a standard protocol to be used by power sourcing equipment (PSE) and powered devices (PD). The M12PWR and M24PWR switches are IEEE 802.3af compliant PSEs and can provide inline power to the Avaya 4600 Series IP Telephones and Avaya Wireless Access Points, which are IEEE 802.3af compliant PDs. Table 2 shows the detected classes and typical (e.g., on-hook/idle) power consumption for the Avaya IP Telephones and Wireless Access Points measured from the M12PWR and M24PWR switches. Avaya IP Telephone Class Power consumption (Watts) 4602 1 3.155 4602 SW 2 3.303 4610 SW 2 3.10 4620 3 6.726 4620 with EU24 3 7.463 4620 SW 3 5.461 4620 SW with EU24 3 5.756 4630 SW 3 10.45 Gen-1 4612 with 30 A 3 5.166 Gen-1 4624 with 30 A 3 5.166 Gen-2 4606 0 5.510 Gen-2 4612 0 4.723 Gen-2 4624 0 4.428 Avaya AP4/5/6 0 4.723 Table 2 Classifications and Typical Power Consumption for Avaya PDs The M12PWR and M24PWR switches measure the power consumption in real time to decide if there is power available for the next added device. The M12PWR and M24PWR can detect the 11 of 17
Avaya PDs with the correct classification and deliver power based on the configured power limit. The power limit is 15.4 Watts by default. Follow [A]dvanced Switch Configuration... [P]ower Over Ethernet Configuration PoE [G]lobal Configuration to verify and change the PoE global configuration. The M12PWR and M24PWR switches support 170 Watts of inline power. Power Over Ethernet Configuration -> PoE Global Configuration Menu Power Budget : 170W Power Consumption : 6W Power Usage Threshold For Sending Trap: 50 % Power Management Method : Deny next port connection, regardless of priority -------------------------------- <COMMAND> ---------------------------------- Set Power [U]sage Set Power [M]anagement Method [Q]uit to previous menu Follow [A]dvanced Switch Configuration... [P]ower Over Ethernet Configuration PoE [P]ort Configuration to verify and administer port configuration including PoE port admin status, power limit and priority. Power Over Ethernet Configuration -> PoE Port Configuration Menu No. Admin Status Class Prio. Limit(mW) Pow.(mW) Vol.(V) Cur.(mA) --- ----- -------------- ----- ------ --------- --------- --------- -------- 1 Up Powered 2 Low 15400 3110 48.6 64 2 Up Not Powered 0 Low 15400 0 0 0 3 Up Powered 0 Low 15400 4656 48.5 96 4 Up Not Powered 0 Low 15400 0 0 0 5 Up Not Powered 0 Low 15400 0 0 0 6 Up Not Powered 0 Low 15400 0 0 0 -------------------------------- <COMMAND> --------------------------------- [N]ext Page Set PoE Port Admin [S]tatus [P]revious Page Set PoE Port Pr[i]ority Set PoE Port Power [L]imit [Q]uit to previous menu Command> 12 of 17
5. DHCP Server Configuration The DHCP Server is configured to support the PCs and the Avaya IP telephones in Figure 1. When an IP telephone initially sends an untagged DHCP request, the DHCP server associates this request with the 10.10.20.0 scope and returns a reply with Option 176 string, instructing the IP telephone to use VLAN ID 110 (as indicated in the first row of Table 3). The IP telephone receiving this reply will release the supplied IP address and issue a new DHCP request with VLAN ID 110. The Cisco Catalyst will relay this request to the DHCP server. The DHCP server will reply with an IP address from the 10.10.10.0 scope as well as several parameters in the Option 176 string (as indicated in the second row of Table 3 below). The IP telephone will use Option 176 parameters to register to the C-LAN in the Avaya G650 Media Gateway. Note that the PC will ignore the Option 176 values. Therefore, no new DHCP request is issued. Table 3 shows the DHCP summary configuration: DHCP Option 3 Option 176 String Notes Scope Router 10.10.20.0 10.10.20.1 L2QVLAN=110 For PCs and Phones 10.10.10.0 10.10.10.1 MCIPADD=10.10.10.10,TFTPSRVR=10.10.20.5 For IP telephones C-LAN IP: 10.10.10.10 Table 3 DHCP Configuration Summary 6. Configuring Cisco Catalyst 6509 The Cisco Catalyst 6509 being used in this configuration supports Layer 3 routing on its Multi- Layer Switch Feature card. In the sample configuration, VLAN 10 is configured for the Avaya S8500 Media Server and the IPSI of the Avaya G650 Media Gateway. VLAN 110 is configured for the IP telephones, the C-LAN and Media Processor of the Avaya G650 Media Gateway. VLAN 120 is configured for the PCs. The following shows the related Layer 3 configuration including DHCP relay. 10.10.20.5 is the IP address of the DHCP server. interface Vlan10 ip address 10.1.1.1 255.255.255.0 interface Vlan110 ip address 10.10.10.1 255.255.255.0 ip helper-address 10.10.20.5 interface Vlan120 ip address 10.10.20.1 255.255.255.0 VLAN 10 configuration VLAN 110 configuration DHCP Relay to the DHCP server. VLAN 120 configuration Port 4/26 on the Cisco Catalyst 6509 is connected to the M24PWR switch. The following screen shows how to configure port 4/26. The same configuration should also apply to any other ports connected to the M12PWR and M24PWR switches. To reduce broadcast/multicast messages from the other VLANs, port 4/26 is configured to support VLAN 1, 110 and 120 only. 13 of 17
Console> (enable) set vlan 1 4/26 Console> (enable) set trunk 4/26 dot1q on Console> (enable) clear trunk 4/26 2-109 Console> (enable) clear trunk 4/26 111-119 Console> (enable) clear trunk 4/26 121-1005 Configure native VLAN to 1 Enable 802.1q. Clear VLANs 2 to 109 Clear VLANs 111 to 119 Clear VLANs 121 to 1005 It is recommended to configure ports 4/46 and 4/47, which are connected to the C-LAN and Media Processor of the Avaya G650 Media Gateway, to 100 BaseT/Full Duplex to match the configuration on the C-LAN and Media Processor in Section 3. Below shows how to configure ports 4/46 and 4/47 to100 BaseT/Full duplex with VLAN 110. Console> (enable) set port speed 4/46-47 100 Console> (enable) set port duplex 4/46-47 full Console> (enable) set vlan 110 4/46-47 Set ports 4/46-47 to 100 BaseT Set ports 4/46-47 to Full duplex Set ports 4/46-47 to VLAN 110 The following shows the QoS configuration on the Cisco Catalyst 6509. In the sample configuration, Trust DiffServ is used for all the ports. Console> (enable) set qos enable Console> (enable) set qos acl ip layer3-dscp trust-dscp ip any any Console> (enable) commit qos acl all Console> (enable) set qos acl map layer3-dscp 4/1-48 Console> (enable) set qos acl map layer3-dscp 9/1-16 Console> (enable) set qos acl map layer3-dscp 1/1-2 Enable QoS Create ACL for L3 Apply ACL change Apply DiffServ ACL to all ports To prioritize VoIP traffic, VoIP DiffServ DSCP 48 must be mapped to a high CoS value. Use the command show qos maps config dscp-cos-map to check the DSCP to CoS mapping configuration. Use the command set qos dscp-cos-map to change the mapping. In the sample set command, DSCP 48 is mapped to CoS 6 (no change from default value). onsole> (enable) show qos maps config dscp-cos-map DSCP - CoS map: DSCP CoS -------------------------------- --- 0-7 0 8-15 1 16-23 2 24-31 3 32-39 4 40-47 5 48-55 6 56-63 7 Console> (enable) set qos dscp-cos-map 48:6 QoS dscp-cos-map set successfully. 14 of 17
Use the command show qos maps config cos-dscp-map to check the CoS to DSCP mapping configuration. Use the command set qos cos-dscp-map to change the mapping. It is recommended to map CoS 6 to DSCP 48 for consistency. In the sample set command, COS 6 is mapped to DSCP 48 (no change from default value). Console> (enable) show qos maps config cos-dscp-map CoS - DSCP map: CoS DSCP --- ---- 0 0 1 8 2 16 3 24 4 32 5 40 6 48 7 56 Console> (enable) set qos cos-dscp-map 0 8 16 24 32 40 48 56 QoS cos-dscp-map set successfully. 7. Verification Steps Verify that the Avaya S8500 Media server recognizes the Avaya G650 Media Gateway. Verify that all the IP telephones and softphones can register with the C-LAN of the Avaya G650 Media Gateway. Verify that an IP telephone and the attached PC are on different VLANs through the DHCP server. While generating data traffic to overload the link between the Cisco Catalyst 6509 and the MNO PoE switches, make a call and verify that voice quality is acceptable across the congested link. 8. Conclusion As illustrated by these Application Notes, MNO M12PWR and M24PWR switches work well with Avaya IP telephones and softphones. Avaya IP telephones can draw power from the MNO PoE switches. With the recommended QoS configuration, the MNO PoE switches can prioritize Avaya VoIP traffic over data traffic. 9. References [1] Title: Sample Avaya S8700 Media Server IP Connect Configuration Link: http://www1.avaya.com/enterprise/whitepapers/s8700ip.pdf 15 of 17
10. Glossary Technical Term LAN IPSI C-LAN MEDPRO Codec PoE QoS DiffServ DSCP CoS SIP Definition as it pertains to this document Local Area Network IP Server Interface Control-LAN Media Processor Coder/Decoder Power over Ethernet Quality of Service Differentiated Services Differentiated Services Code Point Class of Service Session Initiation Protocol 16 of 17
Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by and are registered trademarks or trademarks, respectively, of Avaya Inc. All other trademarks are the property of their respective owners. The information provided in these Application Notes is subject to change without notice. The configurations, technical data, and recommendations provided in these Application Notes are believed to be accurate and dependable, but are presented without express or implied warranty. Users are responsible for their application of any products specified in these Application Notes. Please e-mail any questions or comments pertaining to these Application Notes along with the full title name and filename, located in the lower right corner, directly to the Avaya Solution & Interoperability Test Lab at interoplabnotes@list.avaya.com 17 of 17