AudioCodes Mediant 3000, TP-8410, TP-6310 User Manual
Mediant™ 3000
VoIP Digital Media Gateway
MGCP & MEGACO Protocols
User's Manual
Mediant 3000 with TP-6310 & TP-8410
Version 6.6
December 2015
Document # LTRT-95211
User's Manual Contents
Table of Contents
1 Introduction ......................................................................................................... 9
1.1 General Features ................................................................................................. 11
1.2 High Availability .................................................................................................... 13
1.2.1 Mediant 3000 HA System with TP-6310 ..................................................................13
1.2.2 Mediant 3000 HA System with TP-8410 ..................................................................14
1.2.3 Private IP Address and System (Global) IP Address(es) ........................................15
1.2.3.1 Private (Local) IP Address........................................................................15
1.2.3.2 System (Global) IP Address .....................................................................15
1.3 Functional Block Diagram - TP-6310 .................................................................... 16
1.4 Functional Block Diagram - TP-8410 .................................................................... 17
2 Software Package.............................................................................................. 19
2.1 Installing the Software Package ........................................................................... 19
2.1.1 Installing/Unzipping When Using a Windows™ Operating System ........................19
2.2 Software Directory Contents & Structure .............................................................. 20
3 Getting Started .................................................................................................. 21
3.1 Assigning the Device IP Address .......................................................................... 21
3.1.1 Assigning an IP Address Using HTTP .....................................................................21
3.1.2 Assigning an IP Addr ess Using Boot P ....................................................................22
3.2 Assigning the IP Addresses for High Availability Mode ......................................... 23
4 System Initialization Process ........................................................................... 25
4.1 Boot Firmware & Operational Firmware ................................................................ 25
4.2 Startup Process .................................................................................................... 26
4.3 Configuration Parameters and Files ..................................................................... 28
4.3.1 Initialization (ini) File ................................................................................................28
4.3.1.1 Parameter Value Structure .......................................................................29
4.3.1.2 Tables of Parameter Value Structure .......................................................31
4.3.1.3 Binary Configuration File Download .........................................................33
4.3.2 Auxiliary Files ...........................................................................................................33
4.3.2.1 Downloading Auxiliary Files via TFTP During the Blade Startup .............34
4.3.3 Automatic Update Facility ........................................................................................34
4.4 Backup Copies of ini and Auxiliary Files ............................................................... 37
4.5 Upgrading Device Software .................................................................................. 38
4.6 Software Upgrade Key ......................................................................................... 38
4.7 High Availability .................................................................................................... 39
4.7.1 Initializing the Mediant 3000 System .......................................................................39
4.7.2 Device Initialization Process ....................................................................................39
4.7.3 Special System Specific Behavior ...........................................................................39
4.7.3.1 Rebooting the Blade .................................................................................39
4.7.3.2 High Availability and Syslog .....................................................................40
4.7.4 Actions upon Detecting Blade Failure .....................................................................40
4.7.4.1 Failure in the Active Blade........................................................................40
4.7.4.2 Failure in the Redundant Blade ................................................................40
4.7.5 Hitless Software Upgrade ........................................................................................40
5 Configuration Using the Web Interface ........................................................... 43
5.1 Limiting the Web Interface to Read-Only Mode .................................................... 43
5.2 Disabling the Web Interface .................................................................................. 44
Version 6.6 3 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
5.2.1 Encr ypted HTTP Transport (HTTPS - SSL) ............................................................44
5.2.2 Limiting Web Access to a Predefined List of Client IP Addresses ..........................44
5.2.3 Managing Web Server Access Using a RADIUS Server .........................................44
5.3 Initial Device Configuration using the Web Interface ............................................. 44
5.4 Accessing the Web Interface ................................................................................ 45
5.5 Using Internet Explorer to Access the Web Interface ............................................ 46
5.6 Getting Acquainted with the Web Interface ........................................................... 47
5.6.1 Toolbar .....................................................................................................................48
5.6.2 Navigation Tree .......................................................................................................49
5.6.2.1 Displaying Navigation Tree in Basic and Full View ..................................49
5.6.2.2 Showing / Hiding the Navigation Pane .....................................................50
5.6.3 Working with Configuration Pages ..........................................................................51
5.6.3.1 Accessing Pages ......................................................................................51
5.6.3.2 Viewing Parameters .................................................................................52
5.6.3.3 Displaying Basic and Advanced Parameters ...........................................52
5.6.3.4 Showing / Hiding Parameter Groups ........................................................53
5.6.3.5 Modifying Parameter Values ....................................................................54
5.6.4 Saving Configuration Changes ................................................................................55
5.6.5 Searching for Configuration Parameters .................................................................55
5.6.6 Working with Scenarios ...........................................................................................56
5.6.6.1 Creating a Scenario ..................................................................................57
5.6.6.2 Editing a Scenario ....................................................................................60
5.6.6.3 Saving a Scenario to a PC .......................................................................61
5.6.6.4 Loading a Scenario to the Device ............................................................62
5.6.6.5 Exiting Scenario Mode .............................................................................62
5.6.6.6 Deleting a Scenario ..................................................................................62
5.6.7 Creating a Login Welcome Message .......................................................................63
5.6.8 Getting Help .............................................................................................................64
5.6.9 Logging Off the Web Interface .................................................................................65
5.7 Using the Home Page .......................................................................................... 66
5.7.1 TP-6310 ...................................................................................................................66
5.7.2 TP-8410 ...................................................................................................................69
5.7.3 Viewing the Active Alarms Table .............................................................................70
5.7.4 Viewing Ethernet Port Information ...........................................................................71
5.7.5 High Availability Configuration .................................................................................72
5.7.5.1 Manual Switch Over / Redundant Board Reset .......................................73
5.8 Configuration ........................................................................................................ 74
5.8.1 System .....................................................................................................................74
5.8.1.1 Application Settings ..................................................................................74
5.8.1.2 Syslog Settings .........................................................................................76
5.8.1.3 Regional Settings .....................................................................................76
5.8.1.4 Certificates ...............................................................................................77
5.8.1.5 Management ............................................................................................78
5.8.2 VoIP .........................................................................................................................91
5.8.2.1 Network ....................................................................................................91
5.8.2.2 TDM & Timing ........................................................................................102
5.8.2.3 Security Settings ....................................................................................108
5.8.2.4 PSTN ......................................................................................................113
5.8.2.5 Media ......................................................................................................122
5.8.2.6 Call Control .............................................................................................136
5.8.2.7 V5.2 Configuration (For TP-8410 Only) .................................................141
5.9 Maintenance ....................................................................................................... 142
5.9.1 Maintenance ..........................................................................................................142
5.9.1.1 Maintenance Actions ..............................................................................142
5.9.1.2 High Availability Maintenance ................................................................145
5.9.2 Software Update ....................................................................................................146
5.9.2.1 Load Auxiliary Files ................................................................................147
User's Manual 4 Document #: LTRT-95211
User's Manual Contents
5.9.2.2 Software Upgrade Key ...........................................................................148
5.9.2.3 Software Upgrade Wizard ......................................................................151
5.9.2.4 Configuration File ...................................................................................157
5.10 Status and Diagnostic Menu ............................................................................... 161
5.10.1 System Status ........................................................................................................161
5.10.1.1 Message Log ..........................................................................................161
5.10.1.2 Device Information .................................................................................162
5.10.1.3 Ethernet Port Information .......................................................................163
5.10.1.4 Carrier-Grade Alarms .............................................................................163
5.10.2 Performance Monitoring ........................................................................................165
5.10.2.1 Viewing Trunk Utilization ........................................................................165
5.10.2.2 Viewing MOS per Media Realm .............................................................166
5.10.3 VoIP Status ............................................................................................................168
5.10.3.1 Viewing Trunk and Channel Status ........................................................168
5.10.3.2 Viewing NFAS Groups and D-Channel Status .......................................169
5.10.3.3 Active IP Interfaces ................................................................................170
5.10.3.4 Performance Statistics ...........................................................................171
5.10.3.5 Timing Module Information .....................................................................171
5.10.4 Components Status ...............................................................................................172
5.11 Device High Availability Mode ............................................................................ 173
6 Troubleshooting .............................................................................................. 175
6.1 TP-6310 Self-Test .............................................................................................. 175
6.2 TP-8410 Self-Test .............................................................................................. 176
7 Technical Specifications ................................................................................ 177
7.1 Mediant 3000 with TP-6310/TP-8410 Technical Specification ............................ 177
8 List of Abbreviations ....................................................................................... 183
9 Index ................................................................................................................. 187
Version 6.6 5 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
This page is intentionally left blank.
User's Manual 6 Document #: LTRT-95211
User's Manual Notices
as software files can be viewed by registered customers at
Notice
This document describes the Au dioCod es Med iant 30 00 MGCP & MEG ACO m edia gate way,
housed with TP-8410 SIP blade(s) or TP-6310 blade(s).
Information contained in t his document is believed to be ac curate and reliable at the tim e of
printing. However, du e to ongoing product im provements and revis ions, AudioCodes canno t
guarantee accuracy of printed material after the Date Published nor can it accept
responsibility for error s or omissions. U pdates to this d ocum ent and other docum ents as well
http://www.audiocodes.com/downloads.
© 2015 AudioCodes Inc. All rights reserved
This document is subject to change without notice.
Date Published: December 13, 2015
Trademarks
AudioCodes, AC, HD VoIP, HD VoIP Soun ds Better , I Pmedia, Mediant, MediaPack , What’s
Inside Matters, OSN, SmartTAP, VMAS, VoIPerfect, VoIPerfectHD, Your Gateway To
VoIP, 3GX, VocaNOM and CloudBond 365 are trademarks or registered trademarks of
AudioCodes Limited All other products or trademarks are property of their respective
owners. Product specifications are subject to change without notic e.
WEEE EU Directive
Pursuant to the W EEE EU Directive, electronic and el ectrical waste must not be disposed
of with unsorted waste. Please contact your local recycling authority for disposal of this
product.
Customer Support
Customer technical s upport and s ervices are provided by Au dioCodes or b y an authori zed
AudioCodes Service Partner. For more information on how to buy technical support for
AudioCodes products and for contact information, please visit our Web site at
www.audiocodes.com/support.
Related Documentation
The documentation package contains the following publications, available on the
AudioCodes Web site:
MGCP MEGACO Product Reference Manual - provides an extremely comprehensive
description of MGCP and MEGACO Network Control Protocols and their compliance.
User’s Manual contains the product overview; software package, startup and
initialization; Web GUI-based management; Diagnostics and Product Specification.
MEGACO Release Notes - describes for each new version the various new features
and functionality, issues from the previous version that have been solved, and known
constraints of this new software version.
Version 6.6 7 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
Documentation Feedback
AudioCodes continually strives to produce high quality documentation. If you have any
comments (suggestions or errors) regarding this document, please fill out the mentation
Feedback form on our Web site at http://www.audiocodes.com/downloads
.
User's Manual 8 Document #: LTRT-95211
User's Manual 1. Introduction
1 Introduction
The Mediant 3000 is a VoIP gateway, offering integrated voice gateway functionality
capable of delivering 2016 simultaneous calls, the Mediant 3000 supports all necessary
functions for voice and fax streaming over IP networks.
Supporting up to 2016 voice channels with up to 63 E1 / 84 T1 trunks and with variou s
PSTN interfaces, the Mediant 3000 addresses mid-density applications deployed in IP
networks. The Mediant 3000 supports a wide variety of VoIP and cellular vocoders,
standards-compliant signaling and call control.
There are two types of VoP communication blades supported by the Mediant 3000:
Based on TP-6310 blades - The Mediant 3000 with TP-6310 blades incorporates 1+1
Protected OC-3/STM-1 PSTN or three T3 PSTN telephony interfaces, either directly to
the PSTN or to an enterprise PBX.
Based on TP-8410 blades – The Mediant 3000 with TP-8410 blades incorporates up
to 63 E1 or 84 T1 PSTN interfaces and it also allows the user to have different and
dedicated physical Ethernet ports for each network type (Media, OAMP and Control).
The Mediant 3000 supports a broad selection of voice processing related algorithms,
including:
G.711, G.723.1, G.729A and multiple UMTS, GSM and CDMA Vocoders
G.168-2000 compliant echo cancellation
T.38 real-time Fax over IP
A wide selection of In-band and Out-of-band tone detection and generation
Signaling protocol support including ISDN PRI
The Mediant 3000 is available in the following operating modes:
Simplex Mode (one VoP communication blade and one SA/M3K Synchronization and
Alarm blade). In this mode there is an optional integrated CPU (iCPU) for 3rd party
applications.
High Availability 1+1 Mode (two VoP communication blades, two RTM and two
SA/M3K Synchronization and Alarm blades - one is active and the other is in standby
mode).
For High Availabilit y, the Mediant 3000's har dware design cont ains redundant m odules for
every part in the system, including redundant network connectivity, comprehensive
switchover processing and backup data storage and access, as well as applicable loadsharing schemes.
To achieve high-availability, the software itself resides on redundant components and
monitors system components to detect a hardware failure, as well as handling the
switchover procedures to overcome a possible failure. In addition, components are hotswappable so that they can be replaced while the system is fully operational with no
disruption to service.
The Mediant 3000 contains:
Up to two VoP communication blades
RTM (Rear Transition Module) blades:
In a Simplex configuration, up to two RTM blades for a TP-8410 based system, or a
single RTM for a TP-6310 based system.
In 1+1 system configuration, two RTM blades.
Up to two SA/M3K S ync hro ni zat ion and Alarm blades
Two Po wer Entr y Modu les ( PEM/D C/3 K)
Two Power Supplies (PS/DC/3K)
Version 6.6 9 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
These components function in either an Active / Standby redundant or load-sharing
configuration to prov id e f ul l cont inuo us per f ormance coverage an d are id ea l b ui ld ing bl oc k s
for deploying high-density, high availability Voice over Packet systems.
For more details on the High Availability 1+1 system, refer to 'The High Availability 1+1
System' on page 13.
User's Manual 10 Document #: LTRT-95211
User's Manual 1. Introduction
1.1 General Features
The Mediant 3000 has the following features:
Up to 2016 voice/ f ax/ data independent multiple LBR channels
PSTN interfaces:
• Up to 63 E1 / 84 T1 interfaces (with TP-8410)
• 1 + 1 Protected STM-1/OC-3 interface (with TP-6310)
• Three T3 interfaces (with TP-6310)
Packet interface:
• Dual GbE link ports (for redundancy)
• Four Fast links for multiple IP configurations (with TP-8410)
VoP and Voice Processing capabilities:
• Superior, high quality VoIP calls and FoIP transmissions
• Packet telephony standard compliant
• Vocoder configuration options include:
♦ AMR, AMR WB, EVRC, EVRC-B, G.711 A/u-law PCM, G.722, G.723.1,
G.726 ADPCM, G.727 ADPCM, G.729 A B, G.729.1 (up to 12 kbps),
G.729.1 (up to 32 kbps), G.729E, GSM-EFR, GSM-FR, iLBC, MS GSM &
EG.711
• Independent vocoder selection per channel
• VoIP packet streaming (RTP/ RTCP) per RFC 3550/2551
• RTP stream multiple destination connection
• IP to IP Mediation capabilities
• IP to IP Transcoding (G.711 to and from LBR, to GSM Vocoders, to UMTS
vocoders and to CDMA vocoders)
• Real-time Fax over IP/T.38 with superior performance (round trip delay of up to 9
sec)
• Automatic Fax Bypass modes
• DTMF Detection and Generation according to TIA 464B
• DTMF Relay according RFC 2833
• Tone detection and generation (MF, DTMF, RFC 2833)
• Extensive media processing functions
• G.168-2000 compliant Echo Cancelation with a 32, 64 or 128 msec tail
• Silence Suppression supporting VAD (Voice Activity Detection) and CNG
(Comfort Noise Generation)
“TDM- Switching” – for transferring TDM streams between timeslots
Call Control and Signaling support:
• Call Control: MGCP (RFC 3435), MEGACO (H.248) standard control protocols
• PSTN Signaling: CAS, ISDN, PRI, (and V5 for TP-8410)
• MF-R1, MFC-R2 and Call Progress Tone detection and generation
Version 6.6 11 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
Management Interfaces:
• SNMPv2, Web interface, EMS (Optional), SNMPv3
Mediant 3000 Platform capabilities:
• Flexible deployment and multiple density options
• Redundant Active / Standby configuration
• Load-sharing power supply configuration with separate power sources
• Carrier Grade Alarm System
• NEBS Level 3 compliant
User's Manual 12 Document #: LTRT-95211
User's Manual 1. Introduction
RTM With Full
Interfaces
6310 Active
Blade
SA Active
Card
6310
Redundant
Blade
SA
Redundant
Card
Slot1 Slot2 Slot3 Slot4
Internal Network Connection
Rear
Side
Lower
Side
Front
Side
Upper
Side
2xGbEDS3/SDH
RTM With
Ethernet
Interfaces
2xGbE
1.2 High Availability
The High Availability architecture of the Mediant 3000 provides the following functionality:
Redundant Active / Standby configuration
Support for both TP-6310 & TP-8410 blades
One or many global System IP addresses
Private IP address for each blade for maintenance and fallback.
Upgrading software without disrupting current calls (Hitless Software Upgrade)
1.2.1 Mediant 3000 HA System with TP-6310
The system includes t wo TP-6310 blades. One of the blades is the act ive (working) blade
and the other blade is the redundant (standb y) blade.
The figure below illustrates the general architecture of the Mediant 3000 with 1+1 High
Availability.
Figure 1: Mediant 3000 with TP-6310 System HA 1+1 Architecture
If both TP-6310 blad es are installed at the time the system is powered up, the TP-6310
blade in Slot 1 always initi ally assumes the Active functionalit y and the TP-6310 blade in
Slot 3 always initia lly assumes the Redundant f unctionality. If only one blad e is installed,
(no matter which slot it is occ upying) it al ways ass um es the Activ e funct ionalit y. If at a lat er
time, a second TP-6310 blade is added, this second TP-6310 blade assumes the
redundant functionality.
There is one internal Ethernet link between the Active and Redundant blades, which is
used for the management of the high availability feature. This link is automatically and
internally configured and is used by both of the blades.
Slots 2 and 4 in the front are occupied with the SA/M3K blades. One SA/M3K blade
assumes the Active f unctionality, while the other SA/M3K blade assumes the Redundant
functionality, according to each blade state.
On the rear of the chas sis, a RTM-6310 is located i n slot num ber 2. Its PSTN connections
and GbE interface are always con nected to the Ac tive TP-6310 bla de in the f ront in slot 1.
The RTM-6310/Redund ant is located in slot 3 and su pplies the GbE interfac es to the TP6310 blade in the front in slot 3.
Version 6.6 13 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
Rear
Side
Lower
Side
Front
Side
8410/RTM
Trunks 1-42
8410/RTM
Trunks 43-84
TP-8410
Blade
Default:
Active
Slot 1 Slot 2 Slot 3 Slot 4
Active Segment
Upper
Side
1+1 GBE
42 E1/T1
PSTN
SA/3K
Blade
Default:
Active
TP-8410
Blade
Default:
StandBy
SA/3K
Blade
Default:
StandBy
1+1 GBE
42 E1/T1
PSTN
Redundant Segment
PEM-3
Port A
PEM-3
Port B
PS-3
Power
Supply
PS-3
Power
Supply
48VDC
Source A
48VDC
Source B
Power Supplies
Shared Bus
2 Main
FE Links
BITS/
SETS
Contact
Closures
2 StandBy
FE Links
BITS/
SETS
Contact
Closures
Used by
the Active
TP-8410
Used by
the Active
TP-8410
Two GbE links can b e connected to each blad e through eac h RTM-63 10. At leas t one link
per blade must be connected, but two are recommended for LAN redundancy. After system
initialization is complete, network access is available only to the Active blade. The
Redundant GbE links have no network access.
1.2.2 Mediant 3000 HA System with TP-8410
The HA (High Availability) system includes two TP-8410 blades, two RTM-8410s (Rear
Transition Modules) and two SA/M3K Synchronization and Alarm blades
One of each of the blades is the active (working) blade and the other blade is the
redundant (standby) blade, as illustrated below:
Figure 2: Mediant 3000 with TP-8410 System HA 1+1 Architecture
If both TP-8410 blad es are installed at the time the s ys tem is powered up, the TP-8410
blade in Slot 1 alwa ys initially provides the Active function ality and the TP-8410 blade in
Slot 3 always initiall y provides the Redundan t functionality. If only one blade is insta lled,
(no matter which slot it is o ccupying) i t alwa ys provides the Active f unction ality. If at a later
User's Manual 14 Document #: LTRT-95211
User's Manual 1. Introduction
time, a second TP-8410 blade is added, this second TP-8410 blade provides the redundant
functionality.
There is one interna l Ether net (ET H) link bet ween the Acti ve and Redund ant bl ades , which
is used for the m anagement of the High Ava ilability feature. This link is automaticall y and
internally configured and is used by both of the blades.
Slots 2 and 4 in the front are occupied with the SA/M3K blades. One SA/M3K blade
provides the Active functionality, while the other SA/M3K blade provides the Redundant
functionality, according to each blade's state.
On the rear of the chas sis, an RTM-8410 is located in slot # 2. This RTM is connec ted to
trunks 1-42. Its PSTN connec tions and ETH interface are always connect ed to the Active
TP-8410 blade in the front in slot # 1. The second RTM-8410 is located in slot # 4. This 2nd
RTM is connected to tru nks 43-84. Trunks c onnec ted t o this RT M ar e direc te d to t he Ac t iv e
blade. ETH interfaces are directed to the TP-8410 blade in the front in slot # 3.
Two GbE links can be connec ted to each bl ade through eac h RTM-8410. At least one link
per blade must be connected, but two are recommended for LAN redundancy. After
system initialization is complete, network access is available only to the Acti ve blade. The
Redundant GbE links have no network access.
Each blade has its own local IP address (ac quired via BootP/D HCP) used for loading t he
software by TFTP. In or der for the system to be set to HA, the s ystem address must be
configured via the interface table.
1.2.3 Private IP Address and Sy stem (Global) IP Add ress(es)
Each blade on HA systems, has a single Private (Local) IP address and one or more
System (Global) IP Addresses.
Please refer to 'Ass igning the Dev ice IP Address ' on page 21 to configure th e Private and
System IP Addresses.
1.2.3.1 Private (Local) IP Address
This is a single IP address ( and subnet) per blade that is acquired via BootP/D HCP and
used for loading the software by TFTP.
1.2.3.2 System (Global) IP Address
The Global IP address(es) of the HA system are the IP Address(es) that ar e used by the
Active blade for Media, O AMP and Contr ol. These IP Addr ess(es) are c onfigured us ing an
interface table.
Note: In HA s ystems, the local IP ad dresses (one of each bla de) are rare ly used (on ly
when a major failure occurs). It is necessary to configure these addresses to be valid IP
addresses on the net work with full access to the Syslog server, s o in case of a m ajor
failure, the blades will be able to report to the Syslog server. Moreover, it is
recommended that th ese private IP addresses will be on same subnet as the OAM P
system IP address.
Version 6.6 15 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
T3
SDRAM
Flash
Time Slot
Assigner
H.110 Bus
Interface
PCM Highway
Framers
MPC8260
Parallel
Bus
Copper
Network
Processor
PCI Bus
Utopia
Bridge
STM-1 / OC-3
Transceiver
SDRAM
SRAM
Utopia Bus
Utopia Bus
PCM Highway
PCM Highway
H.110 TSI
Up to
21 AC491
DSPs on
Module
HPI
0 to 8
AC491
DSPs on
Baseboard
CPU
Controller
MPC8280
H.100 Bus
MPC8260
Parallel
Bus
Ethernet
Phy
Fiber Optic
2x Copper OR
2 x Fiber Optic
RJ-45 Copper
10/100/1000
or Optical GbE
OR
1.3 Functional Block Diagram - TP-6310
The figure below illustrates the functionality of the blade.
Figure 3: 6310 Functional Block Diagram
User's Manual 16 Document #: LTRT-95211
User's Manual 1. Introduction
SDRAM
Flash
Time Slot
Assigner
PCM Highway
Framers
MPC8260
Parallel
Bus
PSTN
Network
Processor
C-5e
PCI Bus
Utopia
Bridge
SDRAM
SRAM
Utopia Bus
Utopia Bus
PCM Highway
Up to
21 AC 491
DSPs on
Module
HPI
1 to 4
AC491
DSPs on
Baseboard
CPU
Controller
MPC8280
MPC8260
Parallel
Bus
Ethernet
Switch
RJ-45 Copper
10/100/ 1000
or Optical GbE
Storage Unit
RJ-45 Copper
10/100
RJ-45 Copper
10/100
H.110
Bus
H.110
2 x Copper OR
2 x Fiber Optic
4 x 10/100 Base Tx
1.4 Functional Block Diagram - TP-8410
The figure below illustrates the functionality of the blade.
Figure 4: TP-8410 Functional Block Diagram
Version 6.6 17 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
This page is intentionally left blank.
User's Manual 18 Document #: LTRT-95211
User's Manual 2. Software Package
2 Software Package
After installing and powering up the device, you are ready to install the utilities that are
included in the software package. This software package must be installed on the host
PC/machine to be used to manage the d evice. The sof tware package can b e downloaded
by registered users from the AudioCodes Web site at 'www.audiocodes.com/support'.
To become a registered user, follow the instructions on the Web site.
To get started:
1. To install the software package refer to 'Installing the Software Package' on page 19.
2. Check the software package contents (refer to ''Software Directory Contents &
Structure'' on page 20.)
2.1 Installing the Software Package
3. Perform ''Getting Started'' on page 21.
The software package is available on the AudioCodes' FTP Web site.
Customers using a Windows™ operating system may choose to install the package
via the installation wizard, or choose to unzip the software package from the supplied
zip file (refer to "Installing/Unzipping When Using a Windows™ Operating System"
below).
2.1.1 Installing/Unzipping When Using a Windows™ Operating System
To install the package:
1. Double-click on the setup.exe executable file.
2. Follow on-page instructions.
To unzip when using a Windows™ Operating System:
1. Using a tool like WinZip™, open the zip file.
2. Click the ‘Extract’ button; the ‘Extract’ page opens.
3. Nav igate to the directory that you require to b e the root directory for the installation
and click the ‘Extract’ button; the files are extracted to the location you specified.
Version 6.6 19 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
2.2 Software Directory Contents & Structure
Software Package Contents
Contents Directory Description
Auxiliary Files .\Auxiliary_Files\MIB_Files Various MIB files, e.g., SNMP MIB files: ACL.my,
RTP.my, ds1.my, MIB_2.m y, V2_MI B. my.
.\Auxiliary_Files\Sample_
Call_Progress_Files
.\Auxiliary_Files\Sample_
Contains examples of Call Progress Tones
configuration files.
Contains examples of CAS protocol files.
CAS_Protocol_Files
.\Auxiliary_Files\Sample_
Ini_Files
Contains examples of configuration (ini) files.
Users can utilize these sample files as a baseline
for creating customized configuration files.
Firmware .\Firmware Contains cmp files, loaded to the device when
changing the version of the software. When the
device is supplied to customers, it is already
configured with pre-installed firmware.
Utilities AudioCodes’ utilities pro vid e you with us er-friendly interfaces that enhance
device usability and smooth your transition to the new VoIP infrastructure.
.\Utilities\DConvert Contains the TrunkPack Downloadable
Construction Utilit y. Use the utilit y to build Call
Progress Tones, Voice Prompts, and CAS files.
.\Utilities\PSTN_TRACE_
UTILITY
.\Utilities\Wireshark
Plugins
This utility is designed to convert Wireshark log
files containing the PSTN trace to text format.
Contains the plugins for the Wireshark network
diagnostic tool. The plugin registers itself to
handle a dissection of AudioCodes' proprietary
protocol.
Documentation All relevant product documentation
Note: All the demo programs described above are for reference only. Flawless
operation and stability of these applications cannot be guaranteed.
User's Manual 20 Document #: LTRT-95211
User's Manual 3. Getting Started
3 Getting Started
The Mediant 3000 is supp li ed with app lic at io n sof t ware alr e ady resident in its flas h memory
3.1 Assigning the Device IP Address
(with factory default parameters). The Mediant 3000 is also supplied with a Web interface.
For detailed inform ation on how to fully configure the gateway refer to 'Device Ini tialization
& Configuration Files' on page 25 and 'Configuration Using the Web Interface' on page 43.
The Mediant 3000 HA c an be c onf ig ured vi a EM S (r ef er to LT RT-9480x EMS Conf igur ati on
Guide) or the Web interface (refer to 'Configuration Using the Web Interface' on page 43).
To assign an IP address to the Mediant 3000 use one of the following methods:
HTTP using a Web browser (refer to ''Assigning an IP Address Using HTTP'' on page
21).
BootP (refer to ''Assigning an IP Address Using BootP'' on page 22).
DHCP (refer to 'Using BootP/DHCP').
The default device IP Addresses are shown below.
Default Networking Parameters
Default IP address: 10.1.10.10
Default subnet mask is 255.255.0.0
Default gateway IP address is 0.0.0.0
3.1.1 Assigning an IP Address Using HTTP
To assign an IP address using HTTP:
1. Connect your PC to the device. Either connec t the network interfac e on your PC to a
port on a network hub / switch (using an RJ-45 Ethernet c able), or use an Ethernet
cross-over cable to directly connect the network interface on your PC to the RJ-45
jack on the device.
2. Chan ge your PC’s IP addres s and subnet m ask to corr espond with the d evice fac tory
default IP address and subnet mask, shown in the table above. For details on
changing the IP address and subnet mask of your PC, refer to Windows™ Online Help
(Start>Help and Support).
3. Acc es s the Web interface (refer to the W eb interface chapter in the Product Ref er enc e
Manual).
4. Click Reset and click OK in the prompt. The device applies the cha nges and res tarts.
This takes approximately 1 minute to complete. When the device has finished
restarting, the Ready and LAN LEDs on the front view are lit green.
Tip: Record and retain th e IP address and subnet mask you assign the device.
Do the same when definin g a new username or password. If the Web interface is
unavailable (for example, if you’ve lost your username and password), use a
BootP/TFTP configuration utility to access the device, “reflash” the load and reset
the password.
5. Disconnect your PC from the device or from the hub / switch (depending on the
connection method you used in step 1 above).
Version 6.6 21 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
6. Reconnect the device and your PC (if necessary) to the LAN.
7. Restore your PC’s IP address & subnet mask to what they originally were. If
necessary, restart your PC and re-access the device via the Web interface with its
new assigned IP address.
3.1.2 Assigning an IP Address Using BootP
Notes:
• The BootP procedure should be performed using any standard c ompatible BootP
server.
• For Mediant 3000 HA, in order to get the BootP reset request from the blade,
perform a double reset on the system, as described in 'Private IP Address and
System (Global) IP Address' on page 15.
Tip: You can also use BootP to load the auxiliary files to the device (refer to
'Using BootP/DHCP').
To assign an IP address using BootP:
1. Obtain and install a BootP server application on your PC.
2. Add the client configuration for the device.
3. Res et the g atew ay ph ysicall y causing it to us e Boot P. T he devic e changes its networ k
parameters to the values provided by BootP.
User's Manual 22 Document #: LTRT-95211
User's Manual 3. Getting Started
3.2 Assigning the IP Addresses for High Availability Mode
The private IP addr ess is assigned to the Active and Redundant blades (for m aintenance)
by using the BootP/DHCP.
To assign Private IP addresses to the Mediant 3000 blades:
1. Start your BootP/DHCP Server application.
2. Add a client configuration f or the Mediant 3000 that you wish to initialize and ins ert a
local (private) IP address for each of the two Mediant 3000 blades.
Note: Do not load a cm p or an ini file usin g a BootP/DHC P Server appl ication.
This action will erase the previous configuration that was stored to the flash
memory of the Mediant 3000 device.
3. Power down the Mediant 3000.
4. Power up the Mediant 3000 system for 30 seconds.
5. Power down the Mediant 3000.
6. Power up the Mediant 3000 system within 15 seconds.
7. Us ing a BootP/DHCP S erver app lication, verif y that both bla des in Sl ots 1 and 3 have
received their local IP addresses.
Note: A repeat power down and power up cycle, as described above, is
necessary. By default the redundant and active blades are set to load the IP
addresses from the flash memory and do not automatically send a BootP
request.
To assign an IP address via the CLI:
In the event that a BootP or DHCP server is not available in the network, the following
method can be used to assign local (private) IP addresses to the Mediant 3000 blades.
1. Connect the blade’s RS-232 port to either COM1 or COM2 communication port on
your PC using the serial cable supplied with the Mediant 3000.
2. Use a serial communication application (e.g., HyperTerminalTM) with the following
communications port settings:
• Baud Rate: 115,200 bps
• Data Bits: 8
• Parity: None
• Stop Bits: 1
• Flow Control: None
3. The CLI prompt appears.
4. At the prompt, type conf, and then press <Enter>; the configuration folder is
accessed.
5. Type scp ip <new private ip address> <netmask> <default gw>
(‘scp’ command stands for SetConfigParam) and then press <Enter>.
Version 6.6 23 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
6. T he new ip address is immediately being used (unles s the blade is the active blade
and it already uses the network IF table – global addresses).
7. Type sar.
(save and reset) for saving and restarting with configured address.
Note: The gcp ip comm and can be used to see a cur rent configured private
address.
This private address are used for maintenance purposes and also used as a fallback in
case of major system problem which prevents the system from working in HA mode.
In order for the s ystem to be set to HA, the s ystem's IP address(es ) must be configured.
The configured system address configuration is per f ormed via the Interface Table us ing th e
EMS (Refer to LTRT-9480x EMS Configuration Guide) or Web interface (refer to Network
on page 91). The configured system addresses should differ from private addresses.
Managing the system is done by connecting to the Active blade private address (the
Redundant blade management is blocked). If you don’t know which of the two private
addresses belongs to the active blade, try both. Only one will answer to the EMS/Web
connection attempt.
Note: HA will not be enabled until the system address has been configured.
User's Manual 24 Document #: LTRT-95211
User's Manual 4. System Initialization Process
4 System Initialization P rocess
This section describes the Initialization Procedures and Configuration Options for the
Mediant 3000 System. It includes:
Startup Process (see below)
Configuration Parameters and Files (refer to 'Configuration Parameters and Files' on
28)
page
BootP/DHCP (refer to Using BootP/DHCP)
Software Upgrade
4.1 Boot Firmware & Operational Firmware
High Availability Aspects
The device runs two distinct software programs: Boot firmware and operational firmware.
Boot firmware - Boot firmware (also known as flash software) resides in the device's
non-volatile memory. When the device is reset, Boot firmware is initialized and the
operational software is loaded into the SDRAM from a TFTP server or integral nonvolatile memory. Boot firmware is also responsible for obtaining the device's IP
parameters and ini file name (used to obtain the device's configuration parameters) via
integral BootP or DHCP clients. The Boot firmware version can be viewed on the Web
Interface. The last step the Boot firmware performs is to invoke the operational
firmware.
cmp Operational firmware file - The device is supplied with a cmp file pre-installed on
its flash memory. Therefore, this file is not included on the supplied CD. However, if
you are an AudioCodes registered customer, you can obtain the latest cmp version
files (as well as documentation and other software listed in the table above) from
AudioCodes Web site at 'www.audiocodes.com/support' (customer registration is
performed online at this Web site). If you are not a direct customer of AudioCodes,
please contact the AudioCodes' Distributor and Reseller from whom this product was
purchased.
For more information on BootP/DHCP, refer to the Product Reference Manual.
Note: The ini, MIB and Utility files are available on the CD supplied with the device.
Version 6.6 25 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
Download
firmware via
TFTP
BootP/DHCP
reply contains ini file
name?
Download
configuration
files via TFTP
Run operational
software
No
Reset command from Web interface,
or SNMP
Response to
BootP x times
No
No
Response to
DHCP x times
BootP
Response
Update network
parameters from
BootP/DHCP reply
DHCP
Response
Yes
Yes
No
BootP/DHCP
reply contains
Firmware
file name?
Yes
No
Yes
Reset board via Power Reset
Is device in HA
Mode?
No
Yes
4.2 Startup Process
For more information on BootP/DHCP, refer to the Product Ref erenc e Man ua l.
Figure 5: Startup Process Diagram
User's Manual 26 Document #: LTRT-95211
User's Manual 4. System Initialization Proces s
Notes:
• The default time duration between BootP/DHCP requests is set to 1 second.
This can be changed by the BootPDelay ini file parameter. Also, the default
number of requests is 3 and can be changed by the BootPRetries ini file
parameter. Both parameters can also be set using the Command Line
Switches in the BootP reply packet.
• The ini file configuration parameters are stored in non-volatile memory after
the file is loaded. When a parameter is missing from the ini file, a default
value is assigned to this parameter and stored in non-volatile memory
(thereby overriding any previous value set for that parameter). Refer to Using
BootP/DHCP below.
Version 6.6 27 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
4.3 Configuration Parameters and Files
The device's configuration is stored in two file groups.
The Initialization file - an initialization (ini) text file containing configuration parameters
of the device.
The Auxiliary files - dat files containing the raw data used for various tasks such as
Call Progress Tones, Voice Prompts, logo image, etc.
These files contain factory-pre-configured parameter defaults when supplied with the
device and are store d i n th e de vice's non-volatile mem ory. T he de vice is s tar te d up in it ially
with this default configuration. Subsequently, these files can be modified and reloaded
using either of the following methods:
BootP/TFTP during the startup process (refer to 'Using BootP/DHCP').
Web Interface (refer to 'Configuration Using the Web Interface' on page 43).
Automatic Update facility (refer to 'Automatic Update Facility' on page 34).
The modified auxiliar y files are burned into the n on-volatile memory so that the modif ied
configuration is utilized with subsequent resets. T he configuration file is al ways stored on
the non-volatile memory. There is no need to repeatedly reload the modified files after
reset.
Notes:
• Users who configure the device with the Web interface do not require ini files
to be downloaded and have no need to utilize a TFTP server.
• SNMP users configure the device via SNMP. Therefore a very small ini file is
required which contains the IP address for the SNMP traps.
4.3.1 Initialization (ini) File
The ini file name must not include hyphens or spaces. Use underscores instead.
The ini file can contain a num ber of par ameters . The ini file st ructure s uppor ts the f ollowing
parameter value constructs:
Parameter = Value (refer to 'Parameter = Value Constructs'). The lists of parameters
are provided in the ini File Parameters chapter of the Product Reference Manual.
Tables of Parameter Value (refer to ''Table of Parameter Value Constructs'' on page
31).
The example below shows a sample of the general structure of the ini file for both the
Parameter = Value and Tables of Parameter Value Constructs.
[Sub Section Name]
Parameter_Name = Parameter_Value
Parameter_Name = Parameter_Value
.
..
; REMARK
[Sub Section Name]
...
User's Manual 28 Document #: LTRT-95211
User's Manual 4. System Initialization Process
; Tables Format Rules:
[Table_Name]
; Fields declaration
Format Index_Name_1 ... Index_Name_N = Param_Name_1 ...
Param_Name_M
; Table's Lines (repeat for each line)
Table_Name Index_1_val ... Index_N_val = Param_Val_1 ...
Param_Val_M
[\Table_Name]
4.3.1.1 Paramet er Val ue St r uct u re
The following are the rules in the ini File structure for individual ini file parameters
(Parameter = Value):
Lines beginning with a semi-colon ';' (as the first character) are ignored.
A carriage-return/line-feed must be the final character of each line.
The number of spaces before and after "=" is not relevant.
If there is a syntax error in the parameter name, the value is ignored.
Syntax errors in the parameter value field can cause unexpected errors (because
parameters may be set to the incorrect values).
Sub-section names are optional.
String parameters, representing file names, for example,
CallProgressTonesFileName, must be placed between two inverted commas ('…').
The parameter name is NOT case sensitive; the parameter value is usually case
sensitive.
Numeric parameter values should be entered only in decimal format.
The ini file should be ended with one or more empty lines.
ini File Examples
The example below shows a sample ini file for MGCP.
[TDM BUS configuration]
; 1=aLaw 3=ulaw
PCMLawSelect = 1
BaseUDPPort = 4000
[Trunk Configuration]
;E1_trans_31
ProtocolType = 5
; USER_TERMINATION_SIDE
TerminationSide = 0
; EXTENDED_SUPER_FRAME
FramingMethod = 0
;HDB3
LineCode = 2
[MGCP]
EndpointName = 'ACgw'
CallAgentIP = 10.1.2.34
[Channel Params]
DJBufferMinDelay = 75
RTPRedundancyDepth = 1
Version 6.6 29 Mediant 3000 with TP-6310 & TP-8410
Mediant 3000 with TP-6310 & TP-8410
[Files]
CallProgressTonesFilename = 'CPUSA.dat'
VoicePromptsFilename = 'tpdemo_723.dat'
CasFilename = 'E_M_WinkTable.dat'
The example below shows a sample ini file for MEGACO.
[MEGACO]
; List of Call agents, separated by ','.
; The default is the loading computer.
PROVISIONEDCALLAGENTS = 10.2.1.254
; List of ports for the above Call Agents, separated by ','. The
default is 2944.
PROVISIONEDCALLAGENTSPORTS = 2944
; The next 2 fields are the termination names patterns.
; The first is the pattern for the physical termination, and the
; second is the pattern for the RTP termination. The '*' stands
for ; a number.
PHYSTERMNAMEPATTERN = gws*c*
LOGICALRTPTERMPATTERN = gwRTP/*
; This parameter activates MEGACO. If omitted, MGCP will be active
MGCONTROLPROTOCOLTYPE = 2
; The following disables the keep-alive mechanism if set to 0,
; else it is enabled. Note that the recommended KeepAlive method
is
; the use of the inactivity timer package - 'it'.
KEEPALIVEENABLED = 1
;
; This parameter defines the profile used, and it is a bitmask
MGCPCOMPATIBILITYPROFILE = 2
Note: Before loading an i ni file to the device, m ake sure that the ext ension of the ini
file saved on your PC is correc t: Verify that the c heckbox Hide ex tension f or known f ile
types (My Computer>Tools >Folder Options>View) is unchec ked. Then, verify that the
ini file name extension is xxx.ini and NOT erroneously xxx.ini.ini or xxx~.ini.
The lists of individual ini file parameters are provided in ini File Parameters.
User's Manual 30 Document #: LTRT-95211
Loading...