Read Microsoft Word - IG550.doc text version

Avaya Solution & Interoperability Test Lab

Sample Configuration for Avaya Communication Manager Release 4.0 with an Avaya IG550 Integrated Gateway and Juniper J4350 Services Router ­ Issue 1.1

Abstract

These Application Notes describe how to configure the Avaya IG550 Integrated Gateway and Juniper J4350 Services Router with Avaya Communication Manager Release 4.0. The Avaya IG550 Integrated Gateway is telephony software and hardware embedded in the Juniper J4350 Services Router. This integrated branch gateway provides a telephony, routing and security solution. In addition, the Avaya IG550 Integrated Gateway provides local survivability options, enabling local availability during loss of network connectivity to Avaya Communication Manager. The Avaya IG550 Integrated Gateway requires Avaya Communication Manager 4.0 or higher to operate.

WH; Reviewed: SPOC 3/15/2007

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

1 of 32 IG550.doc

1. Introduction

These Application Notes describe how to configure the Avaya IG550 Integrated Gateway and Juniper J4350 Services Router with Avaya Communication Manager Release 4.0. The Avaya IG550 Integrated Gateway is telephony software and hardware embedded in the Juniper J4350 Services Router. This integrated branch gateway provides a telephony, routing and security solution. In addition, the Avaya IG550 Integrated Gateway provides local survivability options, enabling local availability during loss of network connectivity to Avaya Communication Manager. The Avaya IG550 Integrated Gateway requires Avaya Communication Manager 4.0 or higher to operate. The Avaya IG550 Integrated Gateway is comprised of a gateway blade module (TGM550) and Avaya telephony interface modules that support T1/E1, ISDN and analog connections. The Avaya IG550 Integrated Gateway is an H.248-based voice gateway under the control of an external Avaya Communication Manager. The Avaya IG550 Integrated Gateway registers to Avaya Communication Manager and functions as an Avaya Media Gateway to provide Avaya Communication Manager based telephony services. In these Application Notes, the Avaya IG550 Integrated Gateway registers to Avaya Communication Manager on the Avaya S8710 Media Server at the Main Location. In the sample configuration of these Application Notes, the Standard Local Survivability (SLS) feature on the Avaya IG550 Integrated Gateway is enabled. When activated, SLS mode provides basic calling features when the Avaya IG550 Integrated Gateway cannot communicate to Avaya Communication Manager. The Juniper J4350 Services Router is also configured as a DHCP sever with Avaya option 176 to provide call server and file server IP addresses, and a range of dynamic IP addresses for the Avaya 4600 Series IP Telephones connected to the Juniper J4350 Services Router.

1.1. Configuration

Figure 1 illustrates the configuration used to verify these Application Notes. The Main Location consists of a pair of Avaya S8710 Media Servers with Avaya Single Carrier Cabinet (SCC1). The Remote Location consists of a J4350 Services Router with Avaya telephony interface modules (TIM) and a Juniper T1 WAN physical interface module (PIM). All IP telephones register to Avaya Communication Manager running on the Avaya S8710 Media Servers at the Main Location. Note: These Application Notes assume that the Main Location depicted in Figure 1 is already in place, as well as Avaya Communication Manager and Avaya Single Carrier Cabinet (SCC1). Please consult the appropriate documentation listed in the References section of this document for more information on setting up these components. The focus of these Application Notes is to configure the Avaya IG550 Integrated Gateway and the Juniper J4350 Services Router with Avaya Communication Manager.

WH; Reviewed: SPOC 3/15/2007

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

2 of 32 IG550.doc

Name C-LAN TGM550 GE-0/0/0 T1 WAN (t1-3/0/0) TFTP Server

IP Address 5.1.1.4, 5.1.1.5 5.1.108.1 5.1.108.253 5.1.106.2 5.1.1.12

Location Main Location Remote Location Remote Location Remote Location Main Location

Table 1 - IP Address Assignment

Figure 1: Avaya IG550 Integrated Gateway Controlled by Avaya S8710 Media Servers - Network Configuration Diagram

WH; Reviewed: SPOC 3/15/2007

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

3 of 32 IG550.doc

2. Equipment and Software Validated

The following equipment and software were used for the sample configuration provided: Equipment Avaya S8710 Media Server Avaya SCC1 Media gateway IPSI (TN2312BP) C-LAN (TN799DP) MEDPRO (TN2302AP) Avaya IG550 Integrated Gateway Telephony Interface Modules TGM550AP DS1 MM (TIM510AP) ANA MM (TIM514AP) Avaya 4600 Series IP Telephones Avaya 9600 Series one-X Deskphone Edition IP Telephones

Avaya C363T-PWR Converged Stackable Switch

Software Avaya Communication Manager 4.0 (R014x.00.0.729.0) HW12 FW036 HW01 FW0149 HW20 FW115

HW 00 FW000 26.27.0 HW 02 FW000 HW 02 FW000 2.8 (H.323) 1.2 (H.323)

4.5.14 JUNOS 8.2B3.1

Juniper J4350 Services Router JWAN MM (MMJWAN) Cisco 3725 Router

HW 00 FW000

12.4(5)

Table 2 - Equipment and Version Validated

WH; Reviewed: SPOC 3/15/2007

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

4 of 32 IG550.doc

3. Configure Avaya Communication Manager for Avaya IG550 Integrated Gateway with Standard Local Survivability

This section describes the administration on Avaya Communication Manager that must be performed for the Avaya IG550 Integrated Gateway to register with Avaya Communication Manager. The following commands are issued at the Avaya System Access Terminal (SAT) on the Avaya S8710 Media Server at the Main Location.

3.1. Configure Avaya Communication Manager for Avaya IG550 Integrated Gateway

In the sample configuration of these Application Notes, assume the customer has the following VoIP objectives: · · · At the main office as well as the branch office, intra-office VoIP communications should use G.711MU. This optimizes for voice quality. Inter-office VoIP communications should utilize G.729A codec. This optimizes for efficient use of bandwidth over the WAN between the offices. Calls between IP entities should utilize "shuffling" for direct communication where possible. Shuffling to direct connections makes efficient use of IP media processing resources and can also improve voice quality, since fewer transcodings are necessary.

