Avaya RAD IPmux-14 TDMoIP Application Notes
  1. Manuals
  2. Brands
  3. Avaya Manuals
  4. Gateway
  5. RAD IPmux-14 TDMoIP
  6. Application notes
Avaya RAD IPmux-14 TDMoIP Application Notes

Avaya RAD IPmux-14 TDMoIP Application Notes

Gateway with communication manager
Hide thumbs
Table of Contents

Advertisement

Quick Links

Avaya Solution & Interoperability Test Lab
Application Notes for RAD IPmux-14 TDMoIP Gateway with
Avaya Communication Manager - Issue 1.0
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. Features and functionality were validated and
performance testing was conducted in order to verify operation under load. Information in
these Application Notes has been obtained through interoperability compliance testing and
additional technical discussions. Testing was conducted via the DeveloperConnection Program
at the Avaya Solution and Interoperability Test Lab.
BS; Reviewed:
SPOC 2/14/2005
Abstract
Solution & Interoperability Test Lab Application Notes
©2005 Avaya Inc. All Rights Reserved.
1 of 22
RAD-IP-Mux.doc

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the RAD IPmux-14 TDMoIP and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for Avaya RAD IPmux-14 TDMoIP

Summary of Contents for Avaya RAD IPmux-14 TDMoIP

  • Page 1 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. Features and functionality were validated and performance testing was conducted in order to verify operation under load.

  • Page 2: Sample Network Configuration

    Media Gateway, which will be referred to as the main Port Network (main PN). The remote site consists of Avaya SCC1 Media Gateway, which will be referred to as a remote PN. An Avaya DS1 Converter TN1654 board is installed in the main PN and another TN1654 board is installed in the remote PN.
  • Page 3 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.

  • Page 4: Equipment And Software Validated

    Software/Firmware Avaya S8700 Media Server in MultiConnect 2.0.1 (R012x.01.0.221.1) Configuration Avaya MCC1 Media Gateway (main Port Network) • Switch Node Interface TN573B • DS1 Converter TN1654 with “special” Y cable Avaya SCC1 Media Gateway (remote Port Network) • Expansion Interface TN570B •...
  • Page 5 Login as a superuser, entering user name as su and appropriate password. d. A main menu appears. BS; Reviewed: Solution & Interoperability Test Lab Application Notes 5 of 22 SPOC 2/14/2005 ©2005 Avaya Inc. All Rights Reserved. RAD-IP-Mux.doc...
  • Page 6 255.255.255.0, and the Default gateway is 192.168.50.1. The Host IP address of the IPmux- 14 unit at remote site (not shown here) is 192.168.60.200 and the IP mask is 255.255.255.0. BS; Reviewed: Solution & Interoperability Test Lab Application Notes 6 of 22 SPOC 2/14/2005 ©2005 Avaya Inc. All Rights Reserved. RAD-IP-Mux.doc...
  • Page 7 Display the TDM Configuration menu (Configuration > Physical layer > TDM Configuration) b. Type F to select one of the four T1 or E1 interfaces. BS; Reviewed: Solution & Interoperability Test Lab Application Notes 7 of 22 SPOC 2/14/2005 ©2005 Avaya Inc. All Rights Reserved. RAD-IP-Mux.doc...
  • Page 8 The T1 configuration at the remote site is the same as above, except that the Transmit clock source is set to External. BS; Reviewed: Solution & Interoperability Test Lab Application Notes 8 of 22 SPOC 2/14/2005 ©2005 Avaya Inc. All Rights Reserved. RAD-IP-Mux.doc...
  • Page 9 Note: The Line type is configured as Unframed G.703 and the Transmit clock source is set to External source. BS; Reviewed: Solution & Interoperability Test Lab Application Notes 9 of 22 SPOC 2/14/2005 ©2005 Avaya Inc. All Rights Reserved. RAD-IP-Mux.doc...
  • Page 10 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: Solution & Interoperability Test Lab Application Notes 10 of 22 SPOC 2/14/2005 ©2005 Avaya Inc. All Rights Reserved. RAD-IP-Mux.doc...
  • Page 11 • Default type: Set it to 10BaseT or 100BaseT. In the following example, it is set to 100baseT full duplex. BS; Reviewed: Solution & Interoperability Test Lab Application Notes 11 of 22 SPOC 2/14/2005 ©2005 Avaya Inc. All Rights Reserved. RAD-IP-Mux.doc...
  • Page 12 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. BS; Reviewed: Solution & Interoperability Test Lab Application Notes 12 of 22 SPOC 2/14/2005 ©2005 Avaya Inc. All Rights Reserved. RAD-IP-Mux.doc...
  • Page 13 Jitter Buffer – 5 msec. This sets the desired depth of the jitter buffer. Repeat steps 1 and 2 for other TDM links. BS; Reviewed: Solution & Interoperability Test Lab Application Notes 13 of 22 SPOC 2/14/2005 ©2005 Avaya Inc. All Rights Reserved. RAD-IP-Mux.doc...

  • Page 14: Configure Avaya Communication Manager

    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.
  • Page 15 Set the DS1 Converter board location by setting DS1CONV Board Location field. For example, the location of the DS1 Converter is 11A02. • Set Converter to Yes , the Type field to Avaya, and the Type of Transceivers to A The following SAT screen displays Page 1 of the fiber-link configuration:...
  • Page 16 2.048 Facility Startup Idle Code: 11101000 Line Coding: hdb3 hdb3 hdb3 hdb3 CRC? Line Termination: 75/* 75/* 75/* 75/* BS; Reviewed: Solution & Interoperability Test Lab Application Notes 16 of 22 SPOC 2/14/2005 ©2005 Avaya Inc. All Rights Reserved. RAD-IP-Mux.doc...
  • Page 17 As described in Section 1.1, at the main site, a public network T1 (E1) is connected to a T1 (E1) board in the Avaya MCC1 Media Gateway to provide Synchronization to the main PN. All the boards on the main PN derive synchronization from this common source, including the DS1 Converter board.
  • Page 18 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. Remote PN Synchronization As stated in Section 4.2, connect the External Clock port on the IPmux-14 to a T1 from public network (a common source to the main PN).
  • Page 19 B-PNC DS1 CONV CONV CONV CONV CONV TYPE 01E02 01B02 01E03 02A01 01E20 01E21 11A01 11A02 TN1654 Primary Facility:B BS; Reviewed: Solution & Interoperability Test Lab Application Notes 19 of 22 SPOC 2/14/2005 ©2005 Avaya Inc. All Rights Reserved. RAD-IP-Mux.doc...

  • Page 20: Interoperability Compliance Testing

    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.

  • Page 21: Verification Steps

    Network connectivity (T1/E1) over an IP network. 9. Additional References The following documents are relevant to these Application Notes: 1) Administrator’s Guide for Avaya Communication Manager, Issue 8, June 2004, Document Number 555-233-506. 2) Avaya Maintenance Alarms Reference, Nov 2003, Document Number 555-245-102.
  • Page 22 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.

Table of Contents