Application Notes for Avaya Communication Manager IP

Avaya Solution & Interoperability Test Lab

Application Notes for Avaya Communication Manager IP Telephony on Ethernet Private Lines Transported over a Lucent Technologies Metropolis DMXtend SONET Ring – Issue 1.0

Abstract These Application Notes describe a configuration where Avaya Communication Manager IP Telephony traffic traverses Ethernet private lines that are transported over a SONET ring. The SONET ring is composed of Lucent Technologies Metropolis DMXtend Access Multiplexers. The DMXtend Access Multiplexer is a SONET multiplexer that enables the transmission of traditional voice/TDM and private line services, and data services over SONET. In the compliance tested configuration, an Ethernet private line connects two Avaya Communication Manager systems located in two different sites, and another Ethernet private line connects Avaya IP Telephones in a remote site back to an Avaya Communication Manager system in a main site. During compliance testing, telephone calls traversing the Ethernet private lines were successfully completed and also maintained after UPSR protection switching occurred in the SONET ring. Information in these Application Notes has been obtained through compliance testing and additional technical discussions. Testing was conducted via the DeveloperConnection Program at the Avaya Solution and Interoperability Test Lab.

RL; Reviewed: SPOC 6/28/2005

Solution & Interoperability Test Lab Application Notes ©2005 Avaya Inc. All Rights Reserved.

1 of 25 LU-DMXT-ETH.doc




1. Introduction These Application Notes describe a compliance-tested configuration comprised of Avaya Media Servers, Avaya Media Gateways, and Lucent Technologies Metropolis DMXtend Access Multiplexers. The DMXtend Access Multiplexer is a SONET multiplexer that enables the transmission of traditional voice/TDM and private line services, and data services over SONET. These Application Notes focus on the configuration of Ethernet private lines that are connected to Avaya Communication Manager systems and transported over a SONET ring formed by DMXtend Access Multiplexers. Figure 1 illustrates a sample configuration consisting of:

• an Avaya S8500 Media Server, • an Avaya G650 Media Gateway, • an Avaya S8300 Media Server residing in an Avaya G350 Media Gateway, • Avaya IP Telephone, Avaya Digital Telephones, and analog telephones, • a laptop with an Avaya IP Softphone and an Avaya Modular Messaging client, • Lucent Technologies DMXtend Access Multiplexers, and • Extreme Networks Alpine 3808 and Summit 300-48 Switches.

Avaya Communication Manager runs on the S8500 Media Server and S8300 Media Server, though the solution described herein is also extensible to other Avaya Media Servers and Media Gateways. The Avaya S3400 Modular Messaging servers in Figure 1 are not the focus of these Application Notes, and are not described here. The network illustrated in Figure 1 is divided into three sites that are interconnected by a SONET ring. Site A and Site B contain independent Avaya Communication Manager systems, each with their own dial plans and extensions. An Ethernet private line connects the Alpine 3808 in Site A and the G350 Media Gateway in Site B, and is transported over the SONET ring. An Avaya H.323 IP trunk between the S8500 Media Server and S8300 Media Server is carried over this Ethernet private line. Another Ethernet private line connects the Alpine 3808 in Site A and the Summit 300-48 in Site C, and is also transported over the SONET ring. The Avaya IP Telephones connected to the Summit 300-48 in Site C are remoted stations of the Avaya Communication Manager in Site A.

SONET OC-48 RING

Avaya S8300 Media Server in Avaya G350 Media Gateway

VLAN 60

Avaya 4600 Series IP Telephones

VLAN 53

.…..

Avaya 6400 and 8400 Series Digital Telephones

.…..

Analog Telephones

.…..

Avaya G650Media Gateway

VLAN 50

Extreme Networks Alpine 3808

Avaya S8500Media Server

VLAN 50

GbEVLAN 101

FEFE

FE


VLAN 63

.…..

Avaya 6400 Series Digital Telephones

.…..

Analog Telephones

.…..

GbEVLAN 101

FE

LucentDMXtend

LucentDMXtend

LucentDMXtend

Extreme Networks Summit 300-48


VLAN 53

.…..

Site A

Laptop with Avaya IP Softphone and

Avaya Modular Messaging ClientVLAN 51

GbEVLANs 51, 53

15404

Extreme Networks Summit 300-48