Avaya Communication Manager enables the achievement of these objectives by assigning the main office entities and remote office entities to different "IP network regions." IP network regions can be used to define various IP properties, including the codec set to be used within the network region, and the codec set to be used for communication between a network region and other interconnected regions. A feature of Avaya Communication Manager enables the assignment of IP nodes to network regions via an "IP network map". For example, the IP network map can allow an IP telephone located in the Remote Location to be associated with the same network region as the Avaya IG550 Integrated Gateway in the Remote Location, despite the fact that this IP telephone will be registered with a C-LAN physically located in the Main Location (i.e., under normal operating conditions). The IP network map can assign IP network regions to different IP address ranges, and the IP network region form allows a "location" to be associated with the region. In the sample configuration, network region 1 and network region 2 are each configured to use codec set 1 within the respective regions and codec set 2 between the regions. Direct IP-IP audio connections, often referred to as "shuffling," are enabled for the regions. Shuffling must also be enabled system-wide. The network region form can also be used to configure QoS parameters for the region, but QoS parameters are not the subject of these Application Notes.

WH; Reviewed: SPOC 3/15/2007

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

5 of 32 IG550.doc

Step 1.

Description In the sample configuration, the Avaya IG550 Integrated Gateway is located at location 2 in IP network region 2. Issue the change ip-network-region <n> command, where <n> is an unused network region number. On Page 1, enter the following values:

· Location: Enter "2". The location number for the Remote Location is administered in

Step 7.

· Codec Set: Enter "1". The codec set for intra- region communications is configured in

Step 2.

change ip-network-region 2 IP NETWORK REGION Region: 2 Location: 2 Authoritative Domain: Name: San Hose MEDIA PARAMETERS Intra-region IP-IP Direct Audio: yes Codec Set: 1 Inter-region IP-IP Direct Audio: yes UDP Port Min: 5000 IP Audio Hairpinning? n UDP Port Max: 5999 DIFFSERV/TOS PARAMETERS RTCP Reporting Enabled? y Call Control PHB Value: 46 RTCP MONITOR SERVER PARAMETERS Audio PHB Value: 46 Use Default Server Parameters? y Video PHB Value: 26 802.1P/Q PARAMETERS Call Control 802.1p Priority: 6 Audio 802.1p Priority: 6 Video 802.1p Priority: 5 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 Page 1 of 19

On Page 3 of the ip-network-region form, specify the IP codec set for each source region and destination region pair. The codec set (i.e., codec set 2 below) for inter-region communications is configured in Step 3.

change ip-network-region 2 Inter Network Region Connection Management src rgn 2 2 2 dst codec direct Total rgn set WAN WAN-BW-limits 1 2 2 1 y :NoLimit 3 Video Norm Prio Dyn CAC IGAR y Page 3 of 19

Shr Intervening-regions y

WH; Reviewed: SPOC 3/15/2007

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

6 of 32 IG550.doc

Step 2.

Description Configure the codec set (i.e., codec set 1) for intra region communications. Issue the change ip-codec-set <n> command, where <n> is a valid codec set. Enter the following values: · Audio codec: Enter "G.711MU". · Silence Suppression: Retain the default value "n". · Frames Per Pkt: Retain the default value "2". · Packet Size (ms): Retain the default value "20". · Media Encryption: Enter the value based on the customer's security requirements, for example "aes".

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

Media Encryption 1: aes 2: 3:

Note: A system license file enables the Media Encryption option. Issue the display system-parameters customer-options command and verify that the Media Encryption Over IP field is set to "y". If it is not set to "y", contact an authorized Avaya sales team or business partner.

display system-parameters customer-options OPTIONAL FEATURES Emergency Access to Attendant? Enable 'dadmin' Login? Enhanced Conferencing? Enhanced EC500? Enterprise Survivable Server? Enterprise Wide Licensing? ESS Administration? Extended Cvg/Fwd Admin? External Device Alarm Admin? Five Port Networks Max Per MCC? Flexible Billing? Forced Entry of Account Codes? Global Call Classification? Hospitality (Basic)? Hospitality (G3V3 Enhancements)? IP Trunks? y y y y n n y y n n n n n y n y Page 4 of 11

IP Stations? y ISDN Feature Plus? ISDN Network Call Redirection? ISDN-BRI Trunks? ISDN-PRI? Local Survivable Processor? Malicious Call Trace? Media Encryption Over IP? Mode Code for Centralized Voice Mail? y y y y n y y n

Multifrequency Signaling? y Multimedia Call Handling (Basic)? y Multimedia Call Handling (Enhanced)? y

IP Attendant Consoles? y (NOTE: You must logoff & login to effect the permission changes.)

WH; Reviewed: SPOC 3/15/2007

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

7 of 32 IG550.doc

Step 3. 4.

Description Repeat Step 2 to add a codec set (i.e., codec set 2) for inter-region communications with audio codec "G.729". Using the change ip-network-map command, assign all IP addresses in the range 5.1.1.101 through 5.1.1.200 to network region 1, and all IP addresses in the range 5.1.108.101 through 5.1.108.200 to network region 2. All nodes with IP addresses in the first range are located at the Main Location, and all nodes with IP addresses in the second range are located at the Remote Location. This simple approach suffices in this example, but the ip-network-map form is flexible and can accommodate more complex networks.

change ip-network-map IP ADDRESS MAPPING Emergency Location Extension Page 1 of 32

From IP Address 5 .1 .1 .101 5 .1 .108.101 . . . . . . . . .

(To IP Address 5 .1 .1 .200 5 .1 .108.200 . . . . . . . . .

Subnet or Mask)

Region 1 2

VLAN n n n n n

5.

Issue the display system-parameters customer-options command and navigate to Page 5. Verify that Multiple Locations and Uniform Dialing Plan are set to "y".

display system-parameters customer-options OPTIONAL FEATURES Multinational Locations? n Multiple Level Precedence & Preemption? n Multiple Locations? y Personal Station Access (PSA)? Posted Messages? PNC Duplication? Port Network Support? y n n y Page 5 of 11

Station and Trunk MSP? n Station as Virtual Extension? n System Management Data Transfer? Tenant Partitioning? Terminal Trans. Init. (TTI)? Time of Day Routing? Uniform Dialing Plan? Usage Allocation Enhancements? TN2501 VAL Maximum Capacity? n n y y y y y

