application notes for configuring ... - devconnect program

Avaya Solution & Interoperability Test Lab

Application Notes for Configuring Avaya Communication Manager T1 and FXO/FXS Analog Private Lines over a Lucent Technologies Metropolis DMXtend SONET Ring – Issue 1.0

Abstract These Application Notes describe the procedures for configuring Avaya Communication Manager T1 and FXO/FXS analog private lines 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. In the compliance tested configuration, a T1 private line connects two Avaya Communication Manager systems located in two different sites, and a FXO/FXS private line connects analog telephones in a remote site back to Avaya Communication Manager in a main site. During compliance testing, telephone calls traversing the T1 and FXO/FXS private lines were successfully completed and also maintained after UPSR protection switching occurred in the 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 28 LU-DMXT-T1.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 T1 (ISDN PRI and E&M Wink Start) and FXO/FXS 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 Telephones, Avaya Digital Telephones, and analog telephones, • Lucent Technologies DMXtend Access Multiplexers, and • Adtran Atlas 550 Integrated Access Devices (IADs).

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 and the Extreme Networks Alpine 3808 Switch 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. A T1 line connects the S8500 Media Server in Site A and the S8300 Media Server in Site B, and is transported over the SONET ring. Site C contains analog telephones that are remoted stations of Avaya Communication Manager in Site A. The remoted analog telephones connect to the FXS interface ports of the Atlas 550, which in turn multiplexes the FXS interface ports onto DS0 channels in a T1 line. The T1 line is transported over the SONET ring between Site A and Site C. The Atlas 550 in Site A demultiplexes the DS0 channels onto FXO interface ports, which in turn connect to analog ports on the G650 Media Gateway. In this document, the T1 line between Site A and Site C is referred to as an FXO/FXS line to differentiate it from the T1 ISDN-PRI and E&M Wink Start lines between Site A and Site B.

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

T1

FEFE

FE

T1

FXO

Avaya 4600 Series IP Telephones

VLAN 63

.…..

Avaya 6400 Series Digital Telephones

.…..

Analog Telephones

.…..

T1

FE

LucentDMXtend

LucentDMXtend

LucentDMXtend

Analog Telephones

.…..

Site A

FXS

T1

Adtran Atlas 550

Adtran Atlas 550

FE

FE

Avaya S3400 Servers(running Avaya

Modular Messaging)VLAN 50

PSTN

Site B

Site C

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

TN464GP DS1 Interface 17 Avaya S8300 Media Server 2.2 (R012x.02.0.111.4) Avaya G350 Media Gateway 23.19 (Media Gateway Processor)

MM710 DS1 11 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 S3400 Servers 2.0 Extreme Networks Alpine 3808 7.3.2b3 Lucent Technologies Metropolis DMXtend Access Multiplexer

-

LNW1 SYSCTL 3.1.0 LNW41 OC-48 -

LNW112 16DS1PM 15.0.1 Lucent Technologies WaveStar CIT 14.00.00 Build 1063 Adtran Atlas 550 Integrated Access Device C.09.03




3. Configure Avaya Communication Manager

3.1. T1 ISDN-PRI and E&M Wink Start Lines This section describes the steps for configuring DS1 circuit packs, signaling groups, and trunk groups on each side, namely the S8500 Media Server and G650 Media Gateway in Site A and the S8300 Media Server and G350 Media Gateway in Site B. 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.1. T1 ISDN-PRI Enter the list configuration all command and note the Board Number of the DS1 circuit pack to be configured. list configuration all Page 3 SYSTEM CONFIGURATION Board Assigned Ports Number Board Type Code Vintage u=unassigned t=tti p=psa 01A10 ANALOG LINE TN793B 000005 u u u u u u u u u u u u u u u u u u u u u u u u 01A11 ANALOG LINE TN746B 000019 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 01A12 DS1 INTERFACE TN464GP HW06 FW017 u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u 01A13 IP MEDIA PROCESSOR TN2302AP HW03 FW093 01 02 03 04 05 06 07 08

