AudioCodes Mediant 2000 User Manual
  1. Manuals
  2. Brands
  3. AudioCodes Manuals
  4. Gateway
  5. Mediant 2000
  6. User manual
AudioCodes Mediant 2000 User Manual

AudioCodes Mediant 2000 User Manual

Sip voip gateway
Hide thumbs Also See for Mediant 2000:
Table of Contents

Advertisement

Quick Links

Download this manual See also: Troubleshooting Manual, User Manual
Mediant™ 2000/SIP VoIP Gateway
User's Manual
Version 4.2 Beta
Document #: LTRT-00688
Preliminary Draft Version
US: AudioCodes Inc, 2890 Zanker Road, Suite # 200, San Jose, CA 95134.
Tel: 408-577-0488 - Fax: 408-577-0492
International: AudioCodes Ltd, 4 HaHoresh Street, PO Box 14, Yehud 56470, Israel.
Tel: +972-3-539 4000 - Fax: +972-3-539 4040
China: AudioCodes Ltd, Room 209 Tower A, Grand Pacific Building,
8A Guanghua Road, Chaoyang District, Beijing 100026, P.R.China
Tel: +86-10-6581-6622 - Fax: +86-10-6581-5599
Japan:
S Building B1F, 2-30-2, Chuou, Nakano-ku,
Tokyo 164-0011, Japan
Tel: Fax: +81-3-5348-1405 - Fax: +81-3-5348-1405

Advertisement

Table of Contents
loading
Need help?

Need help?

Do you have a question about the Mediant 2000 and is the answer not in the manual?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for AudioCodes Mediant 2000