Processor and System MSP? n Private Networking? y Processor Ethernet? y Remote Office? y Restrict Call Forward Off Net? y Secondary Data Module? y

Wideband Switching? y Wireless? n

(NOTE: You must logoff & login to effect the permission changes.)

WH; Reviewed: SPOC 3/15/2007

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

8 of 32 IG550.doc

Step 6.

Description Select the C-LANs to be used in setting up the IG550 Integrated Gateway controller list. Issue the display node-names ip command. Note the C-LAN IP addresses "5.1.1.4" and "5.1.1.5". The IP addresses will be used in Section 4 Step 8.

display node-names ip IP NODE NAMES Name C-LAN-A C-LAN-B MedPro-A MedPro-B IP Address 5.1.1.4 5.1.1.5 5.1.1.6 5.1.1.7

7.

Issue the add media gateway <n> command, where <n> is an unassigned media gateway number. Enter the following values:

· Type: Enter the gateway type "j4350". · Name: Enter a descriptive name. · Serial Number: Enter the 12 character alphanumeric serial number of the TGM550

module, which is noted in Section 4 Step 2. · Network Region: Enter the network region number configured in Step 1. · Location: Enter a valid location number between 1 and 250, for example "2".

add media-gateway 4 MEDIA GATEWAY Number: Type: Name: Serial No: Encrypt Link? Network Region: Location: Recovery Rule: Slot V1: V2: V3: V4: V5: V6: 4 j4350 TR-MG4 06IS27819429 y 2 2 none Registered? FW Version/HW Vintage: IP Address: Controller IP Address: MAC Address: Site Data: DSP Type Module Type Name FW/HW version 255 255 n Page 1 of 1

Max Survivable IP Ext: 8 V9:

WH; Reviewed: SPOC 3/15/2007

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

9 of 32 IG550.doc

Step 8.

Description To add an IP phone, issue the add station <n> command, where <n> is a valid unused station number, for example "14083338900". On Page 1, enter the following values:

· · · ·

Type: Enter a valid IP station type, for example "4620". Port: Enter "IP". Name: Enter a descriptive name. Security Code: Enter a valid station security code.

add station 14083338900 STATION Extension: Type: Port: Name: 1408-333-8900 4620 IP TR-MG4-38900 Lock Messages? n Security Code: * Coverage Path 1: Coverage Path 2: Hunt-to Station: Time of Day Lock Table: Personalized Ringing Pattern: Message Lamp Ext: Mute Button Enabled? Expansion Module? BCC: TN: COR: COS: 0 1 1 1 Page 1 of 5

STATION OPTIONS Loss Group: 19 Speakerphone: Display Language: Survivable GK Node Name: Survivable COR: Survivable Trunk Dest? 2-way english internal y 1 1408-333-8900 y n

Media Complex Ext: IP SoftPhone? n Customizable Labels? y

9.

To add an analog phone, issue the add station <n> command, where <n> is a valid unused station number, for example "14083338801". On Page 1, enter the following values:

· Type: Enter station type "6210". · Port: Enter "MVSP". (M: the media gateway number configured in Step 7, S: TIM514

slot number, P: port number). · Name: Enter a descriptive name. · Security Code: Enter a valid station security code.

add station 14083338804 STATION Extension: Type: Port: Name: 1408-333-8804 6210 004V404 TR-MG4-38801 Lock Messages? n Security Code: * Coverage Path 1: Coverage Path 2: Hunt-to Station: BCC: TN: COR: COS: Tests? 0 1 1 1 y Page 1 of 4

STATION OPTIONS Loss Group: 1 Off Premises Station? n Time of Day Lock Table: Message Waiting Indicator: led Message Lamp Ext: 1408-333-8804

Survivable COR: internal Survivable Trunk Dest? y Remote Office Phone? n

WH; Reviewed: SPOC 3/15/2007

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

10 of 32 IG550.doc

Step 10. 11.

Description Repeat Steps 8 and 9 as necessary to add additional IP and analog phones. Add a DS1 circuit pack to support the trunk group between the PSTN and the Avaya IG550 Integrated Gateway. Issue the add ds1 <nvs> command, where <n> is the Media Gateway number and <s> is the slot number into which the DS1 TIM module is inserted, for example "4v5". Enter the following values:

· · · ·

Line Coding: b8zs Signaling Mode: isdn-pri Connect: pbx Interface: user

add ds1 4v5 DS1 CIRCUIT PACK Location: Bit Rate: Line Compensation: Signaling Mode: Connect: TN-C7 Long Timers? Interworking Message: Interface Companding: Idle Code:

004V5 Name: TR-MG4-PSTN 1.544 Line Coding: b8zs 1 Framing Mode: esf isdn-pri pbx Interface: user n Country Protocol: 1 PROGress Protocol Version: a mulaw CRC? n 11111111 DCP/Analog Bearer Capability: 3.1kHz

Page

1 of

2

T303 Timer(sec): 4

Slip Detection? n Echo Cancellation? n

Near-end CSU Type: other

WH; Reviewed: SPOC 3/15/2007

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

11 of 32 IG550.doc

Step 12.

Description Add a trunk group between the PSTN and the Avaya IG550 Integrated Gateway. Issue the add trunk-group <n> command, where <n> is an available trunk group number. On Page 1, enter the following values and leave the rest of the parameters at the default values. · Group Name: Enter a descriptive name. · Group Type: Enter "isdn". · TAC: Enter a valid Trunk Access Code, for example "117". · Carrier Medium: Enter "PRI/BRI". · Service Type: Enter "tie".

add trunk-group 17 TRUNK GROUP Group Number: Group Name: Direction: Dial Access? Queue Length: Service Type: 17 MG4 - PSTN two-way y 0 tie Group Type: isdn CDR Reports: y COR: 1 TN: 1 TAC: 117 Outgoing Display? n Carrier Medium: PRI/BRI Busy Threshold: 255 Night Service: Auth Code? n Far End Test Line No: TestCall ITC: rest Page 1 of 21

TestCall BCC: 4

13.

Issue the add signaling-group <n> command, where <n> is an available signaling group number. On Page 1, enter the following values and leave the rest of the parameters at the default values.

· · ·

