Mediant™ 2000 & TP-1610 SIP User’s Manual Version 4.
Notice This document describes the AudioCodes Mediant™ 2000 SIP (Session Initialization Protocol) gateway and the TP-1610 SIP cPCI 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 SIP User’s Manual Contents Table of Contents 1 Overview.....................................................................................................................13 1.1 1.2 1.3 Available Configurations .................................................................................................................14 SIP Overview ..................................................................................................................................
Mediant 2000 SIP 5.8.3.2 Numbering Plans and Type of Number ...................................................................................... 48 5.8.4 Configuring the Routing Tables...........................................................................................49 5.8.4.1 5.8.4.2 5.8.4.3 5.8.4.4 Tel to IP Routing Table .............................................................................................................. 49 IP to Trunk Group Routing Table ...........................
Mediant 2000 SIP User’s Manual 8.4 8.5 8.6 8.7 8.8 8.9 8.10 8.11 8.12 8.13 Contents Using ISDN NFAS ........................................................................................................................141 8.4.1 NFAS Interface ID .............................................................................................................141 8.4.2 Working with DMS-100 Switches ......................................................................................
Mediant 2000 SIP 11.6.4.2 Configuration via SNMP........................................................................................................... 181 11.7 SNMP Manager Backward Compatibility......................................................................................182 11.8 AudioCodes’ Element Management System ................................................................................182 12 Selected Technical Specifications ........................................................
Mediant 2000 SIP User’s Manual Contents Appendix J SS7 Tunneling........................................................................................... 231 J.1 J.2 J.3 J.4 J.5 J.6 MTP2 Tunneling Technology........................................................................................................232 SS7 Characteristics ......................................................................................................................232 SS7 Parameters ..................................
Mediant 2000 SIP List of Figures Figure 1-1: Typical Mediant 2000 Gateway Application ...................................................................................14 Figure 2-1: Mediant 2000 Front View ...............................................................................................................19 Figure 2-2: Front and Upper View of the TP-1610 cPCI Board........................................................................
Mediant 2000 SIP User’s Manual Contents Figure 8-3: SIP Call Flow Example.................................................................................................................153 Figure 5-2: IP to Trunk Group Routing Table .................................................................................................159 Figure 9-1: Setting the Syslog Server IP Address..........................................................................................
Mediant 2000 SIP List of Tables Table 2-1: Mediant 2000 Front View Component Descriptions........................................................................19 Table 2-2: Chassis LED Indicators ...................................................................................................................20 Table 2-3: Front and Upper View of the TP-1610 cPCI Board Component Descriptions ................................21 Table 2-4: Status LED Indicators...............................................
Mediant 2000 SIP User’s Manual Contents Table K-5: VoiceXML Supported Properties ..................................................................................................260 Table L-1: acBoardFatalError Alarm Trap ......................................................................................................271 Table L-2: acBoardConfigurationError Alarm Trap.........................................................................................
Mediant 2000 SIP Tip: When viewing this manual on CD, Web site or on any other electronic copy, all cross-references are hyperlinked. Click on the page or section numbers (shown in blue) to reach the individual cross-referenced item directly. To return back to the point from where you accessed the cross-reference, press the ALT and ← keys. Note: This User’s Manual describes the Mediant 2000 SIP media gateway and the the TP-1610 SIP board.
Mediant 2000 SIP User’s Manual 1 1. Overview Overview The Mediant 2000 SIP Voice over IP (VoIP) gateway enables voice, fax, and data traffic to be sent over the same IP network. The Mediant 2000 provides excellent voice quality and optimized packet voice streaming over IP networks. The Mediant 2000 uses the award-winning, field-proven Digital Signal Processing (DSP) voice compression technology used in other TrunkPackTM series products.
Mediant 2000 SIP Figure 1-1 below illustrates typical Mediant 2000 gateway applications over VoIP Network. Figure 1-1: Typical Mediant 2000 Gateway Application Telephone PSTN E1/T1 PRI/CAS Mediant 2000 SIP Proxy Router LAN SIP Service Node LAN Router IP Netw ork Mediant 2000 Mediant 2000 LAN LAN Router Router E1/T1 PRI/CAS E1/T1 PRI/CAS PBX - Branch A 1.
Mediant 2000 SIP User’s Manual 1.2 1. Overview • 48 Channels on 2 T1 spans with gateway-1 only • 96 Channels on 4 T1 spans with gateway-1 only • 192 Channels on 8 T1 spans with gateway-1 only • 384 Channels on 16 T1 spans with gateway-1 and gateway-2 SIP Overview SIP is an application-layer control (signaling) protocol used on the Mediant 2000 for creating, modifying, and terminating sessions with one or more participants.
Mediant 2000 SIP 1.3.3 PSTN-to-SIP Interworking The Mediant 2000 gateway performs interworking between ISDN and CAS via E1/T1/J1 digital spans and SIP IETF signaling protocol. 16 E1, T1 or J1 spans are supported (480 channels) in a two modules gateway. The Mediant 2000 gateway supports various ISDN PRI protocols such as EuroISDN, North American NI2, Lucent 4/5ESS, Nortel DMS100, Meridian 1 DMS100, Japan J1, as well as QSIG (basic call). PRI support includes User Termination or Network Termination side.
Mediant 2000 SIP User’s Manual 1. Overview • Works with Proxy or without Proxy, using an internal routing table. • Fallback to internal routing table if Proxy is not responding. • Supports up to four Proxy servers. If the primary Proxy fails, the Mediant 2000 automatically switches to a redundant Proxy. • Supports Proxy server discovery using Domain Name Server (DNS) SRV records. • Proxy and Registrar Authentication (handling 401 and 407 responses) using Basic or Digest methods.
Mediant 2000 SIP Reader’s Notes Mediant 2000 SIP User’s Manual 18 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual 2 2. Mediant 2000 Physical Description Mediant 2000 Physical Description This section provides detailed information on the Mediant 2000 hardware components, the location and functionality of the LEDs, buttons and connectors on the front and rear panels. 2.1 General The Mediant 2000 gateway comprises the following hardware components: • A 19-inch 1U high rack mount chassis (refer to Section 2.2 on page 20). • A single compactPCI™ TP-1610 board (refer to Section 2.
Mediant 2000 SIP 2.2 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.
Mediant 2000 SIP User’s Manual 2. Mediant 2000 Physical Description Figure 2-2: Front and Upper View of the TP-1610 cPCI Board 2 1 7 6 5 4 3 Table 2-3: Front and Upper View of the TP-1610 cPCI Board Component Descriptions Item # Label 1 Component Description Status LEDs 2 ETH Ethernet LEDs 3 Reset button 4 cPCI LEDs 5 cPCI Latch 6 T1 / E1 STATUS T1/E1 Trunk Status LEDs (for each of trunks 1 to 8) 7 T1 / E1 STATUS T1/E1 Trunk Status LEDs (for each of trunks 9 to 16) 2.3.
Mediant 2000 SIP Note 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. Note 2: Do not set components down without protecting them with a static bag. 2.3.1.1 Removing Boards To remove the TP-1610 board from the chassis, take these 3 steps: 1. Unfasten the screws on the plate of the board. 2.
Mediant 2000 SIP User’s Manual 2.3.2 2. Mediant 2000 Physical Description 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 21. Note that there is a choice of front panels according to the number of channels.
Mediant 2000 SIP 2.4 Rear Transition Module The Mediant 2000 RTM includes a PSTN trunks and an Ethernet interfaces. 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 provided with a choice of rear panels (1-span, 2-span, 4-span, 8-span or 16-span).
Mediant 2000 SIP User’s Manual 2. Mediant 2000 Physical Description Figure 2-4: Rear Panel with 8 RJ-48c Connectors for 8 Trunks 2 1 Table 2-9: Rear Panel with 8 RJ-48c Connectors for 8 Trunks Component Descriptions Item # Label 1 ETHERNET 2 TRUNKS 2.5 Component Description 2 Ethernet Ports. 2 RJ-45 network connectors 8 E1/T-1 Spans. 8 RJ-48c trunk connectors Optional CPU Board The Mediant 2000 provides an optional second cPCI slot that can be optionally used for customer’s CPU board.
Mediant 2000 SIP Reader’s Notes Mediant 2000 SIP User’s Manual 26 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual 3 3. Installing the Mediant 2000 Installing the Mediant 2000 This section describes the hardware installation procedures for the Mediant 2000. For information on how to start using the gateway, refer to Section 4 on page 35. For detailed information on the Mediant 2000 connectors, LEDs and buttons, refer to Section 2 on page 19. Caution Electrical Shock The equipment must only be installed or serviced by qualified service personnel.
Mediant 2000 SIP Figure 3-1: 19-inch Rack & Desktop Accessories 3.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.4 on page 30 for cabling the Mediant 2000. 3.3.1 Mounting the Mediant 2000 on a Desktop No brackets are required. Optionally, attach the four (supplied) anti-slide bumpers to the base of the Mediant 2000 and place it on the desktop in the position you require. 3.3.
Mediant 2000 SIP User’s Manual 3. Installing the Mediant 2000 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 SIP 2. 3.4 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. Cabling the Mediant 2000 Refer to Section 2 on page 19 for detailed information on the Mediant 2000 rear panel connectors and LEDs. Note that the Mediant 2000 is available in many configurations, i.e.
Mediant 2000 SIP User’s Manual 3. Installing the Mediant 2000 Figure 3-4: Mediant 2000 Rear Panel Cabling (8 Trunks, DC Power)) 1 2 3 3 1 4 5 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 SIP 3. Repeat steps 1 and 2 for the other Trunk cable but this time connect it to the connector labeled “Trunks 9 16”. The 50-pin male Telco cable connector must be wired according to the pinout in Table 3-3 below, and to mate with the female connector illustrated in Figure 3-5.
Mediant 2000 SIP User’s Manual 3. Installing the Mediant 2000 Figure 3-7: Pinout of RJ-45 Connectors RJ-45 LAN Connector and Pinout 12345678 3.4.3 1 = Tx+ 2 = Tx3 = Rx+ 6 = Rx- 4, 5, 7, 8 not connected Connecting the Power Supply Connect the Mediant 2000 to the power supply using one of the following methods: 3.4.3.
Mediant 2000 SIP Figure 3-8: DC Terminal Block Screw Connector When using a DC terminal block crimp connector, take these 3 steps: 1. Remove the DC adaptor (screw connection type) that is attached to the Mediant 2000 rear panel. 2. 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-9). 3. Insert the terminal block into the DC inlet located on the Mediant 2000.
Mediant 2000 SIP User’s Manual 4 4. Getting Started Getting Started The Mediant 2000 is supplied with application software already resident in its flash memory (with factory default parameters). Section 4.1 below describes how to assign IP addresses to the Mediant 2000, while Section 4.1.2 on page 35 describes how to set up the Mediant 2000 with basic parameters using a standard Web browser (such as Microsoft TM Internet Explorer).
Mediant 2000 SIP correspond with your network IP settings. If your network doesn’t feature a default gateway, enter a dummy value in the ‘Default Gateway IP Address’ field. 5. Click the Reset button and click OK in the prompt; The Mediant 2000 applies the changes and restarts. This takes approximately 3 minutes to complete. When the Mediant 2000 has finished restarting, the Ready and LAN LEDs on the front panel are lit green. Tip: 4.1.
Mediant 2000 SIP User’s Manual 4. Getting Started This option is currently supported on one media gateway module (trunks 1-8) only. To restore networking parameters to their initial state, take these 6 steps: 4.3 1. Disconnect the Mediant 2000 from the power and network cables. 2. Reconnect the power cable; the gateway is powered up. After approximately 45 seconds the ACT LED blinks for about 4 seconds. 3.
Mediant 2000 SIP Enable the DMZ (Demilitarized Zone) configuration on the residential router for the LAN port where the Mediant 2000 gateway is connected. This enables unknown packets to be routed to the DMZ port. 2. Under ‘SIP Parameters’, enter the Mediant 2000 domain name in the field ‘Gateway Name’. If the field is not specified, the Mediant 2000 IP address is used instead (default). 3.
Mediant 2000 SIP User’s Manual 5. Web Management 5 Web Management 5.1 Configuration Concepts Users can utilize the Mediant 2000 in a wide variety of applications, enabled by its parameters and configuration files (e.g., Call Progress Tones (CPT), etc.). The parameters can be configured and configuration files can be loaded using: • A standard Web Browser (described and explained in this section). • A configuration file referred to as the ini file.
Mediant 2000 SIP 5.4 Password Control The Embedded Web Server is protected by a unique username and password combination. The first time a browser request is made, the User is requested to provide his username and password to obtain access.
Mediant 2000 SIP User’s Manual 5.6 5. Web Management Accessing the Embedded Web Server To access the Embedded Web Server, take these 4 steps: 1. Open a standard Web-browsing application such as Microsoft™ Internet Explorer™ (Version 6.0 and higher) or Netscape™ Navigator™ (Version 7.0 and higher). 2. In the Uniform Resource Locator (URL) field, specify the IP address of the Mediant 2000 (e.g., http://10.1.10.10); the Embedded Web Server’s ‘Enter Network Password’ screen appears, shown in Figure 5-1.
Mediant 2000 SIP 5.7 Getting Acquainted with the Web Interface Figure 5-2 shows the general layout of the Web Interface screen. Figure 5-2: Mediant 2000 Web Interface Main Menu Bar MG Module Submenu Bar Title Bar Corporate Logo Main Action Frame Control Protocol The Web Interface screen features the following components: 5.7.1 • Title bar - contains three configurable elements: corporate logo, a background image and the product’s name.
Mediant 2000 SIP User’s Manual 5. Web Management • Advanced Configuration – Use this menu to set the gateway’s advanced configuration parameters (for advanced users only) (refer to Section 5.9 on page 62). • Status & Diagnostics – 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 (refer to Section 5.10 on page 71).
Mediant 2000 SIP 5.8 Protocol Management Use this menu to configure the gateway’s SIP parameters and tables. 5.8.1 Protocol Definition Parameters Use this submenu to configure the following gateway’s specific SIP protocol parameters: 5.8.1.1 • General Parameters • Proxy & Registration Parameters • Coders (refer to Section 5.8.1.
Mediant 2000 SIP User’s Manual 5.8.2 5. Web Management Advanced Parameters Use this submenu to configure the following gateway’s advanced control protocol parameters. 5.8.3 • Disconnect and Answer Supervision • CDR and Debug • Miscellaneous Parameters • Supplementary Services Number Manipulation Tables The VoIP gateway provides four Number Manipulation tables for incoming and outgoing calls.
Mediant 2000 SIP Figure 5-4: Source Phone Number Manipulation Table for Tel IP Calls 2. In the ‘Table Index’ drop-down list, select the range of entries that you want to edit (up to 20 entries can be configured for Source Number Manipulation and 50 entries for Destination Number Manipulation). 3. Configure the Number Manipulation table according to Table 5-1. 4. Click the Submit button to save your changes. 5. To save the changes so they are available after a power fail, refer to Section 5.
Mediant 2000 SIP User’s Manual 5. Web Management Table 5-1: Number Manipulation Parameters Parameter Description Prefix / Suffix to add Prefix - Enter the number / string you want to add to the front of the phone number. For example, if you enter 9 and the phone number is 1234, the new number is 91234. • Suffix - Enter the number / string (in brackets) you want to add to the end of the phone number. For example, if you enter (00) and the phone number is 1234, the new number is 123400.
Mediant 2000 SIP • [2,3,4]xxx# represents four-digit numbers that start with 2, 3 or 4 • 54324 represents any number that starts with 54324 • 54324xx# represents a 7 digit number that starts with 54324 • 123[100-200]# represents all numbers from 123100 to 123200. The VoIP gateway matches the rules starting at the top of the table. For this reason, enter more specific rules above more generic rules.
Mediant 2000 SIP User’s Manual 5.8.4 5. Web Management Configuring the Routing Tables Use this submenu to configure the gateway’s IP Tel and Tel IP routing tables and their associated parameters. 5.8.4.1 Tel to IP Routing Table The Tel to IP Routing Table is used to route incoming Tel calls to IP addresses. This routing table associates a called / calling telephone number’s prefixes with a destination IP address or with an FQDN (Fully Qualified Domain Name).
Mediant 2000 SIP 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. Note that if a domain name in this table is resolved to two IP addresses, the timeout for Invite retransmissions can be reduced by using the parameter ‘Number of RTX Before Hotswap’. Note: If the alternative routing destination is the gateway itself, the call can be configured to be routed back to PSTN.
Mediant 2000 SIP User’s Manual 5. Web Management Table 5-3: Tel to IP Routing Table Parameter Description Any telephone number whose destination number matches the prefix defined in the ‘Destination Phone Prefix’ field and its source number matches the prefix defined in the adjacent ‘Source Phone Prefix‘ field, is sent to the IP address entered in the ‘IP Address’ field.
Mediant 2000 SIP • 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). For information on how to enable this option, refer to Section 5.8.7 on page 60. If a Channel Select Mode for a specific trunk group isn’t specified, then the global ‘Channel Select Mode’ parameter (defined in ‘General Parameters’ screen under ‘Advanced Parameters’) applies.
Mediant 2000 SIP User’s Manual 5. Web Management Table 5-4: IP to Trunk Group Routing Table Parameter Description Any SIP incoming call whose destination number matches the prefix defined in the ‘Destination Phone Prefix’ field and its source number matches the prefix defined in the adjacent ‘Source Phone Prefix‘ field and its source IP address matches the address defined in the ‘Source IP Address’ field, is assigned to the trunk group entered in the field to the right of these fields.
Mediant 2000 SIP 5.8.4.4 Reasons for Alternative Routing The Reasons for Alternative Routing screen includes two tables (Tel IP and IP Tel). Each table enables you to define up to 4 different release reasons. If a call is released as a result of one of these reasons, 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.
Mediant 2000 SIP User’s Manual 5.8.5 5. Web Management Configuring the Profile Definitions Utilizing the Profiles feature, the Mediant 2000 provides high-level adaptation when connected to a variety of equipment (from both Tel and IP sides) and protocols, each of which require a different system behavior.
Mediant 2000 SIP Note 2: If not specified, the ptime gets a default value. Note 3: The ptime specifies the maximum packetization time the gateway can receive. 5. Repeat steps 3 and 4 for the second to fifth coders (optional). 6. Repeat steps 2 to 5 for the second to forth coder groups (optional). 7. Click the Submit button to save your changes. 8. To save the changes so they are available after a power fail, refer to Section 5.12 on page 84. Note: 5.8.5.
Mediant 2000 SIP User’s Manual 5.8.5.3 5. Web Management 3. In the ‘Profile Preference’ drop-down list, select the preference (1-10) of the current Profile. The preference option is used to determine the priority of the Profile. If both IP and Tel profiles apply to the same call, the coders and other common parameters of the preferred Profile are applied to that call. If the Preference of the Tel and IP Profiles is identical, the Tel Profile parameters are applied.
Mediant 2000 SIP 5.8.6 2. In the ‘Profile ID’ drop-down list, select the IP Profile you want to edit (up to four IP Profiles can be configured). 3. In the ‘Profile Preference’ drop-down list, select the preference (1-10) of the current Profile. The preference option is used to determine the priority of the Profile. If both IP and Tel profiles apply to the same call, the coders and other common parameters of the preferred Profile are applied to that call.
Mediant 2000 SIP User’s Manual 5. Web Management Table 5-5: Trunk Group Table Parameter Description Trunk ID The numbers (1-8) in the Trunk ID drop-down list represent the physical trunks on the back of the VoIP gateway. Channels To enable the trunk’s B-channels, you must enter their number in this field. [n-m] represents a range of channels. For example, enter [1-24] to specify the channels from 1 to 24.
Mediant 2000 SIP 5.8.7 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 SIP User’s Manual 5. Web Management Table 5-6: Channel Select Modes Mode Description By phone number Select the gateway port according to the called number (refer to the note below). Cyclic Ascending Select the next available channel in an ascending cycle order. Always select the next higher channel number in the Trunk Group.
Mediant 2000 SIP 5.9 Advanced Configuration Use this menu to set the gateway’s advanced configuration parameters (for advanced users only). 5.9.1 Configuring the Network Settings From the Network Settings page you can define: • IP settings. • NTP settings. • Syslog settings. • SNMP settings. • RTP settings. • Ethernet Ports Information (read-only). To configure the Network Settings parameters, take these 4 steps: 1.
Mediant 2000 SIP User’s Manual 5.9.1.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 6 steps: 1. Access the ‘Network Settings’ screen (Advanced Configuration menu > Network Settings); the ‘Network Settings’ screen is displayed (Figure 5-14). 2.
Mediant 2000 SIP maintenance, and debugging actions become simplified for the network administrator. The NTP client follows a simple process in managing system time; the NTP client requests an NTP update, receives an NTP response, and updates the local system clock based on a configured NTP server within the network. The client requests a time update from a specified NTP server at a specified update interval.
Mediant 2000 SIP User’s Manual 5.9.2 5. Web Management Configuring the Channel Settings The Channels Settings screen enables you to set the VoIP gateway channel parameters, such as Input and Output voice gain, Jitter buffer characteristics, Modem, Fax and DTMF transport modes. These parameters are applied to all Mediant 2000 channels. Note that several Channels Settings parameters can be configured per call using profiles (refer to Section 5.8.5 on page 55).
Mediant 2000 SIP 5.9.3 Configuring the Trunk Settings To configure the Trunk Settings, take these 9 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-7 shows the possible indicators and their descriptions.
Mediant 2000 SIP User’s Manual 5. Web Management Table 5-7: Trunks Status Color Indicator Keys Indicator 3.
Mediant 2000 SIP Click the Close Window button. 7. After modifying the parameters: 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. 8. To save the changes so they are available after a power fail, refer to Section 5.12 on page 84. Note: 9. 5.9.
Mediant 2000 SIP User’s Manual 5.9.5 5. Web Management 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.
Mediant 2000 SIP 5.9.6 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 7 on page 135. To configure the date and time of the Mediant 2000, take these 3 steps: 1.
Mediant 2000 SIP User’s Manual 5.9.7 5. Web Management 7. To save the loaded auxiliary files so they are available after a power fail, refer to Section 5.12 on page 84. 8. To reset the Mediant 2000, refer to Section 5.12 on page 84. Changing the Mediant 2000 Username and Password To prevent unauthorized access to the Mediant 2000, it is recommended that you change the username and password (both are case-sensitive) that are used to access the Web Interface.
Mediant 2000 SIP Note: The information in columns ‘Quality Status’ and ‘Quality Info.’ (per IP address) is reset if two minutes elapse without a call to that destination. To view the IP connectivity information, take these 2 steps: 1. Set ‘AltRoutingTel2IPEnable’ to 1 or 2. 2. Open the ‘IP Connectivity’ screen (Status & Diagnostics menu > Gateway Statistics submenu > IP Connectivity); the ‘IP Connectivity’ screen is displayed (Figure 5-22).
Mediant 2000 SIP User’s Manual 5. Web Management Table 5-8: IP Connectivity Parameters Column Name Description Quality Info. Displays QoS information: delay and packet loss, calculated according to previous calls. Note 1: This field is applicable only if the parameter ‘AltRoutingTel2IPMode’ is set to 2 or 3. Note 2: This field is reset if no QoS information is received for 2 minutes. Can be one of the following: • DNS Disable • DNS Resolved • DNS Unresolved DNS Status 5.10.1.
Mediant 2000 SIP Table 5-9: Call Counters Description (continues on pages 73 to 74) Counter Description This counter indicates the number of established calls.
Mediant 2000 SIP User’s Manual 5. Web Management 5.10.2 Monitoring the Mediant 2000 Trunks & Channels The Trunk & Channel Status screen provides real time monitoring on the current status of the Mediant 2000 trunks & channels. To monitor the status of the trunks and B-channels take this step: • Open the ‘Trunk & Channel Status’ screen (Status & Diagnostics menu > Channel Status); the ‘Trunk & Channel Status’ screen is displayed.
Mediant 2000 SIP 2. Click the submenu links to check/view a specific channel’s parameter settings. Figure 5-26: Channel Status Details Screen 5.10.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 9.2 on page 165.
Mediant 2000 SIP User’s Manual 5. Web Management 3. Select the messages, copy them and paste them into a text editor such as Notepad. Send this txt file to our Technical Support for diagnosis and troubleshooting. 4. To clear the screen of messages, click on the submenu Message Log; the screen is cleared and new messages begin appearing. Tip: Do not keep the ‘Message Log’ screen minimized for a prolonged period as a prolonged session may cause the Mediant 2000 to overload.
Mediant 2000 SIP 5.11 Software Update Menu The ‘Software Update’ menu enables users to upgrade the Mediant 2000 software by loading a new cmp file along with the ini and a suite of auxiliary files, or to update the existing auxiliary files. The ‘Software Update’ menu comprises two submenus: • Software Update Wizard (refer to Section 5.11.1 below). • Auxiliary Files (refer to Section 5.11.2 on page 82).
Mediant 2000 SIP User’s Manual Note: 3. 5. Web Management At this point, the process can be canceled with no consequence to the Mediant 2000 (click the Cancel button). If you continue the process (by clicking the Start Software Upgrade button, the process must be followed through and completed with a Mediant 2000 reset at the end. If you click the Cancel button in any of the subsequent screens, the Mediant 2000 is automatically reset with the configuration that was previously burned in flash memory.
Mediant 2000 SIP Click Cancel; the Mediant 2000 resets utilizing the cmp, ini and all other configuration files that were previously stored in flash memory. Note that these are NOT the files you loaded in the previous Wizard steps. Click Back; the ‘Load a cmp File’ screen is reverted to; refer to Figure 5-30. Click Next; the ‘Load an ini File’ screen opens; refer to Figure 5-32. Loading a new ini file or any other auxiliary file listed in the Wizard is optional.
Mediant 2000 SIP User’s Manual 5. Web Management Figure 5-33: Load a CPT File Screen 7. Follow the same procedure you followed when loading the ini file (refer to Step 6). The same procedure applies to the ‘Load a VP file’ (not applicable to the Mediant 2000 gateway) screen and ‘Load a coefficient file’ screen. 8. In the ‘FINISH’ screen (refer to Figure 5-34), the Next button is disabled. Complete the upgrade process by clicking Reset or Cancel.
Mediant 2000 SIP Figure 5-35: ‘End Process’ Screen 9. Click the End Process button; the ‘Quick Setup’ screen appears and the full Web application is reactivated. 5.11.2 Auxiliary Files The ‘Auxiliary Files’ screen enables you to load to the gateway the following files: CAS, Call Progress Tones, Voice Prompts and Prerecorded Tones (PRT). For detailed information on these files, refer to Section 7 on page 135. For information on deleting these files from the Mediant 2000, refer to Section 5.10.
Mediant 2000 SIP User’s Manual 5. Web Management Figure 5-36: Auxiliary Files Screen 2. Click the Browse button that is in the field for the type of file you want to load. 3. Navigate to the folder that contains the file you want to load. 4. Click the file and click the Open button; the name and path of the file appear in the field beside the Browse button. 5. Click the Send File button that is next to the field that contains the name of the file you want to load.
Mediant 2000 SIP 5.12 Save Configuration The Save Configuration screen enables users to save the current parameter configuration and the loaded auxiliary files to the non-volatile memory so they are available after a power fail. Parameters that are only saved to the volatile memory revert to their previous settings after hardware reset. Note that when performing a software reset (i.e., via Web or SNMP) you can choose to save the changes to the non-volatile memory.
Mediant 2000 SIP User’s Manual 5. Web Management 5.13 Resetting the Mediant 2000 The Reset screen enables you to remotely reset the gateway. Before reset you can choose to save the gateway configuration to flash memory. To reset the Mediant 2000, take these 3 steps: 1. Click the Reset button on the main menu bar; the Reset screen is displayed. Figure 5-38: Reset Screen 2. Select one of the following options: Burn - (default) the current configuration is burned to flash prior to reset.
Mediant 2000 SIP Reader’s Notes Mediant 2000 SIP User’s Manual 86 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual 6 6. ini File Configuration of the Mediant 2000 ini File Configuration of the Mediant 2000 As an alternative to configuring the VoIP gateway using the Web Interface (refer to Section 5 on page 39), 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 B on page 189) or via any standard TFTP server. It can also be loaded through the Web Interface (refer to Section 5.9.
Mediant 2000 SIP 6.3 The ini File Content The ini file contains the following SIP gateway information: 6.4 • Basic, Logging, Web and RADIUS parameters shown in Table 6-1 on page 90. • SNMP parameters shown in Table 6-2 on page 98. • SIP Configuration parameters shown in Table 6-3 on page 100. • ISDN and CAS Interworking-Related Parameters shown in Table 6-4 on page 111. • Number Manipulation and Routing parameters shown in Table 6-5 on page 115.
Mediant 2000 SIP User’s Manual 6.5 6. ini File Configuration of the Mediant 2000 The ini File Example Figure 6-2 shows an example of an ini file for the VoIP gateway. Figure 6-2: SIP ini File Example PCMLawSelect = 1 ProtocolType = 1 TerminationSide = 0 FramingMethod = 0 LineCode = 2 TDMBusClockSource = 4 ClockMaster = 0 ;Channel Params DJBufferMinDelay = 75 RTPRedundancyDepth = 1 IsProxyUsed = 1 ProxyIP = 192.168.122.
Mediant 2000 SIP 6.6 Basic, Logging, Web and RADIUS Parameters Note: In Table 6-1, parameters in brackets are the format in the Embedded Web * Server .
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-1: Basic, Logging, Web and RADIUS Parameters (continues on pages 90 to 97) 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 SIP Table 6-1: Basic, Logging, Web and RADIUS Parameters (continues on pages 90 to 97) ini File Field Name * Web Parameter Name BaseUDPport [RTP Base UDP Port] Valid Range and Description Lower boundary of UDP port used for RTP, RTCP (Real-Time Control Protocol) (RTP port + 1) and T.38 (RTP port + 2). The upper boundary is the Base UDP Port + 10 * (number of gateway’s channels). The range of possible UDP ports is 4000 to 64000. The default base UDP port is 6000.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-1: Basic, Logging, Web and RADIUS Parameters (continues on pages 90 to 97) ini File Field Name * Web Parameter Name GwDebugLevel [Debug Level] Valid Range and Description Defines the Syslog logging level (usually set to 5 if debug traces are needed).
Mediant 2000 SIP Table 6-1: Basic, Logging, Web and RADIUS Parameters (continues on pages 90 to 97) ini File Field Name * Web Parameter Name RAILowThreshold Valid Range and Description Low Threshold (in percentage) that defines the gateway‘s busy endpoints. The range is 0 to 100. The default value is 90%. When the percentage of the gateway’s busy endpoints falls below the value defined in Low Threshold, the gateway sends an SNMP ‘acBoardCallResourcesAlarm’ Alarm Trap with a ‘cleared’ Alarm Status.
Mediant 2000 SIP User’s Manual 6.
Mediant 2000 SIP Table 6-1: Basic, Logging, Web and RADIUS Parameters (continues on pages 90 to 97) ini File Field Name * Web Parameter Name Valid Range and Description RADIUSAuthPort [RADIUS Authentication Port] Port number of Authentication and Authorization server. The default value is 1645. RADIUSAccServerIP [RADIUS Accounting Server IP Address] IP address of accounting server. RADIUSAccPort [RADIUS Accounting Port] Port number of Radius accounting server. The default value is 1646.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-1: Basic, Logging, Web and RADIUS Parameters (continues on pages 90 to 97) ini File Field Name * Web Parameter Name Valid Range and Description BootPDelay The interval between the device’s startup and the first BootP/DHCP request that is issued by the device. 1 = 1 second (default). 2 = 3 second. 3 = 6 second. 4 = 30 second. 5 = 60 second. Note: This parameter only takes effect from the next reset of the device.
Mediant 2000 SIP 6.7 SNMP Parameters Note: In Table 6-2, parameters in brackets are the format in the Embedded Web * Server . Table 6-2: SNMP Parameter (continues on pages 98 to 99) ini File Field Name * Web Parameter Name Valid Range and Description DisableSNMP [Enable SNMP] 0 = SNMP is enabled (default). 1 = SNMP is disabled and no traps are sent. SNMPPort The device’s local UDP port used for SNMP Get/Set commands. The range is 100 to 3999. The default port is 161.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-2: SNMP Parameter (continues on pages 98 to 99) ini File Field Name * Web Parameter Name Valid Range and Description SetCommunityString Note: Obsolete parameter, use SNMPReadWriteCommunityString_x instead. Version 4.4 SNMP community string (up to 19 chars). Default community string for read “public”, for set & get “private”.
Mediant 2000 SIP 6.8 SIP Configuration Parameters Note: In Table 6-3, parameters in brackets are the format in the Embedded Web * Server . Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110) ini File Field Name * Web Parameter Name Valid Range and Description ControlIPDiffServ [Signaling DiffServ] Defines the value of the 'DiffServ' field in the IP header for SIP messages. The valid range is 0 to 63. The default value is 0.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110) ini File Field Name * Web Parameter Name EnableProxySRVQuery [Enable Proxy SRV Queries] Valid Range and Description Enables the use of DNS Service Record (SRV) queries to discover Proxy servers. 0 = Disabled (default). 1 = Enabled. If enabled and the Proxy IP address parameter contains a domain name without port definition (e.g., ProxyIP = domain.
Mediant 2000 SIP Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110) ini File Field Name * Web Parameter Name ProxyRedundancyMode [Redundancy Mode] Valid Range and Description 0 = Parking mode: gateway continues working with the last active Proxy until the next failure. (default) 1 = Homing mode: gateway always tries to work with the primary Proxy server (switches back to the primary Proxy whenever it is available).
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110) 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 SIP Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110) ini File Field Name * Web Parameter Name CoderName [Coders] Valid Range and Description CoderName = Coder,ptime (can appear up to 5 times) The following coder names can be selected: g711Alaw64k – G.711 A-law. g711Ulaw64k – G.711 µ-law. g7231 – G.723.1 6.3 kbps (default). g7231r53 – G.723 5.3 kbps. g726 – G.726 ADPCM 32 kbps (Payload Type = 2). g729 – G.729A. NetCoder6_4 – NetCoder 6.4 kbps. NetCoder7_2 – NetCoder 7.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110) ini File Field Name * Web Parameter Name Valid Range and Description AMRSendRate Determines the selected rate for the AMR coder. This parameter is relevant only if AMR is included in the coder list (‘CoderName’). 0 = AMR 4.75 kbps. 1 = AMR 5.15 kbps. 2 = AMR 5.90 kbps. 3 = AMR 6.70 kbps. 4 = AMR 7.40 kbps. 5 = AMR 7.95 kbps. 6 = AMR 10.2 kbps. 7 = AMR 12.
Mediant 2000 SIP Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110) ini File Field Name * Web Parameter Name Valid Range and Description CngDetectorMode [CNG Detector Mode] 0 = Don’t detect CNG (default) 2 = Detect CNG on caller side and start fax session (if IsFaxUsed=1) Usually T.38 fax session starts when the “preamble” signal is detected by the answering side.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110) ini File Field Name * Web Parameter Name Valid Range and Description XferPrefix [Transfer Prefix] Defined string that is added, as a prefix, to the transferred called number, when Refer/3xx message is received. Note 1: The number manipulation rules apply to the user part of the Refer-TO/Contact URL before it is sent in the Invite message.
Mediant 2000 SIP Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110) ini File Field Name * Web Parameter Name OutOfBandDTMFFormat [Out-of-Band DTMF Format] Valid Range and Description The exact method to send out-of-band DTMF digits 1 = INFO format (Nortel) 2 = INFO format (Cisco) - (default) 3 = NOTIFY format Note 1: To use out-of-band DTMF, set “IsDTMFUsed=1”.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110) ini File Field Name * Web Parameter Name Valid Range and Description Profile Parameters CoderName_ID [Coder Group Settings] Coder list for Profiles (up to five coders in each group). The CoderName_ID parameter (ID from 1 to 4) provides groups of coders that can be associated with IP or Tel profiles. You can select the following coders: g711Alaw64k – G.
Mediant 2000 SIP Table 6-3: SIP Configuration Parameters (continues on pages 100 to 110) ini File Field Name * Web Parameter Name IPProfile_ID [IP Profile Settings] Valid Range and Description IPProfile_ = ,,,,, ,,,, Preference = (1-10) The preference option is used to determine the priority of the Profile.
Mediant 2000 SIP User’s Manual 6.9 6. ini File Configuration of the Mediant 2000 ISDN and CAS Interworking-Related Parameters Note: In Table 6-4, parameters in brackets are the format in the Embedded Web * Server . Table 6-4: ISDN and CAS Interworking-Related Parameters (continues on pages 111 to 114) ini File Field Name * Web Parameter Name EnableTDMoverIP [Enable TDM Tunneling] Valid Range and Description 0 = Disabled (default). 1 = TDM Tunneling is enabled.
Mediant 2000 SIP Table 6-4: ISDN and CAS Interworking-Related Parameters (continues on pages 111 to 114) ini File Field Name * Web Parameter Name PlayRBTone2IP [Play Ringback Tone to IP] Valid Range and Description 0 = Ringback tone isn’t played (default). 1 = Ringback tone is played (to IP) after SIP 183 session progress response is sent.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-4: ISDN and CAS Interworking-Related Parameters (continues on pages 111 to 114) ini File Field Name * Web Parameter Name Valid Range and Description PSTNAlertTimeout [PSTN Alert Timeout] 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.
Mediant 2000 SIP Table 6-4: ISDN and CAS Interworking-Related Parameters (continues on pages 111 to 114) ini File Field Name * Web Parameter Name Valid Range and Description CASTransportType [CAS Transport Type] 0 = Disable CAS relay (default). 1 = Enable CAS relay mode using RFC 2833. The CAS relay mode can be used with the TDM tunneling feature to enable tunneling over IP for both voice and CAS signaling bearers. XChannelHeader 0 = x-channel header is not used (default).
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 6.10 Number Manipulation and Routing Parameters Note: In Table 6-5, parameters in brackets are the format in the Embedded Web * Server . Table 6-5: Number Manipulation and Routing Parameters (continues on pages 115 to 121) ini File Field Name * Web Parameter Name TrunkGroup_x [Trunk Group Table] Valid Range and Description TrunkGroup_x = T/a-b,c,d x = Trunk group ID (1 to 99). T = Physical trunk number (0 to 7).
Mediant 2000 SIP Table 6-5: Number Manipulation and Routing Parameters (continues on pages 115 to 121) 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). 1 = Cyclic Ascending - Select the next available channel in an ascending cycle order.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-5: Number Manipulation and Routing Parameters (continues on pages 115 to 121) ini File Field Name * Web Parameter Name Valid Range and Description UseSourceNumberAsDisplay Name [Use Source Number as Display Name] 0 = Interworks the Tel calling name to SIP Display Name (default). 1 = Set Display Name to Calling Number if not configured.
Mediant 2000 SIP Table 6-5: Number Manipulation and Routing Parameters (continues on pages 115 to 121) ini File Field Name * Web Parameter Name Valid Range and Description RouteModeTel2IP [Tel to IP routing Mode] 0 = Route calls before number manipulation (default) 1 = Route calls after number manipulation Defines order between routing incoming calls to IP, using routing table, and manipulation of destination number Not applicable if Outbound Proxy is used.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-5: Number Manipulation and Routing Parameters (continues on pages 115 to 121) ini File Field Name * Web Parameter Name SourceNumberMapTel2IP [Source Phone Number Manipulation Table for Tel IP calls] Valid Range and Description SourceNumberMapTel2IP = a,b,c,d,e,f,g,h a = Source number prefix b = Number of stripped digits from the left, or (if in brackets are used) from right. A combination of both options is allowed.
Mediant 2000 SIP Table 6-5: Number Manipulation and Routing Parameters (continues on pages 115 to 121) ini File Field Name * Web Parameter Name Valid Range and Description For ETSI ISDN variant, the following Number Plan and Type combinations (Plan/Type) are supported in the Destination and Source Manipulation tables: 0,0 = Unknown, Unknown 9,0 = Private, Unknown 9,1 = Private, Level 2 Regional 9,2 = Private, Level 1 Regional 9,3 = Private, PISN Specific 9,4 = Private, Level 0 Regional (local) 1,0 = Publ
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-5: Number Manipulation and Routing Parameters (continues on pages 115 to 121) ini File Field Name * Web Parameter Name FilterCalls2IP [Filter Calls To IP] Valid Range and Description 0 = Disabled (default) 1 = Enabled If the filter calls to IP feature is enabled, then when a Proxy is used, the gateway first checks the Tel IP routing table before making a call through the Proxy.
Mediant 2000 SIP 6.11 E1/T1 Configuration Parameters Note: In Table 6-6, parameters in brackets are the format in the Embedded Web * Server . Table 6-6: E1/T1/J1 Configuration Parameters (continues on pages 122 to 127) ini File Field Name * Web Parameter Name Valid Range and Description PCMLawSelect [PCM Law Select] 1 = A-law 3 = µ-Law Usually A-Law is used for E1 spans and µ-Law for T1 and J1 spans. FramingMethod [Framing Method] Selects the framing method to be used for E1/T1 spans.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-6: E1/T1/J1 Configuration Parameters (continues on pages 122 to 127) ini File Field Name * Web Parameter Name TerminationSide [ISDN Termination Side] Valid Range and Description Selects the ISDN termination side. Applicable only to ISDN protocols.
Mediant 2000 SIP Table 6-6: E1/T1/J1 Configuration Parameters (continues on pages 122 to 127) ini File Field Name * Web Parameter Name ISDNNFASInterfaceID_x [NFAS Interface ID] Valid Range and Description Defines a different Interface ID for each T1 trunk. The valid range is 0 to 100. The default interface ID equals to the trunk’s ID (0 to 7). ’x’ identifies the trunk ID (0-7) Note: To set the NFAS interface ID, configure: ISDNIBehavior_x to include ‘512’ feature, per each T1 trunk.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-6: E1/T1/J1 Configuration Parameters (continues on pages 122 to 127) ini File Field Name * Web Parameter Name ISDNRxOverlap_x [Enable Receiving of Overlap Dialing] Valid Range and Description Enable / disable Rx ISDN overlap per trunk ID (x = 0 to 7). 0 = Disabled (default). 1 = Enabled. Note 1: If enabled, the Mediant 2000 receives ISDN called number that is sent in the "Overlap" mode.
Mediant 2000 SIP Table 6-6: E1/T1/J1 Configuration Parameters (continues on pages 122 to 127) 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.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-6: E1/T1/J1 Configuration Parameters (continues on pages 122 to 127) ini File Field Name * Web Parameter Name Valid Range and Description ISDNGeneralCCBehavior [General Call Control Behavior] 16 = The gateway clears down the call if it receives a Notify message specifying ‘User-Suspended’. A Notify (User-Suspended) message is used by some networks (e.g.
Mediant 2000 SIP 6.12 Channel Parameters The Channel Parameters define the DTMF, fax and modem transfer modes. Refer to Appendix D on page 203 for a detailed description of Fax and Modem transfer modes; refer to Section 8.2 on page 139 for detailed description on DTMF transport modes. Note that the Default Channel Parameters are applied to all Mediant 2000 channels. Note: In Table 6-7, parameters in brackets are the format in the Embedded Web * Server .
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-7: Channel Parameters (continues on pages 128 to 131) ini File Field Name * Web Parameter Name CNGDetectorMode [CNG Detector Mode] Valid Range and Description 0 = Disable (default). 1 = Event Only (N/A). 2 = Relay. T.38 fax relay session is initiated by the originating fax if ‘IsFaxUsed = 1’. Note that using this mode isn’t recommended.
Mediant 2000 SIP Table 6-7: Channel Parameters (continues on pages 128 to 131) ini File Field Name * Web Parameter Name Valid Range and Description V34ModemTransportType [V.34 Modem Transport Type] V.34 Modem Transport Type that the gateway uses. You can select: 0 = Transparent 2 = Modem Bypass (default). Note: This option applies to V.34 and V.90 modems. InputGain [Input Gain] PCM input gain control in dB. This parameter sets the level for the received (PSTN IP) signal.
Mediant 2000 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 Table 6-7: Channel Parameters (continues on pages 128 to 131) ini File Field Name * Web Parameter Name Valid Range and Description RFC2833PayloadType [RFC 2833 Payload Type] The RFC 2833 DTMF relay dynamic payload type. Range: 96 to 99, 106 to 127; Default = 96 The 100, 102 to 105 range is allocated for proprietary usage. Cisco is using payload type 101 for RFC 2833.
Mediant 2000 SIP 6.12.1 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 SIP User’s Manual 6. ini File Configuration of the Mediant 2000 6.13 Configuration Files Parameters The configuration files (Call Progress Tones, PRT, Voice Prompts and CAS) can be loaded to the Mediant 2000 via the Embedded Web Server (refer to Section 5.11.2 on page 82), or via TFTP session. To load the configuration files via TFTP, take these 3 steps: 1. In the ini file, define the files to be loaded to the device.
Mediant 2000 SIP Reader’s Notes Mediant 2000 SIP User’s Manual 134 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual 7 7. 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 7.1 below). • Prerecorded Tones file (refer to Section 7.2 on page 137). • Voice Prompts file (refer to Section 7.3 on page 137). • CAS protocol configuration files (refer to Section 7.4 on page 138).
Mediant 2000 SIP • [CALL PROGRESS TONE #X] – containing the Xth tone definition (starting from 1 and not exceeding the number of Call Progress Tones defined in the first section) using the following keys: Tone Type – Call Progress Tone type Figure 7-1: Call Progress Tone Types 1. Dial Tone 2. Ringback Tone 3. Busy Tone 7. Reorder Tone 17.Call Waiting Ringback Tone 23.
Mediant 2000 SIP User’s Manual 7.2 7. Configuration Files 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.
Mediant 2000 SIP When the list of recorded files is converted to a single voiceprompts.dat file, every Voice Prompt is tagged with an ID number, starting with “1”. This ID is used later by the Mediant 2000 to start playing the correct announcement. Up to 1000 Voice Prompts can be used. Note: The Voice Prompt ID is used in the VXML file to specify the message that is to be played. AudioCodes provides a professionally recorded English (U.S.) Voice Prompts file.
Mediant 2000 SIP User’s Manual 8. Gateway Capabilities Description 8 Gateway Capabilities Description 8.1 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: 10453@212.179.22.229 Seq: 1 REGISTER Expires: 3600 Contact: sip:GWRegistrationName@212.179.22.
Mediant 2000 SIP 8.3 ISDN Overlap Dialing Overlap dialing is a dialing scheme used by several ISDN variants to send and / or receive called number digits one right after the other (or several at a time). As opposed to the enbloc dialing scheme in which a complete number is sent.
Mediant 2000 SIP User’s Manual 8.4 8. Gateway Capabilities Description 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. The ISDN Non-Facility Associated Signaling (NFAS) feature enables use of a single D-channel to control multiple PRI interfaces.
Mediant 2000 SIP To define an explicit Interface ID for a T1 trunk (that is different from the default), use the following parameters: • ISDNBehavior_x = 512 (x = 0 to 7 identifying the Mediant 2000 physical trunk) • ISDNNFASInterfaceID_x = ID (x = 0 to 255) Note 1: Usually the Interface Identifier is included in the Q.931 Setup/Channel Identification IE only on T1 trunks that doesn’t contain the D-channel.
Mediant 2000 SIP User’s Manual 8.5 8. Gateway Capabilities Description Configuring the DTMF Transport Types You can control the way DTMF digits are transported over the IP network to the remote endpoint. The following five modes are supported: 1. Using INFO message according to the Nortel IETF draft: In this mode DTMF digits are carried to the remote side within INFO messages.
Mediant 2000 SIP 5. Sending DTMF digits (in RTP packets) as part of the audio stream (DTMF Relay is disabled): Note that this method is normally used with G.711 coders; with other Low Bit Rate (LBR) coders the quality of the DTMF digits is reduced.
Mediant 2000 SIP User’s Manual 8. Gateway Capabilities Description Table 8-3: Summary of DTMF Configuration Parameters (continues on pages 144 to 145) ini File Field Name [Web Name] RxDTMFOption Valid Range and Description Defines the supported Receive DTMF negotiation method. 0 = Don’t declare RFC 2833 Telephony-event parameter in SDP 1 = n/a 2 = n/a 3 = Declare RFC 2833 “Telephony-event” parameter in SDP (default) The gateway is designed to always be receptive to RFC 2833 DTMF relay packets.
Mediant 2000 SIP 8.6 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 Mediant 2000 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.
Mediant 2000 SIP User’s Manual 8.6.4 8. Gateway Capabilities Description Relevant Parameters The following parameters (described in Table 6-5) are used to configure the Alternative Routing mechanism: 8.
Mediant 2000 SIP In the transfer scenario there are three parties: Party A - transferring, Party B – transferred, Party C – transferred to. • A Calls B. • B answers. • A presses the hookflash and puts B on-hold (party B hears a hold tone) • A dials C. • 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.
Mediant 2000 SIP User’s Manual 8.8 8. Gateway Capabilities Description TDM Tunneling The Mediant 2000 TDM Tunneling feature allows you to tunnel groups of digital trunk spans or timeslots (B-channels) over the IP network.
Mediant 2000 SIP Figure 8-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.
Mediant 2000 SIP User’s Manual 8.9 8. Gateway Capabilities Description Call Detail Report The Call Detail Report (CDR) contains vital statistic information on calls made by the gateway. CDRs are generated at the end and (optionally) at the beginning of each call (determined by the parameter ‘CDRReportLevel’). The destination IP address for CDR logs is determined by the parameter ‘CDRSyslogServerIP’. The following CDR fields are supported: Table 8-4: Supported CDR Fields Version 4.
Mediant 2000 SIP 8.10 Trunk to Trunk Routing Example This example describes two Mediant 2000 gateways, each interface with the PSTN through four E1 spans. Gateway "A" is configured to route all incoming Tel IP calls to gateway "B". Gateway "B" 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 SIP User’s Manual 8. Gateway Capabilities Description 8.11 SIP Call Flow Example The Call Flow, shown in Figure 8-3, describes SIP messages exchanged between Mediant 2000 gateway and an MP-108 gateway during a simple call. MP-108 with phone number “8000”, calls Mediant 2000 with phone number “1000”: Figure 8-3: SIP Call Flow Example Mediant 2000 10.8.201.10 MP-108 10.8.201.108 INVITE F1 Trying F2 Ringing F3 200 OK F4 Ack F5 BYE F6 200 OK F7 F1 10.8.201.108 ==> 10.8.201.
Mediant 2000 SIP 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:
Mediant 2000 SIP User’s Manual 8. Gateway Capabilities Description 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.10. Voice path is established. F6 10.8.201.108 ==> 10.8.201.10 BYE BYE sip:1000@10.8.201.10;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.201.108;branch=z9hG4bKacRKCVBud From: ;tag=1c5354 To: ;tag=1c7345 Call-ID: 534366556655skKw-8000--1000@10.8.201.
Mediant 2000 SIP 8.12 SIP Authentication Example Mediant 2000 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.
Mediant 2000 SIP User’s Manual 8. Gateway Capabilities Description Using SIP protocol “sip” Proxy IP from ini file “10.2.2.222” 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”.
Mediant 2000 SIP 8.13 Nortel IMS Specific Features and Configuration 8.13.
Mediant 2000 SIP User’s Manual 8. Gateway Capabilities Description For the SIP2PRI gateway to be able to apply the routing rules on the combined string, the prefix (domain name and trunk group) must previously be defined in the IP to Trunk Group Routing table either using the Embedded Web Server (refer to screen below) or via the ini file: Figure 8-4: IP to Trunk Group Routing Table Via the ini file: PSTNPrefix = nortelnetworks.
Mediant 2000 SIP Note: Usually each E1/T1 span is configured as a separate trunk group. Different Domain names, according to the originated trunk group (or E1/T1 spans), can be determined via the Tel to IP Routing table.
Mediant 2000 SIP User’s Manual 2. 8. Gateway Capabilities Description Use the number manipulation table (exemplified below) to assign NPI/TON values according to the number’s prefix: NumberMapIP2TEL= nortelnetworks.com/TrunkGroup3,30,$$,$$,1,2 In the above example, all numbers starting with the ‘nortelnetworks.com/TrunkGroup3’ string, are modified; the first 30 characters in this prefix string (domain and trunk group names) are erased, and the NPI/TON are set to 1/2 respectively.
Mediant 2000 SIP 8.13.2 SIP2CAS (Call Pilot) Gateway To enable SIP2CAS gateway specific features, take these 2 steps: 1. Add the following parameters to the ini file: ApplicationProfile=1 IsProxyUsed = 1 SendInviteToProxy = 1 ProxyIP = EnableHold = 1 EnableTransfer = 1 EnableForward = 1 EnableNortelHeader = 1 ProtocolType = 2 IsDTMFUsed = 1 OutOfBandDTMFFormat = 1 DTMFTransportType = 0 TimeForReorderTone = 10 PlayRBToneonXfer = 1 2. Load the specific Ground Start CAS .
Mediant 2000 SIP User’s Manual 8. Gateway Capabilities Description • If the call transfer fails, the gateway either plays a busy tone (if the destination client to whom the call is transferred is busy) or it plays a reorder tone (for all other reasons). The tone is played for 10 seconds (TimeForReorderTone=10) towards the CallPilot. Usually, the CallPilot detects these Call Progress Tones and either disconnects the call or unholds it using double hook-flash signaling.
Mediant 2000 SIP Reader’s Notes Mediant 2000 SIP User’s Manual 164 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual 9 9. Diagnostics Diagnostics Several diagnostic tools are provided, enabling you to identify correct functioning of the Mediant 2000, or an error condition with a probable cause and a solution or workaround. 9.1 • Front panel indicator LEDs on the Mediant 2000. The location and functionality of the front panel LEDs is shown in Section 2.3.2 on page 23. • Mediant 2000 Self-Testing on hardware initialization (refer to Section 9.1 below).
Mediant 2000 SIP 9.2.1 Syslog Servers Users can use the provided Syslog server (ACSyslog08.exe) or other third-party Syslog servers. Examples of Syslog servers available as shareware on the Internet: • Kiwi Enterprises: http://www.kiwisyslog.com/ • The US CMS Server: http://uscms.fnal.gov/hanlon/uscms_server/ • TriAction Software: http://www.triaction.nl/Products/SyslogDaemon.asp • Netal SL4NT 2.1 Syslog Daemon: http://www.netal.
Mediant 2000 SIP User’s Manual 10 10. BootP/DHCP Support BootP/DHCP Support 10.1 Startup Process The startup process (illustrated in Figure 10-1 on page 168) 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 SIP Figure 10-1: Mediant 2000 Startup Process Reset from the Web Interface or SNMP Physical Reset BootP x times No Response BootP Response DHCP x times No Response DHCP Response Update network parameters from BootP/DHCP reply BootP/DHCP reply contains firmware file name? No Yes Download firmware via TFTP BootP/DHCP reply contains ini file name? BootP/DHCP reply contains ini file name? No Preconfigured firmware URL? Yes Yes Yes Download firmware via TFTP No Device reset No
Mediant 2000 SIP User’s Manual 10. BootP/DHCP Support 10.2 DHCP Support 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 SIP server address). These network parameters have a "time limit". After the time limit expires, the gateway must "renew" its lease from the DHCP server.
Mediant 2000 SIP • 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. When using the Software Upgrade wizard, available through the Web Interface (refer to Section 5.11.1 on page 78), the auxiliary files are saved as well. Note: To save the cmp file to non-volatile memory, use the -fb command line switches.
Mediant 2000 SIP User’s Manual 11 11. SNMP-Based Management SNMP-Based Management Simple Network Management Protocol (SNMP) is a standard-based network control protocol used to manage elements in a network. The SNMP Manager (usually implemented by a Network Manager (NM) or an Element Manager (EM)) connects to an SNMP Agent (embedded on a remote Network Element (NE)) to perform network element Operation, Administration and Maintenance (OAM).
Mediant 2000 SIP • Trap Message - The SNMP standard furnishes a mechanism by which devices can ‘reach out’ to a Network Manager on their own (via a ‘trap’ message) to notify or alert the manager of a problem with the device. This typically requires each device on the network to be configured to issue SNMP traps to one or more network devices that are awaiting these traps.
Mediant 2000 SIP User’s Manual 11. SNMP-Based Management 11.2 Carrier Grade Alarm System The basic alarm system has been extended to a carrier-grade alarm system. A carrier-grade alarm system provides a reliable alarm reporting mechanism that takes into account EMS outages, network outages, and transport mechanism such as SNMP over UDP.
Mediant 2000 SIP 11.4 Third-Party Performance Monitoring Measurements Performance measurements are available for a third-party performance monitoring system through an SNMP interface. These measurements can be polled at scheduled intervals by an external poller or utility in a media server or other off-device system. The device provides two types of performance measurements: 1. Gauges: Gauges represent the current state of activities on the device.
Mediant 2000 SIP User’s Manual Note: 11. SNMP-Based Management The acBoard MIB is still supported but is being replaced by five newer proprietary MIBs. The acBoard MIB has the following groups: boardConfiguration boardInformation channelConfiguration channelStatus reset acTrap As noted above, five new MIBs cover the device’s general parameters. Each contains a Configuration subtree for configuring related parameters. In some, there also are Status and Action subtrees. The 5 MIBs are: 1.
Mediant 2000 SIP acAlarmVarbinds and also in acBoard.acTrap. acBoardTrapDefinitions. oid_1_3_6_1_4_1_5003_9_10_1_21_2_0). The table size can be altered via notificationLogMIB.notificationLogMIBObjects.nlmConfig.nlmConfigGlobalEntryLimit or notificationLogMIB.notificationLogMIBObjects.nlmConfig.nlmConfigLogTable.nlm ConfigLogEntry.nlmConfigLogEntryLimit. The table size can be any value between 50 to 1000 and is 500 by default.
Mediant 2000 SIP User’s Manual 11. SNMP-Based Management 11.6 SNMP Interface Details This section describes details of the SNMP interface that is required when developing an Element Manager (EM) for any of the TrunkPack-VoP Series products, or to manage a device with a MIB browser. Currently, both SNMP and ini file commands and downloads are not encrypted. For ini file encoding, refer to Section 6.1 on page 87. 11.6.
Mediant 2000 SIP To change the only read-write community string from v2admin to v2mgr, take these 4 steps: 1. Follow the procedure above to add a read-write community string to a row for v2mgr. 2. Set up the EM so that subsequent ‘set’ requests use the new community string, v2mgr. 3. If v2admin is being used as the trap community string, follow the procedure to change the trap community string (see below). 4. Follow the procedure above to delete a read-write community name in the row for v2admin.
Mediant 2000 SIP User’s Manual 11. SNMP-Based Management 1. Add a row to the snmpTargetAddrTable with these values: Name=mgr0, TagList=MGR, Params=v2cparams. 2. Add a row to the tgtAddressMaskTable table with these values: Name=mgr0, tgtAddressMask=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. 3. Set the value of the TransportLabel field on each non-TrapGroup row in the srCommunityTable to MGR.
Mediant 2000 SIP 11.6.4 Multiple SNMP Trap Destinations An agent can now send traps to up to five managers. For each manager, set the following parameters defined in the snmpManagersTable in the acBoardMIB: • snmpTrapManagerSending • snmpManagerIsUsed • snmpManagerTrapPort • snmpManagerIP When snmpManagerIsUsed is set to zero (not used), the other three parameters are set to zero. • snmpManagerIsUsed (Default = Disable(0)) The allowed values are 0 (disable or no) and 1 (enable or yes).
Mediant 2000 SIP User’s Manual 11. SNMP-Based Management Figure 11-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 SIP To disable a trap destination: • Change TagList on the appropriate row in the snmpTargetAddrTable to the empty string. To enable a trap destination: • Change TagList on the appropriate row in the snmpTargetAddrTable to ‘AC_TRAP’. 11.7 SNMP Manager Backward Compatibility With support for the Multi Manager Trapping feature, the older acSNMPManagerIP MIB object, synchronized with the first index in the snmpManagers MIB table, is also supported.
Mediant 2000 SIP User’s Manual 12 12. Selected Technical Specifications Selected Technical Specifications Table 12-1: Mediant 2000 Selected Technical Specifications (continues on pages 183 to 185) Function Trunk & Channel Capacity Specification 1 Capacity with E1 1, 2, 4, 8 or 16 E1 spans, 30, 60, 120, 240 or 480 digital channels Capacity with T1 1, 2, 4, 8 or 16 T1 spans, 24, 48, 96, 192 or 384 digital channels Voice & Tone Characteristics Voice Compression G.711 PCM at 64 kbps µ-law/A-law G.
Mediant 2000 SIP Table 12-1: Mediant 2000 Selected Technical Specifications (continues on pages 183 to 185) Function Specification Fax Transparency Automatic fax bypass (pass-through) to G.711, ADPCM or NSE bypass mode Modem Transparency 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).
Mediant 2000 SIP User’s Manual 12. Selected Technical Specifications Table 12-1: Mediant 2000 Selected Technical Specifications (continues on pages 183 to 185) Function Specification Environmental (AC) Operation Temp: Storage: Humidity: 0° to 40° C / 32° to 104° F -40° to 70° C / -40° to 158° F 10 to 90% non-condensing Hot Swap cPCI cards are full hot swap supported Power supplies are redundant but not hot swappable Enclosure Dimensions 445 x 44 x 300 mm; 17.5 x 1.75 x 12 inch.
Mediant 2000 SIP Reader's Notes Mediant 2000 SIP User’s Manual 186 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual A. Mediant 2000 SIP Software Kit Appendix A Mediant 2000 SIP Software Kit Table A-1 describes the standard supplied software kit for Mediant 2000 SIP gateways. The supplied documentation includes this User’s Manual, the Mediant 2000 Fast Track and the Mediant 2000 & TP-1610 SIP Release Notes. Table A-1: Mediant 2000 SIP Supplied Software Kit File Name Description Ram.cmp file Mediant_SIP_xxx.cmp Image file containing the software for the Mediant 2000 gateway.
Mediant 2000 SIP Reader’s Notes Mediant 2000 SIP User’s Manual 188 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual B. The BootP/TFTP Configuration Utility Appendix B The BootP/TFTP Configuration Utility The BootP/TFTP utility enables you to easily configure and provision our boards and media gateways. Similar to third-party BootP/TFTP utilities (which are also supported) but with added functionality; our BootP/TFTP utility can be installed on Windows™ 98 or Windows™ NT/2000/XP.
Mediant 2000 SIP B.4 B.5 • Protection against entering faulty information. • Remote reset. • Unicast BootP response. • User-initiated BootP respond, for remote provisioning over WAN. • Filtered display of BootP requests. • Location of other BootP utilities that contain the same MAC entity. • Common log window for both BootP and TFTP sessions. • Works with Windows™ 98, Windows™ NT, Windows™ 2000 and Windows™ XP.
Mediant 2000 SIP User’s Manual B.7 B. The BootP/TFTP Configuration Utility BootP/TFTP Application User Interface Figure B-1 shows the main application screen for the BootP/TFTP utility. Figure B-1: Main Screen Log Window B.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 SIP 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. B.9 Log Window The log window (refer to Figure B-1 on the previous page) records all BootP request and BootP reply transactions, as well as TFTP transactions.
Mediant 2000 SIP User’s Manual B. The BootP/TFTP Configuration Utility B.10 Setting the Preferences The Preferences window, Figure B-3, is used to configure the BootP Tool parameters. Figure B-3: Preferences Screen B.10.1 BootP Preferences ARP is a common acronym for Address Resolution Protocol, and is the method used by all Internet devices to determine the link layer address, such as the Ethernet MAC address, in order to route Datagrams to devices that are on the same subnet.
Mediant 2000 SIP • ARP Type: The type of entry made into the ARP cache on the computer, once ARP Manipulation is enabled, can be either Dynamic or Static. Dynamic entries expire after a period of time, keeping the cache clean so that stale entries do not consume computer resources. The Dynamic setting is the default setting and the setting most often used. Static entries do not expire.
Mediant 2000 SIP User’s Manual B. The BootP/TFTP Configuration Utility B.11 Configuring the BootP Clients The Clients window, shown in Figure B-4 below, is used to set up the parameters for each specific VoIP gateway. Figure B-4: Client Configuration Screen B.11.1 Adding Clients Adding a client creates an entry in the BootP Tool for a specific gateway. To add a client to the list without using a template, take these 3 steps: 1.
Mediant 2000 SIP To add a client to the list using a template, take these 5 steps: 1. Click on the Add New Client Icon; a client with blank parameters is displayed. 2. In the field Template, located on the right side of the Client Configuration Window, click on the down arrow to the right of the entry field and select the template that you want to use. 3. The values provided by the template are automatically entered into the parameter fields on the right side of the Client Configuration Window.
Mediant 2000 SIP User’s Manual B. The BootP/TFTP Configuration Utility B.11.5 Setting Client Parameters Client parameters are listed on the right side of the Client Configuration Window. • Client MAC: The Client MAC is used by BootP to identify the VoIP gateway. The MAC address for the VoIP gateway is printed on a label located on the VoIP gateway hardware. Enter the Ethernet MAC address for the VoIP gateway in this field.
Mediant 2000 SIP • Call Agent: This field specifies the IP address of the MGCP Call Agent that is controlling the gateway. This field can be ignored for all other control/signaling protocols. B.11.6 Using Command Line Switches You can add command line switches in the field Boot File. To use a Command Line Switch, take these 4 steps: 1. In the field Boot File, leave the file name defined in the field as it is (e.g., ramxxx.cmp). 2. Place your cursor after cmp 3. Press the space bar 4.
Mediant 2000 SIP User’s Manual B. The BootP/TFTP Configuration Utility B.12 Managing Client Templates Templates can be used to simplify configuration of clients when most of the parameters are the same. Figure B-5: Templates Screen To create a new template, take these 4 steps: 1. Click on the Add New Template button 2. Fill in the default parameter values in the parameter fields. 3. Click Apply to save this new template. 4. Click OK when you are finished adding templates.
Mediant 2000 SIP Reader’s Notes Mediant 2000 SIP User’s Manual 200 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual C. RTP/RTCP Payload Types and Port Allocation Appendix C RTP/RTCP Payload Types and Port Allocation RTP Payload Types are defined in RFC 1889 and RFC 1890. We have added new payload types to enable advanced use of other coder types. These types are reportedly not used by other applications. Note: C.1 Refer to the Mediant 2000 & TP-1620 SIP Release Notes for the supported coders.
Mediant 2000 SIP Payload Type Description Basic Packet Rate [msec] 53 54 55 56 96 102 103 104 105 NetCoder 8.0 kbps NetCoder 8.8 kbps NetCoder 9.6 kbps Transparent PCM DTMF relay per RFC 2833 Fax Bypass Modem Bypass RFC 2198 (Redundancy) NSE Bypass 20 20 20 20 C.3 20 20 Same as channel’s voice coder. Default RTP/RTCP/T.38 Port Allocation The following table describes Mediant 2000 gateway default RTP/RTCP/T.38 Port Allocation. Table C-3: Default RTP/RTCP/T.
Mediant 2000 SIP User’s Manual D. Fax and Modem Transport Modes Appendix D Fax and Modem Transport Modes D.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).
Mediant 2000 SIP D.1.3 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.38) while V.
Mediant 2000 SIP User’s Manual E. Mediant 2000 Clock Settings Appendix E Mediant 2000 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. a. To use the internal gateway clock source configure the following parameters: • TDMBusClockSource = 1 • ClockMaster = 1 (for all gateway trunks) b.
Mediant 2000 SIP Reader's Notes Mediant 2000 SIP User’s Manual 206 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual F. Customizing the Mediant 2000 Web Interface Appendix F Customizing the Mediant 2000 Web Interface Customers incorporating the Mediant 2000 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 F-1; a customized title bar is shown in Figure F-3).
Mediant 2000 SIP 2. 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. 3. Click Image Load to Device; the Image Download screen is displayed (shown in Figure F-3). Figure F-3: Image Download Screen 4. 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.
Mediant 2000 SIP User’s Manual F. Customizing the Mediant 2000 Web Interface Table F-1: Customizable Logo ini File Parameters Parameter Description LogoFileName 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. LogoWidth Width (in pixels) of the logo image. Note: The optimal setting depends on the resolution settings.
Mediant 2000 SIP 6. To save the image to flash memory so it is available after a power fail, refer to Section 5.12 on page 84. 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.
Mediant 2000 SIP User’s Manual F.4 F. Customizing the Mediant 2000 Web Interface Modifying ini File Parameters via the Web AdminPage To modify ini file parameters via the AdminPage, take these 6 steps: 1. Access the Mediant 2000 Embedded Web Server (refer to Section 5.6 on page 41). 2. 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. 3.
Mediant 2000 SIP Reader’s Notes Mediant 2000 SIP User’s Manual 212 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual G. Accessory Programs and Tools Appendix G 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.1.4 on page 218).
Mediant 2000 SIP 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 7.1 on page 135. To convert a CPT ini file to a binary dat file, take these 10 steps: 1. Execute the TrunkPack Downloadable Conversion Utility, DConvert240.exe (supplied with the software package); the utility’s main screen opens (shown in Figure G-1). 2.
Mediant 2000 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 7.2 on page 137. To create a loadable Voice Prompts dat file from your voice recording files, take these 7 steps: 1. Execute the TrunkPack Downloadable Conversion Utility, DConvert240.exe (supplied with the software package); the utility’s main screen opens (shown in Figure G-1). 2.
Mediant 2000 SIP 4. 5. 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.
Mediant 2000 SIP User’s Manual G.1.3 G. Accessory Programs and Tools Encoding / Decoding an ini File For detailed information on secured ini file, refer to Section 6.1 on page 87. To encode an ini file, take these 6 steps: 1. Execute the TrunkPack Downloadable Conversion Utility, DConvert240.exe (supplied with the software package); the utility’s main screen opens (shown in Figure G-1). 2.
Mediant 2000 SIP G.1.4 Creating a Loadable Prerecorded Tones File For detailed information on the PRT file, refer to Section 7.2 on page 137. To create a loadable PRT dat file from your raw data files, take these 7 steps: 1. Prepare the prerecorded tones (raw data PCM or L8) files you want to combine into a single dat file using standard recording utilities. 2. Execute the TrunkPack Downloadable Conversion utility, DConvert240.
Mediant 2000 SIP User’s Manual G. Accessory Programs and Tools Click the Add File(s) button; the ‘Select Files’ screen opens. Select the required Prerecorded Tone files and press the Add>> button. Close the ‘Select Files’ screen. 5. For each raw data file, define a Tone Type, a Coder and a Default Duration by completing the following steps: Double-click or right-click the required file; the ‘File Data’ window (shown in Figure G-4) appears.
Mediant 2000 SIP G.2 PSTN Trace Utility These utilities are designed to convert PSTN trace binary files to textual form. The binary PSTN trace files are generated when the User sets the PSTN interface to trace mode. G.2.1 Operation Generating textual trace/audit file for CAS protocols To generate a readable text file out of the binary trace file when using CAS protocols, rename the PSTN trace binary file to CASTrace0.dat and copy it to the same directory in which the translation utility CAS_Trace.
Mediant 2000 SIP User’s Manual G. Accessory Programs and Tools Figure H-8: Trunk Traces Figure H-9: UDP2File Utility Version 4.
Mediant 2000 SIP Reader’s Notes Mediant 2000 SIP User’s Manual 222 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual H. Software Upgrade Key Appendix H Software Upgrade Key H.1 About the Software Upgrade Key Mediant 2000 gateways are supplied with a Software Upgrade Key already pre-configured for each of its TrunkPack Modules (TPM). Users can later upgrade their Mediant 2000 features, capabilities and quantity of available resources by specifying what upgrades they require, and purchasing a new key to match their specification.
Mediant 2000 SIP H.3.1 Loading the Software Upgrade Key Using the Embedded Web Server To load a Software Upgrade Key using the Web Server, take these 5 steps: 1. Access the devices Embedded Web Server (refer to Section 5.5 on page 40). 2. Click the Software Update button. 3. Click the Software Upgrade Key tab; the Software Upgrade Key screen is displayed (shown in Figure H-1). 4.
Mediant 2000 SIP User’s Manual H. Software Upgrade Key Figure H-2: Example of a Software Upgrade Key File Containing Multiple S/N Lines H.3.2 Loading the Software Upgrade Key Using BootP/TFTP To load the Software Upgrade Key file using BootP/TFTP, take these 5 steps: H.4 1. Place the file in the same location you’ve saved the device’s cmp file. 2.
Mediant 2000 SIP Reader’s Notes Mediant 2000 SIP User’s Manual 226 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual Appendix I I. Release Reason Mapping Release Reason Mapping Table I-1 below describes the mapping of ISDN release reason to SIP response. Table I-2 on page 229 describes the mapping of SIP response to ISDN release reason.
Mediant 2000 SIP ISDN Release Reason SIP Response Description Description 66 Channel type not implemented 480* Temporarily unavailable 69 Requested facility not implemented 503* Service unavailable 70 Only restricted digital information bearer capability is available 503* Service unavailable 79 Service or option not implemented 501 Not implemented 81 Invalid call reference value 502* Bad gateway 82 Identified channel does not exist 502* Bad gateway 83 Suspended call exists, but
Mediant 2000 SIP User’s Manual I.
Mediant 2000 SIP Reader’s Notes Mediant 2000 SIP User’s Manual 230 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual J. SS7 Tunneling Appendix J 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 SIP J.1 MTP2 Tunneling Technology The SS7 tunneling technology is based on a pairing of remote and central gateways, as shown in Figure J-3. 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 Controler) entity on the IP side.
Mediant 2000 SIP User’s Manual J.3 J. SS7 Tunneling SS7 Parameters The parameters in Table J-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. Table J-1: SS7 Parameters (continues on pages 233 to 234) ini File Parameter Name Description SS7_MTP2_Param_AERM_TIE Defines the SS7 alignment emergency error rate threshold. The valid range is 0 to 10.
Mediant 2000 SIP Table J-1: SS7 Parameters (continues on pages 233 to 234) ini File Parameter Name Description SS7_MTP2_Param_Timer_T6 Defines the SS7 MTP2 Remote Congestion timer (in msec). The valid range is 0 to 10000. The default value is 6000. SS7_MTP2_Param_Timer_T7 Defines the SS7 MTP2 excessive delay of the ack timer (in msec). The valid range is 0 to 5000. The default value is 2000. J.4 SS7 Table Parameters J.4.
Mediant 2000 SIP User’s Manual J. SS7 Tunneling Table J-2: SIGTRAN Interface Groups (continues on pages 234 to 235) ini File Parameter Name Description SS7_LOCAL_SCTP_PORT Determines the SIGTRAN group SCTP port. The valid range is 0 to 0xFFFE. The default value is 0Xfffe. SS7_SIG_NETWORK Determines the SIGTRAN group Network (ITU, ANSI, CHINA). The valid range is 1 to 3. The default value is 1. SS7_DEST_SCTP_PORT Determines the SIGTRAN group destination SCTP port. The valid range is 0 to 0xFFFE.
Mediant 2000 SIP J.4.3 SS7 Signaling Link Table J-4: SS7 Signaling Link (continues on pages 236 to 237) ini File Parameter Name Description SS7_LINK_INDEX Determines the index field for a line. The valid range is 0 to 7. The default value is 0. SS7_LINK_ROWSTATUS Determines the RowStatus field for a line. The valid range is acPARAMSET_ROWSTATUS_DOESNOTEXIST to acPARAMSET_ROWSTATUS_DESTROY. The default value is acPARAMSET_ROWSTATUS_DOESNOTEXIST.
Mediant 2000 SIP User’s Manual J. SS7 Tunneling Table J-4: SS7 Signaling Link (continues on pages 236 to 237) ini File Parameter Name Description SS7_LINK_GROUP_ID Determines the group ID (M3UA) of signaling link. The valid range is 0 to 0xFFFF. The default value is 0. ATM_SAAL_LINK_PROFILE_NUM Determines the ATM SAAL Link profile number The valid range is 0 to (MAX_SAAL_PROFILES-1). The default value is 0.
Mediant 2000 SIP • There are 8 SS7 links - 4 links of type: MTP2 MGC, and 4 links of type MTP2. Each pair of links (1 MTP2 MGC and 1 MTP2) defines an MTP2 tunnel. • There is 1 interface that is used for the M2UA MGC <=> M2UA SG (Signaling Gateway) connection. • There are 4 interface IDs defined: 1 per link (M2UA MGC side). • This file is intended for ITU link variant (E1 trunks). To load the example SS7 MTP2 tunneling ini files to Mediant 2000 gateways, take these 3 steps: 1.
Mediant 2000 SIP User’s Manual J. SS7 Tunneling Figure J-4: SS7 MTP2 Tunneling ini File Example - MGC 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 SIP Figure J-4: SS7 MTP2 Tunneling ini File Example - MGC SS7_SIG_IF_GROUP_TABLE 4 = 4, 77, 4, 1, 2000, 2000, 30000, 1, 0, 2904, 1,2904,168.100.0.
Mediant 2000 SIP User’s Manual J.
Mediant 2000 SIP Table J-5: Table of Parameter Values Example - Remote Management Connections Index Fields: 1. Connection Number Connection Number User Name User Password Time Connected (msec) Permissions 0 Admin Yellow9 0 All 1 Gillian Red5 1266656 Read Only 2 David Orange6 0 Read Write Table J-6: Table of Parameter Values Example - Port-to-Port Connections Index Fields: 1. Source Ports 2. Destination IP 3.
Mediant 2000 SIP User’s Manual J.6.3 J. SS7 Tunneling Tables of Parameter Value Rules in the ini File Structure The ini file allows you to add/modify parameters in tables. When using tables, Read-Only parameters are not loaded, since they cause an error when trying to download the loaded file. Therefore read-only parameters should not be included in tables in the ini file.
Mediant 2000 SIP • The order of the Data fields in the Format line is not significant (unlike the Index-fields). Field values in Data lines are interpreted according to the order specified in the Format line. • The sign '$$' in the Data line means that the user wants the pre-defined default value assigned to the field for the given line. • The order of Data lines is insignificant. • Data lines must match the Format line, i.e.
Mediant 2000 SIP User’s Manual K. RADIUS Billing and VXML Calling Card Application Appendix K RADIUS Billing and VXML Calling Card Application The Mediant 2000 calling card application capability (included in its IVR - Interactive Voice Response - feature) enables Internet Telephony Service Providers (ITSPs) to provide a VoIP telephone service to subscribers who have purchased calling cards in advance. The subscriber market for calling cards is growing exponentially worldwide.
Mediant 2000 SIP K.3 • Loads the VXML scripts once and stores them in the RAM; scripts can be changed without the need of reset • Barge-in dialing (to shorten menu time), once prompt has started Supported Architecture Figure K-1: Mediant 2000 Supported Architecture Figure K-1 illustrates standard Calling Card IVR application architecture. The figure depicts in general terms an incoming PSTN IP call being conveyed to the IP network.
Mediant 2000 SIP User’s Manual K.4 K. RADIUS Billing and VXML Calling Card Application Implementation The Mediant 2000 uses an embedded VoiceXML interpreter to interpret and execute standard VoiceXML scripts, which are loaded from an outbound HTTP server and stored in the gateway’s volatile memory (RAM).
Mediant 2000 SIP K.4.2 Call Flow Description Figure K-2 on the previous page depicts an example of a standard PSTN IP call (billing-model: debit). • An incoming PSTN call with a published access number reaches the Mediant 2000. • The Mediant 2000 accepts the call (sends an Alert message). • The Mediant 2000 searches its internal Tel IP Destination Number Manipulation table for the specific prefix.
Mediant 2000 SIP User’s Manual K.5 K. RADIUS Billing and VXML Calling Card Application Operation & Configuration To start working with the IVR system, take these 6 steps: 1. Install the Mediant 2000 (refer to Section Installing the Mediant 2000 on page 27 and to Section Getting Started on page 35). 2. Create and load a Voice Prompts file to the Mediant 2000 (refer to Section 7.3 on page 137). 3. Create the VXML scripts (refer to Section K.9 on page 254). 4.
Mediant 2000 SIP ini File Field Name NumberMapIP2Tel 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. A combination of both options is allowed. c = String to add as prefix, or (if brackets are used) as suffix. A combination of both options is allowed. d = Number of remaining digits from the right e = Q.
Mediant 2000 SIP User’s Manual K.7 K. RADIUS Billing and VXML Calling Card Application • RADIUSAuthServerIP • RADIUSAuthPort • RADIUSAccServerIP • RADIUSAccPort • AAAIndications • RADIUSAccountingType Supported RADIUS Attributes Use Table K-3 below for explanations on the RADIUS attributes contained in the communication packets transmitted between the Mediant 2000 and a RADIUS Server.
Mediant 2000 SIP Table K-3: Supported RADIUS Attributes (continues on pages 251 to 252) Attribute Number Attribute Name 26 h323-gw-id 30 Called-Station-Id 31 VSA No.
Mediant 2000 SIP User’s Manual K.8 RADIUS Server Messages Note: K.8.1 K. RADIUS Billing and VXML Calling Card Application In Figure K-4, Figure K-5 and Figure K-6 non-standard parameters are preceded with brackets. Authentication Figure K-4: Authentication Example Access-Request (116) user-name = 111 user-password = (encrypted) nas-ip-address = 212.179.22.
Mediant 2000 SIP 12.1.2 Accounting Figure K-6: Accounting Example Accounting-Request (361) user-name = 111 acct-session-id = 1 nas-ip-address = 212.179.22.213 nas-port-type = 0 acct-status-type = 2 acct-input-octets = 4841 acct-output-octets = 8800 acct-session-time = 1 acct-input-packets = 122 acct-output-packets = 220 called-station-id = 201 calling-station-id = 202 // Accounting non-standard parameters: (4923 33) h323-gw-id = (4923 23) h323-remote-address = 212.179.22.
Mediant 2000 SIP User’s Manual K. RADIUS Billing and VXML Calling Card Application The user_passwd parameter (that initially contained the user password collected from the user) is being assigned the value ‘domain'+user_passwd + '.com’. • Calling number (recived form SIP incoming call) can optionally be used for authentication instead of the user name. form id="GetCallerId">
Mediant 2000 SIP User’s Manual K.
Mediant 2000 SIP Table K-4: VoiceXML Supported Elements & Attributes (continues on pages 256 to 260) Element
Mediant 2000 SIP User’s Manual K. RADIUS Billing and VXML Calling Card Application Table K-4: VoiceXML Supported Elements & Attributes (continues on pages 256 to 260) Element Element’s Description Return from a subdialog. Parameter s finalsilence The interval of silence that indicates end of speech. (Not Supported) dtmfterm If true, any DTMF keypress not matched by an active grammar is treated as a match of an active local DTMF grammar.
Mediant 2000 SIP Table K-4: VoiceXML Supported Elements & Attributes (continues on pages 256 to 260) Element Element’s Description Parameter s Parameter’s Description Supported transferaudi o The URI of audio source to play while the transfer attempt is in progress (before far-end answer). (Not Supported) endaudio An internal Voice Prompt ID that determines the VP that is played when the maximal time allowed for a call expires.
Mediant 2000 SIP User’s Manual K. RADIUS Billing and VXML Calling Card Application 8. “Your account number and password do not match”. 9. “We are having technical difficulties, please call again later”. 10. “Please enter the number that you wish to call followed by the pound key”. 11. “The number you are calling is busy”. 12. “The number you are calling is not answering, please call again later”. 13. “The person you called has hung up”. 14. “We are unable to complete your call”. 15.
Mediant 2000 SIP K.11.
Mediant 2000 SIP User’s Manual K. RADIUS Billing and VXML Calling Card Application Figure K-8: VXML Script Option 1, Make a Call 1 Play VP 5 No DTMF Pressed? Play VP 3 Yes Play VP 6 Go To 1 DTMF Pressed? No Play VP 3 Yes Play VP 7 Waits for Authentication Authentication Finished? No Yes Yes Go To Transfer Yes Play VP 4 Authentication OK? No No Match Counter = x? No Play VP 7 Go To End No Go To 1 Version 4.
Mediant 2000 SIP Figure K-9: VXML Script, Call Transfer Procedure Transfer Play VP 10 DTMF Pressed? No Play VP 3 Yes Play VP 15 Go to Transfer Call for transfer service No Transfer Failed? Play either VP 11, 12 or 13 according to Transfer failure reason No Yes Yes Debit? Final alert time expired? No Go to End Yes Play VP 20 Time for call expired? No Yes Play VP 21 End Mediant 2000 SIP User’s Manual 264 Document #: LTRT-72504
Mediant 2000 SIP User’s Manual K. RADIUS Billing and VXML Calling Card Application Figure K-10: VXML Script, Options 2, 3 and 4 2 Play VP 17 Go To Start 3 Transfer Call To an Operator End 4 Play VP 16 End Figure K-11: VXML Script, Call Termination End VXML Script Terminated? Yes No Play VP 16 Go To Start Free Resources End Version 4.
Mediant 2000 SIP K.12 VXML Script Example Figure K-12: VXML Script Example (continues on pages 266 to 270)
Mediant 2000 SIP Figure K-12: VXML Script Example (continues on pages 266 to 270) called transfer failed
Mediant 2000 SIP Table L-2: acBoardConfigurationError Alarm Trap Corrective Action: Inspect the run-time specific string to determine the nature of the configuration error. Fix the configuration error using the appropriate tool: Web interface, EMS, or ini file. Save the configuration and if necessary reset the device. Table L-3: acBoardTemperatureAlarm Alarm Trap Alarm: acBoardTemperatureAlarm OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.
Mediant 2000 SIP User’s Manual L. SNMP Traps Table L-5: acFeatureKeyError Alarm Trap Condition: After raise Alarm status: Status stays critical until reboot. A clear trap is not sent. Corrective Action: Obtain a corrected feature key from AudioCodes, activate it by loading to the device, then reset the device. Table L-6: acBoardCallResourcesAlarm Alarm Trap Alarm: acBoardCallResourcesAlarm OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.
Mediant 2000 SIP Table L-8: acBoardOverloadAlarm Alarm Trap Condition: An overload condition exists in one or more of the system components.
Mediant 2000 SIP User’s Manual L.1.2 L. SNMP Traps Component: AlarmManager#0 Table L-9: acActiveAlarmTableOverflow Alarm Trap Alarm: acActiveAlarmTableOverflow OID: 1.3.6.1.4.15003.9.10.1.21.2.0.
Mediant 2000 SIP L.1.4 Other Traps The following are provided as SNMP traps and are not alarms. Table L-11: coldStart Trap Trap Name: coldStart OID: 1.3.6.1.6.3.1.1.5.1 MIB SNMPv2-MIB Note: This is a trap from the standard SNMP MIB. Table L-12: authenticationFailure Trap Trap Name: authenticationFailure OID: 1.3.6.1.6.3.1.1.5.5 MIB SNMPv2-MIB Table L-13: acBoardEvBoardStarted Trap Trap Name: acBoardEvBoardStarted OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.
Mediant 2000 SIP User’s Manual M.
Mediant 2000 SIP 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 SIP User’s Manual M. Regulatory Information Original printed on recycled paper and available on CD or Web site Version 4.
AudioCodes Offices International Headquarters AudioCodes Ltd. 1 Hayarden Street, Airport City, Lod 70151, Israel. Tel: +972-3-976 4000 Fax: +972-3-976 4040 Email: info@audiocodes.com USA Headquarters AudioCodes, Inc. 2099 Gateway Place, Suite 500 San Jose, CA 95110 Tel: +1-408-411-1175 Fax: +1-408-451-9520 Email: info@audiocodes.
