Configuring a PRI Trunk Connection between an Avaya S8300
Media Server and an Avaya G700 Media Gateway running
Avaya MultiVantage™ Software and a Siemens Hicom 300.
Issue 1.0
ABSTRACT
Many multi-location enterprises have telecommunications equipment from
vendors that do not provide a gentle migration path to IP converged platforms.
Avaya’s Enterprise Class IP Solutions (ECLIPS) enable a gradual adoption of
IP technology for Third-party PBXs and enables the adoption of the valueadded capabilities of Avaya’s MultiVantage™ Software while providing a
platform to host future applications that will further enhance the enterprise’s
operations.
Following the instructions in these Application Notes facilitates the GentleMigration of a Siemens Hicom 300 PBX to the Avaya ECLIPS platform running
the Avaya MultiVantage Software for call processing. A minimal amount of
new hardware is needed to complete the migration including the Avaya™
S8300 Media Server, the Avaya™ G700 Media Gateway, Avaya™ IP
telephones and the new Avaya™ GUI administration tools.
This solution’s return on investment (ROI) is very high because it does not
require a fork-lift removal of existing hardware, capitalizes on existing phone
assets and the users’ knowledge of the existing user interface, and allows the
enterprise to migrate only those users who can best utilize the productivity
enhancing features of the Avaya MultiVantage Software. The platform can
expand to accommodate the entire enterprise’s organization over time at a
pace the customer dictates.
The configuration shown in figure 1 illustrates a PRI Trunk Connection between an Avaya
S8300 Media Server and an Avaya G700 Media Gateway (S8300/G700) running Avaya
MultiVantage Software placed as an adjunct to a Siemens Hicom 300.
The main Central Office connection for the solution is made through the Siemens Hicom 300.
Additional Central Office lines can be connected to the S8300/G700 in order to facilitate the
use of Avaya™ Extension to Cellular (EC500) and other Avaya MultiVantage Software
features.
This document assumes the reader has a basic knowledge of programming Multivantage and
Hicom platforms. Basic interoperability between S8300/G700 and Hicom 300 and how it was
accomplished is described within these application notes. It should be noted that the
interoperability of the S8300/G700 and Hicom 300 is established on basic network
fundamentals, and more advanced areas of networking and call routing such as QSIG, AAR
and ARS, while functional in this configuration, are not within the scope of this document. E-1
connectivity is possible but requires additional hardware and software upgrades. The
Siemens Hipath series is not covered in this document. The Hipath has very different user
interfaces and hardware architecture.
The configuration used to test performance of this solution was established in an Avaya Lab
setting within the guidelines and use parameters allowed in the user licenses acquired with the
equipment and software listed below.
PlatformVersion
Avaya MultiVantage Software1.2
Avaya S8300 Media Server213.0
Avaya G700 Media Gateway3.12
Avaya™ 4612 IP Phones46XXCommon.V36
Avaya™ 4624 IP Phones46XXCommon.V36
Avaya MM710 T-1 InterfaceFirmware version 5
Siemens Hicom 300 30 EPRelease 9006.5
DSC80 ProcessorFirmware version D961-D
TMDN64P T-1 Interface (Q2484-X)Firmware version D467-C
Optiset E Digital Advanced Plus PhonesModel 69671
3. Requirements:
Avaya S8300 Media Server and an Avaya G700 Media Gateway:
Software:
1. Avaya MultiVantage SoftwareRelease 1.2 or newer
2. G700 Media Gateway FirmwareRelease 3.12or newer
3. S8300 Media Server SoftwareRelease 213.0or newer
Hardware:
1. MM710 DS1 Circuit pack. Installer needs to determine the number of trunks cards
that will be needed for traffic requirements. Consideration must be made for the
available slots and resources of the Hicom.
2. T-1 Interface cable. Connects the MM710 T-1 RJ45 interface port or the TN464 DS1
circuit pack to the Hicom. The actual cable needs to be custom built.
Siemens Hicom 300:
For this application to be successful, the intended switch must have:
1. Available slots for the T-1 boards.
2. Available purchased software ports for the T-1 spans.
3. T-1 boards must be compatible to software version.
4. If software or port capacities need to be upgraded, there are two options.
a. Siemens can be contacted and they will upgrade the system.
b. The software on DAT tape is purchased from Siemens or a vendor. The customer
1. Recommended Siemens Hicom 300. Release 9006.5 or newer.
2. Firmware for the boards and phones are included in the core software.
Hardware:
1. TNBN64P and TNDN64 can be programmed to run PRI and NI2.
2. TMDN TMD24 can only be used with PRI.
Board type used is dependant on software and hardware release of the switch.
4. Cable schematic:
Note: A length of 4-wire cable is needed to make the connection to each PRI
circuit card. The Pin assignments for each are as follows.
Siemens TMDN64P (25 pair amphenol)
XTIPpin 16 RTIPpin 13
XRING pin 41 RRINGpin 38
MM710 (RJ45)
XTIPpin 4RTIPpin 1
XRING pin 5RRINGpin 2
TN464 DS1 (wall field)
XTIPpin 22 RTIPpin 23
XRING pin 47 RRINGpin 48
5. S8300/G700 Configurations:
The following pages are excerpts of an actual system administration session using the
Avaya VisAbility™ Software Suite.
DS1 Interface: ISDN maximizes the number of connections between the switches due to the
fast processing of calls across that medium. ISDN also allows for Caller ID, Call Tracing, Call
Return and many other features. Configure the DS1 form as described below. Select “isdnpri” for the Signaling Mode, this allows for Facility and Non-facility Associated Signaling.
Select “b8zs” for the line coding which is required when running ISDN. Framing Mode should
be “ESF” to allow for best signaling quality. Setting the Connect and Interface prompts to
“PBX” and “Network” allows the MM710 to have control over glare conditions. This allows the
MM710 to have priority over circuit assignment and force the switch on the other end to
continue searching for an open B-Channel. All other prompts are default. If using NI-2
Trunk Group: Create a Trunk Group and select “isdn” as the Group Type and a TAC
number based on your switches dial-plan. Ensure “PRI/BRI” is the Carrier Medium, this is
used for ISDN trunks. Set Dial Access to “Y” and Service type is “tie”, this gives the most
universal type of connection. All other prompts are default.
Figure 4. Trunk–Group Administration
Signaling Group: Create a Signaling Group for the PRI D-channel. The Group Type
default is “isdn-pri”; this creates a channel to control the Bearer channels on the T-1 card.
Select the T-1 port that will be used as the Primary D-channel and assign the Trunk Group for
Channel Selection. All other prompts are default.
Trunk Group Members:Assign trunk ports to the Trunk Group. Up to 255 ports can be
assigned to each ISDN Trunk Group. The Sig Grp prompt will display the signaling group after
the Trunk Group is created and assigned to the Signaling Group.
Figure 5. Assign trunk Group Members
6. Hicom Configurations:
The following listing of Command Line Interface (CLI) text is intended to be an accurate
representation of the actual administrative visuals for implementing the translations
required for the Hicom 300.