CONSOLE

FE

FE

GbEVLANs 51, 53

FE

FE

Avaya S3400 Servers(running Avaya

Modular Messaging)VLAN 50

PSTN

Site B

Site C

1:2 1:1

Figure 1: Sample configuration







2. Equipment and Software Validated The following equipment and software/firmware were used for the sample configuration provided:

Equipment Software/Firmware Avaya S8500 Media Server 2.2 (R012x.02.0.111.4) Avaya G650 Media Gateway -

TN2312BP IP Server Interface 12 TN799DP C-LAN Interface 12 TN2302AP IP Media Processor HW11 FW95

HW03 FW93 TN2224CP Digital Line 15

TN793B Analog Line 5 Avaya S8300 Media Server 2.2 (R012x.02.0.111.4) Avaya G350 Media Gateway 23.19 (Media Gateway Processor)

MM711 Analog 17 MM712 DCP 5

Avaya 4600 Series IP Telephones 1.8.3 (4606) 1.8.3 (4612) 1.8.3 (4624)

1.8.2 (4602SW) 2.1.3 (4610SW) 2.1.3 (4620SW) 2.0.2 (4630SW)

Avaya 6400 Series Digital Telephones - Avaya 8400 Series Digital Telephones - Avaya IP Softphone 5.1 Service Pack 1 Avaya S3400 Servers 2.0 Avaya Modular Messaging Outlook Client 6.1.162.0 Extreme Networks Alpine 3808 7.3.2b3 Extreme Networks Summit 300-48 7.3e.2b4 Lucent Technologies Metropolis DMXtend Access Multiplexer

-

LNW1 SYSCTL 3.1.0 LNW41 OC-48 - LNW67 1GbE-SX 5.1.11.21

LNW70 100/1G-FXS 5.1.11.21 Lucent Technologies WaveStar CIT 14.00.00 Build 1063




3. Configure Avaya Communication Manager This section describes the steps for specifying IP codecs, and configuring IP network regions, H.323 IP trunks and signaling groups. The steps are performed from the System Access Terminal (SAT) interface and are generally applicable to Avaya Communication Manager in both Site A and Site B in the sample configuration; any differences are noted accordingly.

3.1. IP Codec Sets and IP Network Regions Enter the change ip-codec-set m command, where “m” is a number between 1 and 7, inclusive, and enter one or more codecs for the IP codec set. IP codec sets will be selected later in the IP network region form to define which codecs may be used within an IP network region and between IP network regions. In the screens below, IP codec set 1 contains G.711MU, while IP codec set 2 contains G.711MU and G.729. change ip-codec-set 1 Page 1 of 2 IP Codec Set Codec Set: 1 Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n 2 20 2: 3:

change ip-codec-set 2 Page 1 of 2 IP Codec Set Codec Set: 2 Audio Silence Frames Packet Codec Suppression Per Pkt Size(ms) 1: G.711MU n 2 20 2: G.729 n 2 20 3:

Enter the change ip-network-region n command, where “n” is a number between 1 and 250, inclusive.




On page 1 of the ip-network-region form, set Codec Set to the number of a configured IP codec set. change 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: 34 Audio PHB Value: 46 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 On Page 3 of the ip-network-region form, specify the IP codec set for every pair of source and destination IP network regions. In the example below, IP calls from IP network region 1 to IP network region 2 may use the codecs defined in IP codec set 2. change ip-network-region 1 Page 3 of 19 Inter Network Region Connection Management src dst codec direct Dynamic CAC rgn rgn set WAN WAN-BW-limits Intervening-regions Gateway 1 1 1 1 2 2 y :NoLimit 1 3




3.2. H.323 IP Trunks and Signaling Groups On the S8300 Media Server (Site B), enter the change node-names ip command. Specify a node name for the C-LAN board of the G650, and enter its IP address. The node name and IP address for procr (Processor Ethernet) is automatically set when the S8300 Media Server is configured with an IP address. change node-names ip Page 1 of 1 IP NODE NAMES Name IP Address Name IP Address G650-CLAN1A02 192.45 .50 .7 . . . default 0 .0 .0 .0 . . . procr 192.45 .60 .5 . . .

