Page 1 User’s Manual Version 4.4 Beta Document Number: LTRT-69801...
Page 2 Mediant 2000 User’s Manual Document #: LTRT-69801...
Page 3 To reach the individual cross-referenced item directly, you may click on the hyperlinked item, i.e. a page number or section numbers. Structure of this Manual This Mediant 2000 User’s Manual has the following sections: General Notices Contents, Figures and Tables 1.
Page 4: Customer Support
Notice This User’s Manual describes the installation and use of AudioCodes’ Mediant 2000 devices. 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 the accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions.
Page 5: Table Of Contents
3.1 Unpacking ........................33 3.1.1 Package Contents......................34 3.2 Mounting the Mediant 2000..................34 3.2.1 Mounting a Mediant 2000 in a 19-inch Rack..............35 3.2.2 Installing the Mediant 2000 on a Desktop ..............36 3.3 Cabling the Mediant 2000................... 36 3.3.1 Power Supply Cabling....................
Page 6 Mediant 2000 4.3 Upgrading Device Software ..................56 4.4 License Key......................... 57 5 Standard Control Protocols ..............59 5.1 General ........................59 5.2 MGCP Control Protocol....................59 5.2.1 MGCP Overview ......................59 5.2.2 MGCP Operation......................59 5.2.2.1 Executing MGCP Commands ............. 59 5.2.2.2 Setting MGCP Call Agent IP Address ..........
Page 7 6.3.2.1 Limiting the Embedded Web Server to Read-Only Mode ....111 6.3.2.2 Disabling the Embedded Web Server ..........111 6.3.3 Correlating PC /Mediant 2000 IP Address & Subnet Mask.......... 112 6.3.4 Accessing the Embedded Web Server ................ 112 6.3.5 Using Internet Explorer to Access the Embedded Web Server ........113 6.4 Getting Acquainted with the Web Interface ............
Page 8 7.4 Modifying the Call Progress Tones & Sending it to the Device ......195 7.4.1 Converting a Modified CPT ini File to a dat File with AudioCodes' Download Conversion Utility..............195 7.4.2 Playing Prerecorded Tones (PRT) ................196 7.4.2.1 PRT File Configuration................ 196 7.4.2.2 Downloading the PRT dat File ............
Page 9 B.2 Payload Types Not Defined in RFC 3551 ............... 220 B.3 Default Dynamic Payload Types Which are Not Voice Coders......220 B.4 Mediant 2000 Default RTP/RTCP/T.38 Port Allocation.......... 221 Appendix C DTMF, Fax and Modem Transport Modes ......223 C.1 DTMF/MF Relay Settings ..................223 C.2 Fax/Modem Settings ....................
Page 10 F.1 MGCP Compliance Matrix..................251 Appendix G MEGACO Compliance ............265 G.1 MEGACO Compliance Matrix.................. 265 Appendix H Customizing the AudioCodes Web Interface ..... 277 H.1 Company & Product Bar Components..............277 H.2 Replacing the Main Corporation Logo ..............278 H.2.1 Replacing the Main Corporation Logo with an Image File...........
Page 11 Figure 1-1: TP-1610 Functional Block Diagram ................ 19 Figure 1-2: Typical Mediant 2000 VoIP Application ..............20 Figure 2-1: Front View of Mediant 2000 Populated with AudioCodes’ TP-1610 Board ..21 Figure 2-2: AudioCodes’ TP-1610 Board .................. 22 Figure 2-3: View of AudioCodes’ TP-1610 RTM ............... 23 Figure 2-4: TP-1610 Board, Front Panel View ................
Page 12 Figure 7-3: Example of an ini File for MGCP ................186 Figure 7-4: ini File Example for MEGACO ................187 Figure 8-1: AudioCodes' Syslog Server Main Screen and Settings Screen ......199 Figure 8-2: Setting the Syslog Server IP Address ..............200 Figure 8-3: Setting Syslog Server IP Address, Enabling Syslog, in an ini File (Example) ..................
Page 13 Mediant 2000 List of Tables List of Tables Table 2-1: Chassis Indicators ......................22 Table 2-2: Board Status LED Indicators..................30 Table 2-3: Trunk Status LED Indicators ..................30 Table 2-4: Ethernet LED Indicators ....................30 Table 2-5: Auxiliary LED Indicators....................30 Table 3-1: Connections on Each 50-Pin Telco Connector ............39 Table 4-1: Software Package Contents ..................46...
Page 14 Mediant 2000 Table 5-38: Inactivity Timer Package - IT ..................91 Table 5-39: Basic Call Progress Tones Generator with Directionality Package - BCG ....92 Table 5-40: Call Type Discrimination Package - CTYP ...............92 Table 5-41: IP Fax Package - IPFAX .....................92 Table 5-42: MEGACO Endpoint Names (continues on page 95 to page 96)......95...
Page 15: Overview Of The Mediant 2000
ISDN PRI, SIGTRAN (M2UA, M3UA, IUA) and CAS. The Mediant 2000 incorporates 1, 2, 4, 8 or 16 E1 or T1 spans for connection, either directly to PSTN telephony trunks, or to an enterprise PBX, and two 10/100 Base-T Ethernet ports for redundant connection to the LAN.
Page 16: General Features
Mediant 2000 General Features AudioCodes’ Mediant 2000 has the following features: Vocoder configuration options: PCM/ADPCM, G.723, G.729A, GSM FR and NetCoder Up to 16 E1/T1 digital spans Independent vocoder selection per channel Extensive media processing functions RTP stream multiple destination connection (i.e., to TDM, other RTP channels...
Page 17: Tp-1610 Software Overview
Additionally, demo applications are provided. These applications can serve as a reference for developing applications using the VoPLib API. Mediant 2000 Applications AudioCodes’ Mediant 2000 can be used in a variety of applications, which exploit its unique advantages regarding compressing PCM voice channels to IP packets according to ITU standards.
Page 18: Benefits
Concurrent toll quality voice and fax support Wide range of PSTN signaling protocols Fast time-to-market Flexible and easy migration to VoIP networks Extensive VoIP experience accumulated by AudioCodes All-in-one integrated board - Reduced inventory Scalable distributed architectures Shorter development cycle User’s Manual...
Page 19: Functional Block Diagram
Overview of the Mediant 2000 Functional Block Diagram Figure 1-1 illustrates the functionality of AudioCodes’ TP-1610 board. Figure 1-1: TP-1610 Functional Block Diagram Note: The H.110 Bus Interface in not applicable to the Mediant 2000. Version 4.4 Beta June 2004...
Page 20: Figure 1-2: Typical Mediant 2000 Voip Application
Mediant 2000 Figure 1-2, illustrates a typical Mediant 2000 VoIP application. Figure 1-2: Typical Mediant 2000 VoIP Application User’s Manual Document #: LTRT-69801...
Page 21: Hardware Equipment
The Mediant 2000 chassis’ rear cage, slot #1 - the lower slot, houses the TP-1610 RTM. Slot # 2 in the Mediant 2000 chassis’ front and rear cages optionally can be used by Customers for a CPU board. For more information on CPU board options, refer to Section 2.3 on page 31.
Page 22: Chassis Led Indicators
AC connection only.) The TP-1610 Board The TP-1610 cPCI Board is the main component of the Mediant 2000. It is supplied within the Mediant 2000 Gateway shown in Figure 2-1, on page 21. The front panel of the TP-1610 board is shown in Figure 2-4 on page 24. The panel options for the TP-1610 RTM are shown in Figure 2-5 on page 25 to Figure 2-9 on page 29.
Page 23: Board Hot-Swap Support
Mediant 2000 Hardware Equipment Figure 2-3: View of AudioCodes’ TP-1610 RTM 2.2.1 Board Hot-Swap Support The TP-1610 board is hot swappable and can therefore be removed from a slot (and inserted into a slot) when the cPCI system is under power.
Page 24: Figure 2-4: Tp-1610 Board, Front Panel View
Mediant 2000 Figure 2-4: TP-1610 Board, Front Panel View cPCI Latch FAIL Red - Board Failure Green - Active board Yellow - Standby board (N/A) Trunk Status (for each of trunks 1 to 8) Green - All OK Red - Alarm due to any of these 4:...
Page 25: Figure 2-5: Rtm Panel With 2 Telco Connectors (For 16-Spans)
Mediant 2000 Hardware Equipment Figure 2-5: RTM Panel with 2 Telco Connectors (For 16-Spans) cPCI Latch Trunks 1 - 8 50-Pin male Telco connector Trunks 9 - 16 50-Pin male Telco connector cPCI Latch Version 4.4 Beta June 2004...
Page 26: Figure 2-6: Rtm Panel With 8 Rj-48C Trunk Connectors
Mediant 2000 Figure 2-6: RTM Panel with 8 RJ-48c Trunk Connectors cPCI Latch 8 E1/T1 Trunks RJ-48c Connectors 2 Ethernet Ports 2 RJ-45 Connectors ETH 1 ETH 2 cPCI Latch User’s Manual Document #: LTRT-69801...
Page 27: Figure 2-7: Rtm Panel With 4 Rj-48C Trunk Connectors
Mediant 2000 Hardware Equipment Figure 2-7: RTM Panel with 4 RJ-48c Trunk Connectors cPCI Latch 4 E1/T1 Trunks RJ-48c Connectors 2 Ethernet Ports 2 RJ-45 Connectors ETH 1 ETH 2 cPCI Latch Version 4.4 Beta June 2004...
Page 28: Figure 2-8: Rtm Panel With 2 Rj-48C Trunk Connectors
Mediant 2000 Figure 2-8: RTM Panel with 2 RJ-48c Trunk Connectors cPCI Latch 2 E1/T1 Trunks RJ-48c Connectors 2 Ethernet Ports 2 RJ-45 Connectors ETH 1 ETH 2 cPCI Latch User’s Manual Document #: LTRT-69801...
Page 29: Figure 2-9: Rtm Panel With 1 Rj-48C Trunk Connector
Mediant 2000 Hardware Equipment Figure 2-9: RTM Panel with 1 RJ-48c Trunk Connector cPCI Latch 1 E1/T1 Trunk RJ-48c Connector 2 Ethernet Ports 2 RJ-45 Connectors ETH 1 ETH 2 cPCI Latch Version 4.4 Beta June 2004...
Page 30: Tp-1610 Board Front Panel Led Indicators
Mediant 2000 2.2.2 TP-1610 Board Front Panel LED Indicators Refer to Table 2-2 through to Table 2-5 for LED indicator definitions. Table 2-2: Board Status LED Indicators Label Color Function FAIL Normally OFF; Red indicates board failure (fatal error) Green...
Page 31: Optional Cpu Board
For more information of board replacement, refer to Section 3.4 on page 43. Optional CPU Board The Mediant 2000 device features a second cPCI slot that can be optionally used for a customer's CPU board. The CPU board can be used for general applications such as a Softswitch, Application Server, etc.
Page 32 Mediant 2000 Reader’s Notes User’s Manual Document #: LTRT-69801...
Page 33: Hardware Installation
Mediant 2000 Hardware Installation Hardware Installation This section describes the installation procedures for the Mediant 2000 system, as well as board replacement procedures. The Mediant 2000 can be installed either as a desktop system or as a chassis in a standard 19-inch rack.
Page 34: Package Contents
Ensure that the Mediant 2000 package includes the following items (in addition to the device): For the dual AC power supply version of the Mediant 2000, two AC power cables are supplied; for the single AC power supply version of the Mediant 2000, one AC power cable is supplied;...
Page 35: Mounting A Mediant 2000 In A 19-Inch Rack
LEDs are functional; if 4 trunks, only the first four LEDs are functional. AudioCodes’ Mediant 2000 can be mounted, as required, on a desktop or in a standard 19-inch rack. Attach cables as described in Section 3.3 on page 36.
Page 36: Installing The Mediant 2000 On A Desktop
Refer to Figure 3-4 below and Figure 3-10, on page 41 for the rear connectors on the 8-trunk version. Note: The Mediant 2000 is available in all configuration combinations, i.e., AC or DC, as a 16-trunk, 8-trunk, 4-trunk, 2-trunk or 1-trunk configuration. The 16- trunk AC and the 8-trunk DC configuration combinations are illustrated here as representative of the range.
Page 37: Power Supply Cabling
Ground Connector Screw Two 50-Pin Telco Dual 3-Pin AC Power Cable Two RJ-45 Female Connectors Connectors Ethernet Ports Figure 3-4: Mediant 2000 Rear Connections (8 Spans, DC Power) Ground Connector Screw -48 VDC Eight RJ-48c Two RJ-45 Power Connector Connectors Ethernet Ports 3.3.1...
Page 38: Connecting The E1/T1 Trunk Interfaces
Mediant 2000 Figure 3-5: DC Power Connector Note: When cabling a device with a dual AC power supply: The LED on the left side of the device's front panel is activated only on devices featuring a dual AC power supply. It is not relevant to devices featuring a single AC power supply.
Page 39: Figure 3-6: 50-Pin Female Telco Board-Mounted Connector
Step 2b. If you are using RJ-48c connectors: Connect the E1/T1 trunk cables to the Mediant 2000’s E1/T1 interfaces on the RTM panel (refer to Figure 3-7). There are up to eight RJ-48c connectors labeled Trunks 1 to 8 on the RTM, shown in Figure 3-7 below.
Page 40: Figure 3-8: Rj-45 Ethernet/Lan Network Connectors
Restart the applications and run the system. Step 6. Power up the Mediant 2000 The Ready and LAN LEDs on the front panel turn to green (after a self-testing period of about 60 seconds). Any malfunction causes the Ready LED to turn red (refer to Section 2.2.2 on page 30 for details on the Mediant 2000 LEDs).
Page 41: Board Replacement
Mediant 2000 Hardware Installation Figure 3-9: Mediant 2000 Rear with Connected Cables (16 Spans and Dual AC) Ground Connector Screw Category 5 LAN Two cables, each cables, connected Dual 3-Pin AC Power Cable terminated with male to the Ethernet Connectors 50-Pin Telco Connectors.
Page 42: Performing Graceful Lock
Prior to powering down the Mediant 2000, it should be locked gracefully (with no active calls forced to terminate) using the element management system employed in your system.
Page 43: Inserting Boards
The MAC address of the replacement board should be updated in the parameter configuration in the element management system you are utilizing. The Mediant 2000 should be unlocked using the element management system (EMS) employed in your system. For more information on performing graceful lock, refer to Section 3.4.2 on page 42 or the user documentation accompanying the element...
Page 44 Mediant 2000 Reader’s Notes User’s Manual Document #: LTRT-69801...
Page 45: Audiocodes' Software Package
Unzipping the Software Package The software package is contained in AudioCodes' CD supplied with the device. It is also available on AudioCodes' FTP server or on AudioCodes' Web site. Customers using a Windows™ operating system unzip the software package from the self-extractable exe file (refer to Section 4.1.1).
Page 46: Software Directory Structure
Description VoPLibrary sources The VoPLibrary is AudioCodes’ proprietary API for controlling and managing the device. Detailed information on the VoPLibrary can be found in AudioCodes’ VoPLib API Reference Manual, Document #: LTRT-84001 and VoPLib User’s Manual, Document #: LTRT-84401. Utilities These are AudioCodes’...
Page 47: Call Control Protocols
The TP-1610 can be controlled by the following call control protocols: VoPLib over PCI/cPCI - The TP-1610 can be controlled directly through its cPCI interface by AudioCodes’ proprietary API. This API is composed of two software modules, the VoPLib, providing control over all VoIP-related functionality, and the PSTNLib, providing control over all PSTN interface functionality.
Page 48: Management Protocols
IETF’s RFC1305. Through these requests and responses, the AudioCodes NTP client is able to synchronize the system time to a time source within the network thereby eliminating any potential issues should the local system clock 'drift' during operation.
Page 49: Boot Software And Firmware
AudioCodes' VoPLib API Reference Manual, Document #: LTRT-84001 and VoPLib User's Manual, Document #: LTRT-84401). ini File - The ini file is an AudioCodes proprietary text file that includes the device's configuration parameters (for more information on the ini file, refer to Section 8 on page 161).
Page 50: Configuration Files
Prerecorded Tones file – contains prerecorded tones that can be played using regular tone generation request. The configuration files can be loaded into the device via AudioCodes' BootP/TFTP Server or the Embedded Web Server. Most can be burned into the device's non-volatile flash memory so that reloading is not required after every device reset.
Page 51: Figure 4-1: Device Startup Process
Mediant 2000 AudioCodes’ Software Package Figure 4-1: Device Startup Process Version 4.4 Beta June 2004...
Page 52: Bootp/Dhcp Server
4.2.6 BootP/DHCP Server AudioCodes' devices use BootP (Bootstrap protocol) and DHCP to configure the device's initial parameters. BootP/DHCP servers enable network administrators to manage the basic configuration of the TP-1610 from a central PC RFCs (IETF Requests for Comment) 951, 1542, and 2132 describe BootP in detail.
Page 53: Bootp/Dhcp Server Parameters
Command Line Switches In AudioCodes' BootP/TFTP Server, you can add command line switches in the Boot File field (in the Client Configuration screen). Only the cmp file (the compressed firmware file) can be burned to your device's flash memory. You cannot burn the hex file (the uncompressed firmware file) because it is too big.
Page 54: Table 4-3: Command Line Switch Descriptions
TFTP Server’s main screen with the column 'Client Info' on the extreme right). ‘Client Info’ can include IP address, number of channels (in the case of AudioCodes' media gateways), which cmp file is burned into the device's flash memory, etc.
Page 55: Host Name Support
Mediant 2000 AudioCodes’ Software Package 4.2.6.2 Host Name Support From Boot software version 1.92, the device registers a device-specific Host Name on the DNS server by defining the Host Name field of the DHCP request. The host name is set to acl_nnnnnnn, where nnnnnnn is the serial number of the device (the serial number is equal to the last 6 digits of the MAC address converted from HEX to decimal).
Page 56: Microsoft™ Dhcp/Bootp Server
™ 4.2.7 Microsoft DHCP/BootP Server The device can be configured with a 3rd party BootP server (besides AudioCodes' BootP/ ™ TFTP Server), including the Microsoft DHCP server, to provide the TP-1610 with an IP address and other initial parameter configurations.
Page 57: License Key
The License Key can be updated to expand the features and capabilities of the TP-1610. The License Key is upgraded via a file, supplied to customers by AudioCodes, containing a key for one or more devices. Users must specify this file as an ini file and load it into the device instead of an ini file.
Page 58 Mediant 2000 Reader’s Notes User’s Manual Document #: LTRT-69801...
Page 59: Standard Control Protocols
Call Agent using standard MGCP (Media Gateway Control Protocol), MEGACO (Media Gateway Control) protocol and AudioCodes proprietary TPNCP (TrunkPack Network Control Protocol). For information on TPNCP, refer to the section on TPNCP in AudioCodes’ “VoPLib User’s Manual”, Document #: LTRT-84401). MGCP Control Protocol 5.2.1...
Page 60: Setting Mgcp Call Agent Ip Address
Mediant 2000 5.2.2.2 Setting MGCP Call Agent IP Address Users can set the IP address and port of the MGCP Call Agent using the CallAgentIP and Call Agent port parameters. A redundant Call Agent can also be specified using the parameters RedundantAgentIP and RedundantAgentPort.
Page 61: Sdp Support In Mgcp
Mediant 2000 Standard Control Protocols KeepAlive examples: While working in endpoint naming conversions: RSIP 2200 *@AudioCodes.Com MGCP 1.0 RM: X-KeepAlive While working in trunk naming conversions: RSIP 2420 ds/tr/*/*@AudioCodes.Com MGCP 1.0 RM: X-KeepAlive 5.2.5 SDP Support in MGCP MGCP supports basic SDP (Session Description Protocol), as defined in RFC 2327. It also supports SDP-ATM, as defined in RFC 3108.
Page 62: Tgcp Compatibility
Mediant 2000 5.2.7 TGCP Compatibility To use TGCP conventions, the user must set the device to the TGCP profile, e.g. adding MGCPCompatibilityProfile = 32 to the device’s ini file. The following lists the supported TGCP additions: Endpoint Naming Scheme - Supports wild card and Endpoint naming conventions.
Page 63 Mediant 2000 Standard Control Protocols Table 5-2: MGCP Mapping of Payload Numbers to Coders (continues on page 62 to page 63) Default Payload Number Encoding Name Coder "X-G727_40_16" G727_40_16 "X-G727_40_24" G727_40_24 "X-G727_40_32" G727_40_32 "X-NETCODER",“NETCODER“, NetCoder_4_8 “NETCODER_4_8” "X-NETCODER",“NETCODER_5_6” NetCoder_5_6 "X-NETCODER", “NETCODER_6_4”...
Page 64: Supported Mgcp Packages
Mediant 2000 5.2.8 Supported MGCP Packages Events and signals are grouped in packages. Each package supports several events and signals. The TrunkPack series MGCP client supports LINE, DTMF, Fax Package Definition, Media Format Parameter Package, Extended line package, Announcement package, Trunk, Hand Set Emulation and Generic packages.
Page 65: Dtmf Package - D
Mediant 2000 Standard Control Protocols 5.2.8.2 DTMF Package - D Table 5-4: DTMF Package - D Symbol Definition Duration DTMF 0 DTMF 1 DTMF 2 DTMF 3 DTMF 4 DTMF 5 DTMF 6 DTMF 7 DTMF 8 DTMF 9 DTMF #...
Page 66: Handset Emulation Package - H
Mediant 2000 Table 5-5: Line Package - L (continues on page 65 to page 66) Symbol Definition Duration Ringing 180 sec Confirmation tone Report on completion of TO wt, wt1, Call waiting tones wt2,wt3,wt4 ci (ti,nu,na) Caller ID (ci(time, number, name) Time = MM/DD/HH/MN sup(addr(“digits”)
Page 67: Trunk Package - T
Mediant 2000 Standard Control Protocols 5.2.8.5 Trunk Package - T Table 5-7: Trunk Package - T Duration/ Symbol Definition Comment Continuity tone 2 seconds Continuity test 2 seconds Loopback Supported via ‘Connection Mode’ Old milliwatt tone New milliwatt tone Reorder tone...
Page 68: Announcement Package - A
Mediant 2000 Table 5-8: PacketCable (NCS) Line Package - L (continues on page 67 to page 68) Symbol Definition Duration/Comment Reorder tone 180 seconds Ring back tone 30 seconds Stutter dial tone C,TO 180 seconds wt, wt1, wt2, wt3, Call waiting tones...
Page 69 Mediant 2000 Standard Control Protocols If the user does not utilize the event parameters, defaults could be set through ini file: timeout - "BrokenConnectionEventTimeOut". Default value is 300 msec. Parameter can be changed in 100 msec steps. Start-time - "BrokenConnectionEventActivationMode". Default value is 1- start after first incoming rtcp packet.
Page 70: Cas Package - Ms
Mediant 2000 5.2.8.9 CAS Package - MS Table 5-11: CAS Package - MS Symbol Definition Duration/Comment Call answer Block Busy Tone Information Digits Operation complete Operation fail Release call Resume call Release complete Reorder tone Ring back tone Call setup Suspend call 5.2.8.10...
Page 71: Isup Trunk Package - It
TO,C Time-out = 180 seconds 5.2.8.12 Media Format Parameter Package - FM Supported FMTP Formats According to the Media Format Parameter Package, AudioCodes supports the following FMTP formats: L:a:codec1;codec2, fmtp:"codec1 formatX", fmtp:"codec2 formatY" L:a:codec1;codec2, fmtp:"codec1 formatX";"codec2 formatY" L:a:codec1;codec1, fmtp:"codec1 formatX"...
Page 72: Fax Package Definition - Fxr
Mediant 2000 NetCoder Family fmtp: “NETCODER mode-set=0” (bitrate=4.75) fmtp: “NETCODER mode-set=1” (bitrate=5.15) fmtp: “NETCODER mode-set=2” (bitrate=5.9) fmtp: “NETCODER mode-set=3” (bitrate=6.7) fmtp: “NETCODER mode-set=4” (bitrate=7.4) fmtp: “NETCODER mode-set=5” (bitrate=7.95) fmtp: “NETCODER mode-set=6” (bitrate=10.2) G729 Family fmtp: “G729 annexb=yes” (VAD on - Voice Activity Detection on) fmtp: “G729 annexb=no”...
Page 73: V5 Package Definition X-V5
Mediant 2000 Standard Control Protocols 5.2.8.14 V5 Package Definition X-v5 Table 5-15: V5 Package Definition Duration/ Symbol Definition Comment Wink signal Line polarity reversal Infinite 5.2.9 MGCP Endpoint Map The Endpoint Name is a combination of the TrunkName (a string of up to 19 characters)
Page 74: Operation
Mediant 2000 Since this is a standards-based control protocol, AudioCodes does not provide any special software library to enable users to construct their own Call Agent. (Users can choose any of many such stacks are available in the market.) Note: MGCP and MEGACO protocols cannot coexist on the same device.
Page 75: Setting Megaco Call Agent Ip Address And Port
Authorization Check of Call Manager IP Addresses While the MEGACO specification specifies that only one Call Manager can send commands to the gateway at a time, AudioCodes gateways handle the Authorization Check in either of these modes: No authorization check is performed. This mode specifies that every command is accepted and executed.
Page 76: Playing Signals
Mediant 2000 An event can have an embedded descriptor in it. It can be a SignalsDescriptor (refer to Section 5.3.2.7), a new EventDescriptor, or both. The embedded descriptor replaces the current descriptor. 5.3.2.7 Playing Signals Signals in MEGACO reside in a SignalsDescriptor. Only one signal is allowed in the descriptor as the devices cannot play more than one signal at a time.
Page 77: Mediation
Mediant 2000 Standard Control Protocols O-N=gws0c1{ OE=1001{19700101T00003542: g/sc{ Meth=TO,SigId=an/apf,SLID=1234}}}}} 5.3.2.8 Mediation Mediation in MEGACO connects two ephemeral terminations. This operation can be used by a Call Agent to connect users with different coders or to connect two types of users, such as ATM and RTP.
Page 78: Cas/R2 Support In Megaco
Using the Basic CAS Package (refer to Section 5.3.4.17 on page 90) and the R2 CAS Package (refer to Section 5.3.4.18 on page 90), AudioCodes' device converts MFCR2 protocol - which is a PSTN protocol - into MEGACO protocol, thereby bridging the PSTN world with the IP world.
Page 79: Rfc 2833 Support
Mediant 2000 Standard Control Protocols 5.3.2.10 RFC 2833 Support DTMF Transport Type can be set to use RFC 2833 through configuration or dynamically through MEGACO commands. Note: RFC 2833 support is only applicable when running Voice Over IP traffic. It is not operational on Voice over ATM.
Page 80: Fax T.38 And Voice Band Data Support (Bypass Mode)
Mediant 2000 Table 5-1 summarizes the operation of silence suppression: Table 5-16: Silence Suppression Operation CONFIG Setting G.711 G.723 G.729 ON only if: ON only if: ON only if: - a=silencesupp:on - a=silencesupp:on a=silencesupp:on - payload 13 was offered - remote SDP does not contain...
Page 81: Reporting Fax Events
Mediant 2000 Standard Control Protocols Fax redundancy can be requested by including the following attribute line after the ‘m=image’ line: a=T38FaxUdpEC:T38UdpRedundancy This parameter is only applicable for non-V21 packets. For V21 packets, the redundancy is hard coded 4. Two modes of fax support are available. The modes are chosen by the value of bit 2 (value 4) of the MEGACO profiling parameter MGCPCompatibilityProfile.
Page 82: Mapping Payload Numbers To Coders
Mediant 2000 RTPMAP Used for dynamic payload mapping, to map the number to the coder. The format is: a=rtpmap: 97 G723/8000/1 Where: 97 is the payload number to be used G723 is the encoding name 8000 is the clock rate (optional)
Page 83 Mediant 2000 Standard Control Protocols Table 5-17: MEGACO Mapping Payload Numbers to Coders (continues on page 82 to page 84) Default Payload Number Encoding Name Coder "G726-40" G726_40 "X-G727-16" G727_16 "X-G727-24-16" G727_24_16 "X-G727-24" G727_24 "X-G727-32-16" G727_32_16 "X-G727-32-24" G727_32_24 "X-G727-32" G727_32 "X-G727-40-16"...
Page 84: Supported Megaco Packages
Mediant 2000 Table 5-17: MEGACO Mapping Payload Numbers to Coders (continues on page 82 to page 84) Default Payload Number Encoding Name Coder “RED” Redundancy per RFC 2198 “CN” Comfort Noise Note: When using dynamic payloads, do not use the device default payloads for RFC 2833 (96) and RFC 2198 (104).
Page 85: Base Root Package - Root
Mediant 2000 Standard Control Protocols 5.3.4.2 Base Root Package - ROOT Table 5-19: Base Root Package - ROOT Symbol Definition Type maxNumberOfContexts Maximum number of Contexts in the Property device maxTerminationsPerContext Maximum Terminations in a Context Property normalMGExecutionTime Timer for Retransmission...
Page 86: Dtmf Detection Package - Dd (Extends Tonedet)
Mediant 2000 Table 5-22: DTMF Generator Package - DG (continues on page 85 to page 86) Symbol Definition Type Duration DTMF 9 Signal DTMF * Signal DTMF # Signal DTMF A Signal DTMF B Signal DTMF C Signal DTMF D Signal 5.3.4.6...
Page 87: Call Progress Tones Generator Package - Cg (Extends Tonegen)
Mediant 2000 Standard Control Protocols 5.3.4.7 Call Progress Tones Generator Package - CG (Extends ToneGen) Table 5-24: Call Progress Tones Generator Package - CG Map to Symbol Definition Type Duration CPT File Dial tone Signal 180 sec Ringing tone Signal...
Page 88: Network Package - Nt
Mediant 2000 5.3.4.10 Network Package - NT Table 5-27: Network Package - NT Symbol Definition Type Maximal jitter buffer size Property netfail Network failure Event qualert Quality alert - Not supported Event Termination’s InContext duration Statistics Octets sent Statistics Octets received Statistics 5.3.4.11...
Page 89: Expanded Call Progress Tones Generator Package - Xcg (Extends - Tonegen)
Mediant 2000 Standard Control Protocols 5.3.4.14 Expanded Call Progress Tones Generator Package - XCG (Extends - ToneGen) Table 5-31: Expanded Call Progress Tones Generator Package - XCG Map to Symbol Definition Type Duration CPT File cmft Comfort tone Signal 180 sec...
Page 90: Basic Cas Package - Cas
Mediant 2000 5.3.4.17 Basic CAS Package - CAS Table 5-34: Basic CAS Signal/Events Map to Symbol Definition Type Duration CPT File Symbol Seizure Signal/ Event None Answer Signal/ Event None Clear forward Signal/ Event None Clear back Signal/ Event None...
Page 91: Mf Detection Package - Mfd (Extends - Tonedet)
Mediant 2000 Standard Control Protocols Table 5-36: MF Generator Package - MFG (continues on page 90 to page 91) Symbol Definition Type Duration MF E Signal MF F Signal MF G Signal MF H Signal 5.3.4.20 MF Detection Package - MFD (Extends - ToneDet)
Page 92: Basic Call Progress Tones Generator With Directionality Package - Bcg (Extends Tonegen)
Mediant 2000 5.3.4.22 Basic Call Progress Tones Generator with Directionality Package - BCG (Extends ToneGen) Table 5-39: Basic Call Progress Tones Generator with Directionality Package - BCG Map to Symbol Definition Type Duration DPT File Dial tone Signal 180 sec...
Page 93: Megaco Profiling
Mediant 2000 Standard Control Protocols 5.3.5 MEGACO Profiling Profiling of various MEGACO features is controlled via the ini file parameter MGCPCompatibilityProfile. Initially, only value 2 has been supported. (Values 0 and 1 are obsolete). 2 is the default value, and it is for supporting MEGACO version 1. Additional features are: Bit 2 (Value 4) -Controls the type of support for the Fax T.38 negotiation.
Page 94: Old Termination Naming Method
Note also that for trunking gateways, the ‘TrunkName’ can NOT be null. The default values for the Termination name parts depend on the device type: For Analog boards - (such as those used in AudioCodes’ analog Media Gateways, e.g., MP-104, MP-108, and MP-124), the default gateway name is Null, the trunk name is not used, and the endpoint name is ‘line/’.
Page 95: Table 5-42: Megaco Endpoint Names (Continues On Page 95 To
Mediant 2000 Standard Control Protocols Table 5-42 lists only the names for a two trunks unit. Table 5-42: MEGACO Endpoint Names (continues on page 95 to page 96) E1 - PRI/CAS E1 - T1 - CAS Endpoint Name E1 - Transparent...
Page 96 Mediant 2000 Table 5-42: MEGACO Endpoint Names (continues on page 95 to page 96) E1 - PRI/CAS E1 - T1 - CAS Endpoint Name E1 - Transparent Transparent 62 T1 - PRI T1 - Transparent Acgw/T1/C3 Trunk#1/Trunk#1/ Trunk#1/Trunk#1/ Trunk#1/Trunk#1/ Trunk#1/Trunk#1/...
Page 97: Device Management
MIB variables and their usage. The Mediant 2000 contains an embedded SNMP Agent supporting both general network MIBs (such as the IP MIB), VoP-specific MIBs (such as RTP) and AudioCodes' proprietary MIBs (AcBoard, acGateway, AC-ALARM-MIB and other MIBs) enabling a deeper probe into the inter-working of the Gateway.
Page 98: Snmp Mib Objects
Mediant 2000 Each of these message types fulfills a particular requirement of network managers: Get Request - Specific values can be fetched via the "get" request to determine the performance and state of the device. Typically, many different values and parameters can be determined via SNMP without the overhead associated with logging into the device, or establishing a TCP connection with the device.
Page 99: Snmp Extensibility Feature
The ALARM-MIB is currently a draft standard and therefore, has no OID assigned to it. In the current software release, the MIB is rooted in the AudioCodes experimental MIB subtree. In a future release, after the MIB has been ratified and an OID assigned to it, AudioCodes will move to the official OID.
Page 100: Alarm History
The media server performance measurements is provided by two AudioCodes MIBs (acPerfMediaGateway and acPerfMediaServices). The first MIB is generic-type of PM MIB that is available on all AudioCodes devices. The second PM MIB is media server specific. The generic PM MIB covers:...
Page 101: Trunkpack-Vop Series Supported Mibs
MASK-MIB. These MIBs are used in configuration of SNMPv2c community strings and trusted managers. In addition to the standard MIBs, the complete AudioCodes series contains several AudioCodes proprietary MIBs: AcBoard MIB - This AudioCodes proprietary MIB contains objects related to configuration of the board and channels as well as to run-time information.
Page 102 ATM related parameters. acAtmStatus - for the Status of ATM connections. AcAlarm - This is AudioCodes' proprietary carrier grade alarm MIB. It is a simpler implementation of the notificationLogMIB and the IETF suggested alarmMIB (both also supported in all AudioCodes boards).
Page 103: Snmp Interface Details
Mediant 2000 Device Management acBoardConfigurationError - Sent when a board's settings are illegal - the trap contains a message stating/detailing/explaining the illegality of the setting. acBoardFatalError - Sent whenever a fatal board error occurs. acFeatureKeyError - Development pending. Intended to relay Feature Key errors etc.
Page 104: Snmp Community Names
Mediant 2000 6.1.6.1 SNMP Community Names By default, the board uses a single, read-only community string of "public" and a single read-write community string of "private". One can configure up to 5 read-only community strings and up to 5 read-write community strings, and a single trap community string is supported: 6.1.6.1.1 Configuration of Community Strings via the ini File...
Page 105: Trusted Managers
Mediant 2000 Device Management To change the trap community string, take these 2 steps: The following procedure assumes that a row already exists in the srCommunityTable for the new trap community string. The trap community string can be part of the TrapGroup, ReadGroup or ReadWriteGroup.
Page 106: Snmp Ports
Mediant 2000 To add a subsequent Trusted Manager, take these 2 steps: The following procedure assumes that there is at least one configured read-write community. There are currently one or more Trusted Managers. The taglist for columns for all rows in the srCommunityTable are currently set to MGR. This procedure must be done from one of the existing Trusted Managers.
Page 107: Multiple Snmp Trap Destinations
SNMP PDU. 6.1.6.4.1 Configuration via the ini File In the AudioCodes board ini file, parameters below can be set to enable or disable the sending of SNMP traps. Multiple trap destinations can be supported on the media server by setting multiple trap destinations in the ini file.
Page 108 Mediant 2000 ; To configure one of the rows, uncomment all 4 lines in that ;block. Supply an IP address and if necessary, change the port ;numer. ; To delete a trap destination, set ISUSED to 0. ; -change these entries as needed ;SNMPMANAGERTABLEIP_0=...
Page 109: Snmp Manager Backward Compatibility
6.2.1 Node Maintenance Node maintenance for the AudioCodes Media Server is provided via an SNMP interface. The acBoardMIB provides two parameters for graceful and forced shutdowns of the AudioCodes Media Server. (Refer to the note is Section 6.2.2 below.) These parameters are in the acBoardMIB as acgwAdminState and acgwAdminStateLockControl.
Page 110: Graceful Shutdown
AudioCodes’ Embedded Web Server AudioCodes' boards and modules contain an Embedded Web Server to be used for device configuration and for run-time monitoring. AudioCodes' Embedded Web Server enables users equipped with any standard Web-browsing application such as Microsoft™ Internet Explorer™...
Page 111: Embedded Web Server Protection & Security Mechanisms
Mediant 2000 Device Management 6.3.1 Embedded Web Server Protection & Security Mechanisms Access to the Embedded Web Server is controlled by the following protection and security mechanisms: Username and Password - Refer to Section 6.3.1.1 below Limiting the Web Server GUI to Read-Only Mode - Refer to Section 6.3.2.1 below Disabling the Web Server GUI - Refer to Section 6.3.2.2 on page 111...
Page 112: Correlating Pc /Mediant 2000 Ip Address & Subnet Mask
6.3.3 Correlating PC /Mediant 2000 IP Address & Subnet Mask Before using the Web browser to access the Mediant 2000 device’s Embedded Web Server, change the PC’s IP address and Subnet Mask to correspond with the Mediant 2000’s factory default IP address and Subnet Mask shown in Table 6-1. For details on changing the IP address and Subnet Mask, refer to the Help information provided by the Operating System used.
Page 113: Using Internet Explorer To Access The Embedded Web Server
Mediant 2000 Device Management Figure 6-1: Enter Network Password Screen 6.3.5 Using Internet Explorer to Access the Embedded Web Server Internet explorer's security settings may block access to the Gateway's Web browser if they're configured incorrectly. If this happens, the following message appears: Unauthorized Correct authorization is required for this area.
Page 114: Getting Acquainted With The Web Interface
Mediant 2000 Getting Acquainted with the Web Interface 6.4.1 About the Web Interface Screen Figure 6-2 is an example of the General layout of the Web Interface screen. Figure 6-2: Web Interface Screen - Example Main Action Frame Sub-menu Bar...
Page 115: Saving Changes
Mediant 2000 Device Management Save Configuration - Use this menu to save configuration changes to the non-volatile flash memory. Reset - Use this menu to remotely reset the device. Note: When positioning your curser over a parameter name for more than 1 second, a short description of this parameter is displayed.
Page 116: Figure 6-3: Quick Setup Screen
Mediant 2000 Figure 6-3: Quick Setup Screen Step 4. In the Quick Setup screen, enter or modify appropriate information for the IP Configuration, Trunk Configuration and Control Protocol (per type). Step 5. In the IP Configuration section, IP Address and Subnet Mask fields, enter the appropriate addresses, which must correspond with your network IP Address settings.
Page 117: Protocol Management
Step 12. For the Call Agent Domain Name field, when using the DNS server option, enter the Domain Name of the Call Agent operating with the Mediant 2000. The DNS server automatically detects the Call Agent’s IP address from the Domain Name.
Page 118: Figure 6-4: Mgcp Protocol Definition Screen
Mediant 2000 Figure 6-4: MGCP Protocol Definition Screen Figure 6-5: MEGACO Protocol Definition Screen Step 3. From the Control Protocol Type dropdown list, select the appropriate option. The parameter fields are modified accordingly. Step 4. Use Table 7-7 on page 173 and Table 7-8 on page 175 as a reference when configuring/modifying the MGCP or MEGACO parameters in the Protocol Definition screen.
Page 119: Advanced Configuration Screen
Mediant 2000 Device Management Step 5. After configuring/modifying the parameter fields, click the SUBMIT button. The changes are entered into the system and the screen is refreshed. 6.4.4 Advanced Configuration Screen To access the Advanced Configuration screen take this step: To access the device’s advanced configuration parameters, from the main menu list on...
Page 120: Channel Settings
Mediant 2000 Figure 6-7: Network Settings Screen Step 3. Use Table 7-1 on page 146 as a reference when configuring/modifying the network parameter fields in the Network Settings screen. Step 4. After configuring/modifying the parameter fields, click the SUBMIT button. The changes are entered into the system and the screen is refreshed.
Page 121: Figure 6-8: Channel Settings Screen
Mediant 2000 Device Management Figure 6-8: Channel Settings Screen Version 4.4 Beta June 2004...
Page 122: Trunk Settings
Mediant 2000 Step 3. Use Table 7-3 on page 152 as a reference when configuring/modifying the channel parameter fields in the 'Channel Settings' screen. Step 4. After configuring/modifying the parameter fields, click the SUBMIT button. The changes are entered into the system and the screen is refreshed.
Page 123: Table 6-2: Trunk Status Color Indicator Key
Side as “User side” when the PSTN or PBX side is configured as “Network side”, and vice versa. If you do not know the Mediant 2000 ISDN termination side, choose “User side” and refer to the Status & Diagnostics screen. If the D-channel alarm is indicated, choose “Network side”.
Page 124: Figure 6-10: Q931 Bit Map Screen
Mediant 2000 Figure 6-10: Q931 Bit Map Screen Step 7. For the Clock Master (the trunk clock source) drop-down list, select either ‘Recovered’ (the clock is recovered from the trunk; default) or ‘Generated’ (the trunk clock source is provided by the internal/TDM bus clock source) the above selection depends on the parameter ‘TDM Bus Clock Source’.
Page 125: Tdm Bus Settings
Mediant 2000 Device Management Step 11. Click the Save button. The configuration is saved to Flash memory. Note 1: A device reset may be needed in certain circumstances for the setup to be acti- vated, if a reset is needed the Web interface will alert the user. In case such a...
Page 126: Configuration File
The ini file with parameters set at their default values is on the CD accompanying the device. The ini file can also be received as an e-mail attachment from AudioCodes' Technical Support. Users can also generate their own ini file using AudioCodes' DConvert utility (refer to Appendix E on page 237).
Page 127: Regional Settings
Mediant 2000 Device Management Figure 6-12: Configuration File Screen Step 3. Click the Get ini File button. You are prompted to select a location in which to save it. Note: The ini file that you save from the device to the PC contains only those parameters whose values you modified following receipt of the device.
Page 128: Figure 6-13: Regional Settings Screen - Sending Cpt, Cas And/Or Voice Prompt File To The Device
The files are available on the CD accompanying your device. They can also be received as an e-mail attachment from AudioCodes' Technical Support. A Call Progress Tones txt file can be modified and converted into the binary dat file (refer to Figure E-2, on page 238).
Page 129: Change Password
To reset the username and password to their defaults: Set the ini file parameter ResetWebPassword to 1 and use AudioCodes' BootP/TFTP Server to load the ini file to the device (refer to Appendix A on page 211). After loading, the username and password automatically revert to their default values (Admin).
Page 130: Status And Diagnostic Menu
Mediant 2000 6.4.5 Status and Diagnostic Menu To access the Status and Diagnostics menu, Take this step: From the main menu list on the left, click on the Status and Diagnostics link. The Status and Diagnostics screen with the sub-menu bar on the top is displayed.
Page 131: Figure 6-16: Trunk And Channel Status Screen
Mediant 2000 Device Management Figure 6-16: Trunk and Channel Status Screen The number of trunks and channels that appear on the screen depends of the system configuration. The Trunk and Channel Status indicators can appear colored. Table 6-3 shows the possible indicators and their descriptions.
Page 132: Figure 6-17: Channel Status Screen
Mediant 2000 Step 3. To display a screen with a summary of parameter information relevant to a channel, click on the channel. The following 'per channel' screen information is available when clicking on a specific channel: Figure 6-17: Channel Status Screen Figure 6-18: RTP/RTCP Settings Screen User’s Manual...
Page 133: Figure 6-19: Fax & Modem Settings Screen
Mediant 2000 Device Management Figure 6-19: Fax & Modem Settings Screen Figure 6-20: Transport Settings Screen Figure 6-21: Voice Settings Screen Figure 6-22: IBS Detector Settings Screen Version 4.4 Beta June 2004...
Page 134: Message Log
Similarly, AudioCodes does not recommend keeping a Message Log session open for a prolonged period (refer to the Note below). For logging of errors and warnings, refer to Section 8.1.1.4 on page 201.
Page 135: Versions
The Versions screen displays hardware and software product information. This information can help you to expedite any troubleshooting process. Capture the screen and email it to AudioCodes' Technical Support personnel to ensure quick diagnosis and effective corrective action. The screen also displays any loaded files in the device.
Page 136: Software Update
Mediant 2000 6.4.6 Software Update The Software Update screen offers two options for downloading current software update files: the Software Upgrade Wizard and Load Auxiliary Files screen. In addition, the License screen is provided for users to enter their updated license keys.
Page 137: Figure 6-27: Start Software Upgrade Screen
Mediant 2000 Device Management Step 2. From the main menu list on the left, click on the Software Update link. The Software Upgrade screen with the sub-menu bar on the top is displayed. Step 3. On the sub-menu bar on the top, click the Software Upgrade Wizard link. The Start Software Upgrade screen appears.
Page 138: Figure 6-29: File Loading Dialog Screen
Mediant 2000 Note the file type list in the left side of the screen. This list contains the relevant file types that can be loaded via the wizard for this device type (Analog, Digital, FXO, FXS, etc.). The highlighted file type in the file type list indicates which file type is being displayed in the main part of the screen.
Page 139: Figure 6-30: File Loading Dialog Screen - Cpt Type Displayed
Mediant 2000 Device Management Figure 6-30: File Loading Dialog Screen - CPT Type Displayed Step 9. Completing the Software Upgrade Process From any of the file type screens, you can complete the Software Upgrade process by clicking the Reset button. The device is reset utilizing the new files you have loaded up to that point.
Page 140: Auxiliary Files Download
The Auxiliary Files Download screen facilitates the download of software updates using the HTTP protocol. Types of software file updates include: ini - Download the file to provision the Mediant 2000 parameters. The Embedded Web Server enables practically full Mediant 2000 provisioning, but customers may occasionally require new feature configuration parameters, in which case this file is downloaded.
Page 141: License
Mediant 2000 Device Management To download an auxiliary file, take these 5 steps: Step 1. From the main menu list on the left, click on the Software Download link. The Software Download screen is displayed. Step 2. From the sub-menu bar on the top, click the Auxiliary Files Download link. The Auxiliary Files Download screen appears.
Page 142: Save Configuration
Mediant 2000 Figure 6-34: License Screen Step 3. In the New Key field, enter the updated license key supplied by AudioCodes. Step 4. Click the Add Key button. The new key information overwrites the previous key installed on the computer.
Page 143: Reset Button
Mediant 2000 Device Management To use the Save Configuration screen, take these 2 steps: Step 1. From the main menu list on the left, click on the Save Configuration link. The Save Configuration screen is displayed. Figure 6-35: Save Configuration Dialog Screen Step 2.
Page 144 Mediant 2000 Step 3. Click the Restart Button. If the Burn option is selected, all of the changes made to the configuration are saved to the Flash memory of the device. If the Don’t Burn option is selected, all of the changes made to the configuration are discarded.
Page 145: Configuration Parameters And Files
After first-time startup, the configuration can be uploaded from the device and saved to your PC hard disk as an ini file (using AudioCodes' Embedded Web Server. Refer to Section 6.3 on page 110). This ini file can be opened in any text file editor, modified and reloaded to the device using AudioCodes' BootP/TFTP Server (refer to Appendix A, on page 211).
Page 146: System Parameters
Mediant 2000 Array Parameters Some parameters have array values. For each of these parameters listed in the parameter tables below, if the ini file field name is used as is, the parameter applies to all of its elements. To specify each element individually, add _xx (xx equals the element number) to the end of the ini file field name.
Page 147: Infrastructure Parameters
BootPSelectiveEnable 0 or 1 The Board will only accept BootP replies only from AudioCodes proprietary BootP/TFTP Software. 1 = Enable, 0 = Disable. DisableNetRefOn 0 or 1 1 = Disables the NetRef signal when PSTN TrunkFailure reference trunk fails.
Page 148 Mediant 2000 Table 7-2: Infrastructure Parameters (continues on page 147 to page 151) Host/Manual ini File Field Name Default Value Valid Range Description EnableIPAddr 0 or 1 Relevant to NAT. Translation This parameter specifies the type of compare operation performed on the first packet that is received on a newly opened channel for the NAT feature.
Page 149 Mediant 2000 Configuration Parameters and Files Table 7-2: Infrastructure Parameters (continues on page 147 to page 151) Host/Manual ini File Field Name Default Value Valid Range Description ForceExceptionDump 0 or 1 Force exception dump sends last software exception dump each time board restarts.
Page 150 Mediant 2000 Table 7-2: Infrastructure Parameters (continues on page 147 to page 151) Host/Manual ini File Field Name Default Value Valid Range Description TDMBusClockSource 1 to 14 Selects the clock source on which the board synchronizes. 1 = local oscillator...
Page 151 Mediant 2000 Configuration Parameters and Files Table 7-2: Infrastructure Parameters (continues on page 147 to page 151) Host/Manual ini File Field Name Default Value Valid Range Description TDMBusNetRef 0 to 3 Selects the Netref Output functionality. OutputMode 0 = Do not output any NetRef,...
Page 152: Media Processing Parameters
Mediant 2000 7.1.3 Media Processing Parameters Table 7-3 lists and describes the Media Processing parameters contained in the ini file. Use this table as a reference when modifying ini file parameter values. Table 7-3: Media Processing Parameters (continues on page 152 to page 157)
Page 153 Mediant 2000 Configuration Parameters and Files Table 7-3: Media Processing Parameters (continues on page 152 to page 157) Host/Manual ini File Field Name Default Value Valid Range Description CASTransportType 0 or 1 Controls the ABCD Signaling transport type over IP.
Page 154 Mediant 2000 Table 7-3: Media Processing Parameters (continues on page 152 to page 157) Host/Manual ini File Field Name Default Value Valid Range Description ECHybridLoss 0 = 6 dBm 0 to 3 Sets worst case ratio between signal level transmitted to hybrid & echo level returning from hybrid.
Page 155 Mediant 2000 Configuration Parameters and Files Table 7-3: Media Processing Parameters (continues on page 152 to page 157) Host/Manual ini File Field Name Default Value Valid Range Description FaxModemBypass 0 to 3 Sets the basic Fax / Modem bypass RTP...
Page 156 Mediant 2000 Table 7-3: Media Processing Parameters (continues on page 152 to page 157) Host/Manual ini File Field Name Default Value Valid Range Description InputGain 0 = No Gain -32 to +31 PCM input gain. The range is -32 dB to +31 dB in 1 dB steps.
Page 157 Mediant 2000 Configuration Parameters and Files Table 7-3: Media Processing Parameters (continues on page 152 to page 157) Host/Manual ini File Field Name Default Value Valid Range Description RFC2833TxPayload 96 to 127 Controls the RFC 2833 Tx Relay RTP Type...
Page 158: Pstn Parameters
Mediant 2000 7.1.4 PSTN Parameters Table 7-4 lists and describes the PSTN parameters contained in the ini file. Use this table as a reference when modifying ini file parameter values. Table 7-4: PSTN Parameters (continues on page 158 to page 165)
Page 159 Mediant 2000 Configuration Parameters and Files Table 7-4: PSTN Parameters (continues on page 158 to page 165) Host/Manual ini File Field Name Default Value Valid Range Description DisableTrunkAfter 0 or 1 An array value. Reset The number of elements equals the number of Trunks.
Page 160 Mediant 2000 Table 7-4: PSTN Parameters (continues on page 158 to page 165) Host/Manual ini File Field Name Default Value Valid Range Description ISDNGeneral See Manual An array value. CCBehavior LTRT-84001 The number of elements equals the number of Trunks.
Page 161 Mediant 2000 Configuration Parameters and Files Table 7-4: PSTN Parameters (continues on page 158 to page 165) Host/Manual ini File Field Name Default Value Valid Range Description ISDNOutCalls See Manual An array value. Behavior LTRT-84001 The number of elements equals the number of Trunks.
Page 162 Mediant 2000 Table 7-4: PSTN Parameters (continues on page 158 to page 165) Host/Manual ini File Field Name Default Value Valid Range Description LineBuildOut. 0 to 255 An array value. XPM0 The number of elements equals the number of Trunks.
Page 163 Mediant 2000 Configuration Parameters and Files Table 7-4: PSTN Parameters (continues on page 158 to page 165) Host/Manual ini File Field Name Default Value Valid Range Description NFASGroup 0 to 4 An array value. Number The number of elements equals the number of Trunks.
Page 164 Mediant 2000 Table 7-4: PSTN Parameters (continues on page 158 to page 165) Host/Manual ini File Field Name Default Value Valid Range Description ProtocolType E1_AUSTEL_ISDN = 17 (continued from E1_HKT_ISDN = 18 above) E1_KOR_ISDN = 19 T1_HKT_ISDN = 20 E1_QSIG = 21...
Page 165: Ss7 Parameters
Mediant 2000 Configuration Parameters and Files Table 7-4: PSTN Parameters (continues on page 158 to page 165) Host/Manual ini File Field Name Default Value Valid Range Description TraceLevel 0 to 15 An array value. The number of elements equals the number of Trunks.
Page 166 Mediant 2000 Table 7-5: SS7 Parameters (continues on page 165 to page 169) Host/Manual ini File Field Name Default Value Valid Range Description SS7_MTP2_Param_ 0 to 10 An array value. AERM_TIE The number of elements equals the number of MTP parameter tables.
Page 167 Mediant 2000 Configuration Parameters and Files Table 7-5: SS7 Parameters (continues on page 165 to page 169) Host/Manual ini File Field Name Default Value Valid Range Description SS7_MTP2_Param_ 0 to 256 An array value. Octet_Counting_xx The number of elements equals the number of MTP parameter tables.
Page 168 Mediant 2000 Table 7-5: SS7 Parameters (continues on page 165 to page 169) Host/Manual ini File Field Name Default Value Valid Range Description SS7_MTP2_Param_ 8200 0 to 15000 An array value. Timer_T4N The number of elements equals the number of MTP parameter tables.
Page 169 Mediant 2000 Configuration Parameters and Files Table 7-5: SS7 Parameters (continues on page 165 to page 169) Host/Manual ini File Field Name Default Value Valid Range Description SS7_SLI_MTP2_ 0 to 3 An array value. Param_Index The number of elements equals the number of SS7 links.
Page 170: Parameters Common To All Control Protocols
Mediant 2000 7.1.6 Parameters Common to All Control Protocols Table 7-6 lists and describes the parameters, contained in the ini file, that are common to all call control protocols. Use this table as a reference when modifying ini file parameter values.
Page 171 Mediant 2000 Configuration Parameters and Files Table 7-6: Control Protocol Parameters (continues on page 170 to page 172) Host/Manual ini File Field Name Default Value Valid Range Description EndpointPrefix default ="" String[19] MGCP: Together with 'TrunkName' field generates local endpoint name on trunk...
Page 172 Mediant 2000 Table 7-6: Control Protocol Parameters (continues on page 170 to page 172) Host/Manual ini File Field Name Default Value Valid Range Description MGCPRetransmission 200 msec 0 to 10000 Sets initial time for first retransmission. The Timeout msec Retransmission intervals thereafter increase exponentially.
Page 173: Mgcp-Specific Parameters
Mediant 2000 Configuration Parameters and Files 7.1.7 MGCP-Specific Parameters Table 7-7 lists and describes the MGCP-specific parameters contained in the ini file. Use this table as a reference when modifying ini file parameter values. Table 7-7: MGCP-Specific Parameters (continues on page 173 to page 174)
Page 174 Mediant 2000 Table 7-7: MGCP-Specific Parameters (continues on page 173 to page 174) Host/Manual ini File Field Name Default Value Valid Range Description MGCPVersion "MGCP 1.0" String[39] MGCP protocol version MGHistoryBufferTime 0 & > 0. The time a transaction is kept in the history...
Page 175: Megaco-Specific Parameters
Mediant 2000 Configuration Parameters and Files 7.1.8 MEGACO-Specific Parameters Table 7-8 lists and describes the MEGACO-specific parameters contained in the ini file. Use this table as a reference when modifying ini file parameter values. Table 7-8: MEGACO-Specific Parameters (continues on page 175 to page 177)
Page 176 Mediant 2000 Table 7-8: MEGACO-Specific Parameters (continues on page 175 to page 177) Host/Manual ini File Field Name Default Value Valid Range Description EP_Num Any positive An array value. number The number of elements is 5. To specify each element individually, add _xx (xx equals the element number) to the end of the ini file field name.
Page 177 Mediant 2000 Configuration Parameters and Files Table 7-8: MEGACO-Specific Parameters (continues on page 175 to page 177) Host/Manual ini File Field Name Default Value Valid Range Description MGProvisional 100 msec 0 to 20000 Provisional response timer for Media ResponseTime msec...
Page 178: Web Interface Parameters
Web interface pages) width in pixel units. UseProductName If set to 1 it will enable the userProductName string to override any AudioCodes defaults. If set to 0 userProductName string will have no effect on the product name. UseRProductName NULL...
Page 179: 7.1.10 Snmp Parameters
Mediant 2000 Configuration Parameters and Files 7.1.10 SNMP Parameters Table 7-10 lists and describes the SNMP parameters contained in the ini file. Use this table as a reference when modifying ini file parameter values. Table 7-10: SNMP Parameters (continues on page 179 to page 180)
Page 180 Mediant 2000 Table 7-10: SNMP Parameters (continues on page 179 to page 180) Host/Manual ini File Field Name Default Value Valid Range Description SNMPManagerTrap 0 or 1 An array value. SendingEnable The number of elements is 5. To specify each element individually, add _xx (xx equals the element number) to the end of the ini file field name.
Page 181: 7.1.11 Sctp Parameters
Mediant 2000 Configuration Parameters and Files 7.1.11 SCTP Parameters Table 7-11 lists and describes the SCTP parameters contained in the ini file. Use this table as a reference when modifying ini file parameter values. Table 7-11: SCTP Parameters Class Host/Manual...
Page 182: Initialization File (Ini Files)
Mediant 2000 Initialization File (ini files) 7.2.1 ini File Structure The ini file can contain any number of parameters. The ini file structure supports both Parameter = Value (refer to Section 7.2.1.1 on page 182) and Tables of Parameter Values Constructs (refer to Section 7.2.1.2 on page 183). The Figure 7-1 illustrates the general structure of the ini file for both the Parameter = Value and Tables of Parameter Values Constructs.
Page 183: About Tables Of Parameter Values
Table 7-12 and Table 7-13 below provide useful examples for reference. Note: Table 7-12 and Table 7-13 are provided as examples for the purpose of illustration only and are NOT actually implemented in AudioCodes products. Table 7-12: Table of Parameter Values Example - Remote Management Connections Index Fields: 1.
Page 184: Tables Of Parameter Value Rules In The Ini File Structure
Mediant 2000 7.2.1.2.2 Table Permissions Each field in a line has a 'permission' attribute which determines if and when the user may modify the field. There are several types of permissions: Read - The user may read the value of a field (true for all fields).
Page 185: Figure 7-2: Structure Of A Table In An Ini File
Mediant 2000 Configuration Parameters and Files Figure 7-2: Structure of a Table in an ini File ; Table: Items Table. ; Fields: Item_Name, Item_Serial_Number, Item_Color, Item_weight. ; NOTE: Item_Color is not specified. It will be given default value. [Items_Table] ; Fields declaration Format Item_Index = Item_Name, Item_Serial_Number, Item_weight;...
Page 186: Ini File Example
Mediant 2000 Note: Certain Dynamic tables may initialize a line (or more) at start-up time. If so, it is documented in the table's specific section. 7.2.1.3.3 Tables in the Uploaded ini File Tables are grouped according to the applications they configure. For example, several tables are required to configure SS7, and other tables are required to configure ATM.
Page 187: Figure 7-4: Ini File Example For Megaco
Mediant 2000 Configuration Parameters and Files Figure 7-4 shows an example of an ini file for MEGACO. Figure 7-4: ini File Example for MEGACO [MEGACO] ; List of Call agents, separated by ','. The default is the loading computer. PROVISIONEDCALLAGENTS = 10.2.1.254 ;...
Page 188: Secured Configuration File Downloading
In the ini file, you can specify the Voice Prompt/Call Progress Tone table files to be loaded to the Mediant 2000 (using TFTP). In the BootP/TFTP Server, you can specify that these files be stored in the device's non-volatile flash memory when loaded so that it won't be necessary to perform a TFTP process every time the device boots up / is reset.
Page 189: Call Progress Tones And User-Defined Tones
Mediant 2000. The Call Progress Tones are mostly used for Telephony In-Band Signaling applications (e.g. Ring Back tone) while the User-Defined Tones are general purpose tones to be defined by the user. Users can use either one of the Mediant 2000 configuration files supplied by AudioCodes, or construct their own file.
Page 190 Mediant 2000 Low Freq [Hz] - Frequency in Hertz of the lower tone component for a dual frequency tone, or the frequency of the tone for a single tone. High Freq [Hz] - Frequency in Hertz of the higher tone component for of a dual frequency tone, or zero (0) for a single tone.
Page 191: Format Of The User-Defined Tones Section
(User Defined Tones - 1) defined in the first section) using the following keys: Tone Type - refer to the acTToneType enum definition of the AudioCodes' "VoPLib API Reference Manual", Document #: LTRT-84401 Low Freq [Hz] - Frequency in Hertz of the lower tone component when a dual frequency tone or the frequency of the tone when a single tone.
Page 192: Default Template For Call Progress Tones
7.3.2.3 Default Template for Call Progress Tones The Mediant 2000 is initialized with the default Call Progress Tones configuration. To change one of the tones, edit the default call progress txt file. For example: to change the dial tone to 440 Hz only, replace the #Dial tone section in...
Page 193: Table 7-16: Call Progress Tones (Continues On Page 191 To
Mediant 2000 Configuration Parameters and Files Users can specify several tones of the same type using Tone Type definition. These additional tones are used only for tone detection. Generation of specific tone is according to the first definition of the specific tone. For example, the user can define an additional dial tone by appending the second dial tone definition lines to the tone ini file.
Page 194 Mediant 2000 Table 7-16: Call Progress Tones (continues on page 191 to page 195) [NUMBER OF CALL PROGRESS TONES] Number of Call Progress Tones=9 #Busy Tone Type=3 [CALL PROGRESS TONE #4] Low Freq [Hz]=480 High Freq [Hz]=620 Low Freq Level [-dBm]=24 (-24dBm)
Page 195: Modifying The Call Progress Tones & Sending It To The Device
Modifying the Call Progress Tones & Sending it to the Device AudioCodes supplies customers with a modifiable Call Progress Tone ini file and a non- modifiable Call Progress Tone dat binary file in the software package. Only the binary dat file can be sent to the device.
Page 196: Playing Prerecorded Tones (Prt)
AudioCodes' Embedded Web Server GUI's Auxiliary Files. (Refer to Section 6.4.6.2 on page 140.) AudioCodes' BootP/TFTP Server to send to the device the device's ini file (which simultaneously downloads the Call Progress Tone dat file, provided that the device's ini file parameter CallProgressTonesFilename is defined and provided that both files are located in the same directory.) (Refer to Appendix A, on page 211).
Page 197: Downloading The Prt Dat File
Mediant 2000 Configuration Parameters and Files 7.4.2.2 Downloading the PRT dat File Downloading the PRT dat file into the device can be done via HTTP, TFTP or VoIPLib API. For HTTP and TFTP download, refer to Section 6.4.6 on page 136. For VoIPLib API download, refer to the Playing Prerecorded Tones (PRT) section of the VoPLib User’s...
Page 198 Mediant 2000 Reader’s Notes User’s Manual Document #: LTRT-69801...
Page 199: Diagnostics & Troubleshooting
Diagnostics & Troubleshooting Syslog AudioCodes' Syslog server (refer to Figure 8-1, on page 199), now available with version 4.4 of the VoIPerfect platform, enables filtering of messages according to priority, IP sender address, time, date, etc. Customers can alternatively choose to download and use...
Page 200: Operating The Syslog Server
8.1.1.1 Sending the Syslog Messages AudioCodes' Syslog client, embedded in the firmware of the device, sends error reports/ events generated by the device application to a Syslog server, using IP/UDP protocol. There are presently five error levels reported by the Syslog client: Emergency level message: <128>sctp socket setsockopt error 0xf0 [File:sctp.cpp Line:453]...
Page 201: Activating The Syslog Client
The Embedded Web Server's 'Message Log' (Integral Syslog) The 'Message Log' screen in AudioCodes' Embedded Web Server GUI, similar to a Syslog server only integral to the web server, displays debug messages useful for debugging. For detailed information, refer to Section 6.4.5.2 on page 134. The Message Log screen is not recommended for logging of errors and warnings because errors can appear over a prolonged period of time, e.g., a device can display an error after running for a week, and...
Page 202: Mgcp/Megaco Error Conditions
MGCP/MEGACO Error Conditions When working with MGCP/MEGACO, the TP-1610 reports error conditions via AudioCodes’ Call Manager (or via a Call Manager of the customer’s choice) using the standard MGCP/MEGACO facilities, through the network interface. For more information on MGCP/MEGACO error conditions, refer to the IETF web site at URL http://www.ietf.org/...
Page 203: Solutions To Possible Problems
Mediant 2000 Diagnostics & Troubleshooting Solutions to Possible Problems 8.5.1 Possible Common Problems Solutions to possible common problems are described in Table 8-1. Table 8-1: Solutions to Possible Common Problems Problem Possible Cause Solutions Software does not Try to “ping” the board/module. If ping fails, check for network...
Page 204: Possible Voice Problems
Mediant 2000 8.5.2 Possible Voice Problems Solutions to possible voice problems are described in Table 8-2. Table 8-2: Solutions to Possible Voice Problems Problem Possible Cause Solutions G.711 voice Silence compression is not Disable it and check if the quality is better.
Page 205: Functional Specifications
Mediant 2000 Functional Specifications Functional Specifications Mediant 2000 Selected Specifications Table 9-1: Selected Specifications (continued on page 205 to page 209) Item Characteristic Channel Capacity Network Ports/DSP Calls Up to 480 (independent digital voice, fax or All media processing ports can be tied to IP-RTP, PSTN-DS0...
Page 206 Mediant 2000 Table 9-1: Selected Specifications (continued on page 205 to page 209) Item Characteristic Voice Processing All voice processing features are supported simultaneously on all ports Dynamic Network Jitter Buffer with reordered RTP packets correction Call Progress Tones generation and detection Transcoding of a G.711 RTP stream to any Low Bit-Rate Coder...
Page 207 Japan INS1500, QSIG Basic Call, Australian Telecom, New Zealand Telecom, Hong Kong Variant, Korean MIC Management Interfaces SNMP V2 Standard MIB-2, RTP MIB, Trunk MIB, AudioCodes' proprietary MIBs Embedded Web Server Enabling device configuration and run-time monitoring with an Internet browser...
Page 208 Redundant Power Supplies provide protection but are non Hot Swappable Host Interface Via cPCI bus, using AudioCodes' libraries Via Packet interface using AudioCodes’ proprietary TPNCP or standard control protocols Enclosure Dimensions 1U, 19-inch rack mount, shelf or desk top, 2-slot cPCI chassis 44.5 x 445 x 300 mm;...
Page 209: Led Indicators
Mediant 2000 Functional Specifications Table 9-1: Selected Specifications (continued on page 205 to page 209) Item Characteristic LED Indicators LED Indications on Front Panel Power, Ready/Fail T1/E1/J1 per trunk status, LAN statusSwap ready indication Connectors and Switches Rear Panel Power: (model dependent) - Standard AC power socket - DC power - MSTB2.5/2-STF (5.08mm) of Phoenix Contact...
Page 210 Mediant 2000 Reader’s Notes User’s Manual Document #: LTRT-69801...
Page 211: Appendix A Audiocodes Bootp/Tftp Server
Appendix A AudioCodes BootP/TFTP Server Introduction AudioCodes BootP/TFTP Server enables easy configuration and provisioning for AudioCodes boards and Media Gateways. The BootP and TFTP servers contain specific adaptations as per AudioCodes’ requirements. The latest version of the BootP/TFTP application is 2.3.0.5.
Page 212: Bootp/Tftp Server Installation
Client Configuration screen Template Definition screen A.1.3 BootP/TFTP Server Installation The BootP/TFTP Server can be installed on a PC from the AudioCodes Software & Documentation CD. To install the BootP/TFTP Server, take these 3 steps: Step 1. Unzip the TPxx.exe file and navigate to the BootP zip file under .\Utilities\BootP &...
Page 213: Preferences Screen
BootP replay type (Broadcast or Unicast) BootP ARP mode (dynamic or static) Number of initiated BootP replies (send after remote reset), optionally used when the AudioCodes device (e.g., TP-1610 board/module) is installed behind the firewall that blocks BootP broadcast requests. A.1.6...
Page 214: Template Screen
A.2.1 Main Screen Figure A-1: Main Screen Figure A-1 shows the main screen of the AudioCodes BootP/TFTP Server, featuring: Program State - Pauses the program. When the program is paused, no replies to BootP requests are sent. View Clients button - Opens up the Clients Configuration screen.
Page 215 Mediant 2000 AudioCodes BootP/TFTP Server Reset button - Opens a dialog, in which users can enter an IP of a client. The program sends a reset command to that client. Edit>Preferences - Opens the Preferences screen for defining BootP and TFTP parameters.
Page 216: Preferences Screen
The Number of Timed Replies (the number of initiated timed BootP replies) can be used when an AudioCodes device is installed behind a Firewall that blocks BootP broadcast requests. In a typical application, this feature can be disabled by entering 0 in this field.
Page 217: Client Configuration Screen
Mediant 2000 AudioCodes BootP/TFTP Server A.2.3 Client Configuration Screen Figure A-3 is the Client Configuration Screen in which clients are added and defined. Figure A-3: Client Configuration Screen In the left pane of the screen is the client list. By clicking on a client in this list, the following parameters for this client are displayed on the right side of the screen: Client MAC - This is the MAC address of the client.
Page 218: Templates Screen
(except for the IP address). To use the Templates screen, create a template, and then apply the template to the client by selecting it. Figure A-4: AudioCodes BootP/TFTP Templates Screen User’s Manual Document #: LTRT-69801...
Page 219: Appendix B Rtp/Rtcp Payload Types
Appendix B RTP/RTCP Payload Types Latest RTP Payload Types are defined in RFC 3551. For coders that should have dynamic Payload types, AudioCodes has defined proprietary default values out of the dynamic Payload type range. These defaults are appropriate when working with AudioCodes products only.
Page 220: Payload Types Not Defined In Rfc 3551
Mediant 2000 Payload Types Not Defined in RFC 3551 Table B-2: Payload Types Not Defined in RFC 3551 Payload Type Description Basic Packet Rate [msec] G.727 16 kbps G.727 24-16 kbps G.727 24 kbps G.727 32-16 kbps G.727 32-24 kbps G.727-32 kbps...
Page 221: Mediant 2000 Default Rtp/Rtcp/T.38 Port Allocation
Mediant 2000 RTP/RTCP Payload Types Mediant 2000 Default RTP/RTCP/T.38 Port Allocation The following table shows the Mediant 2000 default RTP/RTCP/T.38 port allocation. Table B-4: Default RTP/RTCP/T.38 Port Allocation Channel Number RTP Port RTCP Port T.38 Port 4000 4001 4002 4010...
Page 222 Mediant 2000 Reader’s Notes User’s Manual Document #: LTRT-69801...
Page 223: Appendix C Dtmf, Fax And Modem Transport Modes
Mediant 2000 DTMF, Fax and Modem Transport Modes Appendix C DTMF, Fax and Modem Transport Modes DTMF/MF Relay Settings Users can control the way DTMF/MF digits are transported to the remote Endpoint, using the DTMFTransport/MFTransport configuration parameters. The following four modes are...
Page 224: Configuring Fax/Modem Bypass Mode
Supporting V.34 Faxes Unlike the T.30 fax machines, the V.34 fax machines have no relay standard to transmit the data over IP to the remote side. Therefore AudioCodes provides the following operation modes for transporting the V.34 fax data over the IP.
Page 225: Using Bypass Mechanism For V.34 Fax Transmission
V.34 fax with its full rate. Therefore, AudioCodes recommends this setup. Also note that if CNG relay is used, in some cases, such as for manual answering machine, the fax may revert to T.30 fax with a speed of 14400 bps.
Page 226: Using Relay Mode For Various Fax Machines (T.30 And V.34)
Mediant 2000 C.6.3 Using Relay Mode for Various Fax Machines (T.30 and V.34) The user can force the V.34 fax machines to revert to T.30 and work at relay mode. Configuration: Fax transport mode - Relay Vxx modem mode - Disable CNG detectors mode - Disable In this mode, the fax events are identical to the regular T.30 fax session over T.38 protocol.
Page 227: Appendix Dcas Protocol Table
With this file, the user has full control of the CAS protocol and can define or modify any CAS protocol by writing the protocol state machine in a text file according to a few AudioCodes defined rules. To generate the protocol file, take these 5 steps: Step 1.
Page 228: States
Mediant 2000 D.2.4 States States - Each Protocol table consists of several states that it switches between during the call setup and tear-down process. Every state definition begins with the prefix ST_ followed by the state name and colons. The body of the state is composed of up to 4 unconditional performed functions and list of actions that may trigger this state.
Page 229: Reserved Words
Mediant 2000 CAS Protocol Table Note: This method is not used when working with MFC-R2 protocols. MFC-R2 uses expected number of digits defined in ProtUser_defines_xxx.h. DTMF_DIAL - Defines the On-time and Off-time for the DTMF digits generated towards the PSTN.
Page 230: State's Line Structure
Mediant 2000 State’s Line Structure Each text line in the body of each state is composed of 6 columns: action/event function parameter #1 parameter #2 parameter #3 next state Action/Event Action/event is the name of the table’s events that are the possible triggers for the entire protocol state machine.
Page 231 Mediant 2000 CAS Protocol Table Timer Oriented: EV_TIMER_EXPIRED1 - timer 1 that was previously set by table has expired. EV_TIMER_EXPIRED2 - timer 2 that was previously set by table has expired. EV_TIMER_EXPIRED3 - timer 3 that was previously set by table has expired.
Page 232 Mediant 2000 EV_MFRn_5_ STOPPED - MF digit 5 previously detected, is now stopped. EV_MFRn_6_ STOPPED - MF digit 6 previously detected, is now stopped. EV_MFRn_7_ STOPPED - MF digit 7 previously detected, is now stopped. EV_MFRn_8_ STOPPED - MF digit 8 previously detected, is now stopped.
Page 233: Function
Mediant 2000 CAS Protocol Table EV_FIRST_DIGIT - Reception of first digit out of the incoming digit string. Used in the FXO protocols, where informing the script of receiving of the first digit, enables the script to use the SEND_PROG_TON function to stop the dial tone.
Page 234 Mediant 2000 The Channel Parameter structure contains three parameters regarding sending digits. AddressVector and ANIDigitVector - These parameters are initialized when using a PlaceCall function. When the code reaches the dialing section, it sends MF digit according to the MF type specified in the MF type cell (the types are defined in CAS- Setup.h file):...
Page 235: Next State
Backward for incoming calls. MFC-R2 protocol fault could cause a channel block. In this case, the script file provided by AudioCodes releases the call to enable the User to free the call resources and be notified about being in blocking state.
Page 236 Ringback tone is actually used in all AudioCodes protocols' state machines. All other Call Progress Tones are conveyed via the acEV_TONE_DETECTED, and retrieved by the User according to their type and index (note that the Ringback tone should be defined in the Call Progress Tones table with the relevant type in order to get this event).
Page 237: Appendix E Utilities
Mediant 2000 Utilities Appendix E Utilities This section describes the functionality and operation of a list of utilities supplied with the TrunkPack software package: API Demonstration Utilities LOCATION: .\TPVoIPDemo\Debug\Gui.exe, .\VoIPSh\Debug\voipsh.exe DESCRIPTION: These utilities (supplied in source form) are designed to serve both as a reference for using the VoPLib/PSTNLib and as a demo applications which the user can run immediately after installing the board/module.
Page 238: Generating The Call Progress Tones Configuration Files
To produce a Call Progress Tones configuration file, take these 6 steps: Step 1. Construct a CPT file according to the instructions in the section on “Configuration Files Description” in AudioCodes’ “VoPLib API Reference Manual”, Document #: LTRT-84001. Step 2.
Page 239: Generating Voice Prompts Files
To generate a Voice Prompts file, take these 12 steps: Step 1. Create raw Voice Prompt files according to the instructions in the section on “Relaying DTMF/MF Digits” in AudioCodes’ “VoPLib User’s Manual”, Document #: LTRT-84401). From version 2.2, DConvert supports wav files as well. Step 2.
Page 240: Figure E-4: Select Files Window
Mediant 2000 Figure E-4: Select Files Window Step 4. Select the files from the previous step either by one of these actions: Click the Add Files button. The Add Files window appears.. Navigate to the appropriate file and click the Add>> button. (To close the Add Files window, click the Exit button.)
Page 241: Figure E-5: Voice Prompts Window With Wav Files
Mediant 2000 Utilities Figure E-5: Voice Prompts Window with wav Files Step 5. Arrange the files as desired by dragging and dropping them from one location in the list to another location. Note: The sequence of files in the Add Files window defines the Voice Prompt ID and the coder type (to be used by the acPlayVoicePrompt() function).
Page 242: Generating Cas Protocol Configuration Files
To produce CAS Protocol configuration file, take these 8 steps: Step 1. Construct the CAS protocol xxx.txt and xxx.h files according to the instructions in the sections on “Caller ID Support” and “CAS Protocol Table” in AudioCodes’ “VoPLib User’s Manual”, Document #: LTRT-84401. Step 2.
Page 243: Generating Vxml Files
Mediant 2000 Utilities Step 5. Navigate to the desired location and select the file to be converted. (This automatically designates the output file as the same name and path, but with the dat extension). Step 6. Fill in the vendor name and version number fields. If appropriate, alter the table name that is auto-generated with the selected table file name.
Page 244: Figure E-9: Prerecorded Tones File
Mediant 2000 Figure E-9: Prerecorded Tones file(s Window Step 3. Select the files from the previous step either by one of these actions: Click the Add Files button. The Add Files window appears (refer to Figure E-4, on page 240). Navigate to the appropriate file and click the Add>> button. (To close the Add Files window, click the Exit button.)
Page 245: Figure E-10: Prerecorded Tones File(S) Window With Wav Files
Mediant 2000 Utilities Figure E-10: Prerecorded Tones file(s) Window with wav Files Step 4. Select a tone type, coder and default duration for each file (select the file(s)) then double click or right click on it. The File Date window appears.
Page 246: Generating Encrypted Ini File(S)/Decrypting Ini Files
Mediant 2000 E.2.6 Generating Encrypted ini File(s)/Decrypting ini files The ini file can be both encrypted and decrypted using DConvert. Encryption usually takes place before downloading an ini file to the board while decryption usually takes place after uploading an ini file from the board.
Page 247: Pstn Trace Utilities
Mediant 2000 Utilities Encrypted ini file can be loaded using the regular ini file procedure. To upload a file from a device, use the Web Interface (refer to Section 6.4.6 on page 136). PSTN Trace Utilities LOCATION: .\Utilities\PSTN Trace Utility DESCRIPTION: These utilities are designed to convert PSTN trace binary files to text format.
Page 248: Mgcp Tester Utility
Mediant 2000 Step 7. In the Web page, set the trace level of each trunk. Step 8. Enable the trace via the Web. Step 9. Determine the UDP port (the same as in step 3). Step 10. Click the SUBMIT button. The board starts to send the trace messages.
Page 249: Megaco Tester Utility
Mediant 2000 Utilities MEGACO Tester Utility LOCATION: .\Utilities\MEGACOTester DESCRIPTION: This utility serves as a simulation for the MEGACO Call Agent. It can send any MEGACO command, as well as run complicated scripts. This utility can be used to exercise the MAGACO clients embedded in TrunkPack series boards and modules.
Page 250 Mediant 2000 Reader’s Notes User’s Manual Document #: LTRT-69801...
Page 251: Appendix F Mgcp Compliance
Mediant 2000 MGCP Compliance Appendix F MGCP Compliance The MGCP Compliance Matrix Table F-1 below summarizes the supported MGCP features respectively. The Reference column in Table F-1 refers to IETF RFC 3435 from January 2003 (which replaced RFC 2705). MGCP Compliance Matrix...
Page 252 Mediant 2000 Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) Optional connection Page 28 ID (G/rt@A3F58) Signals on/off Page 29 On/Off (OO) Time out (TO) Brief (BR) Using "+", "-"...
Page 253 Mediant 2000 MGCP Compliance Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) QuarantineHandling 3.2.2.12 page 77 Discard Process loop Events are always processed Process Events are always processed...
Page 254 Mediant 2000 Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) Synchronization of TO (Timeout) signals stop Page 36 Signalrequest action when one of the requested with detected event...
Page 255 Mediant 2000 MGCP Compliance Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) RTP security Providing Key as per RFC Page 39 2327 Type of network (IN, Local, ATM)
Page 256 Mediant 2000 Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) Encapsulated Pages 43, 45, 46, 77 Notification Request Encapsulated Endpoint Configuration Modify Connection return parameters LocalConnection Returns if local connection...
Page 257 Mediant 2000 MGCP Compliance Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) Delete Connection 2.3.6 page 51, 30 (from gateway) CallID EndPointID ConnectionID ReasonCode Connection Parameters DeleteConnection 2.3.7 page 51...
Page 258 Mediant 2000 Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) DetectEvents See connection parameters Pages 53,77 under delete connection ObservedEvents Call agent IP is defined in Page 53...
Page 259 Mediant 2000 MGCP Compliance Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) RemoteConnection Incorrect transaction id Page 56 Descriptor LocalConnection Unknown call id Page 56 Descriptor Connection 2.3.5 pages 48, 56...
Page 260 Mediant 2000 Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) The transaction could not be executed, because the endpoint is "restarting". The transaction could not be Page 59...
Page 261 Mediant 2000 MGCP Compliance Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) The Transaction refers to an Page 60 unknown call ID Unsupported or invalid mode Unsupported or unknown...
Page 262 Mediant 2000 Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) In notified entity, If Page 65 port # is omitted, using default MGCP port (2427) Response 3.2.2.1 Page 68...
Page 263 Mediant 2000 MGCP Compliance Table F-1: MGCP Compliance Matrix (continues on page 251 to page 263) Feature Support AudioCodes References Comments (to IETF RFC 3435) Responses send to source address Backup Call Agent Security, 4.2 page 96 Retransmission, Detection Commands...
Page 264 Mediant 2000 Reader’s Notes User’s Manual Document #: LTRT-69801...
Page 265: Appendix G Megaco Compliance
Mediant 2000 MEGACO Compliance Appendix G MEGACO Compliance The MEGACO Compliance Matrix Table G-1 below summarizes the supported MEGACO features. The Reference column in Table G-1 refers to IETF RFC 3015 from September 2002. MEGACO Compliance Matrix Table G-1: MEGACO Compliance Matrix (continues on page 265 to page 275)
Page 266 Mediant 2000 Table G-1: MEGACO Compliance Matrix (continues on page 265 to page 275) Reference Item Support Comments (in RFC3015) Synchronous ISDN 7.1.3 Multiplex Descriptor: H.221 H.223 H.226 V.76 7.1.4 Media Descriptor: Termination State Descriptor Stream Descriptor Local Control Descriptor...
Page 267 Mediant 2000 MEGACO Compliance Table G-1: MEGACO Compliance Matrix (continues on page 265 to page 275) Reference Item Support Comments (in RFC3015) Multiple groups 7.1.9 Event Descriptor EventBufferControl Lockstep 7.1.10 Event Buffer Descriptor 7.1.11 Signal Descriptor Signal Types On/off Timeout...
Page 268 Mediant 2000 Table G-1: MEGACO Compliance Matrix (continues on page 265 to page 275) Reference Item Support Comments (in RFC3015) ServiceChangeMGCId TimeStamp 7.1.14 Digit Map Descriptor Digit Map Names StartTimer (T) ShortTimer (S) LongTimer (L) DurationModifier (z) Any digit 0-9 (x) Zero or more repetitions (.)
Page 269 Mediant 2000 MEGACO Compliance Table G-1: MEGACO Compliance Matrix (continues on page 265 to page 275) Reference Item Support Comments (in RFC3015) EventsDescriptor SignalsDescriptor Only one signal per channel Up to 30 signals in a signal list DigitMapDescriptor AuditDescriptor 7.2.2...
Page 270 Mediant 2000 Table G-1: MEGACO Compliance Matrix (continues on page 265 to page 275) Reference Item Support Comments (in RFC3015) Event Signal DigitMap ObservedEvents EventBuffer Statistics Packages 7.2.6 Audit Capabilities TerminationID Wildcard AuditDescriptor Media Modem Event Signal DigitMap ObservedEvents EventBuffer...
Page 271: Command Error
Mediant 2000 MEGACO Compliance Table G-1: MEGACO Compliance Matrix (continues on page 265 to page 275) Reference Item Support Comments (in RFC3015) Failover Extension ServiceChangeReason 900 Service Restored 901 Cold Boot 902 Warm Boot 903 MGC Direct Change 904 Termination Malfunctioning...
Page 272 Mediant 2000 Table G-1: MEGACO Compliance Matrix (continues on page 265 to page 275) Reference Item Support Comments (in RFC3015) 402 - Unauthorized 403 - Syntax Error in Transaction 404 - Syntax Error in TransactionReply 405 - Syntax Error in TransactionPending...
Page 273 Mediant 2000 MEGACO Compliance Table G-1: MEGACO Compliance Matrix (continues on page 265 to page 275) Reference Item Support Comments (in RFC3015) 501 - Not Implemented 502 - Not ready 503 - Service Unavailable 504 - Command Received from unauthorized entity...
Page 274 Mediant 2000 Table G-1: MEGACO Compliance Matrix (continues on page 265 to page 275) Reference Item Support Comments (in RFC3015) Transaction API 8.2.1 Transaction Request Multiple actions per request 8.2.2 Transaction Reply Multiple actions per reply 8.2.3 Transaction Pending Transaction Pending Support...
Page 275 Mediant 2000 MEGACO Compliance Table G-1: MEGACO Compliance Matrix (continues on page 265 to page 275) Reference Item Support Comments (in RFC3015) 11.3 Negotiation of Protocol Version 11.4 Failure of an MG 11.5 Failure of an MGC Version 4.4 Beta...
Page 276 Mediant 2000 Reader’s Notes User’s Manual Document #: LTRT-69801...
Page 277: Appendix H Customizing The Audiocodes Web Interface
Web interface to suit their specific corporate logo and product naming conventions. OEMs can customize the Web interface's title bar (AudioCodes' title bar is shown in Figure H-1 and an example of a customized title bar is shown in Figure H-2).
Page 278: Replacing The Main Corporation Logo
When the main corporation logo is replaced, the AudioCodes logo in the main menu bar on the left (refer to Figure 6-2, on page 114) and the AudioCodes logo in the Software Upgrade Wizard (refer to Figure 6-31, on page 139) disappear.
Page 279: Replacing The Main Corporation Logo With A Text String
Replacing the Main Corporation Logo with a Text String The main corporation logo can be replaced with a text string. To replace AudioCodes' default logo with a text string via the Web interface, modify the two ini file parameters in Table H-2 according to the procedure described in Section H.5 on page 282.
Page 280: Replacing The Background Image File
If you intend to replace both the background image and the logo image, load the logo image first and then load the background image. Step 1. Access the AudioCodes Embedded Web Server (refer to Section 6.3.4 on page 112). Step 2.
Page 281: Customizing The Product Name
Customizing the Product Name The Product Name text string can be modified according to OEMs specific requirements. To replace AudioCodes' default product name with a text string via the Web interface, modify the two ini file parameters in Table H-4 according to the procedure described in Section H.5.
Page 282: Modifying Ini File Parameters Via The Web Interface's Adminpage
AdminPage To modify ini file parameters via the AdminPage, take these 7 steps: Step 1. Open AudioCodes' Web Interface Application, using the directions in the Device Management section of the accompanying AudioCodes product user's manual. Step 2. In the MS Windows Explorer Address field, enter the IP address of the location of the AudioCodes' Web Interface Application, followed by /AdminPage.
Page 283: Appendix I List Of Abbreviations
Mediant 2000 List of Abbreviations Appendix I List of Abbreviations Table I-1: List of Abbreviations (continues on page 283 to page 286) Abbreviation Meaning AAL2 ATM Adaptation Layer 2 ADPCM Adaptive Differential PCM - voice compression Alarm Indication Signal ASN.1...
Page 284 Internet Engineering Task Force Internet Protocol IPmedia AudioCodes series of VoIP Media Processing Boards IPM-260 AudioCodes IPmedia PCI VoIP Media Processing Board, to 120 ports IPM-1610 AudioCodes IPmedia cPCI VoIP Media Processing Board, to 240 ports ISDN Integrated Services Digital Network...
Page 285 Request for Comment issued by IETF. RTCP Real Time Control Protocol. Real Time Protocol. SB-1610 AudioCodes TrunkPack VoIP/ 1610 cPCI media streaming board, to 480 ports for Wireless systems ScBus Signal Computing Bus - part of SCSA SCSA Signal Computing System Architecture...
Page 286 Mediant 2000 Table I-1: List of Abbreviations (continues on page 283 to page 286) Abbreviation Meaning User Datagram Protocol Virtual Channel Connection VoAAL2 Voice over AAL2 (see above) VoATM Voice over Asynchronous Transfer Mode VoDSL Voice over Digital Subscriber Line...
Page 287: Appendix J Regulatory Information
4 HaHoresh Street, Yehud 56470, Israel. Type of Equipment: Digital VoIP System. Model Numbers: IPmedia 2000, Mediant 2000, Stretto 2000 I, the undersigned, hereby declare that the equipment specified above conforms to the above Directives and Standards. October, 2003 Yehud, Israel...
Page 288: Digital Device Warnings
Should you experience trouble with this telephone equipment, contact: AudioCodes Inc, San Jose, CA USA. Tel: 1 408 577 0488 Do not attempt to repair this equipment! Facility Interface Code: 04DU9.BN, 04DU9.DN, 04DU9.1KN, 4DU9.ISN...
Page 289: Network Compatibility
Mediant 2000 Regulatory Information Network Information and Intent of Use The product is for access to ISDN at 2048 kb/s and for access to G.703 Leased lines at 2048 kb/s. Network Compatibility The product supports all the Telecom networks in EU that comply with TBR4 and TBR13.
Page 290 International Headquarters: AudioCodes Ltd, 1 Hayarden Street, Airport City, Lod, Israel 70151. Tel: +972-3-976 4000 - Fax: +972-3-976 4040 AudioCodes Inc, 2890 Zanker Road, Suite # 200, San Jose, CA 95134. Tel: 1-408-577-0488 - Fax: 1-408-577-0492 AudioCodes Offices Worldwide: Beijing, Boston, Chicago, London, Paris, Tokyo www.audiocodes.com...

This manual is also suitable for:

Ipmedia 2000

AudioCodes Mediant 2000 User Manual

Quick Links

Need help?

Questions and answers

Related Manuals for AudioCodes Mediant 2000

Summary of Contents for AudioCodes Mediant 2000