Mediant 3000

Setup Guide
Release 1.0

March 2011
© 2011 Avaya Inc. Software that permits one user to interface with the Software. Units
All Rights Reserved. may be linked to a specific, identified Server.
• Named User License (NU):
Notice End User may: (i) install and use the Software on a single
While reasonable efforts have been made to ensure that the information in this Designated Processor or Server per authorized Named User
document is complete and accurate at the time of printing, Avaya assumes no (defined below); or (ii) install and use the Software on a Server so
liability for any errors. Avaya reserves the right to make changes and long as only authorized Named Users access and use the
corrections to the information in this document without the obligation to notify Software. “Named User” means a user or device that has been
any person or organization of such changes. expressly authorized by Avaya to access and use the Software. At
Avaya's sole discretion, a “Named User” may be, without limitation,
Documentation disclaimer designated by name, corporate function (for example, webmaster
Avaya shall not be responsible for any modifications, additions, or deletions to or helpdesk), an e-mail or voice mail account in the name of a
the original published version of this documentation unless such modifications, person or corporate function, or a directory entry in the
additions, or deletions were performed by Avaya. administrative database utilized by the Software that permits one
End User agree to indemnify and hold harmless Avaya, Avaya's agents, user to interface with the Software.
servants and employees against all claims, lawsuits, demands and judgments • Shrinkwrap License (SR):
arising out of, or in connection with, subsequent modifications, additions or Customer may install and use the Software in accordance with the
deletions to this documentation, to the extent made by End User. terms and conditions of the applicable license agreements, such as
“shrinkwrap” or “clickthrough” license accompanying or applicable
Link disclaimer to the Software (“Shrinkwrap License”). (See Third-party
Avaya is not responsible for the contents or reliability of any linked Websites Components for more information).
referenced within this site or documentation(s) provided by Avaya. Avaya is not
Copyright
responsible for the accuracy of any information, statement or content provided
on these sites and does not necessarily endorse the products, services, or Except where expressly stated otherwise, no use should be made of materials
information described or offered within them. Avaya does not guarantee that on this site, the Documentation(s) and Product(s) provided by Avaya. All
these links will work all the time and has no control over the availability of the content on this site, the documentation(s) and the product(s) provided by
linked pages. Avaya including the selection, arrangement and design of the content is owned
either by Avaya or its licensors and is protected by copyright and other
Warranty intellectual property laws including the sui generis rights relating to the
Avaya provides a limited warranty on this product. Refer to your sales protection of databases. You may not modify, copy, reproduce, republish,
agreement to establish the terms of the limited warranty. In addition, Avaya’s upload, post, transmit or distribute in any way any content, in whole or in part,
standard warranty language, as well as information regarding support for this including any code and software. Unauthorized reproduction, transmission,
product, while under warranty, is available to Avaya customers and other dissemination, storage, and or use without the express written consent of
parties through the Avaya Support Website: http://www.avaya.com/support. Avaya can be a criminal, as well as a civil, offense under the applicable law.
Please note that if you acquired the product from an authorized Avaya reseller
Third Party Components
outside of the United States and Canada, the warranty is provided to you by the
said Avaya reseller and not by Avaya. Certain software programs or portions thereof included in the Product may
contain software distributed under third party agreements (“Third Party
Licenses Components”), which may contain terms that expand or limit rights to use
The software license terms available on the Avaya Website, certain portions of the Product (“Third Party Terms”). Information regarding
http://support.avaya.com/licenseinfo/ are applicable to anyone who downloads, distributed Linux OS source code (for those Products that have distributed the
uses and/or installs Avaya software, purchased from Avaya Inc., any Avaya Linux OS source code), and identifying the copyright holders of the Third Party
affiliate, or an authorized Avaya reseller (as applicable) under a commercial Components and the Third Party Terms that apply to them is available on the
agreement with Avaya or an authorized Avaya reseller. Unless otherwise Avaya Support Website: http://support.avaya.com/Copyright.
agreed to by Avaya in writing, Avaya does not extend this license if the
Preventing toll fraud
software was obtained from anyone other than Avaya, an Avaya affiliate or an
Avaya authorized reseller, and Avaya reserves the right to take legal action “Toll fraud” is the unauthorized use of your telecommunications system by an
against you and anyone else using or selling the software without a license. By unauthorized party (for example, a person who is not a corporate employee,
installing, downloading or using the software, or authorizing others to do so, agent, subcontractor, or is not working on your company's behalf). Be aware
you, on behalf of yourself and the entity for whom you are installing, that there can be a risk of toll fraud associated with your system and that, if toll
downloading or using the software (hereinafter referred to interchangeably as fraud occurs, it can result in substantial additional charges for your
“you” and “end user”), agree to these terms and conditions and create a telecommunications services.
binding contract between you and Avaya Inc. Or the applicable Avaya affiliate
Avaya fraud intervention
(“Avaya”).
If you suspect that you are being victimized by toll fraud and you need technical
Avaya grants End User a license within the scope of the license types
assistance or support, call Technical Service Center Toll Fraud Intervention
described below. The applicable number of licenses and units of capacity for
Hotline at +1-800-643-2353 for the United States and Canada. For additional
which the license is granted will be one (1), unless a different number of
support telephone numbers, see the Avaya Support Website:
licenses or units of capacity is specified in the Documentation or other
materials available to End User. “Designated Processor” means a single http://www.support.avaya.com/.
stand-alone computing device. “Server” means a Designated Processor that Suspected security vulnerabilities with Avaya products should be reported to
hosts a software application to be accessed by multiple users. “Software” Avaya by sending mail to:[email protected].
means the computer programs in object code, originally licensed by Avaya and
ultimately utilized by End User, whether as stand-alone products or Trademarks
pre-installed on Hardware. “Hardware” means the standard hardware originally Avaya® and Avaya Aura™ are trademarks of Avaya Inc.
sold by Avaya and ultimately utilized by End User. The trademarks, logos and service marks (“Marks”) displayed in this site, the
documentation(s) and product(s) provided by Avaya are the registered or
License types
unregistered Marks of Avaya, its affiliates, or other third parties. Users are not
• Designated System(s) License (DS):
permitted to use such Marks without prior written consent from Avaya or such
End User may install and use each copy of the Software on only
third party which may own the Mark. Nothing contained in this site, the
one Designated Processor, unless a different number of
documentation(s) and product(s) should be construed as granting, by
Designated Processors is indicated in the Documentation or other
implication, estoppel, or otherwise, any license or right in and to the Marks
materials available to End User. Avaya may require the Designated
without the express written permission of Avaya or the applicable third party.
Processor(s) to be identified by type, serial number, feature key,
location or other specific designation, or to be provided by End All non-Avaya trademarks are the property of their respective owners.
User to Avaya through electronic means established by Avaya Linux® is the registered trademark of Linus Torvalds in the U.S.and other
specifically for this purpose. countries.
• Concurrent User License (CU):
End User may install and use the Software on multiple Designated Downloading documents
Processors or one or more Servers, so long as only the licensed For the most current versions of documentation, see the Avaya Support
number of Units are accessing and using the Software at any given Website: http://www.avaya.com/support.
time. A “Unit” means the unit on which Avaya, at its sole discretion,
bases the pricing of its licenses and can be, without limitation, an Contact Avaya Support
agent, port or user, an e-mail or voice mail account in the name of a Avaya provides a telephone number for you to use to report problems or to ask
person or corporate function (e.g., webmaster or helpdesk), or a questions about your product. The support telephone number is
directory entry in the administrative database utilized by the
1-800-242-2121 in the United States. For additional support telephone
numbers, see the Avaya Website: http://www.avaya.com/support.
 Contents

Mediant 3000 Media Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Assigning an IP address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
Support of multiple gateways and multiple CM servers . . . . . . . . . . . . . . . 8
What this document covers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Needed equipment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Laptop access for staging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Pre-configuration tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Mediant 3000 Media Gateway configuration . . . . . . . . . . . . . . . . . . . . . . . . 12
Logging into the EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Configure an IP address for the system . . . . . . . . . . . . . . . . . . . . . . . . 13
Adding the device in EMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Adding a Region to the deployed device. . . . . . . . . . . . . . . . . . . . . . 14
Adding a device to the region. . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Assigning the global IP address . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Configuring network support parameters . . . . . . . . . . . . . . . . . . . . . . . 15
Locking the device. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Configuring the TP-6310 parameters . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Configuring DS3 trunk on the TP-6310 . . . . . . . . . . . . . . . . . . . . . . . . . 20
To provision a DS3 interface: . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
Configuring ISDN NFAS Trunk Groups . . . . . . . . . . . . . . . . . . . . . . . . 22
To configure ISDN-NFAS Trunks offline . . . . . . . . . . . . . . . . . . . . . . 23
To configure ISDN-NFAS Trunks at real time . . . . . . . . . . . . . . . . . . . 24
Configuring SIP Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Call routing configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
Configuring inbound call routing on the TP-6310 . . . . . . . . . . . . . . . . . . . 27
Configuring outbound call routing on the TP-6310 . . . . . . . . . . . . . . . . . . 29
Unlocking the TP6310 board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Avaya Communication Manager configuration . . . . . . . . . . . . . . . . . . . . . . 33
Verifying system capacities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Assigning IP codec sets. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Assigning IP network regions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Assigning a node name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Adding a signaling group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Adding a trunk group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Defining public numbering format . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Mapping inbound calls (when required) . . . . . . . . . . . . . . . . . . . . . . . . 36
Mapping outbound calls. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
Session Manager configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
System Manager configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
Specifying SIP domains . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

5 Mediant 3000 Media Gateway Setup March 2011

 Adding locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
Setting up the Adaptation module . . . . . . . . . . . . . . . . . . . . . . . . . 40
Adding Mediant 3000 SIP element . . . . . . . . . . . . . . . . . . . . . . . . . 41
Setting up Time Ranges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Defining Policies and Time of day for Mediant 3000 . . . . . . . . . . . . . . . 43
Verifying network connectivity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Verifying call routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Mediant 3000 call routing: setting up 'Tel to IP' for redundancy and performance . . . 46
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
C-LAN and signaling group discussion . . . . . . . . . . . . . . . . . . . . . . . . 46
Tel to IP: alternate routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Tel to IP: routing based on ANI . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Example scenario . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
Overview of the necessary steps . . . . . . . . . . . . . . . . . . . . . . . . . . 50
Performing Mediant 3000 administration via EMS. . . . . . . . . . . . . . . . . 50

Mediant 3000 Media Gateway Setup March 2011 6

 Mediant 3000 Setup

Mediant 3000 Setup

Mediant 3000 Media Gateway

The Mediant 3000 is a feature rich high density SIP trunk gateway. The Mediant 3000 offers
channel scalability of up to 1932 DSO's (to carry voice calls) and 84 D-channels in a compact 19"
- 2U chassis. Additionally, Mediant 3000 delivers the same carrier-grade availability that service
providers are accustomed to on their legacy equipment. Mediant 3000 also provides trunking
and access protocol, such as PRI. Mediant 3000 meets the needs of wireline, cable, cellular, and
mixed service providers.
Enterprises migrate to VOIP due to cost considerations and for a richer, integrated telephony
service. An enterprise can choose to connect to a PSTN Service Provider or to an Internet
Telephony Service Provider (ITSP) or both. Large enterprises deploy business critical contact
centers where the high availability of Mediant 3000 is a key factor. Mediant 3000 supports
high-density PSTN interfaces, such as T3 and OC3 (future release).The proven interoperability
of Mediant 3000 with different PBXs and PSTN switches facilitates smooth deployment.

Sample configuration using Mediant 3000 Media Gateway

Mediant 3000 has a compact footprint (2U) that meets needs of both service providers with
geographically dispersed networks, as well as those of large enterprises, where reliable and
dense VoIP gateways are necessary for business-critical communications.

Mediant 3000 Media Gateway Setup March 2011 7

Mediant 3000 Setup

Assigning an IP address
Mediant 3000 HA has two TP-6310 blades (Active and Redundant). Each blade has a private IP
address (different from one another) for maintenance and initial configuration. When you initially
configure the blades (using BootP/DHCP), the BootP server communicates with the two blades
using these two IP addresses. In addition to these private IP addresses, the device has a global
IP address used by the Active blade for communicating with the IP network. This global IP
address is configured using the.ini file, Web, or EMS management tools and is a valid IP
address that is different from the two private IP addresses of the blades, but in the same subnet.
From the perspective of the WAN interface (for example: proxy server), the product has a single
IP address (the global IP address); the redundant blade is a transparent entity.

Support of multiple gateways and multiple CM servers

To meet high bandwidth requirements and provide more bandwidth than a single Mediant 3000
can support, as well as provide redundancy, Mediant 3000 supports the following
configurations:
● Multiple Mediant 3000 media gateway platforms distributing incoming traffic into multiple
Communication Manager servers
● Multiple Mediant 3000 media gateway systems sending incoming traffic into a single
Communication Manager server
● A single Mediant 3000 media gateway distributing incoming traffic across multiple
Communication Manager servers
Traffic distribution into multiple Communication Manager servers is controlled by the routing
table on the TP6310 and you must configure the TP6310 Tel to IP Route Table with different
CLAN IP addresses that correspond to different Communication Manager servers or different
Session Managers.

8 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

Traffic distribution in multiple gateways and multiple CM servers configuration

What this document covers

This document focuses on the required equipment and the following administration steps for
configuring:
● A SIP trunk between Mediant 3000 Media Gateway and Avaya Communication Manager
● Inbound and outbound call routing
● Load balancing of inbound traffic among multiple TN799DP C-LAN circuit packs
● Alternate routing of inbound traffic when the C-LANs become inaccessible or are busied
out
● SNMP trap receivers to which Mediant 3000 Media Gateway reports alarms

Mediant 3000 Media Gateway Setup March 2011 9

Mediant 3000 Setup

Needed equipment
Mediant 3000 Media Gateway is shipped with the following equipment:
● Mediant 3000 Media Gateway, which at a minimum includes the following components:
- Mediant 3000 chassis.
● A Linux-based server for the Element Management System (EMS) server software.
- Linux CentOS 5.3 Rev 4.
- 1 console cable for network administration.
- 1 DVD - 5.8.90 for EMS Server.
- 1 DVD software Installation & Documentation 5.2.x (media gateway software, EMS
client and server software).

In addition, the following equipment is also required:

● The Services Platform Server (SPS) for the EMS client software that is used for
operations, administration, management, and provisioning functions. This server is
connected to the customer’s network. A Windows 2008 computer is a possible platform for
the EMS client. Avaya Services has chosen the Windows 2008 server as its standard
platform.
● Management platform to handle secure access and control if customer has a maintenance
contract with Avaya. For information on how to install and setup this computer, see Secure
Access and Control at: http://support.avaya.com/sac/.

The customer supplies the following equipment:

● A standard 19-in. (48-cm) four post equipment rack that is properly installed and solidly
secured to EIA-310D or equivalent standards. The rack cabinet must have adequate
ventilation.
● DC/AC power supply.
● Power cable from gateway to DC/AC power supply. Wiring needs to be stripped and
connectors attached on site.
● CAT5 Ethernet cable (gigabit).
● T3 cable to connect the Trunk Processing Modules (TP-6310s). This cable requires a
female mini-SMB connector.
● One incoming twin fiber optic cable with Dual-LC plug for each STM-1 optical interface.
● Avaya S8720 in XL configuration or S8730 Server with a DAL2 board installed, configured,
and operating. Only hardware duplication supports Mediant 3000 Media Gateway.

10 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

● Avaya G650 Media Gateway installed and operating. The media gateway must have an
adequate number of TN799DP C-LAN circuit packs and TN2302AP IP Media Processors
or TN2602AP IP Media Resource 320 circuit packs.
Mediant 3000 Media Gateway comes with
● 1 or 2 Trunk Processing Modules (TP-6310s).
- The second TP6310 functions as a standby module for redundancy.
● 2 SA/RTM for System Controllers, 2 RTM for TP-6310 (Active/Redundant type depending
on configuration). The active TP-6310 RTM has PSTN interfaces, and the redundant
TP-6310 does not.
● Cable to DS3 line (50-ft [15 m]).

Other equipment and items:

● DSX3 broadband patch panel with associated monitoring patch panel jacks and cables
(recommended). The patch panel, collocated with Mediant 3000 Media Gateway, allows
the unobtrusive observation of incoming and outgoing traffic on the DS3 connection.
Contact your Avaya representative for details.
● Laptop computer with EMS client installed for staging
● Filled-out planning form with IP addresses. A blank planning form is available on http:/
support.avaya.com within the product documentation for Mediant 3000 Media Gateway. IP
addresses are required for several items, including certain TN circuit packs, such as
C-LANs, MedPros, and VAL; network servers, such as DNS, NTP, and NMS; and certain
components on Mediant 3000 Media Gateway. The following table provides guidance on
which Mediant 3000 item need IP addresses:

Mediant Module IP Address/Mask

3000 Slots

1 TP 6310
2 Alarm boards
3 TP 6310
4 Alarm boards

Laptop access for staging

If you are staging Mediant 3000 Media Gateway, make sure you have the following equipment
and applications available. For detailed information on staging, refer to the internal Job Aid:
Requirements for Staging Mediant 3000 High Density Trunk Gateway R1 Mediant 3000 HDTG.

Mediant 3000 Media Gateway Setup March 2011 11

Mediant 3000 Setup

● Laptop computer running Windows 2008.

● Internet Explorer, version 6.0 or higher.
● Ethereal, version 0.10. 12 or higher, or Wireshark, version 0.99.4 or higher, with a specific
AudioCodes plug-in (provided with DVD that ships with Mediant 3000 Media Gateway).
● ACSyslog093 Server (provided with DVD that ships with Mediant 3000 Media Gateway).
● BootP server (provided with DVD that ships with Mediant 3000 Media Gateway)
● HyperTerminal programs.
Optional Equipments (if you are using EMS server):
● EMS client software.
● Console cable for EMS server is (Cable and serial adapter is shipped with EMS Server)

Pre-configuration tasks
Before beginning the configuration, make sure that you have all the equipment and it is set up to
simulate the customer’s environment as much as possible, including using the customer’s time
zone.
In addition, ensure the following:
● Avaya Mediant 3000 Media Gateway has power. Refer to Installing and Operating the
Avaya Mediant 3000 Media Gateway (03-601918).
● AudioCodes EMS server software is installed on the Linux server. Refer to EMS Server
Installation, Operation, and Maintenance Manual (LTRT-94108) and EMS User’s Manual
(LTRT-91006)
● AudioCodes EMS client software is installed on the laptop. Refer to EMS Server
Installation, Operation, and Maintenance Manual (LTRT-94108) and EMS User’s Manual
(LTRT-91006)
● EMS server has the current software, available from PLDS.

Mediant 3000 Media Gateway configuration

! Important:
Important: This document uses only the EMS client for administration. Web and GUI
Interface are also options for administration.

12 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

The following sections describe how to configure the SIP and PSTN trunks and call routing for
Mediant 3000 Media Gateway. You configure the media gateway using the GUI-based Element
Management System (EMS). If configuring in a staging area, the EMS client software is
installed on the staging laptop. If configuring at the customer’s site, the EMS client software is
installed on the SPS Server.
The first part covers configuring the network support parameters. The second part covers
configuring the Trunk Processing Module (TP-6310) board, which controls the call signaling for
and routing between the SIP and DS3 interfaces to which it is connected.
Note:
Note: Avaya suggests make changes to Mediant 3000 only through the EMS server.

Logging into the EMS

Before starting this procedure, the Element Management System (EMS) server software must
be installed and configured on the EMS and the EMS client software must be installed on the
SPS Server (Windows 2008 server).

1. Double-click the desktop icon on the computer screen.

2. Type in the login, password, and the server IP address of the EMS server.
Note:
Note: If you are using three or more Mediant 3000, you must purchase the EMS server,
and make all the changes through the EMS server.

Configure an IP address for the system

Mediant 3000 has one or two TP-6310 blades: Active and Redundant. Each blade has a private
IP address (different from one another) for maintenance and initial configuration. When you
initially configure the blades using BootP/DHCP, the BootP server uses these two IP addresses
to communicate with the two blades. In addition to these private IP addresses, the device has a
global IP address that the Active blade uses for communicating with the IP network. This global
IP address is configured using the ini file, Web, or EMS management tools and is a valid IP
address that is different than the two private IP addresses of the blades, but in the same subnet.
From the perspective of the WAN interface, for example, the proxy server, the two blades have
the same IP address or global IP address. However, the redundant blade is a transparent entity.

Adding the device in EMS

Once you define and configure the IP address of the device, you can add the device to the
Element Management System (EMS).

Mediant 3000 Media Gateway Setup March 2011 13

Mediant 3000 Setup

To add the device to the EMS, log into EMS and adhere to the following main stages:
1. Add a Region
2. Add the software device version file (cmp) to the EMS Software Manager
3. Define the IP address and other initial setting of the device.

Adding a Region to the deployed device

1. Click on the Globe icon under the MG Tree.
2. Click Add Region.
The system displays the Region dialog box.
3. In the Region Name field, enter a name for the region.
4. Click OK.
The system adds the region to the MG Tree list.
Note:
Note: To verify that the device is functional, ping the IP address of the device.
5. Add the software version file of the device to the Software Manager.

Adding a device to the region

1. To select Add MG, click on the Region icon added in the section, Adding a Region to the
deployed device on page 14, to the deployed device.
MG Information screen appears.
2. Enter the following details:
In the MG name field, add an arbitrary name.
In the IP Address field, add the private, local IP address that you have assigned to the
blade Slot 1 or the global IP address.
Enter the Community Read / Write strings.
3. Click OK.
The system adds the device to Region in MG List.
You can configure the EMS server with the private IP address of the blade in Slot 1; Mediant
3000 status window displays it.

Assigning the global IP address

1. Select Mediant 3000, from the MG tree.
2. Double-click the active blade in the status window.

14 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

3. Select Network parameters from General Configuration frame.

The system displays the Network Parameters screen.
4. Define the global IP address.
The global IP address must be a unique address that resides in the same subnet as the
private IP addresses that were assigned to Mediant 3000 blades.
5. Click Apply.
6. Click Home on EMS navigation bar.
7. Click Reset.
Ensure that you select the Burn Configuration into Flash Memory check box.
Note:
Note: Once you reset Mediant 3000, you can gain access to Mediant 3000 only when
you use the global IP address.
8. Use the new global IP address, to add Mediant 3000 to the EMS.
9. Right-click the active blade, and select Configuration > Upload.
The EMS server synchronizes with the blade configuration settings.
To verify that Mediant 3000 is functional, ping the IP address. If it is functional, the EMS Status
screen displays a graphic representation of it. The screen displays the active blade in black and
the redundant blade in blue.
To delete Mediant 3000 from the EMS, right-click Mediant 3000 on the MG tree and select
Remove MG.

Configuring network support parameters

The main provisioning screen is the logical or geographical area where the media gateway
resides. This procedure configures the IP addresses you can use to gain access to an NTP
server and SNMP trap receivers.

Mediant 3000 Media Gateway Setup March 2011 15

Mediant 3000 Setup

1. On the right pane under Regions List, double-click the first row entry.

2. In the right pane under the MGs List, select the entry corresponding to the Mediant 3000
Media Gateway device to be configured.

3. Under the Media Gateway pane, double-click on the active TP board.

16 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

4. Select the General config Tab.

5. Click Network > Applications.

6. Enter NTP server information.

Mediant 3000 Media Gateway Setup March 2011 17

Mediant 3000 Setup

7. Enter the following DNS server information.

a. In the DNS Primary Server Type field, select the correct server type from the drop-
down menu.
b. In the DNS Primary Server field, type in the IP address for the primary DNS Server.
c. In the DNS Secondary Server Type field, select the correct server type from the drop-
down menu.
d. In the DNS Secondary Server field, type in the IP address for the secondary DNS
Server
:

8. Click Apply > Close.

Locking the device

1. On the Navigation bar, click the Management tab > Navigation Tree > Management
Configuration > Maintenance Action page.
2. Select one of the following options for Graceful Option.

18 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

a. Yes: The device is locked only after the user-defined time in the Lock Timeout field
(refer to Step 3) expires or active traffic does not exist any more. In addition, no new
traffic is accepted.
b. No: The device is locked regardless of traffic. Any existing traffic is terminated
immediately.
3. In the Lock Timeout field, enter the time (in seconds) after which the device locks.
Note:
Note: If no traffic exists and the time has not yet expired, the device locks.
4. Click the Lock button.
The system displays a confirmation message box.
5. Click OK to lock the device.
Note:
Note: If Graceful Option is set to Yes, the lock is delayed and the system displays a
screen showing the number of remaining calls and time. Otherwise, the lock
process begins immediately.

Configuring the TP-6310 parameters

Before starting these steps, ensure that the Trunk Processing Module (TP-6310) is locked. For
more information, see Locking the device on page 18.

1. Double-click TP-6310 shown in black.

Mediant 3000 Media Gateway Setup March 2011 19

Mediant 3000 Setup

2. Select General Config > Info and Security > General Setting.

3. Set the SSL/TLS Negotiation field to TLSv1Only.

4. Use the default settings for the other fields.
5. Set Enable Early Media under General Info to Yes.
6. Click Apply > Close.

Configuring DS3 trunk on the TP-6310

This section describes how to provision the DS3 Trunk Group (TP-6310 blades only).

To provision a DS3 interface:

1. Select the required device from the MG tree.
The status pane shows the graphic display of the selected device.
2. Double-click the active blade.
Tab bar is displayed.

20 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

3. From the Tab bar, select the General Configuration tab.

4. Click System Settings.

5. On the System Settings Parameters (6310) screen, select CopperDs3 from the
Transmission Type.
6. Click Apply and close the active window.
7. Click T3 on the Tab bar.
The T3 table lists all the T3 interfaces.

8. Select a T3 interface row.

Mediant 3000 Media Gateway Setup March 2011 21

Mediant 3000 Setup

9. Click Properties in the information pane.

The system displays DS3 Parameters Provisioning screen with the DS3 General Info
tab selected.
10. Configure the DS3 interface according to your requirements.
11. Click Apply and close the active window.

Configuring ISDN NFAS Trunk Groups

This section describes how to configure ISDN-NFAS trunks as an initial configuration.
In a regular T1 ISDN trunk, a single 64-kbps channel carries signaling for the other 23
B-channels. This is called the D-channel and it usually resides on timeslot #24. The ISDN
Non-Facility Associated Signaling (NFAS) feature enables the use of a single D-channel to
control multiple PRI interfaces.
With NFAS, you can define a group of T1 trunks, called an NFAS group, in which a single
D-channel carries ISDN signaling messages for the entire group. You can use the B-channels of
the NFAS group to carry traffic, such as voice or data. The NFAS mechanism also enables
definition of a backup D-channel on a different T1 trunk, to be used if the primary D-channel
fails.

22 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

The NFAS group can comprise up to 10 T1 trunks. Each T1 trunk is called an NFAS member.
The T1 trunk whose D-channel is used for signaling is called the Primary NFAS Trunk. The T1
trunk whose D-channel is used for backup signaling is called the Backup NFAS Trunk. The
primary and backup trunks each carry 23 B-channels while all other NFAS trunks each carry 24
B-channels.
You can configure ISDN-NFAS Trunks offline or in real time.

To configure ISDN-NFAS Trunks offline

1. Select the required device from the MG tree.
The status pane displays the selected device graphically.
2. Double-click the Active blade.
3. Select E1/T1 trunks from the Tab Bar.
The system displays DS1 Carriers list table.
4. Double-click the trunk from the DS1 Carriers list.
The system displays SIP provisioning screen.
5. Select the ISDN Settings tab.
The system displays ISDN Setting screen.

6. Perform the following configuration:

a. Configure each trunk in the group with the same values for the Termination Side
parameter.

Mediant 3000 Media Gateway Setup March 2011 23

Mediant 3000 Setup

b. Select the EXPLICIT INTERFACE ID check box to configure the Interface ID (see Step
d) of a NFAS Trunk. If this field is not set, only the Trunk ID is recognized.
c. Select Primary NFAS Trunk, from the D-Channel Configuration drop-down list, for
the T1 trunk whose D-channel is used for signaling or Backup NFAS Trunk for the T1
trunk whose D-channel is used for backup signaling.
d. In the ISDN NFAS Interface ID field enter the Interface ID (0 - 255) of the trunk in the
NFAS group.
e. In the Group Number field, enter the device's NFAS Group Number. If this field is set
to 0, the trunk is not an NFAS trunk.
f. Click Apply.
g. Use Profiles to apply the configured fields to multiple trunks.
7. Select the General Settings tab to configure each trunk in the group with the same values
for the following parameters:
a. Protocol Type
b. Framing Method
c. Line Code
8. Write and reset the device after configuring all the trunks.

To configure ISDN-NFAS Trunks at real time

The procedure below describes how to configure ISDN-NFAS trunks real time. The
configuration process is the same as the initial Offline configuration, but the sequence of
configuring or locking the trunks is important.
1. To unlock an NFAS Group:
a. If there is a Backup trunk for this group, unlock it.
b. Before unlocking any NFAS trunks, unlock the Primary trunk.
c. Unlock the NFAS trunks.
2. To lock and remove an NFAS Group:
a. Lock all NFAS trunks, change their Protocol Type to NONE, and then unlock them.
b. Lock the Backup trunk if it exists. Change its Protocol Type to NONE, and then unlock
it.
c. Lock the Primary trunk, change its Protocol Type to NONE and then unlock it.
Note:
Note: You cannot reconfigure an NFAS group after locking it. You must first set the
Protocol Type trunks to NONE and then start configuring again.

24 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

Configuring SIP Parameters

This section describes how to configure the device with basic SIP control protocol parameters
using the EMS.
1. From the MG tree, select the device that requires configuration.
2. Double- click the desired blade
The system displays Media Gateway Board status screen.
3. Select the SIP from the Tab bar.
4. Click on the Protocol Definition.
The system displays SIP Protocol Definitions screen.

5. Select the Coders tab, and make the following changes:

a. Click the button to add a new Coder entry, and then click Yes to confirm.
b. Double-click each field to enter values.
c. Right-click the new entry, and then choose Unlock Rows.
6. Select the Proxy Server tab, and make the following changes:
a. Set Proxy Used to Yes.

Mediant 3000 Media Gateway Setup March 2011 25

Mediant 3000 Setup

b. (Optional) Enter the Proxy's name. The Proxy name replaces the Proxy IP address in
all SIP messages. This means that messages are still sent to the physical Proxy IP
address, but the SIP URI contains the Proxy name instead. When no Proxy is used,
the internal routing table is used to route the calls.
c. Click the button, and then click Yes to confirm.
d. Enter the IP address of the Proxy Server.
e. Right-click the new entry, and then choose Unlock Rows.
7. Select the Registration tab, and make the following changes:
a. Configure Is Register Needed field:
● No: The device does not register to a Proxy/Registrar server (default).
● Yes: The device registers to a Proxy/Registrar server at the start of power and
every user-defined interval.
b. Click Apply and close the active window.
8. From setup bar, select SIP.
9. Click End Points.
On the SIP EndPoint screen, make the following changes:
a. Click the button to add a new entry, and then click Yes to confirm.
The system displays Phones screen.
b. Double-click each field to enter values.
c. Right-click the new entry, and then select Unlock Rows.
d. Click Apply and close the active window.
10. If a Proxy Server is not implemented, map outgoing telephone calls to IP addresses.
11. On the Tab bar, click on SIP and then Routing.
The system displays SIP Routing frame.
12. Select the Tel to IP tab.
a. Click the button to add a new entry, and then click Yes to confirm.
The system displays Routing table.
b. Double-click each field to enter values.
c. Right-click the new entry and select Unlock Rows.
d. Click Apply and close the active window.

26 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

Call routing configuration

Similar to Avaya Communication Manager, Mediant 3000 Media Gateway must be configured
with SIP and DS3 trunks and with rules to route inbound (DS3 > SIP) and outbound (SIP > DS3)
calls, based on information in the incoming call request. You can load balance the incoming
traffic from Mediant 3000 Media Gateway across multiple TN799DP C-LAN circuit packs in the
Avaya G650 Media Gateway. All outbound calls should be routed from the TN799DP C-LAN
circuit packs to Mediant 3000 Media Gateway, which routes them to the DS3 interface on the
PSTN side. The routing rules are summarized below.

Call Type Routing Condition

(Mediant 3000 to/from
C-LANs)

Inbound Tel > IP > Target IP Last digit of calling

address number = 0-4
Inbound Tel > IP > Target IP Last digit of calling
address 2 number = 5-9
Inbound Tel > IP > All All
Outbound Target IP address > IP > All
Tel

The routing list also has the property that if a call cannot be successfully routed to the
destination specified by a matched rule, then the next rule that matches is used to attempt to
route the call. This can be used to implement a failover strategy if one of the TN799DP C-LAN
circuit packs is not responding or not available. For this feature to work most effectively, during
maintenance operations, the Ethernet interface should be disabled on a TN799DP C-LAN
circuit pack as well as busied it out.
For more information about determining the best routing and alternate routing configurations,
contact an Avaya software specialist.

Configuring inbound call routing on the TP-6310

The Trunk Processing Module (TP-6310) must be locked before starting these steps. See
Locking the device on page 18.

Note:
Note: The two rules set up in these steps implement a form of load sharing that is based
on the calling numbers of the inbound traffic.

Mediant 3000 Media Gateway Setup March 2011 27

Mediant 3000 Setup

1. Double-click the locked TP-6310 shown in black.

2. Select the SIP tab.
3. Select the Routing tab to display the SIP Tel to IP Routing List.

4. Click the + icon to add a routing rule.

Routing rules are applied to inbound calls (Tel to IP).

5. In the Name field, type an appropriate name.

6. In the Source Phone Prefix field, type a match specification, where x matches any digit
in the calling number and [x-y] specifies that the digit in that position should match any
digit in the range x to y.
7. In the Dest Address field, type the IP address of the TN799DP C-LAN circuit pack to
which the incoming PSTN call is sent.
For example, if the last digit of the calling number ends in 0, 1, 2, 3, or 4, then a SIP
INVITE is sent to C-LAN1. See the table in Call routing configuration on page 27.
8. Click Apply and then Close.

28 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

9. Repeat steps 8 and 9, clicking on the + icon to add each rule.

For example, if the last digit of the calling number ends in 5, 6, 7, 8, or 9, then a SIP
INVITE is sent to C-LAN2. See the table in Call routing configuration on page 27.
10. Select the Routing Setting tab.
11. In the Enable Alternative Routing field, select y.
12. Use default settings for the other fields.
13. Click Apply and then Close.
The SIP Tel to IP Routing List appears as:

Configuring outbound call routing on the TP-6310

Lock Trunk Processing Module (TP-6310) before starting these steps. See Locking the device on
page 18.

1. Double-click the locked TP-6310 shown in black.

2. Select the SIP tab.
3. Select the Routing tab

Mediant 3000 Media Gateway Setup March 2011 29

Mediant 3000 Setup

4. Select the IP to Tel tab to display the SIP IP to Tel Routing List.

5. Click the + icon to add a routing rule.

Routing rules are applied to outbound calls (IP to Tel).

6. In the Name field, type an appropriate name.

7. In the Dest Phone Prefix field, type a match specification.
8. In the Source Phone Prefix field, type a match specification.
9. In the Source Address field, type a match specification.
For example, if all calls are to be routed to Trunk group 1, type * in the fields, specifying a
match on any value.
10. In the Trunk Group ID field, type the destination PSTN trunk group number.
11. Click Apply and then Close.
12. Repeat steps 5 through 11, clicking the + icon to add each rule.
13. When done, click the up-arrow icon to return to the MG Status screen.

30 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

The SIP IP to Tel Routing List appears as:

Mediant 3000 Media Gateway Setup March 2011 31

Mediant 3000 Setup

Unlocking the TP6310 board

Unlock the TP6310 board before configuration, and enable it for service.

1. Click the up-arrow icon to display the MG Status screen.

2. In the right pane under the MGs List, select the entry corresponding to Mediant 3000
Media Gateway to be unlocked.
3. Select the MG Status tab to display a replica of the front panel.

Board slots are numbered from 1 to 10 from bottom to top, as displayed on the left side of
the front panel.The TP6310 boards are in slots 9 and 10.
4. Right-click on the active TP6310 card shown in black and select Maintenance > Unlock.
5. Click Yes in the confirmation window.
The TP6310 board resets and returns to service after several minutes. The Alarm Browser pane
at the bottom of the window indicates the status of the board.
Note:
Note: Verify that all the board elements (DS3, DS1, routing rules, trunk groups, etc.) are
unlocked.

32 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

Avaya Communication Manager configuration

The following sections describe how to configure call routing in Avaya Communication Manager
for Mediant 3000 Media Gateway. Other information about SIP administration can be found in
the online help that is part of the SIP Administration Web interface.
The first part covers configuring the SIP trunks that communicate with Mediant 3000 Media
Gateway. The second part covers call routing.

● How inbound calls from Mediant 3000 Media Gateway are directly mapped to 5-digit
extensions in Avaya Communication Manager
● How Automatic Route Selection (ARS) is configured for outbound calls through Mediant
3000 Media Gateway
Note:
Note: The following procedure is for Communication Manager that is using C-LAN
configuration.

Verifying system capacities

You must verify that an adequate number of SIP trunk members are administered for the
system.

1. Log into a SAT session as craft or dadmin.

2. Type display system-parameters customer-options and press Enter.
3. Go to the IP Port Capacities page.
4. In the Maximum Administered SIP Trunks field, verify that you have an adequate
number of trunks.
5. In the Maximum TN2602 Boards with 320 VoIP Channels field, verify that you have an
adequate number of channels.
6. In the ARS? field, verify that it is set to y.

Assigning IP codec sets

1. Type change ip-codec-set n and press Enter.
2. In the Audio Codec field, type in the codec set you want to use.
For example, type G.711MU for G.711 u-law.

Mediant 3000 Media Gateway Setup March 2011 33

Mediant 3000 Setup

Note:
Note: Ensure that the packetization time matches on the Communication Manager and
Mediant 3000 server.

Assigning IP network regions

1. Type change ip-network-region and press Enter.

2. In the Name field, type in a unique name.
3. In the Codec Set field, type in the codec set you want to use for this network region.
4. Set the Intra- and Inter-region IP-IP Direct Audio fields to yes.
Note:
Note: If Mediant 3000 is directly connected to the Communication Manager, do not type
in the Authoritative Domain.

Assigning a node name

In Communication Manager, you must first assign a node name and IP address to each active
TP-6310. This information is used to populate other screens.
1. Type change node-names ip and press Enter.
2. In a blank Name field, type a unique name for the TP-6310.
3. In the IP Address field, type the IP address of the TP-6310.
4. Repeat steps 2 and 3 for each additional TP-6310, if necessary.
5. Press Enter to save your changes.

Adding a signaling group

You must assign a node name and IP address to active TP-6310 before starting this procedure.
See Assigning a node name on page 34. You must also assign an IP network region. See
Assigning IP network regions on page 34.
You need to create a unique signaling group for each SIP trunk.

1. Type add signaling-group next and press Enter.

The system automatically assigns the next available number.

34 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

2. In the Group Type field, type or select sip.

3. In the Transport Method field type tls. Alternatively, you can type tcp but then you must
also set the corresponding setting in Mediant 3000 to TCP, and the port number to 5060.
4. In the Near-end Node Name field, type the name of the C-LAN circuit pack to which the
active TP-6310 is programmed to send calls in the Tel to IP routing rules.
5. In the Far-end Node Name field, type the name of the active TP-6310.
6. In both the Near-end Listen Port and Far-end Listen Port fields, type 5061.
7. In the Far-end Network Region field, type a network region number if your system is
divided into network regions.
This number is the network region to which the active TP-6310 is assigned.
8. In the DTMF over IP: field, type rtp-payload.
9. In the Direct IP-IP Audio Connections?: field, type y.
10. Accept the default values on the remaining fields.
11. Press Enter to save your changes.
If using more than one C-LAN for load balancing, repeat these steps for the each C-LAN.

Adding a trunk group

You must add the active TP-6310 to a signaling group before starting this procedure. See
Adding a signaling group on page 34.

! Important:
Important: The number of trunk members must be distributed across all the trunk groups
used for Mediant 3000 Media Gateway.

1. Type add trunk-group next and press Enter.

The system automatically assigns the next available trunk group number, which is
displayed in the Group Number field.
2. In the Group Type field, type or select sip.
3. In the Group Name field, type a name for this trunk group as it relates to the active
TP-6310.
4. In the COR: field, type 1.
5. In the TAC field, type a valid number that fits your dial plan.
For more information about dial plans in Communication Manager, see the Administrator
Guide for Avaya Communication Manager, 03-300509, at http:// www.avaya.com/support.

Mediant 3000 Media Gateway Setup March 2011 35

Mediant 3000 Setup

6. In the Direction field set the value to two-way.

7. In the Service Type field, type or select tie.
8. In the Signaling Group field, type the number of the signaling group to which the active
TP-6310 is assigned.
9. In the Number of Members field, type the number of members that you wish to use for
this trunk group.
Note:
Note: The maximum number of trunk group members in any one signaling group is 255.
The maximum number of total members is based upon your license agreement. If
you have more than 255 trunk group members in a signaling group, you must
create additional signaling groups.

10. In the Trunk Features section, set the Numbering Format field to public.
11. Accept the default values on the remaining fields.
12. Press Enter to save your changes.
If you have more than one signaling group, repeat these steps for each trunk group.

Defining public numbering format

Avaya Communication Manager must provide the proper calling number when outbound calls
are placed over the SIP trunks. For example, a full 10-digit number includes the CPN prefix plus
5-digit extension.

1. Type change public-unknown-numbering n and press Enter.

2. Fill in all the fields for the number of digits in the extension, the digit with which the
extension starts, and the number of total digits.

Mapping inbound calls (when required)

Customers can map the inbound calls directly to the correct x-digit extensions in
Communication Manager.

1. Type change inc-call-handling-trmt trunk-group n and press Enter.

Incoming calls arriving at each SIP trunk are routed to the extension specified by the last 5
digits of the called number. The first six digits are deleted if the calling number is of the
form 1AAANNNXXXX, and the first five are deleted for the form AAANNNXXXX.

36 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

Mapping outbound calls

Automatic Route Selection (ARS) is used to configure Communication Manager for outbound
calls.

! Important:
Important: Ensure that all trunk groups are added into any affected routes.

1. Type change dialplan analysis and press Enter to add the feature access code for
outside dialing.
2. Fill in all the fields. For example, type 9 if users must dial 9 to get an outside line, length 1,
and fac for Feature Access Code.
3. Type change feature-access-codes and press Enter.
4. In the Auto Route Selection (ARS) - Access Code 1 field specify the correct access
code for outside dialing. For example, type 9 if users must dial 9 to get an outside line.
5. Type change ars analysis n and press Enter to configure the route selection based
on the number dialed following the access code.
For example, type 720 if users must dial the area code 720 after dialing 9 for outbound
local calls.
6. Type change route-pattern n and press Enter to define the SIP trunk groups to be
selected for the corresponding route pattern.
7. Set Secure SIP field to N.
8. Type change locations and press Enter.
9. In the Proxy Sel. Rte. Pat. field, designate the SIP trunk routing patterns from step 6. This
provides support for features such as call transfer.
Refer to the Call Routing Guide available on the Avaya Support Web site (http://
support.avaya.com) for more information.

Mediant 3000 Media Gateway Setup March 2011 37

Mediant 3000 Setup

Session Manager configuration

Note:
Note: These instructions are written assuming the Avaya Aura® Session Manager and
Avaya Aura® System Manager are installed on your machine and are fully
functional.
The following sections describes how to configure call routing in Session Manager for Mediant
3000 Media Gateway.

System Manager configuration

To configure Session Manager, access the user Interface of System Manager using the
following link: http://<ip-address>/SMGR, where <ip-address> is the IP address of System
Manager.
1. Log in to Avaya System Manager with appropriate credentials.
2. Expand the Routing menu on the left pane of the home screen of System Manager.
You can configure System Manager using the following submenus.

Specifying SIP domains

To configure SIP domain appropriately.

38 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

1. Select Domains under the Routing menu.

The system displays the Domain Management screen.
2. Click New to add a new domain name.
3. Under Notes, add a brief description about the new domain.
4. Click Commit to save.

Adding locations
For bandwidth management, the Locations tab is used to specify the logical and physical
locations of SIP entities.

1. Select Locations under the Routing menu.

The system displays the Location details screen.
2. Click New to add a new location name.
3. In the General section, add the following details:
a. In the Names field, add a descriptive location name.
b. In the Notes field, add a brief description about the added location.
4. Click Commit to save.

Mediant 3000 Media Gateway Setup March 2011 39

Mediant 3000 Setup

Setting up the Adaptation module

The Adaptation module performs the digit conversion for incoming and outgoing calls.

1. Select Adaptations under the Routing menu.

The system displays the Adaptations details screen.
2. Click New to add a new Adaptation name.
3. In the General section, add the following details:
a. In the Adaptation Name, add a descriptive name.
b. In the Module Name field, select an appropriate module from the drop-down list.
c. In the Notes field, add a brief description about the added Adaptation module.
4. Click Commit to save.

40 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

Adding Mediant 3000 SIP element

1. Select the SIP Element under the Routing menu.

2. Click New to add a SIP element.
3. In the General section, add the following details:
a. In the Name field, add an identifier for the Mediant 3000 device.
b. In the FQDN or IP Address field, add the IP address for the device.
c. In the Type menu, select the appropriate menu option for the gateway.
d. In the Notes field, add a brief description about the added identifier.
e. In the Adaptation field, select the Adaptation added in Setting up the Adaptation
module on page 40.
f. In the Location field, select the Location added in Adding locations on page 39.
g. In the Time field, select the appropriate time zone.
4. Click Commit to save.

Mediant 3000 Media Gateway Setup March 2011 41

Mediant 3000 Setup

Setting up Time Ranges

1. Select the Time Ranges under the Routing menu.

2. Click New to set up a time range.
3. In the Name field, add a name to identify a new time range.
4. Select the required days of the week.
5. Enter a time value in the Start time and the End time fields.
6. In the Notes field, add a brief description about the entered time range.
7. Click Commit to save.

42 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

Defining Policies and Time of day for Mediant 3000

1. Select Policies under the Routing menu.

2. Click New.
3. In the General section, add the following details.
a. In the Name field, add an identifier to define the routing policy for the Mediant 3000
device.
b. In the Notes field, add a brief description about the identifier.
4. In the SIP Element as Destination section, click Select.
5. In the SIP Element List, select the entry of the Mediant 3000 device added in the section
Adding Mediant 3000 SIP element on page 41, and click Select.
The SIP Entities section displays the Routing Policy Details.
6. In the Time of Day section, click Add.
7. In the Time Ranges List, select the desired Time Range.
8. Click Select.
Note:
Note: The Routing Policy Details page displays the selected time range.
9. Click Commit to save.

Mediant 3000 Media Gateway Setup March 2011 43

Mediant 3000 Setup

Verifying network connectivity

1. To verify network connectivity on Mediant 3000 Media Gateway:
a. In the right pane under the MGs List, select the entry corresponding to the Mediant
3000 device that you configured.
b. Select the MG Status tab to display a replica of the front panel.
c. Double-click the active TP6310 card shown in black and select.
d. Verify that the icons for the DS3 entries are green.
e. Double-click the DS3 entry for the DS1 channel interface parameters that you
configured.
f. Verify that the icons for the DS1 entries are green.

2. To verify network connectivity on the TN799DP C-LAN circuit packs:

a. Log in to Communication Manager on the S8720 or S8730 Media Server and start a
SAT session.
b. Type ping IPAddress board location, where IPAddress is the Ethernet interface on
the Mediant 3000 device and location is the board location of the C-LAN circuit pack
within the G650 Media Gateway.
c. Type status signaling-group and press Enter.
d. Verify that the SIP trunks are running between Communication Manager and the
Mediant 3000 Media Gateway and that the transport protocols and ports match (TLS
and 5061).

Verifying call routing

Verifying call routing means making calls within a session Internet Protocol (SIP) environment
and between SIP and the Public Switched Telephone Network (PSTN).
In general, if a SIP device in the network does not receive an expected response to a SIP
message it has transmitted, the standard procedure is to retransmit that message to an
exponentially decreasing intervals (0.5 s, then 1 s, etc.) up to 6 more times. Look for this
behavior at various points in the call routing path if calls are not successful or if calls only remain
established for about 32 s. Most likely, the expected message was not routed properly because
of NAT, dial-peer, DNS, or firewall configuration errors.

44 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

1. Make calls from a telephone on the PSTN to a SIP telephone. If inbound calls fail, verify
that the proper Tel to IP routing rules have been defined to support routing SIP calls to the
appropriate C-LANS.
2. Make calls between SIP telephones registered within each proxy to verify successful call
completion.
If outbound calls fail, verify that the proper IP to Tel routing rules have been defined to
support routing SIP calls to the appropriate DS3/DS1.
3. Log in to a SAT session on the media server.
4. Type list trace station to verify that the call is being properly routed through the SIP trunk
to Mediant 3000 device.
5. Change the transport protocol to TCP on the SIP trunk and use a SIP-capable protocol
analyzer to monitor the signaling messages.
6. Type change signaling group and press Enter.
7. Change the following fields:
● Transport Method: tcp
● Far-end Listen Port: 5060

8. Log in to Mediant 3000 device.

9. Lock the TP-6310.
10. Double-click the locked TP-6310 shown in black.
11. Select the SIP tab.
12. Select the Protocol Settings tab.
13. Change the following fields:
● SIP Destination Port tcp.
● Transport Type 5060.
14. Click Apply and then Close.

Mediant 3000 Media Gateway Setup March 2011 45

Mediant 3000 Setup

Mediant 3000 call routing: setting up 'Tel to IP' for

redundancy and performance

Introduction
If proper and complete administration is not performed, the following issues can potentially
sabotage a Mediant 3000/CM integration:
● When routing inbound calls to CM (from the PSTN) is based on the ANI of the calling party
and NO ANI is received from the Service Provider. In this case, if Mediant 3000 is not
setup correctly, a one-way talk path may result.
● Failure to administer Mediant 3000 and CM so there are enough trunk members in CM
trunk groups as well as the ability to account for 'alternate routes' to CM in the event of
network issues or resource limitations.
This section takes you step-by-step through the administration process to avoid potential pitfalls
in these situations as well discuss the reasons for each step and the concepts involved.

C-LAN and signaling group discussion

The following guidelines are for assigning and configuring SIP trunks and C-LANs to support
Mediant 3000. It is assumed that Mediant 3000 is already configured with a number of DS3
TP6310 boards, each with several inbound trunks (DS0 channels within DS3 connections). The
sizing of the inbound trunks may be based on customer specifications, or may be determined
from the usual Erlang calculation analysis based on call traffic estimates and parameters such
as busy hour call rates and call durations.
1. TLS links: Each TP6310 board has its own IP address for media and signaling, therefore
each unique pairing of C-LAN <->TP6310 board requires a separate CM TLS link, of which
there are only 16 available on Communication Manager (several of which are usually left
unused to support failover of SES server pairs). C-LANs are a relatively inexpensive
components to add, but generally handle more limited traffic when compared to other
components such as SES, IPSI and Mediant 3000/TP6310. Therefore, it makes more
sense to dedicate each C-LAN to support one and only one signaling group. Each
signaling-group communicates with only one TP6310 board (though its likely that a single
TP6310 will communicate with more than one signaling group). It is assumed that each
DS3 board is supported by a unique set of one or more C-LAN's, which serve no other
DS3's or endpoints.

46 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

Note:
Note: In CM, it's possible to create two (or more) SIP signaling groups where the
'near-end' and 'far-end' nodes have the same exact values. Doing so does NOT
add to the count of utilized TLS links. Two identical SIP signaling groups will still
only count as one TLS link. This sort of programming can also be used to get
around the SIP trunk group limit of 255 members.
2. SIP trunks: For each set of C-LANs supporting a TP6310-DS3 connection, assign at least
as many CM SIP trunk members as DS0 channels they are supporting. Note that there is a
maximum of 255 members per SIP trunk group. Therefore the C-LANs supporting the max
~640 channels on a DS3 (total number of DS-0s vary by DS-1 signaling type) should have
combined at least that many CM SIP trunk members. This can be achieved by creating
three SIP signaling groups, each with 255 trunk members, using three C-LANs, etc.
3. C-LANs: There is no real upper limit to the number of signaling groups or trunk members
per C-LAN. The number of C-LANs to allocate for each DS3 board should be determined
by the call traffic volume (BHCC) and the desired redundancy.
4. Decide, or estimate, how many SIP calls per hour a C-LAN can handle. This number is not
fixed, but depends on the complexity of the call. A C-LAN may be able to handle up to 9k
calls/hr for a standard, no-frills, inbound-to-CM-endpoint call, but only 50% or less of the
more complex call center calls with multiple connections to announcements, IVR,
transfers, each of which is a separate SIP re-INVITE transaction.
- For a call center, consider starting with no more than 5k calls/hr for each C-LAN.
5. Dividing this calls/hr load for a C-LAN into the total call load for a DS3 connection gives us
the number of C-LANs required to support that connection.
- Mediant 3000 can route calls based on dialed digits, which means separate C-LANs
supporting the same DS3 board may see different (uneven) traffic levels based on the
application or service provided on the extensions handled. In this case, C-LAN
allocation may be done according to each type of application traffic on each board.
6. Combining the previous two rules gives the number of CM SIP trunk members on each
C-LAN.
7. If the total SIP trunk use is not close to the CM limit of 12,000 total SIP trunks, and there's
more than one C-LAN supporting a DS3 board, then allocate a number of trunks about
10% greater than the actual number of DS0s. The reason for this is that when the
channels on the DS3 are almost all occupied during very busy periods of time, there is a
greater chance that one or more of the C-LANs supporting that connection will run out of
SIP trunk members.
8. Using the previous example, if you are using three C-LANs to support the full ~640 DS-0
channels on a DS3, you can allocate 255 SIP trunk members on each C-LAN, which is the
maximum amount for one signaling group. Doing this across three trunk-groups gets
765 members (255+255+255=765).

Mediant 3000 Media Gateway Setup March 2011 47

Mediant 3000 Setup

9. Lastly, you want to be sure you have properly set up Alternate Routing in Mediant 3000
(which is discussed below) for the case where you do use up all trunk members in a CM
trunk group. While Mediant 3000 does not have the ability to know how many trunk
members are available in a CM trunk group, it can re-route a call to another trunk group
when it receives any one of four (programmable) SIP reason codes. In this case, CM
returns a 503 reason code to Mediant 3000 when all the trunk members are active or
otherwise unavailable.

Tel to IP: alternate routing

Mediant 3000 has the ability to redirect inbound calls (from PSTN to CM) under the following
scenarios:
● Loss of network connectivity to the C-LAN (C-LAN is no longer pingable by Mediant 3000)
● QoS thresholds exceeded for jitter and/or packet loss
● Definable SIP reason codes returned to Mediant 3000 by CM

Note:
Note: You can add any other SIP reason codes that are applicable to your environment.
None of the scenarios are enabled by default, though, for a thorough Mediant 3000
implementation, all three should be enabled.

48 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

Tel to IP: routing based on ANI

Normally, when an incoming call arrives at Mediant 3000 from the PSTN with no ANI, Mediant
3000 will reference the starting phone number value on the Trunk Group form in order to decide
how to route the call to Communication Manager. For each sequential call on the trunk group,
Mediant 3000 attempts to increment this value by one.
The default value for the starting phone number field is '$$'. A problem can occur if these values
are left unchanged since $$ is non-numeric. Initially, all incoming calls will complete without
incident, though, over time, as Mediant 3000 parses SIP messages where the FROM header
contains ever-changing character strings, performance on the T6310 degrades to the point
where calls result in 'one-way' or 'no-way' talkpath. For example:
From: <sip:[email protected]:5061>;tag=1c26166108
Therefore, it is imperative when setting up Trunk Groups on Mediant 3000, that this default
value is changed to a valid numeric value.

Example scenario
Below is the theoretical configuration that will be used in the example:

CM Trunk Signaling C-LAN IP

Group Group Address

1 1 10.10.10.1
2 2 10.10.10.2
3 3 10.10.10.3

Mediant 3000 Media Gateway Setup March 2011 49

Mediant 3000 Setup

Overview of the necessary steps

The following are the necessary steps for performing Mediant 3000 administration via EMS.
These steps should be repeated for each TP6310.
1. Enter appropriate Tel-To-IP routing rules to send calls to CM Signaling/Trunk Groups.
2. Select the Routing Setting tab and set the Enable Alternate Routing field to 'yes'.
3. Set the Alternative Routing Mode to All or Conn.
4. Set appropriate values for the QoS fields (Max Allowed Delay and Packet Lost) if you set
the Alternative Routing Mode to All in step 3.
5. Select the Alternate Tel to IP tab and add up to four table entries with appropriate SIP
Reason codes (add '503' as one of the reason codes).
6. Create at least one Mediant 3000 trunk group.
7. Select an appropriate 'Starting Phone Number' value for the trunk group (do NOT leave the
default value of '$$' in this field).

Performing Mediant 3000 administration via EMS

1. Enter appropriate Tel-To-IP routing rules to send calls to CM Signaling/Trunk Groups:
a. Double-click the TP6310 board.
b. Select the SIP tab.
c. Select the Routing tab.
d. Select the Tel To IP tab.
Note:
Note: Perform these steps for each active TP6310 board.

50 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

2. Based on the information in the above figure, add the Tel to IP entries as follows:
Note:
Note: Double-clicking a row enables you to edit an existing entry.
Selecting + from the upper right corner of the EMS client enables you
to add new entries.

Note:
Note: For each primary rule, there is a nearly identical rule, the difference being the
destination IP address. Since each IP address represents a different CM
Signaling Group, ultimately the call is being sent to a different CM trunk group.
When Mediant 3000 sees two identical rules it knows the first one in the list is the
primary route and assigns the second rule to be the alternate route, provided that
alternate routing is enabled.
Note:
Note: The last rule, where Dst Phone Prefix and Src Phone Prefix are set to *, accounts
for the case where a 10-digit Src Phone Prefix (ANI) is not received.

! Important:
Important: Verify that each of these rules is UNLOCKED.
3. Select the Routing Setting tab and set the Enable Alternate Routing field to yes.
4. Set the Alternative Routing Mode to Both or Conn.

Mediant 3000 Media Gateway Setup March 2011 51

Mediant 3000 Setup

5. Set appropriate values for the QoS fields (Max Allowed Delay and Packet Lost) if you set
the Alternative Routing Mode to Both in step 4.
The figure below contains values for the settings applied in the above steps.

6. Select the Alternate Tel to IP tab and add up to four table entries with appropriate SIP
Reason codes (add '503' as one of the reason codes).
Currently, in a single CM SIP trunk group there is a limit of 255 trunk members. Notice that
from step 1 an attempt is made to load balance calls across three SIP signaling groups.
However, there is nothing to prevent Mediant 3000 from receiving more than 255
simultaneous calls where the last digit in the callers ANI ends with 0-3. In this case, all the
trunk group members will be exhausted. So, for the 256th call, CM returns a SIP 503
reason code to Mediant 3000, which indicates that no additional trunk members are
available. Rules in the Alternate Tel to IP tab enable you to instruct Mediant 3000 what to
do when receiving specific reason codes (up to four entries). Since you know that CM is
going to send a SIP 503 reason code, you have instructed Mediant 3000 to invoke the
alternate route before giving up on the call.

52 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

! Important:
Important: Verify that each of these rules is UNLOCKED.
7. Create at least one Mediant 3000 trunk group as follows:
a. In the EMS, double-click the TP6310.
b. Select the SIP tab.
c. Select the Trunk Groups tab.

Mediant 3000 Media Gateway Setup March 2011 53

Mediant 3000 Setup

4. Select the Trunk Group.

The Trunk Group form appears.

Note:
Note: The value in the Starting Phone Number field is $$.
5. Change the value in the Starting Phone Number field to a numeric value. This has to
be done in case any or all incoming calls from the PSTN to Mediant 3000 do not
contain ANI. Align the value with the routing rules setup in the Tel to IP routing tab.

54 Mediant 3000 Media Gateway Setup March 2011

 Mediant 3000 Setup

Note:
Note: In the U.S., this will generally be a 10-digit number.

In this example, you have one DS-3. You have created Trunk Group 1 on Mediant
3000, which consists of all 28 DS-1s in the DS-3. For each DS-1 you have also
indicated that all 24 channels are available (you can include a D-channel used for
signaling in the range as Mediant 3000 will not try to utilize it for voice).
When ANI is blocked or otherwise not present, Mediant 3000 will use the number
100000001 as the starting point for routing calls to CM. As calls come across
B-channels, Mediant 3000 will increment this starting number by 1 so that the call can
be properly load balanced across C-LANs using the rules defined in the Tel to IP tab.
This will also enable Mediant 3000 to construct SIP messages where FROM message
containing only a numeric value.
For example: From: <sip:[email protected]:5061>;tag=1c26112113

! Important:
Important: If you have more than one trunk group for a DS-3, set the Starting Phone Number
in each Trunk Group to values that will not overlap. For example, for Trunk Group
1 you could set the Starting Phone Number to 1000000001 and for Trunk Group 2
you would then set the Starting Phone Number to 2000000001.

! Important:
Important: Verify that each of these rules is UNLOCKED.

Mediant 3000 Media Gateway Setup March 2011 55

Mediant 3000 Setup

56 Mediant 3000 Media Gateway Setup March 2011

Appendix A: Initial configuration

Factory production M3K models will be loaded with the following configuration file. This pre-
loaded configuration is helpful to pre-populate administrative settings for the following:
● Voice codec will be set to Mu-law operation
● Ds1 trunks
● DS3 interfaces
● ISDN NFAS groups
● T.38 fax settings
The following textual description describes the exact configuration setting the various features.
Note:
Note: The pre-administrative settings save up to 20 minutes in setting up a new M3K
gateway.
--------------------------------------------------------------------------------------
;**************
;** Ini File **
;**************

;Board: Mediant 3000

;M3K Board Type: TrunkPack 6310
; Avaya M3k R1_0 version 5.8 ini file requested by Wayne Zakowski 31-MAR-2011,
avayaM3kR1_0v1.ini
; avayaM3kR1_0v1_1.ini contains AudioCodes R&D recommended updates.
;**************

M3KGlobalIpAddr = 0.0.0.0

CallProgressTonesFilename = 'M2K_usa_tones.dat'
V22ModemTransportType = 0
V23ModemTransportType = 0
V32ModemTransportType = 0
V34ModemTransportType = 0
FaxTransportMode = 1
isFaxUsed = 1
RFC2833PayloadType = 96
ENABLEEARLYMEDIA = 1

[ CodersGroup0 ]
FORMAT CodersGroup0_Index = CodersGroup0_Name, CodersGroup0_pTime, CodersGroup0_rate,
CodersGroup0_PayloadType, CodersGroup0_Sce;
CodersGroup0 0 = g711Ulaw64k, 20, 64, 0, 0;

Mediant 3000 Media Gateway Setup March 2011 57

Appendix A: Initial configuration

CodersGroup0 1 = g729, 20, 8, 18, 0;

[ \CodersGroup0 ]

PCMLawSelect = 3
;~ PCMLawSelect: Selects the type of PCM companding law in input/output TDM bus (TDM bus
is defined using the TDMBusType parameter). 1 = A-law, 3 = Mu-Law.

TDMBusClockSource = 4
;~ TDMBusClockSource: Selects the clock source on which the board synchronizes. 1 =
Local oscillator, 3 = MVIP, 4 = PSTN Network, 8 = H.110A, 9 = H.110B, 10 = NetRef1, 11
= NetRef2, 12 = SC2M, 13 = SC4M, 14 = SC8M, 15 = BITS, 16 = Network-B, 17 = ATM-OC3, 18
= ATM-OC3-B, 19 = ATM-OC12, 20 = Network-DS3-1, 21 = Network-DS3-2, 22 = Network-DS3-3,
Default = 1, TP-1610 = 3.

[PSTN Params]

ProtocolType = 11
;~ ProtocolType: Used to set the PSTN protocol to be used for this trunk. Relevant only
when TDMBusType=acFRAMERS (2). Either: NONE = 0, E1_EURO_ISDN = 1, T1_CAS = 2,
T1_RAW_CAS = 3, T1_TRANSPARENT = 4, E1_TRANSPARENT_31 = 5, E1_TRANSPARENT_30 = 6,
E1_MFCR2 = 7, E1_CAS = 8, E1_RAW_CAS = 9, T1_NI2_ISDN = 10, T1_4ESS_ISDN = 11,
T1_5ESS_9_ISDN = 12, T1_5ESS_10_ISDN = 13, T1_DMS100_ISDN = 14, J1_TRANSPARENT = 15,
T1_NTT_ISDN = 16, E1_AUSTEL_ISDN = 17, E1_HKT_ISDN = 18, E1_KOR_ISDN = 19, T1_HKT_ISDN
= 20, E1_QSIG = 21, E1_TNZ_ISDN = 22, T1_QSIG = 23, V5_2_AN = 26, T1_IUA = 28, E1_IUA =
29, E1_FRENCH_VN6_ISDN = 30, E1_FRENCH_VN3_ISDN = 31, T1_EURO_ISDN = 34,
T1_DMS100_MERIDIAN_ISDN = 35, T1_NI1_ISDN = 36, E1_DUA = 37, E1_Q931_PACKETS = 38,
T1_Q931_PACKETS = 39, E1_NI2_ISDN = 40.

FramingMethod = D
;~ FramingMethod: Selects the physical framing method used for this trunk. 0 = default
according to protocol type E1 or T1, [E1 default = E1 CRC4 MultiFrame Format extended
G.706B (as c)], [T1 default = T1 Extended SuperFrame with CRC6 (as D)], 1 = T1
SuperFrame Format (as B). a = E1 DoubleFrame Format, b = E1 CRC4 MultiFrame Format, c =
E1 CRC4 MultiFrame Format extended G.706B, A = T1 4-Frame multiframe. B = T1 12-Frame
multiframe (D4). C = T1 Extended SuperFrame without CRC6, D = T1 Extended SuperFrame
with CRC6, E = T1 72-Frame multiframe (SLC96), F = J1 Extended SuperFrame with CRC6
(Japan).

DCHConfig_0 = 0
;~ DCHConfig: Defines D-channel configuration. This setting is only applicable to ISDN
PRI protocols that support NFAS and/or D-channel backup procedures. 0 = D-channel is
Primary, 1 = Backup, 2 = NFAS.

DCHConfig_1 = 1
DCHConfig_2 = 2
DCHConfig_3 = 2
DCHConfig_4 = 2
DCHConfig_5 = 2
DCHConfig_6 = 2
DCHConfig_7 = 2
DCHConfig_8 = 2
DCHConfig_9 = 2

58 Mediant 3000 Media Gateway Setup March 2011

 DCHConfig_10 = 0
;~ DCHConfig: Defines D-channel configuration. This setting is only applicable to ISDN
PRI protocols that support NFAS and/or D-channel backup procedures. 0 = D-channel is
Primary, 1 = Backup, 2 = NFAS.

DCHConfig_11 = 1
DCHConfig_12 = 2
DCHConfig_13 = 2
DCHConfig_14 = 2
DCHConfig_15 = 2
DCHConfig_16 = 2
DCHConfig_17 = 2
DCHConfig_18 = 2
DCHConfig_19 = 2

DCHConfig_20 = 0
;~ DCHConfig: Defines D-channel configuration. This setting is only applicable to ISDN
PRI protocols that support NFAS and/or D-channel backup procedures. 0 = D-channel is
Primary, 1 = Backup, 2 = NFAS.

DCHConfig_21 = 1
DCHConfig_22 = 2
DCHConfig_23 = 2
DCHConfig_24 = 2
DCHConfig_25 = 2
DCHConfig_26 = 2
DCHConfig_27 = 2

ISDNIBehavior = 2560
;~ ISDNIBehavior: Bit-field used to determine several behavior options, which influence
how the Q.931 protocol behaves. Refer to the VoPLib documentation (ISDN Flexible
Behavior).

ISDNNFASInterfaceID_0 = 0
;~ ISDNNFASInterfaceID: Defines the Interface ID. Works with NS_EXPLICIT_INTERFACE_ID.
Refer to the VoPLib documentation(ISDN Flexible Behavior). Default = (unsigned char)-1.
Range = 0 to 255.

ISDNNFASInterfaceID_1 = 1
ISDNNFASInterfaceID_2 = 2
ISDNNFASInterfaceID_3 = 3
ISDNNFASInterfaceID_4 = 4
ISDNNFASInterfaceID_5 = 5
ISDNNFASInterfaceID_6 = 6
ISDNNFASInterfaceID_7 = 7
ISDNNFASInterfaceID_8 = 8
ISDNNFASInterfaceID_9 = 9

ISDNNFASInterfaceID_10 = 0
;~ ISDNNFASInterfaceID: Defines the Interface ID. Works with NS_EXPLICIT_INTERFACE_ID.
Refer to the VoPLib documentation(ISDN Flexible Behavior). Default = (unsigned char)-1.
Range = 0 to 255.

ISDNNFASInterfaceID_11 = 1

Mediant 3000 Media Gateway Setup March 2011 59

Appendix A: Initial configuration

ISDNNFASInterfaceID_12 = 2
ISDNNFASInterfaceID_13 = 3
ISDNNFASInterfaceID_14 = 4
ISDNNFASInterfaceID_15 = 5
ISDNNFASInterfaceID_16 = 6
ISDNNFASInterfaceID_17 = 7
ISDNNFASInterfaceID_18 = 8
ISDNNFASInterfaceID_19 = 9

ISDNNFASInterfaceID_20 = 0
;~ ISDNNFASInterfaceID: Defines the Interface ID. Works with NS_EXPLICIT_INTERFACE_ID.
Refer to the VoPLib documentation(ISDN Flexible Behavior). Default = (unsigned char)-1.
Range = 0 to 255.

ISDNNFASInterfaceID_21 = 1
ISDNNFASInterfaceID_22 = 2
ISDNNFASInterfaceID_23 = 3
ISDNNFASInterfaceID_24 = 4
ISDNNFASInterfaceID_25 = 5
ISDNNFASInterfaceID_26 = 6
ISDNNFASInterfaceID_27 = 7

NFASGroupNumber_0 = 1
;~ NFASGroupNumber: Relevant only to T1 ISDN NFAS trunks, this parameter indicates the
group number of the NFAS group. Valid NFAS group numbers are only 1 to 4. 0 indicates
that this trunk is not NFAS (in this case the parameters ISDN NFAS Interface ID and Dch
Config are ignored). Range = 0 to 9.

NFASGroupNumber_1 = 1
NFASGroupNumber_2 = 1
NFASGroupNumber_3 = 1
NFASGroupNumber_4 = 1
NFASGroupNumber_5 = 1
NFASGroupNumber_6 = 1
NFASGroupNumber_7 = 1
NFASGroupNumber_8 = 1
NFASGroupNumber_9 = 1

NFASGroupNumber_10 = 2
;~ NFASGroupNumber: Relevant only to T1 ISDN NFAS trunks, this parameter indicates the
group number of the NFAS group. Valid NFAS group numbers are only 1 to 4. 0 indicates
that this trunk is not NFAS (in this case the parameters ISDN NFAS Interface ID and Dch
Config are ignored). Range = 0 to 9.

NFASGroupNumber_11 = 2
NFASGroupNumber_12 = 2
NFASGroupNumber_13 = 2
NFASGroupNumber_14 = 2
NFASGroupNumber_15 = 2
NFASGroupNumber_16 = 2
NFASGroupNumber_17 = 2
NFASGroupNumber_18 = 2
NFASGroupNumber_19 = 2

NFASGroupNumber_20 = 3

60 Mediant 3000 Media Gateway Setup March 2011

 ;~ NFASGroupNumber: Relevant only to T1 ISDN NFAS trunks, this parameter indicates the
group number of the NFAS group. Valid NFAS group numbers are only 1 to 4. 0 indicates
that this trunk is not NFAS (in this case the parameters ISDN NFAS Interface ID and Dch
Config are ignored). Range = 0 to 9.

NFASGroupNumber_21 = 3
NFASGroupNumber_22 = 3
NFASGroupNumber_23 = 3
NFASGroupNumber_24 = 3
NFASGroupNumber_25 = 3
NFASGroupNumber_26 = 3
NFASGroupNumber_27 = 3

CASProtocolEnable = 1
;~ CASProtocolEnable: This parameter enables or disables the possibility CAS protocol
configuration. At TP6310 When this parameter is enable the conference will disabled in
case it's relevant. 0 = Disable, 1 = Enable.

PSTNTransmissionType = 2
;~ PSTNTransmissionType: Sets the PSTN Transmission type for the board. Relevant only
when TDMBusType=acFRAMERS (2). Values are: 0 = NONE, PSTN Transmission type is not
defined, 1 = Optical SONET or SDH Transmission type, 2 = Copper DS3 (T3) Transmission
type, 3 = Copper E1 or DS1(T1) Transmission type, Default is NONE for TP6310 and Copper
E1 or DS1 for rest of boards.

[Voice Engine Params]

DTMFTransportType = 2
;~ DTMFTransportType: Defines the type of DTMF transport. 0 = Erase DTMFs from voice
transport not relayed to remote, 2 = DTMFs not erased are not relayed to remote, 3 =
DTMFs are muted from the voice stream and relayed according to RFC 2833, 7 = DTMFs are
sent according to RFC 2833 and muted when received.

[SIP Params]

ADDIEINSETUP = 200200e3
;~ ADDIEINSETUP: Additional information element to send in ISDN Setup message.

SENDIEONTG = '1'
;~ SENDIEONTG: Configure trunk groups on which to send additional IE.

USERTOUSERHEADERFORMAT = 2

;
; *** TABLE DS3CONFIG ***
;
;

[ DS3CONFIG ]
FORMAT DS3CONFIG_Index = DS3CONFIG_FramingMethod, DS3CONFIG_ClockSource,
DS3CONFIG_LineBuildOut, DS3CONFIG_CircuitIdentifier, DS3CONFIG_TrapEnable,
DS3CONFIG_PmOnOff, DS3CONFIG_TappingEnable, DS3CONFIG_AdminState;
DS3CONFIG 0 = 0, 0, 4, , 1, 1, 0, 1;
DS3CONFIG 1 = 0, 0, 4, , 1, 1, 0, 1;
DS3CONFIG 2 = 0, 0, 4, , 1, 1, 0, 1;

Mediant 3000 Media Gateway Setup March 2011 61

Appendix A: Initial configuration

[ \DS3CONFIG ]

------------------------------------------------------------------------------------

62 Mediant 3000 Media Gateway Setup March 2011