Group Type: Enter "isdn-pri". Primary D-Channel: Enter the number of the primary D-channel of the DS1 administered in Step 11, for example "004v524". Trunk Group for Channel Selection: Enter the trunk group number configured in Step 12.

Page SIGNALING GROUP Group Number: 17 Group Type: isdn-pri Associated Signaling? y Primary D-Channel: 004V524 1 of 5

add signaling-group 17

Trunk Group for Channel Selection: 17 TSC Supplementary Service Protocol: a

Max number of NCA TSC: Max number of CA TSC: Trunk Group for NCA TSC: X-Mobility/Wireless Type: Network Call Transfer?

0 0 NONE n

WH; Reviewed: SPOC 3/15/2007

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

12 of 32 IG550.doc

Step 14.

Description To add trunk group members to the trunk group configured in Step 12, issue the change trunk-group command. Navigate to Page 5, and then enter the port numbers and the signaling group. · Port: Enter an unused port on the DS1 defined in Step 11. · Sig Grp: Enter the signaling group administered in Step 13.

change trunk-group 17 Page TRUNK GROUP Administered Members (min/max): Total Administered Members: Night Sig Grp 17 17 17 5 of 1/3 3 21

GROUP MEMBER ASSIGNMENTS Port 1: 004V501 2: 004V502 3: 004V503 4: 5: 6: Code Sfx Name TIM510 TIM510 TIM510

WH; Reviewed: SPOC 3/15/2007

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

13 of 32 IG550.doc

3.2. Configure Avaya IG550 Integrated Gateway for Standard Local Survivability on Avaya Communication Manager

Standard Local Survivability (SLS) uses a module built into the Avaya IG550 Integrated Gateway to provide limited media gateway controller functionality during loss of connectivity to the main controller. SLS is activated when the Avaya IG550 Integrated Gateway cannot register to the primary controller(s) (the primary controller list is administered in Section 4 Step 3). A subset of the Avaya 4600 Series IP telephones can be configured to register to the local survivable gatekeeper (TGM550) when the IG550 is in SLS mode. Refer to [3] to view a list of Avaya IP phone types that are supported in SLS mode. This section describes the steps necessary to administer the IP stations.

Step 1.

Description Add an entry for the Avaya IG550 Integrated Gateway in the IP NODE NAMES form. Issue the change node-names ip command, and enter the following values:

· ·

Name: The Avaya IG550 Integrated Gateway node name, for example "TR-MG-4" IP Address: The Avaya IG550 Integrated Gateway IP address, for example "5.1.108.1".

Page IP Address 5 .1 .1 .4 5 .1 .1 .5 5 .1 .1 .6 5 .1 .1 .7 5 .1 .108.1 0 .0 .0 .0 IP NODE NAMES Name IP . . . . . . Address . . . . . . . . . . . . 1 of 1

change node-names ip Name

C-LAN-A C-LAN-B MedPro-A MedPro-B

TR-MG-4 default

WH; Reviewed: SPOC 3/15/2007

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

14 of 32 IG550.doc

Step 2.

Description Gatekeeper information needs to be administered for all IP stations on the Avaya IG550 Integrated Gateway. Issue the change station <x> command, where <x> is the extension of the IP station, for example "14083338900". Enter the following value:

·

Survivable GK Node Name: Enter the node name defined in Step 1, for example "TR-MG-4".

Page STATION 1 of 5

change station 14083338900

Extension: Type: Port: Name:

1408-333-8900 4620 S02786 38900, MG4

Lock Messages? n Security Code: 1234 Coverage Path 1: Coverage Path 2: Hunt-to Station: Time of Day Lock Table: Personalized Ringing Pattern: Message Lamp Ext: Mute Button Enabled? Expansion Module?

BCC: TN: COR: COS:

0 1 3 3

STATION OPTIONS Loss Group: 19 Speakerphone: Display Language: Survivable GK Node Name: Survivable COR: Survivable Trunk Dest? 1 1408-333-8900 y n

2-way english TR-MG-4 unrestricted y

Media Complex Ext: IP SoftPhone? n

Customizable Labels? y

3.

Repeat Step 2 as necessary to administer additional IP stations on the Avaya IG550 Integrated Gateway.

WH; Reviewed: SPOC 3/15/2007

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

15 of 32 IG550.doc

4. Configure Juniper J4350 Services Router

This section details the administration of the Juniper J4350 Services Router. The following steps use the Command Line Interface (CLI) offered by the Juniper J4350 Services Router. The CLI commands are issued from a PC connected to the Juniper J4350 Services Router console port. Avaya IP telephones can be programmed to search for a gatekeeper. The IP telephones acquire a list of gatekeepers or controllers in messages from the DHCP server. In the sample configuration, the Juniper J4350 Services Router is configured to provide DHCP service to the Avaya IP telephones in the Remote Location. In the DHCP scope corresponding to the Avaya IP telephones in the Remote Location, MCIPADD will contain 5.1.1.4 (C-LAN-A) and 5.1.1.5 (CLAN-B) in option 176. Avaya 4600 Series IP telephone software is downloaded from a TFTP server. The TFTP server IP address is also administered in option 176. Step Description Log in to the Juniper J4350 CLI using the appropriate login ID and password. 1. 2. The TGM550 serial number is needed for the Avaya IG550 Integrated Gateway to register with a media gateway controller. Issue the show chassis hardware command to view the TGM550 serial number.

[email protected]> show chassis hardware Hardware inventory: Item Version Part number Chassis Midplane REV 01 710-014594 System IO REV 01 710-016210 Crypto Module Routing Engine REV 05 710-015273 FPC 0 PIC 0 FPC 1 REV 02 740-016071 PIC 0 FPC 2 REV 02 740-016074 PIC 0 FPC 3 REV 05 750-010355 PIC 0 FPC 4 REV 02 740-016073 PIC 0 FPC 5 REV 02 740-016072 PIC 0 FPC 6 REV 07 750-013492 PIC 0

Serial number JN108BCB6ADA NJ7295 NH9885 JM8033

Description J4350 JX350 System IO Crypto Acceleration RE-J4350-2540 FPC 4x GE Base PIC FPC 1x TGM550 FPC 4x BRI TIM521 FPC 2x T1 FPC 4x FXS, 4x FXO TIM514 FPC 1x DS1 TIM510 FPC 4x FE