On the S8500 Media Server (Site A), enter the change node-names ip command. Specify node names and IP addresses for the Processor Ethernet of the S8300 Media Server and the C-LAN board, and enter their respective IP addresses. change node-names ip Page 1 of 1 IP NODE NAMES Name IP Address Name IP Address CLAN-1A02 192.45 .50 .7 . . . S8300-G350-ICC 192.45 .60 .5 . . . MEDPRO-1A03 192.45 .50 .8 . . . MEDPRO-1A13 192.45 .50 .9 . . . MEDPRO-1B03 192.45 .50 .10 . . . MEDPRO-1B13 192.45 .50 .11 . . . default 0 .0 .0 .0 . . . procr . . . . . .

Enter the add trunk-group p command, where “p” is an available trunk group number. On Page 1 of the trunk-group form, configure the following:

• Group Type – set to “isdn”. • Group Name – enter a meaningful name/description. • TAC – enter a Trunk Access Code that is valid under the provisioned dial plan. • Carrier Medium – set to “IP”. • Service Type – set to “tie”.

The following example shows the configuration of the IP trunk group on the S8500 Media Server. The IP configuration of the IP trunk group on the S8300 Media Server is the same, except possibly the Group Name.




add trunk-group 11 Page 1 of 22 TRUNK GROUP Gr Group Type: isdn CDR Repooup Number: 11 rts: y Group Name: H.323 Calls to S8300/G350 COR: 1 TN: 1 TAC: 111 Direction: two-way Outgoing Display? n Carrier Medium: IP Dial Access? n Busy Threshold: 255 Night Service: Queue Length: 0 Service Type: tie Auth Code? n TestCall ITC: rest Far End Test Line No: TestCall BCC: 4 TRUNK PARAMETERS Codeset to Send Display: 6 Codeset to Send National IEs: 6 Max Message Size to Send: 260 Charge Advice: none Supplementary Service Protocol: a Digit Handling (in/out): enbloc/enbloc Trunk Hunt: cyclical QSIG Value-Added?: n Digital Loss Group: 18 Incoming Calling Number - Delete: Insert: Format: Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0

Enter the add signaling-group q command, where “q” is an available signaling group number. On Page 1 of the signaling-group form, configure the following:

• Group Type – set to “h.323”. • Trunk Group for Channel Selection – enter the number of the trunk group (configured

above) to be associated with this signaling group. • Near-end Node Name – enter the node name of a local C-LAN board, or “procr” if the

local node is an S8300. • Near-end Listen Port – specify the local listen port, typically 1720. • Far-end Node Name – enter the node name of a C-LAN board or processor Ethernet on

the remote Avaya system. • Far-end Listen Port – specify the remote listen port, typically 1720. • Far-end Network Region – (optional) assign a network region to be associated with

calls to the remote system. The following example shows the configuration of the H.323 signaling group on the S8500. Note that the Far-end Network Region is set to 2. This means that from the perspective of the near-end system, the entire system at the far end of the IP trunk is considered to be in IP network region 2, as defined on the near-end system. The configuration of the H.323 signaling group on the S8300 Media Server is similar, with the node names and Far-end Network Region set to locally configured values.




add signaling-group 11 Page 1 of 5 SIGNALING GROUP Group Number: 11 Group Type: h.323 Remote Office? n Max number of NCA TSC: 0 SBS? n Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 11 Supplementary Service Protocol: a T303 Timer(sec): 10 Near-end Node Name: CLAN-1A02 Far-end Node Name: S8300-G350-ICC Near-end Listen Port: 1720 Far-end Listen Port: 1720 Far-end Network Region: 2 LRQ Required? n Calls Share IP Signaling Connection? n RRQ Required? n Bypass If IP Threshold Exceeded? n DTMF over IP: out-of-band Direct IP-IP Audio Connections? y IP Audio Hairpinning? y Interworking Message: PROGress

Enter the change trunk-group p command, where p is the number of the trunk group configured earlier. On Page 6 of the trunk-group form, add one or more trunk members by entering “IP” for Port and the number of the signaling group configured earlier for Sig Grp. change trunk-group 11 Page 6 of 22 TRUNK GROUP Administered Members (min/max): 0/0 GROUP MEMBER ASSIGNMENTS Total Administered Members: 0 Port Code Sfx Name Night Sig Grp 1: IP 11 2: IP 11 3: IP 11 4: IP 11 5: IP 11 6: IP 11 7: IP 11 8: IP 11 9: IP 11 10: IP 11 11: IP 11 12: IP 11 13: IP 11 14: IP 11 15: IP 11

