™ Mediant™ Digital Media Gateways & TrunkPack™ Boards SIP Mediant 2000 TP-1610 & TP-260/UNI Boards User’s Manual Version 5.
SIP User's Manual Contents Table of Contents 1 Overview ............................................................................................................19 1.1 1.2 1.3 1.4 1.5 1.6 Introduction ............................................................................................................ 19 Mediant 2000 Overview ......................................................................................... 19 TP-1610 Overview ............................................................
Mediant 2000 & TP-1610 & TP-260 5 Web Management..............................................................................................55 5.1 5.2 Computer Requirements ........................................................................................ 55 Protection and Security Mechanisms..................................................................... 55 5.2.1 5.2.2 5.2.3 5.3 Accessing the Embedded Web Server .................................................................. 58 5.3.
SIP User's Manual 6.4 The ini File Structure ............................................................................................ 128 6.4.1 6.5 6.6 6.7 6.8 6.9 6.10 6.11 6.12 6.13 6.14 6.15 6.16 6.17 6.18 7 The ini File Example............................................................................................. 129 Networking Parameters........................................................................................ 130 System Parameters...........................................
Mediant 2000 & TP-1610 & TP-260 9.3 NAT Support ........................................................................................................ 230 9.3.1 9.3.2 9.3.3 9.4 Point-to-Point Protocol over Ethernet (PPPoE).................................................... 233 9.4.1 9.4.2 9.4.3 9.5 9.6 9.7 9.8 9.9 9.10 STUN .................................................................................................................... 231 First Incoming Packet Mechanism.........................
SIP User's Manual Contents 12 Special Applications .......................................................................................267 12.1 TDM Tunneling..................................................................................................... 267 12.1.1 Implementation ..................................................................................................... 267 12.2 SS7 Tunneling.................................................................................................
Mediant 2000 & TP-1610 & TP-260 15.7 SNMP Interface Details........................................................................................ 315 15.7.1 15.7.2 15.7.3 15.7.4 15.7.5 SNMP Community Names.................................................................................... 316 SNMP v3 USM Users ........................................................................................... 318 Trusted Managers....................................................................................
SIP User's Manual Contents D.8 Function Buttons on the Main Screen .................................................................. 355 D.9 Log Window ......................................................................................................... 356 D.10 Setting the Preferences........................................................................................ 357 D.10.1 BootP Preferences................................................................................................
Mediant 2000 & TP-1610 & TP-260 List of Figures Figure 1-1: Typical Mediant 2000 / TP-1610 / TP-260 Gateway Application .........................................22 Figure 2-1: Mediant 2000 Front View .....................................................................................................27 Figure 2-2: Front and Upper View of the TP-1610 cPCI Board..............................................................29 Figure 2-3: Rear Panel with two 50-pin Connectors for 16 Trunks ....................
SIP User's Manual Contents Figure 5-36: TelÆIP Call Counters Screen......................................................................................... 108 Figure 5-37: Call Routing Status Screen............................................................................................. 109 Figure 5-38: Trunk & Channel Status Screen ..................................................................................... 110 Figure 5-39: Trunk and Channel Status Color Indicator Keys.....................
Mediant 2000 & TP-1610 & TP-260 Figure 13-14: Example of a User Configuration File for FreeRADIUS Using a Plain-Text Password 296 Figure 13-15: Example of an Access List Definition via ini File........................................................... 298 Figure 13-16: Advanced Example of an Access List Definition via ini File ......................................... 299 Figure 15-1: Example of Entries in a Device ini file Regarding SNMP ...............................................
SIP User's Manual Contents List of Tables Table 2-1: Mediant 2000 Front View Component Descriptions..............................................................27 Table 2-2: Chassis LED Indicators.........................................................................................................28 Table 2-3: Front and Upper View of the TP-1610 cPCI Board Component Descriptions ......................29 Table 2-4: Status LED Indicators ..................................................................
Mediant 2000 & TP-1610 & TP-260 Table 11-1: Example of Parameter Table - Remote Management Connections ................................ 253 Table 11-2: Example of Parameter Table - Port-to-Port Connections ................................................ 253 Table 11-3: Customizable Logo ini File Parameters ........................................................................... 259 Table 11-4: Web Appearance Customizable ini File Parameters .......................................................
SIP User's Manual Contents Table I-18: acBoardEvBoardStarted Trap ........................................................................................... 391 Table I-19: AcDChannelStatus Trap ................................................................................................... 391 Version 5.
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 16 Document #: LTRT-68805
SIP User's Manual Notices Notices Notice This document describes the release of the AudioCodes Mediant 2000 SIP gateway, TP-1610 SIP cPCI board, and TP-260 SIP PCI board. Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, AudioCodes cannot guarantee accuracy of printed material after the Date Published nor can it accept responsibility for errors or omissions.
Mediant 2000 & TP-1610 & TP-260 Related Documentation Document # Manual Name LTRT-690xx (e.g., LTRT-69001) Mediant 3000 & Mediant 2000 & TP Series SIP Digital Gateways Release Notes LTRT-701xx Mediant 2000 Fast Track Guide LTRT-665xx CPE Configuration Guide for IP Voice Mail Warning: The Mediant 2000 is supplied as a sealed unit and must only be serviced by qualified service personnel. Note: Where ‘network’ appears in this manual, it means Local Area Network (LAN), Wide Area Network (WAN), etc.
SIP User's Manual 1 Overview 1.1 Introduction 1. Overview This document provides you with the information on installation, configuration and operation of the Mediant 2000 SIP gateway, TP-1610 SIP cPCI board and TP-260 SIP PCI board. As these products have similar functionality (with the exception of their physical layout and the number of trunks), they are collectively referred to throughout this manual (except for in hardware-related sections) as the gateway. 1.
Mediant 2000 & TP-1610 & TP-260 1.3 TP-1610 Overview The TP-1610 cPCI VoIP media gateway board, based on dual TPM-1100 PMC Modules, is a complete SIP-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 SIP trunking gateways and integrated media gateways for IP-PBXs and all-in-one communication servers. The board is designed for enterprise or carrier applications.
SIP User's Manual 1.4 1. Overview TP-260 Overview The TP-260 SIP PCI VoIP media gateway board is a complete SIP-compliant ‘media gateway on a board’, delivering cost-effective solution in a convenient PCI form-factor. This unique stand-alone PCI media gateway operates independently and relies on the host PCI only for its power. The TP-260 communicates to applications via SIP using an on-board Ethernet interface.
Mediant 2000 & TP-1610 & TP-260 Figure 1-1 below illustrates typical Mediant 2000 / TP-1610 / TP-260 gateway applications over VoIP network. Figure 1-1: Typical Mediant 2000 / TP-1610 / TP-260 Gateway Application 1.5 SIP Overview SIP is an application-layer control (signaling) protocol used on the gateway for creating, modifying, and terminating sessions with one or more participants. These sessions can include Internet telephone calls, media announcements and conferences.
SIP User's Manual 1.6 1. Overview Features This section provides a high-level overview of some of the many gateway supported features. 1.6.1 1.6.2 General Features Compliant with SIP (RFC 3261). Supported coders: G.711 A-law, G.711 µ-law, G.723.1, G.726, G.729, NetCoder, EVRC, AMR, Transparent, GSM Full-Rate, Microsoft GSM and GSM EFR.
Mediant 2000 & TP-1610 & TP-260 The supported interworking features include the following: 1.6.3 Definition and use of Trunk Groups for routing IPÆPSTN calls. B-channel negotiation for PRI spans. ISDN Non Facility Associated Signaling (NFAS). PRI to SIP interworking according to . PRI to SIP Interworking of Q.931 Display (Calling name) information element.
SIP User's Manual 1. Overview Proxy and Registrar Authentication (handling 401 and 407 responses) using Basic or Digest methods. Accepted challenges are kept for future requests to reduce the network traffic. Single gateway Registration or multiple Registration of all gateway endpoints. Supported methods: INVITE, CANCEL, BYE, ACK, REGISTER, OPTIONS, INFO, REFER, UPDATE, NOTIFY, PRACK and SUBSCRIBE. Modifying connection parameters for an already established call (re-INVITE).
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 26 Document #: LTRT-68805
SIP User's Manual 2 2. Physical Description Physical Description This section provides detailed information on the hardware components, the location and functionality of the LEDs, buttons and connectors of the following products: 2.1 Mediant 2000 (refer to Section 2.1 below). TP-1610 (refer to Section 2.2 on page 29). TP-260 (refer to Section 2.3 on page 32).
Mediant 2000 & TP-1610 & TP-260 2.1.1 The Mediant 2000 Chassis The Mediant 2000 chassis is an industrial platform, 19” wide, 1U high and 12” deep that houses the 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. Refer to Table 2-2 for detailed description of the chassis’ LED indicators.
SIP User's Manual 2.2 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. The TP-1610 is composed of one or two identical media gateway modules: Gateway-1 and Gateway-2, each containing 240 DSP channels.
Mediant 2000 & TP-1610 & TP-260 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 29. Note that there is a choice of front panels according to the number of channels.
SIP User's Manual 2.2.2 2. Physical Description 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. The PSTN interface is available in 1-span, 2-span, 4-span, 8-span, or 16-span rear panels.
Mediant 2000 & TP-1610 & TP-260 2.3 TP-260 Physical Description The TP-260 board is a fully ‘Plug and Play’ device. The PC’s boot-up sequence determines its I/O addresses and interrupts.
SIP User's Manual 2.3.1 2. Physical Description TP-260 LEDs Refer to Table 2-11 through to Table 2-13 for LEDs.
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 34 Document #: LTRT-68805
SIP User's Manual 3 3. Installation Installation This section provides detailed information on the installation procedures for the following products: Mediant 2000 (refer to Section 3.1 below). TP-1610 (refer to Section 3.2 on page 44). TP-260 (refer to Section 3.3 on page 46). For information on how to start using the gateway, refer to Chapter 4 on page 49. Caution Electrical Shock The equipment must only be installed or serviced by qualified service personnel. 3.
Mediant 2000 & TP-1610 & TP-260 Small plastic bag containing (refer to Figure 3-1): • Two brackets and four bracket-to-device screws for 19-inch rack installation option. • Four anti-slide bumpers for desktop / shelf installation option. 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.
SIP 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: • • • • • Elevated Operating Ambient - If installed in a closed or multi-unit rack assembly, the operating ambient temperature of the rack environment may be greater than room ambient.
Mediant 2000 & TP-1610 & TP-260 ¾ To place the device on a 19-inch rack’s shelf, take these 2 steps: 1. 2. 3.1.4 Place the device on the preinstalled shelf. You’re now recommended to take the optional steps of fastening the device to the frame of the rack (as described above) while it is placed on the shelf, so preventing it from sliding when inserting cables into connectors on the rear panel.
SIP User's Manual 3. Installation Figure 3-4: Mediant 2000 Rear Panel Cabling (8 Trunks, DC Power) Table 3-2: Mediant 2000 Rear Panel Cabling (8 Trunks, DC Power) Component Descriptions Item # Label 1 Component Description RTM latches. 2 ETH 3 PSTN 4 A Category 5 network cable, connected to the Ethernet 1 RJ-45 port. 8 RJ-48c ports, each supporting a trunk. Protective earthing screw. 5 48V 4A max 2-pin connector for DC.
Mediant 2000 & TP-1610 & TP-260 3.1.4.1 Connecting the E1/T1 Trunk Interfaces Connect the E1/T1 Trunk Interfaces using either Telco or RJ-48 connectors: ¾ With 50-pin Telco connectors (16-trunk device), take these 3 steps: 1. 2. 3. Attach the Trunk cable (of at least 26 AWG UTP) with a 50-pin male Telco connector to the 50-pin female Telco connector labeled ‘Trunks 1Æ8’ on the Rear Transition Module (RTM). Connect the other end of the Trunk cable to the PBX/PSTN switch.
SIP User's Manual 3.1.4.2 3. Installation Installing the Ethernet Connection Connect a standard Category 5 network cable to the Ethernet RJ-45 port (and the other as optional redundancy/backup). Connect the other end of the Category 5 network cables to your IP network. The Ethernet connectors (labeled Ethernet 1 and Ethernet 2) are wired according to Figure 3-7. When assigning an IP address to the gateway using HTTP (under Step 1 in Section 4.2.
Mediant 2000 & TP-1610 & TP-260 3.1.4.4 Connecting the Power Supply Connect the Mediant 2000 to the power supply using one of the following methods: 3.1.4.4.1 Connecting the AC Power Supply ¾ When using a single AC power cable, take this step: Attach one end of the supplied 100/240 VAC power cable to the rear AC socket and connect the other end to the correct earthed AC power supply.
SIP User's Manual 3. Installation Figure 3-9: DC Terminal Block Screw Connector ¾ When using a DC terminal block crimp connector: 1. 2. 3. 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 to the DC power supply maintain the correct polarity (refer to Figure 3-10). Insert the terminal block into the DC inlet located on the Mediant 2000.
Mediant 2000 & TP-1610 & TP-260 3.2 Installing the TP-1610 Electrical Earthing Prior to installation of any board in a chassis, always correctly connect the chassis to a safety ground according to the laws and regulations of the country in which the installation is performed. Electrical Component Sensitivity Electronic components on printed circuit boards are extremely sensitive to static electricity. Normal amounts of static electricity generated by clothing can damage electronic equipment.
SIP User's Manual 3. Installation Notes: • • 3.2.3.1 Before removing or inserting boards from / to the chassis, attach a wrist strap 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. Inserting Boards ¾ To insert the TP-1610 board into the chassis, take these 3 steps: 1. 2. 3.
Mediant 2000 & TP-1610 & TP-260 3.3 Installing the TP-260 Electrical Earthing Prior to installation of any board in a chassis, always correctly connect the chassis to a safety ground according to the laws and regulations of the country in which the installation is performed. Electrical Component Sensitivity Electronic components on printed circuit boards are extremely sensitive to static electricity. Normal amounts of static electricity generated by clothing can damage electronic equipment.
SIP User's Manual 3.3.3 3. Installation Installing the TP-260 ¾ To install the TP-260 board, take these 8 steps: 1. 2. 3. 4. 5. 6. 7. 8. 3.3.4 End all applications running in the PC. Shut down the PC, turn off the power, and remove the PC's cover. Choose an available PCI slot and remove its blank rear bracket. Insert the TP-260 board into the chosen PCI slot. Ensure that the front panel (bracket) of the TP-260 board fits correctly into the opening in the rear panel of the PC's chassis.
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 48 Document #: LTRT-68805
SIP User's Manual 4 4. Getting Started Getting Started The Mediant 2000 is composed of one or two identical media gateway modules. These media gateways are fully independent, each gateway having its own MAC and IP addresses (Table 4-1 shows the default IP addresses of the Mediant 2000). Before you begin configuring each gateway, change its default IP address to correspond with your network environment (refer to Section 4.
Mediant 2000 & TP-1610 & TP-260 4.2 Assigning an IP Address to the Gateway 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). BootP (refer to Section 4.2.2 on page 51). The embedded Command Line Interface (CLI) accessed via RS-232 (if supported) or Telnet (refer to Section 4.2.3 on page 51). Dynamic Host Control Protocol (DHCP) (refer to Section 7.2 on page 204).
SIP User's Manual 4.2.2 4. Getting Started Assigning an IP Address Using BootP Note: BootP procedure can also be performed using any standard compatible BootP server. Tip: You can also use BootP to load the auxiliary files to the Mediant 2000 (refer to Section 6.18 on page 201). ¾ To assign an IP address using BootP, take these 4 steps: 1. 2. 3. 4. 4.2.3 Open the BootP application (supplied with the Mediant 2000 software package).
Mediant 2000 & TP-1610 & TP-260 ¾ To access the CLI via the RS-232 port, take these 2 steps: 1. 2. Connect the RS-232 port to your PC (For the Mediant 2000, refer to Section 3.1.4.3 on page 41. Use serial communication software (e.g., HyperTerminalTM) to connect to the Mediant 2000. Set your serial communication software to the following communications port settings: • Baud Rate: 115,200 bps • Data bits: 8 • Parity: None • Stop bits: 1 • Flow control: None The CLI prompt becomes available. 4.
SIP User's Manual 4.3 4. Getting Started Configuring the Gateway's Basic Parameters To configure the gateway's basic parameters use the Embedded Web Server’s ‘Quick Setup’ screen (shown in Figure 4-1 below). Refer to Section 5.3 on page 58 for information on accessing the ‘Quick Setup’ screen. Figure 4-1: Quick Setup Screen ¾ To configure basic SIP parameters, take these 10 steps: 1. If the gateway is connected to a router with NAT (Network Address Translation) enabled, perform the following procedure.
Mediant 2000 & TP-1610 & TP-260 Configure ‘Enable Registration’ to ‘Yes’ or ‘No’: ‘No’ = the gateway does not register to a Proxy server/Registrar (default). ‘Yes’ = the gateway registers to a Proxy server/Registrar at power up and every ‘Registration Time’ seconds. For detailed information on the parameter ‘Registration Time’, refer to Table 6-7 on page 150. 6. To program the Coders Table, click the arrow button next to ‘Coders Table’.
SIP User's Manual 5 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.
Mediant 2000 & TP-1610 & TP-260 5.2.1 User Accounts To prevent unauthorized access to the Embedded Web Server, two user accounts are available, a primary and secondary. Each account is composed of three attributes: username, password and access level. The username and password enable access to the Embedded Web Server itself; the access level determines the extent of the access (i.e., availability of screens and read / write privileges).
SIP User's Manual 5. Web Management To access the Embedded Web Server with a different account, click the Log Off button and re-access with a new username and password. Tip: For details on changing the account attributes, refer to Section 5.6.8.1 on page 98. Note that the password and username can be a maximum of 19 case-sensitive characters. To reset the username and password of both accounts to their defaults, set the ini file parameter ‘ResetWebPassword’ to 1. 5.2.
Mediant 2000 & TP-1610 & TP-260 5.3 Accessing the Embedded Web Server ¾ To access the Embedded Web Server, take these 4 steps: 1. 2. 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 gateway (e.g., http://10.1.10.10); the Embedded Web Server’s ‘Enter Network Password’ screen appears, shown in Figure 5-1. Figure 5-1: Embedded Web Server Login Screen 3. 4. 5.3.
SIP User's Manual 5.4 5. Web Management Getting Acquainted with the Web Interface Figure 5-2 shows the general layout of the Web Interface screen. Figure 5-2: Web Interface The Web Interface screen features the following components: Title bar: contains three configurable elements: corporate logo, a background image and the product’s name. For information on how to modify these elements, refer to Section 11.6 on page 257. Product name: the gateway's module name (Module 1 or Module 2).
Mediant 2000 & TP-1610 & TP-260 5.4.1 Main Menu Bar The main menu bar of the Web Interface is divided into the following 7 menus: Quick Setup: Use this menu to configure the gateway’s basic settings; for the full list of configurable parameters go directly to ‘Protocol Management’ and ‘Advanced Configuration’ menus. An example of the Quick Setup configuration is described in Section 4.3 on page 53.
SIP User's Manual 5. Web Management Figure 5-3: Searched Result Screen Each searched result displays the following: 3. Version 5.0 • Parameter name (hyperlinked to its location in the Embedded Web Server) • Brief description of the parameter • Hyperlink (in green) displaying the URL path to its location in the Embedded Web Server In the Searched Result list, click the required parameter to open the screen in which the parameter appears.
Mediant 2000 & TP-1610 & TP-260 Figure 5-4: Searched Parameter Highlighted in Screen Note: If the searched parameter is not located, the "No Matches Found For This String" message is displayed. 5.4.4 Entering Phone Numbers in Various Tables Phone numbers entered into various tables on the gateway, such as the Tel to IP routing table, must be entered without any formatting characters. For example, if you wish to enter the phone number 555-1212, it must be entered as 5551212 without the hyphen (-).
SIP User's Manual 5.5 5. Web Management Protocol Management Use this menu to configure the gateway’s SIP parameters and tables. 5.5.1 Protocol Definition Parameters Use this submenu to configure the following gateway’s specific SIP protocol parameters: 5.5.1.1 General Parameters Proxy & Registration Parameters Coders (refer to Section 5.5.1.
Mediant 2000 & TP-1610 & TP-260 6. 7. 8. 9. From the Silence Suppression drop-down list, enable or disable the silence suppression option for the coder you selected. Note: For G.729 it is also possible to select silence suppression without adaptations. Repeat steps 2 to 6 for the second to fifth coders (optional). Click the Submit button to save your changes. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 124. Notes: • • 5.5.
SIP User's Manual 5. Web Management Possible uses for number manipulation can be as follows: To strip/add dialing plan digits from/to the number. For example, a user could dial 9 in front of each number to indicate an external line. This number (9) can be removed here before (after) the call is setup. Assignment of NPI/TON to IPÆTel calls. The VoIP gateway can use a single global setting for NPI/TON classification or it can use the setting in this table on a call by call basis.
Mediant 2000 & TP-1610 & TP-260 Table 5-3: Number Manipulation Parameters (continues on pages 65 to 66) Parameter Description The manipulation rules are applied to any incoming call whose: • Destination number prefix matches the prefix defined in the ‘Destination Number’ field. • Source number prefix matches the prefix defined in the ‘Source Prefix’ field. • Source IP address matches the IP address defined in the ‘Source IP’ field (if applicable).
SIP User's Manual 5.5.3.1 5. Web Management Dialing Plan Notation The dialing plan notation applies, in addition to the four Manipulation tables, also to TelÆIP Routing table and to IPÆTrunk Group Routing table. When entering a number in the destination and source ‘Prefix’ columns, you can create an entry that represents multiple numbers using the following notation: [n-m] represents a range of numbers [n,m] represents multiple numbers. Note that this notation only supports single digit numbers.
Mediant 2000 & TP-1610 & TP-260 For NI-2 and DMS-100 ISDN variants the valid combinations of TON and NPI for calling and called numbers are (Plan/Type): 5.5.
SIP User's Manual 5. Web Management 4. Configure the Phone Context table according to Table 5-5. 5. Click the Submit button to save your changes. 6. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 124. Notes: • Several rows with the same NPI-TON or Phone-Context are allowed. In such a scenario, a Tel-to-IP call uses the first match. • Phone-Context '+' is a unique case as it doesn't appear in the Request-URI as a Phone-Context parameter.
Mediant 2000 & TP-1610 & TP-260 5.5.5 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.5.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).
SIP User's Manual 5. Web Management Alternative routing (using this table) is commonly implemented when there is no response to an INVITE message (after INVITE retransmissions). The gateway then issues an internal 408 ‘No Response’ implicit release reason. If this reason is included in the ‘Reasons for Alternative Routing’ table, the gateway immediately initiates a call to the redundant destination using the next matched entry in the ‘Tel to IP Routing’ table.
Mediant 2000 & TP-1610 & TP-260 Table 5-6: Tel to IP Routing Table Parameter Description Destination Phone Prefix Each entry in the Destination Phone Prefix fields represents a called telephone number prefix. The prefix can be 1 to 19 digits long. An asterisk (*) represents all numbers. Source Phone Prefix Each entry in the Source Phone Prefix fields represents a calling telephone number prefix. The prefix can be 1 to 19 digits long. An asterisk (*) represents all numbers.
SIP User's Manual 5. Web Management To use trunk groups you must also do the following: You must assign a trunk group ID to the VoIP gateway E1/T1 B-channels on the Trunk Group Table. For information on how to assign a trunk group ID to a B-channel, refer to Section 5.5.7 on page 82. You can configure the Trunk Group Settings table to determine the method in which new calls are assigned to channels within the trunk groups (a different method for each trunk group can be configured).
Mediant 2000 & TP-1610 & TP-260 Table 5-7: IP to Trunk Group Routing Table (continues on pages 73 to 74) Parameter Description Source IP Address Each entry in the Source IP Address fields represents the source IP address of an IPÆTel call (obtained from the Contact header in the INVITE message). Note: The source IP address can include the ‘x’ wildcard to represent single digits. For example: 10.8.8.xx represents all the addresses between 10.8.8.10 to 10.8.8.99.
SIP User's Manual 5.5.5.4 5. Web Management Internal SRV Table The Internal SRV table is used for resolving host names to DNS A-Records. Three different A-Records can be assigned to a hostname. Each A-Record contains the host name, priority, weight, and port.
Mediant 2000 & TP-1610 & TP-260 5.5.5.5 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, the gateway tries to find an alternative route to that call. The release reason for IPÆTel calls is provided in Q.931 notation. The release reason for TelÆIP calls is provided in SIP 4xx, 5xx and 6xx response codes.
SIP User's Manual 5.5.5.6 5. Web Management Release Cause Mapping The Release Cause Mapping screen enables the gateway to map (up to 12) different SIP Responses to Q.850 Release Causes and vice versa, thereby overriding the hard-coded mapping mechanism (described in Appendix H on page 379). ¾ To configure the release cause mapping, take these 5 steps: 1.
Mediant 2000 & TP-1610 & TP-260 5.5.6.1 Coder Group Settings Use the Coder Group Settings screen to define up to four different coder groups. These coder groups are used in the Tel and IP Profile Settings screens to assign different coders to Profiles. For each group you can define the first to fifth preferred coders (and their attributes) for the gateway. The first coder is the highest priority coder and is used by the gateway whenever possible.
SIP User's Manual 5. Web Management 10. Click the Submit button to save your changes. 11. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 124. Notes: • • 5.5.6.2 Only the ptime of the first coder in the defined coder list is declared in INVITE / 200 OK SDP, even if multiple coders are defined. If the coder G.
Mediant 2000 & TP-1610 & TP-260 2. 3. 4. 5. 6. 7. 8. 5.5.6.3 In the ‘Profile ID’ drop-down list, select the Tel Profile you want to edit (up to four Tel Profiles can be configured). 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. Where ‘20’ is the highest preference value.
SIP User's Manual 5. Web Management Figure 5-16: IP Profile Settings Screen 2. 3. 4. 5. 6. 7. 8. Version 5.0 In the ‘Profile ID’ drop-down list, select the IP Profile you want to edit (up to four IP Profiles can be configured). 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. Where ‘20’ is the highest preference value.
Mediant 2000 & TP-1610 & TP-260 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. ¾ To configure the Trunk Group table, take these 4 steps: 1. Open the ‘Trunk Group Table’ screen (Protocol Management menu > Trunk Group); the ‘Trunk Group Table’ screen is displayed.
SIP User's Manual 5.5.8 5. Web Management Configuring the Trunk Group Settings The Trunk Group Settings Table is used to determine the method in which new calls are assigned to B-channels within each trunk group. If such a rule doesn’t exist (for a specific Trunk group), the global rule, defined by the Channel Select Mode parameter (Protocol Definition > General Parameters), applies. ¾ To configure the Trunk Group Settings table, take these 7 steps: 1.
Mediant 2000 & TP-1610 & TP-260 Table 5-9: Channel Select Modes Mode Description By phone number Select the gateway port according to the called number (refer to the note below). Select the next available channel in an ascending cycle order. Always select the next higher channel number in the Trunk Group. When the gateway reaches the highest channel number in the Trunk Group, it selects the lowest channel number in the Trunk Group and then starts ascending again (default).
SIP User's Manual 5. Web Management Note that an NFS file server can share multiple file systems. There must be a separate row for each remote file system shared by the NFS file server that needs to be accessed by the gateway. ¾ To configure the NFS Settings parameters, take these 7 steps: 1. 2. Open the ‘Application Settings’ screen (Advanced Configuration menu > Network Settings > Application Settings option); the ‘Application Settings’ screen is displayed.
Mediant 2000 & TP-1610 & TP-260 ¾ To modify an existing remote NFS file system, take these 4 steps: 1. 2. 3. 4. Click the Edit radio button for the row to be modified. Change the values on the selected row according to your requirements. Click the Apply New Settings button; the remote NFS file system is mounted using the new settings. Check the Syslog server for the ‘NFS mount was successful’ message. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 124.
SIP User's Manual 5. Web Management Table 5-10: IP Routing Table Column Description Column Name Description [ini File Parameter Name] Delete Row To delete IP routing rules from the IP Routing Table, check the Delete Row checkbox in the rows of the routing rules you want to delete and click the button Delete Selected Entries; the routing rules are removed from the table. Destination IP Address Specifies the IP address of the destination host / network.
Mediant 2000 & TP-1610 & TP-260 5.6.3 Configuring the Trunk Settings ¾ To configure the Trunk Settings, take these 10 steps: 1. 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). The Stop Trunk button appears at the bottom of the screen. The Trunk Status indicators appear colored. Table 5-11 shows the possible indicators and their descriptions.
SIP User's Manual 5. Web Management Table 5-11: Trunks Status Color Indicator Keys Indicator 3.
Mediant 2000 & TP-1610 & TP-260 7. After modifying the parameters: • 8. 9. To apply the changes to the selected trunk only, click the Apply Trunk Settings button. • To apply the changes to all the trunks, click the Apply to all Trunks button. The screen is refreshed; parameters become read-only (indicated by being grayed). The Stop Trunk button appears at the bottom of the screen. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 124.
SIP User's Manual 5.6.4.1 5. Web Management Configuring M2P2 Attributes For a detailed description of M2P2 attributes, refer to Section 12.2.4 on page 272. ¾ To configure the M2P2 Attributes parameters, take these 4 steps: 1. Open the ‘M2P2 Attributes‘ screen (Advanced Configuration menu > SS7 Configuration > M2P2 Attributes option); the ‘M2P2 Attributes’ screen is displayed. Figure 5-22: M2P2 Attributes Screen 2. 3. 4. Version 5.
Mediant 2000 & TP-1610 & TP-260 5.6.4.2 Configuring Links For a detailed description of Links, refer to Section 12.2.4 on page 272. ¾ To configure the Links parameters, take these 4 steps: 1. Open the ‘Links‘ screen (Advanced Configuration menu > SS7 Configuration > Links option); the ‘Links’ screen is displayed. Figure 5-23: Links Screen 2. 3. 4. Configure or modify the parameters as desired (for a description of the parameters, refer to Section 12.2.4 on page 272). Click Create.
SIP User's Manual 5.6.4.3 5. Web Management Configuring Sigtran Group IDs For a detailed description of Sigtran Group IDs, refer to Section 12.2.4 on page 272. ¾ To configure the Sigtran Group IDs parameters, take these 4 steps: 1. Open the ‘Sigtran Group IDs‘ screen (Advanced Configuration menu > SS7 Configuration > Sigtran Group IDs option); the ‘Sigtran Group IDs‘ screen is displayed. Figure 5-24: Sigtran Group IDs Screen 2. 3. 4. Version 5.
Mediant 2000 & TP-1610 & TP-260 5.6.4.4 Configuring Sigtran Interface IDs For a detailed description of Sigtran Interface IDs, refer to Section 12.2.4 on page 272. ¾ To configure the Sigtran Interface IDs parameters, take these 4 steps: 1. Open the ‘Sigtran Interface IDs‘ screen (Advanced Configuration menu > SS7 Configuration > Sigtran Interface IDs option); the ‘Sigtran Interface IDs‘ screen is displayed. Figure 5-25: Sigtran Interface IDs Screen 2. 3. 4.
SIP User's Manual 5.6.5 5. Web Management Configuring the TDM Bus Settings ¾ To configure the TDM Bus Settings parameters, take these 5 steps: 1. 2. 3. 4. 5. Open the ‘TDM Bus Settings’ screen (Advanced Configuration menu > TDM Bus Settings); the ‘TDM Bus Settings’ screen is displayed. Configure the TDM Bus Settings parameters. Click the Submit button to save your changes. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 124.
Mediant 2000 & TP-1610 & TP-260 5.6.6 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. Back up your configuration if you want to protect your VoIP gateway programming.
SIP User's Manual 5.6.7 5. Web Management Regional Settings The ‘Regional Settings’ screen enables you to set and view the gateway’s internal date and time and to load to the gateway the following configuration files: Call Progress Tones, CAS and Voice Prompts. For detailed information on the configuration files, refer to Section 16 on page 329. ¾ To configure the date and time of the gateway, take these 3 steps: 1.
Mediant 2000 & TP-1610 & TP-260 7. 8. To save the loaded auxiliary files so they are available after a power fail, refer to Section 5.9.2 on page 124. To reset the gateway, refer to Section 5.9.3 on page 125. Notes: • • 5.6.8 Saving a configuration file to flash memory may disrupt traffic on the gateway. To avoid this, perform a graceful lock (Section 5.9.1 on page 122) on all traffic on the device before saving to flash memory. A device reset is required to activate a loaded CPT file.
SIP User's Manual 5. Web Management Figure 5-29: Web User Accounts Screen (for Users with ‘Security Administrator’ Privileges) 2. 3. 4. To change the access level of the secondary account (the access level of the primary account cannot be changed), in the ‘Access Level’ drop-down list, select the new access level and click the button Change Access Level; the new access level is applied immediately.
Mediant 2000 & TP-1610 & TP-260 5.6.8.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. ¾ To manage the Web & Telnet access list, take these 4 steps: 1.
SIP User's Manual 5.6.8.3 5. Web Management Configuring the Firewall Settings The gateway accommodates an internal Firewall, allowing the security administrator to define network traffic filtering rules. For detailed information on the internal Firewall, refer to Section 13.5 on page 298. ¾ To create a new access rule, take these 6 steps: 1. Open the ‘Firewall Settings’ screen (Advanced Configuration menu > Security Settings > Firewall Settings option); the ‘Firewall Settings’ screen is displayed.
Mediant 2000 & TP-1610 & TP-260 ¾ To delete a rule, take these 3 steps: 1. 2. 3. 5.6.8.4 Click the radio button of the entry you want to activate. Click the Delete Rule button; the rule is deleted. To save the changes so they are available after a power fail, refer to Section 5.9.2 on page 124. Configuring the Certificates Use the Certificates screen to replace the server (refer to Section 13.2.4 on page 291) and client (refer to Section 13.2.
SIP User's Manual 5.6.9.1 5. Web Management Configuring the SNMP Managers Table The SNMP Managers table allows you to configure the attributes of up to five SNMP managers. ¾ To configure the SNMP Managers Table, take these 5 steps: 1. 2. 3. 4. 5. Access the ‘Management Settings’ screen (Advanced Configuration menu > Management Settings); the ‘Management Settings’ screen is displayed.
Mediant 2000 & TP-1610 & TP-260 5.6.9.2 Configuring the SNMP Community Strings Use the SNMP Community Strings table to configure up to five read-only and up to five read / write SNMP community strings, and to configure the community string that is used for sending traps. For detailed information on SNMP community strings, refer to section 15.7.1 on page 316. ¾ To configure the SNMP Community Strings, take these 5 steps: 1. 2. 3. 4. 5.
SIP User's Manual 5.6.9.3 5. Web Management Configuring SNMP v3 Users Use the SNMP V3 Table to configure authentication and privacy for up to 10 SNMP v3 users. ¾ To configure the SNMP v3 users, take these 6 steps: 1. 2. Access the ‘Management Settings’ screen (Advanced Configuration menu > Management Settings); the ‘Management Settings’ screen is displayed.
Mediant 2000 & TP-1610 & TP-260 5.7 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 information, call details and call statistics, including the number of call attempts, failed calls, fax calls, etc.
SIP User's Manual 5. Web Management Table 5-12: IP Connectivity Parameters Column Name Description IP address defined in the destination IP address field in the Tel to IP Routing table. or IP address that is resolved from the host name defined in the destination IP address field in the Tel to IP Routing table. Host Name Host name (or IP address) defined in the destination IP address field in the Tel to IP Routing table.
Mediant 2000 & TP-1610 & TP-260 5.7.1.2 Call Counters The Call Counters screens provide you with statistic information on incoming (IPÆTel) and outgoing (TelÆIP) calls. The statistic information is updated according to the release reason that is received after a call is terminated (during the same time as the end-of-call CDR message is sent). The release reason can be viewed in the Termination Reason field in the CDR message. For detailed information on each counter, refer to Table 5-13 on page 108.
SIP User's Manual 5. Web Management Table 5-13: Call Counters Description (continues on pages 108 to 109) Counter Description This counter indicates the number of calls that failed as a result of a busy line. It is Number of Failed Calls incremented as a result of the following release reason: due to a Busy Line GWAPP_USER_BUSY (17) This counter indicates the number of calls that weren’t answered.
Mediant 2000 & TP-1610 & TP-260 5.7.2 Monitoring the Gateway's Trunks & Channels The Trunk & Channel Status screen provides real time monitoring on the current status of the gateway's trunks & channels. This screen also allows you to assign a brief description to each trunk. The 'Trunk & Channel Status' screen is easily accessed using the Home icon located above the main menu bar.
SIP User's Manual 5. Web Management ¾ To monitor the details of a specific channel, take these 2 steps: 1. 2. Click the numbered icon of the specific channel whose detailed status you need to view; the channel-specific Channel Status screen appears, shown in Figure 5-40. Click the submenu links to view a specific channel’s parameter settings. Figure 5-40: Channel Status Details Screen ¾ To add a port description, take these 3 steps: 1. 2. 3. Version 5.
Mediant 2000 & TP-1610 & TP-260 5.7.3 Activating the Internal Syslog Viewer The Message Log screen displays Syslog debug messages sent by the gateway. Note that it is not recommended to keep a ‘Message Log’ session open for a prolonged period (refer to the Note below). For prolong debugging use an external Syslog server, refer to Section 14.2 on page 304. Refer to the Debug Level parameter ‘GwDebugLevel’ (described in Table 6-2) to determine the Syslog logging level.
SIP User's Manual 5.7.4 5. Web Management Device Information The Device Information screen displays specific hardware and software product information. This information can help you to expedite any troubleshooting process. 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 gateway (stored in the RAM).
Mediant 2000 & TP-1610 & TP-260 5.7.5 Viewing the Ethernet Port Information The Ethernet Port Information screen provides read-only information on the Ethernet connection used by the gateway. The Ethernet Port Information parameters are displayed in Table 5-15. For detailed information on the Ethernet redundancy scheme, refer to Section 9.2 on page 229. For detailed information on the Ethernet interface configuration, refer to Section 9.1 on page 229.
SIP User's Manual 5.8 5. Web Management Software Update Menu The ‘Software Update’ menu enables users to upgrade the gateway's software by loading a new cmp file along with the ini and a suite of auxiliary files, or to update the existing auxiliary files. The ‘Software Update’ menu comprises two submenus: Software Upgrade Wizard (refer to Section 5.8.1 below). Auxiliary Files (refer to Section 5.8.2 on page 119).
Mediant 2000 & TP-1610 & TP-260 ¾ To use the Software Upgrade Wizard, take these 10 steps: 1. 2. Stop all traffic on the gateway (refer to the note above). Open the ‘Software Upgrade Wizard’ (Software Update menu > Software Upgrade Wizard); the ‘Start Software Upgrade’ screen appears. Figure 5-44: Start Software Upgrade Screen Note: At this point, the process can be canceled with no consequence to the gateway (click the Cancel button).
SIP User's Manual 4. 5. Web Management Click the Browse button, navigate to the cmp file and click the button Send File; the cmp file is loaded to the gateway and you’re notified as to a successful loading (refer to Figure 5-46). Figure 5-46: cmp File Successfully Loaded onto the Gateway Notification 5. Note that the four action buttons (Cancel, Reset, Back, and Next) are now activated (following cmp file loading).
Mediant 2000 & TP-1610 & TP-260 6. In the ‘Load an ini File’ screen, you can now choose to either: • Click Browse and navigate to the ini file; the check box ‘Use existing configuration’, by default checked, becomes unchecked. Click Send File; the ini file is loaded to the gateway and you’re notified as to a successful loading. • Ignore the Browse button (its field remains undefined and the check box ‘Use existing configuration’ remains checked by default). • 7.
SIP User's Manual 5. Web Management Figure 5-49: Finish Screen Figure 5-50: End Process Screen 10. Click the End Process button; the ‘Quick Setup’ screen appears and the full Web application is reactivated. 5.8.2 Auxiliary Files The ‘Auxiliary Files’ screen enables you to load to the gateway the following files: CAS, Call Progress Tones, Voice Prompts, Prerecorded Tones (PRT) and User Information. For detailed information on these files, refer to Section 16 on page 329.
Mediant 2000 & TP-1610 & TP-260 ¾ To load an auxiliary file to the gateway, take these 8 steps: 1. Open the ‘Auxiliary Files’ screen (Software Upgrade menu > Load Auxiliary Files); the ‘Auxiliary Files’ screen is displayed. Figure 5-51: Auxiliary Files Screen 2. 3. 4. 5. 6. Click the Browse button that is in the field for the type of file you want to load. Navigate to the folder that contains the file you want to load.
SIP User's Manual 5.8.3 5. Web Management Updating the Software Upgrade Key The AudioCodes gateways are supplied with a Software Upgrade Key already preconfigured for each of its TrunkPack Modules (TPM). Users can later upgrade their gateway features, capabilities and quantity of available resources by specifying what upgrades they require, and purchasing a new key to match their specification. The Software Upgrade Key is sent as a string in a text file, to be loaded onto the gateway.
Mediant 2000 & TP-1610 & TP-260 5.9 Maintenance The Maintenance menu is used for the following operations: 5.9.1 Locking and unlocking the gateway (refer to Section 5.9.1 on page 122) Saving the gateway's configuration (refer to Section 5.9.2 on page 124) Resetting the gateway (refer to Section 5.9.3 on page 125) Locking and Unlocking the Gateway The Lock and Unlock options allow you to lock the IPmedia 2000 so that it does not accept any new incoming calls.
SIP User's Manual 5. Web Management 3. In the 'Lock Timeout' field (relevant only if the 'Graceful Option' in the previous step is set to 'Yes'), enter the time (in seconds) after which the gateway locks. Note that if no traffic exists and the time has not expired, the gateway locks. 4. Click the LOCK button. If 'Graceful Option' is set to 'Yes', the lock is delayed and a screen displaying the number of remaining calls and time is displayed. Otherwise, the lock process begins immediately.
Mediant 2000 & TP-1610 & TP-260 5.9.2 Saving Configuration The 'Maintenance Actions' screen enables you to save the current parameter configuration and the loaded auxiliary files to the non-volatile memory (i.e., flash) so they are available after a hardware reset (or power fail). Parameters that are only saved to the volatile memory (RAM) revert to their previous settings after hardware reset. Notes: • • • Saving changes to the non-volatile memory may disrupt traffic on the gateway.
SIP User's Manual 5.9.3 5. Web Management Resetting the IPmedia 2000 The 'Maintenance Actions' screen enables you to remotely reset the gateway. Before you reset the gateway, you can choose the following options: Save the gateway's current configuration to the flash memory (non-volatile) before reset. Perform a graceful shutdown. Reset starts only after a user-defined time expires or no more active traffic exists (the earliest thereof). ¾ To reset the IPmedia 2000, take these 5 steps: 1.
Mediant 2000 & TP-1610 & TP-260 4. In the 'Shutdown Timeout' field (relevant only if the 'Graceful Option' in the previous step is set to 'Yes'), enter the time after which the gateway resets. Note that if no traffic exists and the time has not expired, the gateway resets. 5. Click the RESET button. If 'Graceful Option' is set to 'Yes', the reset is delayed and a screen displaying the number of remaining calls and time is displayed.
SIP User's Manual 6 6. Gateway's ini File Configuration Gateway's ini File Configuration As an alternative to configuring the VoIP gateway using the Web Interface (refer to Chapter 5 on page 55), it can be configured by loading the ini file containing Customer-configured parameters. The ini file is loaded via the BootP/TFTP utility (refer to Appendix D on page 353) or via any standard TFTP server. It can also be loaded through the Web Interface (refer to Section 5.6.6 on page 96).
Mediant 2000 & TP-1610 & TP-260 6.3 The ini File Content The ini file contains the following SIP gateway information: Networking parameters shown in Table 6-1 on page 130. System parameters shown in Table 6-2 on page 138. Web and Telnet parameters shown in Table 6-3 on page 143. Security parameters shown in Table 6-4 on page 145. RADIUS parameters shown in Table 6-5 on page 147. SNMP parameters shown in Table 6-6 on page 148.
SIP User's Manual 6.5 6. Gateway's ini File Configuration The parameter name is NOT case-sensitive; the parameter value is NOT casesensitive except for coder names. The ini file should be ended with one or more carriage returns. The ini File Example Figure 6-2 shows an example of an ini file for the VoIP gateway.
Mediant 2000 & TP-1610 & TP-260 6.6 Networking Parameters Table 6-1: Networking Parameters (continues on pages 130 to 138) ini File Field Name Web Parameter Name EthernetPhyConfiguration DHCPEnable [Enable DHCP] Valid Range and Description 0 = 10 Base-T half-duplex 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 9.1 on page 229.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-1: Networking Parameters (continues on pages 130 to 138) ini File Field Name Web Parameter Name DNS2IP [Internal DNS Table] Valid Range and Description Internal DNS table, used to resolve host names to IP addresses. Two different IP addresses (in dotted format notation) can be assigned to a hostname.
Mediant 2000 & TP-1610 & TP-260 Table 6-1: Networking Parameters (continues on pages 130 to 138) ini File Field Name Web Parameter Name EnableIPAddrTranslation EnableUDPPortTranslation NoOperationSendingMode RTPNoOpEnable NoOpInterval RTPNoOpInterval RTPNoOpPayloadType EnableDetectRemoteMACC hange StaticNatIP [NAT IP Address] SIP User's Manual Valid Range and Description 0 = Disable IP address translation. 1 = Enable IP address translation for RTP, RTCP and T.38 packets (default).
SIP User's Manual 6. Gateway's ini File Configuration Table 6-1: Networking Parameters (continues on pages 130 to 138) ini File Field Name Web Parameter Name SyslogServerIP [Syslog Server IP Address] SyslogServerPort [Syslog Server Port] EnableSyslog [Enable Syslog] BaseUDPport [RTP Base UDP Port] Valid Range and Description IP address (in dotted format notation) of the computer you are using to run the Syslog Server.
Mediant 2000 & TP-1610 & TP-260 Table 6-1: Networking Parameters (continues on pages 130 to 138) ini File Field Name Web Parameter Name L1L1ComplexRxUDPPort [RTP Multiplexing Remote UDP Port] NTPServerIP [NTP Server IP Address] NTPServerUTCOffset [NTP UTC Offset] NTPUpdateInterval [NTP Update Interval] Valid Range and Description Determines the remote UDP port the multiplexed RTP packets are sent to, and the local UDP port used for incoming multiplexed RTP packets (applies to the ThroughPacket™ mechanism
SIP User's Manual 6.
Mediant 2000 & TP-1610 & TP-260 Table 6-1: Networking Parameters (continues on pages 130 to 138) ini File Field Name Web Parameter Name Valid Range and Description User Name for PAP or Host Name for CHAP authentication. The valid range is a string of up to 47 characters. The default value is 0. Password for PAP or Secret for CHAP authentication. PPPoEPassword The valid range is a string of up to 47 characters. The default value is 0. Server Name for CHAP authentication.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-1: Networking Parameters (continues on pages 130 to 138) ini File Field Name Web Parameter Name BronzeServiceClassDiffSer v [Bronze QoS] Valid Range and Description Sets the DiffServ value for the Bronze service class content. The valid range is 0 to 56. The default value is 10. NFS Table Parameters (NFSServers). For an NFS ini file example, refer to Figure 5-20 on page 86. The row index of the remote file system. The valid range is 0 to 4.
Mediant 2000 & TP-1610 & TP-260 6.7 System Parameters Table 6-2: System Parameters (continues on pages 138 to 143) ini File Field Name Web Parameter Name EnableDiagnostics GWAppDelayTime [Delay After Reset [sec]] ActivityListToLog [Activity Types to Report via 'Activity Log' Messages] SIP User's Manual Valid Range and Description Checks the correct functionality of the different hardware components on the gateway.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-2: System Parameters (continues on pages 138 to 143) ini File Field Name Web Parameter Name MaxEchoCancellerLength [Max Echo Canceller Length] Note: It isn’t necessary to configure the parameter EchoCancellerLength as it automatically acquires its value from the parameter MaxEchoCancellerLength.
Mediant 2000 & TP-1610 & TP-260 Table 6-2: System Parameters (continues on pages 138 to 143) ini File Field Name Web Parameter Name EnableRAI Valid Range and Description 0 = Disable RAI (Resource Available Indication) service (default). 1 = Enable RAI service. If RAI is enabled, an SNMP ‘acBoardCallResourcesAlarm’ Alarm Trap is sent if gateway resources fall below a predefined (configurable) threshold. RAIHighThreshold High Threshold (in percentage) that defines the gateway‘s busy endpoints.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-2: System Parameters (continues on pages 138 to 143) ini File Field Name Web Parameter Name Valid Range and Description Silence detection method. 0 (None) = Silence detection option is disabled. 1 (Packets Count) = According to packet count. 2 (Voice/Energy Detectors) = N/A. 3 (All) = N/A. FarEndDisconnectSilenceT Threshold of the packet count (in percents), below which is considered silence hreshold by the media gateway.
Mediant 2000 & TP-1610 & TP-260 Table 6-2: System Parameters (continues on pages 138 to 143) ini File Field Name Web Parameter Name AutoUpdatePredefinedTim e ResetNow Valid Range and Description Schedules an automatic update to a predefined time of the day. The range is 'HH:MM' (24-hour format). For example: 20:18 Note: The actual update time is randomized by five minutes to reduce the load on the Web servers. Invokes an immediate restart of the gateway.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-2: System Parameters (continues on pages 138 to 143) ini File Field Name Web Parameter Name ExtBootPReqEnable 6.8 Valid Range and Description 0 = Disable (default). 1 = Enable extended information to be sent in BootP request. If enabled, the device uses the vendor specific information field in the BootP request to provide device-related initial startup information such as board type, current IP address, software version, etc.
Mediant 2000 & TP-1610 & TP-260 Table 6-3: Web and Telnet Parameters (continues on pages 143 to 144) ini File Field Name Web Parameter Name Valid Range and Description Telnet Parameters Enables or disables the embedded Telnet server. Telnet is disabled by default for security reasons. 0 = Disable (default). 1 = Enable (Unsecured). 2 = Enable Secured (SSL). TelnetServerPort Defines the port number for the embedded Telnet server. [Telnet Server TCP Port] The valid range = valid port numbers.
SIP User's Manual 6.9 6. Gateway's ini File Configuration Security Parameters Table 6-4: Security Parameter (continues on pages 145 to 146) ini File Field Name Web Parameter Name Valid Range and Description Enables / disables the Secure Internet Protocol (IPSec) on the gateway. 0 = Disable (default). 1 = Enable. EnableMediaSecurity Enables or disables the Secure Real-Time Transport Protocol (SRTP). [Enable Media Security] 0 = SRTP is disabled (default). 1 = SRTP is enabled.
Mediant 2000 & TP-1610 & TP-260 Table 6-4: Security Parameter (continues on pages 145 to 146) ini File Field Name Web Parameter Name HTTPSRequireClientCertific ate HTTPSRootFileName HTTPSPkeyFileName [Security Settings > Certificates] HTTPSCertFileName Valid Range and Description Requires client certificates for HTTPS connection. The client certificate must be preloaded to the gateway, and its matching private key must be installed on the managing PC.
SIP User's Manual 6.10 6. Gateway's ini File Configuration RADIUS Parameters For detailed information on the supported RADIUS attributes, refer to Section 8.9 on page 218. Table 6-5: RADIUS Parameters (continues on pages 147 to 148) ini File Field Name Web Parameter Name EnableRADIUS [Enable RADIUS] AAAIndications [AAA Indications] MaxRADIUSSessions [Max. RADIUS Sessions] SharedSecret [Shared Secret] RADIUSRetransmission [RADIUS Max.
Mediant 2000 & TP-1610 & TP-260 Table 6-5: RADIUS Parameters (continues on pages 147 to 148) ini File Field Name Web Parameter Name Valid Range and Description Defines the time (in seconds) the locally stored username and password (verified by the RADIUS server) are valid. When this time expires, the username and password becomes invalid and a must re-verified with the RADIUS server. The valid range is 1 to 0xFFFFFF. -1 = Never expires. 0 = Each request requires RADIUS authentication.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-6: SNMP Parameters (continues on pages 148 to 149) ini File Field Name Web Parameter Name Valid Range and Description SNMPManagerTrapSendingEnable Up to five parameters, each determines the activation/deactivation of _x sending traps to the corresponding SNMP Manager. [SNMP Managers Table] 0 = Sending is disabled 1 = Sending is enabled (default) SNMPTrapManagerHostName Defines a FQDN of a remote host that is used as an SNMP Manager.
Mediant 2000 & TP-1610 & TP-260 6.
SIP User's Manual 6.
Mediant 2000 & TP-1610 & TP-260 Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name DNSQueryType [DNS Query Type] ProxyDNSQueryType [Proxy DNS Query Type] SIP User's Manual Valid Range and Description Enables the use of DNS Naming Authority Pointer (NAPTR) and Service Record (SRV) queries to resolve Proxy and Registrar servers and to resolve all domain names that appear in the Contact and Record-Route headers.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name UseSIPTgrp [Use Tgrp Information] EnableGRUU [Enable GRUU] UserAgentDisplayInfo [User-Agent Information] SessionExpiresMethod [Session Expires Method] Version 5.0 Valid Range and Description 0 = Tgrp parameter isn’t used (default).
Mediant 2000 & TP-1610 & TP-260 Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name UseGatewayNameForOption s [Use Gateway Name for OPTIONS] IsProxyHotSwap [Enable Proxy Hotswap] ProxyHotSwapRtx [Number of RTX before Hotswap] ProxyRedundancyMode [Redundancy Mode] Valid Range and Description 0 = Use the gateway’s IP address in keep-alive OPTIONS messages (default). 1 = Use ‘GatewayName’ in keep-alive OPTIONS messages.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name ProxyLoadBalancingMethod [Proxy Load Balancing Method] ProxyIPListRefreshTime [Proxy IP List Refresh Time] IsFallbackUsed [Enable Fallback to Routing Table] UserName [User Name] Password [Password] Cnonce [Cnonce] IsRegisterNeeded [Enable Registration] Version 5.
Mediant 2000 & TP-1610 & TP-260 Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name RegistrarIP [Registrar IP Address] RegistrarName [Registrar Name] GWRegistrationName [Gateway Registration Name] AuthenticationMode [Authentication Mode] RegistrationTime [Registration Time] RegistrationTimeDivider [Re-registration Timing (%)] RegistrationRetryTime [Registration Retry Time] NumberOfActiveDialogs PrackMode [PRACK Mode] Valid Range and Descrip
SIP User's Manual 6. Gateway's ini File Configuration Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name AssertedIdMode [Asserted Identity Mode] Valid Range and Description 0 = None (default). 1 = P-asserted. 2 = P-preferred. The Asserted ID mode defines the header that is used in the generated INVITE request. The header also depends on the calling Privacy: allowed or restricted.
Mediant 2000 & TP-1610 & TP-260 Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name EnableHistoryInfo [Enable History-Info Header] Valid Range and Description Enables usage of the History-Info header. Valid options include: 0 = Disable (default) 1 = Enable UAC Behavior: Initial request: The History-Info header is equal to the Request URI.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name EnableReasonHeader [Enable Reason Header] EnablePtime EnableUserInfoUsage [Enable User-Information Usage] CoderName Valid Range and Description Enables / disables the usage of the SIP Reason header. 0 = Disable. 1 = Enable (default). 0 = Remove the ptime header from SDP. 1 = Include the ptime header in SDP (default).
Mediant 2000 & TP-1610 & TP-260 Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name Valid Range and Description Transparent [Transparent] 20 (default), 40, 60, 80, 100, 120 Always 64 Dynamic (0-120) Disable [0] Enable [1] QCELP [QCELP] 20 (default), 40, 60, 80, 100, 120 Always 13 Always 12 Disable [0] Enable [1] iLBC [iLBC 20 (default), 40, 60, 80, 100, 120 15 (default) Dynamic (0-120) Disable [0] Enable [1] 30 (default), 60, 90, 12
SIP User's Manual 6. Gateway's ini File Configuration Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name TransparentCoderOnDataCa ll Valid Range and Description 0 = Only use coders from the coder list (default). 1 = Use transparent coder for data calls (according to RFC 4040). The ‘Transparent’ coder can be used on data calls.
Mediant 2000 & TP-1610 & TP-260 Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name DefaultReleaseCause [Default Release Cause] Valid Range and Description Default Release Cause (for IP to Tel calls), used when the gateway initiates a call release, and if an explicit matching cause for this release isn’t found, a default release cause can be configured. The default release cause is described in the Q.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name EnableTransfer [Enable Transfer] XferPrefix [Transfer Prefix] EnableHold [Enable Hold] EnableForward [Enable Call Forward] Valid Range and Description 0 = Call transfer is not allowed. 1 = The gateway responds to a REFER message with ‘Referred-To’ header to initiates a call transfer (default).
Mediant 2000 & TP-1610 & TP-260 Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name TxDTMFOption [DTMF RFC2833 Negotiation] Valid Range and Description Determines a single or several preferred transmit DTMF negotiation methods. 0 (Not Supported) = No negotiation, DTMF digits are sent according to the parameters ‘DTMFTransportType’ and ‘RFC2833PayloadType’ (default).
SIP User's Manual 6. Gateway's ini File Configuration Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name MaxActiveCalls [Max Number Of Active Calls] MaxCallDuration [Max Call Duration] EnableBusyOut [Enable Busy Out] EnableDigitDelivery2IP [Enable Digit Delivery to IP] EnableDigitDelivery [Enable Digit Delivery to Tel] Version 5.
Mediant 2000 & TP-1610 & TP-260 Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name SITDetectorEnable AMDTimeout RTPOnlyMode SIP User's Manual Valid Range and Description Enables or disables Special Information Tone (SIT) detection according to the ITU-T recommendation E.180/Q.35. Valid options include: 0 = Disable (default). 1 = Enable.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name Valid Range and Description Profile Parameters CoderName_ID Defines groups of coders that can be associated with IP or Tel profiles (up to five coders in each group). Enter coder groups in the following format: CoderName_=,,,,.
Mediant 2000 & TP-1610 & TP-260 Table 6-7: SIP Configuration Parameters (continues on pages 150 to 169) ini File Field Name Web Parameter Name Valid Range and Description 30 (default), 60, 90, 120 13 T.38 [t38fax] N/A N/A N/A N/A G.711A-law_VBD [g711AlawVbd] 10, 20 (default), 30, 40, 50, 60, 80, 100, 120 Always 64 Dynamic (0-120) N/A G.711U-law_VBD [g711UlawVbd] 10, 20 (default), 30, 40, 50, 60, 80, 100, 120 Always 64 Dynamic (0-120) N/A Note 1: The coder name is case-sensitive.
SIP User's Manual 6.
Mediant 2000 & TP-1610 & TP-260 6.13 Voice Mail Parameters For detailed information on the Voice Mail (VM) application, refer to the CPE Configuration Guide for Voice Mail. Table 6-8: Voice Mail Configuration Parameters (continues on pages 170 to 171) ini File Field Name Web Parameter Name Valid Range and Description Enables the VM application on the gateway and determines the communication method used between the PBX and the gateway.
SIP User's Manual 6.
Mediant 2000 & TP-1610 & TP-260 6.14 ISDN and CAS Interworking-Related Parameters Table 6-9: ISDN and CAS Interworking-Related Parameters (continues on pages 172 to 179) ini File Field Name Web Parameter Name EnableTDMoverIP [Enable TDM Tunneling] Valid Range and Description 0 = Disabled (default). 1 = TDM Tunneling is enabled.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-9: ISDN and CAS Interworking-Related Parameters (continues on pages 172 to 179) ini File Field Name Web Parameter Name PlayRBTone2Trunk_ID [Play Ringback Tone to Trunk] Valid Range and Description ID = Trunk number (0-7). 0 (Don’t play) = The ISDN / CAS gateway doesn’t play a Ringback Tone (RBT). No PI is sent to the ISDN, unless the parameter ‘Progress Indicator to ISDN’ is configured differently.
Mediant 2000 & TP-1610 & TP-260 Table 6-9: ISDN and CAS Interworking-Related Parameters (continues on pages 172 to 179) ini File Field Name Web Parameter Name PlayRBTone2IP [Play Ringback Tone to IP] DefaultCauseMapISDN2I P [Default Cause Mapping From ISDN to IP] CauseMapSIP2ISDN_ID [Release Cause Mapping from SIP to ISDN] CauseMapISDN2SIP_ID [Release Cause Mapping from ISDN to SIP] RemoveCLIWhenRestrict ed [Remove CLI when Restricted] SIP User's Manual Valid Range and Description 0 = Ringback tone i
SIP User's Manual 6.
Mediant 2000 & TP-1610 & TP-260 Table 6-9: ISDN and CAS Interworking-Related Parameters (continues on pages 172 to 179) ini File Field Name Web Parameter Name PSTNAlertTimeout [PSTN Alert Timeout] ISDNTransferCapability_I D [ISDN Transfer Capabilities] Valid Range and Description Alert Timeout in seconds (ISDN T301 timer) for outgoing calls to PSTN. The default is 180 seconds. The range is 0 to 240. Note: The PSTN stack T301 timer can be overridden by a lower value, but it can’t be increased.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-9: ISDN and CAS Interworking-Related Parameters (continues on pages 172 to 179) ini File Field Name Web Parameter Name EnableAOC TimeForReorderTone DisconnectOnBusyTone [Disconnect Call on Detection of Busy Tone] PlayBusyTone2ISDN [Play Busy Tone to Tel] TrunkTransferMode_X CASTransportType [CAS Transport Type] CASAddressingDelimiter s Version 5.0 Valid Range and Description 0 = Not used (default).
Mediant 2000 & TP-1610 & TP-260 Table 6-9: ISDN and CAS Interworking-Related Parameters (continues on pages 172 to 179) ini File Field Name Web Parameter Name EnableVoiceDetection EnableDSPIPMDetectors XChannelHeader Valid Range and Description 1 = The gateway sends 200 OK message (in response to INVITE) when speech/fax/modem is detected. 0 = The gateway sends 200 OK message (in response to INVITE) immediately after the gateway finishes dialing (default).
SIP User's Manual 6. Gateway's ini File Configuration Table 6-9: ISDN and CAS Interworking-Related Parameters (continues on pages 172 to 179) ini File Field Name Web Parameter Name EnablePatternDetector [Enable Pattern Detector] PDThreshold PDPattern Version 5.0 Valid Range and Description Enables or disables activation of the Pattern Detector (PD). Valid options include: 0 = Disable (default). 1 = Enable. Defines the number of consecutive patterns to trigger the pattern detection event.
Mediant 2000 & TP-1610 & TP-260 6.15 Number Manipulation and Routing Parameters Table 6-10: Number Manipulation and Routing Parameters (continues on pages 180 to 188) ini File Field Name Web Parameter Name TrunkGroup_x [Trunk Group Table] Valid Range and Description TrunkGroup_x = T-U/a-b,c,d x = Trunk group ID (1 to 99). T = Starting physical trunk number (0 to 7). U = Ending physical trunk number (0 to 7). a = Starting B-channel (from 1). b = Ending B-channel (up to 31).
SIP User's Manual 6. Gateway's ini File Configuration Table 6-10: Number Manipulation and Routing Parameters (continues on pages 180 to 188) ini File Field Name Web Parameter Name ChannelSelectMode [Channel Select Mode] Valid Range and Description Defines common rule of port allocation for IP to TEL calls. • • • • • • • 0 = By phone number - Select the gateway port according to the called number (refer to the note below).
Mediant 2000 & TP-1610 & TP-260 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 180 to 188) ini File Field Name Web Parameter Name AddNPIandTON2CallingNu mber [Add NPI and TON to Calling Number] AddNPIandTON2CalledNu mber [Add NPI and TON to Called Number] UseSourceNumberAsDispl ayName [Use Source Number as Display Name] UseDisplayNameAsSource Number [Use Display Name as Source Number] AlwaysUseRouteTable [Use Routing Table for Host Names and Profiles] SIP User's Manual Valid
SIP User's Manual 6. Gateway's ini File Configuration Table 6-10: Number Manipulation and Routing Parameters (continues on pages 180 to 188) ini File Field Name Web Parameter Name Prefix [Tel to IP Routing Table] PSTNPrefix [IP to Trunk Group Routing Table] Valid Range and Description Prefix = ,,, For example: Prefix = 20,10.2.10.2,202,1 Prefix = 10[340-451]xxx#,10.2.10.6,*,1 Prefix = *,gateway.domain.
Mediant 2000 & TP-1610 & TP-260 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 180 to 188) ini File Field Name Web Parameter Name RemovePrefix [IP to Tel Remove Routing Table Prefix] RouteModeIP2Tel [IP to Tel routing Mode] RouteModeTel2IP [Tel to IP routing Mode] SwapRedirectNumber [Swap Redirect and Called Numbers] Prefix2RedirectNumber [Add Prefix to Redirect Number] AddTON2RPI [Add Number Plan and Type to Remote Party ID Header] NumberMapTel2IP [Destination Phone Number
SIP User's Manual 6. Gateway's ini File Configuration Table 6-10: Number Manipulation and Routing Parameters (continues on pages 180 to 188) ini File Field Name Web Parameter Name NumberMapIP2Tel [Destination Phone Number Manipulation Table for IPÆTel calls] Valid Range and Description Manipulate the destination number for IP to Tel calls. NumberMapIP2Tel = a,b,c,d,e,f,g,h,i a = Destination number prefix b = Number of stripped digits from the left, or (if brackets are used) from the right.
Mediant 2000 & TP-1610 & TP-260 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 180 to 188) ini File Field Name Web Parameter Name SourceNumberMapIP2Tel [Source Phone Number Manipulation Table for IPÆTel calls] Valid Range and Description Manipulate the source number for IP to Tel calls. SourceNumberMapIP2Tel = a,b,c,d,e,f,g,h,i a = Source number prefix b = Number of stripped digits from the left, or (if brackets are used) from the right.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-10: Number Manipulation and Routing Parameters (continues on pages 180 to 188) ini File Field Name Web Parameter Name AltRouteCauseTel2IP [Reasons for Alternative Routing Table] Valid Range and Description Table of call failure reason values received from the IP side. If a call is released as a result of one of these reasons, the gateway tries to find an alternative route to that call in the ‘Tel to IP Routing’ table.
Mediant 2000 & TP-1610 & TP-260 Table 6-10: Number Manipulation and Routing Parameters (continues on pages 180 to 188) ini File Field Name Web Parameter Name Valid Range and Description IPConnQoSMaxAllowedDel ay [Max Allowed Delay for Alt Routing] Transmission delay (in msec) at which the IP connection is considered a failure. The range is 100 to 1000. The default value is 250 msec.
SIP User's Manual 6.16 6. Gateway's ini File Configuration E1/T1 Configuration Parameters Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 189 to 195) ini File Field Name Web Parameter Name TDMBusType PCMLawSelect [PCM Law Select] ProtocolType [Protocol Type] ProtocolType_x [Protocol Type] TraceLevel [Trace Level] Version 5.0 Valid Range and Description TP-260 only. Must be set to 2. 1 = A-law (default) 3 = µ-Law Usually A-Law is used for E1 spans and µ-Law for T1 and J1 spans.
Mediant 2000 & TP-1610 & TP-260 Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 189 to 195) ini File Field Name Web Parameter Name FramingMethod [Framing Method] FramingMethod_x [Framing Method] TerminationSide [ISDN Termination Side] TerminationSide_x [ISDN Termination Side] ClockMaster [Clock Master] ClockMaster_x [Clock Master] TDMBusClockSource [TDM Bus Clock Source] TDMBusPSTNAutoClockEn able [TDM Bus PSTN Auto Clock] TDMBusLocalReference [TDM Bus Local Reference] AutoClockTrunk
SIP User's Manual 6. Gateway's ini File Configuration Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 189 to 195) ini File Field Name Web Parameter Name TDMBusPSTNAutoClockRe vertingEnable [TDM Bus PSTN Auto Clock Reverting] LineCode [Line Code] LineCode_x [Line Code] BchannelNegotiation [B-channel Negotiation] NFASGroupNumber_x [NFAS Group Number] DchConfig_x [D-channel Configuration] ISDNNFASInterfaceID_x [NFAS Interface ID] CASTableIndex_x [CAS Table] Version 5.
Mediant 2000 & TP-1610 & TP-260 Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 189 to 195) ini File Field Name Web Parameter Name CASFileName_0 CASFileName_1 CASFileName_7 CASTablesNum IdleABCDPattern [Idle ABCD Pattern] IdlePCMPattern [Idle PCM Pattern] LineBuildOut.Loss [Line Build Out Loss] ISDNRxOverlap_x [Enable Receiving of Overlap Dialing] Valid Range and Description CAS file name (e.g., ‘E_M_WinkTable.dat’) that defines the CAS protocol.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 189 to 195) ini File Field Name Web Parameter Name DigitMapping [Digit Mapping Rules] Valid Range and Description Digit map pattern (used to reduce the dialing period when Overlap dialing is used). If the digit string (dialed number) has matched one of the patterns in the digit map, the gateway stops collecting digits and starts to establish a call with the collected number.
Mediant 2000 & TP-1610 & TP-260 Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 189 to 195) ini File Field Name Web Parameter Name Valid Range and Description ISDN Flexible Behavior Parameters ISDN protocol is implemented in different Switches / PBXs by different vendors. Several implementations vary a little from the specification. Therefore, to provide a flexible interface that supports these ISDN variants, the ISDN behavior parameters are used.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-11: E1/T1/J1 Configuration Parameters (continues on pages 189 to 195) ini File Field Name Web Parameter Name ISDNGeneralCCBehavior [General Call Control Behavior] ISDNOutCallsBehavior [Outgoing Calls Behavior] ISDNIBehavior_x [Q.931 Layer Response Behavior] ISDNInCallsBehavior_x [Incoming Calls Behavior] ISDNOutCallsBehavior_x [Outgoing Calls Behavior] Version 5.
Mediant 2000 & TP-1610 & TP-260 6.17 Channel Parameters The Channel Parameters define the DTMF, fax and modem transfer modes. Refer to Section 8.3 on page 210 for a detailed description of Fax and Modem transfer modes; refer to Section 8.2 on page 208 for detailed description on DTMF transport modes. Note that the Default Channel Parameters are applied to all the gateway's channels.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-12: Channel Parameters (continues on pages 196 to 200) ini File Field Name Web Parameter Name Valid Range and Description Number of (20 msec) coder payloads that are used to generate a fax/modem bypass packet. The valid range is 1, 2 or 3 coder payloads. The default value is 1 coder payload. FaxBypassPayloadType Determines the fax bypass RTP dynamic payload type. [Fax Bypass Payload Type] The valid range is 96 to 120.
Mediant 2000 & TP-1610 & TP-260 Table 6-12: Channel Parameters (continues on pages 196 to 200) ini File Field Name Web Parameter Name V22ModemTransportType [V.22 Modem Transport Type] V23ModemTransportType [V.23 Modem Transport Type] V32ModemTransportType [V.32 Modem Transport Type] V34ModemTransportType [V.
SIP User's Manual 6. Gateway's ini File Configuration Table 6-12: Channel Parameters (continues on pages 196 to 200) ini File Field Name Web Parameter Name Valid Range and Description 0 = There isn’t a Cisco gateway at the remote side (default). 1 = There is a Cisco gateway at the remote side. When there is a Cisco gateway at the remote side, the local gateway must set the value of the ‘annexb’ parameter of the fmtp attribute in the SDP to ‘no’.
Mediant 2000 & TP-1610 & TP-260 Table 6-12: Channel Parameters (continues on pages 196 to 200) ini File Field Name Web Parameter Name RFC2833PayloadType [RFC 2833 Payload Type] MGCPDTMFDetectionPoint DTMFInterDigitInterval DTMFDigitLength VQMonEnable [Enable RTCP XR] RTCPInterval [RTCP XR Packet Interval] DisableRTCPRandomize [Disable RTCP XR Interval Randomization] RTCPXREscIP [RTCP XR Collection Server] RTCPXRReportMode [RTCP XR Report Mode] SIP User's Manual Valid Range and Description The RFC 28
SIP User's Manual 6.18 6. Gateway's ini File Configuration Configuration Files Parameters The configuration files (Call Progress Tones, PRT, Voice Prompts and CAS) can be loaded to the gateway via the Embedded Web Server (refer to Section 5.8.2 on page 119), or via TFTP session. ¾ To load the configuration files via TFTP, take these 3 steps: 1. 2. 3. In the ini file, define the files to be loaded to the device.
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 202 Document #: LTRT-68805
SIP User's Manual 7 7. Using BootP / DHCP Using BootP / DHCP The gateway uses the Bootstrap Protocol (BootP) and the Dynamic Host Configuration Protocol (DHCP) to obtain its networking parameters and configuration automatically after it is reset. BootP and DHCP are also used to provide the IP address of a TFTP server on the network, and files (cmp and ini) to be loaded into memory. DHCP is a communication protocol that automatically assigns IP addresses from a central point.
Mediant 2000 & TP-1610 & TP-260 7.2 Using DHCP When the gateway is configured to use DHCP (DHCPEnable = 1), it attempts to contact the enterprise’s DHCP server to obtain the networking parameters (IP address, subnet mask, default gateway, primary/secondary DNS server and two SIP server addresses). These network parameters have a ‘time limit’. After the time limit expires, the gateway must ‘renew’ its lease from the DHCP server.
SIP User's Manual 7. Using BootP / DHCP 7.3 Using BootP 7.3.1 Upgrading the Gateway When upgrading the gateway (loading new software onto the gateway) using the BootP/TFTP configuration utility: From version 4.4 to version 4.4 or to any higher version, the device retains its configuration (ini file). However, the auxiliary files (CPT, logo, etc.) may be erased. From version 4.6 to version 4.
Mediant 2000 & TP-1610 & TP-260 Table 7-2 exemplifies the structure of the vendor specific information field for a TP-1610 slave module with IP address 10.2.70.1.
SIP User's Manual 8. Telephony Capabilities 8 Telephony Capabilities 8.1 Working with Supplementary Services The gateway gateway supports the following supplementary services: Call Hold / Retrieve (refer to Section 8.1.1 on page 207) Call Transfer (refer to Section 8.1.2 on page 207) Call Forward (doesn't initiate call forward, only responds to call forward request) Call Waiting The gateway SIP users are only required to enable the Hold and Transfer features.
Mediant 2000 & TP-1610 & TP-260 After A completed dialing C, A can perform the transfer by on-hooking the A phone. After the transfer is completed, B and C parties are engaged in a call. The transfer can be initiated at any of the following stages of the call between A to C: Just after completing dialing C phone number - Transfer from setup. While hearing ring back – Transfer from alert. While speaking to C – Transfer from active.
SIP User's Manual 4. Using RFC 2833 relay with Payload type negotiation: In this mode, DTMF digits are carried to the remote side as part of the RTP stream in accordance with RFC 2833 standard. To enable this mode set: • 5. 8.
Mediant 2000 & TP-1610 & TP-260 8.3 Fax & Modem Transport Modes 8.3.1 Fax/Modem Settings Users can choose to use for fax, and for each modem type (V.22/V.23/Bell/V.32/V.34), one of the following transport methods: Fax relay mode (demodulation / remodulation, not applicable to Modem), Bypass (using a high bit rate coder to pass the signal), or Transparent (passing the signal in the current voice coder).
SIP User's Manual 8.3.1.3 8. Telephony Capabilities Supporting V.34 Faxes V.34 fax machine support is available only in bypass mode (fax relay is not supported) when the channel is configured in one of the configurations described below: FaxTransportMode = 2 (Bypass) V34ModemTransportType = 2 (Modem bypass) In this configuration, both T.30 and V.34 faxes work in Bypass mode Or FaxTransportMode = 1 (Relay) V34ModemTransportType = 2 (Modem bypass) In this configuration, T.30 faxes use Relay mode (T.
Mediant 2000 & TP-1610 & TP-260 8.4 Event Notification using X-Detect Header The gateway supports the sending of notifications to a remote party notifying the occurrence (or detection) of certain events on the media stream. Event detection and notifications is performed using the X-Detect SIP message header, and only when establishing a SIP dialog. For supporting some events, certain gateway configurations need to be performed.
SIP User's Manual 8. Telephony Capabilities Below is an example of SIP messages implementing the X-Detect header: INVITE sip:101@10.33.2.53;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.33.2.53;branch=z9hG4bKac5906 Max-Forwards: 70 From: "anonymous" ;tag=1c25298 To: Call-ID: 11923@10.33.2.53 CSeq: 1 INVITE Contact: X- Detect: Request=CPT,FAX SIP/2.0 200 OK Via: SIP/2.0/UDP 10.33.2.
Mediant 2000 & TP-1610 & TP-260 8.5 ThroughPacket™ The gateway supports a proprietary method to aggregate RTP streams from several channels to reduce the bandwidth overhead caused by the attached Ethernet, IP, UDP and RTP headers, and to reduce the packet / data transmission rate. This option reduces the load on network routers and can typically save 50% (e.g., for G.723) on IP bandwidth.
SIP User's Manual 8.6 8. Telephony Capabilities Dynamic Jitter Buffer Operation Voice frames are transmitted at a fixed rate. If the frames arrive at the other end at the same rate, voice quality is perceived as good. In many cases, however, some frames can arrive slightly faster or slower than the other frames. This is called jitter (delay variation), and degrades the perceived voice quality. To minimize this problem, the gateway uses a jitter buffer.
Mediant 2000 & TP-1610 & TP-260 8.7 Configuring the Gateway’s Alternative Routing (based on Connectivity and QoS) The Alternative Routing feature enables reliable routing of Tel to IP calls when Proxy isn’t used. The gateway periodically checks the availability of connectivity and suitable Quality of Service (QoS) before routing. If the expected quality cannot be achieved, an alternative IP route for the prefix (phone number) is selected.
SIP User's Manual 8.7.4 8. Telephony Capabilities Relevant Parameters The following parameters (described in Table 6-10) are used to configure the Alternative Routing mechanism: 8.8 AltRoutingTel2IPEnable AltRoutingTel2IPMode IPConnQoSMaxAllowedPL IPConnQoSMaxAllowedDelay Call Detail Report The Call Detail Report (CDR) contains vital statistic information on calls made by the gateway.
Mediant 2000 & TP-1610 & TP-260 Table 8-2: Supported CDR Fields (continues on pages 217 to 218) Field Name Description ReleaseTime RTPdelay RTPjitter RTPssrc RemoteRTPssrc RedirectReason TON NPI RedirectPhonNum 8.
SIP User's Manual 8. Telephony Capabilities Table 8-3: Supported RADIUS Attributes (continues on pages 218 to 219) Attribute Number Attribute Name 26 h323-gw-id 30 Called-StationId 31 Calling-StationId 40 Acct-StatusType 41 Acct-DelayTime Acct-InputOctets Acct-OutputOctets 42 43 44 Acct-Session-Id 46 Acct-SessionTime Acct-InputPackets Acct-OutputPackets 47 48 61 VSA No.
Mediant 2000 & TP-1610 & TP-260 8.9.1 RADIUS Server Messages In Figure 8-1 below, non-standard parameters are preceded with brackets. Figure 8-1: Accounting Example Accounting-Request (361) user-name = 111 acct-session-id = 1 nas-ip-address = 212.179.22.
SIP User's Manual 8.10 8. Telephony Capabilities Trunk to Trunk Routing Example This example describes two AudioCodes 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’ generates calls to PSTN on the same E1 Trunk as the call was originally received (in gateway ‘A’). Gateway ‘A’ IP address is 192.168.3.50 Gateway ‘B’ IP address is 192.168.3.51 Ini File Parameters of Gateways ‘A’ and ‘B’: 1.
Mediant 2000 & TP-1610 & TP-260 8.11 Proxy or Registrar Registration Example REGISTER sip:servername SIP/2.0 VIA: SIP/2.0/UDP 212.179.22.229;branch=z9hG4bRaC7AU234 From: ;tag=1c29347 To: Call-ID: mailto:10453@212.179.22.229 Seq: 1 REGISTER Expires: 3600 Contact: sip:GWRegistrationName@212.179.22.
SIP User's Manual 8.12 8. Telephony Capabilities SIP Call Flow Example The SIP call flow, shown in Figure 8-2, describes SIP messages exchanged between a Mediant 2000 gateway and an MP-108 gateway during a simple call. MP-108 (10.8.201.108) with phone number ‘8000’, calls Mediant 2000 (10.8.201.10) with phone number ‘1000’: Figure 8-2: SIP Call Flow Example F1 10.8.201.108 ==> 10.8.201.10 INVITE INVITE sip:1000@10.8.201.10;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.201.
Mediant 2000 & TP-1610 & TP-260 F2 10.8.201.10 ==> 10.8.201.108 Trying SIP/2.0 100 Trying Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacsiJkDGd From: ;tag=1c5354 To: Call-ID: 534366556655skKw-8000--1000@10.8.201.108 Server: Audiocodes-Sip-Gateway/TrunkPack 1610/v.4.20.299.412 CSeq: 18153 INVITE Content-Length: 0 F3 10.8.201.10 ==> 10.8.201.108 180 Ringing SIP/2.0 180 Ringing Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacsiJkDGd From:
SIP User's Manual 8. Telephony Capabilities F5 10.8.201.108 ==> 10.8.201.10 ACK ACK sip:1000@10.8.201.10;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacZYpJWxZ From: ;tag=1c5354 To: ;tag=1c7345 Call-ID: 534366556655skKw-8000--1000@10.8.201.108 User-Agent: Audiocodes-Sip-Gateway/MP-108 FXS/v.4.20.299.410 CSeq: 18153 ACK Supported: 100rel,em Content-Length: 0 Note: Phone ‘8000’ goes on-hook; gateway 10.8.201.108 sends BYE to gateway 10.8.201.
Mediant 2000 & TP-1610 & TP-260 8.13 SIP Authentication Example The gateway supports basic and digest authentication types, according to SIP RFC 3261 standard. A proxy server might require authentication before forwarding an INVITE message. A Registrar/Proxy server may also require authentication for client registration. A proxy replies to an unauthenticated INVITE with a 407 Proxy Authorization Required response, containing a Proxy-Authenticate header with the form of the challenge.
SIP User's Manual 8. Telephony Capabilities The equation to be evaluated: ‘REGISTER:sip:10.2.2.222’. The MD5 algorithm is run on this equation and stored for future usage. The result is:’a9a031cfddcb10d91c8e7b4926086f7e’ The final stage: The A1 result The nonce from the proxy response: ‘11432d6bce58ddf02e3b5e1c77c010d2’ The A2 result The equation to be evaluated: ‘A1:11432d6bce58ddf02e3b5e1c77c010d2:A2’. The MD5 algorithm is run on this equation.
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 228 Document #: LTRT-68805
SIP User's Manual 9. Networking Capabilities 9 Networking Capabilities 9.1 Ethernet Interface Configuration Using the parameter ‘EthernetPhyConfiguration‘, users can control the Ethernet connection mode. Either the manual modes (10 Base-T Half-Duplex, 10 Base-T Full-Duplex, 100 Base-TX Half-Duplex, 100 Base-TX Full-Duplex) or Auto-Negotiate mode can be used.
Mediant 2000 & TP-1610 & TP-260 For correct functionality of the redundancy mechanism, it is recommended to configure both links to the same mode. It is essential that both link partners (the primary link partner and the secondary link partner) have the same capabilities, so that whenever a switchover occurs the gateway is able to provide at least the same Ethernet services as were provided prior to the switchover.
SIP User's Manual 9.3.1 9. Networking Capabilities STUN Simple Traversal of UDP through NATs (STUN) (according to RFC 3489) is a client / server protocol that solves most of the NAT traversal problems. The STUN server operates in the public Internet and the STUN clients are embedded in end-devices (located behind NAT). STUN is used both for the signaling and the media streams. STUN works with many existing NAT types, and does not require any special behavior from them.
Mediant 2000 & TP-1610 & TP-260 9.3.2 First Incoming Packet Mechanism If the remote gateway resides behind a NAT device, it’s possible that the gateway can activate the RTP/RTCP/T.38 streams to an invalid IP address / UDP port. To avoid such cases, the gateway automatically compares the source address of the incoming RTP/RTCP/T.38 stream with the IP address and UDP port of the remote gateway.
SIP User's Manual 9.4 9. Networking Capabilities Point-to-Point Protocol over Ethernet (PPPoE) PPPoE is a method of sending the Point-to-Point Protocol over Ethernet network. 9.4.1 Point-to-Point Protocol (PPP) Overview Point-to-Point Protocol (PPP) provides a method of transmitting data over serial point-topoint links. The protocol defines establishing, configuring and testing the data link connection and the network protocol.
Mediant 2000 & TP-1610 & TP-260 9.4.2 PPPoE Overview PPPoE is a method of sending the Point-to-Point Protocol over Ethernet network. PPPoE provides the ability to connect a network of hosts over a simple bridging access device to a remote Access Concentrator. Access control, billing and type of service can be done on a per-user, rather than a per-site, basis.
SIP User's Manual 9. Networking Capabilities When working in a PPPoE environment, the gateway negotiates for its IP address (as described above). However, if the user desires to disable the PPPoE client, the gateway can be configured to use default values for IP address, subnet mask and default gateway. This can be done using ini file parameters PPPoERecoverIPAddress, PPPoERecoverSubnetMask and PPPoERecoverDfgwAddress.
Mediant 2000 & TP-1610 & TP-260 9.8 Simple Network Time Protocol Support The Simple Network Time Protocol (SNTP) client functionality generates requests and reacts to the resulting responses using the NTP version 3 protocol definitions (according to RFC 1305). Through these requests and responses, the NTP client is able to synchronize the system time to a time source within the network, thereby eliminating any potential issues should the local system clock 'drift' during operation.
SIP User's Manual 9.10 9. Networking Capabilities VLANS and Multiple IPs 9.10.1 Multiple IPs Media, Control, and Management (OAM) traffic in the gateway can be assigned one of the following IP addressing schemes: Single IP address for all traffic (i.e., Media, Control, and OAM). Separate IP address for each traffic type. For separate IP addresses, the different traffic types are separated into three dedicated networks.
Mediant 2000 & TP-1610 & TP-260 For the mapping of an application to its class-of-service and traffic type, refer to Table 9-1 below. Media traffic type is assigned ‘Premium media’ class of service, Management traffic type is assigned ‘Bronze’ class of service, and Control traffic type is assigned ‘Premium control’ class of service.
SIP User's Manual 9. Networking Capabilities 9.10.2.1 Operation Outgoing packets (from the gateway to the switch): All outgoing packets are tagged, each according to its interface (control, media or OAM). If the gateway’s native ID is identical to one of the other IDs (usually to the OAM ID), this ID (e.g., OAM) is set to zero on outgoing packets (VlanSendNonTaggedOnNative = 0). This method is called Priority Tagging (p tag without Q tag).
Mediant 2000 & TP-1610 & TP-260 9.10.3.1 Integrating Using the Embedded Web Server ¾ To integrate the gateway into a VLAN and multiple IPs network using the Embedded Web Server, take these 7 steps: 1. 2. 3. Access the Embedded Web Server (Section 5.3 on page 58). Use the Software Upgrade Wizard (Section 5.8.1 on page 115) to load and burn the firmware version to the gateway (VLANs and multiple IPs support is available only when the firmware is burned to flash).
SIP User's Manual 9. Networking Capabilities Figure 9-3: Example of the IP Settings Screen 5. • Click the Submit button to save your changes.
Mediant 2000 & TP-1610 & TP-260 9.10.3.2 Integrating Using the ini File ¾ To integrate the gateway into a VLAN and multiple IPs network using the ini file, take these 3 steps: 1.
SIP User's Manual 10. Advanced PSTN Configuration 10 Advanced PSTN Configuration 10.1 Gateway Clock Settings The gateway can either generate its own timing signals, using an internal clock, or recover them from one of the E1/T1 trunks.
Mediant 2000 & TP-1610 & TP-260 Relevant parameters (described in Table 6-11 on page 189): 10.3 ISDNRxOverlap TimeBetweenDigits MaxDigits ISDNInCallsBehavior DigitMapping ISDNRxOverlap_x Using ISDN NFAS In regular (non-NFAS) T1 ISDN trunks, a single 64 kbps channel carries signaling for the other 23 B-channels of that particular T1 trunk. This channel is called the D-channel and usually resides on timeslot # 24.
SIP User's Manual 10. Advanced PSTN Configuration 10.3.1 NFAS Interface ID Several ISDN switches require an additional configuration parameter per T1 trunk that is called ‘Interface Identifier’. In NFAS T1 trunks the Interface Identifier is sent explicitly in Q.931 Setup / Channel Identification IE for all NFAS trunks, except for the B-channels of the Primary trunk (refer to note 1 below).
Mediant 2000 & TP-1610 & TP-260 10.
SIP User's Manual 11. Advanced System Capabilities 11 Advanced System Capabilities 11.1 Restoring Networking Parameters to their Initial State You can use the ‘Reset’ button to restore the Mediant 2000 / TP-1610 networking parameters (described in Table 4-1) to their factory default values and to reset the username and password. Note that the gateway returns to the software version burned in flash. This process also restores the gateway’s parameters to their factory settings.
Mediant 2000 & TP-1610 & TP-260 11.2 Establishing a Serial Communications Link with the Mediant 2000 Use serial communication software (e.g., HyperTerminalTM) to establish a serial communications link with the Mediant 2000 via the RS-232 connection. You can use this link to change the networking parameters (Section 4.2.3 on page 51) and to receive error / notification messages. Note: The TP-260 amd TP-1610 don't provide an RS-232 port.
SIP User's Manual 11.3 11. Advanced System Capabilities Automatic Update Mechanism The gateway is capable of automatically updating its cmp, ini and configuration files. These files can be stored on any standard Web, FTP or NFS server/s and can be loaded periodically to the gateway via HTTP, HTTPS, FTP or NFS. This mechanism can be used even for Customer Premise(s) Equipment (CPE) devices that are installed behind NAT and firewalls. The Automatic Update mechanism is applied separately to each file.
Mediant 2000 & TP-1610 & TP-260 The following example illustrates how to utilize Automatic Updates for deploying devices with minimum manual configuration. ¾ To utilize Automatic Updates for deploying the gateway with minimum manual configuration, take these 5 steps: 1. 2. 3. Set up a Web server (in the following example it is http://www.corp.com/) where all configuration files are to be stored. To each device, pre-configure the following parameter (DHCP / DNS are assumed): IniFileURL = 'http://www.corp.
SIP User's Manual 11.4 11. Advanced System Capabilities Startup Process The startup process (illustrated in Figure 11-3 on page 252) begins when the gateway is reset (physically or from the Web / SNMP) and ends when the operational software is running. In the startup process, the network parameters, software and configuration files are obtained. After the gateway powers up or after it is physically reset, it broadcasts a BootRequest message to the network.
Mediant 2000 & TP-1610 & TP-260 Figure 11-3: Gateway's Startup Process SIP User's Manual 252 Document #: LTRT-68805
SIP User's Manual 11.5 11. Advanced System Capabilities Using Parameter Tables The gateway 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. Tables are composed of lines and columns. Columns represent parameters’ types. Lines represent specific entities. The instances in each line are called line attributes.
Mediant 2000 & TP-1610 & TP-260 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. The following permissions are available: Read: Value of the field can be read. Write: Value of the field can be modified.
SIP User's Manual 11. Advanced System Capabilities 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. Consequently, tables are loaded with all parameters having at least one of the following permissions: Write, Create or Maintenance Write.
Mediant 2000 & TP-1610 & TP-260 Figure 11-4 displays an example of the structure of a parameter table in the ini file. Figure 11-4: Structure of a Parameter Table in the ini File ; Table: Items Table. ; Fields: Item_Name, Item_Serial_Number, Item_Color, Item_weight. ; NOTE: Item_Color is not specified. It will be given default value.
SIP User's Manual 11.6 11. Advanced System Capabilities Customizing the Web Interface Customers incorporating the gateway's into their portfolios can customize the device’s 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; a customized title bar is shown in Figure 11-6).
Mediant 2000 & TP-1610 & TP-260 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. 5. Click the Send File button; the file is sent to the device. When loading is complete, the screen is automatically refreshed and the new logo image is displayed. 6. Note the appearance of the logo.
SIP User's Manual 11. Advanced System Capabilities Table 11-3: Customizable Logo ini File Parameters Parameter LogoFileName Description The name of the image file containing your corporate logo. Use a gif, jpg or jpeg image file. The default is AudioCodes’ logo file. Note: The length of the name of the image file is limited to 47 characters. Width (in pixels) of the logo image. Note: The optimal setting depends on the resolution settings.
Mediant 2000 & TP-1610 & TP-260 The new background appears on all Web Interface screens. Tip 1: If you encounter any problem during the loading of the files, or you want to restore the default images, click the Restore Default Images button. Tip 2: When replacing both the background image and the logo image, first load the logo image followed by the background image.
SIP User's Manual 11. Advanced System Capabilities 11.6.4 Modifying ini File Parameters via the Web AdminPage ¾ To modify ini file parameters via the AdminPage, take these 6 steps: 1. 2. 3. Access the gateway's Embedded Web Server (refer to Section 5.3 on page 58). 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. Click the INI Parameters option, the INI Parameters screen is displayed (shown in Figure 11-8).
Mediant 2000 & TP-1610 & TP-260 11.7 Software Upgrade Key The gateways are supplied with a Software Upgrade Key already pre-configured for each of its TrunkPack Modules (TPM). Users can later upgrade their gateway's features, capabilities and quantity of available resources by specifying what upgrades they require, and purchasing a new key to match their specification. The Software Upgrade Key is sent as a string in a text file, to be loaded onto the gateway.
SIP User's Manual 11. Advanced System Capabilities 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 6 steps: 1. 2. 3. 4. 5. 6. Access the devices Embedded Web Server (refer to Section 5.3 on page 58). Click the Software Update button. Click the Software Upgrade Key tab; the Software Upgrade Key screen is displayed (shown in Figure 11-9).
Mediant 2000 & TP-1610 & TP-260 Figure 11-10: Example of a Software Upgrade Key File Containing Multiple S/N Lines 11.7.2.2 Loading the Software Upgrade Key Using BootP/TFTP ¾ To load the Software Upgrade Key file using BootP/TFTP, take these 5 steps: 1. 2. 3. 4. 5. Place the file in the same location you’ve saved the device’s cmp file. Note that in order to load the Software Upgrade Key via TFTP server, the extension of the key file must be ini.
SIP User's Manual 11. Advanced System Capabilities 11.7.5 Abort Procedure Reload the key you backed-up in Section Backing up the Current Software Upgrade Key on page 262 to restore your device capabilities to what they originally. To load the backedup key use the procedure described in Section Loading the Software Upgrade Key on page 262. Version 5.
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 266 Document #: LTRT-68805
SIP User's Manual 12. Special Applications 12 Special Applications 12.1 TDM Tunneling The gateway's TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network.
Mediant 2000 & TP-1610 & TP-260 Figure 12-1: ini File Example for TDM Tunneling (Originating Side) EnableTDMOverIP = 1 ;E1_TRANSPARENT_31 ProtocolType_0 = 5 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 ; coder for B-channels (time slot 16) that carries PRI signaling.
SIP User's Manual 12.2 12. Special Applications 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.
Mediant 2000 & TP-1610 & TP-260 12.2.1 MTP2 Tunneling Technology The SS7 tunneling technology is based on a pairing of remote and central gateways, as shown in Figure 12-5. The remote gateways are configured to backhaul MTP layer 2 signaling over the IP network using standard M2UA protocol (over SCTP protocol). The function of the M2TN entity is to transmit traffic and handle all management events between MTP2 on the TDM side and M2UA's MGC (Media Gateway Controller) entity on the IP side.
SIP 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.
Mediant 2000 & TP-1610 & TP-260 Table 12-1: SS7 Parameters (continues on pages 271 to 272) ini File Parameter Name SS7_MTP2_Param_Timer_T5 [T5] SS7_MTP2_Param_Timer_T6 [T6] SS7_MTP2_Param_Timer_T7 [T7] Description Defines the SS7 MTP2 Sending SIB timer. The valid range is 0 to 2400. The default value is 120. Defines the SS7 MTP2 Remote Congestion timer (in msec). The valid range is 0 to 10000. The default value is 6000. Defines the SS7 MTP2 excessive delay of the ack timer (in msec).
SIP User's Manual 12. Special Applications Table 12-2: SIGTRAN Interface Groups (continues on pages 272 to 273) ini File Parameter Name Description Determines the SIGTRAN group behavior bit. The valid range is 0 to 0xFFFFFFFE. The default value is 0. Determines the SIGTRAN group SCTP port. The valid range is 0 to 0xFFFE. The default value is 0Xfffe. Determines the SIGTRAN group Network (ITU, ANSI, CHINA). The valid range is 1 to 3. The default value is 1.
Mediant 2000 & TP-1610 & TP-260 12.2.4.
SIP User's Manual 12.
Mediant 2000 & TP-1610 & TP-260 12.2.5 SS7 MTP2 Tunneling ini File Example For the SS7 MTP2 tunneling ini file example, note the following: The first ini file acts as an MTP2 tunneling central side (M2UA MGC links). There are eight SS7 links - four links of type: MTP2 MGC, and four links of type MTP2. Each pair of links (one MTP2 MGC and one MTP2) defines an MTP2 tunnel. There is one interface that is used for the M2UA MGC <=> M2UA SG (Signaling Gateway) connection.
SIP 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.
Mediant 2000 & TP-1610 & TP-260 Figure 12-6: SS7 MTP2 Tunneling ini File Example - MGC [ \SS7_LINK_TABLE ] [ SS7_SIG_IF_GROUP_TABLE ] FORMAT SS7_SIG_IF_GR_INDEX = SS7_IF_GR_ID,SS7_SIG_SG_MGC, SS7_SIG_LAYER, SS7_SIG_TRAF_MODE, 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,29
SIP User's Manual 12.
Mediant 2000 & TP-1610 & TP-260 Figure 12-7: SS7 MTP2 Tunneling ini File Example - SG SS7_SIG_INT_ID_TABLE 7 = 50, BELFAST12, 4, 4, 0, 0; SS7_SIG_INT_ID_TABLE 8 = 12, AMSTERDAM, 4, 4, 1, 0; SS7_SIG_INT_ID_TABLE 9 = 18, ROTERDAM , 4, 4, 2, 0; SS7_SIG_INT_ID_TABLE 10 = 1, GAUDA , 4, 4, 3, 0; [ \SS7_SIG_INT_ID_TABLE ] 12.3 QSIG Tunneling The gateway supports QSIG tunneling over SIP according to .
SIP User's Manual 13 13. Security Security This section describes the security mechanisms and protocols implemented on the gateway. The following list specifies the available security protocols and their objectives: 13.1 IPSec and IKE protocols are part of the IETF standards for establishing a secured IP connection between two applications. IPSec and IKE are used in conjunction to provide security for control and management protocols but not for media (refer to Section 13.1 below).
Mediant 2000 & TP-1610 & TP-260 13.1.1 IKE IKE is used to obtain the Security Associations (SA) between peers (the gateway and the application it’s trying to contact). The SA contains the encryption keys and profile used by the IPSec to encrypt the IP stream. The IKE table lists the IKE peers with which the gateway performs the IKE negotiation (up to 20 peers are available). The IKE negotiation is separated into two phases: main mode and quick mode.
SIP User's Manual 13. Security IPSec specifications: Transport mode only. Encapsulation Security Payload (ESP) only. Support for Cipher Block Chaining (CBC). Supported IPSec SA encryption algorithms - DES, 3DES, and AES. Hash types for IPSec SA are SHA1 and MD5. 13.1.3 Configuring the IPSec and IKE To enable IPSec and IKE on the gateway set the ini file parameter ‘EnableIPSec’ to 1. 13.1.3.
Mediant 2000 & TP-1610 & TP-260 Table 13-1: IKE Table Configuration Parameters (continues on pages 283 to 284) Parameter Name Description Authentication Method Determines the authentication method for IKE.
SIP User's Manual 13. Security In the example, a single IKE peer is configured. Its pre-shared key is 123456789. Two security proposals are configured: DES/SHA1/786DH and 3DES/SHA1/1024DH. ¾ To configure the IKE table using the Embedded Web Server, take these 6 steps: 1. 2. Access the Embedded Web Server (refer to Section 5.3 on page 58). Open the ‘IKE Table’ screen (Advanced Configuration menu > Security Settings > IKE Table option); the ‘IKE Table’ screen is displayed.
Mediant 2000 & TP-1610 & TP-260 13.1.3.2 IPSec Configuration The parameters described in Table 13-3 below are used to configure the SPD table. A different set of parameters can be configured for each of the 20 available IP destinations. Table 13-3: SPD Table Configuration Parameters (continues on pages 286 to 286) Parameter Name Description Remote IP Address Defines the destination IP address (or a FQDN) the [IPSecPolicyRemoteIPAddres IPSec mechanism is applied to. s] This parameter is mandatory.
SIP User's Manual 13. Security If no IPSec methods are defined (Encryption / Authentication), the default settings (shown in Table 13-4 below) are applied. Table 13-4: Default IKE Second Phase Proposals Encryption Authentication Proposal 0 3DES SHA1 Proposal 1 3DES MD5 Proposal 2 DES SHA1 Proposal 3 DES MD5 ¾ To configure the SPD table using the ini file: SPD table is configured using ini file tables (described in Section 11.5 on page 253).
Mediant 2000 & TP-1610 & TP-260 ¾ To configure the SPD table using the Embedded Web Server, take these 6 steps: 1. 2. Access the Embedded Web Server (refer to Section 5.3 on page 58). Open the ‘IPSec Table’ screen (Advanced Configuration menu > Security Settings > IPSec Table option); the ‘IPSec Table’ screen is displayed. Figure 13-5: IPSec Table Screen In the ‘Policy Index’ drop-down list, select the rule you want to edit (up to 20 rules can be configured). 4.
SIP User's Manual 13. Security 13.1.3.3 IPSec and IKE Configuration Table’s Confidentiality Since the pre-shared key parameter of the IKE table must remain undisclosed, measures are taken by the ini file, Embedded Web Server and SNMP agent to maintain this parameter’s confidentiality. On the Embedded Web Server a list of asterisks is displayed instead of the pre-shared key. On SNMP, the pre-shared key parameter is a write-only parameter and cannot be read.
Mediant 2000 & TP-1610 & TP-260 13.2 SSL/TLS SSL, also known as TLS, is the method used to secure the gateway's SIP Signaling connections, Embedded Web Server and Telnet server. The SSL protocol provides confidentiality, integrity and authenticity between two communicating applications over TCP/IP. Specifications for the SSL/TLS implementation: Supports transports: SSL 2.0, SSL 3.0, TLS 1.0 Supports ciphers: DES, RC4 compatible Authentication: X.509 certificates; CRLs are not supported 13.
SIP User's Manual 13. Security The figure below is an example of a host file: Figure 13-8: Example of a Host File # This is a sample HOSTS file used by Microsoft TCP/IP for Windows. # Location: C:\WINDOWS\SYSTEM32\DRIVERS\ETC\hosts # 127.0.0.1 localhost 10.31.4.47 ACL_280152 13.2.
Mediant 2000 & TP-1610 & TP-260 Figure 13-9: Certificate Signing Request Screen 3. 4. 5. In the 'Subject Name' field, enter the DNS name and click Generate CSR. A textual certificate signing request, that contains the SSL device identifier, is displayed. Copy this text and send it to your security provider; the security provider (also known as Certification Authority or CA) signs this request and send you a server certificate for the device. Save the certificate in a file (e.g., cert.txt).
SIP User's Manual 8. 9. 13. Security Click Browse, navigate to the cert.txt file, and then click Send File. When the operation is completed, save the configuration (Section 5.9.2 on page 124) and restart the gateway; the Embedded Web Server uses the provided certificate. Notes: • • • The certificate replacement process can be repeated when necessary (e.g., the new certificate expires). It is possible to use the IP address of the gateway (e.g., 10.3.3.
Mediant 2000 & TP-1610 & TP-260 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. If both the CA certificate and the client certificate appear in the Trusted Root Certificate file, the user is not prompted for a password (thus providing a single-signon experience - the authentication is performed using the X.509 digital signature).
SIP User's Manual 13.4 13. Security RADIUS Login Authentication Users can enhance the security and capabilities of logging to the gateway’s Web and Telnet embedded servers by using a Remote Authentication Dial-In User Service (RADIUS) to store numerous usernames, passwords and access level attributes (Web only), allowing multiple user management on a centralized platform.
Mediant 2000 & TP-1610 & TP-260 Figure 13-13: Example of a Dictionary File for FreeRADIUS (FreeRADIUS Client Configuration) # # AudioCodes VSA dictionary # VENDOR AudioCodes 5003 ATTRIBUTE ACL-Auth-Level 35 integer AudioCodes VALUE ACL-Auth-Level ACL-Auth-UserLevel 50 VALUE ACL-Auth-Level ACL-Auth-AdminLevel 100 VALUE ACL-Auth-Level ACL-Auth-SecurityAdminLevel 200 3.
SIP User's Manual 7. 8. 13. Security In the field ‘Local RADIUS Password Cache Timeout’, enter a time (in seconds); when this time expires, the username and password verified by the RADIUS server becomes invalid and a username and password must be re-validated with the RADIUS server.
Mediant 2000 & TP-1610 & TP-260 13.5 Internal Firewall The gateway accommodates an internal access list facility, allowing the security administrator to define network traffic filtering rules.
SIP User's Manual 13. Security Figure 13-16 shows an advanced example of an access list definition via ini file: Figure 13-16: Advanced Example of an Access List Definition via ini File [ ACCESSLIST ] FORMAT AccessList_Index = AccessList_Source_IP, AccessList_Net_Mask, AccessList_Start_Port, AccessList_End_Port, AccessList_Protocol, AccessList_Packet_Size, AccessList_Byte_Rate, AccessList_Byte_Burst, AccessList_Allow_Type; AccessList 10 = 10.0.0.0, 255.0.0.
Mediant 2000 & TP-1610 & TP-260 13.6 Network Port Usage The following table lists the default TCP/UDP network port numbers used by the gateway. Where relevant, the table lists the ini file parameters that control the port usage and provide source IP address filtering capabilities. Table 13-5: Default TCP/UDP Network Port Numbers Port Number Peer Port Application Notes 2 2 Debugging interface Always ignored 23 - Telnet Disabled by default (TelnetServerEnable).
SIP User's Manual 13.7 13. Security Recommended Practices To improve network security, the following guidelines are recommended when configuring the gateway: 13.8 Set the password of the primary web user account (refer to Section 5.6.8.1 on page 98) to a unique, hard-to-hack string. Do not use the same password for several devices as a single compromise may lead to others. Keep this password safe at all times and change it frequently. If possible, use a RADIUS server for authentication.
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 302 Document #: LTRT-68805
SIP User's Manual 14 14. Diagnostics Diagnostics Several diagnostic tools are provided, enabling you to identify correct functioning of the gateway, or an error condition with a probable cause and a solution or workaround. 14.1 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 30. Gateway Self-Testing on hardware initialization (refer to Section 14.1 below).
Mediant 2000 & TP-1610 & TP-260 Run-time test (Periodic): Used for monitoring the gateway during run-time. The Periodic Test is performed every hour after startup, even when there is full traffic on the gateway; quality is not degraded. The following hardware components are being tested: • TSA. • PSTN framers (when they are used). • Missing DSP’s. • Conference channels (where they are supported). • If an error is detected, an error message is sent to the Syslog.
SIP User's Manual 14. Diagnostics 14.2.2 Operation The Syslog client, embedded in the gateway, sends error reports/events generated by the gateway unit application to a Syslog server, using IP/UDP protocol. ¾ To activate the Syslog client on the gateway, take these 5 steps: 1. 2. 3. 4. 5. Version 5.0 Set the parameter ‘EnableSyslog’ to 1 (Table 6-1 on page 130). Use the parameter ‘SyslogServerIP’ to define the IP address of the Syslog server you use (Table 6-1 on page 130).
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 306 Document #: LTRT-68805
SIP User's Manual 15 15. SNMP-Based Management SNMP-Based Management Simple Network Management Protocol (SNMP) is a standards-based network control protocol for managing elements in a network. The SNMP Manager (usually implemented by a Network Management System (NMS) or an Element Management System (EMS)) connects to an SNMP Agent (embedded on a remote Network Element (NE)) to perform network element Operation, Administration and Maintenance (OAM).
Mediant 2000 & TP-1610 & TP-260 Set Request: The SNMP standard provides a method of effecting an action associated with a device (via the ‘set’ request) to accomplish activities such as disabling interfaces, disconnecting users, clearing registers, etc. This provides a way of configuring and controlling network devices via SNMP.
SIP User's Manual 15. SNMP-Based Management viewed with a MIB Browser, which is a traditional SNMP management tool incorporated into virtually all Network Management Systems. The act of compiling the MIB allows the manager to know about the special objects supported by the agent and access these objects as part of the standard object set. 15.2 Carrier Grade Alarm System The basic alarm system has been extended to a carrier-grade alarm system.
Mediant 2000 & TP-1610 & TP-260 15.3 Cold Start Trap The gateway's 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: 15.4 The standard coldStart trap - iso(1).org(3).dod(6).internet(1). snmpV2(6). snmpModules(3). snmpMIB(1). snmpMIBObjects(1). snmpTraps(5). coldStart(1) - sent at system initialization.
SIP User's Manual 15. SNMP-Based Management acPMPSTN: for PSTN related monitoring such as channel use, trunk utilization. Note that the acPMTrunkUtilizationTable is not supported. acPMSystem: for general (system related) monitoring. The log trap, acPerformanceMonitoringThresholdCrossing (non-alarm) is sent every time the threshold of a Performance Monitored object is crossed.
Mediant 2000 & TP-1610 & TP-260 RTCP-XR: This MIB (RFC) implements the following partial support: • • The rtcpXrCallQualityTable is fully supported. In the rtcpXrHistoryTable, support of the RCQ objects is provided only with no more than 3 intervals, 15 minutes long each. Supports the rtcpXrVoipThresholdViolation trap.
SIP User's Manual 15. SNMP-Based Management acAlarm: This is AudioCodes' proprietary carrier-grade alarm MIB. It is a simpler implementation of the notificationLogMIB and the IETF suggested alarmMIB (both also supported in all AudioCodes’ devices). The acAlarm MIB has the following groups: • ActiveAlarm: straightforward (single-indexed) table, listing all currently active alarms, together with their bindings (the alarm bindings are defined in acAlarm. acAlarmVarbinds and also in acBoard.acTrap.
Mediant 2000 & TP-1610 & TP-260 15.6 Traps Full proprietary trap definitions and trap Varbinds are found in the acBoard MIB and acAlarm MIB. Table 15-1 lists the supported proprietary traps. For detailed information on these traps, refer to Appendix I on page 383. Note: All traps are sent from the SNMP port (default 161). This is part of the NAT traversal solution.
SIP User's Manual 15. SNMP-Based Management Table 15-1: Proprietary Traps Description (continues on pages 314 to 315) Trap Description acEnhancedBITStatus This trap is used to indicate the status of the Built In Test (BIT). The information in the trap contains board hardware elements being tested and their status. The information is presented in the additional info fields. acBoardEthernetLinkAlarm Sent when an Ethernet link(s) is down.
Mediant 2000 & TP-1610 & TP-260 15.7.1 SNMP Community Names By default, the device uses a single, read-only community string of ‘public’ and a single read-write community string of ‘private’.
SIP User's Manual 15. SNMP-Based Management ¾ To add a read-write community string (v2admin), take these 2 steps: 1. 2. Add a new row to the snmpCommunityTable with CommunityName v2admin. Add a row to the vacmSecurityToGroupTable for SecurityName v2admin, GroupName ReadWriteGroup and SecurityModel snmpv2c. ¾ To delete the read-write community string (v2admin), take these 2 steps: 1. 2. If v2admin is being used as the trap community string, follow the procedure for changing the trap community string.
Mediant 2000 & TP-1610 & TP-260 15.7.2 SNMP v3 USM Users You can define up to 10 User-based Security Model (USM) users (USM users are referred to as “v3 users”). Each v3 user can be associated with an authentication type (none, MD5, or SHA-1) and a privacy type (none, DES, 3DES, or AES).
SIP User's Manual 15.
Mediant 2000 & TP-1610 & TP-260 Note: A row with the same security level (authPriv) must already exist in the usmUserTable (see the usmUserTable for details). ¾ To delete the read-write, authPriv SNMPv3 user (v3admin1), take these 3 steps: 1. 2. 3. If v3admin1 is associated with a trap destination, follow the procedure for associating a different user to that trap destination. (See below.) Delete the vacmSecurityToGroupTable row for SecurityName v3admin1, GroupName ReadWriteGroup1, and SecurityModel usm.
SIP User's Manual 15. SNMP-Based Management ¾ To add the first Trusted Manager, take these 3 steps: 1. 2. Add a row to the snmpTargetAddrTable with these values: • Name=mgr0 • TagList=MGR • Params=v2cparams Add a row to the snmpTargetAddrExtTable table with these values: • 3. Name=mgr0 • snmpTargetAddrTMask=255.255.255.255:0. The agent does not allow creation of a row in this table unless a corresponding row exists in the snmpTargetAddrTable.
Mediant 2000 & TP-1610 & TP-260 15.7.4 SNMP Ports The SNMP Request Port is 161 and the Trap Port is 162. These ports can be changed by setting parameters in the device ini file. The parameter name is: SNMPPort = Valid UDP port number; default = 161 This parameter specifies the port number for SNMP requests and responses. Usually, it should not be specified. Use the default. 15.7.5 Multiple SNMP Trap Destinations An agent can send traps to up to five managers.
SIP User's Manual 15. SNMP-Based Management Figure 15-1: Example of Entries in a Device ini file Regarding SNMP ; SNMP trap destinations ; The board maintains a table of trap destinations containing 5 ;rows. The rows are numbered 0..4. Each block of 4 items below ;apply to a row in the table. ; To configure one of the rows, uncomment all 4 lines in that ;block. Supply an IP address and if necessary, change the port ;number. ; To delete a trap destination, set ISUSED to 0.
Mediant 2000 & TP-1610 & TP-260 15.7.5.3 Configuring Trap Managers via SNMP The standard snmpTargetMIB interface is available for configuring trap managers. Note: The acBoard MIB is planned to become obsolete. The only relevant section in this MIB is the trap sub tree acTrap.
SIP User's Manual 15. SNMP-Based Management ¾ To enable a trap destination, take this step: 15.8 Change TagList on the appropriate row in the snmpTargetAddrTable to ‘AC_TRAP’. SNMP Manager Backward Compatibility With support for the Multi Manager Trapping feature, the older acSNMPManagerIP MIB object, which is synchronized with the first index in the snmpManagers MIB table is also supported. This is translated in two features: 15.9 SET/GET to either of the two MIB objects is identical.
Mediant 2000 & TP-1610 & TP-260 15.10 SNMP NAT Traversal A NAT placed between the gateway and the element manager calls for traversal solutions: Trap source port: all traps are sent out from the SNMP port (default 161). A manager receiving these traps can use the binding information (in the UDP layer) to traverse the NAT back to the device. The trap destination address (port and IP) are as configured in the snmpTargetMIB.
SIP User's Manual 15. SNMP-Based Management 15.11 SNMP Administrative State Control 15.11.1 Node Maintenance Node maintenance for the IPmedia 2000 is provided by an SNMP interface. The acBoardMIB provides two parameters for graceful and forced shutdowns of the IPmedia 2000: acgwAdminState acgwAdminStateLockControl The acgwAdminState is used either to request (set) a shutdown (0), undo shutdown (2), or to view (get) the gateway condition (0 = locked; 1 = shutting down; 2 = unlocked).
Mediant 2000 & TP-1610 & TP-260 15.12 AudioCodes’ Element Management System Using AudioCodes’ Element Management System (EMS) is recommended to Customers requiring large deployments (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.
SIP User's Manual 16 16. Configuration Files Configuration Files This section describes the configuration (dat) files that are load (in addition to the ini file) to the gateway. The configuration files are: Call Progress Tones file (refer to Section 16.1 below). Prerecorded Tones file (refer to Section 16.2on page 332 ). Voice Prompts file (refer to Section 16.3 on page 332). CAS protocol configuration files (refer to Section 16.4 on page 333).
Mediant 2000 & TP-1610 & TP-260 Burst: A single sound followed by silence. Only the ‘First Signal On time’ and ‘First Signal Off time’ should be specified. All other on and off periods must be set to zero. The burst tone is detected after the off time is completed. Users can specify several tones of the same type. These additional tones are used only for tone detection. Generation of a specific tone conforms to the first definition of the specific tone.
SIP User's Manual 16. Configuration Files • Third Signal Off Time [10 msec]: ‘Signal Off’ period (in 10 msec units) for the third cadence ON-OFF cycle. Can be omitted if there isn’t a third cadence. • Forth Signal On Time [10 msec]: ‘Signal On’ period (in 10 msec units) for the fourth cadence ON-OFF cycle. Can be omitted if there isn’t a fourth cadence. • Forth Signal Off Time [10 msec]: ‘Signal Off’ period (in 10 msec units) for the fourth cadence ON-OFF cycle.
Mediant 2000 & TP-1610 & TP-260 16.2 Prerecorded Tones (PRT) File The Call Progress Tones mechanism has several limitations, such as a limited number of predefined tones and a limited number of frequency integrations in one tone. To work around these limitations and provide tone generation capability that is more flexible, the PRT file can be used. If a specific prerecorded tone exists in the PRT file, it takes precedence over the same tone that exists in the CPT file and is played instead of it.
SIP User's Manual 16. Configuration Files ¾ To generate and load the Voice Prompts file, take these 3 steps: 1. 2. 3. 16.4 Prepare one or more voice files using standard utilities. Use the TrunkPack Downloadable Conversion Utility to generate the voiceprompts.dat file from the pre-recorded voice messages (refer to Section G.1.2 on page 371). Load the voiceprompts.dat file to the gateway either by using a TFTP procedure (refer to Section 6.18 on page 201), or via the Embedded Web Server (Section 5.8.
Mediant 2000 & TP-1610 & TP-260 Table 16-1: User Information Items Item Description Maximum Size PBX extension # The relevant PBX extension number 10 Global IP # The relevant IP number 20 Display name A string that represents the PBX extensions for the Caller ID. 30 Username A string that represents the username for SIP registration. 20 Password A string that represents the password for SIP registration.
SIP User's Manual A. Selected Technical Specifications A Selected Technical Specifications A.1 General Specifications The General Specifications (show in Table A-1 below) apply to the Mediant 2000, TP-1610 and TP-260 gateways. For the product-specific specifications, refer to: Mediant 2000 (Section A.2 on page 337). TP-1610 (Section A.3 on page 339). TP-260 (Section A.4 on page 341).
Mediant 2000 & TP-1610 & TP-260 Table A-1: General Selected Technical Specifications (continues on pages 335 to 336) Function Modem Transparency Specification Automatic switching (pass-through) to PCM, ADPCM or NSE bypass mode for modem signals (V.34 or V.90 modem detection) Protocols VoIP Signaling Protocol SIP RFC 3261 Communication Protocols RTP/RTCP packetization. IP stack (UDP, TCP, RTP). Remote Software load (TFTP, HTTP and HTTPS).
SIP User's Manual A.2 A.
Mediant 2000 & TP-1610 & TP-260 Table A-2: Mediant 2000 Selected Technical Specifications (continues on pages 337 to 338) Function Specification Physical AC Power Supply Universal 90 to 260 VAC 1A max, 47-63 Hz Option for a dual redundant power supply. AC Power Consumption 1 or 2 span: 39.7 W 4 spans: 42.1 W (approximated) 8 spans: 45.3 W DC Power Supply (optional) 36 to 72 VDC (nominal 48 VDC), 4A max, floating input DC Power Consumption 1 or 2 span: 28.8 W 4 spans: 32.8 W 8 spans: 36.
SIP User's Manual A.3 A.
Mediant 2000 & TP-1610 & TP-260 Table A-3: TP-1610 Selected Technical Specifications (continues on pages 339 to 340) Function Specification Supply Voltages and Power 480 channels Consumption (typical) 40.7 W, 3 A at 5 V, 7.8 A at 3.3 V 240 channels 24 W, 1.5 A at 5 V, 5 A at 3.3 V 120 channels 18.4 W, 0.9 A at 5 V, 4.2 A at 3.
SIP User's Manual A.4 A. Selected Technical Specifications TP-260 Specifications Table A-4: TP-260 Selected Technical Specifications Function Trunk & Channel Capacity Specification 6 Capacity with E1 1, 2, 4 or 8 E1 spans, 30, 60, 120 or 240 digital channels Capacity with T1 1, 2, 4 or 8 T1 spans, 24, 48, 96 or 192 digital channels Interfaces PCI Universal PCI 33/66 MHz, 32/64-bit, 3.
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 342 Document #: LTRT-68805
SIP User's Manual B B. Supplied SIP Software Kit Supplied SIP Software Kit Table B-1 describes the standard supplied software kit for the Mediant 2000, TP-1610 and TP-260 SIP gateways. The supplied documentation includes this User’s Manual, the Mediant 2000 Fast Track Guide and the Mediant 3000 & Mediant 2000 & TP Series SIP Digital Release Notes. Table B-1: Supplied Software Kit File Name Description Ram.cmp file Mediant_SIP_xxx.
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 344 Document #: LTRT-68805
SIP User's Manual C C. SIP Compliance Tables SIP Compliance Tables The gateway complies with RFC 3261, as shown in the following sections. C.1 SIP Functions Table C-1: SIP Functions Function Supported User Agent Client (UAC) User Agent Server (UAS) Proxy Server Yes Yes Third-party only (Checked with Ubiquity, Delta3, Microsoft, 3Com, BroadSoft, Snom and Cisco Proxies) Third-party Third-party Yes Redirect Server Registrar Server Event Publication Agent (EPA) Event State Compositore (ESC) C.
Mediant 2000 & TP-1610 & TP-260 Table C-3: SIP Headers (continues on pages 345 to 347) Header Field Supported Authorization Call-ID Call-Info Contact Content-Disposition Content-Encoding Content-Length Content-Type Cseq Date Diversion Encryption Expires Fax From History-Info Join Max-Forwards Messages-Waiting MIN-SE Organization P-Asserted-Identity P-Preferred-Identity Priority Proxy- Authenticate Proxy- Authorization Proxy- Require Prack Reason Record- Route Refer-To Referred-By Replaces Require Remote-
SIP User's Manual C. SIP Compliance Tables Table C-3: SIP Headers (continues on pages 345 to 347) Header Field Supported Via Voicemail Warning WWW- Authenticate Yes Yes Yes Yes C.
Mediant 2000 & TP-1610 & TP-260 C.5.1 1xx Response – Information Responses Table C-5: 1xx SIP Responses 1xx Response Supported Comments 100 Trying Yes 180 Ringing Yes 181 Call is being forwarded Queued Yes Session Progress Yes The SIP gateway generates this response upon receiving of Proceeding message from ISDN or immediately after placing a call for CAS signaling. The SIP gateway generates this response for an incoming INVITE message.
SIP User's Manual C.5.4 C. SIP Compliance Tables 4xx Response – Client Failure Responses Table C-8: 4xx SIP Responses (continues on pages 349 to 350) 4xx Response Supported Comments 400 Bad Request Yes The gateway does not generate this response. On reception of this message, before a 200 OK has been received, the gateway responds with an ACK and disconnects the call. 401 Unauthorized Yes Authentication support for Basic and Digest.
Mediant 2000 & TP-1610 & TP-260 Table C-8: 4xx SIP Responses (continues on pages 349 to 350) 4xx Response Supported Comments 420 Bad Extension Yes The gateway does not generate this response. On reception of this message, before a 200OK has been received, the gateway responds with an ACK and disconnects the call. 480 Temporarily Unavailable Yes If the gateway receives a 480 Temporarily Unavailable response, it notifies the User with a Reorder Tone.
SIP User's Manual C.5.6 C. SIP Compliance Tables 6xx Response – Global Responses Table C-10: 6xx SIP Responses 6xx Response 600 Busy Everywhere 603 Decline 604 Does Not Exist Anywhere 606 Not Acceptable Version 5.0 Comments On reception of any of these Responses, the GW releases the call, sending appropriate release cause to PSTN side.
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 352 Document #: LTRT-68805
SIP User's Manual D D. The BootP/TFTP Configuration Utility 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; our BootP/TFTP utility can be installed on Windows™ 98 or Windows™ NT/2000/XP. The BootP/TFTP utility enables remote reset of the device to trigger the initialization procedure (BootP and TFTP).
Mediant 2000 & TP-1610 & TP-260 D.4 D.5 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. Works with Windows™ 98, Windows™ NT, Windows™ 2000 and Windows™ XP.
SIP User's Manual D.7 D. The BootP/TFTP Configuration Utility BootP/TFTP Application User Interface Figure D-1 shows the main application screen for the BootP/TFTP utility. Figure D-1: Main Screen Log Window D.8 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.
Mediant 2000 & TP-1610 & TP-260 Figure D-2: Reset Screen When a gateway resets, it first sends a BootRequest. Therefore, Reset can be used to force a BootP session with a gateway without needing to power cycle the gateway. As with any BootP session, the computer running the BootP Tool must be located on the same subnet as the controlled VoIP gateway. D.
SIP User's Manual D. The BootP/TFTP Configuration Utility Use right-click on a line in the Log Window to open a pop-up window with the following options: Reset: Selecting this option results in a reset command being sent to the client VoIP gateway. The program searches its database for the MAC address indicated in the line. If the client is found in that database, the program adds the client MAC address to the Address Resolution Protocol (ARP) table for the computer.
Mediant 2000 & TP-1610 & TP-260 D.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. When ARP Manipulation is enabled on this screen, the BootP Tool creates an ARP cache entry on your computer when it receives a BootP BootRequest from the VoIP gateway.
SIP User's Manual D. The BootP/TFTP Configuration Utility Timeout: This specifies the number of seconds that the TFTP utility waits before retransmitting TFTP messages. This can be left at the default value of 5 (the more congested your network, the higher the value you should define in these fields). Maximum Retransmissions: This specifies the number of times that the TFTP utility tries to resend messages after timing out.
Mediant 2000 & TP-1610 & TP-260 D.11.1 Adding Clients Adding a client creates an entry in the BootP Tool for a specific gateway. ¾ To add a client to the list without using a template, take these 3 steps: Click on the Add New Client icon ; a client with blank parameters is displayed. Enter values in the fields on the right side of the window, using the guidelines for the fields in Section D.11.5 on page 361. 3.
SIP User's Manual 3. 4. D. The BootP/TFTP Configuration Utility Make the changes required for each parameter. Click Apply to save the changes, or click Apply & Reset to save the changes and send a reset message to that gateway to immediately implement the settings. Note: To use Apply & Reset you must enable ARP Manipulation in the Preferences window. Also, you must have administrator privileges for the computer you are using. D.11.
Mediant 2000 & TP-1610 & TP-260 TFTP Server IP: This field contains the IP address of the TFTP utility that is used for file transfer of software and initialization files to the gateway. When creating a new client, this field is populated with the IP address used by the BootP Tool. If a different TFTP utility is to be used, change the IP address in this field to the IP address used by the other utility.
SIP User's Manual D. The BootP/TFTP Configuration Utility Table D-1: Command Line Switch Descriptions Switch Description -fb -em # Burn ram.cmp in flash (only for cmp files) Use this switch to set Ethernet mode. 0 = 10 Base-T half-duplex 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 9.1 on page 229.
Mediant 2000 & TP-1610 & TP-260 D.12 Managing Client Templates Templates can be used to simplify configuration of clients when most of the parameters are the same. Figure D-5: Templates Screen ¾ To create a new template, take these 4 steps: 1. 2. 3. 4. Click on the Add New Template button . Fill in the default parameter values in the parameter fields. Click Apply to save this new template. Click OK when you are finished adding templates. ¾ To edit an existing template, take these 4 steps: 1. 2. 3. 4.
SIP User's Manual E E. RTP/RTCP Payload Types and Port Allocation 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. E.1 Payload Types Defined in RFC 3551 Table E-1: Packet Types Defined in RFC 3551 Payload Type Description Basic Packet Rate [msec] 0 G.711 µ-Law 10,20 2 G.726-32 10,20 3 GSM-FR 20 4 G.723 (6.
Mediant 2000 & TP-1610 & TP-260 E.3 Default RTP/RTCP/T.38 Port Allocation The following table describes gateway's default RTP/RTCP/T.38 port allocation. Table E-3: Default RTP/RTCP/T.38 Port Allocation Channel Number RTP Port RTCP Port T.
SIP User's Manual F F. RTP Control Protocol Extended Reports (RTCP-XR) RTP Control Protocol Extended Reports (RTCP-XR) RTP Control Protocol Extended Reports (RTCP-XR) is a VoIP management control that defines a set of metrics containing information for assessing VoIP call quality and diagnosing problems. RTCP-XR (RFC 3611) extends the RTCP reports defined in RFC 3550 by providing additional VoIP metrics.
Mediant 2000 & TP-1610 & TP-260 Table F-1: RTCP-XR Published VoIP Metrics (continues on pages 367 to 368) Metric Name Burst Gap Loss Burst Loss Density Burst Duration Gap Loss Density Gap Duration Minimum Gap Threshold Delay Round Trip Delay End System Delay One Way Delay Interarrival Jitter Min Absolute Jitter Signal Signal Level Noise Level Residual Echo Return Noise Quality Estimates Listening Quality R RLQ Est. Algorithm Conversational Quality R RCQ Est. Algorithm External R In Ext. R In Est.
SIP User's Manual G G. Accessory Programs and Tools 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: G.1 TrunkPack Downloadable Conversion Utility (refer to Section G.1 below). PSTN Trace Utility (refer to Section G.2 on page 376).
Mediant 2000 & TP-1610 & TP-260 G.1.1 Converting a CPT ini File to a Binary dat File For detailed information on creating a CPT ini file, refer to Section 16.1 on page 329. ¾ To convert a CPT ini file to a binary dat file, take these 10 steps: 1. 2. Execute the TrunkPack Downloadable Conversion Utility, DConvert.exe (supplied with the software package); the utility’s main screen opens (shown in Figure G-1).
SIP User's Manual G.1.2 G. Accessory Programs and Tools Creating a Loadable Voice Prompts File For detailed information on the Voice Prompts file, refer to Section 16.3 on page 331. ¾ To create a loadable Voice Prompts dat file from your voice recording files, take these 7 steps: 1. 2. Execute the TrunkPack Downloadable Conversion Utility, DConvert.exe (supplied with the software package); the utility’s main screen opens (shown in Figure G-1).
Mediant 2000 & TP-1610 & TP-260 4. 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. Tip 1: Use the Play button to play wav files through your PC speakers. Tip 2: Use the Remove and Remove all buttons to delete files from the list. 5.
SIP User's Manual G. Accessory Programs and Tools Figure G-5: Call Associated Signaling (CAS) Screen 5. 6. 7. Click the button Select File… under the section ‘CAS File’; a Browse window appears. Navigate to the desired location and select the txt file you want to converted; this automatically designates the output file as the same name and path, but with a dat extension, the table’s name is also automatically designated.
Mediant 2000 & TP-1610 & TP-260 G.1.4 Encoding / Decoding an ini File For detailed information on secured ini file, refer to Section 6.1 on page 127. ¾ To encode an ini file, take these 6 steps: 1. 2. Execute the TrunkPack Downloadable Conversion Utility, DConvert.exe (supplied with the software package); the utility’s main screen opens (shown in Figure G-1). Click the Process Encoded/Decoded ini file(s) button; the ‘Encode/Decode ini File(s)’ screen, shown in Figure G-6, opens.
SIP User's Manual G.1.5 G. Accessory Programs and Tools Creating a Loadable Prerecorded Tones File For detailed information on the PRT file, refer to Section 16.2.1 on page 332. ¾ To create a loadable PRT dat file from your raw data files, take these 7 steps: 1. 2. 3. Prepare the prerecorded tones (raw data PCM or L8) files you want to combine into a single dat file using standard recording utilities. Execute the TrunkPack Downloadable Conversion utility, DConvert.
Mediant 2000 & TP-1610 & TP-260 5. For each raw data file, define a Tone Type, a Coder and a Default Duration by completing the following 6 steps: • Double-click or right-click the required file; the ‘File Data’ window (shown in Figure G-4) appears. • From the ‘Type’ drop-down list, select the tone type this raw data file is associated with. • From the ‘Coder’ drop-down list, select the coder that corresponds to the coder this raw data file was originally recorded with.
SIP User's Manual G. Accessory Programs and Tools ¾ To start and collect the PSTN trace via the Web, take these 10 steps: Run the UDP2File utility. Determine the trace file name. Determine the UDP port. Mark the 'PSTN Trace' check box. Click the Run button; the UDP2File utility starts to collect the trace messages. Activate the Web page by entering /TrunkTraces, such as: http://10.8.8.101/TrunkTraces. The user and password is the same for the unit. 7.
Mediant 2000 & TP-1610 & TP-260 Reader's Notes SIP User's Manual 378 Document #: LTRT-68805
SIP User's Manual H H. Release Reason Mapping Release Reason Mapping This appendix describes the available mapping mechanisms of SIP Responses to Q.850 Release Causes and vice versa. Table H-1 and Table H-2 describe the existing mapping of ISDN Release Causes to SIP Responses. To override this hard-coded mapping and flexibly map SIP Responses to ISDN Release Causes use the parameters CauseMapISDN2SIP and CauseMapSIP2ISDN (described in Section 6.
Mediant 2000 & TP-1610 & TP-260 H.2 Fixed Mapping of ISDN Release Reason to SIP Response Table H-1 below describes the mapping of ISDN release reason to SIP response.
SIP User's Manual H.
Mediant 2000 & TP-1610 & TP-260 H.3 Fixed Mapping of SIP Response to ISDN Release Reason Table H-2 below describes the mapping of SIP response to ISDN release reason.
SIP User's Manual I I. SNMP Traps 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 11 varbinds (Variable Binding) (1.3.6.1.4.1.5003.9.10.1.21.1). The source varbind is composed of a string that details the component from which the trap is being sent (forwarded by the hierarchy in which it resides).
Mediant 2000 & TP-1610 & TP-260 Table I-2: acBoardConfigurationError Alarm Trap Alarm: OID: Default Severity Event Type: Probable Cause: Alarm Text: Status Changes: acBoardConfigurationError Condition: Alarm status: value: Condition: Alarm status: Corrective Action: A configuration error was detected critical A run-time specific string describing the configuration error. After configuration error Status stays critical until reboot. A clear trap is not sent.
SIP User's Manual I. SNMP Traps Table I-5: acFeatureKeyError Alarm Trap acFeatureKeyError Alarm: OID: Default Severity Event Type: Probable Cause: Alarm Text: Status Changes: 1.3.6.1.4.1.5003.9.10.1.21.2.0.6 Critical processingErrorAlarm configurationOrCustomizationError (7) Feature key error Support of this alarm is pending Note: Table I-6: acBoardCallResourcesAlarm Alarm Trap acBoardCallResourcesAlarm Alarm: OID: Default Severity Event Type: Probable Cause: Alarm Text: Status Changes: 1.3.6.1.4.1.
Mediant 2000 & TP-1610 & TP-260 Table I-8: acBoardOverloadAlarm Alarm Trap acBoardOverloadAlarm Alarm: OID: Default Severity Event Type: Probable Cause: Alarm Text: Status Changes: 1.3.6.1.4.1.5003.9.10.1.21.2.0.11 Major processingErrorAlarm softwareError (46) Board overload alarm Condition: Alarm Status: Condition: Alarm Status: I.1.2 An overload condition exists in one or more of the system components.
SIP User's Manual I.1.3 I. SNMP Traps Component: EthernetLink#0 The source varbind text for all the alarms under this component is Board#/EthernetLink#0 where n is the slot number. This trap relates to the Ethernet Link Module (the #0 numbering doesn’t apply to the physical Ethernet link). This trap doesn’t apply to TP-260 boards.
Mediant 2000 & TP-1610 & TP-260 I.1.4 Component: SS7#0 The source varbind text for all alarms under this component Board#/SS7#0/SS7Link# where n is the slot number and m is the link number. is Table I-11: acSS7LinkStateChangeAlarm Trap Alarm: OID: Default Severity Event Type: Probable Cause: Alarm Text: Status Changes: acSS7LinkStateChangeAlarm 1.3.6.1.4.1.5003.9.10.1.21.2.0.
SIP User's Manual I. SNMP Traps Table I-12: acSS7LinkCongestionStateChangeAlarm Trap Alarm: OID: Default Severity Event Type: Probable Cause: Alarm Text: Status Changes: acSS7LinkCongestionStateChangeAlarm 1.3.6.1.4.1.5003.9.10.1.21.2.0.22 Major communicationsAlarm Other *** SS7 *** Link %i is %s %s Condition: SS7 link becomes congested (local or remote).
Mediant 2000 & TP-1610 & TP-260 Table I-14: acPerformanceMonitoringThresholdCrossing Log Trap acPerformanceMonitoringThresholdCrossing Trap: OID: Default Severity Event Type: Probable Cause: Trap Text: 1.3.6.1.4.1.5003.9.10.1.21.2.0.
SIP User's Manual I.1.6 I. SNMP Traps Other Traps The following are provided as SNMP traps and are not alarms. Table I-16: coldStart Trap coldStart Trap Name: OID: MIB SNMPv2-MIB Note: This is a trap from the standard SNMP MIB. 1.3.6.1.6.3.1.1.5.1 Table I-17: authenticationFailure Trap Trap Name: OID: MIB authenticationFailure 1.3.6.1.6.3.1.1.5.5 SNMPv2-MIB Table I-18: acBoardEvBoardStarted Trap Trap Name: OID: MIB Severity Event Type: Probable Cause: Alarm Text: acBoardEvBoardStarted 1.3.6.1.4.
Mediant 2000 & TP-1610 & TP-260 I.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.
SIP User's Manual J J. Installation and Configuration of Apache HTTP Server Installation and Configuration of Apache HTTP Server This appendix describes the installation and configuration of Apache’s HTTP server with Perl script environment (required for recording). J.1 Windows 2000/XP Operation Systems Note: For detailed installation information, refer to http://perl.apache.org/docs/2.0/os/win32/config.html. ¾ To configure the Apache HTTP server and mod_perl version 2.
Mediant 2000 & TP-1610 & TP-260 7. Open the Apache2/conf/perl.conf file for editing and add the line “Script PUT /perl/put.cgi” after the last line in the following section (note that if the following section is omitted or different in the file, insert it into the file or change it there accordingly): Alias /perl/ "C:/Apache2/perl/ SetHandler perl-script PerlResponseHandler ModPerl::Registry Options +ExecCGI PerlOptions +ParseHeaders Locate the file put.
SIP User's Manual 4. J. Installation and Configuration of Apache HTTP Server Configure the Apache sever: a. Open etc/httpd/conf/httpd.conf (or a similar file) for editing b. Set the KeepAlive parameter to true c. Set the MaxKeepAliveRequests parameter to 0 (enables an unlimited number of requests during a persistent connection – required for multiple consecutive HTTP POST requests for uploading the file). d. Set MaxClients to 250 e. Change the mod_perl module lines to:
Mediant 2000 & TP-1610 & TP-260 Reader’s Notes SIP User's Manual 396 Document #: LTRT-68805
SIP User's Manual K. Regulatory Information K Regulatory Information K.1 Mediant 2000 Declaration of Conformity 73/23/EEC (including amendments) Application of Council Directives: 89/336/EEC (including amendments) 1999/5/EC Annex-II of the Directive EN55022: 1998 + A1: 2000 + A2: 2003 Standards to which Conformity is Declared: EN55024:1998 + A1: 2001 + A2: 2003 EN61000-3-2: 2000 + A2: 2005 (AC only) EN61000-3-3: 1995 + A1: 2001 (AC only) EN60950-1: 2001 Manufacturer’s Name: AudioCodes Ltd.
Mediant 2000 & TP-1610 & TP-260 Safety Notices 1. Installation and service of this gateway must only be performed by authorized, qualified service personnel. 2. The protective earth terminal on the device must be permanently connected to protective earth. 3. The equipment must be connected by service personnel to a socket-outlet with a protective earthing connection. 4. This equipment should be installed in restricted access locations with maximum allowed temperature 40°C (104°F).
SIP User's Manual K. Regulatory Information FCC Statement This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications.
Mediant 2000 & TP-1610 & TP-260 K.2 TP-1610 Declaration of Conformity 73/23/EEC (including amendments) Application of Council Directives: 89/336/EEC (including amendments) 1999/5/EC Annex-II of the Directive EN55022: 1998 + A1: 2000 + A2: 2003 Standards to which Conformity is Declared: EN55024:1998 + A1: 2001 + A2: 2003 EN60950-1: 2001 Manufacturer’s Name: AudioCodes Ltd. Manufacturer’s Address: 1 Hayarden Street, Airport City, Lod 70151, Israel.
SIP User's Manual K. Regulatory Information Industry Canada Notice This equipment meets the applicable Industry Canada Terminal Equipment technical specifications. This is confirmed by the registration numbers. The abbreviation, IC, before the registration number signifies that registration was performed based on a declaration of conformity indicating that Industry Canada technical specifications were met. It does not imply that Industry Canada approved the equipment.
Mediant 2000 & TP-1610 & TP-260 K.3 TP-260 Declaration of Conformity 73/23/EEC (including amendments) Application of Council Directives: 89/336/EEC (including amendments) 1999/5/EC Annex-II of the Directive EN55022: 1998 + A1: 2000 + A2: 2003 Standards to which Conformity is Declared: EN55024:1998 + A1: 2001 + A2: 2003 EN60950-1: 2001 Manufacturer’s Name: AudioCodes Ltd. Manufacturer’s Address: 1 Hayarden Street, Airport City, Lod 70151, Israel.
SIP User's Manual K. Regulatory Information Industry Canada Notice This equipment meets the applicable Industry Canada Terminal Equipment technical specifications. This is confirmed by the registration numbers. The abbreviation, IC, before the registration number signifies that registration was performed based on a declaration of conformity indicating that Industry Canada technical specifications were met. It does not imply that Industry Canada approved the equipment.
™ Mediant™ Digital Media Gateways & TrunkPack™ Boards SIP Mediant 2000 TP-1610 & TP-260/UNI Boards User’s Manual Version 5.0 www.audiocodes.