06IS27819429 06IS28811770 AI06317848 06IS30813219 06IS29812370 NH3432

WH; Reviewed: SPOC 3/15/2007

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

16 of 32 IG550.doc

Step Description The Avaya IG550 Integrated Gateway maintains a statically provisioned list of controllers. This 3. controller list can be set using a Juniper J4350 CLI command. Issue the set tgm fpc <x> mediagateway-controller [ <n1 n2>] command to set the media gateway controller list, where <x> is the slot number where the TGM550 is inserted and <n1 n2> is a list of IP addresses of the media gateway controller. The C-LAN IP addresses for media gateway controller can be found in Section 3.1 Step 6. The show mgc command, as shown in Section 5.1 Step 2, can be used to view the media gateway controller list and status. Enter commit to submit the change.

[email protected]> set tgm fpc 1 media-gateway-controller [ 5.1.1.4 5.1.1.5 ] [email protected]>commit

4.

Issue the configure command to enter edit mode.

[email protected]> configure Entering configuration mode [edit] [email protected]#

5.

Issue the set interfaces ge-0/0/0 command to add a new interface with inet address "5.1.108.253". The Avaya IP telephones in the Remote Location will connect to the Avaya IG550 Integrated Gateway via this interface. Enter commit to submit the change.

[edit] [email protected]> set interfaces ge-0/0/0 unit 0 family inet address 5.1.108.253/24 [edit] [email protected]>commit

WH; Reviewed: SPOC 3/15/2007

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

17 of 32 IG550.doc

Step Description Execute the following command to allow web management on the Ethernet interface ge-0/0/0. 6. Enter commit to submit the change.

[edit] [email protected]> set system services web-management http interface ge0/0/0.0 [edit] [email protected]>commit

7.

Execute the following command to configure the DHCP range between "5.1.108.101" and "5.1.108.200" for the Avaya IP telephones in the Remote Location. Enter commit to submit the change.

[edit] [email protected]> set system services dhcp pool 5.1.108.0/24 addressrange low 5.1.108.101 high 5.1.108.200 [edit] [email protected]>commit

8.

Execute the following command to configure DHCP Option 176. The C-LAN IP addresses for MCIPADD can be found in Section 3.1 Step 6. Enter commit to submit the change.

[edit] [email protected]> set system services dhcp pool 5.1.108.0/24 option 176 string MCIPADD=5.1.1.4,5.1.1.5,MCPORT=1719,TFTPSRVR=5.1.1.12; [edit] [email protected]>commit

WH; Reviewed: SPOC 3/15/2007

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

18 of 32 IG550.doc

Step Description The interface for the TGM550 is vp-x/0/0, where x is the slot number where the TGM550 is 9. inserted. In the sample configuration, the TGM550 is in slot 1. The TGM550 IP address is configured as the destination of a point to point link. All packets received on the vp-x/0/0 interface will be forwarded to the TGM550. Execute the following command to configure the TGM550 interface vp-1/0/0. Assign an unused internal IP address to the vp-1/0/0 interface, for example, "10.1.1.1". Enter commit to submit the change.

[edit] [email protected]# set interfaces vp-1/0/0 unit 0 family inet address 10.1.1.1/32 destination 5.1.108.1; [edit] [email protected]>commit

10.

The Juniper J4350 Services Router is connected to the Cisco router via the T1 WAN interface module. Execute the following commands to configure the t1-3/0/0 interface, where "3" is the slot number. Enter commit to submit the change.

[edit] [email protected]# set interfaces t1-3/0/0 description T1 mtu 1500 clocking external encapsulation ppp t1-options timeslots 1-24 [edit] [email protected]# set interfaces t1-3/0/0 unit 0 family inet address 5.1.106.2/24 [edit] [email protected]>commit

11.

Issue the set protocols ospf command to exchange routing information with the Cisco router connected to the t1-3/0/0.0 interface. Enter commit to submit the change.

[edit] [email protected]> set protocols ospf area 0.0.0.0 interface t1-3/0/0.0 [edit] [email protected]>commit

WH; Reviewed: SPOC 3/15/2007

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

19 of 32 IG550.doc

5. Configure Avaya IG550 Integrated Gateway with Standard Local Survivability

This section describes the steps to administer the Avaya IG550 Integrated Gateway. The following commands are issued at the Avaya TGM550 module on the Avaya IG550 Integrated Gateway. Use Telnet to connect to the Avaya TGM550 module. After logging in, use the help to display the list of commands that are available. Type help followed by a word to see a list of all commands starting with that word.

5.1. Configure Avaya IG550 Integrated Gateway

Step 1. 2. Description Log in to the Avaya IG550 Integrated Gateway with the proper credentials. The Avaya IG550 Integrated Gateway maintains a statically provisioned list of controllers. The media gateway controller list is administered in Section 4 Step 3. The show mgc list and show mgc commands can be used to view the media gateway controller list and status.

TGM550-004(super)# TGM550-004(super)# show mgc CALL CONTROLLER STATUS ------------------------------------------Registered : YES Active Controller : 5.1.1.4 H248 Link Status : UP H248 Link Error Code: 0x0 CONFIGURED MGC HOST --------------------5.1.1.4 5.1.1.5 -- Not Available --- Not Available --

3.

The Avaya IG550 Integrated Gateway must be configured with information relevant to its recovery process. The set reset-times help command is illustrated below to show the commands that will be described briefly in subsequent Steps.

TGM550-004(super)# set reset-times help Set reset-times commands: ----------------------------------------------------------------set reset-times primary-search Sets the primary search timer set reset-times total-search Sets the total search timer set reset-times transition-point Sets the entry point

WH; Reviewed: SPOC 3/15/2007

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

20 of 32 IG550.doc

Step 4.

Description Issue the set reset-times transition-point command to configure the point at which the primary media gateway controllers end and the survivable media gateway controller begin. In the sample configuration, the media gateway controller list is configured with the IP addresses of two C-LANs as primary controllers. Hence, the transition point should be set to "2".

TGM550-004(super)# set reset-times transition-point 2 Done!

5.

The primary search time is the time (in minutes) that the Avaya IG550 Integrated Gateway will attempt to connect with those addresses in the controller list up to and including the transition point, before moving on to try to connect to addresses beyond the transition point. Issue the set reset-times primary-search command to set the primary search timer. In the sample configuration, the default value of "1 minute" for the primary search timer is retained.