3.3. Remote IP Stations The administration for the remote IP telephones in Site C is the same as the administration for the local IP telephones in Site A. Enter the command add station s, where s is an extension that




is valid under the provisioned dial plan of Avaya Communication Manager in Site A. On Page 1 of the station form, set Type to an Avaya 4600 Series IP Telephone type, enter a descriptive Name, and specify a Security Code. add station 50006 Page 1 of 4 STATION Extension: 50006 Lock Messages? n BCC: 0 Type: 4610 Security Code: 12345 TN: 1 Port: IP Coverage Path 1: COR: 1 Name: STA-50006 Remote Site Coverage Path 2: COS: 1 Hunt-to Station: STATION OPTIONS Loss Group: 19 Personalized Ringing Pattern: 1 Message Lamp Ext: 50006 Speakerphone: 2-way Mute Button Enabled? y Display Language: english Survivable GK Node Name: Media Complex Ext: IP SoftPhone? n

4. Configure Layer 2 and Layer 3 Switching and Routing In the sample configuration of Figure 1, Extreme Networks switches and the Avaya G350 Media Gateway perform the Layer 2 and Layer 3 switching and routing. The Alpine 3808 and G350 perform switching and routing within their respective sites, as well as routing between Site A and Site B. The Ethernet link that connects the Alpine 3808 in Site A and the Summit 300-48 in Site C carries VLANs 51 and 53, so that VLANs 51 and 53 in Site A are extended to Site C. As such, the Summit 300-48 in Site C only needs to perform Layer 2 switching, and routing for packets to/from Site C is provided by the Alpine 3808 in Site A.

4.1. Extreme Networks Alpine 3808 The following commands create and configure three VLANs on the Alpine 3808 at Site A: VLAN 50, VLAN 51, and VLAN 53. VLAN 50 is configured as an untagged VLAN on the ports (4:1-4:12) that are connected to the S8500, and G650 IPSI, C-LAN, and MedPro boards. VLAN 51 is configured as an untagged VLAN on the ports (4:17-4:32 and 5:1-5:32) that may connect to PCs, while VLAN 53 is configured as a tagged VLAN on the ports (5:1-5:32) that may connect to IP telephones. Note that in this example, ports 5:1-5:32 are configured with both VLAN 51 and VLAN 53; this enables the option of attaching a PC directly to an IP telephone that is physically connected to one of those ports.




create vlan vlan50 configure vlan vlan50 tag 50 configure vlan vlan50 add ports 4:1-4:12 untagged create vlan vlan51 configure vlan vlan51 tag 51 configure vlan vlan51 add ports 4:17-4:32,5:1-5:32 untagged create vlan vlan53 configure vlan vlan53 tag 53 configure vlan vlan53 add ports 5:1-5:32 tagged

The following commands create IP interfaces on VLAN 50, VLAN 51 and VLAN 53. These IP interfaces are the default gateways for IP endpoints on their respective VLANs. configure vlan vlan50 ipaddress 192.45.50.2 255.255.255.0 configure vlan vlan51 ipaddress 192.45.51.1 255.255.255.0 configure vlan vlan53 ipaddress 192.45.53.1 255.255.255.0

As mentioned above, the Ethernet link that connects the Alpine 3808 to the Summit 300-48 in Site C carries VLANs 51 and 53. The following commands configure VLAN 51 (untagged) and VLAN 53 (tagged) on the port (1:2) connected (through the SONET ring) to the Summit 300-48. configure vlan vlan51 add ports 1:2 untagged configure vlan vlan53 add ports 1:2 tagged

The following commands create VLAN 101, create an IP interface on VLAN 101, and configure VLAN 101 on the port (1:1) connected (through the SONET ring) to the G350 in Site B. create vlan101 configure vlan vlan101 tag 101 configure vlan vlan101 ipaddress 192.45.101.1 255.255.255.0 configure vlan vlan101 add ports 1:1 tagged