Enter the add ds1 xxxxx command, where xxxxx is the board number of the DS1 circuit pack. On Page 1 of the ds1 form, configure the following:

• Name – enter a meaningful/description. • Line Coding – ensure that both sides of the ISDN-PRI are set to the same line coding. • Framing Mode – ensure that both sides of the ISDN-PRI are set to the same framing

mode. • Signaling Mode – set to “isdn-pri”. • Connect – set to “pbx”. • Interface – set to “network” on one side of the ISDN-PRI and “user” on the other side.

In the sample configuration, Site A is set to “network” and Site B is set to “user”.




add ds1 01A12 Page 1 of 2 DS1 CIRCUIT PACK Location: 01A12 Name: T1-ISDN-PRI Bit Rate: 1.544 Line Coding: b8zs Line Compensation: 1 Framing Mode: esf Signaling Mode: isdn-pri Connect: pbx Interface: network TN-C7 Long Timers? n Country Protocol: 1 Interworking Message: PROGress Protocol Version: a Interface Companding: mulaw CRC? n Idle Code: 11111111 DCP/Analog Bearer Capability: 3.1kHz T303 Timer(sec): 4 Slip Detection? n Near-end CSU Type: other

Enter the add trunk-group m command, where “m” 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 “PRI/BRI”. • Service Type – set to “tie”.

add trunk-group 1 Page 1 of 22 TRUNK GROUP Group Number: 1 Group Type: isdn CDR Reports: y Group Name: ISDN-PRI to Site B COR: 1 TN: 1 TAC: 101 Direction: two-way Outgoing Display? n Carrier Medium: PRI/BRI 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: 13 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 n command, where “n” is an available signaling group number. On Page 1 of the signaling-group form, configure the following:

• Group Type – set to “isdn-pri”. • Primary D-Channel – enter xxxxxyy, where xxxxx is the board number of the DS1

circuit pack configured earlier, and yy is the number of the ISDN-PRI D-Channel (the 24th channel in T1 ISDN-PRI).

• Trunk Group for Channel Selection – enter the number of the trunk group (configured above) to be associated with this signaling group.

add signaling-group 1 Page 1 of 5 SIGNALING GROUP Group Number: 1 Group Type: isdn-pri Associated Signaling? y Max number of NCA TSC: 0 Primary D-Channel: 01A1224 Max number of CA TSC: 0 Trunk Group for NCA TSC: Trunk Group for Channel Selection: 1 Supplementary Service Protocol: a Network Call Transfer? n

Enter the change trunk-group m command, where m is the number of the trunk group configured earlier in this section. On Page 6 of the trunk-group form, add one or more trunk members by entering:

• xxxxxzz, where xxxxx is the board number of the DS1 circuit pack configured earlier in this section, and zz is a channel in the T1 ISDN-PRI , and

• the number of the signaling group configured earlier in this section for Sig Grp. The example below shows the assignment of the first 15 channels, but additional channels, up to 23 for a T1 ISDN-PRI, may be assigned in subsequent pages of the trunk-group form. change trunk-group 1 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: 1A1201 TN464 G 1 2: 1A1202 TN464 G 1 3: 1A1203 TN464 G 1 4: 1A1204 TN464 G 1 5: 1A1205 TN464 G 1 6: 1A1206 TN464 G 1 7: 1A1207 TN464 G 1 8: 1A1208 TN464 G 1 9: 1A1209 TN464 G 1 10: 1A1210 TN464 G 1 11: 1A1211 TN464 G 1 12: 1A1212 TN464 G 1 13: 1A1213 TN464 G 1 14: 1A1214 TN464 G 1 15: 1A1215 TN464 G 1




3.1.2. T1 E&M Enter the list configuration all and note the Board Number of the DS1 circuit pack to be configured. list configuration all SYSTEM CONFIGURATION Board Assigned Ports Number Board Type Code Vintage u=unassigned t=tti p=psa 01B10 ANALOG LINE TN793B 000002 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 01B11 ANALOG LINE TN746B 000019 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 01B12 DS1 INTERFACE TN464GP HW02 FW017 u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u 01B13 IP MEDIA PROCESSOR TN2302AP HW03 FW093 01 02 03 04 05 06 07 08 01A IP SERVER INTFC TN2312BP HW36 FW012 01 02 03 04 05 06 07 08

