AudioCodes Mediant 3000 User manual

User's Manual
Mediant 3000 with TP-6310 & TP-8410
Version 6.6
December 2015
Document # LTRT-95211
Mediant™ 3000
VoIP Digital Media Gateway
MGCP & MEGACO Protocols

Version 6.6 3 Mediant 3000 with TP-6310 & TP-8410
User's Manual Contents
Table of Contents
1Introduction .........................................................................................................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
2Software 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
3Getting 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 Address Using BootP ....................................................................22
3.2 Assigning the IP Addresses for High Availability Mode.........................................23
4System 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
5Configuration Using the Web Interface...........................................................43
5.1 Limiting the Web Interface to Read-Only Mode ....................................................43
5.2 Disabling the Web Interface..................................................................................44

User's Manual 4 Document #: LTRT-95211
Mediant 3000 with TP-6310 & TP-8410
5.2.1 Encrypted 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

Version 6.6 5 Mediant 3000 with TP-6310 & TP-8410
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
6Troubleshooting..............................................................................................175
6.1 TP-6310 Self-Test ..............................................................................................175
6.2 TP-8410 Self-Test ..............................................................................................176
7Technical Specifications ................................................................................177
7.1 Mediant 3000 with TP-6310/TP-8410 Technical Specification ............................177
8List of Abbreviations.......................................................................................183
9Index.................................................................................................................187

User's Manual 6 Document #: LTRT-95211
Mediant 3000 with TP-6310 & TP-8410
This page is intentionally left blank.

Version 6.6 7 Mediant 3000 with TP-6310 & TP-8410
User's Manual Notices
Notice
This document describes the AudioCodes Mediant 3000 MGCP & MEGACO media gateway,
housed with TP-8410 SIP blade(s) or TP-6310 blade(s).
Information contained in this document is believed to be accurate and reliable at the time of
printing. However, due to ongoing product improvements and revisions, AudioCodes cannot
guarantee accuracy of printed material after the Date Published nor can it accept
responsibility for errors or omissions. Updates to this document and other documents as well
as software files can be viewed by registered customers at
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 Sounds Better, IPmedia, 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 notice.
WEEE EU Directive
Pursuant to the WEEE EU Directive, electronic and electrical waste must not be disposed
of with unsorted waste. Please contact your local recycling authority for disposal of this
product.
Customer Support
Customer technical support and services are provided by AudioCodes or by an authorized
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.

User's Manual 8 Document #: LTRT-95211
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.

Version 6.6 9 Mediant 3000 with TP-6310 & TP-8410
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 various
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 Availability, the Mediant 3000's hardware design contains redundant modules for
every part in the system, including redundant network connectivity, comprehensive
switchover processing and backup data storage and access, as well as applicable load-
sharing 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 hot-
swappable 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 Synchronization and Alarm blades

Two Power Entry Modules (PEM/DC/3K)

Two Power Supplies (PS/DC/3K)

User's Manual 10 Document #: LTRT-95211
Mediant 3000 with TP-6310 & TP-8410
These components function in either an Active / Standby redundant or load-sharing
configuration to provide full continuous performance coverage and are ideal building blocks
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.

Version 6.6 11 Mediant 3000 with TP-6310 & TP-8410
User's Manual 1. Introduction
1.1 General Features
The Mediant 3000 has the following features:

Up to 2016 voice/fax/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

User's Manual 12 Document #: LTRT-95211
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

Version 6.6 13 Mediant 3000 with TP-6310 & TP-8410
User's Manual 1. Introduction
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 two TP-6310 blades. One of the blades is the active (working) blade
and the other blade is the redundant (standby) 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 blades are installed at the time the system is powered up, the TP-6310
blade in Slot 1 always initially assumes the Active functionality and the TP-6310 blade in
Slot 3 always initially assumes the Redundant functionality. If only one blade is installed,
(no matter which slot it is occupying) it always assumes the Active functionality. If at a later
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 functionality, while the other SA/M3K blade assumes the Redundant
functionality, according to each blade state.
On the rear of the chassis, a RTM-6310 is located in slot number 2. Its PSTN connections
and GbE interface are always connected to the Active TP-6310 blade in the front in slot 1.
The RTM-6310/Redundant is located in slot 3 and supplies the GbE interfaces to the TP-
6310 blade in the front in slot 3.
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