Summary of Contents for AudioCodes Mediant 2000

  • Page 1 Version 4.2 Beta Document #: LTRT-00688 Preliminary Draft Version US: AudioCodes Inc, 2890 Zanker Road, Suite # 200, San Jose, CA 95134. Tel: 408-577-0488 - Fax: 408-577-0492 International: AudioCodes Ltd, 4 HaHoresh Street, PO Box 14, Yehud 56470, Israel. Tel: +972-3-539 4000 - Fax: +972-3-539 4040 China: AudioCodes Ltd, Room 209 Tower A, Grand Pacific Building, 8A Guanghua Road, Chaoyang District, Beijing 100026, P.R.China...
  • Page 3 Limited. All other products or trademarks are property of their respective owners. Customer Support Customer technical support and service are provided by AudioCodes’ Distributors, Partners, and Resellers from whom the product was purchased. For Customer support for products purchased directly from AudioCodes, contact support@audiocodes.com.
  • Page 4 This User’s Manual describes the Mediant™ 2000/SIP VoIP Gateway and TrunkPack™ TP-1610/SIP cPCI board from AudioCodes. Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions.

  • Page 5: Table Of Contents

    2.1.7 Optional CPU Board......................19 Mediant 2000/SIP Front & Rear Panels ..................20 2.2.1 Mediant 2000/SIP Front Panels ..................20 2.2.2 Mediant 2000/SIP Rear Panels ...................21 2.2.3 Mediant 2000/SIP Front Panel LED Indicators ..............27 Software Installation....................29 Installation Package........................29 Mediant 2000/SIP Initialization .......................29 Quick Setup Procedure........................29 BootP/DHCP and TFTP Procedures ....................32...
  • Page 6 6.2.11.2 HTTP Download......................... 98 6.2.11.3 License............................99 6.2.11.4 Save Configuration........................100 Diagnostics ......................101 Diagnostics Overview ........................101 Mediant 2000/SIP Gateway Alarms and SNMP Traps..............101 7.2.1 LED Visual Indicator Status and Alarms ................101 7.2.2 SNMP Traps ........................102 Mediant 2000/SIP Self-Testing .....................102 SysLog Support ..........................103 7.4.1 Overview..........................103...
  • Page 7 - Transport Modes DTMF, Fax and Modem ......... 114 C.1 DTMF/MF Relay Settings ......................114 C.2 Fax/Modem Settings........................114 C.2.1 Configuring Fax Relay Mode.....................114 C.2.2 Configuring Fax/Modem ByPass Mode................114 C.2.3 Supporting V.34 Faxes......................115 Appendix D – Mediant 2000 Clock Settings ............. 116 Version 4.2 Beta June 2003...
  • Page 8 Figure 2-6: Mediant 2000/SIP Front Panel Supporting up to 16 Trunks ............20 Figure 2-7: Mediant 2000/SIP Front Panel Supporting up to 8 Trunks ............21 Figure 2-8: Mediant 2000/SIP Rear Panel with two 50-pin Connectors for 16 Trunks ........22 Figure 2-9: Mediant 2000/SIP Rear Panel with 8 RJ-48c Connectors for 8 Trunks.........23 Figure 2-10: Mediant 2000/SIP Rear Panel with 4 RJ-48c Connectors for 4 Trunks........24...

  • Page 9: Version 4.2 Beta

    Mediant 2000/SIP User’s Manual Contents Figure 6-30: TFTP Download Screen.......................98 Figure 6-31: Software Update-HTTP........................98 Figure 6-32: License Screen ..........................99 Figure 7-1: The ini File Example for SysLog ....................103 Version 4.2 Beta June 2003...
  • Page 10 Table 4-1: Using SIP Gateway Features (continues on pages 41 to 42) ............41 Table 5-1: Basic and Logging Parameters (continues on pages 50 to 51) ............50 Table 5-2: Mediant 2000/SIP E1/T1/J1 Configuration Parameters (continues on pages 52 to 55) ....52 Table 5-3: Channel Parameters (continues on pages 56 to 57) ..............56 Table 5-4: SIP Configuration Parameters (continues on pages 58 to 62)............58...

  • Page 11: Overview Of The Mediant 2000

    Gateway uses AudioCodes’ well-established DSP voice compression technology. The Mediant 2000/SIP incorporates 1, 2, 4, 8 or 16 E1 or T1 spans for connection, directly to PSTN telephony trunks, and includes one or two 10/100 Base-T Ethernet ports for connection to the LAN.

  • Page 12: Figure 1-2: Mediant 2000/Sip Rear View

    Mediant 2000/SIP Figure 1-2: Mediant 2000/SIP Rear View Figure 1-3 below illustrates typical Mediant 2000/SIP Gateway applications over VoIP Network. Figure 1-3: Typical Mediant 2000/SIP Gateway Application Mediant 2000/SIP Document #: LTRT-00688...

  • Page 13: Mediant 2000/Sip Gateway Key Features

    Mediant 2000/SIP User’s Manual 1. Overview Mediant 2000/SIP Gateway Key Features " Superior, high quality PSTN Gateway for Voice and Fax over IP calls. " Up to 16 E1/T1/J1 digital spans supporting various PRI and CAS protocols. " Two 10/100 Base-T Ethernet interface connections to the IP network, providing LAN redundancy.
  • Page 14 Mediant 2000/SIP Reader's Notes Mediant 2000/SIP Document #: LTRT-00688...

  • Page 15: Hardware Installation

    2.1.1 General The Mediant 2000/SIP Gateway comprises a single AudioCodes CompactPCI™ board and a 19- inch 1U chassis with 110/220 VAC or optional 48 VDC power supply. The cPCI board is a high- density, hot-swappable, compactPCI resource board with a capacity of up to 480 ports, supporting all necessary functions for voice, data and fax streaming over IP networks.

  • Page 16: Applicable Boards

    384 Channels on 16 T1 spans with Gateway-1 and Gateway-2 2.1.3 Applicable Boards " TP-1610 - The board used for the Mediant 2000/SIP Gateway. Figure 2-2: Front and Upper View of TP-1610 cPCI Board Figure 2-3: View of Rear TP-1610 cPCI Board 2.1.4 Unpacking "...

  • Page 17: Installation

    $ To install the Mediant 2000, take the next 5 steps: Step 1 Insert the Mediant 2000/SIP into the 19-inch rack and fasten the left-hand and right- hand brackets to the vertical tracks of the 19-inch rack, using standard 19-inch rack bolts (not provided).

  • Page 18: Board Replacement

    2.1.6 Board Replacement " The Mediant 2000/SIP cPCI board, which is also the TP-1610 cPCI board, is hot-swappable, meaning that the board can be inserted and removed when the Mediant 2000/SIP chassis is under power. Mediant 2000/SIP Document #: LTRT-00688...

  • Page 19: Optional Cpu Board

    2.1.7 Optional CPU Board The Mediant 2000/SIP provides an optional second cPCI slot that can be used for Customer’s CPU board. This CPU board can be used for general applications such as SIP Proxy, Softswitch, Application Server or other. The following CPU boards were tested for compliancy with the Mediant 2000/SIP chassis: "...

  • Page 20: Mediant 2000/Sip Front & Rear Panels

    2.2.1 Mediant 2000/SIP Front Panels There is a choice of front panels according to the number of channels. Figure 2-6: Mediant 2000/SIP Front Panel Supporting up to 16 Trunks cPCI Latch FAIL Red - Board failure ACT Green - Initialization OK...

  • Page 21: Mediant 2000/Sip Rear Panels

    Mediant 2000/SIP User’s Manual 2. Hardware Installation Figure 2-7: Mediant 2000/SIP Front Panel Supporting up to 8 Trunks cPCI Latch FAIL Red - Board failure ACT Green - Initialization OK FAIL 1610 Series Ethernet LEDs (for each line) LINK Green -Link all OK...

  • Page 22: Figure 2-8: Mediant 2000/Sip Rear Panel With Two 50-Pin Connectors For 16 Trunks

    Mediant 2000/SIP Figure 2-8: Mediant 2000/SIP Rear Panel with two 50-pin Connectors for 16 Trunks cPCI Latch 1610 Series E1/T1 trunks 1 to 8 50-pin male Telco connector wired per Table 2-1 must be connected here. E1/T1 trunks 9 to 16...

  • Page 23: Figure 2-9: Mediant 2000/Sip Rear Panel With 8 Rj-48C Connectors For 8 Trunks

    Mediant 2000/SIP User’s Manual 2. Hardware Installation Figure 2-9: Mediant 2000/SIP Rear Panel with 8 RJ-48c Connectors for 8 Trunks cPCI Latch 1610 Series 8 E1/T-1 Spans 8 RJ-48c trunk connectors Ethernet 2 Ethernet Ports 2 RJ-45 LAN connectors cPCI Latch Version 4.2 Beta...

  • Page 24: Figure 2-10: Mediant 2000/Sip Rear Panel With 4 Rj-48C Connectors For 4 Trunks

    Mediant 2000/SIP Figure 2-10: Mediant 2000/SIP Rear Panel with 4 RJ-48c Connectors for 4 Trunks cPCI Latch 1610 Series 4 E1/T-1 Spans 4 RJ-48c trunk connectors Ethernet 2 Ethernet Ports 2 RJ-45 LAN connectors cPCI Latch Mediant 2000/SIP Document #: LTRT-00688...

  • Page 25: Figure 2-11: Mediant 2000/Sip Rear Panel With 2 Rj-48C Connectors For 2 Trunks

    Mediant 2000/SIP User’s Manual 2. Hardware Installation Figure 2-11: Mediant 2000/SIP Rear Panel with 2 RJ-48c Connectors for 2 Trunks cPCI Latch 1610 Series 2 E1/T-1 Spans 2 RJ-48c trunk connectors Ethernet 2 Ethernet Ports 2 RJ-45 LAN connectors cPCI Latch Version 4.2 Beta...

  • Page 26: Figure 2-12: Mediant 2000/Sip Rear Panel With 1 Rj-48C Connector For 1 Trunk

    Mediant 2000/SIP Figure 2-12: Mediant 2000/SIP Rear Panel with 1 RJ-48c Connector for 1 Trunk cPCI Latch 1610 Series 1 E1/T-1 Span 1 RJ-48c trunk connector Ethernet 2 Ethernet Ports 2 RJ-45 LAN connectors cPCI Latch Mediant 2000/SIP Document #: LTRT-00688...

  • Page 27: Mediant 2000/Sip Front Panel Led Indicators

    2. Hardware Installation 2.2.3 Mediant 2000/SIP Front Panel LED Indicators The functionality of the Front Panel LEDs for the Mediant 2000/SIP is described in the following four tables. Table 2-2: Indicator LEDs on the Mediant 2000/SIP Front Panel LED Name...
  • Page 28 Mediant 2000/SIP Reader's Notes Mediant 2000/SIP Document #: LTRT-00688...

  • Page 29: Software Installation

    Gateway configuration can be performed from a Web browser such as from Microsoft™ Internet Explorer. The ini file and other configuration files can be downloaded to Mediant 2000/SIP from Web Browser through HTTP or using standard TFTP Server or AudioCodes’ configuration utility. The Image software file Mediant.cmp is only used for software upgrade.

  • Page 30: Figure 3-1: Enter Network Password Screen

    " Default Gateway: 0.0.0.0 $ For a quick Mediant 2000 setup, take the next 12 steps: Power-up the Gateway. After self-testing, in about 20 seconds the ACT LED on front panel turns to green. Any malfunction causes the Fail LED to turn to red.

  • Page 31: Figure 3-2: Sip Quick Setup Screen

    Mediant 2000/SIP User’s Manual 3. Software Installation Figure 3-2: SIP Quick Setup Screen Fill in the Gateway’s active E1/T1 “B” channels. For example, for 4 T1 spans enter “1- 96” in the “Channels” field and starting phone number, such as 1001 in the adjacent “Phone Number”...

  • Page 32: Bootp/Dhcp And Tftp Procedures

    The following RFCs (IETF Requests for Comment) describe BootP in detail: RFC 951, RFC 1542 and RFC 2132. Downloading of the image file by the Mediant 2000/SIP is performed using Trivial File Transfer Protocol (TFTP). TFTP protocol is described in RFC 906 and RFC 1350.

  • Page 33: Configuring The Tftp Server

    TFTP Server on a different host. The utility enables remote reset of the Mediant 2000/SIP unit to trigger the initialization procedure (BootP & TFTP). For details of the procedure, refer to Appendix A in the AudioCodes "Software Utilities Manual", Catalog Number: LTRT-00602.

  • Page 34: Other Tftp & Bootp Servers

    Third party TFTP and BootP Servers can be used; for example, Weird Solutions (www.weird- solutions.com). ™ Note: Weird Solutions TFTP and BootP Servers must be installed on the same Host. Details can be found in the AudioCodes "Software Utilities Manual", Catalog Number: LTRT-00602. Mediant 2000/SIP Document #: LTRT-00688...

  • Page 35: Mediant 2000/Sip Software Upgrade

    After Mediant 2000/SIP power reset, the ini parameters are downloaded using the TFTP procedure and stored in the non-volatile memory. Reset the Mediant 2000. Wait about 20 seconds until the ACT LED changes to Green. After successfully completing BootP and TFTP procedures, the new software is downloaded and stored in the Mediant 2000/SIP unit’s flash memory.

  • Page 36: Figure 3-3: Audiocodes Configuration Utility Main Screen

    In the Services menu, choose Clients. This opens the Client Configuration screen shown in Figure 3-5 on page 37. The parameter fields displayed on the right side of the screen constitute the Mediant 2000/SIP software profile configuration. The parameter fields are all blank in the case of a Client Not Found.

  • Page 37: Figure 3-5: Client Configuration

    To permanently store the new image file in the unit’s flash memory, add –fb suffix to Boot file name, such as ram.cmp -fb. After entering the file names, click “Apply & Reset” button. The following status messages is displayed in the AudioCodes BootP/TFTP Server main screen: Version 4.2 Beta...

  • Page 38: Figure 3-6: Audiocodes Configuration Utility - Client Found

    Mediant 2000/SIP Figure 3-6: AudioCodes Configuration Utility - Client Found Mediant 2000/SIP Document #: LTRT-00688...

  • Page 39: Profile, Operation & Configuration

    4.1.1 PSTN-to-SIP Interworking The Mediant 2000/SIP Gateway supports various ISDN PRI protocols such as EuroISDN, North American NI2, Lucent 5ESS, Nortel DMS100, Japan J1, as well as QSIG (basic call). PRI support includes User Termination or Network Termination side. ISDN-PRI protocols can be defined on an E1/T1 basis (i.e., different variants of PRI are allowed on different E1/T1 spans).
  • Page 40 Supported codecs: G.711 A-law, G.711 µ-law, G.723, G.729A and NetCoder (6.4 to 8.8 kbps). • Can negotiate codec from a list of given codecs. For detailed information, refer to the latest Mediant 2000/SIP Release Notes, Catalog Number: LTRT- 00690. Mediant 2000/SIP...

  • Page 41: Using Mediant 2000/Sip Gateway Features

    4. SIP Operation & Configuration Using Mediant 2000/SIP Gateway Features Details of how to use the Mediant 2000 SIP Gateway Features are shown below in Table 4-1. Table 4-1: Using SIP Gateway Features (continues on pages 41 to 42) Feature...
  • Page 42 Mediant 2000/SIP Table 4-1: Using SIP Gateway Features (continues on pages 41 to 42) Feature Parameter Sheet of Value Excel Utility In this mode, several codecs are sent in SDP message. On receiving the remote response (200 OK) with its SDP, a process of matching coders is done between the local set of coders (from the ini file) and the remote set.

  • Page 43: Trunk To Trunk Routing Example

    4. SIP Operation & Configuration Trunk to Trunk Routing Example This example describes two Mediant 2000 Gateways, each interface with the PSTN through four E1 spans. Gateway "A" is configured to route all incoming Tel!IP calls to Gateway "B". Gateway "B"...

  • Page 44: Sip Call Flow Example

    The Call Flow, shown in Figure 4-1, describes SIP messages exchanged between Mediant 2000/SIP Gateway and an MP-108 Gateway during a simple call. MP-108 with phone number “8000”, calls Mediant 2000 with phone number “1000”: Figure 4-1: SIP Call Flow Example...
  • Page 45 Mediant 2000/SIP User’s Manual 4. SIP Operation & Configuration a=rtpmap:8 pcma/8000 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 a=ptime:20 F2 10.8.201.10 ==> 10.8.201.108 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacsiJkDGd From: <sip:8000@10.8.201.108>;tag=1c5354 To: <sip:1000@10.8.201.10> Call-ID: 534366556655skKw-8000--1000@10.8.201.108 CSeq: 18153 INVITE Content-Length: 0 F3 10.8.201.10 ==> 10.8.201.108 180 Ringing SIP/2.0 180 Ringing...
  • Page 46 Mediant 2000/SIP m=audio 7210 RTP/AVP 8 96 a=rtpmap:8 pcma/8000 a=ptime:20 a=rtpmap:96 telephone-event/8000 a=fmtp:96 0-15 F5 10.8.201.108 ==> 10.8.201.10 ACK ACK sip:1000@10.8.201.10;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacZYpJWxZ From: <sip:8000@10.8.201.108>;tag=1c5354 To: <sip:1000@10.8.201.10>;tag=1c7345 Call-ID: 534366556655skKw-8000--1000@10.8.201.108 CSeq: 18153 ACK Supported: 100rel,em Content-Length: 0 Phone "8000" goes on-hook; Gateway 10.8.201.108 sends "BYE" to Gateway 10.8.201.10 F6 10.8.201.108 ==>...

  • Page 47: Sip Authentication Example

    4. SIP Operation & Configuration SIP Authentication Example Mediant 2000/SIP Gateway supports basic and digest authentication types, according to the SIP standard. A proxy Server might require authentication before forwarding an INVITE message. A registrar Server may also require authentication for client registration. A proxy replies to an unauthenticated INVITE with a 407 Proxy Authorization Required response, containing a Proxy- Authenticate header with the form of the challenge.
  • Page 48 From: <sip: 122@10.1.1.200>;tag=1c23940 To: <sip: 122@10.1.1.200> Call-ID: 654982194@10.1.1.200 CSeq: 1 REGISTER Contact: sip:122@10.1.1.200: Expires:3600 Authorization: Digest, Username: MP108-AudioCodes, realm="audiocodes.com”, nonce="11432d6bce58ddf02e3b5e1c77c010d2", uri=”10.2.2.222”, response=“ b9c45d0234a5abf5ddf5c704029b38cf” On receiving this request, if accepted by the Proxy, the proxy returns a 200OK response closing the REGISTER transaction.

  • Page 49: Provisioning

    The file names in ini file must be enclosed in quotation marks (‘…’). All ini file data is downloaded at startup and stored in non-volatile memory. The provisioning procedure should be used again only to modify Mediant 2000/SIP parameters; otherwise, BootP and TFTP are not needed again.

  • Page 50: Basic, Logging And Web Parameters

    Note that BootPRetries parameter becomes active after the Mediant 2000/SIP is reset and ini file is loaded. To change the parameters, first modify the ini file, and then reset the Gateway.
  • Page 51 Mediant 2000/SIP User’s Manual 5. Provisioning for SIP Table 5-1: Basic and Logging Parameters (continues on pages 50 to 51) ini File Field Name Valid Range and Description GUI Parameter Name LoggerFormat 0 = name + msg 1 = time + msg...

  • Page 52: E1/T1 Configuration Parameters

    In Table 5-2, where there are parameters shown in brackets they refer to the format in the Embedded Web Server Table 5-2: Mediant 2000/SIP E1/T1/J1 Configuration Parameters (continues on pages 52 to 55) ini File Field Name Valid Range and Description...
  • Page 53 Mediant 2000/SIP User’s Manual 5. Provisioning for SIP Table 5-2: Mediant 2000/SIP E1/T1/J1 Configuration Parameters (continues on pages 52 to 55) ini File Field Name Valid Range and Description GUI Parameter Name ClockMaster 0 = Recover clock from the E1/T1 line (default) 1 = The clock is generated by the Gateway Refer to Appendix D for extended details of how to configure the Gateway’s clock...
  • Page 54 Mediant 2000/SIP Table 5-2: Mediant 2000/SIP E1/T1/J1 Configuration Parameters (continues on pages 52 to 55) ini File Field Name Valid Range and Description GUI Parameter Name CASTableIndex_x Defines CAS protocol for each Trunk ID (x = 0 to 7) from a list of protocols defined by the "CASFileName_Y"...
  • Page 55 Mediant 2000/SIP User’s Manual 5. Provisioning for SIP Table 5-2: Mediant 2000/SIP E1/T1/J1 Configuration Parameters (continues on pages 52 to 55) ini File Field Name Valid Range and Description GUI Parameter Name SwapRedirectNumber 0 = Don't change numbers (default) 1 = Swap between DNIS and Redirect numbers for ISDN incoming calls. Incoming (Swap Redirect and Called ISDN call that includes redirect number (sometimes referred as "original called...

  • Page 56: Channel Parameters

    Mediant 2000/SIP 5.1.3 Channel Parameters Note: In Table 5-3, where there are parameters shown in brackets they refer to the format in the Embedded Web Server Table 5-3: Channel Parameters (continues on pages 56 to 57) ini File Field Name...
  • Page 57 (RFC 2833 Payload Type) Range: 96 to 99, 106 to 127; Default = 96 The 100 to 105 range is allocated for AudioCodes proprietary usage. Cisco™ are using payload type 101 for RFC 2833. The same payload type should be used for receive and for transmit.

  • Page 58: Sip Configuration Parameters

    Mediant 2000/SIP 5.1.4 SIP Configuration Parameters Note: In Table 5-4, where there are parameters shown in brackets they refer to the format in the Embedded Web Server Details of how to use and configure the SIP Gateway Parameters are shown below.
  • Page 59 Mediant 2000/SIP User’s Manual 5. Provisioning for SIP Table 5-4: SIP Configuration Parameters (continues on pages 58 to 62) ini File Field Name Valid Range and Description GUI Parameter Name CoderName Supported Coders: G.711 µ-law, 20 msec g711Ulaw64k g711Alaw64k G.711 A-law, 20 msec G.711 µ-law, 5 msec...
  • Page 60 Mediant 2000/SIP Table 5-4: SIP Configuration Parameters (continues on pages 58 to 62) ini File Field Name Valid Range and Description GUI Parameter Name NumberMapIP2Tel a ,b, c, d, e, f (Manipulation Tables: a = Phone number prefix IP!Tel Destination...
  • Page 61 0 = Select the “B” channel according to destination phone number received in H225 setup message, (used only for bulk load testing) 1 = Select the next available “B” channel (default) Should be set to ‘1’ for Mediant 2000/SIP EnableEarlyMedia 0 = Early Media is disabled (default)
  • Page 62 Mediant 2000/SIP Table 5-4: SIP Configuration Parameters (continues on pages 58 to 62) ini File Field Name Valid Range and Description GUI Parameter Name SecureCallsFromIP 0 = Accept all SIP Calls (default) (IP Security) 1 = Accept SIP calls only from the IP addresses which are defined in the Prefix Routing table.

  • Page 63: Loading Call Progress Tones And E1/T1 Cas Configuration Files

    “CASfilename” This is the name of the file containing specific CAS protocol definition (such as ‘E_M_WinkTable.dat’). These files are provided by AudioCodes to support various types of CAS signaling. “CASfilename_x” It is possible to download up to 8 different CAS files (x=0 to 7), by repeating the CASFileName parameter.

  • Page 64: The Ini File Structure

    Mediant 2000/SIP The ini File Structure The ini file can contain any number of parameters. The parameters are divided into groups by their functionality. The general form of the ini file is shown below. Figure 5-1: ini File Structure [Sub Section Name]...

  • Page 65: The Ini File Examples

    Mediant 2000/SIP User’s Manual 5. Provisioning for SIP 5.2.2 The ini File Examples Examples of ini files for an SIP Gateway are shown in Figure 5-2 Figure 5-2: SIP ini File Example MGControlProtocolType = 8 PCMLawSelect = 1 ProtocolType = 1...

  • Page 66: Excel Utility For Ini File Generation

    Mediant 2000/SIP Excel Utility for ini File Generation The Excel Utility enables easy generation of Mediant 2000/SIP and other MediaPack series Gateway ini files. To use the Excel utility, first install the Microsoft Office 2000 Excel application. Currently, the utility can be used to generate ini files only for SIP Gateways.

  • Page 67: Sip Parameters Sheet

    Mediant 2000/SIP User’s Manual 5. Provisioning for SIP 5.3.2 SIP Parameters Sheet Figure 5-4: SIP Parameters Sheet 5.3.3 End Points Data Sheet Figure 5-5: End Points Data Sheet Version 4.2 Beta June 2003...

  • Page 68: Prefix To Ip Routing Table

    Mediant 2000/SIP 5.3.4 Prefix to IP Routing Table Figure 5-6: Routing Table Data Sheet 5.3.5 E1/T1 Parameters Sheet Figure 5-7: E1/T1 Parameter Sheet Mediant 2000/SIP Document #: LTRT-00688...

  • Page 69: Using Call Progress Tones

    AudioCodes, or construct their own file. The Call Progress Tones Configuration File used by the Mediant 2000/SIP is a binary file (with the extension dat). Users can construct their own configuration file by starting from tone.ini file format, then modifying the file, and finally converting it into binary format using the “Download...

  • Page 70: Default Template For Call Progress Tones

    For example, the User can define an additional dial tone by appending the second dial tone definition lines to the tone ini file. The Mediant 2000/SIP reports dial tone detection if either of the two tones is detected.
  • Page 71 Mediant 2000/SIP User’s Manual 5. Provisioning for SIP Table 5-5: Call Progress Tones Template (continues on pages 70 to 73) #Dial tone [CALL PROGRESS TONE #1] Tone Type=1 Low Freq [Hz]=440 High Freq [Hz]=0 Low Freq Level [-dBm]=10 High Freq Level [-dBm]=32...
  • Page 72 Mediant 2000/SIP Table 5-5: Call Progress Tones Template (continues on pages 70 to 73) First Signal Off Time [10msec]=50 Second Signal On Time [10msec]=50 Second Signal Off Time [10msec]=50 #Busy [CALL PROGRESS TONE #5] Tone Type=3 Low Freq [Hz]=440 High Freq [Hz]=0...

  • Page 73: Call Progress Tone Generation And Download Procedure

    Mediant 2000/SIP User’s Manual 5. Provisioning for SIP Table 5-5: Call Progress Tones Template (continues on pages 70 to 73) Low Freq Level [-dBm]=20 High Freq Level [-dBm]=32 First Signal On Time [10msec]=0 First Signal Off Time [10msec]=0 Second Signal On Time [10msec]=30 Second Signal Off Time [10msec]=900 5.4.3...

  • Page 74: Figure 5-9: File Selection Screen

    Save the “usa_tone.dat” and “Mediant.ini” files in TFTP folder Set the Boot file name in the BootP Server: Mediant.ini, or use Web Browser (Network setting page). Activate the BootP and TFTP Servers and reset the Mediant 2000/SIP (refer to Section 5.1, describing Mediant 2000/SIP provisioning). Mediant 2000/SIP...

  • Page 75: Device Management

    MIBs (such as the IP MIB), VoP-specific MIBs (such as RTP, MGCP, Trunk, etc.) and a proprietary MIB (known also as AudioCodes MIB) enabling a deeper probe into the ”inner working” of the Gateway. All the supported MIBs files are supplied as part of the release.

  • Page 76: Snmp Mib Objects

    The act of compiling the MIB allows the manager to know about the special objects supported by the agent and access these objects as part of the standard object set. 6.1.5 Mediant 2000/SIP Gateway Supported MIBs The TrunkPack-VoP Series contains an embedded SNMP Agent supporting the following MIBs: "...
  • Page 77 Mediant 2000/SIP User’s Manual 6. Device Management " RTP MIB - The RTP MIB is supported per the RFC 2959. It contains objects relevant to the RTP streams generated and terminated by the Gateway and to the RTCP information related to these streams.

  • Page 78: Web Management

    Web Management 6.2.1 Overview AudioCodes’ Mediant 2000/SIP Media Gateway is supplied with an integrated Web server to be used both for device configuration and for run-time monitoring. AudioCodes’ Embedded Web Server enables Users equipped with no more than a standard Web browser to: Provision all parameters (refer to section 6.2.8, “Protocol Management”...

  • Page 79: Security Preferences

    Mediant 2000/SIP User’s Manual 6. Device Management supports. MD5 authentication takes as input a message of arbitrary length and produces as output a 128-bit "fingerprint" or "message digest" of the input. It cannot produce two messages having the same message digest, or produce any message having a given pre-specified target message digest.

  • Page 80: Quick Setup Configuration Parameters

    Mediant 2000/SIP Figure 6-1: Enter Network Password Screen 6.2.7 Quick Setup Configuration Parameters To configure the device’s parameters, Users can either use the “Quick Setup” menu or go directly to “Advanced Configuration” and “protocol Management” menus. “Quick Setup” provides a minimal set of Gateway configuration settings.

  • Page 81: Protocol Management Menu

    Mediant 2000/SIP User’s Manual 6. Device Management 6.2.8 Protocol Management Menu $ To access the Advanced Configuration menu, take the following 2 steps Step 1 To access the device’s Protocol Management parameters, from the main menu list on the left, click on the “Protocol Management” button. The Protocol Management Parameters screen with the sub-menu bar on the top is displayed.

  • Page 82: Figure 6-4: General, Proxy Server And Authentication Parameters

    Mediant 2000/SIP • General, Proxy Server and Authentication Parameters shown in Figure 6-4. Figure 6-4: General, Proxy Server and Authentication Parameters • VoIP Coders shown below in Figure 6-5. Figure 6-5: VoIP Coders • Early Media Parameters shown below in Figure 6-6.

  • Page 83: Trunk Group Table

    Mediant 2000/SIP User’s Manual 6. Device Management define routing rules based on the Trunk group from where the call arrived. The two routing mode parameters define the execution order of number manipulation as opposed to the routing rules. Shown below in Figure 6-7.

  • Page 84: Number Manipulation Tables

    Mediant 2000/SIP $ To set the Trunk Group table, take the following 3 steps: Step 1 On the sub-menu bar on the top, click the “Trunk Group” option. The Trunk Group screen appears. Step 2 Define the Trunk Groups. Figure 6-11: Trunk Group Table In the example above, trunk group number 1 is composed of B-channels from the first and the second E1 spans.

  • Page 85: Tel To Ip Routing Table

    Mediant 2000/SIP User’s Manual 6. Device Management Figure 6-12: Phone Number Manipulation Table for IP ! Tel calls In Figure 6-12 above, the 1 rule adds "972" prefix to all numbers starting with "03". The 2 rule first deletes 4 digits from all numbers starting with "1001" and then the digit "5" is added as prefix.

  • Page 86: Ip To Trunk Routing Table

    Mediant 2000/SIP In the example above, all incoming PSTN calls, with destination numbers starting with “10” and “210xxxx” are routed to IP address 10.8.201.108 while calls with destination numbers starting with “21xxxx”, (excluding calls which start with the prefix “210”) are sent over IP to address 10.8.201.141.

  • Page 87: Network Settings

    Mediant 2000/SIP User’s Manual 6. Device Management Figure 6-15: Advanced Configuration Step 2 To display the active configuration of a section and its relevant parameters; click on an option in the sub-menu bar on the top (Network Settings, Channel Settings, etc.).

  • Page 88: Channel Settings

    Mediant 2000/SIP Figure 6-16: Network Settings Screen 6.2.9.2 Channel Settings $ To set Channel Settings, take the following 3 steps: Step 1 On the sub-menu bar on the top, click the Channel Settings option. The Channel Settings screen appears. Step 2 In the Channel Settings screen, you can enter or modify the Gateway’s channel...

  • Page 89: Trunk Settings

    Mediant 2000/SIP User’s Manual 6. Device Management Figure 6-17: Channel Settings 6.2.9.3 Trunk Settings $ To set Trunk Settings, take the following 5 steps: Step 1 On the sub-menu bar on the top, click the Trunk Settings option. The Trunk Settings screen appears.

  • Page 90: Figure 6-18: E1/T1 Trunk Settings

    Mediant 2000/SIP Figure 6-18: E1/T1 Trunk Settings Number indicates which Trunk is selected Table 6-1: Trunks Status Color Indicator Key Indicator Color Description White Disabled Green Active-OK Yellow RAI Alarm LOS Alarm Blue AIS Alarm Orange D-Channel Alarm Step 4 Modify the relevant Trunk configuration parameters;...

  • Page 91: Tdm Bus Settings

    Mediant 2000/SIP User’s Manual 6. Device Management Step 5 After modifying any parameters, do one of the following: • To apply the changes to the selected trunk only, click the “Apply Trunk Settings” button. • To apply the changes to all the trunks, click the “Apply to All Trunks button”.

  • Page 92: Regional Settings

    Mediant 2000/SIP $ To access the Configuration File screen, take this step: Step On the sub-menu bar on the top, click the Configuration File option. The Configuration File screen appears. Figure 6-20: Configuration File Screen $ To get the board’s ini file: Click on the “Get INI File”...

  • Page 93: Change Password

    Mediant 2000/SIP User’s Manual 6. Device Management Figure 6-21: Regional Settings Screen $ To send a Call Progress Tone or CAS file to the board, take these 3 steps: Step 1 Use the Browse button to locate the predefined Call Progress Tone or CAS file as appropriate.

  • Page 94: 6.2.10 Status And Diagnostic Menu

    Mediant 2000/SIP Figure 6-22: Change Password Screen Step 2 Enter user name and new password information into the fields and click the Change Password button. The new password is active only after restarting the device. Otherwise, the “old” password is still active.

  • Page 95: Trunk And Channel Status

    Mediant 2000/SIP User’s Manual 6. Device Management Step 2 To display the active configuration of a section and its relevant parameters; click on an option in the sub-menu bar on the top (Channel Status, Message Log etc.). 6.2.10.1 Trunk and Channel Status $ To access the Trunk and Channel Status screen, take this step: On the sub-menu bar on the top, click the Channel Status option.

  • Page 96: Message Log

    Mediant 2000/SIP Figure 6-26: Channel Status 6.2.10.2 Message Log The Message Log provides debug messages (similar to the syslog). It is useful in pursuing troubleshooting issues. $ To display the Message Log, take this step: .On the sub-menu bar on the top, click the Message Log option. The Message Log screen appears.

  • Page 97: Versions

    Mediant 2000/SIP User’s Manual 6. Device Management 6.2.10.3 Versions The Versions screen displays hardware and software product information. $ To display the Versions screen, take this step: On the sub-menu bar on the top, click the Versions option. The Versions screen appears.

  • Page 98: Tftp Download

    Mediant 2000/SIP 6.2.11.1 TFTP Download The TFTP Download screen facilitates the download of the image, *.cmp, and ini files using the TFTP protocol. $ To use the TFTP Download screen, take these 2 steps: Step 1 On the sub-menu bar on the top, click the TFTP Download option. The TFTP Download screen appears.

  • Page 99: License

    On the sub-menu bar on the top, click the License option. The License screen appears. Figure 6-32: License Screen Step 2 In the “New Key” field, enter the updated license key supplied by AudioCodes. Step 3 Click the “Add Key” button. The new key information overwrites the previous key installed on the computer.

  • Page 100: Save Configuration

    Mediant 2000/SIP 6.2.11.4 Save Configuration The Save Configuration screen allows the User to save changes to the configuration locally, in the Flash memory, until a system Reset is performed. Note: If you perform the reset immediately after making the changes to the configuration there is no need to use the Save Configuration function prior to the reset.

  • Page 101: Diagnostics

    7. Diagnostics Diagnostics Diagnostics Overview AudioCodes provides several diagnostic tools to enable the User to identify an error condition and to provide a solution or work around when working with Mediant 2000/SIP Gateway " LED Indication of Gateway status, E1/T1 signals, LAN status, cPCI status.

  • Page 102: Snmp Traps

    Blue The cPCI board was inserted successfully. During correct Mediant 2000/SIP operation, the ACT LED is lit green, the FAIL LED is off. Changing of the FAIL LED to red indicates a failure. In the correct Mediant 2000/SIP operation, the E1/T1 Status LED is lit green. Any other condition indicates failure, either in the E1/T1 cable, in the Mediant 2000/SIP or at the remote side.

  • Page 103: Syslog Support

    7.4.2.1 Sending the SysLog Messages AudioCodes’ SysLog client, embedded in the firmware of the Mediant 2000/SIP, sends error reports/events generated by the Mediant 2000/SIP unit application to a SysLog Server, using IP/UDP protocol. AudioCodes does NOT provide a SysLog Server. Examples of SysLog Servers...

  • Page 104: Solutions To Problems

    Table 7-5: Solutions to Common Problems (continues on pages 104 to 105) Problem Possible Cause Solutions Software does not Try to “ping” to Mediant 2000. If ping fails, check for network communication function in Mediant 2000 problems/definitions and try to reset the Mediant 2000/SIP Network problem Check cables.
  • Page 105 Mediant 2000/SIP User’s Manual 7. Diagnostics Table 7-5: Solutions to Common Problems (continues on pages 104 to 105) Problem Possible Cause Solutions Version 4.2 Beta June 2003...

  • Page 106: Possible Voice Problems

    Mediant 2000/SIP 7.5.2 Possible Voice Problems Solutions to possible voice problems are described in Table 7-6 Table 7-6: Solutions to Possible Voice Problems Problem Possible Solutions Cause G.711 voice quality is bad Silence Disable it and check if quality is better.

  • Page 107: Specifications

    Mediant 2000/SIP User’s Manual 8. Specifications Specifications Mediant 2000/SIP Specifications Table 8-1: Mediant 2000/SIP Specifications (continues on pages 107 to 108) Function Specification Mediant 2000/SIP Trunk & Channel Capacity Capacity with E1 1, 2, 4, 8 or 16 E1 spans, 30, 60, 120, 240 or 480 digital channels...
  • Page 108 Mediant 2000/SIP Table 8-1: Mediant 2000/SIP Specifications (continues on pages 107 to 108) Function Specification MF-R1, MF-R2 User-defined Call Progress Tones Interfaces Telephony Interface 1,2,4, 8 or 16 E1/T1/J1 Balanced 120/100 ohm Network Interface Two 10/100 Base-T, half or full duplex with auto-negotiation...

  • Page 109: Appendices

    This section contains the following Appendices: Appendix A - Default RTP/RTCP/T.38 Ports Allocation Appendix B - RTP/RTCP Payload Types Appendix C - Fax, Modem and DTMF Transport Modes Appendix D – Mediant 2000 Clock Settings Version 4.2 Beta June 2003...

  • Page 110: Appendix A - Default Rtp/Rtcp/T.38 Port Allocation

    Mediant 2000/SIP Appendix A - Default RTP/RTCP/T.38 Port Allocation The following table describes Mediant 2000/SIP Gateway default RTP/RTCP/T.38 Port Allocation. Table A-1: Default RTP/RTCP/T.38 Port Allocation Channel Number RTP Port RTCP Port T.38 Port 6000 6001 6002 6010 6011 6012...
  • Page 111 Mediant 2000/SIP User’s Manual Appendix A Reader’s Notes Version 4.2 Beta June 2003...

  • Page 112: Appendix B - Rtp/Rtcp Payload Types

    Mediant 2000/SIP Appendix B - RTP/RTCP Payload Types RTP Payload Types are defined in RFC 1889 and RFC 1890. AudioCodes has added new payload types to enable advanced use of other coder types. These types are reportedly not used by other applications.

  • Page 113: Audiocodes Defined Payload Types

    Mediant 2000/SIP User’s Manual Appendix B AudioCodes Defined Payload Types Table B-2: AudioCodes Defined Payload Types Payload Type Description Basic Packet Rate [msec] G.726 16 kbps G.726 24 kbps G.726 40 kbps G.727 16 kbps G.727 24-16 kbps G.727 24 kbps G.727 32-16 kbps...

  • Page 114: Appendix C - Transport Modes Dtmf, Fax And Modem

    Mediant 2000/SIP Appendix C - Transport Modes DTMF, Fax and Modem 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 three modes are supported: DTMF/MFTransportType= 0 (MuteDTMF/MF). In this mode, DTMF/MF digits are erased from the audio stream and are not relayed to the remote side.

  • Page 115: Supporting V.34 Faxes

    Mediant 2000/SIP User’s Manual Appendix D then when fax/modem is detected, the channel automatically switches from the current voice coder to a high bit-rate coder, as defined by the User, with the FaxModemBypassCoderType configuration parameter. If fax relay is enabled for one of the modes, then the Answer Tone mode packets are relayed as fax relay packets.

  • Page 116: Appendix D - Mediant 2000 Clock Settings

    TDMBusLocalReference = # (Trunk index: 0 to 7, default = 0) US: AudioCodes Inc, 2890 Zanker Road, Suite # 200, San Jose, CA 95134. Tel: 408-577-0488 - Fax: 408-577-0492 International: AudioCodes Ltd, 4 HaHoresh Street, PO Box 14, Yehud 56470, Israel.

Table of Contents