Page 1 Mediant 2000, Mediant 1000 & TP-1610 H.323 User’s Manual Version 4.6 Document #: LTRT-69903...
Page 2 Notice This document describes the release of the AudioCodes Mediant 2000 H.323 gateway, digital Mediant 1000 H.323 gateway and TP-1610 H.323 cPCI board. Information contained in this document is believed to be accurate and reliable at the time of printing.
Page 3: Table Of Contents
3.1.2 Package Contents .......................41 3.1.3 Mounting the Mediant 2000....................42 3.1.3.1 Mounting the Mediant 2000 on a Desktop ..............42 3.1.3.2 Installing the Mediant 2000 in a 19-inch Rack ..............42 3.1.4 Cabling the Mediant 2000 ....................44 3.1.4.1 Connecting the E1/T1 Trunk Interfaces ................45 3.1.4.2 Installing the Ethernet Connection ................46...
Page 4 3.3.4.3 Connecting the Audio IN/OUT Cable ................55 Getting Started ......................57 Configuration Concepts ........................57 Assigning the Mediant 2000 IP Address..................58 4.2.1 Assigning an IP Address Using HTTP ................58 4.2.2 Assigning an IP Address Using BootP ................59 Configuring the Mediant 2000 Basic Parameters................59 Web Management ......................61...
Page 5 Mediant Series and TP-1610 H.323 User’s Manual Contents 5.6.7 Changing the Mediant 2000 Username and Password ............94 Status & Diagnostic ........................95 5.7.1 Gateway Statistics .......................95 5.7.1.1 IP Connectivity ......................95 5.7.1.2 Call Counters ........................96 5.7.1.3 Call Routing Status .......................98 5.7.2 Monitoring the Mediant 2000 Trunks & Channels ...............99 5.7.3 Activating the Internal Syslog Viewer................101...
Page 6 10.4 Redirect Number and Calling Name (Display)................184 11 Advanced System Capabilities ................185 11.1 Restoring Networking Parameters to their Initial State..............185 11.2 Establishing a Serial Communications Link with the Mediant 2000 ..........185 11.3 Automatic Update Mechanism......................186 11.4 Startup Process ..........................188 11.5 Using Parameter Tables .......................190...
Page 7 16.7.4.1 Trap Manger Configuration via Host Name ..............242 16.7.4.2 Trap Managers Configuration via the ini File ..............243 16.7.4.3 Trap Mangers Configuration via SNMP ..............244 16.8 SNMP Manager Backward Compatibility..................245 16.9 Dual Module Interface........................245 16.10 AudioCodes’ Element Management System ................245 Version 4.6 July 2005...
Page 8 17.3 Voice Prompts File........................250 17.4 CAS Protocol Configuration Files ....................251 18 Selected Technical Specifications ................. 253 18.1 General Specifications........................253 18.2 Mediant 2000 Specifications......................255 18.3 TP-1610 Specifications.........................257 18.4 Mediant 1000 Specifications......................259 Appendix A Supplied H.323 Software Kit ..............261 Appendix B The BootP/TFTP Configuration Utility ............ 263 When to Use the BootP/TFTP ......................263...
Page 9 Mediant Series and TP-1610 H.323 User’s Manual Contents Appendix F Regulatory Information ................297 Mediant 2000 ..........................297 TP-1610 ............................299 Version 4.6 July 2005...
Page 10 Figure 2-15: HDMX Module..........................40 Figure 3-1: 19-inch Rack & Desktop Accessories ....................42 Figure 3-2: Mediant 2000 Front View with 19-inch Rack Mount Brackets ............43 Figure 3-3: Mediant 2000 Rear Panel Cabling (16 Trunks, Dual AC Power)...........44 Figure 3-4: Mediant 2000 Rear Panel Cabling (8 Trunks, DC Power))............44 Figure 3-5: 50-pin Female Telco Board-Mounted Connector................45...
Page 11 Figure 5-32: Start Software Upgrade Screen ....................104 Figure 5-33: Load a cmp File Screen ......................105 Figure 5-34: cmp File Successfully Loaded into the Mediant 2000 Notification..........105 Figure 5-35: Load an ini File Screen ......................106 Figure 5-36: Load a CPT File Screen......................107 Figure 5-37: FINISH Screen ...........................107...
Page 12 Table 2-16: CM Module Component Descriptions ...................38 Table 2-17: iPMX Module Component Descriptions ..................39 Table 3-1: Mediant 2000 Rear Panel Cabling (16 Trunks, Dual AC Power) Component Descriptions ...44 Table 3-2: Mediant 2000 Rear Panel Cabling (8 Trunks, DC Power) Component Descriptions......44 Table 3-3: E1/T1 Connections on each 50-pin Telco Connector ..............45...
Page 13 Table 15-5: /BSP/EXCeption Folder.......................230 Table 18-1: General Selected Technical Specifications (continues on pages 255 to 256)......253 Table 18-2: Mediant 2000 Selected Technical Specifications (continues on pages 257 to 258)....255 Table 18-3: TP-1610 Selected Technical Specifications (continues on pages 259 to 260)......257 Table 18-4: Mediant 1000 Selected Technical Specifications................259...
Page 14 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 15: Customer Support
Trademarks AC logo, Ardito, AudioCoded, AudioCodes, AudioCodes logo, IPmedia, Mediant, MediaPack, MP- MLQ, NetCoder, Stretto, TrunkPack, VoicePacketizer and VoIPerfect, are trademarks or registered trademarks of AudioCodes Limited. All other products or trademarks are property of their respective owners. Customer Support Customer technical support and service are provided by AudioCodes’...
Page 16 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 17: Overview
TrunkPack series products. The Mediant 2000 incorporates 1, 2, 4, 8 or 16 E1 or T1 spans for connection, directly to Public Switched Telephone Network (PSTN) / Private Branch Exchange (PBX) telephony trunks, and includes one or two 10/100 Base-TX Ethernet ports for connection to the network.
Page 18: Tp-1610 Overview
Mediant Series and TP-1610 H.323 TP-1610 Overview The TP-1610 cPCI VoIP media gateway board, based on dual TPM-1100 PMC Modules, is a complete H.323-compliant ‘two media gateways on a board’, delivering cost-effective solution in a convenient cPCI form-factor. The TP-1610 is an ideal solution for H.323 trunking gateways and integrated media gateways for IP-PBXs and all-in-one communication servers.
Page 19: Mediant 1000 Overview
Mediant Series and TP-1610 H.323 User’s Manual 1. Overview Mediant 1000 Overview The Mediant 1000 is a cost-effective, converged wireline VoIP media gateway utilizing cutting edge technology. Intelligently packaged in a stackable 1U chassis, it is designed to interface between TDM & IP networks as a Customer Premise(s) Equipment (CPE) device. Incorporating innovative Voice over Packet technology, the Mediant 1000 enables rapid time-to-market and reliable cost-effective deployment of next-generation networks.
Page 20: Mediant 2000 Features
Figure 1-1 below illustrates a typical Mediant 2000 gateway application over VoIP Network. Figure 1-1: Typical Mediant 2000 Gateway Application Mediant 2000 Features This section provides a high-level overview of some of the many Mediant 2000 supported features. 1.5.1 General Features •...
Page 21: Pstn-To-H.323 Interworking
Secured Web access (HTTPS) and Telnet access using SSL / TLS. 1.5.2 PSTN-to-H.323 Interworking The Mediant 2000 gateway performs interworking between ISDN or CAS via E1/T1/J1 digital spans and H.323 VoIP ITU-T protocol. 16 E1 T1, or J1 spans are supported (480 channels) in a two modules gateway.
Page 22: Compatibility
Mediant Series and TP-1610 H.323 1.5.3 H.323 Compatibility The Mediant 2000 H.323 gateway is built on and implements the RadVision™ H.323 version 4.2 protocol stack. The gateway complies with H.323 Version 4.0 ITU standard, H.245 Version 10 and H.225 Version 4.
Page 23: General H.323 Features
• Supports ISDN PRI Setup and Facility messages tunneling in H.323 according to H.323 Annex M.3. Note that the vulnerability of the Mediant 2000 was evaluated to H.323 messages per NISCC Vulnerability Advisory 006489/H323 (refer to uniras.gov.uk and to kb.cert.org).
Page 24 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 25: Physical Description
• A single available cPCI slot for an optional third-party CPU board (refer to Section 2.1.2 page 29). Figure 2-1: Mediant 2000 Front View Table 2-1: Mediant 2000 Front View Component Descriptions Item # Label Component Description FAULT Dual AC Power LED.
Page 26: The Mediant 2000 Chassis
TP-1610 board in its front cage, slot #1 (the lower slot) and the TP-1610 RTM in its rear cage, slot #1 (the lower slot). Slot # 2 in the Mediant 2000 chassis’ front and rear cages can optionally be used by customers for a CPU board.
Page 27: Tp-1610 Physical Description
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description TP-1610 Physical Description The TP-1610 (shown in Figure 2-2) is a high-density, hot-swappable, cPCI resource board with a capacity of up to 480 ports, supporting all necessary functions for voice, data and fax streaming over IP networks.
Page 28: Tp-1610 Front Panel Led Indicators
Mediant Series and TP-1610 H.323 2.2.1 TP-1610 Front Panel LED Indicators The functionality of the front panel LEDs for the TP-1610 is described in the following four tables and illustrated in Figure 2-2 on page 27. Note that there is a choice of front panels according to the number of channels.
Page 29: Rear Transition Module
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description 2.2.2 Rear Transition Module The RTM includes PSTN trunks, an Ethernet interface and an optional RS-232 connector (available only on the 1, 2 and 4-span configuration). The Ethernet interface features dual 10/100 Base-TX, RJ-45 shielded connectors for (an active / standby) redundancy scheme providing protection against the event of a failure.
Page 30: Mediant 1000 Physical Description
Mediant Series and TP-1610 H.323 Mediant 1000 Physical Description Designed to meet Network Equipment Building System (NEBS) Level 3, the Mediant 1000 is a 19-inch industrial platform chassis, 1U high and 13.8 inch deep. The Mediant 1000 supports a scalable, modular architecture that includes up to four modules, a single CPU module, a power supply module and an optional fan try module (the extractable modules are shown in Table 2-15...
Page 31: I/O Modules
• Audible or visual alarms – bell, siren, hooter, or light • Loudspeakers for paging • Locking mechanisms or general-purpose switches such as door locks etc. Not currently supported. Contact AudioCodes regarding availability. Version 4.6 July 2005...
Page 32: Audio In/Out
The clean air passes through the entire set of modules cooling each one and exits the Mediant 1000 via perforated vents on the left side of the chassis. Not currently supported. Contact AudioCodes regarding availability. Mediant Series and TP-1610 H.323...
Page 33: Replacing The Air Filter
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description Blank panels are used to cover all unoccupied slots on the front and rear sides of the chassis. The blank panels are especially constructed to assist optimal air flow within the chassis. It is imperative to cover all unoccupied slots in the front and rear panels of the Note: chassis with blank panels to maintain internal airflow pressure.
Page 34: Figure 2-8: Fan Try With Filter Extracted
Alternatively, if you are replacing the filter, discard the old air filter and replace it with an air filter purchased from AudioCodes. Attach the (new / cleaned) air filter to the fan try module; position the two holes on the filter...
Page 35: Front Panel Leds
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description 2.3.1.5 Front Panel LEDs Figure 2-9 below, shows the location of the front panel LEDs on the Mediant 1000. They are described below in Table 2-11, Table 2-12 Table 2-13. Figure 2-9: Location of Front Panel LEDs Table 2-11: Functionality of the CPU Module LEDs Location...
Page 36: Mediant 1000 Rear Panel
Mediant Series and TP-1610 H.323 2.3.2 Mediant 1000 Rear Panel The Mediant 1000 rear connectors are described in the following sections (refer to Figure 2-10). Figure 2-10: Mediant 1000 Rear Connectors Table 2-14: Mediant 1000 Rear Connectors Component Descriptions Item # Label Component Description ESD (Electrostatic Discharge) port.
Page 37: Mediant 1000 Modules
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description 2.3.3 Mediant 1000 Modules The extractable Mediant 1000 modules are shown in Table 2-15 below. Table 2-15: Extractable Mediant 1000 Modules Module Description CPU module Digital I/O module Fan tray module with six fans and an air filter Power supply module Version 4.6 July 2005...
Page 38: Partner Application Platform
Mediant Series and TP-1610 H.323 2.3.4 Partner Application Platform The Mediant 1000 can also host a flexible platform for partner applications. The open platform on the Mediant 1000 offers partners the option to host their own applications (e.g., IP-PBX or call center application) using a powerful, low-power consumption processor and hard disks to provide a complete solution within the Mediant 1000 chassis.
Page 39: Figure 2-12: Ipmx Module
Mediant Series and TP-1610 H.323 User’s Manual 2. Physical Description Figure 2-12: iPMX Module Table 2-17: iPMX Module Component Descriptions Item # Component Description RJ-45 connector as 10/100 Base-TX Ethernet port Ethernet activity LED (yellow) Ethernet link LED (green) RJ-11 connector used for night bell relay output. The pinout of this connector is described in Figure 2-13.
Page 40: Hdmx Module
Mediant Series and TP-1610 H.323 2.3.4.3 HDMX Module The HDMX module is located on the Mediant 1000 rear panel. A 40 Giga Byte Hard Disk Drive 5200 RPM. A second HDD is optional. Figure 2-15: HDMX Module HDD activity Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 41: Installation
3.1.4 on page 44). After powering-up the Mediant 2000, the Ready and LAN LEDs on the front panel turn to green (after a self-testing period of about 3 minutes). Any malfunction changes the Ready LED to red (refer to Section 2.2.1...
Page 42: Mounting The Mediant 2000
The Mediant 2000 Fast Track Installation Guide. Figure 3-1: 19-inch Rack & Desktop Accessories 3.1.3 Mounting the Mediant 2000 The Mediant 2000 can be mounted on a desktop, or installed in a standard 19-inch rack. Refer to Section 3.1.4 on page for cabling the Mediant 2000.
Page 43: Figure 3-2: Mediant 2000 Front View With 19-Inch Rack Mount Brackets
Mediant Series and TP-1610 H.323 User’s Manual 3. Installation Figure 3-2: Mediant 2000 Front View with 19-inch Rack Mount Brackets Rack Mount Safety Instructions (UL) When installing the chassis in a rack, be sure to implement the following Safety instructions recommended by Underwriters Laboratories: •...
Page 44: Cabling The Mediant 2000
Mediant 2000 rear panel connectors and LEDs. Note that the Mediant 2000 is available in many configurations, i.e., AC or DC, in the 16-trunk, 8-trunk, 4-trunk, 2-trunk or 1-trunk device. The 16-trunk dual AC...
Page 45: Connecting The E1/T1 Trunk Interfaces
3.1.4.1 below). Install the Ethernet connection (refer to Section 3.1.4.2 on page 46). Optionally, connect the Mediant 2000 RS-232 port to your PC (refer to Section 3.1.4.3 page 46). Connect the power supply (refer to Section 3.1.4.4 on page 47).
Page 46: Installing The Ethernet Connection
Mediant Series and TP-1610 H.323 With RJ-48c Connectors, take these 2 steps: Connect the E1/T1 trunk cables to the ports labeled ’Trunks 1 to 8’ (in the case of the 8-trunk device) on the RTM. Connect the other ends of the Trunk cables to the PBX/PSTN switch. RJ-48c trunk connectors are wired according to Figure 3-6 below.
Page 47: Connecting The Power Supply
Each of the dual power cables can be connected to different AC power phases. 3.1.4.4.2 Connecting the DC Power Supply To connect the Mediant 2000 to a DC power supply use one of these two options: • DC Terminal block with a screw connection type.
Page 48: Figure 3-10: Dc Terminal Block Crimp Connector
Mediant Series and TP-1610 H.323 When using a DC terminal block crimp connector, take these 3 steps: Remove the DC adaptor (screw connection type) that is attached to the Mediant 2000 rear panel. Connect the two insulated wires to the correct DC power supply. Ensure that the connections...
Page 49: Installing The Tp-1610
Open the carton and remove packing materials. Remove the TP-1610 board from the carton. Check that there is no equipment damage. Check, retain and process any documents. Notify AudioCodes or your local supplier of any damage or discrepancies. Retain any diskettes or CDs. 3.2.2 Package Contents Ensure that in addition to the TP-1610, the package contains: •...
Page 50: Inserting Boards
Mediant Series and TP-1610 H.323 Before removing or inserting boards from / to the chassis, attach a wrist strap Note 1: for electrostatic discharge (ESD) and connect it to the rack frame using an alligator clip. Do not set components down without protecting them with a static bag. Note 2: 3.2.3.1 Inserting Boards...
Page 51: Installing The Mediant 1000
Open the carton and remove packing materials. Remove the Mediant 1000 from the carton. Check that there is no equipment damage. Check, retain and process any documents. Notify AudioCodes or your local supplier of any damage or discrepancies. Retain any diskettes or CDs. 3.3.2 Package Contents Ensure that in addition to the Mediant 1000, the package contains: •...
Page 52: Installing The Mediant 1000 In A 19-Inch Rack
Mediant Series and TP-1610 H.323 3.3.3.2 Installing the Mediant 1000 in a 19-inch Rack Users can install the Mediant 1000 in a standard 19-inch rack either by placing it on a shelf preinstalled in the rack (preferred method), or by attaching it directly to the rack’s frame. If the rack is without shelves, it is advised to acquire shelves.
Page 53: Cabling The Mediant 1000
Mediant Series and TP-1610 H.323 User’s Manual 3. Installation 3.3.4 Cabling the Mediant 1000 Protective Earthing The equipment is classified as Class I EN60950 and UL60950 and must be earthed at all times. To protect against electrical shock and fire, use a 26 AWG min wire to connect T1 or E1 ports to the PSTN.
Page 54: Connecting The Mediant 1000 Rs-232 Port To Your Pc
Table 3-4: Dry Contact Wires’ Mate Component Descriptions Item # Component Description Position 4 4 spring-cage connections Orange Buttons: Press to open spring-cage connections Position 1 Not currently supported. Contact AudioCodes regarding availability. Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 55: Connecting The Audio In/Out Cable
The audio IN level must be below the AC signal 2V PTP (peak-to-peak). Audio OUT Level The audio OUT level is variable but must not exceed 3V PTP. Figure 3-15: Audio Cable and IN/OUT RCA Connectors Not currently supported. Contact AudioCodes regarding availability. Version 4.6 July 2005...
Page 56 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 57: Getting Started
Default subnet mask is 255.255.0.0, default gateway IP address is 0.0.0.0 Configuration Concepts Users can utilize the Mediant 2000 in a wide variety of applications, enabled by its parameters and configuration files (e.g., Call Progress Tones (CPT)). The parameters can be configured and configuration files can be loaded using: •...
Page 58: Assigning The Mediant 2000 Ip Address
Mediant Series and TP-1610 H.323 Assigning the Mediant 2000 IP Address To assign an IP address to each of the Mediant 2000 modules use one of the following methods: • HTTP using a Web browser (refer to Section 4.2.1 below).
Page 59: Assigning An Ip Address Using Bootp
Assigning an IP Address Using BootP BootP procedure can also be performed using any standard compatible Note: BootP server. You can also use BootP to load the auxiliary files to the Mediant 2000 (refer Tip: to Section 6.16 on page 158).
Page 60 Select the coder (i.e., vocoder) that best suits your VoIP system requirements. The default coder is: G.7231 30 msec. To program the entire list of coders you want the Mediant 2000 to use, click the button on the left side of the ‘1 Coder’...
Page 61: Web Management
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management Web Management The Embedded Web Server is used both for gateway configuration, including loading of configuration files, and for run-time monitoring. The Embedded Web Server can be accessed from a standard Web browser, such as Microsoft™ Internet Explorer, Netscape™ Navigator, etc. Specifically, users can employ this facility to set up the gateway configuration parameters.
Page 62: Limiting The Embedded Web Server To Read-Only Mode
Open a standard Web-browsing application such as Microsoft™ Internet Explorer™ or Netscape™ Navigator™. In the Uniform Resource Locator (URL) field, specify the IP address of the Mediant 2000 (e.g., http://10.1.10.10); the Embedded Web Server’s ‘Enter Network Password’ screen appears, shown in Figure 5-1.
Page 63: Using Internet Explorer To Access The Embedded Web Server
This fixes any issues related to domain use logon policy. 5.4 Getting Acquainted with the Web Interface Figure 5-2 shows the general layout of the Web Interface screen. Figure 5-2: Mediant 2000 Web Interface Main Menu MG Module Submenu Title Bar...
Page 64: Main Menu Bar
• Control Protocol – the Mediant 2000 control protocol. • MG Module – the Mediant 2000 media gateway module (Module 1 or Module 2). 5.4.1 Main Menu Bar The main menu bar of the Web Interface is divided into the following 7 menus: •...
Page 65: Protocol Management
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management Protocol Management Use this menu to configure the gateway’s H.323 parameters and tables. 5.5.1 Protocol Definition Parameters Use this submenu to configure the following gateway’s specific H.323 protocol parameters: • General Parameters •...
Page 66: Advanced Parameters
Mediant Series and TP-1610 H.323 5.5.2 Advanced Parameters Use this submenu to configure the following gateway’s advanced control protocol parameters. • Disconnect and Answer Supervision • CDR and Debug • Miscellaneous Parameters • Supplementary Services 5.5.3 Number Manipulation Tables The VoIP gateway provides four Number Manipulation tables for incoming and outgoing calls. These tables are used to modify the destination and source telephone numbers so that the calls can be routed correctly.
Page 67: Figure 5-4: Source Phone Number Manipulation Table For Tel Ip Calls
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management Figure 5-4: Source Phone Number Manipulation Table for Tel IP Calls In the ‘Table Index’ drop-down list, select the range of entries that you want to edit (up to 20 entries can be configured for Source Number Manipulation and 50 entries for Destination Number Manipulation).
Page 68: Dialing Plan Notation
Mediant Series and TP-1610 H.323 Table 5-1: Number Manipulation Parameters Parameter Description Number of digits to leave Enter the number of digits that you want to leave from the right. Note: The manipulation rules are executed in the following order: Num of stripped digits Number of digits to leave Prefix / suffix to add...
Page 69: Numbering Plan And Type Of Number
Numbering Plan and Type of Number Numbers are classified by their Numbering Plan Indication (NPI) and their Type of Number (TON). The Mediant 2000 supports all NPI/TON classifications used in the standard. The list of ISDN ETSI NPI/TON values is shown as follows:...
Page 70: Configuring The Routing Tables
Mediant Series and TP-1610 H.323 5.5.4 Configuring the Routing Tables Use this submenu to configure the gateway’s IP Tel and Tel IP routing tables and their associated parameters. 5.5.4.1 Tel to IP Routing Table The Tel to IP Routing Table is used to route incoming Tel calls to IP addresses. This routing table associates a called / calling telephone number’s prefixes with a destination IP address or with an FQDN (Fully Qualified Domain Name).
Page 71: Figure 5-5: Tel To Ip Routing Table Screen
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management Tel to IP routing can be performed either before or after applying the number Tip: manipulation rules. To control when number manipulation is done, set the RouteModeTel2IP parameter. For information on this parameter, refer to Table 6-8 on page 142.
Page 72: Ip To Trunk Group Routing Table
Mediant Series and TP-1610 H.323 Table 5-3: Tel to IP Routing Table Parameter Description Status A read only field representing the quality of service of the destination IP address. N/A = Alternative Routing feature is disabled. OK = IP route is available Ping Error = No ping to IP destination, route is not available QoS Low = Bad QoS of IP destination, route is not available DNS Error = No DNS resolution (only when domain name is used instead of an IP...
Page 73: Figure 5-6: Ip To Trunk Group Routing Table
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management Figure 5-6: IP to Trunk Group Routing Table In the ‘IP to Tel Routing Mode’ field, select the IP to Tel routing mode (refer to Table 6-8 page 142). In the ‘Routing Index’ drop-down list, select the range of entries that you want to edit (up to 24 entries can be configured).
Page 74: Internal Dns Table
Mediant Series and TP-1610 H.323 5.5.4.3 Internal DNS Table The internal DNS table, similar to a DNS resolution, translates hostnames into IP addresses. This table is used when hostname translation is required (e.g., ‘Tel to IP Routing’ table). Two different IP addresses can be assigned to the same hostname.
Page 75: Reasons For Alternative Routing
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management 5.5.4.4 Reasons for Alternative Routing The Reasons for Alternative Routing screen includes two tables (Tel IP and IP Tel). Each table enables you to define up to 4 different release reasons. If a call is released as a result of one of these reasons (received in Q.931 presentation), the gateway tries to find an alternative route to that call.
Page 76: Configuring The Profile Definitions
5.5.5 Configuring the Profile Definitions Utilizing the Profiles feature, the Mediant 2000 provides high-level adaptation when connected to a variety of equipment (from both Tel and IP sides) and protocols, each of which require a different system behavior. Using Profiles, users can assign different Profiles (behavior) on a per- call basis, using the Tel to IP and IP to Trunk Group Routing tables, or associate different Profiles to the gateway’s B-channels(s).
Page 77: Tel Profile Settings
Use the Tel Profile Settings screen to define up to four different Tel Profiles. These Profiles are used in the ‘Trunk Group’ table to associate different Profiles to gateway’s B-channels, thereby applying different behavior to different Mediant 2000 B-channels. To configure the Tel Profile settings, take these 8 steps: Open the ‘Tel Profile Settings’...
Page 78: Ip Profile Settings
Mediant Series and TP-1610 H.323 Note: If the coder lists of both IP and Tel Profiles apply to the same call, an intersection of the coders is performed (i.e., only common coders remain). The order of the coders is determined by the preference. Configure the Profile’s parameters according to your requirements.
Page 79 Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management In the ‘Profile Preference’ drop-down list, select the preference (1-10) of the current Profile. The preference option is used to determine the priority of the Profile. If both IP and Tel profiles apply to the same call, the coders and other common parameters of the preferred Profile are applied to that call.
Page 80: Configuring The Registration Prefixes Table
In this registration mode the ‘Type of Number’ columns are used, to define the prefix’s TON. In other modes (GwRegistrType = 0, 1 or 2), the TON column is ignored. For detailed information on the available methods the Mediant 2000 gateway registers with a Gatekeeper, refer to Section on page 168.
Page 81: Table 5-5: Registration Prefixes Table
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management Table 5-5: Registration Prefixes Table Parameter Description Gatekeeper Registration Prefixes Enter the Gatekeeper Registration prefixes. These prefixes are used by the VoIP gateway to register to a Gatekeeper. When entering a prefix, you can create an entry that represents multiple prefixes using the following notation: n-m represents a range of numbers.
Page 82: Configuring The Trunk Group Table
Mediant Series and TP-1610 H.323 5.5.7 Configuring the Trunk Group Table Use the Trunk Group table to assign trunk groups, profiles and logical telephone numbers to the gateway's E1/T1 B-channels. Trunk Groups are used for routing IP Tel calls with common rules. Channels that are not defined are disabled.
Page 83: Trunk Group Settings
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management Table 5-6: Trunk Group Table Parameter Description Trunk Group ID In each of the Trunk Group ID fields, enter the trunk group ID (1-99) assigned to the channels. The same trunk group ID can be used for more than one group of channels. Trunk group ID is used to define a group of common behavior channels that are used for routing IP to Tel calls.
Page 84: Table 5-7: Channel Select Modes
Mediant Series and TP-1610 H.323 In the Channel Select Mode drop-down list, select the Channel Select Mode that determines the method in which new calls are assigned to B-channels within the Trunk groups entered in the field to the right of this field. For information on available Channel Select Modes, refer to Table 5-7.
Page 85: Advanced Configuration
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management Advanced Configuration Use this menu to set the gateway’s advanced configuration parameters (for advanced users only). 5.6.1 Configuring the Network Settings From the Network Settings you can: • Define the IP Settings. •...
Page 86: Configuring The Web And Telnet Access List
Mediant Series and TP-1610 H.323 5.6.1.2 Configuring the Web and Telnet Access List Use this screen to define up to ten IP addresses that are permitted to access the gateway’s Web and Telnet interfaces. Access from an undefined IP address is denied. This security feature is inactive (the gateway can be accessed from any IP address) when the table is empty.
Page 87: Table 5-8: Ip Routing Table Column Description
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management Figure 1-3: IP Routing Table Screen Use the ‘Add a new table entry’ pane to add a new routing rule. Each field in the IP routing table is described in Table 5-8.
Page 88: Viewing The Ethernet Port Information
5.6.1.4 Viewing the Ethernet Port Information The Ethernet Port Information screen provides read-only information on the Ethernet connection used by the Mediant 2000. The Ethernet Port Information parameters are displayed in Table 5-9. For detailed information on the Ethernet redundancy scheme, refer to Section on page 177.
Page 89: Configuring The Trunk Settings
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management 5.6.3 Configuring the Trunk Settings To configure the Trunk Settings, take these 9 steps: Open the ‘Trunk Settings’ screen (Advanced Configuration menu > Trunk Settings); the ‘Trunk Settings’ screen is displayed. Initially, the screen appears with the parameters fields grayed (indicating read-only).
Page 90: Table 5-10: Trunks Status Color Indicator Keys
If the trunk can’t be stopped because it provides the gateway’s clock Note: (assuming the Mediant 2000 is synchronized with the E1/T1 clock), assign a different E1/T1 trunk to provide the gateway’s clock or enable ‘TDM Bus PSTN Auto Clock’ on the TDM Bus Settings screen.
Page 91: Configuring The Tdm Bus Settings
110. Some parameter configuration options require a device reset; when this is the Note: case, the Web Interface prompts the user. To reset the Mediant 2000, refer to Section on page 110. 5.6.4 Configuring the TDM Bus Settings To configure the TDM Bus Settings parameters, take these 5 steps: Open the ‘TDM Bus Settings’...
Page 92: Restoring And Backing Up The Gateway Configuration
Mediant Series and TP-1610 H.323 5.6.5 Restoring and Backing Up the Gateway Configuration The Configuration File screen enables you to restore (load a new ini file to the gateway) or to back up (make a copy of the VoIP gateway ini file and store it in a directory on your computer) the current configuration the gateway is using.
Page 93: Regional Settings
Prompts. For detailed information on the configuration files, refer to Section on page 247. To configure the date and time of the Mediant 2000, take these 3 steps: Open the ‘Regional Settings’ screen (Advanced Configuration menu > Regional Settings); the ‘Regional Settings' screen is displayed.
Page 94: Changing The Mediant 2000 Username And Password
Note 2: To save the loaded auxiliary files so they are available after a power fail, refer to Section on page 110. To reset the Mediant 2000, refer to Section on page 110. 5.6.7 Changing the Mediant 2000 Username and Password To prevent unauthorized access to the Embedded Web Server, two levels of security are available: Administrator and Monitoring.
Page 95: Status & Diagnostic
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management Status & Diagnostic Use this menu to view and monitor the gateway’s channels, Syslog messages, hardware / software product information, and to assess the gateway’s statistics and IP connectivity information. 5.7.1 Gateway Statistics Use the screens under Gateway Statistics to monitor real-time activity such as IP Connectivity...
Page 96: Call Counters
Mediant Series and TP-1610 H.323 Table 5-11: IP Connectivity Parameters Column Name Description IP address defined in the destination IP address field in the Tel to IP Routing table. IP Address IP address that is resolved from the host name defined in the destination IP address field in the Tel to IP Routing table.
Page 97: Figure 5-24: Tel Ip Call Counters Screen
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management Figure 5-24: Tel IP Call Counters Screen Table 5-12: Call Counters Description (continues on pages 97 to 98) Counter Description This counter indicates the number of attempted calls. It is composed of established and failed calls. The number of established calls is Number of Attempted represented by the ‘Number of Established Calls’...
Page 98: Call Routing Status
Mediant Series and TP-1610 H.323 Table 5-12: Call Counters Description (continues on pages 97 to 98) Counter Description This counter indicates the number of calls that failed due to mismatched gateway Number of Failed Calls capabilities. It is incremented as a result of an internal identification of capability due to No Matched mismatch.
Page 99: Monitoring The Mediant 2000 Trunks & Channels
Open the ‘Trunk & Channel Status’ screen (Status & Diagnostics menu > Channel Status); the ‘Trunk & Channel Status’ screen is displayed. Figure 5-26: Mediant 2000 Trunk & Channel Status Screen The number of trunks and channels that appear on the screen depends on the system configuration.
Page 100: Figure 5-28: Channel Status Details Screen
Mediant Series and TP-1610 H.323 Click the submenu links to check/view a specific channel’s parameter settings. Figure 5-28: Channel Status Details Screen Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 101: Activating The Internal Syslog Viewer
Do not keep the ‘Message Log’ screen minimized for a prolonged period as a Tip: prolonged session may cause the Mediant 2000 to overload. As long as the screen is open (even if minimized), a session is in progress and messages are sent.
Page 102: Device Information
Capture the screen and email it to ‘our’ Technical Support personnel to ensure quick diagnosis and effective corrective action. From this screen you can also view and remove any loaded files used by the Mediant 2000 (stored in the RAM).
Page 103: Front Panel View (Mediant 1000 Only)
Mediant Series and TP-1610 H.323 User’s Manual 5. Web Management 5.7.5 Front Panel View (Mediant 1000 Only) The Front Panel View screen displays the configuration of the Mediant 1000 in real time (the number of installed modules and the number of trunks on each module). For information on the trunk’s status indicators, refer to Table 5-10 on page...
Page 104: Software Update Menu
Mediant Series and TP-1610 H.323 Software Update Menu The ‘Software Update’ menu enables users to upgrade the Mediant 2000 software by loading a new cmp file along with the ini and a suite of auxiliary files, or to update the existing auxiliary files.
Page 105: Figure 5-33: Load A Cmp File Screen
Figure 5-33: Load a cmp File Screen Click the Browse button, navigate to the cmp file and click the button Send File; the cmp file is loaded to the Mediant 2000 and you’re notified as to a successful loading (refer to Figure 5-34).
Page 106: Figure 5-35: Load An Ini File Screen
Note that these are NOT the files you loaded in the previous Wizard steps. Click Reset; the Mediant 2000 resets, utilizing the new cmp and ini file you loaded up to now as well as utilizing the other configuration files.
Page 107: Figure 5-36: Load A Cpt File Screen
Reset or Cancel. Button Result The Mediant 2000 ‘burns’ the newly loaded files to flash memory. The ‘Burning files to flash Reset memory’ screen appears. Wait for the ‘burn’ to finish. When it finishes, the ‘End Process’...
Page 108: Auxiliary Files
These files are provided to support various types of CAS signaling. The voice announcement file contains a set of Voice Prompts to be played by the Voice Prompts Mediant 2000 during operation. Applicable only to the VXML application. This is a region-specific, telephone exchange-dependent file that contains the Call Call Progress Progress Tones levels and frequencies that the VoIP gateway uses.
Page 109: Updating The Software Upgrade Key
The Software Upgrade Key is sent as a string in a text file, to be loaded into the Mediant 2000. Stored in the device’s non-volatile flash memory, the string defines the features and capabilities allowed by the specific key purchased by the user.
Page 110: Save Configuration
Mediant Series and TP-1610 H.323 Save Configuration The Save Configuration screen enables users to save the current parameter configuration and the loaded auxiliary files to the non-volatile memory so they are available after a power fail. Parameters that are only saved to the volatile memory revert to their previous settings after hardware reset.
Page 111: Resetting The Mediant 2000
The Reset screen enables you to remotely reset the gateway. Before reset you can choose to save the gateway configuration to flash memory. To reset the Mediant 2000, take these 3 steps: Click the Reset button on the main menu bar; the Reset screen is displayed.
Page 112 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 113: Ini File Configuration Of The Mediant 2000
Therefore an encoded ini file significantly reduces these threats. You can choose to load an encoded ini file to the Mediant 2000. When you load an encoded ini file, the retrieved ini file is also encoded. Use the ‘TrunkPack Downloadable Conversion Utility’ to encode or decode the ini file before you load it to, or retrieve it from, the device.
Page 114: The Ini File Content
Mediant Series and TP-1610 H.323 The ini File Content The ini file contains the following H.323 gateway information: • Networking parameters shown in Table 6-1 on page 116. • System parameters shown in Table 6-2 on page 119. • Web and Telnet parameters shown in Table 6-3 on page 123.
Page 115: The Ini File Examples
Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 • String parameters, representing file names, for example CallProgressTonesFileName, must be placed between two inverted commas (‘…’). • The parameter name is NOT case-sensitive; the parameter value is not case-sensitive except for coder names.
Page 116: Networking Parameters
Mediant Series and TP-1610 H.323 Networking Parameters Table 6-1: Networking Parameters (continues on pages 116 to 118) ini File Field Name Valid Range and Description Web Parameter Name 0 = 10 Base-T half-duplex EthernetPhyConfiguration 1 = 10 Base-T full-duplex 2 = 100 Base-TX half-duplex 3 = 100 Base-TX full-duplex 4 = auto-negotiate (default) For detailed information on Ethernet interface configuration, refer to Section...
Page 117 Note 1: Syslog messages may increase the network traffic. Note 2: To configure the Syslog logging levels use the parameter ‘GwDebugLevel’. Starting UDP port for RTP channels. Should be above 4000 for Mediant 2000 H.323 BaseUDPport [RTP Base UDP Port] gateways.
Page 118 Mediant Series and TP-1610 H.323 Table 6-1: Networking Parameters (continues on pages 116 to 118) ini File Field Name Valid Range and Description Web Parameter Name Determines the remote UDP port the multiplexed RTP packets are sent to, and the L1L1ComplexRxUDPPort [RTP Multiplexing Remote UDP local UDP port used for incoming multiplexed RTP packets (applies to the...
Page 119: System Parameters
Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 System Parameters Table 6-2: System Parameters (continues on pages 119 to 122) ini File Field Name Valid Range and Description Web Parameter Name Tests the correct functionality of the different hardware components on the EnableDiagnostics gateway.
Page 120 Mediant Series and TP-1610 H.323 Table 6-2: System Parameters (continues on pages 119 to 122) ini File Field Name Valid Range and Description Web Parameter Name Defines the destination IP address for CDR logs. CDRSyslogServerIP [CDR Server IP Address] The default value is a null string that causes the CDR messages to be sent with all Syslog messages.
Page 121 Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-2: System Parameters (continues on pages 119 to 122) ini File Field Name Valid Range and Description Web Parameter Name Automatic Update Parameters Specifies the name of the cmp file and the location of the server (IP address CmpFileURL or FQDN) from which the gateway loads a new cmp file and updates itself.
Page 122 Mediant Series and TP-1610 H.323 Table 6-2: System Parameters (continues on pages 119 to 122) ini File Field Name Valid Range and Description Web Parameter Name BootP and TFTP Parameters The BootP parameters are special ‘Hidden’ parameters. Once defined and saved in the flash memory, they are used even if they don't appear in the ini file.
Page 123: Web And Telnet Parameters
Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 Web and Telnet Parameters Table 6-3: Web and Telnet Parameters (continues on pages 123 to 124) ini File Field Name Valid Range and Description Web Parameter Name Defines up to ten IP addresses that are permitted to access the gateway’s Web and...
Page 124 Name of the image file containing the user’s logo. LogoFileName File name can be up to 47 characters. The logo file name can be used to replace AudioCodes’ default Web logo with a user defined logo. Use a gif, jpeg or jpg image file.
Page 125: Radius Parameters
Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 RADIUS Parameters For detailed information on the supported RADIUS attributes, refer to Section 8.10 on page 173. Table 6-4: RADIUS Parameter ini File Field Name...
Page 126: Snmp Parameters
Mediant Series and TP-1610 H.323 6.10 SNMP Parameters Table 6-5: SNMP Parameter (continues on pages 126 to 127) ini File Field Name Valid Range and Description Web Parameter Name 0 = SNMP is enabled (default). DisableSNMP [Enable SNMP] 1 = SNMP is disabled and no traps are sent. The device’s local UDP port used for SNMP Get/Set commands.
Page 127 Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-5: SNMP Parameter (continues on pages 126 to 127) ini File Field Name Valid Range and Description Web Parameter Name SNMPReadWriteCommunityString_x Read-write community string (up to 19 chars).
Page 128: Configuration Parameters
3 = NPI/TON from Table (applicable only when registration prefixes are defined) 4 = NPI/TON and H323-ID (applicable only when registration prefixes are defined) For detailed information on the available methods the Mediant 2000 gateway registers with a Gatekeeper, refer to Section on page 168.
Page 129 Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-6: H.323 Configuration Parameters (continues on pages 128 to 137) ini File Field Name Valid Range and Description Web Parameter Name Definition of gateway H.323-ID for registration to Gatekeeper.
Page 130 Mediant Series and TP-1610 H.323 Table 6-6: H.323 Configuration Parameters (continues on pages 128 to 137) ini File Field Name Valid Range and Description Web Parameter Name 0 = Disabled (default) EnableH235Security [Enable H.235 Security] 1 = H.235 Security Annex D Procedure 1 is enabled Username string up to 20 characters for H.235 security.
Page 131 Fast Start call using ‘Transparent’ coder (even if the coder is not included in the coders list). This option is an AudioCodes’ proprietary feature that requires the use of Fast Start mode and the inclusion of the ‘Transparent’ coder in the coder list of the receiving side.
Page 132 0 = Disable call forward (default) EnableForward [Enable Call Forward] 1 = Enable call forward service (H.450.3). The Mediant 2000 doesn't initiate call forward, it can only respond to call forward requests. 0 = Disabled (default) EnableCallWaiting [Enable Call Waiting]...
Page 133 Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-6: H.323 Configuration Parameters (continues on pages 128 to 137) ini File Field Name Valid Range and Description Web Parameter Name Table parameter (up to 4 instances) that defines the supported Transmit DTMF TxDTMFOption –...
Page 134 (except RTP ports) starting from H323Baseport to H323BasePort + 2000. For example if H323BasePort = 10000. Mediant 2000 gateway uses dynamic ports within the range 10000 to 12000. These ports are used for RAS, H.225 and H.245 protocols, not including RTP ports.
Page 135 Note: For incoming IP Tel calls, if the called number includes the characters ‘w’ or ‘p’, the Mediant 2000 gateway places a call with the first part of the called number, and plays DTMF digits after receiving a CONNECT message. If the character ‘p’...
Page 136 Mediant Series and TP-1610 H.323 Table 6-6: H.323 Configuration Parameters (continues on pages 128 to 137) ini File Field Name Valid Range and Description Web Parameter Name TelProfile_<Profile ID> = TelProfile_ID [Tel Profile Settings] <Profile Name>,<Preference>,<Coder Group ID>,<IsFaxUsed *>,<DJBufMinDelay *>, <DJBufOptFactor *>,<IPDiffServ *>,<ControlIPDiffServ*>,<DtmfVolume>,<InputGain>, <VoiceVolume>, <EnableDigitDelivery>, <ECE>...
Page 137 Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-6: H.323 Configuration Parameters (continues on pages 128 to 137) ini File Field Name Valid Range and Description Web Parameter Name Coder list for Profiles (up to five coders in each group).
Page 138: Isdn And Cas Interworking-Related Parameters
B-channel that the call originates from. The IP to Trunk Group routing table is used to define the destination IP address of the terminating Mediant 2000. The terminating Mediant 2000 gateway automatically answers these calls if its E1/T1 protocol is set to ‘Transparent’ (ProtocolType = 5).
Page 139 Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-7: ISDN and CAS Interworking-Related Parameters (continues on pages 138 to 141) ini File Field Name Valid Range and Description Web Parameter Name PlayRBTone2Tel 0 (Don't play) = The ISDN / CAS gateway doesn’t play a Ringback Tone (RBT).
Page 140 Mediant Series and TP-1610 H.323 Table 6-7: ISDN and CAS Interworking-Related Parameters (continues on pages 138 to 141) ini File Field Name Valid Range and Description Web Parameter Name 0 = No PI is sent in H.225 messages ProgressIndicator2IP [Progress Indicator to IP] 1 = PI = 1 is sent to IP in H.225 Alert 8 = PI = 8 is sent to IP in H.225 Alert If not configured (default), the PI sent in H.225 messages is set according to ‘Play...
Page 141 ISDNJapanNTTTimerT3JA This parameter overrides the internal PSTN T301 timeout on the Users Side (TE side). If an outgoing call from the Mediant 2000 to ISDN is not answered during this timeout, the call is released. The valid range is 10 to 240. The default value is 50.
Page 142: Number Manipulation And Routing Parameters
3 span, and 72 to 95 for 4 span. It is suggested to use Trunk Groups in Mediant 2000 gateway to define enabled B-channels, instead of ChannelList parameter. Defines the telephone number that the gateway uses if the parameters...
Page 143 Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-8: Number Manipulation and Routing Parameters (continues on pages 142 to 148) ini File Field Name Valid Range and Description Web Parameter Name Defines common rule of port allocation for IP to TEL calls.
Page 144 Mediant Series and TP-1610 H.323 Table 6-8: Number Manipulation and Routing Parameters (continues on pages 142 to 148) ini File Field Name Valid Range and Description Web Parameter Name Prefix = <Destination Phone Prefix>, <IP Address>,<Src Phone Prefix>,<IP Prefix [Tel to IP Routing Table] Profile ID>...
Page 145 Note 1: This parameter can appear up to 5 times. Note 2: If the Mediant 2000 fails to establish a cal to the PSTN because it has no available channels in a specific trunk group (e.g., all of the trunk group’s channels are occupied, or the trunk group’s spans are disconnected or out of...
Page 146 Mediant Series and TP-1610 H.323 Table 6-8: Number Manipulation and Routing Parameters (continues on pages 142 to 148) ini File Field Name Valid Range and Description Web Parameter Name Manipulate the destination number for IP to Tel calls. NumberMapIP2Tel [Destination Phone Number NumberMapIP2Tel = a,b,c,d,e,f,g,h,i Manipulation Table for IP Tel calls]...
Page 147 Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-8: Number Manipulation and Routing Parameters (continues on pages 142 to 148) ini File Field Name Valid Range and Description Web Parameter Name Manipulate the source number for IP to Tel calls.
Page 148 Mediant Series and TP-1610 H.323 Table 6-8: Number Manipulation and Routing Parameters (continues on pages 142 to 148) ini File Field Name Valid Range and Description Web Parameter Name 0 = Disabled (default) FilterCalls2IP [Filter Calls To IP] 1 = Enabled If the filter calls to IP feature is enabled, then when a Gatekeeper is used, the gateway first checks the Tel IP routing table before making a call through the Gatekeeper.
Page 149: E1/T1 Configuration Parameters
1 = ISDN Network Termination Side (NT) Note: select ‘User Side’ when the PSTN or PBX side is configured as ‘Network side’, and vice-versa. If you don’t know the Mediant 2000 ISDN termination side, choose ‘User Side’ and refer to the ‘Status & Diagnostics>Channel Status’ screen.
Page 150 Mediant Series and TP-1610 H.323 Table 6-9: E1/T1 Configuration Parameters (continues on pages 149 to 153) ini File Field Name Valid Range and Description Web Parameter Name Same as the description for parameter ‘TerminationSide’ for a specific trunk ID (x = TerminationSide_x [ISDN Termination Side] 0 to 7).
Page 151 Dialing] Any number bigger than one = Number of digits to receive. Note 1: If enabled, the Mediant 2000 receives ISDN called number that is sent in the ‘Overlap’ mode. Note 2: The Setup to IP is sent only after the number (including ‘Sending Complete’...
Page 152 Mediant Series and TP-1610 H.323 Table 6-9: E1/T1 Configuration Parameters (continues on pages 149 to 153) ini File Field Name Valid Range and Description Web Parameter Name Defines the maximum number of collected destination number digits received from MaxDigits [Max Digits in Phone Number for the ISDN when Tel IP overlap dialing is performed.
Page 153 Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-9: E1/T1 Configuration Parameters (continues on pages 149 to 153) ini File Field Name Valid Range and Description Web Parameter Name 1 = Q.931 Status message isn’t sent if Q.931 received message contains an ISDNIBehavior [Q.931 Layer Response Behavior]...
Page 154: Channel Parameters
Section page for detailed description on DTMF transport modes. Note that the Default Channel Parameters are applied to all Mediant 2000 channels. Table 6-10: Channel Parameters (continues on pages 154 to 157) ini File Field Name...
Page 155 Some gateways do not support the detection of this fax signal on the answering side. For these cases, it is possible to configure the Mediant 2000 gateways to start the T.38 fax session when the CNG tone is detected by the originating side.
Page 156 [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 is using payload type 101 for RFC 2833. 0 = DTMF event is reported on the start of a detected DTMF digit.
Page 157 Mediant Series and TP-1610 H.323 User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-10: Channel Parameters (continues on pages 154 to 157) ini File Field Name Valid Range and Description Web Parameter Name Enables / disables the automatic mute of DTMF digits when out-of-band DTMF DisableAutoDTMFMute transmission is used.
Page 158: Configuration Files Parameters
Mediant Series and TP-1610 H.323 6.16 Configuration Files Parameters The configuration files (Call Progress Tones and CAS) can be loaded to the Mediant 2000 via the Embedded Web Server (refer to Section 5.8.2 on page 108), or via TFTP session.
Page 159: Using Bootp / Dhcp
IP address, subnet mask - These mandatory parameters are sent to the Mediant 2000 every time a BootP/DHCP process occurs. • Default gateway IP address - An optional parameter that is sent to the Mediant 2000 only if configured in the BootP/DHCP server. •...
Page 160: Using Bootp
(to verify that the gateway is still connected to the same network). When DHCP is enabled, the gateway also includes its product name (e.g., ‘Mediant 2000’) in the DHCP ‘option 60’ Vendor Class Identifier. The DHCP server can use this product name to assign an IP address accordingly.
Page 161: Vendor Specific Information Field
7. Using BootP / DHCP 7.3.2 Vendor Specific Information Field The Mediant 2000 uses the vendor specific information field in the BootP request to provide device-related initial startup information. The BootP/TFTP configuration utility displays this information in the ‘Client Info’ column (refer to Figure B-1).
Page 162 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 163: Telephony Capabilities
The party that initiates the hold is called the holding party, the other party is called the held party. The Mediant 2000 can't initiate the hold, but it can respond to hold request, and as such it is a held party.
Page 164: Call Forward
C immediately without speaking with C. The result of the transfer is a call between B and C (just like consultation transfer only skipping the consultation stage). The Mediant 2000 doesn't initiate call transfer, it only can respond to call transfer request. 8.1.3 Call Forward There are three kinds of call forwards: Immediate –...
Page 165: Configuring The Dtmf Transport Types
8.2.1 Overview of In-Band DTMF Transport Types The Mediant 2000 gateway controls the way DTMF digits are transferred in-band (as part of the audio stream) using the DTMFTransport configuration parameter. Note that this parameter is automatically updated in the first four methods described in the previous section and therefore shouldn’t be changed, while, for the fifth method (in-band DTMF) it...
Page 166: Fax & Modem Transport Modes
Mediant Series and TP-1610 H.323 should normally be set to Transparent. The following four modes are supported: • DTMFTransportType = 0 (Mute DTMF). In this mode DTMF digits are erased from the audio stream and are not relayed to the remote side. Instead silence is sent in the RTP stream. •...
Page 167: Supporting V.34 Faxes
Mediant Series and TP-1610 H.323 User’s Manual 8. Telephony Capabilities FaxModemBypassM configuration parameter. The network packets to be generated and received during the bypass period are regular voice RTP packets (per the selected bypass coder) but with a different RTP Payload type. When fax/modem transmission ends, the reverse is carried out, and bypass coder is switched to regular voice coder.
Page 168: Redundant Gatekeeper Implementation
If none of the Gatekeepers respond, the gateway goes over the list again and works with the first responsive Gatekeeper. The Mediant 2000 gateway can fallback to the internal ‘Tel to IP Routing’ table when communication with Gatekeepers is lost. If this option is enabled (IsFallbackUsed=1), the Mediant 2000 starts using its internal routing table, and works without a Gatekeeper.
Page 169: Registration With H.323-Id
Mediant Series and TP-1610 H.323 User’s Manual 8. Telephony Capabilities E.164 and H323-ID [2] = The gateway registers the prefixes using E.164 and H.323-ID formats. In this mode the H323IDString (if defined) is added once to the Registration Request; if not defined, each prefix registers twice, in E.164 format and H.323-ID format (as a string).
Page 170: Configuring The Gateway's Alternative Routing (Based On Connectivity And Qos)
Fallback). 8.8.1 Alternative Routing Mechanism When a Tel IP call is routed through the Mediant 2000 gateway, the call’s destination number is compared to the list of prefixes defined in the Tel to IP Routing table (described in Section 5.5.4.1 on page 70).
Page 171: Determining The Availability Of Destination Ip Addresses
If no call statistics are received for two minutes, the QoS information is reset. The Mediant 2000 gateway matches the rules starting at the top of the table. For this reason, enter the main IP route above any alternative route.
Page 172: Call Detail Report
Mediant Series and TP-1610 H.323 Call Detail Report The Call Detail Report (CDR) contains vital statistic information on calls made by the gateway. CDRs are generated at the end and (optionally) at the beginning of each call (determined by the ’...
Page 173: Supported Radius Attributes
8.10 Supported RADIUS Attributes Table 8-2 below for explanations on the RADIUS attributes contained in the communication packets transmitted between the Mediant 2000 and a RADIUS Server. Table 8-2: Supported RADIUS Attributes (continues on pages 173 to 174) Attribute Value...
Page 174: Radius Server Messages
Stop Acc Packets during the call Acct-Output- Number of packets sent Numeric Stop Acc Packets during the call Mediant 2000 physical port Start Acc String NAS-Port-Type type on which the call is Asynchronou Stop Acc active Response Attributes The reason for failing...
Page 175: Trunk To Trunk Routing Example
8. Telephony Capabilities 8.11 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 176 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 177: Networking Capabilities
Ethernet configuration. Ethernet Interface Redundancy The Mediant 2000 supports the following redundancy scheme: At the beginning of the start-up procedure, the gateway tests whether the ‘Primary’ Ethernet interface is connected by checking the existence of the Ethernet link carrier. If it is connected, the start-up procedure commences as usual.
Page 178: Nat (Network Address Translation) Support
NAT architecture. Figure 9-1: NAT Functioning If the remote gateway resides behind a NAT device, it’s possible that the Mediant 2000 can activate the RTP/RTCP/T.38 streams to an invalid IP address / UDP port. To avoid such cases, the Mediant 2000 automatically compares the source address of the incoming RTP/RTCP/T.38...
Page 179: Multiple Routers Support
Mediant Series and TP-1610 H.323 User’s Manual 9. Networking Capabilities • The new packet has a source IP address and UDP port which are the same as the remote IP address and UDP port that were stated during the opening of the channel. In this case, the gateway reverts to this new RTP stream.
Page 180 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 181: Advanced Pstn Configuration
(or several at a time). As opposed to the enbloc dialing scheme in which a complete number is sent. The Mediant 2000 can optionally support ISDN overlap dialing for incoming ISDN calls for the entire gateway by setting ‘ISDNRxOverlap’ to 1, or per E1/T1 span by setting ‘ISDNRxOverlap_x’...
Page 182: Using Isdn Nfas
(0 to 7). For example, to assign the first four Mediant 2000 T1 trunks to NFAS group #1, in which trunk #0 is the primary trunk and trunk #1 is the backup trunk, use the following configuration:...
Page 183: Nfas Interface Id
Note: In the current version, the Mediant 2000 doesn’t support the DMS-100 Backup trunk. Therefore, InterfaceID #1, should not be used. For example, if four T1 trunks on a Mediant 2000 are configured as a single NFAS group, that is used with a DMS-100 switch, the following parameters should be used:...
Page 184: Redirect Number And Calling Name (Display)
Mediant Series and TP-1610 H.323 10.4 Redirect Number and Calling Name (Display) The following tables define the Mediant 2000 redirect number and calling name (Display) support for various PRI variants: Table 10-1: Calling Name (Display) DMS-100 NI-2 4/5ESS Euro ISDN...
Page 185: Advanced System Capabilities
Use serial communication software (e.g., HyperTerminal ) to establish a serial communications link with the Mediant 2000 via the RS-232 connection. You can use this link to access the CLI (Section on page 229) and to receive error / notification messages.
Page 186: Automatic Update Mechanism
To establish a serial communications link with the Mediant 2000 via the RS-232 port, take these 2 steps: Connect the RS-232 port to your PC (For the Mediant 2000 / TP-1610, refer to Section 3.1.4.3 on page 46. For the Mediant 1000, refer to Section 3.3.4.1...
Page 187: Figure 11-2: Example Of An Ini File Activating The Automatic Update Mechanism
To automatically update the cmp file, use the parameter ‘CmpFileURL’ to specify its name and location. As a precaution (in order to protect the Mediant 2000 from an accidental update) the Automatic Update mechanism doesn’t apply to the cmp file by default.
Page 188: Startup Process
# The device resets after all of the files are processed. ResetNow = 1 You can modify the master_configuration.ini file (or any of the config_<MAC>.ini files) at any time. The Mediant 2000 queries for the latest version every 60 minutes and applies the new settings immediately. 11.4 Startup Process...
Page 189: Figure 11-3: Mediant 2000 Startup Process
Mediant Series and TP-1610 H.323 User’s Manual 11. Advanced System Capabilities Figure 11-3: Mediant 2000 Startup Process Reset from the Web Physical Reset Interface or SNMP DHCP BootP x times x times Response Response BootP Response DHCP Response Update network...
Page 190: Using Parameter Tables
Parameter tables are only used for SS7 tunneling. Note: The Mediant 2000 uses parameter tables to group related parameters of specific entities and manage them together. These tables, similar to regular parameters, can be configured via the ini file, Embedded Web Server, SNMP, etc.
Page 191: Table Permissions
Mediant Series and TP-1610 H.323 User’s Manual 11. Advanced System Capabilities 11.5.2 Table Permissions Each column has a 'permission' attribute that is applied to all instances in the column. This permission determines if and when a field can be modified. Several permissions can be applied to each column.
Page 192: Using The Ini File To Configure Parameter Tables
Mediant Series and TP-1610 H.323 11.5.5 Using the ini File to Configure Parameter Tables You can use the ini file to add / modify parameter tables. When using tables, Read-Only parameters are not loaded, as they cause an error when trying to reload the loaded file. Therefore, Read-Only parameters mustn’t be included in tables in the ini file.
Page 193 Mediant Series and TP-1610 H.323 User’s Manual 11. Advanced System Capabilities Refer to the following notes: • Indices (in both the Format and the Data lines) must appear in the same order determined by the specific table's documentation. The Index field must never be omitted. •...
Page 194: Customizing The Mediant 2000 Web Interface
Mediant Series and TP-1610 H.323 11.6 Customizing the Mediant 2000 Web Interface Customers incorporating the Mediant 2000 into their portfolios can customize the Web Interface to suit their specific corporate logo and product naming conventions. Customers can customize the Web Interface’s title bar (AudioCodes’ title bar is shown in Figure 11-5;...
Page 195: Figure 11-7: Image Download Screen
Mediant Series and TP-1610 H.323 User’s Manual 11. Advanced System Capabilities Figure 11-7: Image Download Screen Click the Browse button in the Send Logo Image File from your computer to the Device box. Navigate to the folder that contains the logo image file you want to load. Click the Send File button;...
Page 196: Replacing The Main Corporate Logo With A Text String
Section 11.6.3.1 page 198. • To replace AudioCodes’ default logo with a text string via the ini file, add/modify the two ini file parameters in Table 11-4 according to the procedure described in Section on page 113.
Page 197: Customizing The Product Name
Section 11.6.3.1 on page 198. • To replace AudioCodes’ default product name with a text string via the ini file, add/modify the two ini file parameters in Table 11-6 according to the procedure described in Section page 113.
Page 198: Modifying Ini File Parameters Via The Web Adminpage
11.6.3.1 Modifying ini File Parameters via the Web AdminPage To modify ini file parameters via the AdminPage, take these 6 steps: Access the Mediant 2000 Embedded Web Server (refer to Section on page 62). In the URL field, append the suffix ‘AdminPage’ (note that it’s case-sensitive) to the IP address, e.g., http://10.1.229.17/AdminPage.
Page 199: Software Upgrade Key
11. Advanced System Capabilities 11.7 Software Upgrade Key Mediant 2000 gateways are supplied with a Software Upgrade Key already pre-configured for each of its TrunkPack Module (TPM). Users can later upgrade their Mediant 2000 features, capabilities and quantity of available resources by specifying what upgrades they require, and purchasing a new key to match their specification.
Page 200: Loading The Software Upgrade Key Using The Embedded Web Server
Mediant Series and TP-1610 H.323 11.7.2.1 Loading the Software Upgrade Key Using the Embedded Web Server To load a Software Upgrade Key using the Web Server, take these 5 steps: Access the devices Embedded Web Server (refer to Section on page 62). Click the Software Update button.
Page 201: Loading The Software Upgrade Key Using Bootp/Tftp
• Open the Software Upgrade Key file and check that the S/N line of the specific device whose key you want to update is listed in it. If it isn’t, contact AudioCodes. • Verify that you’ve loaded the correct file and that you haven’t loaded the device’s ini file or the CPT ini file by mistake.
Page 202 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 203: Special Applications
‘broken’ connections. In addition, when a failure in a physical trunk or in the IP network occurs, the Mediant 2000 gateways reestablish the tunneling connections as soon as the network restores.
Page 204: Figure 12-1: Ini File Example For Tdm Tunneling (Originating Side)
ProtocolType_1 = 5 ProtocolType_2 = 5 ProtocolType_3 = 5 prefix = '*,10.8.24.12' ;(IP address of the Mediant 2000 in the opposite location) ; Channel selection by Phone number ChannelSelectMode = 0 ;Profiles can be used do define different coders per B-channels, such as Transparent ;...
Page 205: Ss7 Tunneling
The Signaling System 7 (SS7) tunneling feature facilitates peer-to-peer transport of SS7 links between gateways that support AudioCodes' unique MTP2 (Message Transfer Part) Tunneling application (M2TN) for transferring SS7 MTP2 link data over IP. In this scenario, both sides of the link are pure TDM switches and are unaware of the IP tandem that is utilized between them.
Page 206: Mtp2 Tunneling Technology
• Only standard protocols are used on external interfaces (MTP2 on PSTN side, and M2UA over SCTP on IP side) - the M2TN application resides internally in the Mediant 2000. • No extra signaling point codes are required; both endpoints are unaware that the SS7 connection is via IP.
Page 207: Ss7 Parameters
Mediant Series and TP-1610 H.323 User’s Manual 12. Special Applications 12.2.3 SS7 Parameters The parameters in Table 12-1 below configure all MTP attributes simultaneously. To set each MTP attribute individually, add _xx (xx equals the element number in the range of 0 to 2) to the end of the ini file field name.
Page 208: Ss7 Parameter Tables
Mediant Series and TP-1610 H.323 Table 12-1: SS7 Parameters (continues on pages 207 to 208) ini File Parameter Name Description Defines the SS7 MTP2 Remote Congestion timer (in msec). SS7_MTP2_Param_Timer_T6 The valid range is 0 to 10000. The default value is 6000. Defines the SS7 MTP2 excessive delay of the ack timer (in msec).
Page 209: Sigtran Interface Ids
Mediant Series and TP-1610 H.323 User’s Manual 12. Special Applications Table 12-2: SIGTRAN Interface Groups (continues on pages 208 to 209) ini File Parameter Name Description Determines the SIGTRAN group SCTP instance. SS7_SCTP_INSTANCE The valid range is 0 to 0xFFFE. The default value is 0xFFFE.
Page 210: Ss7 Signaling Link
Mediant Series and TP-1610 H.323 12.2.4.3 SS7 Signaling Link Table 12-4: SS7 Signaling Link (continues on pages 210 to 211) ini File Parameter Name Description Determines the index field for a line. SS7_LINK_INDEX The valid range is 0 to 7. The default value is 0. Determines the RowStatus field for a line.
Page 211 Mediant Series and TP-1610 H.323 User’s Manual 12. Special Applications Table 12-4: SS7 Signaling Link (continues on pages 210 to 211) ini File Parameter Name Description SS7_CONGESTION_LOW_MARK Determines the link congestion low mark of signaling link (TDM). The valid range is 0 to 255. The default value is 5. Determines the link congestion high mark of signaling link (TDM).
Page 212: Ss7 Mtp2 Tunneling Ini File Example
There are 4 interface IDs defined: 1 per link (M2UA MGC side). • This file is intended for ITU link variant (E1 trunks). To load the example SS7 MTP2 tunneling ini files to Mediant 2000 gateways, take these 3 steps: Load the ini file that is shown in Figure 12-6 to a tunnel central gateway (MTP2 MGC).
Page 213 Mediant Series and TP-1610 H.323 User’s Manual 12. Special Applications Figure 12-6: SS7 MTP2 Tunneling ini File Example - MGC SS7_MTP2_PARAM_TIMER_T1_0=50000 SS7_MTP2_PARAM_TIMER_T2_0=150000 SS7_MTP2_PARAM_TIMER_T3_0=1000 SS7_MTP2_PARAM_TIMER_T4E_0=500 SS7_MTP2_PARAM_TIMER_T4N_0=8200 SS7_MTP2_PARAM_TIMER_T5_0=100 SS7_MTP2_PARAM_TIMER_T6_0=3000 SS7_MTP2_PARAM_TIMER_T7_0=2000 [syslog] SYSLOGSERVERIP = 168.100.0.1 ENABLESYSLOG = 1 ;FORCEEXCEPTIONDUMP = 1 WATCHDOGSTATUS = 0 [ SS7_LINK_TABLE ] FORMAT SS7_LINK_INDEX = SS7_LINK_NAME, SS7_LINK_TRACE_LEVEL, SS7_LINK_ADMINISTRATIVE_STATE,SS7_LINK_L2_TYPE, SS7_LINK_L3_TYPE, SS7_LINK_GROUP_ID,...
Page 214: Figure 12-7: Ss7 Mtp2 Tunneling Ini File Example - Sg
Mediant Series and TP-1610 H.323 Figure 12-6: SS7 MTP2 Tunneling ini File Example - MGC SS7_SIG_T_REC, SS7_SIG_T_ACK, SS7_SIG_T_HB, SS7_SIG_MIN_ASP, SS7_SIG_BEHAVIOUR, SS7_LOCAL_SCTP_PORT, SS7_SIG_NETWORK, SS7_DEST_SCTP_PORT, SS7_DEST_IP, SS7_MGC_MX_IN_STREAM, SS7_MGC_NUM_OUT_STREAM; SS7_SIG_IF_GROUP_TABLE 4 = 4, 77, 4, 1, 2000, 2000, 30000, 1, 0, 2904, 1,2904,168.100.0.2,3,3; [ \SS7_SIG_IF_GROUP_TABLE ] [ SS7_SIG_INT_ID_TABLE ] FORMAT SS7_SIG_IF_ID_INDEX = SS7_SIG_IF_ID_VALUE, SS7_SIG_IF_ID_NAME, SS7_SIG_IF_ID_OWNER_GROUP,...
Page 215 Mediant Series and TP-1610 H.323 User’s Manual 12. Special Applications Figure 12-7: SS7 MTP2 Tunneling ini File Example - SG SS7_LINK_TRUNK_NUMBER,SS7_LINK_TIMESLOT_NUMBER,SS7_LINK_M2UA_IF_ID; SS7_LINK_TABLE 0 = new_link_0, 0, 2, 1,1, 1, 15,50; SS7_LINK_TABLE 1 = new_link_1, 0, 2, 1,1, 2, 12, 12; SS7_LINK_TABLE 2 = new_link_2, 0, 2, 1, 1, 4, 7,18;...
Page 216: Answering Machine Detection (Amd)
Mediant 2000 to be controlled by a third-party Application Server that uses H.323 protocol. When AMD is enabled, the Mediant 2000 channel capacity is reduced to 200 channels (8 T1 spans, or 6 E1 spans). Note that the Mediant 2000 doesn’t tear down a call when a signal is detected.
Page 217: Activation Acknowledgement
2111 12.3.1.2 Activation Acknowledgement The Mediant 2000 informs the Application Server on a successful / unsuccessful activation of the AMD mechanism via H.323 Connect message. This message includes (in the ‘data’ element of the non-standard data structure) the string ‘VD=1’ (the AMD are active) or ‘VD=1’ (the AMD aren’t active).
Page 218: Relevant Parameters
Mediant Series and TP-1610 H.323 12.3.2 Relevant parameters To enable the AMD mechanism on the Mediant 2000 set the following parameters: • EnableDSPIPMDetectors = 1 • AMDTimeout = 2000 (2 seconds) • SITDetectorEnable = 1 (to enable detection of the SIT tone) •...
Page 219: Security
13.2 on page 223). 13.1 SSL/TLS SSL, also known as TLS, is the method used to secure the Mediant 2000 Embedded Web Server and Telnet server. The SSL protocol provides confidentiality, integrity and authenticity between two communicating applications over TCP/IP.
Page 220: Secured Telnet
OpenSSL toolkit). Contact AudioCodes to obtain the acSSLTelnet utility. 13.1.3 Server Certificate Replacement The Mediant 2000 is supplied with a working SSL configuration consisting of a unique self-signed server certificate. When the Mediant 2000 is upgraded to firmware version 4.6, a unique self- signed server certificate is created.
Page 221: Client Certificates
Store. The Trusted Root Certificate file should contain both the certificate of the authorized user and the certificate of the CA. Since X.509 certificates have an expiration date and time, the Mediant 2000 must be configured to use NTP (Section on page 179) to obtain the current date and time.
Page 222 When the operation is completed, set the ini file parameter, HTTPSRequireClientCertificates = 1. Save the configuration (Section on page 110) and restart the Mediant 2000. When a user connects to the secure Web server: • If the user has a client certificate from a CA listed in the Trusted Root Certificate file, the connection is accepted and the user is prompted for the system password.
Page 223: Radius Login Authentication
= tp1610_master_tpm In the RADIUS server, define the list of users authorized to use the Mediant 2000, using one of the password authentication methods supported by the server implementation. The following example shows a user configuration file for FreeRADIUS using a plain-text password.
Page 224: Configuring Radius Support
RADIUS database. The local system password is still active and is used when the RADIUS server is down. To configure RADIUS support on the Mediant 2000 using the ini file: • Add the following parameters to the ini file. For information on modifying the ini file, refer to Section on page 113.
Page 225: Network Port Usage
13. Security 13.3 Network Port Usage The following table lists the default TCP/UDP network port numbers used by the Mediant 2000. Where relevant, the table lists the ini file parameters that control the port usage and provide source IP address filtering capabilities.
Page 226: Recommended Practices
Stateful firewalls. Do not allow unauthorized traffic to reach the Mediant 2000. 13.5 Legal Notice By default, the Mediant 2000 supports export-grade (40-bit and 56-bit) encryption due to US government restrictions on the export of security technologies. To enable 128-bit and 256-bit encryption on your device, contact your AudioCodes representative.
Page 227: Diagnostics
Several diagnostic tools are provided, enabling you to identify correct functioning of the Mediant 2000, or an error condition with a probable cause and a solution or workaround. • Front panel indicator LEDs on the Mediant 2000. The location and functionality of the front panel LEDs is shown in Section 2.2.1 on page 28.
Page 228: Syslog Servers
14.2.2 Operation The Syslog client, embedded in the Mediant 2000, sends error reports/events generated by the Mediant 2000 unit application to a Syslog server, using IP/UDP protocol. To activate the Syslog client on the Mediant 2000, take these 4 steps: Set the parameter ‘EnableSyslog’...
Page 229: Embedded Command Line Interface
15. Embedded Command Line Interface Embedded Command Line Interface An embedded Command Line Interface (CLI) is available on the Mediant 2000. The CLI (or CommandShell) can be accessed via Telnet, RS-232 and the Embedded Web Server. You can use the CLI for diagnostics and basic configuration, such as to modify most of the ini file...
Page 230: Using The Cli
Mediant Series and TP-1610 H.323 15.2 Using the CLI The CLI commands are organized in folders. When first entering CLI, the user prompt is located at the root folder. Each time a command is executed, the CLI lists the current folder’s available commands and sub-folders.
Page 231: Changing The Networking Parameters
Connectivity is active at the new IP address. Note: This command requires you to enter all three network parameters (each separated by a space). To save the configuration, at the prompt, type ‘SAR’ and press enter; the Mediant 2000 restarts with the new network settings. Version 4.6...
Page 232 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 233: Snmp-Based Management
Mediant Series and TP-1610 H.323 User’s Manual 16. SNMP-Based Management SNMP-Based Management Simple Network Management Protocol (SNMP) is a standard-based network control protocol used to manage elements in a network. The SNMP Manager (usually implemented by a Network Manager (NM) or an Element Manager (EM)) connects to an SNMP Agent (embedded on a remote Network Element (NE)) to perform network element Operation, Administration and Maintenance (OAM).
Page 234: Snmp Mib Objects
Mediant Series and TP-1610 H.323 of a problem with the device. This typically requires each device on the network to be configured to issue SNMP traps to one or more network devices that are awaiting these traps. The above message types are all encoded into messages referred to as Protocol Data Units (PDUs) that are interchanged between SNMP devices.
Page 235: Carrier Grade Alarm System
MIB browser. 16.3 Cold Start Trap Mediant 2000 technology supports a cold start trap to indicate that the device is starting. This allows the manager to synchronize its view of the device's active alarms. Two different traps are sent at start-up: •...
Page 236: Third-Party Performance Monitoring Measurements
Performance measurements are provided by several proprietary MIBs that are located under the ‘performance’ sub tree: iso(1).org(3).dod(6).internet(1).private(4).enterprises(1).audioCodes(5003).acPerformance(10). Two formats of performance monitoring MIBs are available: Old format (obsolete as of version 4.6): Each MIB is composed of a list of single MIB objects, each relates to a separate attribute within a gauge or a counter.
Page 237: Supported Mibs
Mediant Series and TP-1610 H.323 User’s Manual 16. SNMP-Based Management 16.5 Supported MIBs The Mediant 2000 contains an embedded SNMP Agent supporting the following MIBs: • Standard MIB (MIB-2) - The various SNMP values in the standard MIB are defined in RFC 1213.
Page 238: Traps
Mediant Series and TP-1610 H.323 AC-SYSTEM-MIB AC-SS7-MIB Other proprietary MIBs are: • acGateway MIB - This proprietary MIB contains objects related to configuration of the device when applied as a SIP or H.323 media gateway only. This MIB complements the other proprietary MIBs.
Page 239: Snmp Interface Details
Mediant Series and TP-1610 H.323 User’s Manual 16. SNMP-Based Management Full proprietary trap definitions and trap Varbinds are found in the acBoard MIB and acAlarm MIB. The following proprietary traps are supported. For detailed information on these traps, refer to Appendix E on page 289: •...
Page 240: Configuration Of Community Strings Via The Ini File
Mediant Series and TP-1610 H.323 Users 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: 16.7.1.1 Configuration of Community Strings via the ini File SNMPREADONLYCOMMUNITYSTRING_<x> = '#######' SNMPREADWRITECOMMUNITYSTRING_<x>...
Page 241: Trusted Managers
Mediant Series and TP-1610 H.323 User’s Manual 16. SNMP-Based Management Add a row to the vacmSecurityToGroupTable with these values: SecurityModel=2, SecurityName=the new trap community string, GroupName=TrapGroup, ReadGroup or ReadWriteGroup. The SecurityModel and SecurityName objects are row indices. You must add GroupName and RowStatus on the same set. Note: Modify the SecurityName field in the sole row of the snmpTargetParamsTable.
Page 242: Snmp Ports
Mediant Series and TP-1610 H.323 Add a row to the snmpTargetAddrTable with these values: Name=mgrN, TagList=MGR, Params=v2cparams, where N is an unused number between 0 and 4. Add a row to the tgtAddressMaskTable table with these values: Name=mgrN, tgtAddressMask=255.255.255.255:0. An alternative to the above procedure is to set the tgtAddressMask column while you are creating other rows in the table.
Page 243: Trap Managers Configuration Via The Ini File
16.7.4.2 Trap Managers Configuration via the ini File In the Mediant 2000 ini file, the parameters below can be set to enable or disable the sending of SNMP traps. Multiple trap destinations can be supported on the device by setting multiple trap destinations in the ini file.
Page 244: Trap Mangers Configuration Via Snmp
Mediant Series and TP-1610 H.323 To configure the trap manger host name use the parameter SNMPTrapManagerHostName. For example: SNMPTrapManagerHostName = 'myMananger.corp.MyCompany.com’. The same information configurable in the ini file can also be configured via Note: the acBoardMIB. 16.7.4.3 Trap Mangers Configuration via SNMP Two MIB interfaces are available for configuring the trap managers.
Page 245: Snmp Manager Backward Compatibility
(multiple media gateways in globally distributed enterprise offices, for example), that need to be managed by central personnel. The EMS is not included in the device’s supplied package. Contact AudioCodes for detailed information on AudioCodes’ EMS and on AudioCodes’ EVN - Enterprise VoIP Network – solution for large VoIP deployments.
Page 246 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 247: Configuration Files
CAS protocol configuration files (refer to Section 17.4 on page 251). To load any of the configuration files to the Mediant 2000 use the Embedded Web Server (refer to Section 5.8.2 on page 108) or alternatively specify the name of the relevant configuration file in the gateway’s ini file and load it (the ini file) to the gateway (refer to Section...
Page 248: Figure 17-1: Call Progress Tone Types
The Mediant 2000 reports dial tone detection if either of the two tones is detected.
Page 249: Prerecorded Tones (Prt) File
17.2.1 PRT File Format The PRT dat file contains a set of prerecorded tones to be played by the Mediant 2000 during operation. Up to 40 tones (totaling approximately 10 minutes) can be stored in a single file in flash memory.
Page 250: Voice Prompts File
When the list of recorded files is converted to a single voiceprompts.dat file, every Voice Prompt is tagged with an ID number, starting with ‘1’. This ID is used later by the Mediant 2000 to start playing the correct announcement. Up to 1000 Voice Prompts can be used.
Page 251: Cas Protocol Configuration Files
Mediant Series and TP-1610 H.323 User’s Manual 17. Configuration Files 17.4 CAS Protocol Configuration Files The CAS Protocol Configuration Files contain the CAS Protocol definitions to be used for CAS- terminated trunks, users can either use the files supplied or construct their own files. It is possible to load up to eight files and to use different files for different trunks.
Page 252 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 253: Selected Technical Specifications
18. Selected Technical Specifications Selected Technical Specifications 18.1 General Specifications The General Specifications (show in Table 18-1 below) apply to the Mediant 2000, Mediant 1000 and TP-1610 gateways. For the product-specific specifications, refer to: • Mediant 2000 (Section 18.2 on page 255).
Page 254 Mediant Series and TP-1610 H.323 Table 18-1: General Selected Technical Specifications (continues on pages 253 to 254) Function Specification Communication Protocols RTP/RTCP packetization. IP stack (UDP, TCP, RTP). Remote Software load (TFTP, HTTP and HTTPS). PRI (ETSI Euro ISDN, ANSI NI2, 4/5ESS, DMS 100, QSIG Basic Call, Japan INS1500, Telephony Protocols Australian Telecom, New Zealand Telecom, Hong Kong Variant, Korean MIC) E1/T1 CAS protocols: MFC R2, E&M wink start,...
Page 255: Mediant 2000 Specifications
5/6. For detailed information refer to the parameter ‘MaxEchoCancellerLength’ (Table 6-2). • When the AMD feature is enabled, the Mediant 2000 channel capacity is reduced to 200 channels (8 T1 spans, or 6 E1 spans). The following Balun adaptors were tested and certified by AudioCodes: Manufacture Name: AC&E...
Page 256 Mediant Series and TP-1610 H.323 Table 18-2: Mediant 2000 Selected Technical Specifications (continues on pages 255 to 256) Function Specification Note that to meet UL approvals, users must fulfill the criteria below. 2-pin terminal block (crimp connection type) comprising a Phoenix Contact Adaptor: Shroud: MSTBC2,5/2-STZF-5,08.
Page 257: Tp-1610 Specifications
• When the AMD feature is enabled, the TP-1610 channel capacity is reduced to 200 channels (8 T1 spans, or 6 E1 spans). The following Balun adaptors were tested and certified by AudioCodes: Manufacture Name: AC&E Part Number: B04040072 Manufacture Name: RIT Part Number: R3712271 Version 4.6...
Page 258 Mediant Series and TP-1610 H.323 Table 18-3: TP-1610 Selected Technical Specifications (continues on pages 257 to 258) Function Specification Physical 6U single cPCI slot. PICMG 2.0, R2.1 and R2.16 and R.3.0 CompactPCI™ card Physical 480 channels Supply Voltages and Power 40.7 W, 3 A at 5 V, 7.8 A at 3.3 V Consumption (typical) 240 channels...
Page 259: Mediant 1000 Specifications
Mediant Series and TP-1610 H.323 User’s Manual 18. Selected Technical Specifications 18.4 Mediant 1000 Specifications Table 18-4: Mediant 1000 Selected Technical Specifications Function Specification Modularity and Capacity up to four digital trunks (fully flexible, from a single and up to four trunks per module) Interfaces I/O Modules 1, 2, 3 or 4 E1/T1/J1 spans (Balanced 120/100 ohm) using RJ-48 connectors per...
Page 260 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 261: Appendix A Supplied H.323 Software Kit
Appendix A Supplied H.323 Software Kit Table A-1 describes the standard supplied software kit for the Mediant 2000, digital Mediant 1000 and TP-1610 H.323 gateways. The supplied documentation includes this User’s Manual, the relevant Fast Track manuals and the Mediant Series & TP-1610 H.323 Release Notes.
Page 262 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 263: Appendix B The Bootp/Tftp Configuration Utility
Mediant Series and TP-1610 H.323 User’s Manual B. The BootP/TFTP Configuration Utility Appendix B The BootP/TFTP Configuration Utility The BootP/TFTP utility enables you to easily configure and provision our boards and media gateways. Similar to third-party BootP/TFTP utilities (which are also supported) but with added functionality;...
Page 264: Specifications
Mediant Series and TP-1610 H.323 • Remote reset. • Unicast BootP response. • User-initiated BootP respond, for remote provisioning over WAN. • Filtered display of BootP requests. • Location of other BootP utilities that contain the same MAC entity. • Common log window for both BootP and TFTP sessions.
Page 265: Bootp/Tftp Application User Interface
Mediant Series and TP-1610 H.323 User’s Manual B. The BootP/TFTP Configuration Utility BootP/TFTP Application User Interface Figure B-1 shows the main application screen for the BootP/TFTP utility. Figure B-1: Main Screen Log Window Function Buttons on the Main Screen Pause: Click this button to pause the BootP Tool so that no replies are sent to BootP requests. Click the button again to restart the BootP Tool so that it responds to all BootP requests.
Page 266: Log Window
Mediant Series and TP-1610 H.323 Log Window The log window (refer to Figure B-1 on the previous page) records all BootP request and BootP reply transactions, as well as TFTP transactions. For each transaction, the log window displays the following information: •...
Page 267: Setting The Preferences
Mediant Series and TP-1610 H.323 User’s Manual B. The BootP/TFTP Configuration Utility B.10 Setting the Preferences The Preferences window, Figure B-3, is used to configure the BootP Tool parameters. Figure B-3: Preferences Screen B.10.1 BootP Preferences ARP is a common acronym for Address Resolution Protocol, and is the method used by all Internet devices to determine the link layer address, such as the Ethernet MAC address, in order to route Datagrams to devices that are on the same subnet.
Page 268: Tftp Preferences
Mediant Series and TP-1610 H.323 • ARP Type: The type of entry made into the ARP cache on the computer, once ARP Manipulation is enabled, can be either Dynamic or Static. Dynamic entries expire after a period of time, keeping the cache clean so that stale entries do not consume computer resources.
Page 269: Configuring The Bootp Clients
Mediant Series and TP-1610 H.323 User’s Manual B. The BootP/TFTP Configuration Utility B.11 Configuring the BootP Clients The Clients window, shown in Figure B-4 below, is used to set up the parameters for each specific VoIP gateway. Figure B-4: Client Configuration Screen B.11.1 Adding Clients Adding a client creates an entry in the BootP Tool for a specific gateway.
Page 270: Deleting Clients
Mediant Series and TP-1610 H.323 To add a client to the list using a template, take these 5 steps: Click on the Add New Client Icon; a client with blank parameters is displayed. In the field Template, located on the right side of the Client Configuration Window, click on the down arrow to the right of the entry field and select the template that you want to use.
Page 271: Setting Client Parameters
Mediant Series and TP-1610 H.323 User’s Manual B. The BootP/TFTP Configuration Utility B.11.5 Setting Client Parameters Client parameters are listed on the right side of the Client Configuration Window. • Client MAC: The Client MAC is used by BootP to identify the VoIP gateway. The MAC address for the VoIP gateway is printed on a label located on the VoIP gateway hardware.
Page 272: Using Command Line Switches
Mediant Series and TP-1610 H.323 B.11.6 Using Command Line Switches You can add command line switches in the field Boot File. To use a Command Line Switch, take these 4 steps: In the field Boot File, leave the file name defined in the field as it is (e.g., ramxxx.cmp). Place your cursor after cmp Press the space bar Type in the switch you require.
Page 273: Managing Client Templates
Mediant Series and TP-1610 H.323 User’s Manual B. The BootP/TFTP Configuration Utility B.12 Managing Client Templates Templates can be used to simplify configuration of clients when most of the parameters are the same. Figure B-5: Templates Screen To create a new template, take these 4 steps: Click on the Add New Template button Fill in the default parameter values in the parameter fields.
Page 274 Mediant Series and TP-1610 H.323 Reader’s Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 275: Appendix C Rtp/Rtcp Payload Types And Port Allocation
Mediant Series and TP-1610 H.323 User’s Manual C. RTP/RTCP Payload Types and Port Allocation Appendix C RTP/RTCP Payload Types and Port Allocation RTP Payload Types are defined in RFC 3550 and RFC 3551. We have added new payload types to enable advanced use of other coder types. These types are reportedly not used by other applications.
Page 276: Default Rtp/Rtcp/T.38 Port Allocation
Mediant Series and TP-1610 H.323 Default RTP/RTCP/T.38 Port Allocation The following table describes Mediant 2000 gateway default RTP/RTCP/T.38 port allocation. Table C-3: Default RTP/RTCP/T.38 Port Allocation Channel Number RTP Port RTCP Port T.38 Port 4000 4001 4002 4010 4011 4012...
Page 277: Appendix D Accessory Programs And Tools
Mediant Series and TP-1610 H.323 User’s Manual D. Accessory Programs and Tools Appendix D Accessory Programs and Tools The accessory applications and tools shipped with the device provide you with friendly interfaces that enhance device usability and smooth your transition to the new VoIP infrastructure. The following applications are available: •...
Page 278: Converting A Cpt Ini File To A Binary Dat File
Mediant Series and TP-1610 H.323 D.1.1 Converting a CPT ini File to a Binary dat File For detailed information on creating a CPT ini file, refer to Section 17.1 on page 247. To convert a CPT ini file to a binary dat file, take these 10 steps: Execute the TrunkPack Downloadable Conversion Utility, DConvert240.exe (supplied with the software package);...
Page 279: Creating A Loadable Voice Prompts File
Mediant Series and TP-1610 H.323 User’s Manual D. Accessory Programs and Tools D.1.2 Creating a Loadable Voice Prompts File For detailed information on the Voice Prompts file, refer to Section 17.2 on page 249. To create a loadable Voice Prompts dat file from your voice recording files, take these 7 steps: Execute the TrunkPack Downloadable Conversion Utility, DConvert240.exe (supplied with the software package);...
Page 280: Figure D-4: File Data Window
Mediant Series and TP-1610 H.323 Arrange the files according to your requirements by dragging and dropping them from one location in the list to another. Note that the sequence of the files determines their assigned Voice Prompt ID. Use the Play button to play wav files through your PC speakers. Tip 1: Use the Remove and Remove all buttons to delete files from the list.
Page 281: Creating A Loadable Cas Protocol Table File
Mediant Series and TP-1610 H.323 User’s Manual D. Accessory Programs and Tools D.1.3 Creating a loadable CAS Protocol Table File To create a loadable CAS protocol table file, take these 11 steps: Construct the CAS protocol files (xxx.txt and UserProt_defines_xxx.h). Copy the files generated in the previous step to the same directory the TrunkPack Downloadable Conversion utility is located and ensure that the files CASSetup.h and cpp.exe are also located in the same directory.
Page 282 Mediant Series and TP-1610 H.323 To create a file (for troubleshooting purposes) that contains the name of the States and their actual values: Check the Output state names to file checkbox; the default file name TableStateNames.txt appears in the adjacent field (you can modify the name of the file). The generated file is to be located in the same directory as the TrunkPack Downloadable Conversion utility.
Page 283: Encoding / Decoding An Ini File
Mediant Series and TP-1610 H.323 User’s Manual D. Accessory Programs and Tools D.1.4 Encoding / Decoding an ini File For detailed information on secured ini file, refer to Section on page 113. To encode an ini file, take these 6 steps: Execute the TrunkPack Downloadable Conversion Utility, DConvert240.exe (supplied with the software package);...
Page 284: Creating A Loadable Prerecorded Tones File
Mediant Series and TP-1610 H.323 D.1.5 Creating a Loadable Prerecorded Tones File For detailed information on the PRT file, refer to Section 17.2 on page 249. To create a loadable PRT dat file from your raw data files, take these 7 steps: Prepare the prerecorded tones (raw data PCM or L8) files you want to combine into a single dat file using standard recording utilities.
Page 285: Figure D-8: File Data Window
Mediant Series and TP-1610 H.323 User’s Manual D. Accessory Programs and Tools Click the Add File(s) button; the ‘Select Files’ screen opens. Select the required Prerecorded Tone files and press the Add>> button. Close the ‘Select Files’ screen. For each raw data file, define a Tone Type, a Coder and a Default Duration by completing the following steps: Double-click or right-click the required file;...
Page 286: Pstn Trace Utility
Mark the PSTN Trace check box. Push the Run button=> the UDP2File utility starts to collect the trace messages. Activate the Web page by entering <Mediant 2000 IP address>/TrunkTraces, such as: http://10.8.8.101/TrunkTraces. The user and password is the same for the unit.
Page 287: Figure D-9: Trunk Traces
Mediant Series and TP-1610 H.323 User’s Manual D. Accessory Programs and Tools Figure D-9: Trunk Traces Figure D-10: UDP2File Utility Version 4.6 July 2005...
Page 288 Mediant Series and TP-1610 H.323 Reader’s Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 289: Appendix E Snmp Traps
Mediant Series and TP-1610 H.323 User’s Manual E. SNMP Traps Appendix E SNMP Traps This section provides information on proprietary SNMP traps currently supported by the gateway. There is a separation between traps that are alarms and traps that are not (logs). Currently all have the same structure made up of the same 10 varbinds (Variable Binding) (1.3.6.1.4.1.5003.9.10.1.21.1).
Page 290: Table E-3: Acboardtemperaturealarm Alarm Trap
Mediant Series and TP-1610 H.323 Table E-2: acBoardConfigurationError Alarm Trap Status Changes: Condition: A configuration error was detected Alarm status: critical <text> value: A run-time specific string describing the configuration error. Condition: After configuration error Alarm status: Status stays critical until reboot. A clear trap is not sent. Corrective Action: Inspect the run-time specific string to determine the nature of the configuration error.
Page 291: Table E-6: Acboardcallresourcesalarm Alarm Trap
Mediant Series and TP-1610 H.323 User’s Manual E. SNMP Traps Table E-5: acFeatureKeyError Alarm Trap configurationOrCustomizationError (7) Probable Cause: Feature key error Alarm Text: Status Changes: Note: Support of this alarm is pending, Condition: Alarm status: Condition: Alarm status: Corrective Action: Table E-6: acBoardCallResourcesAlarm Alarm Trap acBoardCallResourcesAlarm Alarm:...
Page 292: Component: Alarmmanager#0
Mediant Series and TP-1610 H.323 Table E-8: acBoardOverloadAlarm Alarm Trap acBoardOverloadAlarm Alarm: 1.3.6.1.4.1.5003.9.10.1.21.2.0.11 OID: Major Default Severity processingErrorAlarm Event Type: softwareError (46) Probable Cause: Board overload alarm Alarm Text: Status Changes: Condition: An overload condition exists in one or more of the system components. Alarm Status: Major Condition:...
Page 293: Component: Ss7#0
Mediant Series and TP-1610 H.323 User’s Manual E. SNMP Traps Table E-10: acBoardEthernetLinkAlarm Alarm Trap Ethernet link alarm: <text> Alarm Text: Status Changes: Condition: Fault on single interface Alarm status: major <text> value: Redundant link is down Condition: Fault on both interfaces Alarm status: critical <text>...
Page 294: Log Traps (Notifications)
Mediant Series and TP-1610 H.323 Table F-12: acSS7LinkCongestionStateChangeAlarm Trap Status Changes: Condition: SS7 link becomes congested (local or remote). Alarm status: Major <text> value: %i - <Link number> %s – If link has MTP3 layer, then this string equals: (SP %i linkset %i slc %i) Where: %i - <SP number>...
Page 295: Trap Varbinds
Probable Cause: Initialization Ended Alarm Text: Note: This is the AudioCodes Enterprise application cold start trap. E.1.7 Trap Varbinds Each trap described above provides the following fields (known as ‘varbinds’). Refer to the AcBoard MIB for additional details on these varbinds.
Page 296 Mediant Series and TP-1610 H.323 Reader's Notes Mediant Series and TP-1610 H.323 Document #: LTRT-69903...
Page 297: Appendix F Regulatory Information
Undertegnede [AudioCodes Ltd] erklærer herved, at følgende udstyr [2000 Series] overholder de væsentlige krav og øvrige relevante krav i direktiv 1999/5/EF Dutch Hierbij verklaart [AudioCodes Ltd] dat het toestel [2000 Series] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van richtlijn 1999/5/EG English Hereby, [AudioCodes Ltd], declares that this [2000 Series] is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC.
Page 298: Safety Notices
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! Do not attempt to repair this equipment! Facility Interface Code: 04DU9.BN, 04DU9.DN, 04DU9.1KN, 4DU9.ISN...
Page 299: F.2 Tp-1610
Undertegnede [AudioCodes Ltd] erklærer herved, at følgende udstyr [1610 Series] overholder de væsentlige krav og øvrige relevante krav i direktiv 1999/5/EF Dutch Hierbij verklaart [AudioCodes Ltd] dat het toestel [1610 Series] in overeenstemming is met de essentiële eisen en de andere relevante bepalingen van richtlijn 1999/5/EG English Hereby, [AudioCodes Ltd], declares that this [1610 Series] is in compliance with the essential requirements and other relevant provisions of Directive 1999/5/EC.
Page 300: Industry Canada Notice
If this happens the telephone company will provide advance notice in order for you to make necessary modifications to maintain uninterrupted service. 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 301 Mediant Series and TP-1610 H.323 User’s Manual F. Regulatory Information Original printed on recycled paper and available on CD or Web site Version 4.6 July 2005...
Page 302 www.audiocodes.com...

This manual is also suitable for:

Mediant 1000 Mediant tp-1610 h.323 Tp-1610

AudioCodes Mediant 2000 User Manual

1 Overview

2 Physical Description

3 Installation

4 Getting Started

5 Web Management

6 Ini File Configuration of the Mediant 2000

7 Using Bootp / DHCP

8 Telephony Capabilities

Quick Links

Need help?

Questions and answers

Subscribe to Our Youtube Channel

Related Manuals for AudioCodes Mediant 2000

Summary of Contents for AudioCodes Mediant 2000