User's Manual 14 Document #: LTRT-95211
Mediant 3000 with TP-6310 & TP-8410
Two GbE links can be connected to each blade through each RTM-6310. 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 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 blades are installed at the time the system is powered up, the TP-8410
blade in Slot 1 always initially provides the Active functionality and the TP-8410 blade in
Slot 3 always initially provides the Redundant functionality. If only one blade is installed,
(no matter which slot it is occupying) it always provides the Active functionality. If at a later
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

Version 6.6 15 Mediant 3000 with TP-6310 & TP-8410
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 internal Ethernet (ETH) 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
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 chassis, an RTM-8410 is located in slot # 2. This RTM is connected to
trunks 1-42. Its PSTN connections and ETH interface are always connected 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 trunks 43-84. Trunks connected to this RTM are directed to the Active
blade. ETH interfaces are directed to the TP-8410 blade in the front in slot # 3.
Two GbE links can be connected to each blade through each 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 Active blade. The
Redundant GbE links have no network access.
Each blade has its own local IP address (acquired via BootP/DHCP) used for loading the
software by TFTP. In order for the system to be set to HA, the system address must be
configured via the interface table.
1.2.3 Private IP Address and System (Global) IP Address(es)
Each blade on HA systems, has a single Private (Local) IP address and one or more
System (Global) IP Addresses.
Please refer to 'Assigning the Device IP Address' on page 21 to configure the 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/DHCP 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 are used by the
Active blade for Media, OAMP and Control. These IP Address(es) are configured using an
interface table.
Note: In HA systems, the local IP addresses (one of each blade) are rarely used (only
when a major failure occurs). It is necessary to configure these addresses to be valid IP
addresses on the network with full access to the Syslog server, so in case of a major
failure, the blades will be able to report to the Syslog server. Moreover, it is
recommended that these private IP addresses will be on same subnet as the OAMP
system IP address.

User's Manual 16 Document #: LTRT-95211
Mediant 3000 with TP-6310 & TP-8410
1.3 Functional Block Diagram - TP-6310
The figure below illustrates the functionality of the blade.
Figure 3: 6310 Functional Block Diagram
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

Version 6.6 17 Mediant 3000 with TP-6310 & TP-8410
User's Manual 1. Introduction
1.4 Functional Block Diagram - TP-8410
The figure below illustrates the functionality of the blade.
Figure 4: TP-8410 Functional Block Diagram
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
21AC 491
DSPs on
Module
HPI 1 to4
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

User's Manual 18 Document #: LTRT-95211
Mediant 3000 with TP-6310 & TP-8410
This page is intentionally left blank.

Version 6.6 19 Mediant 3000 with TP-6310 & TP-8410
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 device. The software package can be 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.)
3. Perform ''Getting Started'' on page 21.
2.1 Installing the Software Package
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. Navigate to the directory that you require to be the root directory for the installation
and click the ‘Extract’ button; the files are extracted to the location you specified.

User's Manual 20 Document #: LTRT-95211
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.my, V2_MIB.my.
.\Auxiliary_Files\Sample_
Call_Progress_Files Contains examples of Call Progress Tones configuration files.
.\Auxiliary_Files\Sample_
CAS_Protocol_Files Contains examples of 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 provide you with user-friendly interfaces that enhance
device usability and smooth your transition to the new VoIP infrastructure.
.\Utilities\DConvert Contains the TrunkPack Downloadable
Construction Utility. Use the utility to build Call
Progress Tones, Voice Prompts, and CAS files.
.\Utilities\PSTN_TRACE_
UTILITY This utility is designed to convert Wireshark log files containing the PSTN trace to text format.
.\Utilities\Wireshark
Plugins 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.