Enter the add ds1 xxxxx command, where xxxxx is the board number of the DS1 circuit pack. On Page 1 of the ds1 form, configure the following:

• Name – enter a meaningful/description. • Line Coding – ensure that both sides of the T1 E&M line are set to the same line coding. • Framing Mode – ensure that both sides of the T1 E&M line are set to the same framing

mode. • Signaling Mode – set to “robbed-bit”.

add ds1 01B12 Page 1 of 2 DS1 CIRCUIT PACK Location: 01B12 Name: T1-RB Bit Rate: 1.544 Line Coding: b8zs Line Compensation: 1 Framing Mode: esf Signaling Mode: robbed-bit Interface Companding: mulaw Idle Code: 11111111 Slip Detection? n Near-end CSU Type: other




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 “tie”. • Group Name – enter a meaningful name/description. • TAC – enter a Trunk Access Code that is valid under the provisioned dial plan. • Service Type – set to “rbavd”. • Trunk Type (in/out) – set to “wink/wink”.

add trunk-group 2 Page 1 of 20 TRUNK GROUP Group Number: 2 Group Type: tie CDR Reports: y Group Name: E&M to Site B COR: 1 TN: 1 TAC: 102 Direction: two-way Outgoing Display? n Trunk Signaling Type: Dial Access? n Busy Threshold: 255 Night Service: Queue Length: 0 Incoming Destination: Comm Type: rbavd Auth Code? n Trunk Flash? n BCC: 0 TRUNK PARAMETERS Trunk Type (in/out): wink/wink Incoming Rotary Timeout(sec): 5 Outgoing Dial Type: tone Incoming Dial Type: tone Wink Timer(msec): 300 Disconnect Timing(msec): 500 Digit Treatment: Digits: Sig Bit Inversion: none Analog Loss Group: 9 Digital Loss Group: 13 Incoming Dial Tone? y Bit Rate: 1200 Synchronization: async Duplex: full Disconnect Supervision - In? y Out? n Answer Supervision Timeout: 0 Receive Answer Supervision? y

On Page 4 of the trunk-group form, add one or more trunk members by entering xxxxxzz, where xxxxx is the board number of the DS1 circuit pack configured earlier in this section, and zz is a channel in the T1. The example below shows the assignment of the first 15 channels, but additional channels, up to 24 for T1 E&M, may be assigned in subsequent pages of the trunk-group form.




add trunk-group 2 Page 4 of 20 TRUNK GROUP Administered Members (min/max): 0/0 GROUP MEMBER ASSIGNMENTS Total Administered Members: 0 Port Code Sfx Name Night Mode Type Ans Delay 1: 01B1201 TN464 G 2: 01B1202 TN464 G 3: 01B1203 TN464 G 4: 01B1204 TN464 G 5: 01B1205 TN464 G 6: 01B1206 TN464 G 7: 01B1207 TN464 G 8: 01B1208 TN464 G 9: 01B1209 TN464 G 10: 01B1210 TN464 G 11: 01B1211 TN464 G 12: 01B1212 TN464 G 13: 01B1213 TN464 G 14: 01B1214 TN464 G 15: 01B1215 TN464 G

3.2. FXO/FXS Line This section describes the steps for configuring the remoted analog phone extensions in Site C. The steps are performed from the SAT interface of the Avaya S8500 Media Server in Site A. Enter the list configuration all command and note the Board Number of the analog line circuit pack to which the remoted analog phones are to be connected. list configuration all Page 3 SYSTEM CONFIGURATION Board Assigned Ports Number Board Type Code Vintage u=unassigned t=tti p=psa 01A10 ANALOG LINE TN793B 000005 u u u u u u u u u u u u u u u u u u u u u u u u 01A11 ANALOG LINE TN746B 000019 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 01A12 DS1 INTERFACE TN464GP HW06 FW017 u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u u 01A13 IP MEDIA PROCESSOR TN2302AP HW03 FW093 01 02 03 04 05 06 07 08

