Dialogic® 1000 and 2000 Media Gateway Series User’s Guide September 2007 64-0260-02
Copyright © 2007, Dialogic Corporation. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Corporation. All contents of this document are furnished for informational use only and are subject to change without notice and do not represent a commitment on the part of Dialogic Corporation or its subsidiaries (“Dialogic”). Reasonable effort is made to ensure the accuracy of the information contained in the document.
Software License Agreement This is a Software License Agreement ("Agreement") between you the Company and your Affiliates and all your Authorized Users (collectively referred to hereinafter as "You" or "Your") and Dialogic Corporation ("Dialogic"). Do not use any Dialogic Corporation software and any associated materials (collectively, the "Software") which are loaded on the Dialogic® Media Gateway hardware product ("Product") until You have carefully read the following terms and conditions.
LIMITED WARRANTY: The only warranty Dialogic makes is that the medium on which the Software is recorded will be replaced without charge if Dialogic, in good faith, determines that it was defective in materials or workmanship and if returned to your supplier with a copy of your receipt within ninety (90) days from the date you received it. Dialogic offers no warranty for your reproduction of the Software.
Contents Revision History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 About This Publication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 Purpose . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Intended Audience . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3.5 3.6 3.7 3.8 3.9 3.10 6 3.4.1 Timing Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 3.4.2 Feature Codes Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57 3.4.3 Message Waiting Control Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59 3.4.4 CPID Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 3.11 3.12 4 125 126 126 127 127 127 127 128 128 128 129 129 129 130 130 131 131 131 132 132 132 133 133 133 134 Working with Call Progress Tones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 4.1 4.2 5 Tone Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.11.1 ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 5.5 5.6 5.7 5.8 5.9 6 Media Gateway Parsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163 6.1 6.2 7 7.3 7.4 7.5 8.6 8.7 Summary Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181 Alarm Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 182 Call Log Status Information . . . . . . . . . . .
Contents 9.4 9.5 9.6 9.7 9.3.2 PBX Self Verification Test Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Diagnostic Logging . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.2 Debug Trace Capture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9.4.
Contents 10 Dialogic® 1000 and 2000 Media Gateway Series User’s Guide – September 2007 Dialogic Corporation
Figures 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 Typical IP Gateway Phone Emulating Topology - PBX Connection . . . . . . . . . . . . . . . . . . . . . 23 Typical IP Gateway Phone Emulating Topology - PSTN Connection . . . . . . . . . . . . . . . . . . . . 23 IP Gateway Using Serial Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 Multiple IP Gateways Using Serial Link . . . .
Contents 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 12 VoIP Interface Call Log Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 PBX/PSTN Interface Diagnostic Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 200 PBX/PSTN Interface Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201 PBX/PSTN Interface Test Status Web Page . .
Tables 1 2 3 4 5 6 7 8 9 10 11 12 Coder/Decoder Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77 Syntax Used for Number Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 TDM Interface Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153 Syntax Used for CPID Manipulation . . . . . . . . . . . . . . . . . . . . . . . . .
Contents 14 Dialogic® 1000 and 2000 Media Gateway Series User’s Guide – September 2007 Dialogic Corporation
Revision History This revision history summarizes the changes made in each published version of this document. Document No. Publication Date Description of Revisions 64-0260-02 September 2007 Updated to support Version 5.1 SU2 Software. Added new DMG1004LS model. Added note to say H.323 is only supported in Version 5.1 SU1 Software or earlier. Chapter 3, “Parameter Reference” added new parameter in Serial Protocol Parameters section for MCI Message Type.
Revision History 16 Dialogic® 1000 and 2000 Media Gateway Series User’s Guide – September 2007 Dialogic Corporation
About This Publication The following topics provide information about this guide: • Purpose • Intended Audience • How to Use This Publication • Related Information Purpose This document provides information about installing, configuring, operating, and maintaining the Dialogic® Media Gateway.
About This Publication units. These parsers allow the user to define the meaning of either the in-band/on-hook integration strings or display strings received from the telephony network. • Chapter 7, “Data Security” provides information about configuring security on the Media Gateway for HTTP, call control, and voice. • Chapter 8, “Unit Status” describes the various types of status information that may be obtained about the Media Gateway.
About This Publication • http://www.dialogic.
About This Publication 20 Dialogic® 1000 and 2000 Media Gateway Series User’s Guide — September 2007 Dialogic Corporation
Overview 1 The following information provides an overview of the Dialogic® Media Gateway: • Product Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 • Call Routing in Phone Emulating Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26 • Voice over IP Address Translation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27 • Security . . . . . . . . . . . . . . . . . . . . . . . .
Overview Depending on the model, the Media Gateway can be configured for the following operating mode: • Phone Emulating 1.1.
Overview Figure 1. Typical IP Gateway Phone Emulating Topology - PBX Connection PSTN VoIP Terminal Device Digital Telephone IP Media Gateway (All Phone Emulating Models) Digital PBX 1-8 Digital Phone Lines or 1-4 T1/E1 Trunks Digital Telephone VoIP Terminal Device LAN Figure 2.
Overview 1.1.1.1 Serial Protocol Support in Phone Emulating Mode By emulating telephone sets to the switch, the Media Gateway provides call party information over the IP network. However, the amount of call party information that the Media Gateway can provide is limited to the amount of data that the switch provides its station sets.
Overview For DMG1000 types, the serial link from the switch is connected to the serial port interface on the DMG1000 (DIAGNOSTICS connector). Table 1, "DIAGNOSTICS Connector Pin Designations" in the Getting Started Guide shows the connector pin designations. For DMG2000 types, the serial link from the switch is connected to the serial port interface on the DMG2000 (COM 1 or COM 2 connector).
Overview The Media Gateway supports the following serial protocols: • SMDI (Simple Message Desk Interface) • MCI (NEC Systems only) • MD110 (Ericsson Systems only) Both the serial interface and the selection of which serial protocol to use are configurable using the Web interface. Refer to Chapter 3, “Parameter Reference” for information about configuring the serial interface and serial protocols. 1.
Overview 1.2.1 Un-Routable Calls A call is un-routable by the Media Gateway if the unit is unable to route the call to the other network. This may occur if there is insufficient destination address information to determine a destination for the call, or if there are not enough free resources on the Media Gateway to route the call. The Media Gateway provides a number of different ways to handle these conditions in order to insure that no calls are dropped or not completed. 1.2.1.
Overview receive H.323 calls. SIP devices register with the VoIP Address Translator to sent and receive SIP calls. Note: In H.323 mode, the VoIP Address Translator is a Gatekeeper. In SIP mode, the VoIP Address Translator is a SIP Registration Server and/or a SIP Proxy Server. Note: H.323 is only supported in Version 5.1 SU1 Software or earlier. The VoIP Address Translator can provide network services such as: • Controlling the number and type of connections allowed across the network.
Overview • Voice security - The actual conversation once a call is connected. To secure voice, the Media Gateway uses SRTP. Note: Security is not provided over H.323. If H.323 is selected instead of SIP, TLS and SRTP are not supported and call control and voice data cannot be secured. Note: H.323 is only supported in Version 5.1 SU1 Software or earlier. Because, for security, the HTTPS and TLS protocols also require digital identity certificates (e.g.
Overview Figure 5.
Overview Figure 6. DMG2000 Web Interface The Media Gateway's Web interface is divided into two sections, H.323 or SIP Status and Configure. The Status Web pages provide run-time information and statistics about the operation of the unit. Note: H.323 is only supported in Version 5.1 SU1 Software or earlier. The Configure Web pages provide the system administrator with an interface to configure the Media Gateway.
Overview • Serial Protocol (Phone Emulating mode only) - Selecting Serial Protocol brings up the Serial Protocol Web page. This Web page allows you to configure the serial protocol for the Media Gateway serial port. See Section 3.5, “Serial Protocol Parameters”, on page 62 for detailed information about the Serial Protocol parameters. • Gateway - Selecting Gateway brings up the Gateway Web page which allows you to configure Gateway parameters.
Overview 1.6 Online Help Context-sensitive online Help is provided for the various Web pages. When you move the mouse pointer over a parameter name, the pointer changes from an arrow to an insertion symbol and Help information about that parameter is displayed at the bottom of the page.
Overview 34 Dialogic® 1000 and 2000 Media Gateway Series User’s Guide — September 2007 Dialogic Corporation
Configuring the Media Gateway 2 Information about configuring, and upgrading the Dialogic® 1000 Media Gateway (DMG1000) and Dialogic® 2000 Media Gateway (DMG2000) is contained in the following sections: • Setting the IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35 • Basic Configuration Via the Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36 • Changing the Password . . . . . . . . . . . . . . . . . . .
Configuring the Media Gateway 8. Once the system completes its initialization (after approximately one minute), browse to the new IP address. The Web browser can now access the unit at the new IP address. 9. If it was necessary to change the IP address of your Windows® workstation in the Initial Log On procedure (described in the Getting Started Guide), you should now change it back to the original IP address and access the Media Gateway using the Media Gateway’s newly configured IP address. 10.
Configuring the Media Gateway • For DMG1000 models, select PBX Type (See PBX Type parameter information in Section 3.3, “System Parameters”, on page 51.) • For DMG2000 models, select: – Line Mode (Section 3.7.1.1, “Line Mode”, on page 87) – CAS Protocol (Section 3.7.1.2, “Signaling Mode”, on page 87 and Section 3.7.2.1, “T1 CAS Protocol”, on page 88) or ISDN Protocol (Section 3.7.1.2, “Signaling Mode”, on page 87 and Section 3.7.3.1, “ISDN Protocol”, on page 94) 8.
Configuring the Media Gateway 4. Select the appropriate configuration Web page from the Configure menu. For example, to define the PCM Coding as aLaw, select the System Web page from the menu. When the System Web page appears, select aLaw from the drop down box as the PCM Coding parameter value. 5. Click on the Apply Changes button to save the new configuration in the database, or click on the Reset button to return the parameter to the previous value.
Configuring the Media Gateway • Multiple unit implementation - At a site where there are multiple Media Gateway units, much of the configuration will be the same between units (e.g. Audio Parameters, SIP/H.323 Parameters, etc.). An installer could configure the first unit, export the *.ini file, edit the unit specific parameters in the *.ini file (e.g. IP Address) using Notepad, and then import the modified file to the next unit. This will speed up and simplify the installation procedure at larger sites.
Configuring the Media Gateway 2.7 Upgrading the Software Software upgrades for the Media Gateway products will be made available on the Dialogic support Web site as needed. Contact technical support to obtain software upgrade files. Upgrade files are uploaded to the Media Gateway using the Web interface. Caution: When a major software upgrade is performed, existing configuration information may be erased and the default values restored.
Parameter Reference 3 This section lists each Dialogic® 1000 Media Gateway (DMG1000) and Dialogic® 2000 Media Gateway (DMG2000) configuration parameter that may be changed using the Web browser Configure menu. Also listed are non-menu (hidden) parameters which are not accessible from the Configure menu. Changing non-menu parameters significantly modifies the operation of the Media Gateway.
Parameter Reference 3.1.1.1 Client IP Address Description: Sets the IP address of the Media Gateway. Allowed Values: Any valid IP address in dotted decimal notation. Default Value = 10.12.13.74 INI File Parameter Name = ipClientAddr Note: 3.1.1.2 Unit requires a restart if this parameter value is changed. Client Subnet Mask Description: Sets the subnet mask of the Media Gateway. Allowed Values: Any valid IP mask. Default Value = 255.255.255.0 INI File Parameter Name = ipSubnetMask Note: 3.1.1.
Parameter Reference INI File Parameter Name = ipBootpEnabled Note: 3.1.1.5 Unit requires a restart if this parameter value is changed. SNTP Server IP Address Description: Simple Network Time Protocol (SNTP) server IP address. Used for SIP Transport Layer Security (TLS) data verification Allowed Values: Any valid IP address in dotted decimal notation. Default Value = No default value INI File Parameter Name = ipSntpServerAddr Note: 3.1.2 Unit requires a restart if this parameter value is changed.
Parameter Reference INI File Parameter Name = ipSubnetMaskLan2 Note: 3.1.3 Unit requires a restart if this parameter value is changed. IP Advanced Parameters (DMG2000) The IP advanced parameters allow an advanced network topology to be configured using the LAN interfaces. The administrator can configure which LAN interfaces provide access to the IP management protocols.
Parameter Reference Figure 7. Example of a Network Topology Two routes are required in this topology so that: 1. LAN1 can access LAN1 Subnet B 2. LAN2 can access LAN2 Subnet B The IP Router 1 may be configured as the default network gateway. However, the DMG2000 must also be configured to use IP Router 2 as a network gateway. A custom route must be created so that LAN2 can access LAN2 Subnet B. In addition, the default network gateway may be optionally replaced by another custom route.
Parameter Reference An IP route rule is a custom routing rule on a specific LAN interface. It allows access to a specific subnet that matches the destination address/mask via the specified gateway address. This rule supplements or replaces the functionality of the default network gateway address by providing access to multiple subnets across all LAN interfaces. The IP route rules are available on the DMG2000 only. Ethernet Interface Description: Specifies the LAN interface used for the route.
Parameter Reference Gateway Address Description: IP address of the gateway router that receives all IP packets from the LAN that match this route. The gateway IP address must be in the same subnet as the route's LAN interface. Allowed Values: Any valid IP address in dotted decimal notation. Default Value = blank INI File Parameter Name = ipRouteGw Note: 3.2 Unit requires a restart if this parameter value is changed.
Parameter Reference Allowed Values: • Self Signed = Use the self-signed TLS certificate • CA Signed = Use the CA-signed TLS certificate Default Value = Self Signed INI File Parameter Name = secSipTlsUseSelfSignedCert Note: 3.2.2 Unit requires a restart if this parameter value is changed.
Parameter Reference 3.2.2.2 MKI on Transmit Stream Description: Specifies if Master Key Index (MKI) is supported on transmit stream. Allowed Values: • Yes = Transmit stream supports MKI • No = Transmit stream does not support MKI Default Value = Yes INI File Parameter Name = srtpTxMkiEnable Note: 3.2.2.3 Currently, the Media Gateway uses only one master key. Key Derivation Enable Description: Specifies if the Secure RTP (SRTP) Key is changed during a voice session.
Parameter Reference 3.2.2.6 Cipher Mode Description: Specifies the cipher used to encrypt voice packets. Note: Plain text is essentially no encryption and should be used only for testing purposes. For no encryption, you should specify RTP ONLY in the SRTP Preference parameter. Allowed Values: • Plain_Text = Use Plain_Text as the cipher (No encryption - for testing purposes only) Note: Plain_Text is not supported in Version 5.1 SU2 Software.
Parameter Reference 3.3 System Parameters These parameters control the system level operation of the Media Gateway. The System parameters include the following groups: • System Group • Telephony Group • Serial Port, COM1 Group • Serial Port, COM2 Group (DMG2000 Only) 3.3.1 System Group The following parameter is in the System Group: 3.3.1.1 Operating Mode Description: Selects the VoIP protocol (SIP or H.323) of the Media Gateway. Allowed Values: • H.323 = H.323 protocol is used.
Parameter Reference • M1 = Nortel Meridian-1/Meridian SL-1 • Norstar = Nortel Norstar Key Systems • Optiset_300ECS = Siemens Hicom 300E CS • Optiset_300E = Siemens Hicom 300E • Lucent = Lucent DEFINITY G3 • Magix = Merlin Magix • NEC_IMG = NEC IMG • NEC_IMX = NEC IMX • NEC_NEAX = NEC NEAX or NEC 2400 IPX • Rolm_8000 = Rolm 8000 • Rolm_9751_SW9005 = Rolm 9751 with software release 9005 or earlier • Rolm_9751_SW9006 = Rolm 9751 with software release 9006 or earlier Default Value = None INI File Parameter Na
Parameter Reference 3.3.3.1 Serial Port Baud Rate Description: Specifies the baud rate of the Media Gateway serial port. Allowed Values: • 1200 = 1200 bps • 2400 = 2400 bps • 9600 = 9600 bps • 19200 = 19200 bps • 38400 = 38400 bps Default Value = 38400 INI File Parameter Name = sysSerialBaudRate 3.3.3.2 Serial Port Parity Description: Specifies the parity of the Media Gateway serial port. Allowed Values: • None = Parity will not be used. • Even = Even parity will be used.
Parameter Reference Allowed Values: • 1 stop bit • 2 stop bits Default Value = 1 stop bit INI File Parameter Name = sysSerialStopBits 3.3.4 Serial Port, COM2 Group (DMG2000 Only) The Serial Port, COM2 group parameters are used to configure the DMG2000 diagnostics/administration serial port (COM2 connector). The system parameters in the Serial Port group include: • Serial Port Baud Rate • Serial Port Parity • Serial Port Data Bits • Serial Port Stop Bits 3.3.4.
Parameter Reference Default Value = None INI File Parameter Name = sysSerialParityCom2 3.3.4.3 Serial Port Data Bits Description: Specifies the number of data bits used by the DMG2000 serial port. Allowed Values: • 7 data bits • 8 data bits Default Value = 8 data bits INI File Parameter Name = sysSerialDataBitsCom2 3.3.4.4 Serial Port Stop Bits Description: Specifies the number of stop bits used by the DMG2000 serial port.
Parameter Reference • Incoming Rings Before Answer • Ringing Timeout 3.4.1.1 Flash Hook Description: Specifies the duration in milliseconds that the DMG1000 will remain on-hook during a hook flash operation. Allowed Values: 50 to 4000 milliseconds Default Value = 500 milliseconds INI File Parameter Name = telFlashMs 3.4.1.
Parameter Reference 3.4.2 Feature Codes Group The Analog parameters in the Feature Codes group include: • Consult Call Dialtone Drop Code • Consult Call Proceeding Drop Code • Consult Call Busy Drop Code • Consult Call Connected Drop Code • Consult Call Disconnected Drop Code • Consult Call Error Drop Code 3.4.2.1 Consult Call Dialtone Drop Code Description: Defines the Feature Code to dial in order to drop a Consult call that is in the Dialtone state and to reconnect to the original call.
Parameter Reference Default Value = !! Note: Each ! is a hook flash. For !, the Media Gateway will perform a single hook-flash operation. For !!, the Media Gateway will perform a double hook-flash operation. INI File Parameter Name = telFacCDropBusy 3.4.2.4 Consult Call Connected Drop Code Description: Defines the Feature Code to dial in order to drop a Consult call that is in the Connected state and to reconnect to the original call.
Parameter Reference 3.4.3 Message Waiting Control Group The Analog parameters in the Message Waiting Control group include: • MWI Confirmation Tone • Use Same Port for MWI Clear/Set 3.4.3.1 MWI Confirmation Tone Description: Specifies whether or not the PBX sends a confirmation tone to signal the successful completion of a Message Waiting Indication (MWI) request. Allowed Values: • Yes = PBX will send a confirmation tone. • No = PBX will not send a confirmation tone.
Parameter Reference • CPID Parsing Configuration 3.4.4.1 Initial Wait for Inband CPID Description: Specifies the number of milliseconds the DMG1000 will wait for the first inband DTMF digit to arrive after answering an incoming PBX call. Allowed Values: 100 to 10000 milliseconds Default Value = 2000 milliseconds INI File Parameter Name = telInbCpidStartMs 3.4.4.
Parameter Reference Allowed Values: • Bellcore FSK • DTMF • None Default Value = None INI File Parameter Name = telAlgCoCidType 3.4.4.5 Central Office (Type I) Caller ID Alert Type Description: Specifies the kind of Type I caller ID alert that is used on the trunk(s) connected to the DMG1000, either pause in ring cycle, ring burst, polarity reversal, or none. This configuration option is only enabled when the Central Office (Type I) Caller ID Type is set to Bellcore FSK. Notes: 1.
Parameter Reference 3.4.4.7 Central Office (Type I) FSK Caller ID Timeout Description: Specifies the duration in milliseconds that the digital signal processor (DSP) will perform FSK Type I Caller ID detection after an alert is detected. This configuration option is only enabled when the Central Office Caller ID Type is Bellcore FSK and the Caller ID Alert Type is other than None.
Parameter Reference 3.5.1 Serial Mode (Master/Slave) Description: Specifies if the Media Gateway is using the serial protocol and, if so, whether the unit is the Serial Protocol Master or Slave. The Media Gateway must be configured as the Master if it is physically connected to the serial link of the PBX. In a system with multiple Media Gateways, only one of the units can be connected to the serial link of the PBX.
Parameter Reference Default Value = Six-Digits INI File Parameter Name = telSerMciMsg 3.5.4 MCI Message Type Description: Specifies the type of MCI messages. Messages can be Type B (default) or Type A. Type B messages include a tenant number of ‘01’ while Type A messages exclude a tenant number. Allowed Values: • Type_A • Type_B Default Value = Type_B INI File Parameter Name = telSerMciMsgType 3.5.
Parameter Reference 3.5.7 Voice Mail Port Length Description: Specifies the length of the field in the serial data packet that contains the "voice mail port" number that the call arrived (or will arrive) on. This parameter is only required when the serial protocol is set to MD110 and the Media Gateway is the Serial Protocol Master. Allowed Values: 2 to 5 Default Value = 2 INI File Parameter Name = telSerVmpLen 3.5.
Parameter Reference Default Value = (no default value) INI File Parameter Name = telSerAddrSrvr Note: 3.5.11 Unit requires a restart if this parameter value is changed. Serial CPID Expiration Description: Specifies the time in milliseconds that serial CPID information received by a Media Gateway (Master or Slave) remains valid. If the timeout expires before an inbound call is received on the Media Gateway PBX port indicated by the serial CPID information, the serial CPID information is discarded.
Parameter Reference 3.6.1.1 Call Routing Group The Call Routing group includes the following parameters: • Fault Tolerance Enabled • Load Balancing Enabled • VoIP Endpoint ID Fault Tolerance Enabled Description: Enables or disables fault-tolerance handling of outbound Voice over IP (VoIP) calls. If Yes is selected, the Media Gateway will failover to the next configured VoIP endpoint if an outbound VoIP call attempt fails. If No is selected, then a failed outbound VoIP call attempt will not be retried.
Parameter Reference Allowed Values: • If no H.323 Gatekeeper, SIP Registration Server, or DNS Server is used, then any valid IP address (in dotted decimal notation) may be specified. • If an H.323 Gatekeeper, SIP Registration Server, or DNS Server is used, then the IP terminal address may also be specified as an alias string name, an e-mail address, or an IP address (in dotted decimal notation). Note: H.323 is only supported in Version 5.1 SU1 Software or earlier.
Parameter Reference Call Connect Mode Description: Specifies when voice path is created between the IP device endpoint and the PBX on IP-to-PBX calls. Allowed Values: • On-Answer = the voice path is not established until the dialed PBX extension answers the call. • Instant = the voice path is established as soon as the PBX extension is dialed.
Parameter Reference Destination for Un-routable PBX Calls Description: Specifies the PBX extension number to which un-routable PBX-To-IP calls will be transferred. Allowed Values: • Any valid dialable number string (0 to 7 characters). • If blank (none), then un-routable calls are ignored/dropped.
Parameter Reference • Maximum Call Party Delay (Phone Emulating Only) • Dial Digit On Time • Dial Inter-Digit Time • Dial Pause Time • Turn MWI On FAC (Phone Emulating Only) • Turn MWI Off FAC (Phone Emulating Only) • Dial Send Key (Phone Emulating Only) • Outbound Call Connect Timeout (Phone Emulating Only) • Wait for Ringback/Connect on Blind Transfer (Phone Emulating Only) • Hunt Group Extension (Phone Emulating Only) Minimum Call Party Delay (Phone Emulating Only) Description: Specifies the minimum nu
Parameter Reference Dial Inter-Digit Time Description: Specifies the delay in milliseconds between dialed DTMF digits to the PBX. Allowed Values: 30 through 2000 milliseconds Default Value = 100 milliseconds INI File Parameter Name = telDialInterDigitMs Dial Pause Time Description: Specifies the delay in milliseconds for each pause (,) character encountered in a dial string.
Parameter Reference Allowed Values: *, #, None Default Value = None INI File Parameter Name = dpInbVoipAltRoute Outbound Call Connect Timeout (Phone Emulating Only) Description: Specifies the time in milliseconds that the Media Gateway will wait for a connect event on an outbound circuit call. If no connect event is received within the time specified, the Media Gateway will automatically transition the call to the connected state. Allowed Values: 0 to 60000 milliseconds Default Value = 10000 milliseconds.
Parameter Reference 3.6.2.3 Audio Group The Audio subgroup includes the following parameters: • Audio Compression • RTP Digit Relay Mode • RTP Fax/Modem Tone Relay Mode • RTP Source IP Address Validation • RTP Source UDP Port Validation • Signaling Digit Relay Mode • Voice Activity Detection • Codec/Frame Size/Frames Per Packet Audio Compression Description: Sets the audio coder/decoder to be used by the Media Gateway. Allowed Values: • G.711u/G.711a = G.711 uLaw preferred, G.711 aLaw secondary • G.
Parameter Reference • Inband-Tone = The DTMF tones are coded into the regular audio packets (RTP voice packets) sent between the Media Gateway and VoIP endpoints. Default Value = RFC2833 INI File Parameter Name = dspDigitRelay RTP Fax/Modem Tone Relay Mode Description: Selects the Realtime Transfer Protocol (RTP) method by which fax and modem tones are transported between the TDM network and VoIP network.
Parameter Reference Default Value = Off INI File Parameter Name = gwRTPValidateSrcPort Note: Unit requires a restart if this parameter value is changed. Signaling Digit Relay Mode Description: Specifies if out-of-band messages are used to transport DTMF tones between the Media Gateway and VoIP endpoints. Note: This parameter should be set to Off when the Operating Mode parameter is set to either SIP Emulating or SIP Driving.
Parameter Reference Table 1. Coder/Decoder Parameters Codec Type Frame Size in Bytes Frames Per Packet DMG1000 G.711 Selectable: 10, 20, 30 1 G.723 10 Selectable: 1 through 4 G.729 20 Selectable: 1 through 8 DMG2000 G.711 Selectable: 10, 20, 30 1 G.723 10 1 or 2 G.729 20 Selectable: 1 through 6 INI File Parameter Name = dspFrameSizeG711, dspFramesPerPktG723k, dspFramesPerPktG729 3.6.2.
Parameter Reference Call Control QOS Byte Description: The Call Control QOS Byte parameter defines a decimal byte value that represents QOS bit flags. This parameter is used in each call control (SIP or H.323) data packet transmitted from the Media Gateway with a QOS byte code. Routers use this byte code to assign priority levels to packets. The QOS byte may be interpreted as either IPv4 TOS or DiffServ. Note: H.323 is only supported in Version 5.1 SU1 Software or earlier.
Parameter Reference RTP QOS Type Description: The RTP QOS Type parameter defines a decimal value that represents QOS bit flags. This parameter is used in each RTP data packet transmitted from the Media Gateway with a QOS byte code. Routers use this byte code to assign priority levels to packets. The QOS byte may be interpreted as either IPv4 TOS or DiffServ.
Parameter Reference 3.6.2.6 E-Mail Group The E-Mail subgroup includes the following parameters: • E-Mail Alarms Enabled • E-Mail Minimum Alarm Severity • Destination E-Mail List • E-Mail Server IP Address • Source E-Mail Address E-Mail Alarms Enabled Description: Defines whether an e-mail is generated to signal an alarm. Allowed Values: • Yes = E-mail is generated. • No = E-mail is not generated.
Parameter Reference E-Mail Server IP Address Description: IP addresses of the SMTP e-mail server that receive the e-mail generated by the IP gateway. Allowed Values: Any valid IP address in dotted decimal notation. Default Value = (no default value) INI File Parameter Name = emailServerAddr Source E-Mail Address Description: E-mail address used as source of e-mail alarm messages. Allowed Values: Any valid e-mail address Default Value = alarm@pbxgw.com INI File Parameter Name = emailSource 3.6.2.
Parameter Reference Allowed Values: • Yes = Alarms are sent as user-level facility messages. • No = Alarms are sent to SysLog server. Default Value = No INI File Parameter Name = syslogAlarmEnabled SysLog Minimum Alarm Severity Description: Defines the minimum alarm severity level that generates notifications to SysLog server. Allowed Values: • Error = Error alarms are sent to the SysLog server. • Warn = Error and Warning alarms are sent to the SysLog server.
Parameter Reference SNMP Traps Enabled? Description: Defines whether an SNMP trap is generated to signal an alarm. Allowed Values: • Yes = SNMP trap is generated. • No = SNMP trap is not generated. Default Value = No INI File Parameter Name = snmpTrapEnabled SNMP Minimum Alarm Severity Description: Defines the minimum alarm severity level to generate an SNMP trap.
Parameter Reference INI File Parameter Name = snmpCommunity Note: Unit requires a restart if this parameter value is changed. SNMP System Name Description: Specifies the SNMP System name. Allowed Values: Any string with length between 0 - 63 characters. Default Value = (no default value) INI File Parameter Name = snmpSysName Note: Unit requires a restart if this parameter value is changed. SNMP System Contact Description: Specifies the SNMP System administration contact name.
Parameter Reference Allowed Values: • Yes = HTTP Server is enabled. • No = HTTP Server is disabled. Default Value = Yes INI File Parameter Name = webHttpEnabled Note: Unit requires a restart if this parameter value is changed. HTTPs Server Enabled Description: Defines whether the HTTPs Server is enabled or disabled. Disable the HTTP Server to disable non-secure Web access. Allowed Values: • Yes = HTTPs Server is enabled. • No = HTTPs Server is disabled.
Parameter Reference 3.6.3 Gateway Capabilities Group The Port Capabilities parameters allow you to individually configure the call control capabilities of each port connected to the Media Gateway. These parameters also allow you to enable or disable individual ports. The Port Capabilities group includes the following parameters: • Port # • Telephony Port Capability • Telephony Port Enabled 3.6.3.1 Port # Description: This is a read-only parameter that defines the Media Gateway port numbers. Note: 3.6.
Parameter Reference 3.7 T1/E1 Parameters (DMG2000 Only) The T1/E1 parameters are used to configure the T1 and E1 port(s) on a DMG2000 and include the following groups: • T1/E1 Mode Group • T1 CAS Protocol Group (T1 CAS Signaling Mode) • T1 ISDN Protocol Group (ISDN Signaling Mode) • E1 ISDN Protocol Group (ISDN Signaling Mode) • CPID Parsing Configuration 3.7.1 T1/E1 Mode Group The parameters in the T1/E1 Mode group include the following: • Line Mode • Signaling Mode • Interface Side 3.7.1.
Parameter Reference 3.7.1.3 Interface Side Description: Identifies the side of the connection. Allowed Values: • Terminal = Terminal (user) side of device • Network = Network side of device Default Value = Terminal INI File Parameter Name = t1e1Interface 3.7.
Parameter Reference • Ground Start = Ground Start protocol will be used. • E&M Immediate = E&M Immediate protocol will be used. • E&M Delay = E&M Delay protocol will be used. • E&M Wink = E&M Wink protocol will be used. Default Value = Loop Start INI File Parameter Name = t1e1CASProtocol 3.7.2.2 Line Encoding Description: Specifies the type of T1 line coding that will be used. Allowed Values: • AMI = Alternate Mark Inversion line coding is used.
Parameter Reference Default Value = Short Haul 110 ft INI File Parameter Name = t1e1TxWave 3.7.2.5 Flash Hook Description: - Specifies the duration in milliseconds that the Media Gateway will remain on-hook during a hook flash operation. Allowed Values: 50 to 4000 milliseconds Default Value = 500 milliseconds INI File Parameter Name = telFlashMs 3.7.2.
Parameter Reference 3.7.2.9 Consult Call Dialtone Drop Code Description: Defines the Feature Code to dial in order to drop a Consult call that is in the Dialtone state and to reconnect to the original call. Allowed Values: A string from 0 to 10 digits in length using any of the following characters: 0-9, *, #, ! Default Value = !! Note: Each ! is a hook flash. For !, the Media Gateway will perform a single hook-flash operation. For !!, the Media Gateway will perform a double hook-flash operation.
Parameter Reference Allowed Values: A string from 0 to 10 digits in length using any of the following characters: 0-9, *, #, ! Default Value = !! Note: Each ! is a hook flash. For !, the Media Gateway will perform a single hook-flash operation. For !!, the Media Gateway will perform a double hook-flash operation. INI File Parameter Name = telFacCDropCon 3.7.2.
Parameter Reference INI File Parameter Name = telMwiConfirm 3.7.2.16 CPID Type Description: Selects the timing of in-band CPID information. Allowed Values: • Type I DTMF = CPID sent between first and second ring • Type II DTMF = CPID sent after off-hook Default Value = Type I DTMF INI File Parameter Name = t1e1CpidType 3.7.2.
Parameter Reference • Outbound TDM Calling Party Source • Static TDM Calling Party 3.7.3.1 ISDN Protocol Description: If ISDN is selected as the Signaling Mode, specifies the T1 ISDN protocol to be used. Allowed Values: • QSIG = QSIG ISDN protocol is used. • NI-2 = US National ISDN - Phase 2 protocol is used. • 5ESS = 5ESS protocol is used. • DMS100 = DMS100 protocol is used. Default Value = QSIG INI File Parameter Name = t1IsdnProtocol 3.7.3.
Parameter Reference Allowed Values: • SF = D4 Superframe format (12 consecutive T1 frames) is used. • ESF = Extended Superframe format (24 consecutive T1 frames) is used. Default Value = ESF INI File Parameter Name = t1Framing 3.7.3.5 Selects Transmit Pulse Waveform Description: Selects the method to be used for generating the Transmit Waveform Shape. Allowed Values: • Short Haul 110 ft = The DMG2000 is 0 - 110 feet from T1 line source.
Parameter Reference • VoIP_Preferred = Calling party is derived from the VoIP call/mwi-request. If not available from VoIP, then the statically configured calling party is used. Default Value = Static INI File Parameter Name = gwTdmOutboundCallingPartySrc 3.7.3.7 Static TDM Calling Party Description: Specifies the calling party that will be provided to the TDM interface if Outbound TDM Calling Party Source is set to Static or VoIP_Preferred.
Parameter Reference Allowed Values: • QSIG = QSIG ISDN protocol is used. • ETSI = EuroISDN (ETSI) protocol is used. Default Value = QSIG INI File Parameter Name = e1IsdnProtocol Note: 3.7.4.2 Unit requires a restart if this parameter value is changed. ISDN Protocol Variant Description: Specifies the type of E1 ISDN protocol variant to be used. Allowed Values: • None = None (Standard) • Alcatel = Support Alcatel Extensions. • Ericsson = Support Ericsson Extensions.
Parameter Reference Default Value =CRC_FMF INI File Parameter Name = e1Framing Note: 3.7.4.5 Unit requires a restart if this parameter value is changed. Selects Transmit Pulse Waveform Description: Selects the method to be used for generating the Transmit Waveform Shape. Allowed Values: • 75_Ohm = 75 ohm (unbalanced) impedance is used. • 120_Ohm = 120 ohm (balanced) impedance is used. Default Value = 75 Ohm Impedance INI File Parameter Name = e1TxWave Note: 3.7.4.
Parameter Reference Allowed Values: • None = No calling party is sent. • VoIP = Calling party is derived from the VoIP call/mwi-request. • Static = A statically configured calling party is used. • VoIP_Preferred = Calling party is derived from the VoIP call/mwi-request. If not available from VoIP, then the statically configured calling party is used. Default Value = Static INI File Parameter Name = gwTdmOutboundCallingPartySrc 3.7.4.
Parameter Reference • Gateway Prefix • Gatekeeper IP Address • Gatekeeper Multicast IP Address • Proxy IP Address • Preferred Gatekeeper ID • Fast Start • H.245 Signaling User Input • Master OLC Transmit Delay Note: 3.8.1 H.323 is only supported in Version 5.1 SU1 Software or earlier. Gatekeeper Mode Description: Specifies the H.323 gatekeeper mode. Allowed Values: • None = No gatekeeper is used. • Manual = Gatekeeper IP Address parameter is used to identify the IP address of the gatekeeper.
Parameter Reference 3.8.3 Gateway Prefix Description: Specifies the E.164 prefix number to be used by IP terminal devices to access this Media Gateway. Used only when an H.323 gatekeeper is in the system. Allowed Values: Any valid E.164 prefix number (0 to 9 digits) Default Value = 9 INI File Parameter Name = h323GatewayPrefix Note: Unit requires a restart if this parameter value is changed. Note: H.323 is only supported in Version 5.1 SU1 Software or earlier. 3.8.
Parameter Reference INI File Parameter Name = h323ProxyAddr 3.8.7 Preferred Gatekeeper ID Description: Specifies the preferred gatekeeper ID when multiple gatekeepers respond to a gatekeeper auto-discovery query. Used only when the GateKeeper Mode is Auto. Allowed Values: Any valid string (0 to 63 characters) Default Value = (no default value) INI File Parameter Name = h323GKPreferred Note: 3.8.8 Unit requires a restart if this parameter value is changed.
Parameter Reference 3.8.10 Master OLC Transmit Delay Description: Specifies the delay in milliseconds before H.323 master transmits an Open-LogicalChannel. Allowed Values: 0 through 30000 Default Value = 2000 INI File Parameter Name = h323OLCXmitDelayMs Note: 3.9 H.323 is only supported in Version 5.1 SU1 Software or earlier.
Parameter Reference 3.9.1.2 Transport Type Description: Defines the preferred transport protocol of call signaling packets. Allowed Values: • TCP = Transmission Control Protocol is used as the transport protocol. • UDP = User Datagram Protocol is used as the transport protocol. Default Value = UDP INI File Parameter Name = sipTransportType 3.9.1.3 Call as Domain Name? Description: Defines the host name used in the From header of generated INVITE requests.
Parameter Reference Default Value = 120 seconds INI File Parameter Name = sipExpInvSec 3.9.2 Server Group The Server group includes the following parameters: • DNS Server Address • DNS Translation of Phone Numbers • Registration Server Address • Registration Server Port • Registration Expiration (sec) 3.9.2.1 DNS Server Address Description: Specifies the IP address of the Domain Name Server (DNS) that the Media Gateway will use to resolve IP address information. Notes: 1.
Parameter Reference INI File Parameter Name = sipEnumDnsEnabled 3.9.2.3 Registration Server Address Description: IP Address of the SIP Registration Server that the Media Gateway should register with. If blank, the Media Gateway will not register with a Registration Server. Allowed Values: • Any valid IP address in dotted decimal notation. • Blank Default Value = (no default value) INI File Parameter Name = sipRegAddr Note: 3.9.2.4 Unit requires a restart if this parameter value is changed.
Parameter Reference 3.9.3.1 UDP/TCP Transport Enabled Description: Enables or disables the UDP/TCP transports. Allowed Values: • Yes = UDP and TCP transports are enabled. • No = UDP and TCP transports are disabled. Default Value = Yes INI File Parameter Name = sipUdpTcpEnabled Note: 3.9.3.2 Unit requires a restart if this parameter value is changed. TCP/UDP Server Port Description: The TCP/UDP Port of the Media Gateway on which SIP messages are sent/received.
Parameter Reference • Verify TLS Peer Certificate Trust 3.9.4.1 TLS Transport Enabled Description: Determines whether the TLS transport is enabled or disabled. Allowed Values: • Yes = TLS transport is enabled. • No = TLS transport is disabled. Default Value = No INI File Parameter Name = sipTlsEnabled Note: 3.9.4.2 Unit requires a restart if this parameter value is changed.
Parameter Reference 3.9.4.4 Mutual Authentication Required Description: If Yes is selected, the SIP client sends a certificate to the peer server and the SIP server will send a certificate request to the client. The certificate received from the client is validated. If the client does not provide a valid certificate, the server will close the session. If No is selected, the SIP server does not send a client certificate request to the client and the client does not send a certificate to the server.
Parameter Reference 3.9.4.7 Verify TLS Peer Certificate Trust Description: Determines whether the TLS peer's certificate trust relationship is validated against the list of trusted CA certificates. Allowed Values: • Yes = Validate • No = Do not validate Default Value = Yes INI File Parameter Name = sipTlsCertVerifyTrust 3.9.
Parameter Reference 3.9.5.3 Backup Proxy Server Address Description: The IP Address of the SIP Backup Proxy Server through which the Media Gateway may send/receive requests. If blank, the Media Gateway will not use a Backup Proxy Server. Allowed Values: Any valid IP Address in dotted decimal notation. Default Value = (no default value) INI File Parameter Name = sipProxyServerAddr2 3.9.5.4 Backup Proxy Server Port Description: The IP Port of the SIP Backup Proxy Server.
Parameter Reference 3.9.6.1 T1 Time Description: The T1 Time specifies the SIP request retransmit timeout in milliseconds. This timer is started when a SIP request is generated. If no response to the request is received in T1 Time milliseconds, the request is retransmitted and the timeout is doubled to 2*T1 Time milliseconds. If again no response is received before the new timeout, the message is again retransmitted and the timeout is again doubled - this time to 4*T1 Time milliseconds.
Parameter Reference 3.10.1 DSP Advanced Group The DSP Advanced parameters are not included in the Configuration menu selections. These parameters are accessed instead by typing dsp.htm following the Media Gateway IP address in the Web browser address box. For example: http://10.12.13.74/dsp.htm Caution: Modifying any of these parameters affects the digital signal processors and significantly changes the operation of the Media Gateway.
Parameter Reference • IP to PCM AGC Max Gain (DMG2000 Only) • IP to PCM AGC Min Gain (DMG2000 Only) • TDM to IP AGC Enable (DMG2000 Only) • TDM to IP AGC Slew Rate (DMG2000 Only) • TDM to IP AGC Target Level (DMG2000 Only) • TDM to IP AGC Max Gain (DMG2000 Only) • TDM to IP AGC Min Gain (DMG2000 Only) T.38 Advanced Settings • Allow T.38 ECM Faxes (DMG2000 Only) • Transmit Small T4 ECM T.38 Packets (DMG2000 Only) • Enable T.
Parameter Reference INI File Parameter Name = dspIPtoPbxGain 3.10.2.3 Line Echo Cancellation (DMG1000 Only) Description: Enables or disables the echo canceller on the PBX (TDM) side. Allowed Values: • On = Enables the echo canceller. • Off = Disables the echo canceller. Default Value = On INI File Parameter Name = dspEc 3.10.2.4 Line Echo Cancellation NLP (DMG1000 Only) Description: Enables or disables the echo canceller non-linear processor (NLP) on the PBX (TDM) side.
Parameter Reference 3.10.2.6 Voice Activity Noise Floor Description: Defines the noise floor for the voice activity detector (VAD). Signal levels below the value selected will be treated as silence by the VAD. Allowed Values: -80 dB to -10 dB Default Value = -40 dB INI File Parameter Name = vadNoiseFloor Note: 3.10.2.7 Unit requires a restart if this parameter value is changed.
Parameter Reference 3.10.2.10 Call Progress Filter Debounce Description: Specifies the debounce time in milliseconds for the Call Progress Tone Detector. This value defines the minimum time that a call progress signal must be present before the detector is triggered. Allowed Values: 100 to 32768 milliseconds Default Value = 100 milliseconds INI File Parameter Name = cpFilterDebounce Note: 3.10.2.11 Unit requires a restart if this parameter value is changed.
Parameter Reference INI File Parameter Name = cpFilterHighCutoff Note: 3.10.2.14 Unit requires a restart if this parameter value is changed. Call Progress Filter SNR in dB (DMG2000 Only) Description: Specifies the Signal to Noise Ratio (SNR) of the Call Progress Tone Detector. Call progress signals whose SNR is lower than specified will be ignored. Allowed Values: 0 dB to 40 dB Default Value = 20 dB INI File Parameter Name = cpFilterSnr Note: 3.10.2.
Parameter Reference Allowed Values: 0 to 200 milliseconds Default Value = 200 milliseconds INI File Parameter Name = dspJbDelayMaxMs 3.10.2.18 Jitter-Buffer Initial Delay (DMG2000 Only) Description: Specifies the starting jitter-buffer delay. It is recommended that this value be set to at least two times the duration of one RTP packet interval. If the minimum, maximum, and initial jitter-buffer delays are set to the same value, the jitter-buffer will operate in the non-adaptive mode.
Parameter Reference Default Value = Soft INI File Parameter Name = dspJbDeletionMode 3.10.2.22 IP to PCM AGC Enable (DMG2000 Only) Description: Enables automatic gain control (AGC) in the IP to PCM direction. Allowed Values: • On = AGC is enabled. • Off = AGC is disabled. Default Value = On INI File Parameter Name = dspIpToPbxAgcEnable 3.10.2.23 IP to PCM AGC Slew Rate (DMG2000 Only) Description: Determines the speed at which the AGC adapts in the IP to PCM direction.
Parameter Reference INI File Parameter Name = dspIpToPbxAgcMaxGain 3.10.2.26 IP to PCM AGC Min Gain (DMG2000 Only) Description: Defines the IP to PCM AGC minimum gain within the range of 0 to -15 dB. Allowed Values: 0 to -15 dB Default Value = -15 dB INI File Parameter Name = dspIpToPbxAgcMinGain 3.10.2.27 TDM to IP AGC Enable (DMG2000 Only) Description: Enables automatic gain control (AGC) in the PCM to IP direction. Allowed Values: • On = AGC is enabled. • Off = AGC is disabled.
Parameter Reference 3.10.2.30 TDM to IP AGC Max Gain (DMG2000 Only) Description: Defines the PCM to IP AGC maximum gain within the range of 0 to 15 dB. Allowed Values: 0 to 15 dB Default Value = 12 dB INI File Parameter Name = dspPbxToIpAgcMaxGain 3.10.2.31 TDM to IP AGC Min Gain (DMG2000 Only) Description: Defines the PCM to IP AGC minimum gain within the range of 0 to -15 dB. Allowed Values: 0 to -15 dB Default Value = -15 dB INI File Parameter Name = dspPbxToIpAgcMinGain 3.10.3 T.
Parameter Reference 3.10.3.3 Enable T.38 Spoofing (DMG2000 Only) Description: Enables/disables spoofing in T.38. Allowed Values: • On = Enable T.38 spoofing. • Off = Disable T.38 spoofing. Default Value = On INI File Parameter Name = dspT38SpoofingEnable 3.10.3.4 TSI Removal (DMG2000 Only) Description: Determines if the Transmitting Subscriber Identification (TSI) is removed. Allowed Values: • On - Remove TSI from TDM to reduce packet delay. • Off - Include TSI in packet sent to packet network.
Parameter Reference INI File Parameter Name = dspT38NsfRemovalEnable 3.10.3.7 DIS Removal (DMG2000 Only) Description: Determines if the Digital Identification signal (DIS) is removed. Allowed Values: • On - Remove DIS from TDM to reduce packet delay. • Off - Include DIS in packet sent to packet network. Default Value = Off INI File Parameter Name = dspT38DisRemovalEnable 3.10.3.8 T.38 Packet Loss Concealment Method (DMG2000 Only) Description: Selects the packet loss concealment method in T.38.
Parameter Reference 3.10.3.11 Fax Transmit Level (dBm) (DMG2000 Only) Description: Set the FAX transmit level in T.38 FAX relay mode. Allowed Values: -15 to 0 Default Value = -10 INI File Parameter Name = dspT38FaxTransmitLevel 3.10.3.12 Maximum UDPTL Packet Size (DMG2000 Only) Description: Sets the maximum UDPTL packet size in bytes that the T.38 channel will transmit. Note: This does not include the IP header or UDP header. It only includes the UDPTL header and UPDTL payload.
Parameter Reference These call progress tones can be viewed and edited manually from the Web interface if the characteristics are known, or the Media Gateway can be directed to analyze and learn the characteristics of specific call progress tones. For more information on viewing, editing, learning, and validating call progress tones from the Web interface, see Chapter 4, “Working with Call Progress Tones”.
Parameter Reference Default Value = None INI File Parameter Name = cpToneEvent 3.11.3 Tone Name Description: Specifies the text name associated with this tone definition. Allowed Values: String with length between 0 - 31 characters Default Value = Empty string INI File Parameter Name = cpToneName 3.11.4 Cadence Type Description: Specifies the cadence type for this tone definition. Allowed Values: • Continuous = an "on" tone with no "off". • OnOff = an "on" cadence followed by an "off" cadence.
Parameter Reference the middle frequency is the second frequency, and the bottom frequency is the third frequency. A value of 0 means to ignore the entry. Allowed Values: 0-2000 Hz Default Value = 0 INI File Parameter Name = cpToneFreq 3.11.7 Tone Frequency Deviation Description: Specifies the deviation for the tone frequencies for this tone definition. Allowed Values: 0-200 Hz Default Value = 0 INI File Parameter Name = cpToneFreqDeviation 3.11.
Parameter Reference Allowed Values: 0-1000 ms Default Value = 700 INI File Parameter Name = cpToneTimeDeviation 3.11.10 Editing the INI File Directly The call progress tone parameters can be edited directly in the INI file if desired. In older versions of the INI file, 16 tone definitions were listed regardless of the number of actual tone definitions in use. In these older INI files unused tone definitions would have the cpToneEvent parameter set to none.
Parameter Reference the VoIP endpoint. This allows the gateway to send the CPID information as part of the initial callrequest to the VoIP endpoint. If this parameter is disabled, then the gateway will not answer the inbound TDM call until after the call-request is sent to the VoIP endpoint and the VoIP endpoint answers the call-request. In this case, the CPID information will not be part of the initial callrequest to the VoIP endpoint.
Parameter Reference • No = Media Gateway will not generate this informational message. Default Value = No INI File Parameter Name = gwInformUpdatedCallingNumber 3.12.4 Inform On No PBX CPID (Phone Emulating Only) Description: When this parameter is enabled (Yes), the Media Gateway will generate an informational VoIP message to the IP peer if no CPID information is available for the call within the prescribed time-out. Note: This parameter can only be changed in the configuration file.
Parameter Reference Default Value = 1 INI File Parameter Name = isdnOverlapRcvMinDigits 3.12.7 ISDN Overlap Receive Timeout (msecs) Description: Specifies the number of milliseconds before the call is answered when in overlap receive mode. Note: This parameter can only be changed in the configuration file. It is not accessible through the Web interface. Allowed Values: 0 to 65535 milliseconds Default Value = 14000 milliseconds INI File Parameter Name = isdnOverlapRcvToutMs 3.12.
Parameter Reference 3.12.10 Unauthenticated SRTP Enable Description: This parameter can be used to force Realtime Transport Protocol (RTP) packets to be received without authentication even if an authentication algorithm has been negotiated between parties. Note: This parameter can only be changed in the configuration file. It is not accessible through the Web interface. Allowed Values: • Yes = RTP VOICE packets will NOT be authenticated.
Parameter Reference Default Value = No INI File Parameter Name = srtpUnEncryptedSRTP 3.12.13 Wait for Dial Tone after Flash Hook Description: Indicate if the gateway should wait for dial tone after flash hook. Notes: 1. This parameter is only applicable to T1/E1 CAS. 2. This parameter can only be changed in the configuration file. It is not accessible through the Web interface.
Working with Call Progress Tones 4 Call progress tone parameters define the characteristics (frequencies, durations, and deviations) of the tones that the Dialogic® Media Gateway detects during call progress analysis. The following sections discuss how to view, edit, learn, and validate call progress tones using a Web interface: • Viewing and Editing Call Progress Tones. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135 • Learning and Validating Call Progress Tones . . . . . . . . .
Working with Call Progress Tones Use the following buttons on the Manual Tones Web page to manipulate call progress tones: Apply Changes button Saves changes to the configuration once the parameters have been edited. Add button Adds a row to the tone table, allowing a new tone definition to be added. Reset to Default Values button Deletes all existing tones and restores factory default tones. Export Tones Definitions button Exports the current tone definitions to an INI file.
Working with Call Progress Tones Figure 9. Learn Tone Web Page The Learn Tone user interface has the following components of interest: Acquire Tone field A check indicates that the corresponding tone event is to be learned or validated. Tone Event field Indicates one of four types: dialtone, busy, error, or ringback. Destination Address field Specifies the phone number or extension that when dialed will generate the call progress tone associated with the tone event.
Working with Call Progress Tones • Ringback – Call a valid extension not in use. Caution: Make sure that this extension is not forwarded on "no answer" and that it will ring until answered. Learn button Specifies that the Media Gateway will automatically learn the tone. Used when the frequency and timing information of a call progress tone are unknown. For more information on using the Learn feature, see Section 4.2.2, “Learning the Characteristics of Unknown Call Progress Tones”, on page 138.
Working with Call Progress Tones Figure 10. Learn Tone Progress Web Page Progress messages are described as follows: Learning The Gateway has gone off hook and dialed the destination address. It is collecting raw data on the call progress tone. Analyzing The Gateway is analyzing the raw data to extract the tone characteristics. Comparing The Gateway is comparing the new tones to existing tones and other new tones for possible conflicts.
Working with Call Progress Tones Figure 11.
Working with Call Progress Tones Figure 12. Learn Tone Results Web Page (Bottom) The learned tones are grouped into the following possible tone results on the Web page: • Tone Errors • Existing Tones • Unique Tones • Conflicting Tones After selecting the tones to be added to the tone definition table, the Apply button adds the selected tones to the tone definition table. The Manual Tones Web page discussed in Section 4.
Working with Call Progress Tones Not enough data The Gateway dialed the destination address but the data collected was not enough to extract tone characteristics. Action: Verify the destination address and ensure that the destination does not forward to another extension or that the destination is not answered.
Working with Call Progress Tones Learn Tone Issues and Possible Solutions When comparing tone definitions, both the frequency and timing need to be considered. To compare frequencies, both the frequency itself and the frequency deviation are needed. When a frequency is detected on the line, it is compared to the bandwidth of the tone definition.
Working with Call Progress Tones 4.2.5 Validating Call Progress Tones If the timing and frequency information is available and the desire is to only validate the information, then use the Validate Only button. The Media Gateway will dial a destination address where the call progress tone to be tested can be heard. The unit will then call each destination address and determine if the specified call progress tone is detected.
Working with Call Progress Tones Figure 13. Validate Tone Progress Web Page The message, Validating, means that the Gateway is redialing the destination addresses and testing to see if the call progress tone definitions can detect the tones. The Cancel button cancels the current session and returns to the Learn Tone Web page. 4.2.7 Validate Tone Results Web Page When the Media Gateway has finished validating the tones, a results page, shown in Figure 14 and Figure 15, will be displayed.
Working with Call Progress Tones Figure 14.
Working with Call Progress Tones Figure 15. Validate Tone Results Web Page (Bottom) The validated tones are grouped into the following tone results: • Validation Errors • Validated Tones After viewing the validation results, you can return to the Manual Tones Web Page (see Figure 8) by clicking on the Return to Tone Configuration link. Validation Errors An error occurred when trying to validate the tones listed in this section.
Working with Call Progress Tones Validated Tones The tones listed in this section were successfully validated.
5 Dial Plan Information about dial plan and how it is supported by the Dialogic® Media Gateway is described in the following sections: • Dial Plan Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149 • CPID (Number) Matching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152 • Channel Pools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Dial Plan Figure 16. VoIP to TDM calls Calling Number: 101 Calling Number Dial Plan Called Number: 8675309 VoIP Address: 172.16.3.131 Called Number Physical TDM channel The dial plan configuration will determine what calling and called numbers are sent to the TDM device, as well as the physical TDM destination. 5.1.2 TDM to VoIP Calls Calls originating from the TDM interface have a physical source, along with calling, called, and redirect number information.
Dial Plan 5.1.3 Determining the Call Destination The dial plan uses four tables configured by the user to determine the final destination. • The "Channel Pool" table creates a logical grouping of interfaces and channels that define the physical interface for the TDM side of the call. • The "CPID Manipulation" table is used to create a set of formulae used to establish the calling, called, and redirect numbers for the destination call.
Dial Plan 5.2 CPID (Number) Matching Part of the criteria for matching the characteristics of an incoming call to a rule in one of the dial plan routing tables is number matching. The incoming calling or called number is tested against a match rule defined in the routing table. If the match fails, this routing rule table entry will fail. The formula for number matching gets entered via the dial plan configuration in the "Inbound VoIP Call Routing" Web page and the "Inbound TDM Call Routing" Web page.
Dial Plan Table 3. TDM Interface Types Maximum number of supported Interfaces Gateway Type 5.3.3 Number of supported Channels per interface Analog 8 1 Digital (PBX) 8 1 T1 - CAS 4 24 T1 - ISDN 4 23 E1 4 30 Channel Selection Mode It is often desirable to select a method for choosing which channel within a channel pool is used to place an outgoing TDM call. The channel pool configuration uses a channel selection mode configuration option for this.
Dial Plan Select - Click anywhere in this column to select an entry. A selected row may be moved up or down in the table, or deleted. Label - Label for this entry. This label is referenced in the "Inbound VoIP Routing" and the "Inbound TDM Routing" configuration pages. Interface Range - The 1-based physical interface(s) assigned to this channel pool. Numbers can be entered in the form #,# to select individual interfaces, or #-# to select a range of interfaces, or a combination of both.
Dial Plan Table 4. Syntax Used for CPID Manipulation (Continued) Rule Syntax 5.4.2 Description Example Example Result I Inbound VoIP address I 172.16.3.
Dial Plan Calling Party Change Rule - The formula as specified in the section above that determines the calling party number of the outgoing call. Called Party Change Rule - The formula as specified in the section above that determines the called party number of the outgoing call. Redirecting Party Change Rule - The formula as specified in the section above that determines the redirecting party number of the outgoing call. See Section 5.
Dial Plan Select - Click anywhere in this column to select an entry. A selected row may be moved up or down in the table, or deleted. Label - Label for this entry. This label is used only to help identify the rule to the administrator. It is not used by any other tables in the dial plan configuration. Enable - Check this box to enable the rule. If this box is not checked, this rule is not checked for incoming calls. Host - The string to match the host address of the incoming call.
Dial Plan Figure 22. Inbound TDM Call Routing Configuration Web Page Select - Click anywhere in this column to select an entry. A selected row may be moved up or down in the table, or deleted. Label - Label for this entry. This label is used only to help identify the rule to the administrator. It is not used by any other tables in the dial plan configuration. Enable - Check this box to enable the rule. If this box is not checked, this rule is not checked for incoming calls.
Dial Plan • To change a rule, edit any of the fields in a row. • To delete a rule, click the row on the left side in the "select" area. The background of the row will change color as in the example below. Once the row has been selected, click the "Delete Selected Row" button to delete the row. • Since rules are processed top down, it may be necessary to move a rule either up or down in the table. To do this, select the row, and then press one of the "Move Selected Row" buttons.
Dial Plan Figure 24. Inbound VOIP Input and Output Data Figure 25.
Dial Plan 5.9 Implementation Example 5.9.1 Route an Incoming TDM Call based on the Calling and Called Number Figure 25 represents a real world scenario where a gateway would be used to route an incoming TDM call to a different VoIP endpoint based on the calling and called numbers. Figure 26. Route an Incoming TDM Call to a Different VoIP Endpoint New York Distributor 10.20.30.212 Flowers Agent Cookies Agent A 212-867 -5309 B Public Telephone Network Gateway 1.2.3.
Dial Plan Figure 27. Setting Up the CPID Manipulation Rules 2. Set up the TDM to VoIP routing rules. Calls from the 212 area code route to the New York Distributor. Calls from the 716 area code route to the Buffalo Distributor. Calls from the 315 area code route to the Syracuse Distributor. Compare the first 4 digits of the incoming calling number to determine the VoIP address of the distributor. The table would look like this: Figure 28.
Media Gateway Parsers 6 This section describes the Dialogic® Media Gateway in-band Type I (on-hook) and Type II (offhook) integration parsers for analog and T1 CAS integrations, and the display parsers for digital integrations. These parsers allow the user to define the meaning of either the in-band/on-hook integration strings or display strings received from the telephony network. For this discussion, the term parser will be used when referencing all three variants listed above.
Media Gateway Parsers Figure 29. Default Analog CPID Configuration Data on Analog Web Page 6.2 Parsing Configuration Syntax The configuration data syntax is used to describe the type I or II CPID (analog or T1 CAS) or display (digital) strings that may be received from the telephone network. The type of information that can be received using analog DTMF integrations is a subset of that which can be gleaned from digital displays.
Media Gateway Parsers Figure 30. Default Analog CPID Configuration in the .ini File ;******************** PBX IP Media Gateway ***************** ;Version Information: ;MAC:00-a0-e6-06-05-07 ;IP:10.0.1.41 ;DSP Firmware: |9.1w/Fax|FRI MAY 02 17:59:51 2003| ;DSP Firmware (ROM): 9.1 w/Fax|FRI MAY 02 17:59:51 2003 ;Main Board Boot (ROM): |4.
Media Gateway Parsers Figure 31. Sample Analog Type II CPID Configuration Data in the .
Media Gateway Parsers Figure 32. Default Mitel Digital CPID Configuration Data (cpid.htm) The parser attempts to match an input integration or display string to a rule defined by the configuration data. If a match is made, the parser uses the call-party, reason code, and origin specifiers of the matching rule. In this manner, the parser can extract the call party information from the correct locations of the integration or display strings. 6.2.
Media Gateway Parsers 6.2.2 Call Class Rules On a telephone network, there can be several different string formats for call information. Integration or display strings which use the same format are said to be in the same "Call Class". That is, two integration or display strings can be parsed using the same rules if they are in the same call class. If an integration or display string cannot be parsed using the same rules, then a new call class must be declared.
Media Gateway Parsers [A1500*300#] the rule might read: rule A1\d(0-10)\*\d(0-10)*# dst_number 1 src_number 2 reason no-answer This means that when the regular expression is satisfied, the first digits string is the destination number, the second digit string is the source number, and the reason code is 'no-answer'. In order to describe the display: [a= JOE 123 to BILL 456 b] the rule might read: rule .
Media Gateway Parsers Table 6. Parser Reason Codes Reason String Used by Media Gateway no-answer Call is tagged as a forwarded on no-answer call. busy Call is tagged as a forwarded on busy call. direct Call is tagged as a direct call. fwd-all Call is tagged as a forwarded all call. disconnect Call is disconnected. Any other call reason token specified in a rule will cause the Media Gateway to ignore the received string (if the received string matches the rule).
Data Security 7 Information about data security and how it is supported by the Dialogic® Media Gateway is described in the following sections: • Data Security Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 • Secure HTTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 171 • SIP Call Control Security using TLS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Data Security HTTPS requires two actions by the user: • Both the Media Gateway and the PC on which the Web browser used to connect to the Media Gateway via HTTPS is running must be configured with the proper certificate. • When accessing the Media Gateway, use https:// instead of the non-secure http:// followed by the Media Gateway's URL. This section includes the following information about HTTP security: • HTTPS Certificate Configuration • HTTPS Example 7.2.
Data Security get lengthy if the PC/Web Browser needs to communicate with a number of Media Gateway units. On the other hand, CA signed certificates require time and effort to install since the certificates must be signed by a CA. However, once you have the signed certificate, the CA root certificate can be used to communicate with multiple Media Gateway units. 7.2.2 HTTPS Example An example of how HTTPS is used with a self-signed certificate is described below.
Data Security carries SIP data in a secure way by encrypting the data and authenticating the transport connections. Authentication guarantees that you are talking to the intended peer. 7.3.1 TLS Certificate Configuration A TLS certificate can be self-signed or certificate authority (CA) signed. A self-signed certificate can be generated by the Media Gateway. CA signed certificates must be requested by the Media Gateway and signed by a CA.
Data Security number other than the default, specify the number. The Media Gateway will then communicate this number to peers via URI. • TLS Cipher List - The Cipher list is not a configurable parameter. The Media Gateway supports 6 ciphers in a list but cannot be changed. Valid OpenSSL ciphers can be found at: http://www.openssl.org/docs/apps/ciphers.html A default cipher list must be specified for TLS to work. The Media Gateway uses the default: ALL:!ADH:!LOW:!EXP:!MD5:@STRENGTH.
Data Security • Verify TLS Peer Certificate date: No • Verify TLS Peer Certificate trust: No Example 2: Assume a company has five sites: one in Indiana, one in Illinois, one in California, one in New York, and one in Washington. Each of these sites uses a local telephone company. People at different sites frequently call each other. They have decided to use VoIP service with one Media Gateway at each site. They also use one media server. A CA signed certificate, which will expire in 1 year, is used.
Data Security request secure audio and will reject all requests for non-secure audio. If SRTP_Preferred is specified, the gateway will request both secure audio and non-secure audio, with a preference for secure audio, and the gateway will accept requests for both secure and non-secure audio. If RTP_Only is specified, the gateway will only request non-secure audio and will only accept requests for non-secure audio. Note: SRTP_Preferred is not supported in Version 5.1 SU2 Software.
Data Security • MKI: Not supported • KDR: Not supported The Media Gateway should be configured as follows: • SRTP Preference: SRTP Only • Cipher Mode: AES Counter Mode • Authentication Type: SHA1 • Authentication Tag Length: SHA1 32 bits or 80 bits • Master Key Index (MKI) on Transmit Stream: No • Key Derivation Enable: No • Key Derivation Rate (KDR): Not applicable Example 2: In this example, the Media Gateway is talking to an IP phone that does not support security: • SRTP Preference: RTP Only • Master
Data Security Figure 33. Storing Self-Signed Certificate by Certificate Import Wizard 11. If the Certificate store is not Trusted Root Certification Authorities, use the Browse button to locate it. 12. Click Next. 13. Click Finish. 14. Click Yes. 15. Click the OK button. 16. Close the windows and Internet Explorer.
Data Security 180 Dialogic® 1000 and 2000 Media Gateway Series User’s Guide — September 2007 Dialogic Corporation
Unit Status 8 Status information about the Dialogic® 1000 Media Gateway (DMG1000) and Dialogic® 2000 Media Gateway (DMG2000) units can be obtained through the Web interface. The DMG1000 Status and DMG2000 Status Web pages allow an administrator to view the number of calls processed by the unit as well as a log of all calls (with call party information). The Media Gateway supports SNMP Version 1. The Media Gateway-specific SNMP MIB can be downloaded from the unit using the Web interface. The MIB file dmg.
Unit Status 8.2 Alarm Information Selecting Alarm from the Status menu displays the following types of alarm information: • Time- Timestamp of alarm entry. • ID - Identifier of alarm entry. • Severity - Severity Level of alarm entry. • Description - Text Description of alarm entry. • Port - Port Number of alarm entry. • Text Message - Text message of alarm entry. Clicking on the Clear Alarms button will clear all alarm information. 8.
Unit Status 8.4 Telephony Status Information Selecting Telephony from the Status menu displays information about the state of each PBX port that connects to the Media Gateway. For each port, the following status information is provided: • State (DMG1000): – In Service – No Link – Red Alarm – Yellow Alarm – Pend D-Chan – n/a • State (DMG2000): – In Service – No Link – Red Alarm – Yellow Alarm – Pend D-Chan – n/a Note: 8.
Unit Status • SNMP: 8.5.1 Records error statistics for SNMP protocol datagrams. SNMP Agent The gateway SNMP agent is v1/v2c compatible. The agent provides read-only access to the gateway's configuration and status data. The gateway does not support SNMP write commands since SNMP v2 does not provide secure communications. You can configure the gateway through a Web browser using HTTP (or HTTPS when secure communication is required). The SNMP agent provides GET, NEXT, BULK GET and V1 trap PDU's.
Unit Status 8.5.2 Supported MIBs 8.5.2.1 RFC 1213 MIB-II The gateway supports RFC 1213 MIB-II titled "Management Information Base for Network Management of TCP/IP-based Internets: MIB-II". The RFC is available on numerous Web sites. A few are: • http://www.faqs.org/rfcs/rfc1213.html • http://tools.ietf.org/html/rfc1213 • http://www.rfc-archive.org/getrfc.php?rfc=1213 The Defense Data Network Network Information Center (DDN NIC) is the primary repository for RFCs. Hard copies can be obtained from them.
Unit Status Table 7. Gateway Specific MIB OID 186 Name Position Type
.3 status Node
.3.1 .numCurrentCalls Leaf Integer
.3.2 .numEthernetConnectionLosses Leaf Integer
.3.3 .numInboundIpCalls Leaf Integer
.3.4 .numInboundPbxCalls Leaf Integer
.3.5 .numIpToPbxCalls Leaf Integer
.3.6 .numPbxToIpCalls Leaf Integer
.3.7 .numPeerConnectionLosses Leaf Integer
.3.8 .numTelephonyCarrierLosses Leaf Integer
.3.9 .
Unit Status Table 7. Gateway Specific MIB OID Name Position Type
.5.1.1.4 …callLogEndTime Leaf TimeTicks
.5.1.1.5 …callLogEndReason Leaf Octet String
.5.1.1.6 …callLogInboundInfo Leaf Octet String
.5.1.1.7 …callLogOutboundInfo Leaf Octet String 8.5.3 SNMP Alarms Gateway alarms are reported as SNMP traps. They can also generate an e-mail as described in Section 8.5.3.1, “Alarm E-Mails”, on page 189. Table 8 maps an alarm severity index to a severity level.
Unit Status Table 9.
Unit Status Table 9.
Unit Status Figure 35. E-mail Parameters in Traps and Alarms Section of Gateway Advanced Web Page E-Mail Alarms Enabled: Set to yes to generate alarm e-mails E-Mail Minimum Alarm Severity: The gateway has three levels of alarms: Info, Warn and Error, where Info is the lowest level alarm and Error is the highest. This field specifies the lowest level that generates e-mails. Destination E-Mail List: A list of e-mail addresses, separated by semi-colons, to which the alarm e-mails are sent.
Unit Status Sample E-Mails Figure 36 shows the e-mail sent when the gateway powers up. This is an info alarm. Figure 36. Sample Info Alarm E-Mail Figure 37 shows the e-mail sent when a port loses communication with the PBX. Notice that the associated physical port is shown. This is a warn alarm. Figure 37. Sample Warn Alarm E-Mail Figure 38 shows the e-mail sent for a software fault, more specifically a SW Watchdog Timer Expiration. Notice that it has a more detailed description. This is an error alarm.
Unit Status Figure 38. Sample Error Alarm E-Mail 8.6 Version Information Selecting Version from the Status menu displays version information about the Media Gateway software and hardware. Note: The firmware version information displayed will vary, depending on the Media Gateway model.
Unit Status 8.7 Diagnostics Information Selecting Diagnostics from the Status menu displays diagnostics information about the Media Gateway. Refer to Chapter 9, “Diagnostics” for detailed information about the Media Gateway diagnostic capabilities.
Unit Status 194 Dialogic® 1000 and 2000 Media Gateway Series User’s Guide — September 2007 Dialogic Corporation
Diagnostics 9 This chapter describes how to perform diagnostics tasks on the Dialogic® 1000 Media Gateway (DMG1000) and Dialogic® 2000 Media Gateway (DMG2000) units and includes the following sections: • VoIP Interface Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 195 • PBX/PSTN Interface Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 199 • PBX Self Verification Test . . . . . . . . . . . . .
Diagnostics 9.1.1.1 Features Currently the VoIP interface diagnostic provides the ability to: • Originate a VoIP call to a specified endpoint address and verify endpoint response. • Send a message waiting notification status update request and verify endpoint response. 9.1.1.2 Location The VoIP interface diagnostic tool is only part of the suite of diagnostic utilities that can be used to assist in recording, testing, and resolving configuration or compatibility issues.
Diagnostics Figure 40. VoIP Interface Web Page 9.1.2.1 Configuration Options The following configuration items are available to be modified by the user: Test Selection Choose the type of diagnostic test to perform. Available options are Initiate Call and Send Message Waiting Status. Destination VoIP Address The required address of the VoIP endpoint that the diagnostic test will use when attempting to establish a connection. If this configuration is empty the diagnostic test will not be performed.
Diagnostics When the test is completed a hyperlink will be displayed to allow the user to return to the VoIP Interface Test configuration Web page. Figure 41. VoIP Interface Test Status Web Page When the test is completed the results will show if the diagnostic test was able to establish a VoIP connection with the specified Destination VoIP Address.
Diagnostics 9.1.2.3 Call Log The test results from the VoIP interface diagnostic tool are also stored in the Media Gateway call log. The Source field will contain From Test App to indicate that the connection was created by a diagnostic application. The call log is accessible through the Web by selecting the Call Log link on the left side menu of any Web page. Figure 42. VoIP Interface Call Log Web Page 9.
Diagnostics Figure 43. PBX/PSTN Interface Diagnostic Test 9.2.1.1 Features Currently the PBX/PSTN interface diagnostic provides the ability to: • Originate a PBX/PSTN call to a specified endpoint address and verify endpoint response. • Send a message waiting notification status update request and verify endpoint response. 9.2.1.
Diagnostics To start the specified diagnostic test, press the Start Test button on the Web page. Note: Executing the PBX/PSTN interface diagnostic tool temporarily disables gateway functionality. Any active connections will be released. Figure 44. PBX/PSTN Interface Web Page 9.2.2.1 Configuration Options The following configuration items are available to be modified by the user: Test Selection Choose the type of diagnostic test to perform.
Diagnostics Source Number The number representing the source party that is delivered to the destination endpoint during the diagnostic test. This is an optional field that is not required to perform the diagnostic test. Messages Waiting Status Choose the status value of the message waiting notification update. This field is only valid when the Message Waiting diagnostic test is selected. 9.2.2.
Diagnostics Device Not Available PBX/PSTN interface is not in-service User Busy Destination number is busy (in-use) User Not Found Destination number not found at PBX/PSTN endpoint If an error occurs some other suggestions are: • Verify gateway PBX/PSTN interface is in-service and configured properly. • Verify destination PBX/PSTN endpoint is valid and in-service.
Diagnostics 9.3.1 PBX Self Verification Test Overview The PBX self verification diagnostic tool is a Web page user application that can be used to provide verification of PBX compatibility and also to confirm the Media Gateway configuration values relating to the PBX interface are valid. Figure 47. PBX Self Verification Diagnostic Test 9.3.1.
Diagnostics 9.3.1.2 Restrictions The PBX self verification diagnostic is currently only available on PBX interfaces and protocols that allow the interfaces and channels to be individually assigned extension numbers and allows outbound and inbound call routing from one interface and channel to another. Note: 9.3.1.3 The PBX self verification diagnostics is not available on any ISDN protocol.
Diagnostics 4. Select the Test Mode to be Sequential or Simultaneous (this is an optional parameter for the test). Note: The Send Message Waiting Status diagnostic tests are always executed in Sequential mode due to possible load issues of the PBX under test. To start the specified diagnostic test, press the Start Test button on the Web page. Note: Executing the PBX/PSTN interface diagnostic tool temporarily disables gateway functionality. Any active connections will be released. Figure 48.
Diagnostics Test Selection Choose the type of diagnostic test to perform. Available options are Initiate Call / Answer Call, Transfer Call and Send Message Waiting Status. Test Mode Select the execution mode of the diagnostic test to be either Simultaneous or Sequential. Sequential test mode executes only a single diagnostic test at one time. The next diagnostic test will not start until the previous test has completed. Simultaneous test mode executes as many diagnostic tests at once as possible.
Diagnostics Initiate Call / Answer Call and Transfer Call The call flow of the Initiate Call / Answer Call and Transfer Call diagnostic test tries to verify not only the operation of originating an outbound call and answering an inbound call, but transferring the call as well. These tests also include verification of outbound call progress, inbound CPID, send/receive DTMF and disconnect supervision. Figure 50.
Diagnostics Figure 51. Call Flow for Send Message Waiting Status 9.3.2.3 Test Status When a diagnostic test is executed the test results are shown in the PBX Self Verification Test Status table on the Web page. Test Result Symbol Description - Test skipped because not configured or not available (no capability, not enabled, or not in-service). n Test was pending but did not execute because a failure occurred.
Diagnostics Figure 52. PBX Self Verification Test Status Web Page 9.3.2.4 Test Results After the diagnostic test(s) are completed or canceled the test results can be opened or saved to a text file (.txt) for documented proof of the verification process. To open the test results in another Web browser window click the pbxtest.txt hyperlink.
Diagnostics Figure 53. PBX Self Verification Test Results 9.3.2.5 Test Failures If a failure occurs some suggestions are: • Verify PBX interface is in-service and configured properly • Verify gateway is configured for specific PBX interface (is there a default .ini file) • Run the test again with a minimum number of extensions configured and in Sequential test mode.
Diagnostics Test Failure Reasons Originate an outbound PBX call • The extension numbers for the PBX interface are not correct. • The PBX interface and channel are not configured properly*. • Dial tone is not detected or being provided. Answer an outbound PBX call • The extension numbers for the PBX interface are not correct. • The PBX interface and channel are not configured properly*.
Diagnostics Figure 54. PBX Self Verification Call Log Web Page 9.4 Diagnostic Logging The following is an overview describing the diagnostic logging capabilities of the Media Gateway and includes the following sections: • Overview • Debug Trace Capture • Network Capture • TDM Capture 9.4.1 Overview The Media Gateway provides the user with the ability to record, in real-time, diagnostic information. This information can then be transferred to a PC for off-line analysis of problems.
Diagnostics • TDM Capture: The TDM log is a copy of the voice data transferred on the T1/E1 line. It is available only on the DMG2000. To view a log you must transfer the log to a PC. When transferred to a PC, each log is formatted into an industry standard to facilitate viewing and sharing of data. The format for each log is: • Debug Trace Capture: Uses an ASCII text format (.TXT) • Network Capture: Uses an Ethereal format. Ethereal is a freeware program downloadable from the Internet.
Diagnostics • The Media Gateway stores the logs in RAM. Therefore, the logs are not preserved if the unit is reset or powered down. To save a log you must transfer it to a PC. • Special applications are not required to download logs from the Media Gateway to a PC, but are required to view the logs. • All control of logging is through the Web interface. 9.4.2 Debug Trace Capture The Debug Trace Capture enhances the trace mechanism described in Section 9.6, “Trace Mechanism”, on page 223.
Diagnostics Figure 56 shows the default trace keys (i.e. immediately after power-up). Notice the Error and Debug trace masks are not shown as they are always enabled. To use the Debug Trace Capture, first check the appropriate trace masks. Click Apply Masks and then click Start Logging. Logging starts and the display changes to show the state of the log. An example of a running log is shown in Figure 57. Figure 57.
Diagnostics The log can be transferred to a PC by right-clicking Download trace.log file. Doing this brings up a File Download dialog box as shown in Figure 58. Select Save to save the file to your PC. After saving, you can view the file using most any ASCII text editor, such as Wordpad or Notepad. Figure 58. File Download Dialog Box for Trace.log Important points to remember about Debug Trace Capture are: • After modifying the trace keys be sure to click Apply Masks.
Diagnostics The DMG2000 unit has three network interfaces: • DSP: an internal network that connects the DMG2000 DSP to the DMG2000 CPU • LAN1: an external network that connects the DMG2000 to a network (VOIP) • LAN2: an external network that connects the DMG2000 to a network (non-VOIP) Notes: 1. The DMG1000’s LAN1 is equivalent to the DMG2000’s LAN1. 2. Currently, LAN2 is only supported in Version 5.1 SU1 Software or later. The Network Capture is controlled from the Media Gateway's Web interface.
Diagnostics Figure 60. Example of Running Log - Network Capture When the Network Capture is running, the fill level of the log is displayed. The log uses a circular buffer, so when it reaches capacity, new data overwrites the old. Once the log reaches capacity the fill level does not change. The log can be transferred to a PC by right-clicking Download iplog.pcap file. Doing this brings up a File Download dialog box as shown in Figure 61. Select Save to save the file to the PC.
Diagnostics Important points to remember about Network Capture are: • Downloading does not require any special software, but viewing requires Ethereal. • On the Network Capture Web page, checking a protocol type causes it NOT to be captured. • After selecting protocol filters, be sure to click Apply Filters. • Size of the log is determined at startup. DMG1000 ~1.1 Mbytes, DMG2000 ~24 Mbytes. • Downloading the Network Capture clears the log and starts another.
Diagnostics To use the TDM Capture, enter the Channel Number to capture, select either RX or RX & TX, then click Start Capturing. Logging begins and the display changes to show the state of the log. An example of a running log is shown in Figure 63. Figure 63. Example of Running Log - TDM Capture While the TDM Capture is running, the fill level of the log is displayed. The log is a circular buffer, so when it reaches capacity, new data overwrites the old.
Diagnostics Important points to remember about TDM Capture are: • For proper downloading you must right click on Download tdmlog.wav file. Note: A right click is necessary due to the Windows® OS mapping the .wav extension to Windows Media Player. Said mapping results in a left click automatically bringing up Windows Media Player, which does not allow for saving a file. • TDM capture occurs regardless of channel call state.
Diagnostics 3. Press the Enter key repeatedly until the following prompt appears: PIMG> 4. At the prompt, type pwd and press Enter. 5. When prompted, enter the password for the admin user (the default is IpodAdmin) and press Enter. The Media Gateway will respond with Admin level accepted, and then display the prompt. You may now issue terminal commands to the Media Gateway. 9.5.
Diagnostics Traces that are related to a telephony port number are tagged with the 1-based telephony port number to which they are related.
Diagnostics 9.6.2.1 Trace Key The trace key defines the specific sub-system within the Media Gateway to trace. For example, if you are only interested in capturing SIP packets (SIP Emulating or SIP Driving mode), you would use the VoIp trace key: trace voip on Table 11 describes all trace keys supported by the trace function as well as the trace types available to each trace key.
Diagnostics Table 11. Supported Trace Keys Trace Keys Description Prot Code Error Warn Init Alarm ● ● ● ● ● Event System OS-Independent layer, System initialization Tel Digital Telephony Interface (for protocol, hook, lamp, display, CPID, in phone-emulation and phonedriving etc.) ●(8) ● ● ● ● ● ●(6) TelDrv Low layer ISDN trace coming from the Telesoft driver. Includes the RAW ISDN layer 3 packets.
Diagnostics Table 11.
Diagnostics Table 12. Supported Trace Types Trace Types Trace Description Prot Protocol Code Software/Code Error Errors (1) Warn Warnings Init Software/Device initialization (1) Alarm Alarms (1) Event Hookswitch, Lamps, Tones, Displays, Button Presses Stat Statistics (1) System starts with these enabled on all trace keys. 9.6.
Diagnostics Pbn VoIP Gw Gcc Adept teldrv CallLog Log Error Error Error Error Error Error Error Error Init Init Init Init Init Init Init Init Debug Debug Debug Debug Debug Debug Debug Debug Channel Trace State ('*' enabled, '-' disabled) -----------------------------------------------* * * * * * * * 9.6.3.2 trace default The trace default command sets the default tracing of all trace keys, and enables VoIP and telephony event tracing. PIMG>trace default 9.6.3.
Diagnostics 9.6.3.5 trace reset This command resets specified (or all) trace keys to their defaults (from system start). 9.6.3.6 trace all off This command disables all traces, except Error and Debug, on all trace keys. Error and Debug cannot be disabled. 9.6.3.7 trace port <1-based port number|all> This command enables or disables port-related traces.
Diagnostics 002:59:314 002:59:550 002:59:552 003:02:300 003:02:372 003:02:490 003:02:570 [Tel-2 [Tel-2 [Tel-2 [Tel-1 [Tel-2 [Tel-1 [Tel-2 ] ] ] ] ] ] ] Event Event Event Event Event Event Event Lamp 60:CallApp0:0 OFF->FLASH 0:0:48 | 251 Cpid (251->) (Direct) Lamp 60:CallApp0:0 FLASH->OFF Lamp 60:CallApp0:0 FLASH->OFF 0:0:48 | MAY 13 7:44 P 0:0:48 | MAY 13 7:44 P | | | Example 2 Enable tracing of SIP messages: PIMG>trace voip prot on Ok PIMG>exit Good-Bye.
Diagnostics [VoIP ] Prot [VoIP ] Prot ---->SIP/2.0 100 Trying! [VoIP ] Prot Via:SIP/2.0/UDP 10.0.1.110:5060! [VoIP ] Prot Call-ID:01B2270D9C81400000000006@pbxgw.default.com! [VoIP ] Prot CSeq:1 INVITE! [VoIP ] Prot From:"250";user=phone;tag=1A1F32463135364100000ABE! [VoIP ] Prot To:sip:101@10.0.1.215;tag=3246313536412A29002455E5! [VoIP ] Prot Contact:! [VoIP ] Prot Server:DMG1000 1.
Diagnostics [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1
Diagnostics [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 [DspCpi-1 ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] ] Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Stat Error Stats: invalid_header_count: to_micro_overflow_count: lost_enh_packet_count: no_core_packet_count: pkt_lost_by_network: rc4key_update
Diagnostics 9.7 Diagnostic Commands This section describes a number of diagnostic commands and includes: • Devstat Command • Restart Command • Ping Command • Ver Command • Alarm List Command 9.7.1 Devstat Command The Devstat command displays the current high-level settings of the unit and the unit's main status and telephony port status. The telephony port state can be 'In Service', 'Out of Service', or 'Active'. 'Active' means that the port is off-hook.
Diagnostics PIMG>ping 10.0.1.1 10.0.1.1 is alive PIMG>ping 10.0.1.1 5 PING 10.0.1.1: 56 data bytes 64 bytes from 10.0.1.1: icmp_seq=0. time=2. ms 64 bytes from 10.0.1.1: icmp_seq=1. time=0. ms 64 bytes from 10.0.1.1: icmp_seq=2. time=0. ms 64 bytes from 10.0.1.1: icmp_seq=3. time=0. ms 64 bytes from 10.0.1.1: icmp_seq=4. time=0. ms ----10.0.1.1 PING Statistics---5 packets transmitted, 5 packets received, 0% packet loss round-trip (ms) min/avg/max = 0/0/2 PIMG>ping 10.10.10.10 no answer from 10.10.10.10 9.
Index A Advanced Call Routing Subgroup 68 alarm information 182 alarms command 236 Analog parameters 55 CPID Group 59 Feature Codes Group 57 Message Waiting Control Group 59 Timing Group 55 Analog Web page 31 Audio Subgroup 74 B basic configuration via the serial port 36 C call class rules 168 reason tokens 169 regular expressions 168 rule order 169 rule syntax 168 call log status information 182 call progress tones characteristics 135 editing 135 editing INI file directly 129 learn tone issues 143 Learn
call routing un-routable calls 27 changing the password 37 configuration information exporting 39 importing 39 configuration options 163, 171 configuration procedure 37 configuration syntax 164 configuration via the serial port 36 connecting to terminal interface via Diagnostics connector 222 connecting to terminal interface via LAN connector 223 control of log files 214 CPID Group parameters 59 CPID Parsing Configuration 125 D debug trace capture 215 Description 72, 73 devstat command 235 diagnostic loggi
G Gateway parameters 66 Gateway Advanced group 68 Gateway Capabilities group 86 Gateway Routing group 66 Gateway Web page 32 H H.323 parameters 99 H.
N network capture 217 Non-Menu (Hidden) parameters CPID Parsing Configuration 125 DSP Advanced Group 113 O online Help 33 operating modes phone emulating 22 overview diagnostic logging 213 P parameter categories Analog 55 Call Progress Tone 125 Gateway 66 H.
parameters Analog Interface Type 60 Audio Compression 74 Authentication Tag Length 50 Authentication Type 50 Backup Proxy Server Address 111 Backup Proxy Server Port 111 BOOTP Enabled 42 Cadence Type 127 Call as Domain Name? 104 Call Connect Mode 69 Call Monitor Interval 70 Call Party Delay 71 Call Progress Filter Debounce 117 Call Progress Filter High Cutoff 117 Call Progress Filter Low Cutoff 117 Call Progress Filter Percent 117 Call Progress Filter SNR in dB 118 Call Progress Filter Threshold 116 Call Pr
Gateway Prefix 101 H.
Proxy Query Interval 111 QOS Precedence 78 QOS Type of Service 79 Registration Expiration 106 Registration Server Address 106, 108, 109, 110, 129, 130, 132, 134 Registration Server Port 106 Ring Cycle Time 90 Ringing Timeout 56, 90 RTP Digit Relay Mode 74, 75 Selects Transmit Pulse Waveform 89, 95, 98 Send DNIS to VoIP Endpoint 69 Serial CPID Expiration 66 Serial Interface Protocol 63 Serial Mode (Master/Slave) 63 Serial Port Baud Rate 53, 54 Serial Port Data Bits 53, 55 Serial Port Parity 53, 54 Serial Por
parsing call class rules 168 display translation descriptors 167 password changing 37 Password Web page 32, 37 phone emulating 22 ping command 235 Port Capabilities parameters 86 procedures basic configuration via the serial port 36 changing the password 37 configuring the IP Media Gateway 37 exporting configuration information 39 importing configuration information 39 setting the IP address 35 upgrading the software 40 product description 21 Q Quality of Service Subgroup 77 R reason tokens 169 regular ex
status alarm information 182 call log information 182 MIB-II information 183 summary information 181 telephony information 183 version information 192 summary information 181 Summary Web page 36 System Group parameters 51 System parameters 51 Serial Port, COM1 Group 52 Serial Port, COM2 Group 54 System Group 51 Telephony Group 51 System Web page 31 T T1 CAS Protocol Group parameters 88 T1 ISDN Protocol Group parameters 93 T1/E1 Mode Group parameters 87 T1/E1 parameters 87 E1 Configuration Group 96 T1 CAS P
trace command and display examples example 1, tracing telephony events 230 example 2, tracing SIP messages 231 example 3, tracing RTP statistics 232 example 4, tracing telephony protocol 234 trace commands 228 trace 229 trace all 229 trace all off 230 trace default 229 trace -l 230 trace port 230 trace reset 230 trace show 228 trace time 230 trace default command 229 trace format 224 trace function 223 trace key 225 trace -l command 230 trace mechanism trace format 224 trace function 223 trace utility 224 t
W Web interface 29 Web page Analog 31 Gateway 32 H.