TGM550-004(super)# set reset-times primary-search 1 Done!

6.

The total search time is the time (in minutes) that the Avaya IG550 Integrated Gateway will attempt to connect with all addresses in the controller list, before the Avaya IG550 Integrated Gateway will perform a hard reset. Issue the set reset-times total-search <time> command.

TGM550-004(super)# set reset-times total-search 15 Done!

7.

Issue the show recovery command to view the summary of the recovery parameters.

TGM550-004(super)# show recovery RECOVERY TIMES -------------------------------Primary Search : 1 Total Search : 15 Transition Point: 2

8.

To activate the change, issue the copy running-config startup-config command and reboot the Avaya IG550 Integrated Gateway.

TGM550-004(super)# copy running-config startup-config TGM550-004(super)# reset

WH; Reviewed: SPOC 3/15/2007

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

21 of 32 IG550.doc

5.2. Configure Avaya IG550 Integrated Gateway for Standard Local Survivability

This section describes the administration on the Avaya IG550 Integrated Gateway that is performed to configure the Standard Local Survivability (SLS). Type help followed by a word to see a list of all commands starting with that word. Step 1. 2. Description Log in to the Avaya IG550 Integrated Gateway using the proper credentials. To enable survivable call engine, issue the set survivable-call-engine enable command, as shown below.

TGM550-004(super)# set survivable-call-engine enable

Survivable Call Engine is enabled

Issue the show mgc list command to view the media gateway controllers. The fifth entry shows survivable-call-engine. It indicates that the survivable call engine is enabled.

TGM550-004(super)# show mgc list CONFIGURED MGC HOST --------------------5.1.1.4 5.1.1.5 -- Not Available --- Not Available -survivable-call-engine

.3.

To enter the survivable-call-engine configuration mode, issue the survivable-call-engine command as shown below.

TGM550-004(super)# survivable-call-engine TGM550-004(super-survivable-call-engine)#

WH; Reviewed: SPOC 3/15/2007

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

22 of 32 IG550.doc

Step 4.

Description To add a new IP station in the SLS mode, enter the station <x> <class> command, where <x> is a station extension configured in Section 3.1 Steps 8 through 10, and <class> is the type of the phone. Note: SLS only supports a subset of Avaya 4600 Series IP Telephones. Type help to see the list of IP phone types that are supported by the SLS.

TGM550-004(super-survivable-call-engine)# station 14083338900 ip

Done!

TGM550-004(super-survivable-call-engine/station 14083338900)#

5.

Issue the following station sub-commands to set the IP station parameters. Press Enter after each sub-command.

· · · ·

set cor <x>, where <x> is the class of restriction, for example "unrestricted". set password <*>, where <*> is the password of the IP station. set trunk-destination yes, to allow the station to receive analog loop-start trunk calls. set type <x>, where <xx> is the phone type, for example "ip4620sw".

When finished with all the sub-commands, type exit and then press Enter. The results can be viewed by issuing the show extension command as shown below.

TGM550-004(super-survivable-call-engine)# show extension Extension Type Port Cor Trk-Des Exp-Mod Flash Passwd ----------- ---------- ---------------- ------------ ------- ------- ----- -----14083338900 ip4620sw 0.0.0.0 unrestricted yes no - ******

6.

Repeat Steps 4 and 5 to add the remaining IP stations. The results can be viewed by issuing the show extension command as shown below:

TGM550-004(super-survivable-call-engine)# Extension Type Port ------------- ---------- ---------------14083338900 ip4620sw 0.0.0.0 14083338901 ip4620sw 0.0.0.0 show extension Cor Trk-Des Exp-Mod Flash Passwd -------- ------- ------- ----- -----unrestri yes no - ****** unrestri yes no - ******

WH; Reviewed: SPOC 3/15/2007

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

23 of 32 IG550.doc

Step 7.

Description Repeat Step 4 to add an analog station. Issue the following station sub-commands to set the analog station parameters. Press Enter after each sub-command.

· set cor <x>, where <x> is the class of restriction, for example "unrestricted". · set port <vxxx>, where <vxxx> is the physical port on the analog module, for

example "v405". · set trunk-destination yes. · set flash yes (If switch hook flash signal is required.) When finished with all the sub-commands, type exit and then press Enter. The result can be viewed by issuing the show extension command as shown below.

TGM550-004(super-survivable-call-engine)# show extension Extension Type Port Cor Trk-Des Exp-Mod Flash Passwd ------------- ---------- ---------------- ------------ ------- ------- ----- -----14083338900 ip4620sw 0.0.0.0 unrestri yes no ****** 14083338901 ip4620sw 0.0.0.0 unrestri yes no ****** 14083338801 analog2500 v405 unrestri yes yes -

8.

Repeat Step 7 to add the remaining analog stations. The result can be viewed by issuing the show extension command as shown below.

TGM550-004(super-survivable-call-engine)# show extension Extension Type Port Cor Trk-Des Exp-Mod Flash Passwd ------------- ---------- ---------------- -------- ------- ------- ----- -----14083338900 ip4620sw 0.0.0.0 unrestri yes no ****** 14083338901 ip4620sw 0.0.0.0 unrestri yes no ****** 14083338801 analog2500 v405 unrestri yes yes 14083338804 analog2500 v408 unrestri yes yes -

9.

To add a trunk group, type trunk-group <id> <type>, where

· <id> is a unique identifier for the trunk group, "1". · <type> is the trunk-group type, for example "t1-isdn".

TGM550-004(super-survivable-call-engine)# trunk-group 1 t1-isdn TGM550-004(super-survivable-call-engine/trunk-group 1) Done!

WH; Reviewed: SPOC 3/15/2007

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

24 of 32 IG550.doc

Step 10.

Description Issue the DS1 commands to set the DS1 parameters (which should match the values defined in Section 3.1 Step 11). The sequence of commands is shown below.