Enter the command add station s, where s is an extension that is valid under the provisioned dial plan of the Avaya Communication Manager in Site A. On Page 1 of the station form, set Type




to an analog telephone set type, set Port to xxxxxrr, where xxxxx is the board number of the analog line circuit pack and rr is an available port on the analog line circuit pack, and enter a descriptive Name. add station 50107 Page 1 of 3 STATION Extension: 50107 Lock Messages? n BCC: 0 Type: 2500 Security Code: TN: 1 Port: 01A1001 Coverage Path 1: COR: 1 Name: Remote analog station 1 Coverage Path 2: COS: 1 Hunt-to Station: Tests? y STATION OPTIONS Loss Group: 1 Message Waiting Indicator: none Off Premises Station? n

4. Configure Lucent DMXtend Access Multiplexer This section describes the steps for configuring the DMXtend Access Multiplexers to transport T1 and FXO/FXS lines over the SONET ring.

4.1. T1 Equipment Configuration Step Description

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

2. Double click on a DMXtend Access Multiplexer to launch its System View. Log in to the System View with the appropriate credentials.

3. In the System View main window, select “Equipment” from the Configuration menu.




Step Description 4. In the left pane of the Configure Equipment window, select a DS1 circuit pack and expand the

tree down to the VT Group level. For a T1 ISDN-PRI or E&M Wink Start line, select the DS1 port that is connected to the DS1 circuit pack configured in Section 3.1. For an FXO/FXS line, select the DS1 port that is connected to the Atlas 550. Click on “Select”.




Step Description 5. In the right pane of the Configure Equipment window, set the Signal Format and Line Code

to match those of the connected DS1 port on the G650, G350, or Atlas 550. Select “This Port” for Apply To:, and click on “Apply” and then “Close”.

6. Repeat steps 2 through 5 for the other DMXtend Access Multiplexers with DS1 circuit packs.

4.2. Entry and Exit Nodes on the SONET Ring “Add/drop” cross-connections must be configured on the DMXtend Access Multiplexers where the T1 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 T1 ISDN-PRI and E&M Wink Start lines. Similarly, “add/drop” cross-connections must be configured on the DMXtend Access Multiplexers in Site A and Site C for the FXO/FXS line. The following steps apply to each of the T1 and FXO/FXS lines. Step Description

1. At one of the entry/exit DMXtend Access Multiplexers, in the System View main window, select “Cross-Connections” from the Configuration menu.




Step Description 2. In the Cross-Connection Wizard window, select “Create a new cross-connection” and click

on “Next >”.

3. Set Rate to “VT1.5” and select “UPSR Ring Add/Drop” for Type of Cross-connection. Click on “Next >”.




Step Description 4. Set Range to “Single VT” and click on “Select…”.

5. In the UPSR Tributary window, select a ring port and expand the tree down to the VT Group level. Select a VT Group and an available Tributary within the VT Group. Click on “Select”. In the example below, the m1-1-1-1-1 notation represents the Circuit Pack-Port-STS1-VT Group-Tributary. Note the STS1-VT Group-Tributary number because this specific tributary (the first tributary in the first VT Group in the first STS1 on the OC-48) will be used throughout the SONET ring to transport the T1 or FXO/FXS line.




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

automatically set to the same tributary as main-1. Click on “Select…”.

7. In the Add/Drop Tributary window, locate the DS1 port configured earlier in Step 5 of Section 4.1. Select the Tributary and click on “Select”.




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

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

10. Repeat steps 1 through 9 at the other entry/exit DMXtend Access Multiplexer.

4.3. Intermediate Nodes in the SONET Ring “Through” cross-connections must be configured on the DMXtend Access Multiplexers that the T1 or FXO/FXS line traverses on the SONET ring between entry and exit. For example, in the sample configuration, “through” cross-connections must be configured on the DMXtend Access Multiplexer in Site C for the T1 ISDN-PRI and E&M Wink Start lines between Site A and Site B. Similarly, a “through” cross-connection must be configured on the DMXtend Access Multiplexer in Site B for the FXO/FXS line between Site A and Site C. The following steps apply to each of the T1 and FXO/FXS lines. Step Description