The following commands create static routes to Site B with the router interface of the G350 Media Gateway as the next hop. configure iproute add 192.45.60.0 255.255.255.0 192.45.101.2 configure iproute add 192.45.61.0 255.255.255.0 192.45.101.2 configure iproute add 192.45.63.0 255.255.255.0 192.45.101.2

The following commands enable IP forwarding on the VLANs. IP forwarding allows packets to be routed to/from the VLANs. enable ipforwarding vlan50 enable ipforwarding vlan51 enable ipforwarding vlan53 enable ipforwarding vlan101




4.2. Configure Avaya G350 Media Gateway This section describes the Layer 2 and Layer 3 switching and routing configuration on the Avaya G350 Media Gateway. The configuration of other parameters, such as the Media Gateway Controller list, is not described here, but may be found in the product documentation. The following commands create and configure three VLANs on the G350 at Site B: VLAN 60, VLAN 61, and VLAN 63. VLAN 60 is designated as the “ICC-VLAN”; the G350 communicates with the ICC (S8300 Media Server) over the ICC-VLAN. VLAN 61 is configured as an untagged VLAN on the ports (6/1 through 6/12) that may connect to PCs, while VLAN 63 is configured as a tagged VLAN on the ports (6/1 through 6/12) that may connect to IP telephones. Note that in this example, ports 6/1 through 6/12 are configured with both VLAN 61 and VLAN 63; this enables the option of attaching a PC directly to an IP telephone that is physically connected to one of those ports. G350-001(super)# set vlan 60 G350-001(super)# interface vlan 60 G350-001(super-if:Vlan 60)# ip address 192.45.60.2 255.255.255.0 G350-001(super-if:Vlan 60)# icc-vlan G350-001(super-if:Vlan 60)# exit G350-001(super)# set vlan 61 G350-001(super)# set port vlan 61 6/1-12 G350-001(super)# set vlan 63 G350-001(super)# set port static-vlan 6/1-12 63 G350-001(super)# set trunk 6/1-12 off G350-001(super)# set port vlan-binding-mode 6/1-12 static

The following commands create IP interfaces on VLAN 61 and VLAN 63. These IP interfaces are the default gateways for IP endpoints on their respective VLANs. G350-001(super)# interface vlan 61 G350-001(super-if:Vlan 61)# ip address 192.45.61.1 255.255.255.0 G350-001(super-if:Vlan 61)# exit G350-001(super)# interface vlan 63 G350-001(super-if:Vlan 63)# ip address 192.45.63.1 255.255.255.0 G350-001(super-if:Vlan 63)# exit

The following commands create VLAN 101 and an IP interface on VLAN 101. G350-001(super)# set vlan 101 G350-001(super)# interface vlan 101 G350-001(super-if:Vlan 101)# ip address 192.45.101.2 255.255.255.0 G350-001(super-if:Vlan 101)# exit

The following commands configure VLAN 101 on the port (6/51) connected (through the SONET ring) to the Alpine 3808, and configure the port as an 802.1Q trunk. G350-001(super)# set port vlan 101 6/51 G350-001(super)# set trunk 6/51 dot1q G350-001(super)# set port vlan-binding-mode 6/51 static




The following commands create static routes to Site A (and thus Site C) with the Alpine 3808 as the next hop. G350-001(super)# ip route 192.45.50.0 255.255.255.0 192.45.101.1 G350-001(super)# ip route 192.45.51.0 255.255.255.0 192.45.101.1 G350-001(super)# ip route 192.45.53.0 255.255.255.0 192.45.101.1

4.3. Extreme Networks Summit 300-48 The following commands create and configure two VLANs on the Summit 300-48 at Site C: VLAN 51, and VLAN 53. VLAN 51 is configured as an untagged VLAN on the ports (1:1-1:12) that may connect to PCs, while VLAN 53 is configured as a tagged VLAN on the ports (1:1-1:12) that may connect to IP telephones. Note that in this example, ports 1:1-1:12 are configured with both VLAN 51 and VLAN 53; this enables the option of attaching a PC directly to an IP telephone that is physically connected to one of those ports. create vlan vlan51 configure vlan vlan51 tag 51 configure vlan vlan51 add ports 1:1-1:12 untagged create vlan vlan53 configure vlan vlan53 tag 53 configure vlan vlan53 add ports 1:1-1:12 tagged