TGM550-004(super-survivable-call-engine)# ds1 v5 Done! TGM550-004(super-survivable-call-engine/ds1 v5)# set connect pbx Done! TGM550-004(super-survivable-call-engine/ds1 v5)# TGM550-004(super-survivable-call-engine/ds1 v5)# set protocol-version a Done! TGM550-004(super-survivable-call-engine/ds1 v5)# show DS1 Rate Signaling Chan Connect Interface Side Protocol Ver Bearer Cmpd Ltm --- ---- --------- ----- -------- ---------- ---- --------- --- ------ ---- --v5 1544 isdnpri tslot pbx user a country1 a 3khz ulaw no

11.

Issue the sig-group command to configure the sig-group parameters. The sequence of commands is shown below.

TGM550-004(super-survivable-call-engine)# sig-group 1 Done! TGM550-004(super-survivable-call-engine/sig-group 1)# set primary-dchannel 004v524 Done! TGM550-004(super-survivable-call-engine/sig-group 1)# set trunk-group-chan-select 1 Done! TGM550-004(super-survivable-call-engine/sig-group 1)#exit Done!

WH; Reviewed: SPOC 3/15/2007

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

25 of 32 IG550.doc

Step 12.

Description Issue the following trunk-group commands to set the trunk-group parameters. Press Enter after each sub-command.

· trunk-group <n>, where <n> is the trunk group number configured in Step 9. · add port <vSP> <g>, where S is the DS1 slot number, P is the port number on the

DS1 slot, and g is the sig-group number configured in Step 11. For example, "v501 1". Repeat this command as necessary to add the same number of DS1 channels as added in Section 3.2 Step 14. · set dial <rotary | dtmf>. Sets how the trunks in the current trunk group dial. · set tac <x>, where <x> is the trunk access code, for example "101". When finished with all sub-commands, type exit and then press Enter to return to the first level Command Line Interface. The sequence of commands is shown below.

TGM550-004(super-survivable-call-engine)# trunk-group 1

Done!

TGM550-004(super-survivable-call-engine/trunk-group 1)# add port v501 1

Done!

TGM550-004(super-survivable-call-engine/trunk-group 1)# add port v502 1

Done!

TGM550-004(super-survivable-call-engine/trunk-group 1)# add port v503 1

Done!

TGM550-004(super-survivable-call-engine/trunk-group 1)# set dial dtmf

Done!

The trunk group 1 configuration is shown below:

TGM550-004(super-survivable-call-engine)# show trunk-group 1 Group Type Dial Tac Supervision Treat Insert ----- ------------ ------ ---- ----------------- ------- -----1 t1-isdn dtmf 101 blank Name=MG4-SLS Trunk Ports=v501:1 Codeset Codeset Channel Digit Japan Send Send Number Trunk Display National Preference Handling Discon Name Number Format Hunt -------- -------- ---------- --------------- ------ ---- ------ ------- ------Done!

WH; Reviewed: SPOC 3/15/2007

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

26 of 32 IG550.doc

Step 13.

Description Assume that to place calls to the PSTN, users in the Remote Location dial an ARS FAC (see Step 15), followed by a "1" and then the 10-digit PSTN number. Configure a dial pattern for outbound PSTN calls by typing set dial-pattern <ds>, where <ds> is the dialed string, for example "1". The sequence of the sub-commands is as shown below.

· · · ·

set max-length <n>, where <n> is the maximum dial string length allowed. set min-length <n>, where <n> is the minimum dial string length required. set type <call_type>, where <call_type> is the call type, for example "fnpa". set tgnum <n>, where <n> is the trunk group number configured in Step 9. Calls matching this dial pattern will be routed to this trunk group.

TGM550-004(super-survivable-call-engine)# dial-pattern 1 TGM550-004(super-survivable-call-engine/dial-pattern 1)# set max-length 11 TGM550-004(super-survivable-call-engine/dial-pattern 1)# set min-length 11 Done! TGM550-004(super-survivable-call-engine/dial-pattern 1)#

TGM550-004(super-survivable-call-engine/dial-pattern 1)# TGM550-004(super-survivable-call-engine/dial-pattern 1)# set type fnpa Done! TGM550-004(super-survivable-call-engine/dial-pattern 1)# set tgnum 1 Done! TGM550-004(super-survivable-call-engine/dial-pattern 1)# TGM550-004(super-survivable-call-engine/dial-pattern 1)# show Dial-String/Deny Min/Max Type Trunk Delete/Insert Length Group Digits -------------------- ------- ---- ----- --------------------------------------1/n 11/11 fnpa 1 0/-

14.

To configure an IP codec set within the SLS data set, type set ip-codec-set <codec>, where codec is the codec type, for example "g.711mu".

TGM550-004(super-survivable-call-engine)# set ip-codec-set g.711mu

WH; Reviewed: SPOC 3/15/2007

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

27 of 32 IG550.doc

Step 15.

Description Feature Access Codes (FAC) need to be programmed on the Avaya IG550 Integrated Gateway. These include ars1, ars2, hold, contact-open, contact-close, and contact-pulse (detailed information can be found in [2]). The FAC for hold is shown below. To set the Feature Access Code, type set fac <feature> <fac>, where

· <feature> is the feature name, for example "hold" or "ars1". · <fac> is the feature access code, for example "*3".

TGM550-004(super-survivable-call-engine)# set fac hold *3 TGM550-004(super-survivable-call-engine)# set fac ars1 9 Done! TGM550-004(super-survivable-call-engine)# show fac Feature Access Code ------------- ----------hold *3 ars1 9

Done! TGM550-004(super-survivable-call-engine)#

Note: When in SLS mode, a user can press switch-hook flash and dial *3 to place the analog station on the hard hold state. 16. Repeat Step 15 as necessary to add other FAC features.

WH; Reviewed: SPOC 3/15/2007

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

28 of 32 IG550.doc

6. Verification Steps

This section provides the tests that may be used to verify the proper configuration. Step Description Issue the display media-gateway 2 command from the Avaya Communication Manager SAT to 1. verify that the Avaya IG550 Integrated Gateway (j4350), administered in Section 3.1, Step 7, is registered with Avaya Communication Manager.

display media-gateway 2 MEDIA GATEWAY Number: Type: Name: Serial No: Encrypt Link? Network Region: Location: Recovery Rule: Slot V1: V2: V3: V4: V5: V6: 2 j4350 TR-MG-4 06IS27819429 y 2 2 none Registered? FW Version/HW Vintage: IP Address: Controller IP Address: MAC Address: Site Data: DSP Type DAR1 FW/HW version 1 0 y 26 .24 .0 /0 5 .1 .108.1 5 .1 .1 .4 00:04:0d:f5:50:86 Page 1 of 1

