Avaya Solution & Interoperability Test Lab Application Notes for RAD IPmux-14 TDMoIP Gateway with Avaya Communication Manager - Issue 1.0 Abstract These Application Notes describe the configuration steps required to support DS1 Converter remote Port Network connectivity over an IP network using the RAD Data Communication IPmux-14 TDMoIP Gateway and Avaya S8700 Media Server Multi-Connect configuration running Avaya Communication Manager.
1. Introduction These Application Notes describe the compliance-tested configuration utilizing RAD Data Communication’s IPmux-14 TDMoIP Gateway and Avaya S8700 Media Server Multi-Connect configuration running Avaya Communication Manager, to transport DS1 Converter Remote Port Network connectivity (T1/E1s) over an IP network.
Both the main PN and remote PN derive synchronization from a common public source - a public T1 (E1). At the main site, a public network T1 (E1) is connected to a T1 (E1) board in the Avaya MCC1 Media Gateway. At the remote site, a public network T1 (E1) is connected to an External port on the RAD IPmux-14 device, and this device transmits the synchronization clock to the Avaya SCC1 Media Gateway via the T1 (E1) links associated to the DS1 Converter board.
2.
3.1. Managing IPmux-14 via Terminal Control Session Step 1. Description a. Connect IPmux-14 to a PC equipped with an ASCII terminal emulation application (for example Procomm). b. Launch the terminal emulator application and set its port parameters to 115.2kbps, 8 bits/character, 1 stop bit, and no parity. Set the terminal emulator to ANSI VT100 emulation. c. Login as a superuser, entering user name as su and appropriate password. d. A main menu appears.
3.2. Configure IP Parameters Step 1. Description a. Display the Host IP menu (Configuration > System > Host IP), and configure the IP address and the mask of the host. b. In the following example, the Host IP address is 192.168.50.200, the IP mask is 255.255.255.0, and the Default gateway is 192.168.50.1. The Host IP address of the IPmux14 unit at remote site (not shown here) is 192.168.60.200 and the IP mask is 255.255.255.0.
3.3. Configure T1/E1 Parameters at the Physical Layer Step Description 1. Configure T1 or E1 a. Display the Physical Layer menu (Configuration > Physical layer) b. Configure the TDM Interface Type as T1 or E1. In the following example, the TDM interface type is set to T1. 2. Select a T1/E1 for TDM Configuration a. Display the TDM Configuration menu (Configuration > Physical layer > TDM Configuration) b. Type F to select one of the four T1 or E1 interfaces.
Step Description 3. TDM Configuration Configure the following TDM parameters for a T1 or E1. a. Admin Status: Admin Status – set it to Enable. This enables the T1/E1 link. b. Transmit clock source – a. For the IPmux-14 at the remote site, set the clock source to External. Make sure the External clock port on the IPmux-14 at the remote site is connected to a public T1 (or public E1). See Section 4.2 for more details on clocking (Synchronization). b.
Step Description 4. The following example shows the E1 configuration for an IPmux-14 at the remote site. Note: The Line type is configured as Unframed G.703 and the Transmit clock source is set to External source. BS; Reviewed: SPOC 2/14/2005 Solution & Interoperability Test Lab Application Notes ©2005 Avaya Inc. All Rights Reserved. 9 of 22 RAD-IP-Mux.
Step Description 5. The following example shows a T1 configuration for an IPmux-14 at main site. Note: The Transmit clock source is set to Adaptive BS; Reviewed: SPOC 2/14/2005 Solution & Interoperability Test Lab Application Notes ©2005 Avaya Inc. All Rights Reserved. 10 of 22 RAD-IP-Mux.
3.4. Configure Ethernet Parameters Step Description 1. Configure an Ethernet port for network interface to an IP network, as in the following example: a. Display the ETH Configuration menu (Configuration > Physical layer > Eth Configuration) b. Type F to select the Ethernet interface to be configured. Select Network=Eth1. c. Configure the following parameters: • Channel State: set it to Enable. • Auto Negotiation: set it Enable or Disable. In the following example, it is set to Disable.
3.5. Configure Bundle Connections IPmux-14 associates each T1 (E1) with a bundle. Select a bundle on the IPmux-14 at the main site, and configure it to connect to the bundles on the IPmux-14 unit at the remote site. Step Description 1. Select a Bundle ID a. Display the Connection menu (Configuration > Connection). b. Select a Bundle ID. By selecting a bundle number, a TDM link (1-4) is specified. c. In the following example, Bundle ID 1 specifies the first TDM (T1) link.
Step Description 2. Connect the bundles Display the Bundle connection configuration menu (Configuration > Connection > Bundle connection configuration). Configure the following parameters: a. Destination IP address – IP address of IPmux-14 at remote site. For example, 192.168.60.200 b. Next Hop – For example, 192.168.50.1. c. Connection Status – Enable. d. Destination bundle – For example 1. e. OAM Connectivity – Enable.
4. Configure Avaya Communication Manager Avaya Communication Manager can be configured via a System Access Terminal (SAT). There are two basic configuration steps that need to be followed when the DS1 Remote Port Connectivity application is deployed: 1. Configure Fiber link - The DS1 Converter Complex is installed in place of the conventional fiber. The configurartion of the DS1 Converter complex is done by configuring the conventional fiber link, administering the DS1 Converter related parameters. 2.
• • • • Set the field Is one endpoint remoted via DS1 Converter Complex? to yes. This enables the configuration of ‘fiber connectivity’ over the T1s using the DS1 Converter board and pops up the related fields on the form. For Endpoint 1 (main PN), o Set the board location for the switch node interface (sni) by setting Board Location field. For example, the location of the sni board is 1E20. o Set the DS1 Converter board location by setting DS1CONV Board Location field.
The following SAT screen displays page 2 of the fiber-link configuration: display fiber-link 11 Page 2 of 2 FIBER LINK ADMINISTRATION A-PNC DS1 CONVERTER (DS1CONV) ATTRIBUTES DS1CONV Board Location: 01E21 DS1CONV Board Type: TN1654 DS1CONV Board Location: 11A02 DS1CONV Board Type: TN1654 DS1 CONVERTER FACILITIES Facility Installed? Bit Rate: Facility Startup Idle Code: Line Coding: Framing Mode: DS1CONV-1 Line Compensation: DS1CONV-2 Line Compensation: Facility Facility Facility Facility A B C D Ci
4.2. Synchronization For successful operation of this application, it is imperative that: • Both the main PN and the remote PN derive synchronization from a facility that can be traced to a common public source - a public T1 (E1). • The remote PN must derive the synchronization from the DS1-C facility on a DS1 Converter board resident in the remote PN. As described in Section 1.
main PN and the System G, and configure the T1 (DS1) on the main PN using add ds1 command via SAT, as follows: add ds1 c15 Page 1 of 2 DS1 CIRCUIT PACK Location: Bit Rate: Line Compensation: Signaling Mode: 01C15 1.544 1 isdn-ext Name: synch for main PN Line Coding: b8zs Framing Mode: esf Interface Companding: mulaw Idle Code: 11111111 Slip Detection? n Near-end CSU Type: other Here the T1 board in slot 01C15 is connected to a T1 board in another Avaya Media Gateway. 4.2.2.
To further validate the quality of the Synchronization source, enter list measurements ds1-facility summary xy command on SAT, where x is the location of the DS1 Converter board in the remote PN and y is the DS1-C facility name on that board such as A, B, C or D. Verify that there are no Errored Seconds or Severely Errored Seconds. The following example lists the measurements for the DS1-C facility A (11a02a) on the remote PN.
5. Interoperability Compliance Testing The interoperability compliance testing focused on transporting the T1/E1s utilized for Avaya DS1 Converter Remote Port Network connectivity, over an IP network using the RAD IPmux-14 TDMoIP Gateway device. The testing was performed for transporting four T1s from an Avaya MCC1 Media Gateway (main PN) at the main site to an Avaya SCC1 Media Gateway (remote PN) at the remote site. The same tests were repeated for transporting four E1s. 5.1.
6. Verification Steps The following steps may be used to verify the configuration and connectivity: • Verify that the remote PN is deriving synchronization from the DS1C facility, as described in Section 4.2.2. • Verify that a voice call from remote PN to main PN is successful. 7. Support For technical support on the RAD product line, consult www.rad.com or contact RAD Technical Support at phone number 1-800-444-7234. 8.
©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.