As mentioned above, the Ethernet link that connects the Summit 300-48 to the Alpine 3808 in Site A carries VLANs 51 and 53. The following commands configure VLAN 51 (untagged) and VLAN 53 (tagged) on the port (1:52) connected (through the SONET ring) to the Alpine 3808. configure vlan vlan51 add ports 1:52 untagged configure vlan vlan53 add ports 1:52 tagged

5. Configure Lucent DMXtend Access Multiplexer This section describes the steps for configuring the DMXtend Access Multiplexers to transport Ethernet private lines over the SONET ring.

5.1. Entry and Exit Nodes on the SONET Ring “Add/drop” cross-connections must be configured on the DMXtend Access Multiplexers where the Ethernet private line enters and exits the SONET ring. For example, in the sample configuration, “add/drop” cross-connections must be configured on the DMXtend Access Multiplexers in Site A and Site B for the Ethernet private line between those two sites. Similarly, “add/drop” cross-connections must be configured on the DMXtend Access Multiplexers in Site A and Site C for the Ethernet private line between those two sites. The following steps apply to each of the Ethernet private lines.




Step Description 1. Launch the WaveStar CIT application and log in with the appropriate credentials.

2. Double click on one of the entry/exit DMXtend Access Multiplexers to launch the System View

for the selected DMXtend. Log in to the System View with the appropriate credentials.

3. In the System View main window, select “Cross-Connections” from the Configuration menu.

4. In the Cross-Connection Wizard window, select “Create a new cross-connection” and click on “Next >”.




Step Description 5. Set Rate to “STS1” and select “UPSR Ring Add/Drop” for Type of Cross-connection. Click

on “Next >”.

6. Click on “Select…”.




Step Description 7. In the UPSR Tributary window, select a ring port and then the first Tributary of a range of 21*

consecutive available tributaries. Click on “Select”. In the example below, the m-1-2 notation represents the second STS1 on the OC-48. Note this specific STS1 will be used throughout the SONET ring to transport the Ethernet private line. In the next step, the 20 consecutive STS1 that follow this STS1 will be added so the Ethernet private line will actually use 21 STS1 throughout the SONET ring.

* DMXtend fixes the number of tributaries at 21. The rate of each STS1 is 51.840 Mbps, so the aggregation of 21 STS1 tributaries equate approximately to the 1 GbE rate.




Step Description 8. Back in the Cross-Connection Wizard window, note that the STS1 for main-2 was

automatically set to the same STS1 as main-1. Set Range to “21”, and click on “Select…”.

9. In the Add/Drop Tributary window, select the VCG corresponding to the Ethernet port connected to the Ethernet switch/router (Alpine 3808, G350 Media Gateway, or Summit 300-48 in the sample configuration). Select the first Tributary (note that only the first tributary is available) and click on “Select”.




Step Description 10. Back in the Cross-Connection Wizard window, click on “Next >”.

11. Enter a meaningful name/description for Circuit Identifier, and click on “Finish”.

12. Repeat steps 2 through 11 for the entry/exit DMXtend Access Multiplexer at the other end of the Ethernet private line.

5.2. Intermediate Nodes in the SONET Ring “Through” cross-connections must be configured on the DMXtend Access Multiplexers that the Ethernet private line traverses on the SONET ring between entry and exit. For example, in the sample configuration, a “through” cross-connection must be configured on the DMXtend Access Multiplexer in Site C for the Ethernet private line between Site A and Site B. Similarly, a “through” cross-connection must be configured on the DMXtend Access Multiplexer in Site B for the Ethernet private line between Site A and Site C. The following steps apply to each of the Ethernet private lines. Step Description

1. In the WaveStar CIT main window, double click on one of the intermediate DMXtend Access Multiplexers to launch its System View. Log in to the System View with the appropriate credentials.

2. In the System View main window, select “Cross-Connections” from the Configuration menu.

3. In the Cross-Connection Wizard window, select “Create a new cross-connection” and click on “Next >”.







Step Description 4. Set Rate to “STS1” and select “2-Way Point-to-Point, Through” for Type of Cross-

connection. Click on “Next >”.

5. Click on “Select…”.




Step Description 6. In the Source Tributary window, select a ring port and the same starting STS1 that was selected

at the entry/exit node in Step 7 of Section 5.1. Click on “Select”.