Module Type TGM550 MMJWAN TIM514 TIM510

Name ANA IMM JWAN MM ANA MM DS1 MM

Max Survivable IP Ext: 8

2.

Issue the list registered-ip-stations command to verify the stations 1408-333-8900 through 1408-333-8902, administered in Section 3 Steps 8 through 10 are registered to Avaya Communication Manager.

list registered-ip-stations REGISTERED IP STATIONS Station Ext/ Orig Port 1408-333-8900 1408-333-8901 1408-333-8902 1732-123-8002 1732-123-8003 1732-123-8004 Set Type 4620 4620 9640 4625 4625 4625 Product ID IP_Phone IP_Phone IP_Phone IP_Phone IP_Phone IP_Phone Prod Rel 2.800 2.800 1.200 2.800 1.200 2.800 Station IP Address 5.1.108.102 5.1.108.104 5.1.108.115 5.1.1.156 5.1.1.123 5.1.1.154 Net Rgn 2 2 2 1 1 1 Gatekeeper IP Address 5.1.1.4 5.1.1.4 5.1.1.4 5.1.1.4 5.1.1.4 5.1.1.4 TCP Skt y y y y y y Page 1

3.

Verify that analog/IP to analog/IP station to station calls can be established with two-way talk path within the Remote Location.

WH; Reviewed: SPOC 3/15/2007

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

29 of 32 IG550.doc

Step Description Verify that station to station calls can be established with two-way talk path between the Main 4. Location and the Remote Location. Repeat for all available phone types. 5. Verify that Avaya Communication Manager call features can be performed on the Avaya IG550 Integrated Gateway. Place an intra-office station call within the Remote Location. · Verify that the call can be transferred, forwarded, and conferenced to stations in the Remote Location. · Verify that the call can be transferred, forwarded, and conferenced to stations in the Main Location. Verify that the Avaya IG550 Integrated Gateway can recover from network connection failure. · Disconnect the T1 WAN cable for 1 minute and then reconnect the T1 WAN cable. Verify that the Avaya IG550 Integrated Gateway registers to Avaya Communication Manager and all IP stations are re-registered. · Place several intra station calls within the Remote Location. Verify that all calls are successfully connected with two-way talk path. Verify that the Avaya IG550 Integrated Gateway can recover from a C-LAN link bounce. · Place a call from an IP station in the Remote Location to a station at the Main Location. Disconnect and reconnect the C-LAN before the H.248 link loss timer expires. Verify after C-LAN is reconnected, all IP stations are re-registered. Verify that the call is still connected with two-way talk path. · Place several intra/inter Remote Location station calls. Verify that all calls are successfully connected with two-way talk path. Disconnect the T1 WAN cable. Verify that SLS becomes active after primary search timeout. The following list shows the state changes of the Avaya IG550 Integrated Gateway.

· TGM550-004(super)# The IG550 is registered with Avaya Communication Manager. · TGM550-???(super)# The IG550 lost connectivity with Avaya Communication Manager. · TGM550-SLS(super)# The IG550 is in SLS mode. The sequence of the state changes is shown below.

TGM550-004(super)# TGM550-???(super)# TGM550-???(super)# TGM550-SLS(super)#

6.

7.

8.

WH; Reviewed: SPOC 3/15/2007

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

30 of 32 IG550.doc

Step Description Continue from Step 8. Use the show extension command to verify that the IP telephones in the 9. Remote Location are registered to the Avaya IG550 Integrated Gateway after SLS is activated. Note: When the IP telephone registers to the Avaya IG550 Integrated Gateway, the IP address of the IP telephone will be displayed in the Port column.

TGM550-SLS(super)# survivable-call-engine TGM550-SLS(super-survivable-call-engine)# Extension Type Port ------------- ---------- ---------------14083338801 analog2500 v405 14083338804 analog2500 v408 14083338900 ip4620sw 5.1.108.102 14083338901 ip4620sw 5.1.108.106

show extension Cor Trk-Des Exp-Mod Flash Passwd -------- ------- ------- ----- -----unrestri yes yes unrestri yes yes unrestri yes no - ****** unrestri yes no - ******

10.

Continue from Step 9. Verify the following within the Remote Location. · IP/analog station to station calls have two-way talk path. · IP/analog station to station calls can be transferred. · IP/analog station calls can be held and un-held. · IP/analog phones can place calls to/from the PSTN and have two way talk path. Reconnect the T1 WAN cable. Verify that the Avaya IG550 Integrated Gateway automatically re-registers to Avaya Communication Manager.

11.

7. Conclusion

These Application Notes demonstrate how to provision the Avaya IG550 Integrated Gateway with Avaya Communication Manager to function as an Avaya Media Gateway. In addition, these Application Notes also describe the steps required to configure Standard Local Survivability on an Avaya IG550 Integrated Gateway.

8. Additional References

The following documents can be found at http://support.avaya.com: [1] Administrator's Guide for Avaya Communication Manager, TBD [2] Avaya IG550 CLI Reference, TBD. [3] Administration for the Avaya IG550 Integrated Media Gateways, TBD. The following documents can be found at http://www.juniper.net/techpubs/software/junos/junos82/index.html: [4] JUNOS Internet Software CLI User Guide Release 8.2 [5] JUNOS Internet Software Services Interfaces Configuration Guide Release 8.2 [6] JUNOS Internet Software Routing Protocols Configuration Guide Release 8.2

WH; Reviewed: SPOC 3/15/2007

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

31 of 32 IG550.doc

©2007 Avaya Inc. All Rights Reserved.

Avaya and the Avaya Logo are trademarks of Avaya Inc. All trademarks identified by ® and TM 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 [email protected]

WH; Reviewed: SPOC 3/15/2007

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

32 of 32 IG550.doc

Information

Microsoft Word - IG550.doc

32 pages

Report File (DMCA)

Our content is added by our users. We aim to remove reported files within 1 working day. Please use this link to notify us:

Report this file as copyright or inappropriate

32080


Notice: fwrite(): send of 199 bytes failed with errno=104 Connection reset by peer in /home/readbag.com/web/sphinxapi.php on line 531