1. At an intermediate DMXtend Access Multiplexer, in the System View main window, select “Cross-Connections” from the Configuration menu.

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







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

connection. Click on “Next >”.

4. Set Range to “Single VT” and click on “Select…”.




Step Description 5. In the Source Tributary window, select a ring port and the same tributary that was selected at

the entry/exit node in Step 5 of Section 4.2. Click on “Select”.

6. Back in the Cross-Connection Wizard window, note that the tributary for main-2 was automatically set to the same tributary as main-1. Click on “Next >”.




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

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




5. Configure Adtran Atlas 550 Integrated Access Device This section describes the steps for configuring the Atlas 550 to multiplex/demultiplex FXO/FXS interface ports onto/from DS0 channels in a T1. The steps are applicable to both Atlas 550 devices in the sample configuration; any differences are noted accordingly. Step Description

1. Telnet into the Atlas 550 console and log in with the appropriate credentials.

2. Select Modules on the left pane and tab over to a T1/PRI card row on the right pane. Select [+] on the row and press Enter. Atlas-550-SiteA/Modules[Ntw1]/T1/PRI-1 Menus System Info │ Slt Type Menu Alarm Test State Status Rev System Status │ Slt0 Sys Ctrl [+] OK n/a ONLINE Online P System Config │ Ntw1 T1/PRI-1 [+] [OK] [OFF] ONLINE Online A System Utility│ Ntw2 T1/PRI-1 [+] [ALARM] [OFF] ONLINE Online A Modules │ Slt1 FXS-4 [+] OK [OFF] ONLINE Online R Packet Manager│ Rsc1 EMPTY ONLINE Empty - Router │ Slt2 EMPTY ONLINE Empty - Dedicated Maps│ Rsc2 EMPTY ONLINE Empty - Circuit Status│ Slt3 FXO-4 [+] OK [OFF] ONLINE Online P Dial Plan │ Rsc3 EMPTY ONLINE Empty - │ Slt4 EMPTY ONLINE Empty - │ Rsc4 EMPTY ONLINE Empty - │ │ │ │ │ │ │ │ │ SYS: OK NETWK1:ONLN NETWK2:ALRM 1: OK 2: -- 3: OK 4: -- Access menus for Network T1 ^Z=help 16:06




Step Description 3. Select T1-PRI Menus on the left pane and tab over to Configuration [+] on the right pane, and

press Enter. Atlas-550-SiteA/Modules[Ntw1]/T1/PRI-1 Menus/Configuration T1/PRI-1 Menus│ Info [+] Module Alarms │ Alarm Status [+] Test Activity │ DS0 Status [+] │ DS0 Alarms [+] │ Sig Status [+] │ Performance Curr [+] │ Performance 15Min [+] │ Performance 24Hr [+] │ Configuration [+] │ Test [+] │ │ │ │ │ │ │ │ │ │ │ SYS: OK NETWK1:ONLN NETWK2:ALRM 1: OK 2: -- 3: OK 4: -- Port Configuration ^Z=help 16:01

4. Select Configuration on the left pane and tab over to the right pane. Enter a descriptive Port

Name and ensure that both Atlas 550 devices are set to the same Frame and Code values as the values set on the DS1 circuit packs on the DMXtend Access Multiplexers. Atlas-550-SiteA/Modules[Ntw1]/T1/PRI-1 Menus/Configuration[1] Info │ Prt Port Name Frame Code Tx Yel Tx PRM LBO LB Accept P Alarm Status │ 1 T1/PRI ESF B8ZS On Off 0 dB Accept DS0 Status │ DS0 Alarms │ Sig Status │ Performance Curr │ Performance 15Min│ Performance 24Hr │ Configuration │ Test │ │ │ │ │ │ │ │ │ │ │ │ SYS: OK NETWK1:ONLN NETWK2:ALRM 1: OK 2: -- 3: OK 4: -- Port Configuration ^Z=help 15:52