7. Back in the Cross-Connection Wizard window, note that the STS1 for main-2 was automatically set to the same STS1 as main-1. Set Range to “21”, and click on “Next >”.




Step Description 8. Enter a meaningful name/description for Circuit Identifier, and click on “Finish”.

9. Repeat steps 1 through 8 for each intermediate DMXtend Access Multiplexer (applicable to SONET rings with more than three nodes).




6. Interoperability Compliance Testing The interoperability compliance testing focused on verifying site-to-site connectivity and interface compatibility.

6.1. General Test Approach The general approach was to place calls between sites over the Ethernet private lines transported over the SONET ring. The main objectives were to verify that:

• Calls between Site A and Site B, between Site A and C, and between Site B and Site C are successfully completed and maintained.

• Calls between each site and the PSTN are successfully completed and maintained. • When Unidirectional Path Switched Ring (UPSR) protection switching occurs on the

SONET ring, active calls between sites are maintained. • Calls between sites are successfully completed and maintained after recovering from

failures such as Ethernet cable disconnects, reset of the G350 Media Gateway, and resets of the Gigabit Ethernet circuit packs on the DMXtend Access Multiplexers.

• A remoted IP telephone user in Site C successfully retrieves voice mail from the Avaya Modular Messaging servers in Site A.

• Calls may be forwarded from a phone in Site A to a remoted IP telephone in Site C.

6.2. Test Results All test cases completed successfully. The types of calls placed included calls between sites, call transfers to phones within the same site and to remoted IP telephones, and conference calls involving parties from all three sites. In addition, the calls were placed with different codecs (G.711MU and G.729), silence suppression on and off, and in-band and out-of-band DTMF over IP. The DMXtend Access Multiplexer is capable of performing Layer 2 switching and 802.1p QoS, but this functionality is not required in the configuration described in these Application Notes (since the Avaya G350 Media Gateway, Alpine 3808, and Summit 300-48 provided the Layer 2 functionality). During the compliance testing, 802.1p QoS testing was also performed using the same physical infrastructure described in these Application Notes, but with a different transport configuration (a 1 Gb/s “shared packet ring” instead of a 1 Gb/s private line). In the “shared packet ring” configuration, Layer 2 switching was enabled and configured on the DMXtend Access Multiplexers and point-to-multipoint cross-connections were created (versus the point-to-point and through cross-connections of the private line configuration). In addition, the DMXtend Access Multiplexers were configured to recognize 802.1p values in incoming VLAN-tagged Ethernet frames and apply the appropriate QoS treatment according to those values. For the QoS testing, phone calls were successfully completed with good voice quality when 1.1 Gb/s of competing low priority data traffic was transmitted over the 1 Gb/s shared packet ring.




7. Verification Steps The following steps may be used to verify the configuration:

• From the SAT, enter the command status signaling-group s, where s is the number of the H.323 signaling group, and verify that the Group State is “in service”.

• From the SAT, enter the command status trunk-group t, where t is the number of the H.323 IP trunk group, and verify that the Service States of all trunks are “in-service/idle” or “in-service/active”.

• Verify dial-tone on the remoted IP telephones. • Place calls between sites and verify successful completion.

8. Support For technical support on Lucent Technologies Metropolis DMX Access Multiplexer products, consult the support pages at http://www.lucent.com/support or contact Lucent customer support at (866) 237-4448.

9. Conclusion These Application Notes illustrate a configuration where Avaya Communication Manager IP Telephony traffic traverses Ethernet private lines that are transported over a SONET ring composed of Lucent Technologies Metropolis DMXtend Access Multiplexers. The DMXtend Access Multiplexer is a SONET multiplexer that enables the transmission of traditional voice/TDM and private line services, and data services over SONET. During compliance testing, telephone calls traversing the Ethernet private lines were successfully completed and also maintained after UPSR protection switching occurred in the ring.

10. Additional References Product documentation for Avaya products may be found at http://support.avaya.com. Product documentation for Lucent Technologies products may be found at http://www.lucent.com/support.

http://www.lucent.com/support

http://support.avaya.com/

http://www.lucent.com/support




©2005 Avaya Inc. All Rights Reserved. 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 DeveloperConnection Program at [email protected].

Documents

Application Notes for Avaya Communication Manager IP