MediaPack SIP User’s Manual Version 4.
Notice This document describes the AudioCodes MediaPack series Voice over IP (VoIP) gateways. 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. Updates to this document and other documents can be viewed by registered Technical Support customers at www.
MediaPack SIP User’s Manual Contents Table of Contents 1 Overview ....................................................................................................................17 1.1 1.2 1.3 1.4 2 Introduction .....................................................................................................................................17 Gateway Description.......................................................................................................................17 SIP Overview .
MediaPack SIP 5.2.3 Disabling the Embedded Web Server.....................................................................................48 Accessing the Embedded Web Server...........................................................................................48 5.3.1 Using Internet Explorer to Access the Embedded Web Server..............................................49 5.4 Getting Acquainted with the Web Interface ....................................................................................
MediaPack SIP User’s Manual Contents 5.6.5 Changing the MediaPack Username and Password ............................................................146 Status & Diagnostics.....................................................................................................................147 5.7.1 Gateway Statistics ................................................................................................................147 5.7.1.1 IP Connectivity.....................................................
MediaPack SIP 8.11.4 Remote IP Extension between FXO and FXS ......................................................................189 8.11.4.1 Dialing from Remote Extension ..................................................................................189 8.11.4.2 Dialing from other PBX line, or from PSTN ................................................................190 8.11.4.3 FXS MediaPack Configuration (using the Embedded Web Server)...........................190 8.11.4.
MediaPack SIP User’s Manual Contents 15 SNMP-Based Management ..................................................................................... 227 15.1 About SNMP .................................................................................................................................227 15.1.1 SNMP Message Standard ....................................................................................................227 15.1.2 SNMP MIB Objects ....................................................
MediaPack SIP B.11.6 Using Command Line Switches ............................................................................................266 B.12 Managing Client Templates..........................................................................................................267 Appendix C C.1 C.2 C.3 RTP/RTCP Payload Types and Port Allocation .................................. 269 Packet Types Defined in RFC 3551 ......................................................................................
MediaPack SIP User’s Manual Contents List of Figures Figure 1-1: Typical MediaPack VoIP Application .............................................................................................18 Figure 2-1: MP-108 Front Panel .......................................................................................................................23 Figure 2-2: MP-124 Front Panel .......................................................................................................................
MediaPack SIP Figure 5-34: VLAN Settings Screen ...............................................................................................................125 Figure 5-35: Security Settings Screen............................................................................................................127 Figure 5-36: Voice Settings Screen................................................................................................................134 Figure 5-37: Fax / Modem / CID Settings Screen ...
MediaPack SIP User’s Manual Contents Figure D-4: Prerecorded Tones Screen .........................................................................................................274 Figure D-5: File Data Window ........................................................................................................................275 Figure D-6: Initial Settings Screen..................................................................................................................
MediaPack SIP List of Tables Table 2-1: Front Panel Buttons on the MP-1xx ................................................................................................24 Table 2-2: Indicator LEDs on the MP-1xx Front Panel.....................................................................................24 Table 2-3: MP-10x Rear Panel Component Descriptions ................................................................................25 Table 2-4: Indicator LEDs on the MP-10x Rear Panel .............
MediaPack SIP User’s Manual Contents Table 5-45: IP Connectivity Parameters.........................................................................................................148 Table 5-46: Call Counters Description (continues on pages 149 to 150).......................................................149 Table 5-47: Call Routing Status Parameters..................................................................................................150 Table 5-48: Channel Status Color Indicators ..........
MediaPack SIP Reader’s Notes MediaPack SIP User’s Manual 14 Document #: LTRT-65405
MediaPack SIP User’s Manual Tip: General 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.
MediaPack SIP Note: Where ‘network’ appears in this manual, it means Local Area Network (LAN), Wide Area Network (WAN), etc. accessed via the gateway’s Ethernet interface. Note: FXO (Foreign Exchange Office) is the interface replacing the analog telephone and connects to a Public Switched Telephone Network (PSTN) line from the Central Office (CO) or to a Private Branch Exchange (PBX).
MediaPack SIP User’s Manual 1 Overview 1.1 Introduction 1. Overview This document provides you with the information on installation, configuration and operation of the MP-124 24-port, MP-108 8-port, MP-104 4-port, MP-102 2-port, MP-118 8-port, MP-114 4port and MP-112 2-port VoIP media gateways. As these units have similar functionality (with the exception of their number of channels and some minor features), they are collectively referred to in the manual as the MediaPack. 1.
MediaPack SIP The layout diagram (Figure 1-1), illustrates a typical MediaPack VoIP application. Figure 1-1: Typical MediaPack VoIP Application 1.3 SIP Overview SIP (Session Initialization Protocol) is an application-layer control (signaling) protocol used on the MediaPack for creating, modifying, and terminating sessions with one or more participants. These sessions can include Internet telephone calls, media announcements and conferences.
MediaPack SIP User’s Manual 1.4 1. Overview MediaPack Features This section provides a high-level overview of some of the many MediaPack supported features. 1.4.1 1.4.2 1.4.3 General Features • Superior, high quality Voice, Data and fax over IP networks. • Toll quality voice compression. • Enhanced capabilities including MWI, long haul, metering, CID and out door protection. • Proven integration with leading PBXs, IP-PBXs, Softswitches and SIP servers.
MediaPack SIP • 1.4.4 Restart button on the back panel that restarts the MP-11x gateway, and is also used to restore the MP-11x parameters to their factory default values. SIP Features The MediaPack SIP gateway complies with the IETF RFC 3261 standard. • Reliable User Datagram Protocol (UDP) transport, with retransmissions. • Transmission Control Protocol (TCP) Transport layer. • SIPS using TLS (MP-11x only). • T.38 real time fax (using SIP).
MediaPack SIP User’s Manual 1. Overview ¾ INFO method . ¾ INFO method, compatible with Cisco gateways. ¾ NOTIFY method . • SIP URL: sip:”phone number”@IP address (such as 122@10.1.2.4, where “122” is the phone number of the source or destination phone number) or sip:”phone_number”@”domain name”, such as 122@myproxy.com. Note that the SIP URI host name can be configured differently per called number.
MediaPack SIP Reader’s Notes MediaPack SIP User’s Manual 22 Document #: LTRT-65405
MediaPack SIP User’s Manual 2 2. MediaPack Physical Description MediaPack Physical Description This section provides detailed information on the hardware, the location and functionality of the LEDs, buttons and connectors on the front and rear panels of the MP-1xx (refer to Section 2.1 below) and MP-11x (Section 2.2 on page 27) gateways. For detailed information on installing the MediaPack, refer to Section 3 on page 29. 2.1 MP-1xx Physical Description 2.1.
MediaPack SIP 2.1.1.1 MP-1xx Front Panel Buttons Table 2-1 lists and describes the front panel buttons on the MP-1xx. Table 2-1: Front Panel Buttons on the MP-1xx Type Function Reset the MP-1xx Reset button 2.1.1.2 Comment Press the reset button with a paper clip or any other similar pointed object, until the gateway is reset. Restore the MP-1xx parameters to Refer to Section 10.1 on page 201.
MediaPack SIP User’s Manual 2. MediaPack Physical Description 2.1.2 MP-1xx Rear Panel 2.1.2.1 MP-10x Rear Panel Figure 2-3 illustrates the rear panel layout of the MP-104. For descriptions of the MP-10x rear panel components, refer to Table 2-3. For the functionality of the MP-10x rear panel LEDs, refer to Table 2-4. Tip 1: MP-10x (FXS/FXO) media gateways feature almost identical rear panel connectors and LEDs, located slightly differently from one device to the next.
MediaPack SIP 2.1.2.2 MP-124 Rear Panel Figure 2-4 illustrates the rear panel layout of the MP-124. For descriptions of the MP-124 rear panel components, refer to Table 2-5. For the functionality of the MP-124 rear panel LEDs, refer to Table 2-6. Figure 2-4: MP-124 (FXS) Rear Panel Connectors 3 2 1 4 6 5 Table 2-5: MP-124 Rear Panel Component Descriptions Item # Label Component Description 1 Protective earthing screw (mandatory for all installations).
MediaPack SIP User’s Manual 2. MediaPack Physical Description 2.2 MP-11x Physical Description 2.2.1 MP-11x Front Panel Figure 2-5 illustrates the front layout of the MP-118 (almost identical on MP-114 and MP-112). Table 2-7 lists and describes the front panel LEDs on the MP-11x. Tip: MP-11x gateways feature almost identical front panel LEDs; they only differ in the number of channel LEDs that correspond to the number of channels.
MediaPack SIP 2.2.2 MP-11x Rear Panel Figure 2-6 illustrates the rear layout of the MP-118 (almost identical on MP-114 and MP-112). Table 2-8 lists and describes the rear panel connectors and button on the MP-11x. Figure 2-6: MP-118 Rear Panel Connectors 1 2 3 4 5 4 Table 2-8: MP-11x Rear Panel Component Descriptions Item # Label 1 100-240~0.3A max.
MediaPack SIP User’s Manual 3 3. Installing the MediaPack Installing the MediaPack This section provides information on the installation procedure for the MP-1xx (refer to Section 3.1 below) and the MP-11x (refer to Section 3.2 on page 38). For information on how to start using the gateway, refer to Section 4 on page 43. Caution Electrical Shock The equipment must only be installed or serviced by qualified service personnel. 3.1 Installing the MP-1xx ¾ To install the MP-1xx, take these 4 steps: 1.
MediaPack SIP 3.1.2 Mounting the MP-1xx The MP-1xx can be mounted on a desktop or on a wall (only MP-10x), or installed in a standard 19-inch rack. Refer to Section 3.1.3 on page 33 for cabling the MP-1xx. 3.1.2.1 Mounting the MP-1xx on a Desktop No brackets are required. Simply place the MP-1xx on the desktop in the position you require.
MediaPack SIP User’s Manual 3. Installing the MediaPack 4. Use the screws found in the devices’ package to attach the short bracket to the side of the device. 5. Remove the two screws on the other side of the device nearest the front panel. 6. Position the long bracket so that the holes in the bracket line up with the two empty screw holes on the device. 7. Use the screws found in the device’s package to attach the long bracket to the side of the device. 8.
MediaPack SIP Figure 3-3: MP-124 with Brackets for Rack Installation 3.1.2.4 Mounting the MP-10x on a Wall The MP-10x is mounted on a wall by the addition of two short (equal-length) supplied brackets. The MP-102 with brackets for wall mount is shown in Figure 3-4. ¾ To mount the MP-10x on a wall, take these 7 steps: 1. Remove the screw on the side of the device that is nearest the bottom and the front panel. 2.
MediaPack SIP User’s Manual 3.1.3 3. Installing the MediaPack Cabling the MP-1xx Verify that you have the cables listed under column ‘Cable’ in Table 3-1 before beginning to cable the MP-1xx according to the column ‘Cabling Procedure’. For detailed information on the MP-1xx rear panel connectors, refer to Section 2.1.2 on page 25.
MediaPack SIP Figure 3-6: RJ-11 Phone Connector Pinout RJ-11 Connector and Pinout 1234 1234- Not connected Tip Ring Not connected Figure 3-7: 50-pin Telco Connector (MP-124/FXS only) Pin Numbers 25 1 26 50 Figure 3-8: MP-124 in a 19-inch Rack with MDF Adaptor 19-inch Rack Rear View FRONT INPUT 24 line cords 2-wire with RJ-11 connectors M D F Adaptor Block - rear REAR OUTPUT 24 wire pairs in Octopus cable with 50-pin male Telco connector Primary LAN Cable to Eth 1 AC Power Cord Back-up LAN Ca
MediaPack SIP User’s Manual 3. Installing the MediaPack Table 3-2: Pin Allocation in the 50-pin Telco Connector Phone Channel Connector Pins Phone Channel Connector Pins 1 2 3 4 5 6 7 8 9 10 11 12 1/26 2/27 3/28 4/29 5/30 6/31 7/32 8/33 9/34 10/35 11/36 12/37 13 14 15 16 17 18 19 20 21 22 23 24 13/38 14/39 15/40 16/41 17/42 18/43 19/44 20/45 21/46 22/47 23/48 24/49 3.1.3.
MediaPack SIP Figure 3-10: Lifeline Splitter Pinout & RJ-11 Connector for MP-10x/FXS 1234 1234- Lifeline Tip Tip Ring Lifeline Ring ¾ To cable the MP-10x/FXS Lifeline phone, take these 3 steps: 1. Connect the Lifeline Splitter to port #4 (on the MP-104/FXS or MP-108/FXS) or to port #2 (on the MP-102/FXS). 2. Connect the Lifeline phone to Port A on the Lifeline Splitter. 3. Connect an analog PSTN line to Port B on the Lifeline Splitter.
MediaPack SIP User’s Manual 3. Installing the MediaPack Table 3-3: MP-104/FXS Lifeline Setup Component Descriptions Item # Version 4.6 Component Description 1 B: To PSTN wall port. 2 Phone to Port 1. 3 Lifeline to Port 4. 4 PSTN to Splitter (B). 5 Phone to Port 1. 6 Lifeline phone to Splitter (A). 7 Lifeline phone.
MediaPack SIP 3.2 Installing the MP-11x ¾ To install the MP-11x, take these 3 steps: 1. Unpack the MP-11x (refer to Section 3.2.1 below). 2. Check the package contents (refer to Section 3.2.2 below). 3. Mount the MP-11x (refer to Section 3.2.4 on page 39). 4. Cable the MP-11x (refer to Section 3.2.5 on page 33). After connecting the MP-11x to the power source, the Ready and Power LEDs on the front panel turn to green (after a self-testing period of about 2 minutes).
MediaPack SIP User’s Manual 3.2.3 3. Installing the MediaPack 19-inch Rack Installation Package Additional option is available for installing the MP-11x in a 19-inch rack. The 19-inch rack installation package contains a single shelf (shown in Figure 3-12 below) and eight shelf-todevice screws. Figure 3-12: 19-inch Rack Shelf 3.2.4 Mounting the MP-11x The MP-11x can be mounted on a desktop (refer to Section 3.2.4.1 below), on a wall (refer to Section 3.2.4.
MediaPack SIP 3.2.4.1 Mounting the MP-11x on a Desktop Attach the four (supplied) anti-slide bumpers to the base of the MP-11x (refer to item #1 in Figure 3-13) and place it on the desktop in the position you require. 3.2.4.2 Mounting the MP-11x on a Wall ¾ To mount the MP-11x on a wall, take these 4 steps: 1. 3.2.4.3 Drill four holes according to the following dimensions: ¾ Side-to-side distance 140 mm. ¾ Front-to-back distance 101.4 mm. 2.
MediaPack SIP User’s Manual 3.2.5 3. Installing the MediaPack Cabling the MP-11x Cable your MP-11x according to each section of Table 3-6. For detailed information on the MP11x rear panel connectors, refer to Table 2-8 on page 28. Table 3-6: Cables and Cabling Procedure Cable Cabling Procedure RJ-45 Ethernet cable Connect the Ethernet connection on the MP-11x directly to the network using a standard RJ-45 Ethernet cable. For connector’s pinout refer to Figure 3-15 on page 41.
MediaPack SIP 3.2.5.2 Cabling the MP-11x Lifeline The Lifeline (connected to port #1) provides a wired analog POTS phone connection to any PSTN or PBX FXS port when there is no power, or the when network connection fails. Users can therefore use the Lifeline phone even when the MP-11x is not powered on or not connected to the network. The Lifeline’s Splitter connects pins #1 and #4 to another source of an FXS port, and pins #2 and #3 to the POTS phone. Refer to the Lifeline Splitter pinout in Figure 3-18.
MediaPack SIP User’s Manual 4 4. Getting Started Getting Started The MediaPack is supplied with default networking parameters (show in Table 4-1 below) and with an application software already resident in its flash memory (with factory default parameters). Before you begin configuring the gateway, change its default IP address to correspond with your network environment (refer to Section 4.2) and learn about the configuration methods available on the MediaPack (refer to Section 4.1 below).
MediaPack SIP 4.2.1 Assigning an IP Address Using HTTP ¾ To assign an IP address using HTTP, take these 8 steps: 1. Disconnect the MediaPack from the network and reconnect it to your PC using one of the following two methods: ¾ Use a standard Ethernet cable to connect the network interface on your PC to a port on a network hub / switch. Use a second standard Ethernet cable to connect the MediaPack to another port on the same network hub / switch.
MediaPack SIP User’s Manual 4.3 4. Getting Started 2. Add client configuration for the MediaPack, refer to Section B.11.1 on page 263. 3. Use the reset button to physically reset the gateway causing it to use BootP; the MediaPack changes its network parameters to the values provided by the BootP. Configure the MediaPack Basic Parameters To configure the MediaPack basic parameters use the Embedded Web Server’s ‘Quick Setup’ screen (shown in Figure 4-1 below). Refer to Section 5.
MediaPack SIP ‘Registration Time’ seconds; The MediaPack sends a REGISTER request according to the ‘Authentication Mode’ parameter. For detailed information on the parameters ‘Registration Time’ and ‘Authentication Mode’, refer to Table 5-2 on page 57. 6. Select the coder (i.e., vocoder) that best suits your VoIP system requirements. The default coder is: G.7231 30 msec.
MediaPack SIP User’s Manual 5 5. Configuring the MediaPack Configuring the MediaPack The Embedded Web Server is used both for gateway configuration, including loading of configuration files, and for run-time monitoring. The Embedded Web Server can be accessed from a standard Web browser, such as Microsoft™ Internet Explorer, Netscape™ Navigator, etc. Specifically, users can employ this facility to set up the gateway configuration parameters.
MediaPack SIP The first time a browser request is made, the user is requested to provide his Administrator or Monitoring username and password to obtain access. Subsequent requests are negotiated by the browser on behalf of the user, so that the user doesn’t have to re-enter the username and password for each request, but the request is still authenticated (the Embedded Web Server uses the MD5 authentication method supported by the HTTP 1.1 protocol).
MediaPack SIP User’s Manual 5.3.1 5. Configuring the MediaPack Using Internet Explorer to Access the Embedded Web Server Internet explorer’s security settings may block access to the gateway’s Web browser if they’re configured incorrectly. In this case, the following message is displayed: Unauthorized Correct authorization is required for this area. Either your browser does not perform authorization or your authorization has failed. RomPager server.
MediaPack SIP 5.4.1 • Main menu bar - always appears on the left of every screen to quickly access parameters, submenus, submenu options, functions and operations. • Submenu bar - appears on the top of screens and contains submenu options. • Main action frame - the main area of the screen in which information is viewed and configured. • Corporate logo – AudioCodes’ corporate logo. For information on how to remove this logo Section 10.5 on page 206.
MediaPack SIP User’s Manual 5.5 5. Configuring the MediaPack Protocol Management Use this menu to configure the gateway’s SIP parameters and tables. Note: 5.5.1 Those parameters contained within square brackets are the names used to configure the parameters via the ini file. Protocol Definition Parameters Use this submenu to configure the gateway’s specific SIP protocol parameters. 5.5.1.1 General Parameters Use this screen to configure general SIP parameters.
MediaPack SIP 2. Configure the general parameters under Protocol Definition according to Table 5-1. 3. Click the Submit button to save your changes. 4. To save the changes so they are available after a power fail, refer to Section 5.9 on page 161. Table 5-1: Protocol Definition, General Parameters (continues on pages 52 to 55) Parameter Description PRACK Mode [PRACKMode] PRACK mechanism mode for 1XX reliable responses: Disable [0]. Supported [1] (default). Required [2].
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-1: Protocol Definition, General Parameters (continues on pages 52 to 55) Parameter Description Asserted Identity Mode [AssertedIdMode] Disable [0] = None (default). Adding PAsserted Identity [1]. Adding PPreferred Identity [2]. 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.
MediaPack SIP Table 5-1: Protocol Definition, General Parameters (continues on pages 52 to 55) Parameter Description Enable SIPS [EnableSIPS] Enables secured SIP (SIPS) connections over multiple hops (MP-11x only). Disable [0] (default). Enable [1]. When SIPTransportType = 2 (TLS) and EnableSIPS is disabled, TLS is used for the next network hop only. When SIPTransportType = 2 (TLS) or 1 (TCP) and EnableSIPS is enabled, TLS is used through the entire connection (over multiple hops).
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-1: Protocol Definition, General Parameters (continues on pages 52 to 55) Parameter Description Retransmission Parameters SIP T1 Retransmission Timer The time interval (in msec) between the first transmission of a SIP message and the first [msec] retransmission of the same message. [SipT1Rtx] The default is 500.
MediaPack SIP 5.5.1.2 Proxy & Registration Parameters Use this screen to configure parameters that are associated with Proxy and Registration. ¾ To configure the Proxy & Registration parameters, take these 4 steps: 1. Open the ‘Proxy & Registration’ parameters screen (Protocol Management menu > Protocol Definition submenu > Proxy & Registration option); the ‘Proxy & Registration’ parameters screen is displayed. Figure 5-4: Proxy & Registration Parameters Screen 2.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-2: Proxy & Registration Parameters (continues on pages 57 to 60) Parameter Description Enable Proxy [IsProxyUsed] Don’t Use Proxy [0] = Proxy isn’t used, the internal routing table is used instead (default). Use Proxy [1] = Proxy is used. If you are using a Proxy server, enter the IP address of the primary Proxy server in the Proxy IP address field.
MediaPack SIP Table 5-2: Proxy & Registration Parameters (continues on pages 57 to 60) Parameter Description Third Redundant Proxy IP Address [ProxyIP] IP addresses of the third redundant Proxy you are using. Enter the IP address as FQDN or in dotted format notation (for example 192.10.1.255). You can also specify the selected port in the format: :. Note 1: This parameter is available only if you select ‘Yes’ in the ‘Enable Proxy’ field.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-2: Proxy & Registration Parameters (continues on pages 57 to 60) Parameter Description Registrar IP Address [RegistrarIP] IP address and optionally port number of Registrar server. Enter the IP address in dotted format notation, for example 201.10.8.1:<5080>. Note 1: If not specified, the REGISTER request is sent to the primary Proxy server (refer to ‘Proxy IP address’ parameter).
MediaPack SIP Table 5-2: Proxy & Registration Parameters (continues on pages 57 to 60) Parameter Description Send All INVITE to Proxy [SendInviteToProxy] No [0] = INVITE messages, generated as a result of Transfer or Redirect, are sent directly to the URL (according to the refer-to header in the REFER message or contact header in 30x response) (default). Yes [1] = All INVITE messages, including those generated as a result of Transfer or Redirect are sent to Proxy.
MediaPack SIP User’s Manual 5.5.1.3 5. Configuring the MediaPack Coders From the Coders screen you can configure the first to fifth preferred coders (and their corresponding ptimes) for the gateway. The first coder is the highest priority coder and is used by the gateway whenever possible. If the far end gateway cannot use the coder assigned as the first coder, the gateway attempts to use the next coder and so forth. ¾ To configure the Gateway’s coders, take these 6 steps: 1.
MediaPack SIP Table 5-3: ini File Coder Parameter Parameter Description CoderName Enter the coders in the format: CoderName=,. For example: CoderName = g711Alaw64k,20 CoderName = g711Ulaw64k,40 CoderName = g7231,90 Note 1: This parameter (CoderName) can appear up to 10 times. Note 2: The coder name is case-sensitive. You can select the following coders: g711Alaw64k – G.711 A-law. g711Ulaw64k – G.711 µ-law. g7231 – G.723.1 6.3 kbps (default). g7231r53 – G.723.1 5.3 kbps. g726 – G.
MediaPack SIP User’s Manual 5.5.1.4 5. Configuring the MediaPack DTMF & Dialing Parameters Use this screen to configure parameters that are associated with DTMF and dialing. ¾ To configure the dialing parameters, take these 4 steps: 1. Open the ‘DTMF & Dialing’ screen (Protocol Management menu > Protocol Definition submenu > DTMF & Dialing option); the ‘DTMF & Dialing’ parameters screen is displayed. Figure 5-6: DTMF & Dialing Parameters Screen 2.
MediaPack SIP Table 5-4: DTMF & Dialing Parameters (continues on pages 63 to 65) Parameter Description Use Out-of-Band DTMF [IsDTMFUsed] Use out-of-band signaling to relay DTMF digits. No [0] = DTMF digits are sent in-band (default). Yes [1] = DTMF digits are sent out-of-band according to the parameter ‘Out-of-band DTMF format’. Note: When out-of-band DTMF transfer is used, the parameter ‘DTMF Transport Type’ is automatically set to 0 (erase the DTMF digits from the RTP stream).
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-4: DTMF & Dialing Parameters (continues on pages 63 to 65) Parameter Description Digit Mapping Rules [DigitMapping] Digit map pattern. If the digit string (dialed number) has matched one of the patterns in the digit map, the gateway stops collecting digits and starts to establish a call with the collected number The digit map pattern contains up to 52 options separated by a vertical bar (|).
MediaPack SIP 5.5.2 Configuring the Advanced Parameters Use this submenu to configure the gateway’s advanced control protocol parameters. 5.5.2.1 General Parameters Use this screen to configure general control protocol parameters. ¾ To configure the general parameters under Advanced Parameters, take these 4 steps: 1. Open the ‘General Parameters’ screen (Protocol Management menu > Advanced Parameters submenu > General Parameters option); the ‘General Parameters’ screen is displayed.
MediaPack SIP User’s Manual 5. Configuring the MediaPack 2. Configure the general parameters under ‘Advanced Parameters’ according to Table 5-5. 3. Click the Submit button to save your changes. 4. To save the changes so they are available after a power fail, refer to Section 5.9 on page 161.
MediaPack SIP Table 5-5: Advanced Parameters, General Parameters (continues on pages 67 to 70) Parameter Description Enable DID Wink [EnableDIDWink] Disable [0] = DID is disabled (default). Enable [1] = Enable DID. If enabled, the MediaPack can be used for connection to EIA/TIA-464B DID Loop Start lines. Both FXO (detection) and FXS (generation) are supported. An FXO gateway dials DTMF digits after a Wink signal is detected (instead of a Dial tone).
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-5: Advanced Parameters, General Parameters (continues on pages 67 to 70) Parameter Description Silence Detection Method Silence detection method. [FarEndDisconnectSilenceM None [0] = Silence detection option is disabled. ethod] Packets Count [1] = According to packet count. Voice/Energy Detectors [2] = According to energy and voice detectors (default). All [3] = According to packet count and energy / voice detectors.
MediaPack SIP Table 5-5: Advanced Parameters, General Parameters (continues on pages 67 to 70) Parameter Description Max Number of Active Calls [MaxActiveCalls] Defines the maximum number of calls that the gateway can have active at the same time. If the maximum number of calls is reached, new calls are not established. The default value is max available channels (no restriction on the maximum number of calls). The valid range is 1 to max number of channels.
MediaPack SIP User’s Manual 5.5.2.2 5. Configuring the MediaPack Supplementary Services Use this screen to configure parameters that are associated with supplementary services. For detailed information on the supplementary services, refer to Section 8.1 on page 169. ¾ To configure the supplementary services’ parameters, take these 4 steps: 1.
MediaPack SIP Table 5-6: Supplementary Services Parameters (continues on pages 72 to 74) Parameter Description Enable Hold [EnableHold] No [0] = Disable the Hold service (default). Yes [1] = Enable the Hold service. If the Hold service is enabled, a user can activate Hold (or Unhold) using the hook-flash. On receiving a Hold request, the remote party is put on-hold and hears the hold tone. Note: To use this service, the gateways at both ends must support this option.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-6: Supplementary Services Parameters (continues on pages 72 to 74) Parameter Description Enable Caller ID [EnableCallerID] No [0] = Disable the Caller ID service (default). Yes [1] = Enable the Caller ID service. If the Caller ID service is enabled, then, for FXS gateways, calling number and Display text are sent to gateway port.
MediaPack SIP Table 5-6: Supplementary Services Parameters (continues on pages 72 to 74) Parameter Description Stutter Tone Duration [StutterToneDuration] Duration (in msec) of the played stutter dial tone that indicates waiting message(s). The default is 2000 (2 seconds). The range is 1000 to 60000. The Stutter tone is played (instead of a regular Dial tone) when a MWI is received. The tone is composed of a ‘Confirmation tone’ that is played for ‘StutterToneDuration’ followed by a ‘Stutter tone’.
MediaPack SIP User’s Manual 4. 5. Configuring the MediaPack To save the changes so they are available after a power fail, refer to Section 5.9 on page 161. Note: The method used by the gateway to collect dialed numbers is identical to the method used during a regular call (i.e., max digits, interdigit timeout, digit map, etc.). Table 5-7: Keypad Features Parameters Parameter Description Forward Unconditional [KeyCFUnCond] Keypad sequence that activates the immediate forward option.
MediaPack SIP 5.5.3 Configuring the Number Manipulation Tables The VoIP gateway provides four Number Manipulation tables for incoming and outgoing calls. These tables are used to modify the destination and source telephone numbers so that the calls can be routed correctly.
MediaPack SIP User’s Manual 5. Configuring the MediaPack 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.9 on page 161. Table 5-8: Number Manipulation Parameters Parameter Description Destination Prefix Each entry in the Destination Prefix fields represents a destination telephone number prefix. An asterisk (*) represents any number.
MediaPack SIP Table 5-9: Number Manipulation ini File Parameters (continues on pages 78 to 79) Parameter Description NumberMapTel2IP Manipulates the destination number for Tel to IP calls. NumberMapTel2IP = a,b,c,d,e,f,g 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.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Parameter Description SourceNumberMapTel2IP 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. c = String to add as prefix, or (if in brackets are used) as suffix. A combination of both options is allowed.
MediaPack SIP For example: • [5551200-5551300]# represents all numbers from 5551200 to 5551300 • [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.
MediaPack SIP User’s Manual 5.5.4 5. Configuring the MediaPack Configuring the Routing Tables Use this submenu to configure the gateway’s IPÆTel and TelÆIP routing tables and their associated parameters. 5.5.4.1 General Parameters Use this screen to configure the gateway’s IPÆTel and TelÆIP routing parameters. ¾ To configure the general parameters under Routing Tables, take these 4 steps: 1.
MediaPack SIP Table 5-10: Routing Tables, General Parameters (continues on pages 81 to 82) Parameter Description IP to Tel Remove Routing Table Prefix [RemovePrefix] No [0] = Don't remove prefix (default) Yes [1] = Remove the prefix (defined in the IP to Hunt Group Routing table) from a telephone number for an IPÆTel call, before forwarding it to Tel. For example: To route an incoming IPÆTel Call with destination number 21100, the IP to Hunt Group Routing table is scanned for a matching prefix.
MediaPack SIP User’s Manual 5.5.4.2 5. Configuring the MediaPack 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).
MediaPack SIP Tel to IP routing can be performed either before or after applying the number manipulation rules. To control when number manipulation is done, set the Tel to IP Routing Mode parameter (described in Table 5-11). Tip: ¾ To configure the Tel to IP Routing table, take these 6 steps: 1. Open the ‘Tel to IP Routing’ screen (Protocol Management menu > Routing Tables submenu > Tel to IP Routing option); the ‘Tel to IP Routing’ screen is displayed (shown in Figure 5-12). 2.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-11: Tel to IP Routing Table Parameter Description Destination IP Address In each of the IP Address fields, enter the IP address (and optionally port number) that is assigned to these prefixes. Domain names, such as domain.com, can be used instead of IP addresses. For example: : To discard outgoing IP calls, enter 0.0.0.0 in this field.
MediaPack SIP 5.5.4.3 IP to Hunt Group Routing The IP to Hunt Group Routing Table is used to route incoming IP calls to groups of channels called hunt groups. Calls are assigned to hunt groups according to any combination of the following three options (or using each independently): • Destination phone prefix • Source phone prefix • Source IP address The call is then sent to the VoIP gateway channels assigned to that hunt group.
MediaPack SIP User’s Manual 5. Configuring the MediaPack 2. In the ‘IP to Tel Routing Mode’ field, select the IP to Tel routing mode (refer to Table 5-12). 3. In the ‘Routing Index’ drop-down list, select the range of entries that you want to edit (up to 24 entries can be configured). 4. Configure the IP to Hunt Group Routing table according to Table 5-12. 5. Click the Submit button to save your changes. 6. To save the changes so they are available after a power fail, refer to Section 5.
MediaPack SIP 5.5.4.4 Internal DNS Table The internal DNS table, similar to a DNS resolution, translates hostnames into IP addresses. This table is used when hostname translation is required (e.g., ‘Tel to IP Routing’ table). Two different IP addresses can be assigned to the same hostname. If the hostname isn’t found in this table, the gateway communicates with an external DNS server. Assigning two IP addresses to hostname can be used for alternative routing (using the ‘Tel to IP Routing’ table).
MediaPack SIP User’s Manual 5.5.4.5 5. Configuring the MediaPack 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.
MediaPack SIP Table 5-14: Reasons for Alternative Routing ini File Parameter Parameter Name in ini File Parameter Format AltRouteCauseTel2IP AltRouteCauseTel2IP = For example: AltRouteCauseTel2IP = 408 AltRouteCauseTel2IP = 486 (Response timeout). (User is busy). Note: This parameter can appear up to 4 times. AltRouteCauseIP2Tel AltRouteCauseIP2Tel = For example: AltRouteCauseIP2Tel = 3 (No route to destination).
MediaPack SIP User’s Manual 5.5.5 5. Configuring the MediaPack Configuring the Profile Definitions Utilizing the Profiles feature, the MediaPack 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.
MediaPack SIP many coder payloads are combined into one RTP (voice) packet. Note 1: The ptime packetization period depends on the selected coder name. 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.
MediaPack SIP User’s Manual 5.5.5.2 5. Configuring the MediaPack Tel Profile Settings Use the Tel Profile Settings screen to define up to four different Tel Profiles. These Profiles are used in the ‘Endpoint Phone Number’ table to associate different Profiles to gateway’s endpoints, thereby applying different behavior to different MediaPack ports. ¾ To configure the Tel Profile settings, take these 9 steps: 1.
MediaPack SIP 5. Configure the Profile’s parameters according to your requirements. For detailed information on each parameter, refer to the description of the screen in which it is configured as an individual parameter. 6. In the ‘Coder Group’ drop-down list, select the coder group you want to assign to that Profile. You can select the gateway’s default coders (refer to Section 5.5.1.3 on page 61) or one of the coder groups you defined in the Coder Group Settings screen (refer to Section 5.5.5.
MediaPack SIP User’s Manual 5.5.5.3 5. Configuring the MediaPack IP Profile Settings Use the IP Profile Settings screen to define up to four different IP Profiles. These Profiles are used in the Tel to IP and IP to Hunt Group Routing tables to associate different Profiles to routing rules. IP Profiles can also be used when working with Proxy server (set ‘AlwaysUseRouteTable’ to 1). ¾ To configure the IP Profile settings, take these 9 steps: 1.
MediaPack SIP the coder groups you defined in the Coder Group Settings screen (refer to Section 5.5.5.1 on page 91). 7. Repeat steps 2 to 6 for the second to fifth IP Profiles (optional). 8. Click the Submit button to save your changes. 9. To save the changes so they are available after a power fail, refer to Section 5.9 on page 161.
MediaPack SIP User’s Manual 5.5.6 5. Configuring the MediaPack Configuring the Endpoint Phone Numbers From the Endpoint Phone Numbers screen you can enable and assign telephone numbers, hunt groups (optional) and profiles to the VoIP gateway ports. ¾ To configure the Endpoint Phone Numbers table, take these 4 steps: 1. Open the ‘Endpoint Phone Numbers Table’ screen (Protocol Management menu > Endpoint Phone Numbers); the ‘Endpoint Phone Numbers Table’ screen is displayed.
MediaPack SIP Table 5-18: Endpoint Phone Numbers Table Parameter Description Hunt Group ID In each of the Hunt Group ID fields, enter the hunt group ID (1-99) assigned to the channel(s). The same hunt group ID can be used for more than one channel and in more than one field. The hunt group ID is an optional field that is used to define a group of common behavior channels that are used for routing IP to Tel calls.
MediaPack SIP User’s Manual 5.5.7 5. Configuring the MediaPack Configuring the Hunt Group Settings The Hunt Group Settings Table is used to determine the method in which new calls are assigned to channels within each hunt group. If such a rule doesn’t exist (for a specific hunt group), the global rule, defined by the Channel Select Mode parameter (Protocol Definition > General Parameters), applies. ¾ To configure the Hunt Group Settings table, take these 7 steps: 1.
MediaPack SIP Table 5-19: 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 ascending cycle order. Always select the next higher channel number in the hunt group. When the gateway reaches the highest channel number in the hunt group, it selects the lowest channel number in the hunt group and then starts ascending again.
MediaPack SIP User’s Manual 5.5.8 5. Configuring the MediaPack Configuring the Endpoint Settings The Endpoint Settings screens enable you to configure port-specific parameters. 5.5.8.1 Authentication The Authentication Table (normally used with FXS gateways) defines a username and password combination for authentication for each MediaPack port. The ‘Authentication Mode’ parameter (described in Table 5-2) determines if authentication is performed per port or for the entire gateway.
MediaPack SIP 5.5.8.2 Automatic Dialing Use the Automatic Dialing Table to define telephone numbers that are automatically dialed when a specific port is used. ¾ To configure the Automatic Dialing table, take these 6 steps: 1. Open the ‘Automatic Dialing’ screen (Protocol Management menu > Endpoint Settings submenu > Automatic Dialing option); the ‘Automatic Dialing’ screen is displayed. Figure 5-22: Automatic Dialing Table Screen 2.
MediaPack SIP User’s Manual 5.5.8.3 5. Configuring the MediaPack Caller ID Use the Caller Display Information screen to send (to IP) Caller ID information when a call is made using the VoIP gateway (relevant to both FXS and FXO). The person receiving the call can use this information for caller identification. The information on this table is sent in an INVITE message in the ‘From’ header. For information on Caller ID restriction according to destination / source prefixes, refer to Section 5.5.
MediaPack SIP Table 5-22: Caller ID ini File Parameter Parameter Name in ini File Parameter Format CallerDisplayInfoX CallerDisplayInfo = , 0 = Not restricted (default). 1 = Restricted. For example: CallerDisplayInfo0 = Susan C.,0 CallerDisplayInfo2 = Mark M.,1 Note 1: The numbering of channels starts with 0. Note 2: This parameter can appear up to eight times for 8-port gateways, and up to 24 times for MP-124. 5.5.8.
MediaPack SIP User’s Manual 5. 5. Configuring the MediaPack To save the changes so they are available after a power fail, refer to Section 5.9 on page 161. Table 5-23: Authentication ini File Parameter Parameter Name in ini File Parameter Format EnableCallerID_X EnableCallerID_ = Caller ID: 0 = Disabled (default). 1 = Enabled. If not configured, use the global parameter ‘EnableCallerID’. Note 1: The numbering of ports starts with 0.
MediaPack SIP Table 5-24: Call Forward Table Parameter Description Forward Type Not in use [0] = Don’t forward incoming calls (default). On Busy [1] = Forward incoming calls when the gateway port is busy. Immediate [2] = Forward any incoming call to the Phone number specified. No reply [3] = Forward incoming calls that are not answered with the time specified in the ‘Time for No Reply Forward’ field.
MediaPack SIP User’s Manual 5.5.9 5. Configuring the MediaPack Configuring the FXO Parameters Use this screen to configure the gateway’s specific FXO parameters. ¾ To configure the FXO parameters, take these 4 steps: 1. Open the ‘FXO Settings’ screen (Protocol Management menu > FXO Settings > FXO Settings option); the ‘FXO Settings’ screen is displayed. Figure 5-26: FXO Settings Screen 2. Configure the FXO parameters according to Table 5-25. 3. Click the Submit button to save your changes. 4.
MediaPack SIP Table 5-25: FXO Parameters (continues on pages 107 to 109) Parameter Description Waiting For Dial Tone [IsWaitForDialTone] No [0] = Don’t wait for dial tone. Yes [1] = Wait for dial tone (default). Used for IPÆMediaPack/FXO gateways, when ‘One Stage Dialing’ is enabled. If ‘wait for dial tone’ is enabled, the FXO gateway dials the phone number (to the PSTN/PBX line) only after it detects a dial tone.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-25: FXO Parameters (continues on pages 107 to 109) Parameter Description DisconnectOnBusyTone [Disconnect on Busy Tone] No [0] = Call isn’t released (FXO gateway). Yes [1] = Call is released (on FXO gateways) if busy or reorder (fast busy) tones are detected on the gateway’s FXO port (default). 5.5.10 Configuring the Voice Mail (VM) Parameters Use this screen to configure the VM parameters.
MediaPack SIP Table 5-26: Voice Mail Parameters Parameter Description General Voice Mail Interface [VoiceMailInterface] Enables the VM application on the MediaPack and determines the communication method used between the PBX and the gateway. None [0] (default). DTMF [1]. SMDI [2]. Wait For Dial Time N/A. Line Transfer Mode [LineTransferMode] Determines the transfer method used by the gateway. Disable [0] = IP (default). Blind Transfer [1] = PBX blind transfer.
MediaPack SIP User’s Manual 5. Configuring the MediaPack 5.5.11 Protocol Management ini File Parameters Table 5-27 describes the SIP Protocol Management parameters that can only be configured via the ini file. Table 5-27: Protocol Management, ini File Parameters (continues on pages 111 to 113) ini File Parameter Name Valid Range and Description EnablePtime 0 = Remove the ptime header from SDP. 1 = Include the ptime header in SDP (default).
MediaPack SIP Table 5-27: Protocol Management, ini File Parameters (continues on pages 111 to 113) ini File Parameter Name Valid Range and Description MeteringType Defines the metering tone (12 kHz or 16 kHz) that is detected by FXO gateways and generated by FXS gateways. 0 = 12 kHz metering tone (default). 1 = 16 kHz metering tone. Note: Suitable (12 kHz or 16 KHz) coeff file must be used for both FXS and FXO gateways.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-27: Protocol Management, ini File Parameters (continues on pages 111 to 113) ini File Parameter Name Valid Range and Description Serial parameters (applicable only to the VM SMDI application) SerialBaudRate Determines the value of the RS-232 baud rate. The valid range is: any value. It is recommended to use the following standard values: 1200, 2400, 9600 (default), 14400, 19200, 38400, 57600, 115200.
MediaPack SIP 5.6 Advanced Configuration Use this menu to set the gateway’s advanced configuration parameters (for advanced users only). Note: 5.6.1 Those parameters contained within square brackets are the names used to configure the parameters via the ini file. Configuring the Network Settings From the Network Settings you can: 5.6.1.1 • Define the IP Settings (refer to Section 5.6.1.1 below). • Define the Application Settings (refer to Section 5.6.1.2 on page 117).
MediaPack SIP User’s Manual 4. 5. Configuring the MediaPack To save the changes so they are available after a power fail, refer to Section 5.9 on page 161. Table 5-28: Network Settings, IP Settings Parameters (continues on pages 128 to 131) Parameter Description IP Networking Mode [EnableMultipleIPs] Enables / disables the Multiple IPs mechanism. Single IP Network [0] (default). Multiple IP Network [1]. For detailed information on Multiple IPs, refer to Section 9.6 on page 196.
MediaPack SIP Table 5-28: Network Settings, IP Settings Parameters (continues on pages 128 to 131) Parameter Description DHCP Settings Enable DHCP [DHCPEnable] Disable [0] = Disable DHCP support on the gateway (default). Enable [1] = Enable DHCP support on the gateway. After the gateway is powered up, it attempts to communicate with a BootP server.
MediaPack SIP User’s Manual 5.6.1.2 5. Configuring the MediaPack Configuring the Application Settings ¾ To configure the Application Settings parameters, take these 4 steps: 1. Open the ‘Application Settings’ screen (Advanced Configuration menu > Network Settings > Application Settings option); the ‘Application Settings’ screen is displayed. Figure 5-29: Application Settings Screen 2. Configure the Application Settings according to Table 5-29. 3. Click the Submit button to save your changes. 4.
MediaPack SIP Table 5-29: Network Settings, Application Settings Parameters Parameter Description Syslog Settings Syslog Server IP address [SyslogServerIP] IP address (in dotted format notation) of the computer you are using to run the Syslog Server. The Syslog Server is an application designed to collect the logs and error messages generated by the VoIP gateway. Note: The default UDP Syslog port is 514. For information on the Syslog, refer to Section 13.2 on page 222.
MediaPack SIP User’s Manual 5.6.1.3 5. Configuring the MediaPack 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 ‘Application Settings’ screen (Advanced Configuration menu > Network Settings > Application Settings option); the ‘Application Settings’ screen is displayed (Figure 5-29). 2.
MediaPack SIP 5.6.1.4 Configuring the Web and Telnet Access List Use this screen to define up to ten IP addresses that are permitted to access the gateway’s Web and Telnet interfaces. Access from an undefined IP address is denied. This security feature is inactive (the gateway can be accessed from any IP address) when the table is empty. ¾ To manage the Web & Telnet access list, take these 4 steps: 1.
MediaPack SIP User’s Manual 5.6.1.5 5. Configuring the MediaPack Configuring the RTP Settings ¾ To configure the RTP Settings parameters, take these 4 steps: 1. Open the ‘RTP Settings’ screen (Advanced Configuration menu > Network Settings > RTP Settings option); the ‘RTP Settings’ screen is displayed. Figure 5-32: RTP Settings Screen 2. Configure the RTP Settings according to Table 5-32. 3. Click the Submit button to save your changes. 4.
MediaPack SIP Table 5-32: Network Settings, RTP Settings Parameters Parameter Description RTP IP Precedence [IPPrecedence] Value that is assigned to the IP Precedence field in the IP header for all RTP packets sent by the VoIP gateway. The valid range is 0 to 7. The default value is 0. Note: The parameters IPTOS and IPPrecedence mustn’t be used simultaneously with the parameter IPDiffServ. Remote RTP Base UDP Port [RemoteBaseUDPPort] Determines the lower boundary of UDP ports used for RTP, RTCP and T.
MediaPack SIP User’s Manual 5.6.1.6 5. Configuring the MediaPack Configuring the IP Routing Table The IP routing table is used by the gateway to determine IP routing rules. It can be used, for example, to define static routing rules for the OAM and Control networks since a default gateway isn’t supported for these networks (refer to Section 9.6.1 on page 196). Before sending an IP packet, the gateway searches this table for an entry that matches the requested destination host / network.
MediaPack SIP Table 5-33: IP Routing Table Column Description Column Name [ini File Parameter Name] Description The address of the host / network you want to reach is determined by an AND operation that is applied on the fields ‘Destination IP Address’ and ‘Destination Mask’. For example: To reach the network 10.8.x.x, enter 10.8.0.0 in the field ‘Destination IP Address’ and 255.255.0.0 in the field ‘Destination Mask’.
MediaPack SIP User’s Manual 5.6.1.8 5. Configuring the MediaPack Configuring the VLAN Settings For detailed information on the MediaPack VLAN implementaion, refer to Section 9.6 on page 196. ¾ To configure the VLAN Settings parameters, take these 4 steps: 1. Open the ‘VLAN Settings’ screen (Advanced Configuration menu > Network Settings > VLAN Settings option); the ‘VLAN Settings’ screen is displayed. Figure 5-34: VLAN Settings Screen 2. Configure the VLAN Settings according to Table 5-35. 3.
MediaPack SIP Table 5-35: Network Settings, VLAN Settings Parameters Parameter Description VLAN Mode [VlanMode] Sets the VLAN functionality. Disable [0] (default). Enable [1]. PassThrough [2] = N/A. Note: This parameter cannot be changed on-the-fly and requires a gateway reset. IP Settings Native VLAN ID [VlanNativeVlanID] Sets the native VLAN identifier (PVID, Port VLAN ID). The valid range is 1 to 4094. The default value is 1.
MediaPack SIP User’s Manual 5.6.1.9 5. Configuring the MediaPack Configuring the Security Settings (MP-11x Only) Use the Security Settings screen to set the secured Web access parameters (HTTPS) (for detailed information refer to Section 12.1.2 on page 213), and to configure the RADIUS authentication parameters (for detailed information refer to Section 12.2 on page 217). ¾ To configure the Security Settings parameters, take these 4 steps: 1.
MediaPack SIP Table 5-36: Network Settings, Security Settings Parameters Parameter Description RADIUSAuthServerIP [RADIUS Authentication Server IP Address] IP address of the RADIUS authentication server. RADIUSAuthPort [RADIUS Authentication Server Port] Port number of the RADIUS authentication server. The default value is 1645. SharedSecret [RADIUS Shared Secret] ‘Secret’ used to authenticate the gateway to the RADIUS server. Should be a cryptographically strong password. 5.6.1.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-37: Board, ini File Parameters (continues on pages 128 to 131) ini File Parameter Name Valid Range and Description ResetWebPassword Resets the Administrator and Monitoring username and password to their defaults. 0 = Password and username retain their values (default). 1 = Password and username are reset to: Administrator: Default username ‘Admin’. Default password ‘Admin’. Monitoring: Default username ‘User’. Default password ‘User’.
MediaPack SIP Table 5-37: Board, ini File Parameters (continues on pages 128 to 131) ini File Parameter Name RADIUSTo Valid Range and Description Determines the time interval (measured in seconds) the gateway waits for a response before a RADIUS retransmission is issued (MP-11x only). The valid range is 1 to 30. The default value is 10. HTTPS Parameters (MP-11x Only) HTTPSPort Determine the local Secured HTTPS port of the device.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-37: Board, ini File Parameters (continues on pages 128 to 131) ini File 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. ExtBootPReqEnable 0 = Disable (default).
MediaPack SIP 5.6.1.11 Automatic Updates Parameters For detailed information on the automatic update mechanism, refer to Section 10.3 on page 202. Table 5-38: Automatic Updates Parameters ini File Parameter Name Description CmpFileURL Specifies the name of the cmp file and the location of the server (IP address or FQDN) from which the gateway loads a new cmp file and updates itself. The cmp file can be loaded using: TFTP, HTTP or HTTPS (MP-11x only). For example: tftp://192.168.0.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Invokes an immediate restart of the gateway. This option can be used to activate offline (not on-the-fly) parameters that are loaded via IniFileUrl. 0 = The immediate restart mechanism is disabled (default). 1 = The gateway immediately restarts after an ini file with this parameter set to 1 is loaded. ResetNow 5.6.1.12 SNMP ini File Parameters Table 5-39 describes the SNMP parameters that can only be configured via the ini file.
MediaPack SIP 5.6.2 Configuring the Channel Settings From the Channel Settings page you can define: • Voice Settings (refer to Section 5.6.2.1 below). • Fax / Modem / CID Settings (refer to Section 5.6.2.2 on page 136). • RTP Settings (refer to Section 5.6.2.3 on page 139). • Hook-Flash Settings (refer to Section 5.6.2.4 on page 141). These parameters are applied to all MediaPack channels. Note that several Channels Settings parameters can be configured per call using profiles (refer to Section 5.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-40: Channel Settings, Voice Settings Parameters Parameter Description Voice Volume [VoiceVolume] Voice gain control in dB. This parameter sets the level for the transmitted (IPÆTel) signal. The valid range is -32 to 31 dB. The default value is 0 dB. Input Gain [InputGain] PCM input gain control in dB. This parameter sets the level for the received (TelÆIP) signal. The valid range is -32 to 31 dB. The default value is 0 dB.
MediaPack SIP 5.6.2.2 Configuring the Fax / Modem / CID Settings ¾ To configure the Fax / Modem / CID Settings parameters, take these 4 steps: 1. Open the ‘Fax / Modem / CID Settings’ screen (Advanced Configuration menu > Channel Settings > Fax / Modem / CID Settings option); the ‘Fax / Modem / CID Settings’ screen is displayed. Figure 5-37: Fax / Modem / CID Settings Screen 2. Configure the Fax / Modem / CID Settings according to Table 5-41. 3. Click the Submit button to save your changes. 4.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-41: Channel Settings, Fax/Modem/CID Parameters (continues on pages 136 to 138) Parameter Description Caller ID Type [CallerIDType] Defines one of the following standards for detection (FXO) and generation (FXS) of Caller ID and detection (FXO) of MWI (when specified) signals. Bellcore [0] (Caller ID and MWI) (default). ETSI [1] (Caller ID and MWI) NTT [2].
MediaPack SIP Table 5-41: Channel Settings, Fax/Modem/CID Parameters (continues on pages 136 to 138) Parameter Description Fax/Modem Bypass Coder Type [FaxModemBypassCoderType] Coder the gateway uses when performing fax/modem bypass. Usually, high-bitrate coders such as G.711 should be used. You can select: G711 A-law 64 [0] (default). G711 µ-law [1]. G726 32 [4]. G726 40 [11].
MediaPack SIP User’s Manual 5.6.2.3 5. Configuring the MediaPack Configuring the RTP Settings ¾ To configure the RTP Settings parameters, take these 4 steps: 1. Open the ‘RTP Settings’ screen (Advanced Configuration menu > Channel Settings > RTP Settings option); the ‘RTP Settings’ screen is displayed. Figure 5-38: RTP Settings Screen 2. Configure the RTP Settings according to Table 5-42. 3. Click the Submit button to save your changes. 4.
MediaPack SIP Table 5-42: Channel Settings, RTP Parameters Parameter Description Basic RTP Packet Interval [BasicRTPPacketInterval] Note: This parameter should not be used. Use the ‘Coders’ screen under ‘Protocol Definition’ instead. N/A. Controlled internally by the gateway according to the selected coder. RTP Directional Control [RTPDirectionControl] N/A. Controlled internally by the gateway according to the selected coder. RFC 2833 TX Payload Type [RFC2833TxPayloadType] N/A.
MediaPack SIP User’s Manual 5.6.2.4 5. Configuring the MediaPack Configuring the Hook-Flash Settings ¾ To configure the Hook-Flash Settings parameters, take these 4 steps: 1. Open the ‘Hook-Flash Settings’ screen (Advanced Configuration menu > Channel Settings > Hook-Flash Settings option); the ‘Hook-Flash Settings’ screen is displayed. Figure 5-39: Hook-Flash Settings Screen 2. Configure the Hook-Flash Settings according to Table 5-43. 3. Click the Submit button to save your changes. 4.
MediaPack SIP Table 5-44: Channel Settings, ini File Parameters ini File Parameter Name Valid Range and Description MGCPDTMFDetectionP oint 0 = DTMF event is reported on the end of a detected DTMF digit. 1 = DTMF event is reported on the start of a detected DTMF digit (default). DTMFDigitLength Time in msec for generating DTMF tones to the PSTN side (if OutOfBandDTMFFormat = 1 or 2). The default value is 100 msec. The valid range is 0 to 32767.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Table 5-44: Channel Settings, ini File Parameters ini File Parameter Name ETSICallerIDTypeOneS ubStandard Valid Range and Description Selects the ETSI Caller ID Type 1 sub-standard (FXS only). 0 = ETSI between rings (default). 1 = ETSI before ring DT_AS. 2 = ETSI before ring RP_AS. 3 = ETSI before ring LR_DT_AS. 4 = ETSI not ring related DT_AS. 5 = ETSI not ring related RP_AS. 6 = ETSI not ring related LR_DT_AS.
MediaPack SIP 5.6.3 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. The backup ini file includes only those parameters that were modified and contain other than default values.
MediaPack SIP User’s Manual 5.6.4 5. Configuring the MediaPack 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, coefficient (different files for FXS and FXO gateways) and Voice Prompts (currently not applicable to MediaPack gateways). For detailed information on the configuration files, refer to Section 6 on page 163.
MediaPack SIP 5.6.5 Note 1: Saving a configuration file to flash memory may disrupt traffic on the MediaPack. To avoid this, disable all traffic on the device before saving to flash memory. Note 2: A device reset is required to activate a loaded CPT file. 7. To save the loaded auxiliary files so they are available after a power fail, refer to Section 5.9 on page 161. 8. To reset the MediaPack, refer to Section 5.9 on page 161.
MediaPack SIP User’s Manual 5.7 5. Configuring the MediaPack 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. 5.7.1 Gateway Statistics Use the screens under Gateway Statistics to monitor real-time activity such as IP Connectivity information, call details and call statistics, including the number of call attempts, failed calls, fax calls, etc.
MediaPack SIP Table 5-45: IP Connectivity Parameters Column Name Description IP Address IP address defined in the destination IP address field in the Tel to IP Routing table. or IP address that is resolved from the host name defined in the destination IP address field in the Tel to IP Routing table. Host Name Host name (or IP address) defined in the destination IP address field in the Tel to IP Routing table.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Figure 5-44: TelÆIP Call Counters Screen Table 5-46: Call Counters Description (continues on pages 149 to 150) Counter Number of Attempted Calls Description This counter indicates the number of attempted calls. It is composed of established and failed calls. The number of established calls is represented by the ‘Number of Established Calls’ counter. The number of failed calls is represented by the five failed-call counters.
MediaPack SIP Table 5-46: Call Counters Description (continues on pages 149 to 150) Counter Description This counter indicates the number of calls that failed due to mismatched gateway Number of Failed Calls capabilities. It is incremented as a result of an internal identification of capability due to No Matched mismatch.
MediaPack SIP User’s Manual 5.7.2 5. Configuring the MediaPack Monitoring the MediaPack Channels The Channel Status screen provides real time monitoring on the current channels status. ¾ To monitor the status of the MediaPack channels take this step: • Open the ‘Channel Status’ screen (Status & Diagnostics menu > Channel Status); the ‘Channel Status’ screen is displayed (different screen for FXS and FXO).
MediaPack SIP Figure 5-47: Channel Status Details Screen MediaPack SIP User’s Manual 152 Document #: LTRT-65405
MediaPack SIP User’s Manual 5.7.3 5. Configuring the MediaPack 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 13.2 on page 222. Refer to the Debug Level parameter ‘GwDebugLevel’ (described in Table 5-5) to determine the Syslog logging level.
MediaPack SIP 5.7.4 Device Information The Device Information screen displays specific hardware and software product information. This information can help you to expedite any troubleshooting process. Capture the screen and email it to ‘our’ Technical Support personnel to ensure quick diagnosis and effective corrective action. From this screen you can also view and remove any loaded files used by the MediaPack (stored in the RAM).
MediaPack SIP User’s Manual 5.8 5. Configuring the MediaPack Software Update The ‘Software Update’ menu enables users to upgrade the MediaPack 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.8.1 below). • Auxiliary Files (refer to Section 5.8.2 on page 159). Note: 5.8.
MediaPack SIP Note: 3. At this point, the process can be canceled with no consequence to the MediaPack (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 MediaPack reset at the end. If you click the Cancel button in any of the subsequent screens, the MediaPack is automatically reset with the configuration that was previously burned in flash memory.
MediaPack SIP User’s Manual 5. Configuring the MediaPack current configuration files. ¾ Click Cancel; the MediaPack 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-51. ¾ Click Next; the ‘Load an ini File’ screen opens; refer to Figure 5-53.
MediaPack SIP Figure 5-54: 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 MediaPack gateway) screen and ‘Load a coefficient file’ screen. 8. In the ‘FINISH’ screen (refer to Figure 5-55), the Next button is disabled. Complete the upgrade process by clicking Reset or Cancel. Button Result Reset The MediaPack ‘burns’ the newly loaded files to flash memory.
MediaPack SIP User’s Manual 5. Configuring the MediaPack Figure 5-56: ‘End Process’ Screen 9. 5.8.2 Click the End Process button; the ‘Quick Setup’ screen appears and the full Web application is reactivated. Auxiliary Files The ‘Auxiliary Files’ screen enables you to load to the gateway the following files: Call Progress Tones, coefficient and Prerecorded Tones (PRT). The Voice Prompts file is currently not applicable to the MediaPack.
MediaPack SIP Note 1: Saving an auxiliary file to flash memory may disrupt traffic on the MediaPack. To avoid this, disable all traffic on the device before saving to flash memory. Note 2: A MediaPack reset is required to activate a loaded CPT file, and may be required for the activation of certain ini file parameters. 7. To save the loaded auxiliary files so they are available after a power fail, refer to Section 5.9 on page 161. 8. To reset the MediaPack, refer to Section 5.9 on page 161.
MediaPack SIP User’s Manual 5.9 5. Configuring the MediaPack 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.
MediaPack SIP 5.10 Resetting the MediaPack 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 MediaPack, take these 3 steps: 1. Click the Reset button on the main menu bar; the Reset screen is displayed. Figure 5-59: Reset Screen 2. 3. Select one of the following options: ¾ Burn - (default) the current configuration is burned to flash prior to reset.
MediaPack SIP User’s Manual 6 6. ini File Configuration of the MediaPack ini File Configuration of the MediaPack As an alternative to configuring the VoIP gateway using the Web Interface (refer to Section 5 on page 47), 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 257) or via any standard TFTP server. It can also be loaded through the Web Interface (refer to Section 5.6.
MediaPack SIP 6.3 The ini File Structure The ini file can contain any number of parameters. The parameters are divided into groups by their functionality. The general form of the ini file is shown in Figure 6-1 below. Figure 6-1: ini File Structure [Sub Section Name] Parameter_Name = Parameter_Value Parameter_Name = Parameter_Value ; REMARK [Sub Section Name] 6.3.1 6.3.2 The ini File Structure Rules • Lines beginning with a semi-colon ‘;’ (as the first character) are ignored.
MediaPack SIP User’s Manual 7 7. Using BootP / DHCP Using BootP / DHCP The MediaPack uses the Bootstrap Protocol (BootP) and the Dynamic Host Configuration Protocol (DHCP) to obtain its networking parameters and configuration automatically after it is reset. BootP and DHCP are also used to provide the IP address of a TFTP server on the network, and files (cmp and ini) to be loaded into memory. DHCP is a communication protocol that automatically assigns IP addresses from a central point.
MediaPack SIP new network address (since this function is beyond the scope of a VoIP gateway). Therefore, administrators are advised to configure DHCP servers to allow renewal of IP addresses. Note: If the gateway's network cable is disconnected and reconnected, a DHCP renewal is performed (to verify that the gateway is still connected to the same network). When DHCP is enabled, the gateway also includes its product name (e.g., ‘MP-118 FXS’ or ‘MP104 FXO’) in the DHCP ‘option 60’ Vendor Class Identifier.
MediaPack SIP User’s Manual 7.3.2 7. Using BootP / DHCP Vendor Specific Information Field The MediaPack uses the vendor specific information field in the BootP request to provide devicerelated initial startup information. The BootP/TFTP configuration utility displays this information in the ‘Client Info’ column (refer to Figure B-1). Note: This option is not available on DHCP servers. The Vendor Specific Information field is disabled by default.
MediaPack SIP Reader’s Notes MediaPack SIP User’s Manual 168 Document #: LTRT-65405
MediaPack SIP User’s Manual 8. Telephony Capabilities 8 Telephony Capabilities 8.1 Working with Supplementary Services The MediaPack SIP FXS and FXO gateways support the following supplementary services: • Hold / Retrieve; refer to Section 8.1.1. • Consultation / Alternate; refer to Section 8.1.2. • Transfer (Refer + Replaces); refer to Section 8.1.3. • Call Forward (3xx Redirect Responses); refer to Section 8.1.4. • Call Waiting (182 Queued Response); refer to Section 8.1.5.
MediaPack SIP 8.1.3 • While hearing dial tone, or when dialing to the new destination (before dialing is complete) the user can retrieve the held call by pressing hook-flash. • The held call can’t be retrieved while Ringback tone is heard. • After the consultation call is connected, the user can switch between the held and active call by pressing hook-flash.
MediaPack SIP User’s Manual 5. Do Not Disturb 8. Telephony Capabilities - Immediately reject incoming calls. Three forms of forwarding parties are available: 1. Served party – the party that is configured to forward the call – MediaPack/FXS. 2. Originating party – the party that initiated the first call – MediaPack/FXS or FXO. 3. Diverted party – the new destination of the forwarded call – MediaPack/FXS or FXO.
MediaPack SIP To configure MWI set the following parameters: • EnableMWI • MWIServerIP • MWIAnalogLamp • MWIDisplay • StutterToneDuration • EnableMWISubscription • MWIExpirationTime • SubscribeRetryTime • SubscriptionMode • CallerIDType (determines the standard for detection of MWI signals) • ETSIVMWITypeOneStandard • BellcoreVMWITypeOneStandard MediaPack SIP User’s Manual 172 Document #: LTRT-65405
MediaPack SIP User’s Manual 8.2 8. Telephony Capabilities 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.
MediaPack 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 LBR coders the quality of the DTMF digits is reduced.
MediaPack SIP User’s Manual 8. Telephony Capabilities Table 8-1: Summary of DTMF configuration Parameters (continues on pages 174 to 175) ini File Field Name [Web Name] RxDTMFOption [Declare RFC 2833 in SDP] Valid Range and Description Defines the supported Receive DTMF negotiation method. No [0] = Don’t declare RFC 2833 Telephony-event parameter in SDP Yes [3] = Declare RFC 2833 Telephony-event parameter in SDP (default) The MediaPack is designed to always be receptive to RFC 2833 DTMF relay packets.
MediaPack SIP 8.3 Fax & Modem Transport Modes 8.3.1 Fax/Modem Settings Users may choose to use one of the following transport methods for fax and for each modem type (V.22/V.23/Bell/V.32/V.34): • Fax relay demodulation / modulation • Bypass using a high bit rate coder to pass the signal • Transparent passing the signal in the current voice coder When the fax relay mode is enabled, distinction between fax and modem is not immediately possible at the beginning of a session.
MediaPack SIP User’s Manual 8.3.4 8. Telephony Capabilities Supporting V.34 Faxes V.34 faxes don’t comply with the T.38 relay standard. We therefore provide the optional modes described under Sections 8.3.4.1 and 8.3.4.2: Note that the CNG detector is disabled (CNGDetectorMode=0) in all the following examples. 8.3.4.1 Using Bypass Mechanism for V.34 Fax Transmission In this proprietary scenario, the media gateway uses a high bit-rate coder to transmit V.
MediaPack SIP 8.5 • Detection of Reorder / Busy tones The call is immediately disconnected after Reorder / Busy tone is detected on the Tel side (assuming the PBX / CO produces this tone). This method requires the correct tone frequencies and cadence to be defined in the Call Progress Tones file. If these frequencies are not known, define them in the CPT file (the tone produced by the PBX / CO must be recorded and its frequencies analyzed). This method is slightly less reliable than the previous one.
MediaPack SIP User’s Manual 8. Telephony Capabilities perceived voice quality. To minimize this problem, the gateway uses a jitter buffer. The jitter buffer collects voice packets, stores them and sends them to the voice processor in evenly spaced intervals. The MediaPack uses a dynamic jitter buffer that can be configured using two parameters: • Minimum delay, ‘DJBufMinDelay’ (0 msec to 150 msec). Defines the starting jitter capacity of the buffer.
MediaPack SIP is found; the prefix’s corresponding destination IP address is checked. If the destination IP address is disallowed, an alternative route is searched for in the following table entries. Destination IP address is disallowed if no ping to the destination is available (ping is continuously initiated every 7 seconds), when an inappropriate level of QoS was detected, or when DNS host name is not resolved. The QoS level is calculated according to delay or packet loss of previously ended calls.
MediaPack SIP User’s Manual 8.9 8. Telephony Capabilities 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-2: Supported CDR Fields Version 4.
MediaPack SIP 8.10 Proxy or Registrar Registration Example The REGISTER message is sent to the Registrar’s IP address (if configured) or to the Proxy’s IP address. The message is sent per gateway or per gateway endpoint according to the ‘AuthenticationMode’ parameter. Usually the FXS gateways are registered per gateway port, while FXO gateways send a single registration message, where Username is used instead of phone number in From/To headers.
MediaPack SIP User’s Manual 8. Telephony Capabilities 8.11 Configuration Examples 8.11.1 Establishing a Call between Two Gateways After you’ve installed and set up the MediaPack, you can ensure that it functions as expected by establishing a call between it and another gateway. This section exemplifies how to configure two 8-port MediaPack FXS SIP gateways in order to establish a call.
MediaPack SIP 8.11.2 SIP Call Flow The following Call Flow describes SIP messages exchanged between two MediaPack gateways during simple call. Phone ‘6000’ dials ‘2000’, sending INVITE message to Gateway 10.8.201.161 Figure 8-1: SIP Call Flow 10.8.201.158 10.8.201.161 INVITE F1 Ringing F2 200 OK F3 ACK F4 BYE F5 200 OK F6 F1 10.8.201.158 ==> 10.8.201.161 INVITE INVITE sip:6000@10.8.201.161;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.201.158;branch=z9hG4bKacolwbzYF From:
MediaPack SIP User’s Manual 8. Telephony Capabilities F2 10.8.201.161 ==> 10.8.201.158 180 RINGING SIP/2.0 180 Ringing Via: SIP/2.0/UDP 10.8.201.158;branch=z9hG4bKacolwbzYF From: ;tag=1c3535 To: ;tag=1c29715 Call-ID: 2123353775377NrpL-2000--6000@10.8.201.158 Server: Audiocodes-Sip-Gateway/MP-108 FXS/v.4.20.299.410 CSeq: 20214 INVITE Supported: 100rel,em Content-Length: 0 Note: Phone ‘2000’ answers the call, and sends 200 OK message to gateway 10.8.201.158.
MediaPack SIP F5 10.8.201.161 ==> 10.8.201.158 BYE BYE sip:2000@10.8.201.158;user=phone;user=phone SIP/2.0 Via: SIP/2.0/UDP 10.8.201.161;branch=z9hG4bKacLBzZgmA From: ;tag=1c29715 To: ;tag=1c3535 Call-ID: 2123353775377NrpL-2000--6000@10.8.201.158 User-Agent: Audiocodes-Sip-Gateway/MP-108 FXS/v.4.20.299.410 CSeq: 34541 BYE Supported: 100rel,em Content-Length: 0 F6 10.8.201.158 ==> 10.8.201.161 200 OK SIP/2.0 200 OK Via: SIP/2.0/UDP 10.8.201.
MediaPack SIP User’s Manual 8. Telephony Capabilities 8.11.3 SIP Authentication Example MediaPack gateways support basic and digest (MD5) 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.
MediaPack SIP The method type ‘REGISTER’ 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’. The MD5 algorithm is run on this equation.
MediaPack SIP User’s Manual 8. Telephony Capabilities 8.11.4 Remote IP Extension between FXO and FXS This application explains how to implement remote extension via IP, using 8-port FXO and 8-port FXS MediaPack gateways. In this configuration, PBX incoming calls are routed to the ‘Remote Extension’ via the FXO and FXS gateways. Requirements: • One FXO MediaPack gateway • One FXS MediaPack gateway • Analog phones (POTS) • PBX – one or more PBX loop start lines • LAN.
MediaPack SIP 8.11.4.2 Dialing from other PBX line, or from PSTN ¾ To configure the call, take these 5 steps: 1. Dial the PBX subscriber number the same way as if the user’s phone was connected directly to PBX. 2. Immediately as PBX rings into FXO MediaPack, the ring signal is ‘send’ to phone connected to FXS MediaPack. 3. Once the phone’s handset, connected to FXS MediaPack, is raised, the FXO MediaPack seizes the PBX line and the voice path is established between the phone and the PBX line. 4.
MediaPack SIP User’s Manual 8. Telephony Capabilities 8.11.4.4 FXO MediaPack Configuration (using the Embedded Web Server) ¾ To configure the FXO MediaPack, take these 4 steps: 1. In the ‘Endpoint Phone Numbers’ screen, assign the phone numbers 200 to 207 for the gateway’s endpoints. 2. In the ‘Automatic Dialing’ screen, enter the phone numbers of the FXS MediaPack gateway in the ‘Destination Phone Number’ fields.
MediaPack SIP Reader's Notes MediaPack SIP User’s Manual 192 Document #: LTRT-65405
MediaPack SIP User’s Manual 9. Networking Capabilities 9 Networking Capabilities 9.1 Ethernet Interface Configuration Using the parameter ‘EthernetPhyConfiguration‘, users can control the Ethernet connection mode. Either the manual modes (10 Base-T Half-Duplex, 10 Base-T Full-Duplex, 100 Base-TX HalfDuplex, 100 Base-TX Full-Duplex) or Auto-Negotiate mode can be used.
MediaPack SIP The RTP, RTCP and T.38 can thus have independent destination IP addresses and UDP ports. Users can choose to disable the NAT mechanism by setting the ini file parameter ‘DisableNAT’ to 1. The two parameters ‘EnableIpAddrTranslation’ and ‘EnableUdpPortTranslation’ enable users to specify the type of compare operation that takes place on the first incoming packet. To compare only the IP address, set ‘EnableIpAddrTranslation = 1’ and ‘EnableUdpPortTranslation = 0’.
MediaPack SIP User’s Manual 9. Networking Capabilities restarted. The NTP server identity (as an IP address) and the update interval are configurable parameters that can be specified either in the ini file (NTPServerIP, NTPUpdateInterval respectively) or via an SNMP MIB object.
MediaPack SIP 9.6 VLANS and Multiple IPs 9.6.1 Multiple IPs Media, Control and Management (OAM) traffic in the MediaPack can be separated into three dedicated networks. Instead of a single IP address, the MediaPack can be assigned three IP addresses and subnet masks, each relates to a different traffic type. This architecture enables users to integrate the MediaPack into a three-network environment that is focused on security and segregation. Each entity in the MediaPack (e.g.
MediaPack SIP User’s Manual 9. Networking Capabilities For information on how to configure VLAN parameters, refer to Section 5.6.1.8 on page 125.
MediaPack SIP Table 9-2: Example of VLAN and Multiple IPs Configuration Network Type IP Address Subnet Mask Default Gateway IP Address VLAN ID External Routing Rule OAM 10.31.174.50 255.255.0.0 0.0.0.0 4 83.4.87.X Control 10.32.174.50 255.255.0.0 0.0.0.0 5 130.33.4.6 Media 10.33.174.50 255.255.0.0 10.33.0.
MediaPack SIP User’s Manual Note: 9. Networking Capabilities Configure the OAM parameters only if the OAM networking parameters are different from the networking parameters used in the Single IP Network mode. Figure 9-3: Example of the IP Settings Screen ¾ 5. Click the Submit button to save your changes.
MediaPack SIP ¾ 9.6.3.2 Click the Submit button to save your changes. 6. Save your changes to flash so they are available after a power fail, refer to Section 5.9 on page 161. 7. Reset the gateway. Click the Reset button on the main menu bar; the Reset screen is displayed. Click the button Reset. Integrating Using the ini File ¾ To integrate the MediaPack into a VLAN and multiple IPs network using the ini file, take these 3 steps: 1.
MediaPack SIP User’s Manual 10 10. Advanced System Capabilities Advanced System Capabilities 10.1 Restoring Networking Parameters to their Initial State You can use the ‘Reset’ button to restore the MediaPack networking parameters to their factory default values (described in Table 4-1) and to reset the username and password. Note that the MediaPack returns to the software version burned in flash. This process also restores the MediaPack parameters to their factory settings.
MediaPack SIP 2. Use a serial communication software (e.g., HyperTerminalTM) with the following communications port settings: ¾ Baud Rate: 115,200 bps (MP-1xx), 9,600 bps (MP-11x) ¾ Data bits: 8 ¾ Parity: None ¾ Stop bits: 1 ¾ Flow control: Hardware Note that after resetting the gateway, the information, shown in Figure 11-1 below, appears on the terminal screen.
MediaPack SIP User’s Manual 10. Advanced System Capabilities Figure 10-2: Example of an ini File Activating the Automatic Update Mechanism # DNS is required for specifying domain names in URLs DnsPriServerIP = 10.1.1.11 # Load an extra configuration ini file using HTTP IniFileURL = 'http://webserver.corp.com/AudioCodes/inifile.ini' # Load Call Progress Tones file using HTTPS # Note: HTTPS is not available on the MP-1xx CptFileUrl = 'https://10.31.2.17/usa_tones.
MediaPack SIP You can modify the master_configuration.ini file (or any of the config_.ini files) at any time. The MediaPack queries for the latest version every 60 minutes and applies the new settings immediately. 10.4 Startup Process The startup process (illustrated in Figure 10-3 on page 205) begins when the gateway is reset (physically or from the Web / SNMP) and ends when the operational software is running.
MediaPack SIP User’s Manual 10.
MediaPack SIP 10.5 Customizing the MediaPack Web Interface Customers incorporating the MediaPack into their portfolios can customize the Web Interface to suit their specific corporate logo and product naming conventions. Customers can customize the Web Interface’s title bar (AudioCodes’ title bar is shown in Figure 10-4; a customized title bar is shown in Figure 10-6).
MediaPack SIP User’s Manual 10. Advanced System Capabilities Figure 10-6: 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. Click the Send File button; the file is sent to the device. When loading is complete, the screen is automatically refreshed and the new logo image is displayed. 5. Note the appearance of the logo.
MediaPack SIP Table 10-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. The default value is 339, which is the width of AudioCodes’ displayed logo. 10.5.1.
MediaPack SIP User’s Manual 6. 10. Advanced System Capabilities To save the image to flash memory so it is available after a power fail, refer to Section 5.9 on page 161. 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.
MediaPack SIP 10.5.4 Modifying ini File Parameters via the Web AdminPage ¾ To modify ini file parameters via the AdminPage, take these 6 steps: 1. Access the MediaPack Embedded Web Server (refer to Section 5.3 on page 48). 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 the INI Parameters option, the INI Parameters screen is displayed (shown in Figure 10-7). Figure 10-7: INI Parameters Screen 4.
MediaPack SIP User’s Manual 11 11. Special Applications Special Applications 11.1 Metering Tones Relay The MediaPack FXS and FXO gateways can be used to relay standard 12 or 16 kHz metering tones over the IP network as illustrated in Figure 11-1 below. Figure 11-1: Metering Tone Relay Architecture After a call is established between the FXS and FXO gateways, the PSTN generates 12 or 16 kHz metering tones towards the FXO gateway.
MediaPack SIP Reader’s Notes MediaPack SIP User’s Manual 212 Document #: LTRT-65405
MediaPack SIP User’s Manual 12 12. Security (MP-11x Only) Security (MP-11x Only) This section describes the security mechanisms and protocols implemented on the MP-11x. The following list specifies the available security protocols and their objectives: • SSL (Secure Socket Layer) / TLS (Transport Layer Security) – The SSL / TLS protocols are used to provide privacy and data integrity between two communicating applications over TCP/IP.
MediaPack SIP 12.1.2.1 Using the Secured Embedded Web Server ¾ To use the secured Embedded Web Server, take these 3 Steps: 1. Access the MP-11x using the following URL: https://[host name] or [IP address] Depending on the browser's configuration, a security warning dialog may be displayed. The reason for the warning is that the MP-11x initial certificate is not trusted by your PC.
MediaPack SIP User’s Manual 12. Security (MP-11x Only) Figure 12-2: Certificate Signing Request Screen 3. In the Subject Name field, enter the DNS name and click Generate CSR. A textual certificate signing request, that contains the SSL device identifier, is displayed. 4. Copy this text and send it to your security provider; the security provider (also known as Certification Authority or CA) signs this request and send you a server certificate for the device. 5. Save the certificate in a file (e.g.
MediaPack SIP Note 1: The certificate replacement process can be repeated when necessary (e.g., the new certificate expires). Note 2: It is possible to use the IP address of the MP-11x (e.g., 10.3.3.1) instead of a qualified DNS name in the Subject Name. This practice is not recommended since the IP address is subject to changes and may not uniquely identify the device. Note 3: The server certificate can also be loaded via ini file using the parameter ‘HTTPSCertFileName’. 12.1.
MediaPack SIP User’s Manual 12. Security (MP-11x Only) 12.2 RADIUS Login Authentication (MP-11x Only) Users can enhance the security and capabilities of logging to the gateway’s Web and Telnet embedded servers by using a Remote Authentication Dial-In User Service (RADIUS) to store numerous usernames and passwords, allowing multiple user management on a centralized platform.
MediaPack SIP 3. Record and retain the IP address, port number and ’shared secret’ used by the RADIUS server. 4. Configure the MP-11x relevant parameters according to Section 12.2.2 below. 12.2.2 Configuring RADIUS Support For information on the RADIUS parameters, refer to Table 5-36 on page 127. ¾ To configure RADIUS support on the MP-11x via the Embedded Web Server, take these 8 steps: 1. Access the Embedded Web Server (refer to Section 5.3 on page 48). 2.
MediaPack SIP User’s Manual 12. Security (MP-11x Only) 12.3 Network Port Usage The following table lists the default TCP/UDP network port numbers used by the MediaPack. Where relevant, the table lists the ini file parameters that control the port usage and provide source IP address filtering capabilities. Table 12-1: Default TCP/UDP Network Port Numbers Port Number Peer Port Application Notes 2 2 Debugging interface Always ignored 23 - Telnet Disabled by default (TelnetServerEnable).
MediaPack SIP • If the number of users that access the Web and Telnet interfaces is limited, you can use the ‘Web and Telnet Access List’ to define up to ten IP addresses that are permitted to access these interfaces. Access from an undefined IP address is denied (refer to Section 5.6.1.4 on page 120). • Use HTTPS when accessing the Web interface. Set HTTPSOnly to 1 to allow only HTTPS traffic (and block port 80). If you don't need the Web interface, disable the Web server (DisableWebTask).
MediaPack SIP User’s Manual 13 13. Diagnostics Diagnostics Several diagnostic tools are provided, enabling you to identify correct functioning of the MediaPack, or an error condition with a probable cause and a solution or workaround. • Front and rear panel indicator LEDs on the MediaPack. The location and functionality of the MP-1xx front panel LEDs is shown in Section 2.1.1.2 on page 24. The location and functionality of the MP-1xx rear panel LEDs is shown in Sections 2.1.2 and 25.
MediaPack SIP 13.2 Syslog Support Syslog protocol is an event notification protocol that enables a machine to send event notification messages across IP networks to event message collectors -also known as Syslog servers. Syslog protocol is defined in the IETF RFC 3164 standard. Since each process, application and operating system was written independently, there is little uniformity to Syslog messages.
MediaPack SIP User’s Manual 14 14. Embedded Command Line Interface Embedded Command Line Interface An embedded Command Line Interface (CLI) is available on the MediaPack. The CLI (or CommandShell) can be accessed via Telnet, RS-232 and the Embedded Web Server. You can use the CLI for diagnostics and basic configuration, such as to modify most of the ini file parameters and to change the network settings (IP address, subnet mask and default gateway IP address) of the gateway (refer to Section 14.2.
MediaPack SIP 14.2 Using the CLI The CLI commands are organized in folders. When first entering CLI, the user prompt is located at the root folder. Each time a command is executed, the CLI lists the current folder’s available commands and sub-folders. Before using the CLI, refer to the following notes: • Enter ‘h’ at the CLI prompt for help on global commands and enter ‘h ’ for information on a specific command. • Use two consecutive dots (i.e., ‘..’) to access a higher directory level.
MediaPack SIP User’s Manual 14. Embedded Command Line Interface 14.2.1 Changing the Networking Parameters You can use the CLI to change the network settings (IP address, subnet mask and default gateway IP address) of the MediaPack. ¾ To change the network settings via the CLI, take these 4 steps: 1. At the prompt type ‘conf’ and press enter; the configuration folder is accessed. 2.
MediaPack SIP Reader's Notes MediaPack SIP User’s Manual 226 Document #: LTRT-65405
MediaPack SIP User’s Manual 15 15. 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).
MediaPack 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.
MediaPack SIP User’s Manual 15. SNMP-Based Management 15.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.
MediaPack SIP • The enterprise acBoardEvBoardStarted which is generated at the end of system initialization. This is more of an ‘application-level’ cold start sent after the entire initializing process is complete and all the modules are ready. 15.4 Third-Party Performance Monitoring Measurements Performance measurements are available for a third-party performance monitoring system through an SNMP interface.
MediaPack SIP User’s Manual 15. SNMP-Based Management 15.5 Supported MIBs The MediaPack contains an embedded SNMP Agent supporting the following MIBs: • Standard MIB (MIB-2) - The various SNMP values in the standard MIB are defined in RFC 1213. The standard MIB includes various objects to measure and monitor IP activity, TCP activity, UDP activity, IP routes, TCP connections, interfaces and general system indicators. • RTP MIB - The RTP MIB is supported in conformance with the IETF RFC 2959.
MediaPack SIP Other proprietary MIBs are: • acGateway MIB - This proprietary MIB contains objects related to configuration of the device when applied as a SIP or H.323 media gateway only. This MIB complements the other proprietary MIBs. The acGateway MIB has the following groups: • ¾ Common - for parameters common to both SIP and H.323 ¾ SIP - for SIP parameters only ¾ H.323 - for H.323 parameters only acAlarm - This is a proprietary carrier-grade alarm MIB.
MediaPack SIP User’s Manual 15. SNMP-Based Management The following proprietary traps are supported. For detailed information on these traps, refer to Appendix E on page 281: • acBoardFatalError - Sent whenever a fatal device error occurs. • acBoardEvResettingBoard - Sent after the device is reset. • acBoardEvBoardStarted - Sent after the device is successfully restored and initialized following reset.
MediaPack SIP snmpTargetMIB. ¾ To add a read-only community string (v2user): • Add a new row to the srCommunityTable with CommunityName v2user and GroupName ReadGroup. ¾ To delete the read-only community string (v2user), take these 2 steps: 1. If v2user is being used as the trap community string, follow the procedure for changing the trap community string (see below). 2. Delete the srCommunityTable row with CommunityName v2user.
MediaPack SIP User’s Manual 15. SNMP-Based Management 15.7.2 Trusted Managers By default, the agent accepts ‘get’ and ‘set’ requests from any IP address, as long as the correct community string is used in the request. Security can be enhanced via the use of Trusted Managers. A Trusted Manager is an IP address from which the SNMP Agent accepts and processes ‘get’ and ‘set’ requests. An EM can be used to configure up to 5 Trusted Managers.
MediaPack SIP srCommunityTable are currently set to MGR. This procedure must be performed from one of the existing trusted managers, but not the one that is being deleted. • Remove the appropriate row from the snmpTargetAddrTable. The change takes effect immediately. The deleted trusted manager cannot access the device. The agent automatically removes the row in the tgtAddressMaskTable.
MediaPack SIP User’s Manual 15. SNMP-Based Management 15.7.4.2 Trap Managers Configuration via the ini File In the MediaPack ini file, the parameters below can be set to enable or disable the sending of SNMP traps. Multiple trap destinations can be supported on the device by setting multiple trap destinations in the ini file. SNMPManagerTrapSendingEnable_ = 0 or 1 indicates if traps are to be sent to the specified SNMP trap manager.
MediaPack SIP acBoard MIB (is going to be removed in the following version). The second, via the standard snmpTargetMIB. Using the acBoard MIB: The following parameters (that are defined in the snmpManagersTable) are available: 1. snmpTrapManagerSending 2. snmpManagerIsUsed 3. snmpManagerTrapPort 4. snmpManagerIP When snmpManagerIsUsed is set to zero (not used), the other three parameters are set to zero as well.
MediaPack SIP User’s Manual 15. SNMP-Based Management ¾ 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’. 15.8 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.
MediaPack SIP Reader's Notes MediaPack SIP User’s Manual 240 Document #: LTRT-65405
MediaPack SIP User’s Manual 16 16. Configuration Files Configuration Files This section describes the configuration dat files that are loaded (in addition to the ini file) to the gateway. The configuration files are: • Call Progress Tones file (refer to Section 16.1 on page 241). • Prerecorded Tones file (refer to Section 16.2 on page 246). • FXS/FXO Coefficient files (refer to Section 16.3 on page 247).
MediaPack SIP Users can specify several tones of the same type. These additional tones are used only for tone detection. Generation of a specific tone conforms to the first definition of the specific tone. For example, users can define an additional dial tone by appending the second dial tone’s definition lines to the first tone definition in the ini file. The MediaPack reports dial tone detection if either of the two tones is detected.
MediaPack SIP User’s Manual 16. Configuration Files ¾ First Signal Off Time [10 msec] – ‘Signal Off’ period (in 10 msec units) for the first cadence on-off cycle (for cadence tones). For burst tones, this parameter defines the off time required after the burst tone ends and the tone detection is reported. For continuous tones, this parameter is ignored. ¾ Second Signal On Time [10 msec] – ‘Signal On’ period (in 10 msec units) for the second cadence on-off cycle.
MediaPack SIP In the following examples, the MediaPack plays the Ringing tone with ‘Ringing Pattern’ equals 2. If the number of the ‘Ringing Pattern’ isn’t found, the default Ringing tone (0) is played. Alert-Info: Alert-Info: http://127.0.0.1/Bellcore-dr2 Each ringing pattern configures the ringing tone frequency and up to 4 ringing cadences. The same ringing frequency is used for all the ringing pattern cadences.
MediaPack SIP User’s Manual 16. Configuration Files 16.1.2.
MediaPack SIP 16.2 Prerecorded Tones (PRT) File The Call Progress Tones mechanism has several limitations, such as a limited number of predefined tones and a limited number of frequency integrations in one tone. To work around these limitations and provide tone generation capability that is more flexible, the PRT file can be used. If a specific prerecorded tone exists in the PRT file, it takes precedence over the same tone that exists in the CPT file and is played instead of it.
MediaPack SIP User’s Manual 16. Configuration Files 16.3 The Coefficient Configuration File The Coeff_FXS.dat and Coeff_FXO.dat files are used to provide best termination and transmission quality adaptation for different line types for FXS and FXO gateways respectively. This adaptation is performed by modifying the telephony interface characteristics (such as DC and AC impedance, feeding current and ringing voltage). The coeff.
MediaPack SIP Reader’s Notes MediaPack SIP User’s Manual 248 Document #: LTRT-65405
MediaPack SIP User’s Manual 17 17. Selected Technical Specifications Selected Technical Specifications 17.1 MP-1xx Specifications Table 17-1: MP-1xx Selected Technical Specifications (continues on pages 249 to 251) MP-1xx/FXS Functionality FXS Capabilities Short or Long Haul: MP-10x/FXS: Up to 7 km (23,000 feet) using 24 AWG line. MP-124/FXS: Up to 6 km (20,000 feet) using 24 AWG line.
MediaPack SIP Table 17-1: MP-1xx Selected Technical Specifications (continues on pages 249 to 251) Fax and Modem Transport Modes Real time Fax Relay Group 3 real-time fax relay up to 14400 bps with auto fallback Tolerant network delay (up to 9 seconds round trip delay) T.30 (PSTN) and T.38 (IP) compliant (real-time fax) CNG tone detection & Relay per T.38 Answer tone (CED or AnsAm) detection & Relay per T.38 Fax Transparency Automatic fax bypass (pass-through) to G.
MediaPack SIP User’s Manual 17. Selected Technical Specifications Table 17-1: MP-1xx Selected Technical Specifications (continues on pages 249 to 251) Installation Desk-top, shelf, or 19-inch rack mount with side brackets. Electrical Maximum operating voltage range 90-264 VAC Nominal operating voltage range 100-250 VAC, 0.
MediaPack SIP Table 17-2: MP-11x Functional Specifications (continues on pages 251 to 253) Voice & Tone Characteristics Voice Compression G.711 PCM at 64 kbps µ-law/A-law G.723.1 MP-MLQ at 5.3 or 6.3 kbps G.726 at 32 kbps ADPCM G.729 CS-ACELP 8 Kbps Annex A / B (10, 20, 30, 40, 50, 60, 80, 100, 120 msec) (30, 60, 90 msec) (10, 20, 30, 40, 50, 60, 80, 100, 120 msec) (10, 20, 30, 40, 50, 60 msec) Silence Suppression G.723.1 Annex A G.
MediaPack SIP User’s Manual 17. Selected Technical Specifications Table 17-2: MP-11x Functional Specifications (continues on pages 251 to 253) Reset Button Resets the MP-11x Physical Dimensions (HxWxD) 42 x 172 x 220 mm Environmental Operational: Storage: Humidity: Mounting Rack mount, Desktop, Wall mount.
MediaPack SIP Reader’s Notes MediaPack SIP User’s Manual 254 Document #: LTRT-65405
MediaPack SIP User’s Manual A. MediaPack SIP Software Kit Appendix A MediaPack SIP Software Kit Table A-1 describes the standard supplied software kit for MediaPack FXS/FXO SIP gateways. The supplied documentation includes this User’s Manual, the MediaPack Fast Track and the MediaPack SIP Release Notes. Table A-1: MediaPack SIP Supplied Software Kit File Name Description Ram.cmp files MP124_SIP_xxx.cmp Image file containing the software for the MP-124/FXS gateway. MP108_SIP_xxx.
MediaPack SIP Reader’s Notes MediaPack SIP User’s Manual 256 Document #: LTRT-65405
MediaPack 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.
MediaPack SIP B.4 B.5 • 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.
MediaPack 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.
MediaPack 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.
MediaPack 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.
MediaPack 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.
MediaPack 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.
MediaPack 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.
MediaPack 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.
MediaPack SIP 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. Type in the switch you require. Example: ‘ramxxx.cmp –fb’ to burn flash memory. ‘ramxxx.cmp -fb -em 4’ to burn flash memory and for Ethernet Mode 4 (auto-negotiate).
MediaPack 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.
MediaPack SIP Reader’s Notes MediaPack SIP User’s Manual 268 Document #: LTRT-65405
MediaPack 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 3550 and RFC 3551. We have added new payload types to enable advanced use of other coder types. These types are reportedly not used by other applications. C.1 Packet Types Defined in RFC 3551 Table C-1: Packet Types Defined in RFC 3551 C.2 Payload Type Description Basic Packet Rate [msec] 0 2 4 8 18 200 G.711 µ-Law G.726-32 G.723 (6.
MediaPack SIP C.3 Default RTP/RTCP/T.38 Port Allocation The following table shows the default RTP/RTCP/T.38 port allocation. Table C-3: Default RTP/RTCP/T.38 Port Allocation Channel Number RTP Port RTCP Port T.
MediaPack SIP User’s Manual D. Accessory Programs and Tools Appendix D Accessory Programs and Tools The accessory applications and tools shipped with the device provide you with friendly interfaces that enhance device usability and smooth your transition to the new VoIP infrastructure. The following applications are available: D.1 • TrunkPack Downloadable Conversion Utility (refer to Section D.1 below). • Call Progress Tones Wizard (refer to Section D.1.3 on page 274).
MediaPack SIP D.1.1 Converting a CPT ini File to a Binary dat File For detailed information on creating a CPT ini file, refer to Section 16.1 on page 241. ¾ 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 D-1). 2.
MediaPack SIP User’s Manual D.1.2 D. Accessory Programs and Tools Encoding / Decoding an ini File For detailed information on secured ini file, refer to Section 6.1 on page 163. ¾ 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 D-1). 2.
MediaPack SIP D.1.3 Creating a Loadable Prerecorded Tones File For detailed information on the PRT file, refer to Section 16.2 on page 246. ¾ 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.
MediaPack SIP User’s Manual ¾ 5. D. Accessory Programs and Tools Click the Add File(s) button; the ‘Select Files’ screen opens. Select the required Prerecorded Tone files and press the Add>> button. Close the ‘Select Files’ screen. For each raw data file, define a Tone Type, a Coder and a Default Duration by completing the following steps: ¾ Double-click or right-click the required file; the ‘File Data’ window (shown in Figure D-5) appears.
MediaPack SIP D.2 Call Progress Tones Wizard This section describes the Call Progress Tones Wizard (CPTWizard), an application designed to facilitate the provisioning of an MediaPack/FXO gateway by recording and analyzing Call Progress Tones generated by any PBX or telephone network. D.2.
MediaPack SIP User’s Manual 3. Select the gateway’s ports that are connected to your PBX, and specify the phone number of each extension. 4. In the Invalid phone number field, enter a number that generates a ‘fast busy’ tone when dialed. Usually, any incorrect phone number should cause a ‘fast busy’ tone. 5. Press Next. Note: D.2.4 D. Accessory Programs and Tools The CPTWizard communicates with the FXO gateway via TPNCP (TrunkPack Network Control Protocol).
MediaPack SIP 5. The wizard then analyzes the recorded Call Progress Tones and displays a message specifying the tones that were detected (by the gateway) and analyzed (by the wizard) correctly. At the end of a successful detection operation, the detected Call Progress Tones are displayed in the Tones Analyzed pane (refer to Figure D-8). Figure D-8: Recording Screen after Automatic Detection 6.
MediaPack SIP User’s Manual D.2.5 D. Accessory Programs and Tools Recording Screen – Manual Mode In manual mode you can record and analyze tones, included in the Call Progress Tones ini file, in addition to those tones analyzed when in automatic mode. ¾ To start recording in manual mode, take these 6 steps: 1. Press the Manual tab at the top of the recording screen, the manual recording screen is displayed. Figure D-9: Recording Screen - Manual Mode 2.
MediaPack SIP Figure D-10: Call Progress Tone Properties [CALL PROGRESS TONE #1] Tone Type=1 Low Freq [Hz]=350 High Freq [Hz]=440 Low Freq Level [-dBm]=0 High Freq Level [-dBm]=0 First Signal On Time [10msec]=0 First Signal Off Time [10msec]=0 Second Signal On Time [10msec]=0 Second Signal Off Time [10msec]=0 • Information related to possible matches of each tone with the CPTWizard’s internal database of well-known tones.
MediaPack SIP User’s Manual E. SNMP Traps Appendix E SNMP Traps This section provides information on proprietary SNMP traps currently supported by the gateway. There is a separation between traps that are alarms and traps that are not (logs). Currently all have the same structure made up of the same 11 varbinds (Variable Binding) (1.3.6.1.4.1.5003.9.10.1.21.1).
MediaPack SIP Table E-2: acBoardEvResettingBoard Alarm Trap Alarm Text: User resetting board Status Changes: Condition: When a soft reset is triggered via the Web interface or SNMP. Alarm status: Critical Condition: After raise Alarm status: Status stays critical until reboot. A clear trap is not sent. Corrective Action: A network administrator has taken action to reset the device. No corrective action is required.
MediaPack SIP User’s Manual E. SNMP Traps Table E-5: acBoardOverloadAlarm Alarm Trap Alarm: acBoardOverloadAlarm OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.11 Default Severity Major Event Type: processingErrorAlarm Probable Cause: softwareError (46) Alarm Text: Board overload alarm Status Changes: Condition: An overload condition exists in one or more of the system components. Alarm Status: Major Condition: The overload condition passed Alarm Status: Cleared E.1.
MediaPack SIP Table E-7: acBoardEthernetLinkAlarm Alarm Trap Event Type: equipmentAlarm Probable Cause: underlyingResourceUnavailable (56) Alarm Text: Ethernet link alarm: Status Changes: Condition: Fault on single interface Alarm status: major value: Redundant link is down Condition: Fault on both interfaces Alarm status: critical value: No Ethernet link Condition: Both interfaces are operational Alarm status: cleared Corrective Action: Ensure that both Ethernet
MediaPack SIP User’s Manual E.1.5 E. SNMP Traps Other Traps The following are provided as SNMP traps and are not alarms. Table E-9: 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 E-10: authenticationFailure Trap authenticationFailure Trap Name: OID: 1.3.6.1.6.3.1.1.5.5 MIB SNMPv2-MIB Table E-11: acBoardEvBoardStarted Trap Trap Name: acBoardEvBoardStarted OID: 1.3.6.1.4.1.5003.9.10.1.21.2.0.
MediaPack SIP Reader’s Notes MediaPack SIP User’s Manual 286 Document #: LTRT-65405
MediaPack SIP User’s Manual F. Regulatory Information Appendix F Regulatory Information F.1 MP-1xx FXS Declaration of Conformity Application of Council Directives: 73/23/EEC (including amendments), 89/336/EEC (including amendments), Standards to which Conformity is Declared: EN55022: 1998, Class B EN55024:1998 EN61000-3-2: 1995 EN60950: 2000 (including amendments A1: 1998, A2: 1998, A14: 2000) EN61000-3-3: 1995 Manufacturer’s Name: AudioCodes Ltd.
MediaPack SIP Safety Notice Installation and service of this card must only be performed by authorized, qualified service personnel. The protective earth terminal on the back of the MP-1xx must be permanently connected to protective earth.
MediaPack SIP User’s Manual F. Regulatory Information Czech [AudioCodes Ltd] tímto prohlašuje, že tento [MP-1xx/FXO] je ve shodě se základními požadavky a dalšími příslušnými ustanoveními směrnice 1999/5/ES.
MediaPack SIP MP-1xx/FXO Notice The MP-1xx FXO Output Tones and DTMF level should not exceed -9 dBm (AudioCodes setting #23) in order to comply with FCC 68, TIA/EIA/IS-968 and TBR-21. The maximum allowed gain between any 2 ports connected to the PSTN should be set to 0 dB in order to comply with FCC 68, TIA/EIA/IS-968 Signal power limitation FCC Statement This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules.
MediaPack SIP User’s Manual Hungarian F. Regulatory Information Alulírott, [AudioCodes Ltd] nyilatkozom, hogy a [MP-124] megfelel a vonatkozó alapvetõ követelményeknek és az 89/336/EEC, 73/23/EEC irányelv egyéb elõírásainak Icelandic æki þetta er í samræmi við tilskipun Evrópusambandsins 89/336/EEC, 73/23/EEC Italian Con la presente [AudioCodes Ltd] dichiara che questo (MP-124) è conforme ai requisiti essenziali ed alle altre disposizioni pertinenti stabilite dalla directiva 89/336/EEC, 73/23/EEC.
MediaPack SIP F.4 MP-11x FXS Declaration of Conformity Application of Council Directives: 73/23/EEC (including amendments), 89/336/EEC (including amendments), Standards to which Conformity is Declared: EN55022: 1998, Class B EN55024:1998 EN61000-3-2: 1995 (including amendments A1: 1998, A2: 1998, A14: 2000) EN61000-3-3: 1995 EN60950-1: 2001 Manufacturer’s Name: AudioCodes Ltd. Manufacturer’s Address: 1 Hayarden Street, Airport City, Lod 70151, Israel. Type of Equipment: Analog VoIP System.
MediaPack SIP User’s Manual F. Regulatory Information Safety Notice Installation and service of this unit must only be performed by authorized, qualified service personnel. The protective earth terminal on the back of the MP-11x/FXS must be permanently connected to protective earth.
www.audiocodes.