Step Description 5. Press Esc as many times as necessary to return to the top-level menu. Select Dedicated Maps

on the left pane and tab over to Create/Edit Maps [+] on the right pane, and press Enter. A Dedicated Map will be created in the subsequent steps to map analog phone ports to DS0s in the T1. Atlas-550-SiteA/Dedicated Maps/Create/Edit Maps System Info │ Activate Map AUTO System Status │ Current Map Map 1 System Config │ Create/Edit Maps [+] System Utility│ Modules │ Packet Manager│ Router │ Dedicated Maps│ Circuit Status│ Dial Plan │ │ │ │ │ │ │ │ │ │ │ │ SYS: OK NETWK1:ONLN NETWK2:ALRM 1: OK 2: -- 3: OK 4: -- ^Z=help 16:18

6. Select and Enable a map row on the right pane, and press Enter on the Connects column entry.

Atlas-550-SiteA/Dedicated Maps/Create/Edit Maps[1]/Connects Create/Edit Maps│ Map Name Sort TO/FROM Connects Activate Time Enbl Day │ 1 Map 1 FROM [Cncts=0] 00:00:00 [Enable] │ 2 Map 2 FROM [Cncts=0] 00:00:00 [Disabl] │ 3 Map 3 FROM [Cncts=0] 00:00:00 [Disabl] │ 4 Map 4 FROM [Cncts=0] 00:00:00 [Disabl] │ 5 Map 5 FROM [Cncts=0] 00:00:00 [Disabl] │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ SYS: OK NETWK1:ONLN NETWK2:ALRM 1: OK 2: -- 3: OK 4: -- ^Z=help 16:21




Step Description 7. On the Atlas 550 in Site A, select Connects on the left pane, and configure the following:

• FROM Slt and Port: select an FXO card and port. • TO Slt/S: select a T1/PRI card • To Config: Specify a DS0 in the T1

Atlas-550-SiteA/Dedicated Maps/Create/Edit Maps[1]/Connects[1] Connects│ # FROM Slt Port TO Slt/S Prt/PEP From Config To Config SIG Enbl Day│ 1 S3)FXO-4 1)FXO 3 N1)T1/PR 1)T1/PR [Port=1] [DS0=1] │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ SYS: OK NETWK1:ONLN NETWK2:ALRM 1: OK 2: -- 3: OK 4: -- INS/DEL ^Z=help 16:30

On the Atlas 550 in Site C, select Connects on the left pane, and configure the following:

• FROM Slt and Port: select an FXS card and port. • TO Slt/S: a T1/PRI card • To Config: Specify the same DS0 that was specified on the Atlas 550 in Site A.

Atlas-55 -C/Dedicated Maps/Create/E0-Site dit Maps[1]/Connects[1] Connects│ # FROM Slt Port TO Slt/S Prt/PEP From Config To Config SIG Enbl Day│ 1 S1)FXS-4 1)FXS 1 N1)T1/PR 1)T1/PR [Port=1] [DS0=1] │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ │ SYS: OK NETWK1:ONLN NETWK2: -- 1: OK 2: OK 3: -- 4: -- INS/DEL ^Z=help 16:33

Repeat this step for every remoted analog telephone.




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 T1 and FXO/FXS 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 T1 cable disconnects, busyouts/releases and resets of the DS1 circuit packs on the G650 and G350 Media Gateways, and resets of the DS1 circuit packs on the DMXtend Access Multiplexers.

• A remoted analog 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 analog phone in Site C.

6.2. Test Results All test cases completed successfully. The types of calls included calls between sites, call transfers to phones within the same site and to remoted analog phones, and conference calls involving parties from all three sites.

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

• For the ISDN-PRI private line only, from the SAT, enter the command status signaling-group s, where s is the number of the ISDN-PRI 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 ISDN-PRI or E&M 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 analog 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 the procedures for configuring Avaya Communication Manager T1 and FXO/FXS analog private lines 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 T1 and FXO/FXS 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].

application notes for configuring ... - devconnect program

Documents