Subscribe to Our Youtube Channel
Related Manuals for Dialogic 1000
Summary of Contents for Dialogic 1000
- Page 1 ® Dialogic 1000 and 2000 Media Gateway Series SIP Compliance (Version 6.0 SU8 Software) September 2011 05-2666-004 www.dialogic.com...
- Page 2 Copyright and Legal Notice Copyright © 2008-2011 Dialogic Inc. All Rights Reserved. You may not reproduce this document in whole or in part without permission in writing from Dialogic Inc. at the address provided below. 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 Inc.
-
Page 3: Table Of Contents
® Dialogic 1000 and 2000 Media Gateway Series SIP Compliance Table of Contents Scope ......................7 References ..................... 8 Configuration Parameters ................9 Configuration INI Parameters ................9 Configuration XML parameters ................ 14 General ......................19 VOIP to TDM Connect Determination ............... 19 SDP Usage .................... - Page 4 ® Dialogic 1000 and 2000 Media Gateway Series SIP Compliance VOIP to TDM Success with Early Media ............53 VOIP to TDM Failure – Call Un-Routable ............54 VOIP to TDM Failure – Call Canceled ..............55 VOIP to TDM Failure – TDM Channel Unavailable ..........56 VOIP to TDM Failure –...
- Page 5 ® Dialogic 1000 and 2000 Media Gateway Series SIP Compliance INVITE Authentication Success – Gateway is UAS ........... 108 INVITE Authentication Failure – Gateway is UAS ..........109 Register Authentication Success – Gateway is UAC .......... 110 Calling ID Privacy ..................111 Gateway Configuration ................
-
Page 6: Revision History
® Dialogic 1000 and 2000 Media Gateway Series SIP Compliance Revision History Revision Release date Notes 05-2666-004 September 2011 Version 6.0 SU8 Software Last modified: September 2011 Refer to www.dialogic.com for product updates and for information about support policies, warranty information, and service offerings. -
Page 7: Scope
1000 Media Gateway Series (DMG1000) and Dialogic ® 2000 Media Gateway Series (DMG2000) product lines, which also are referred to collectively herein as Dialogic ® Media Gateway or Media Gateway or gateway. A gateway can provide a connection between VOIP telephony networks and proprietary digital telephony networks. -
Page 8: References
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle References Dialogic 1000 and 2000 Media Gateway Series User‟s Guide ®... -
Page 9: Configuration Parameters
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Configuration Parameters The following table lists the configuration parameters that govern the operation of the SIP mode of the gateway. This is not a complete list of all gateway configurable parameters. - Page 10 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Parameter (INI) Valid Settings Default Description state of active IP calls. If the active IP call has lost connection, the Media Gateway will tear down the call. gwMonitorCallIntSec 10-3600 Call Monitor Interval (secs).
- Page 11 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Parameter (INI) Valid Settings Default Description gwU2UEnable On, Off Enables/disables gateway support for the user-user header. See chapter 15. gwU2UTranslateMethod String, Hex String If the user-user header does not specify an encoding, this parameter is used as the implied encoding.
- Page 12 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Parameter (INI) Valid Settings Default Description 0-60000 Invite Expiration Time (secs). sipExpInvSec sipPrivacyHdrEnabled Yes, No Enable SIP Privacy headers (RFC3325 & RFC3323, and draft-ietf-sip-privacy-04 sipPrivacyHdrMethod P-Asserted-Identity P-Asserted- Supported headers Identity...
- Page 13 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Parameter (INI) Valid Settings Default Description 10-60000 Number of seconds after which an idle sipTcpInactivitySec TCP connection will be closed. sipTlsCertVerifyDate Yes, No Verify TLS Peer Certificate Date. sipTlsCertVerifyPurpose Yes, No Verify TLS Peer Certificate Purpose.
-
Page 14: Configuration Xml Parameters
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Configuration XML parameters The following SIP configuration items are stored in XML format in the gateway file named dmg.xml. Parameter (XML) Valid Settings Default Description RouteTable/ Blank Valid endpoint Specifies a VOIP endpoint that is to receive calls from the either the address (VOIP, URL, TDM or VOIP network. - Page 15 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Parameter (XML) Valid Settings Default Description NetworkGroups/ Yes = All Request, To, From, and Contact URIs generated by the gateway will use the SIPS URI scheme. Group/ Signaling/ No = All Request, To, From, and Contact URIs generated by the SIPS gateway will use the SIP URI scheme.
- Page 16 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Parameter (XML) Valid Settings Default Description p/Register/Addr between register with. If blank, the Gateway will not 1–128 characters. register with a Registration Server. 1024-65000 5060 IP Port of the SIP Registration Server.
- Page 17 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Parameter (XML) Valid Settings Default Description 32, 80 Length of the SHA1 authentication tag in bits. SIP/NetworkGroups/Grou p/SRTP/AuthTag Yes, No If enabled then a one-byte MKI (Master Key Index) is used when SIP/NetworkGroups/Grou transmitting secure-RTP and secure-RTPC packets.
- Page 18 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Parameter (XML) Valid Settings Default Description String with length Blank Specifies the Password associated with UserName for inbound SIP SIPAuth/Authentication/ between methods. Users/User/Password 1-64 characters. MD5, Sets the Authentication algorithm.
-
Page 19: General
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle General VOIP to TDM Connect Determination The gateway does not send the 200 OK response to the INVITE until a positive detect event is detected on the TDM network call. The positive detect event could be voice activity, ring-back tone termination, etc. -
Page 20: Functions
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Functions Function Supported? User Agent Client (UAC) User Agent Server (UAS) Proxy Server Party Redirect Server... -
Page 21: Supported Rfcs And Drafts
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supported RFCs and Drafts Specification Notes RFC 3261 SIP None RFC 3263 DNS Resolution None RFC 2976 SIP INFO Method None RFC 3824 Using ENUM for SIP Applications None RFC 4028: The SIP Session Timer None RFC 3265: SIP –... - Page 22 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Authentication is supported Draft-johnston-cuss-sip-uui-01.pdf Using the transport mechanism described in section 3.6...
-
Page 23: Methods
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Methods Method Supported? Comments INVITE Generated and received for call initiation and hold/unhold. Generated and received. OPTIONS Generated to monitor status of proxy server and VOIP endpoints (when RouteTable/VoipHostGroups/Group/FaultTolerant is enabled). -
Page 24: Responses
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Responses 1xx Response – Information Responses Response Supported? Comments 100 Trying Generated for an incoming INVITE. 180 Ringing Generated when ring-back tone is detected on outbound TDM call. 181 Call is being forwarded Not generated. -
Page 25: 4Xx Response - Request Failure Responses
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle 4xx Response – Request Failure Responses Response Supported? Comments 400 Bad Request Generated on receive of invalid requests. When received, call gracefully fails/disconnects. 401 Unauthorized Generated when UAS Authentication is enabled. -
Page 26: 5Xx Response - Server Failure Responses
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Response Supported? Comments fails/disconnects. 415 Unsupported Media Not generated. When received, call gracefully fails/disconnects. 420 Bad Extension Not generated. When received, call gracefully fails/disconnects. 480 Temporarily Unavailable Generated when call can be routed to TDM network, but the telephony port is already active. -
Page 27: 6Xx Response - Global Responses
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle 501 Not Implemented Not generated. When received, call gracefully fails/disconnects. 502 Bad Gateway Not generated. When received, call gracefully fails/disconnects. 503 Service Unavailable Generated on detection of Special Information Tone (SIT) for reasons of "reorder"... -
Page 28: Headers
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Headers All supported headers in the table are supported in the receive direction. Those generated as well are noted. Header Supported? Comments Accept Accept-Encoding Accept-Language Allow Allow-Events Authentication-Info Also Authorization... - Page 29 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Priority Privacy Generated Proxy-Authenticate Proxy-Authorization Proxy-Require Reason Generated Record-Route Remote-Party-ID Generated Reply-To...
- Page 30 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Referred-By Generated Referred-To Generated Replaces Generated Requested-By Generated Require Response-Key Retry-After Route Generated Server Generated Subject Subscription-State Supported Timestamp Generated Unsupported User-Agent Generated User-To-User Generated Generated Warning WWW-Authenticate Generated...
-
Page 31: 10. Sip Methods
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle 10. SIP METHODS INVITE Requests (Generated) From Header The From header of the INVITE request identifies the TDM network originator of the call. INVITE requests originating from the gateway provide source party information, including the phone number of the TDM network calling party (if available) and the telephony port (logical TDM channel) on which the TDM network call was received. -
Page 32: To Header
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle To Header The To header is created using the configured RouteTable/VoipHostGroups/Group/Host. If the RouteTable/VoipHostGroups/Group/Host is an IP address, then the user name „Anonymous‟ is used. For instance, if RouteTable/VoipHostGroups/Group/Host is set to „10.10.1.132‟, then the To header appears as:... -
Page 33: Route Header
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supported Diversion reasons consist of the following: “no-answer”, “unconditional”, “user-busy” Route Header The generated INVITE request will contain a Route header if SIP/NetworkGroups/Group/Proxy/Server/Addr is set. The Route header will contain the IP address of the currently-active proxy server specified by SIP/NetworkGroups/Group/Proxy/Server/Addr. -
Page 34: Invite Requests (Received)
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle INVITE Requests (Received) Vendor-Specific Port Specifier When a VOIP call is received by the gateway, the gateway routes the call based on the gateway‟s configured Routing Table. If a TDM port is specified in the INVITE sent to the gateway, using the vendor specific „vnd.pimg.port‟... -
Page 35: Early-Media
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Early-Media VOIP-to-TDM Calls A SIP endpoint that wants to receive RTP on an outbound connection to the TDM network from the gateway prior to the TDM subscriber answering the call may request early-media. If the gateway‟s sipEarlyMediaSupport is configured for On-Demand, then the INVITE that is received by the gateway must have a Supported header that contains early-session. - Page 36 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle TDM-to-VOIP Calls If the gateway‟s sipEarlyMediaSupport is configured for On-Demand, then the INVITE that is sent by the gateway will include the Supported header that includes „early-session‟. The INVITE will also contain SDP with an active and compatible audio stream. If the VOIP peer sends a 183 in response to the INVITE which includes the SDP answer, the gateway will send RTP to the connection address prior to the 200OK response.
-
Page 37: Positive Answering Machine Detection (Pamd)
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Positive Answering Machine Detection (PAMD) A SIP endpoint that sends an INVITE to the gateway may request the gateway to perform a DSP analysis of the voice of the answering party. This is known as a PAMD request. The purpose of the PAMD request is to allow the peer to know if the source of the audio is human, answering machine or unknown. -
Page 38: Invite Responses
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle INVITE Responses The gateway will send a 200OK response to a received INVITE request only upon receiving a connect event from the switch (here we are considering only VOIP and TDM routing and not VOIP to VOIP routing). - Page 39 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle DISCONNECT, Cause Code = 38 network out of 503 Service unavailable order DISCONNECT, Cause Code = 41 temporary failure 503 Service unavailable DISCONNECT, Cause Code = 42 switching 503 Service unavailable...
-
Page 40: Info
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle INFO The INFO method is generated by the gateway if the TDM call party information was not available when the INVITE request was made, but now is available. This could occur if the call party information did not arrive at the gateway at the same time as the TDM call, or if the TDM call had to be answered before its call party information is made available by the TDM switch. - Page 41 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle The SIP INFO method is used by a UA to send call signaling information to another UA with which it has an established media session. The following example shows a SIP INFO message with DTMF content: INFO sip:7007471000@example.com SIP/2.0...
-
Page 42: Bye
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle The BYE method is generated to terminate a call with a UA on the VOIP network. The Reason header contains the reason for the call termination if it can be determined. For instance, if dial-... -
Page 43: Cancel
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle CANCEL The CANCEL method is generated to cancel a call from the TDM network and the VOIP network. OPTIONS The OPTIONS Request is generated when the Gateway is monitoring the status of a proxy-server or the status of a VOIP endpoint (RouteTable/VoipHostGroups/Group/FaultTolerant is enabled). -
Page 44: Voip Endpoint Monitoring
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VoIP Endpoint Monitoring VoIP endpoint monitoring is enabled when: 1. Fault Tolerant is enabled on the Routing Table‟s VoIP Host Groups page OR 2. The configuration parameter „gwProactiveMonitorDnsARecordsEnable‟ is enabled AND when the endpoint was obtained from the DNS resolution of an FQDN. -
Page 45: Notify ("Message-Summary")
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle NOTIFY (“message-summary”) If the gateway receives a NOTIFY request with the Event header to “message-summary”, the gateway assumes this to be a request to set/clear a TDM network MWI. The To header of the indication must contain the dial number of the TDM network destination of the MWI set/clear (see section 0) The Messages-Waiting header must be set to either “yes”... -
Page 46: Refer
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle REFER The REFER method indicates that the recipient (identified by Request-URI) should contact a third party using the contact information provided in the request. Media Gateway uses REFER method for doing supervised and un-supervised transfers. If the “Refer-To” of the REFER request contains the IP address of the current gateway, then the REFER is requesting a transfer of a call that is on current gateway to another call that is on the same gateway. -
Page 47: Register
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle REGISTER The REGISTER method may be configured to be sent for each Network Group specified. On reception, the gateway may respond with a 200OK (if authentication passes or is disabled) however the gateway does not store or pass on received registrations. - Page 48 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle 6. Some Registrars may require the Gateway Name be set to the Registration Server Address. REGISTER From Contact RU@GWN RU@GWN RU@CIP:CSP RSA:RSP GWN (when RU is null) GWN (when RU is null) CIP:CSP (when RU is null) An example REGISTER sent from the gateway is shown here.
-
Page 49: 11. Call Flows
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle 11. Call Flows The following diagrams show the message and control flows between the TDM network switch attached to the gateway and one or more SIP VOIP devices. A proxy/registrar/location server could be inserted between the gateway and the SIP devices, but their inclusion does not significantly change the call flows. -
Page 50: Voip To Tdm Success
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to TDM Success The gateway generates 200 OK after a positive answer is detected. This may occur upon in-band voice activity detection, ring-back tone interruption, pager tone detection, or fax tone detection. -
Page 51: Voip To Tdm Success (Isdn Connect)
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to TDM Success (ISDN CONNECT) When the TDM interface uses an ISDN protocol, the gateway relies on the ISDN CONNECT message from the TDM Switch to determine when the call has been answered (exception to this is if the TDM switch sends an ISDN Progress Indication:(1 or 8), described in next section). -
Page 52: Voip To Tdm Success (Isdn Progress Indication:8 In-Band)
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to TDM Success (ISDN Progress Indication:8 In-Band) When the TDM interface uses an ISDN protocol, the gateway relies on the ISDN CONNECT message from the TDM Switch to determine when the call has been answered. However, if the TDM Switch determines that the call is not ISDN end-to-end, then it will send an ISDN Progress Indication:(1 or 8) message to the Gateway. -
Page 53: Voip To Tdm Success With Early Media
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to TDM Success with Early Media In this scenario, the SIP device requests for early media support using the „Supported‟ header field with the „early-session‟ option tag. The gateway responds with an additional 183 Session Progress message that indicates support for early media via the „Content-Disposition‟... -
Page 54: Voip To Tdm Failure - Call Un-Routable
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to TDM Failure – Call Un-Routable If the INVITE request does not contain any valid destination number and no routing table rule may be positively matched, then the following scenario occurs. -
Page 55: Voip To Tdm Failure - Call Canceled
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to TDM Failure – Call Canceled If the INVITE request source cancels the request before the gateway completes the request, then the gateway will terminate the TDM network call. -
Page 56: Voip To Tdm Failure - Tdm Channel Unavailable
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to TDM Failure – TDM Channel Unavailable If there are no available gateway TDM channels, then the gateway responds with a 480. SIP Device Gateway TDM Switch TDM Device... -
Page 57: Voip To Tdm Failure - Glare
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to TDM Failure – Glare If a TDM network call is inbound on a TDM channel that is about to be used for a TDM call origination, then a glare condition occurs. The gateway fails the INVITE request, and presents a TDM-To-VOIP INVITE request for the inbound TDM call. -
Page 58: Voip To Tdm Failure - Busy Response
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to TDM Failure – Busy Response A busy response detected during TDM call origination results in a failure response to the INVITE request and the TDM call is terminated. The busy response could be a busy-tone or an ISDN busy- disconnect. -
Page 59: Voip To Tdm Failure - Error Response
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to TDM Failure – Error Response An error response detected during TDM call origination results in a failure response to the INVITE request and the TDM call is terminated. The error response could be an error tone or an ISDN error-disconnect. -
Page 60: Tdm To Voip Success (Post-Invite Cpid)
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle TDM to VOIP Success (Post-INVITE CPID) The INFO method is generated only if the TDM call party information was not available at the time of the INVITE request generation, but has now become available. This can occur as a result of Type II CPID, in which the CPID is available only after the TDM call is answered. -
Page 61: Tdm To Voip Success (Calling Number Updated)
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle TDM to VOIP Success (Calling Number Updated) If the calling number is updated either before or after the call is answered (either ringing or connected state), the Media Gateway can send an INFO message update to the VOIP endpoint. -
Page 62: Tdm To Voip Success With Early Media (Gateway Model)
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle TDM to VOIP Success with Early Media (Gateway Model) In this scenario, the SIP device requests for early media support by responding to the initial INVITE sent by the gateway – which included a SDP Offer – with a SDP Answer in a 183 Session Progress message. -
Page 63: Tdm To Voip Success With Early Media (Application Model)
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle TDM to VOIP Success with Early Media (Application Model) In this scenario, the SIP device requests for early media support by responding to the initial INVITE sent by the gateway – which included a Session header set to „early-session and a SDP Offer –... -
Page 64: Tdm To Voip Failure - Rejected
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle TDM to VOIP Failure - Rejected If the VOIP destination rejects the call with any error response, or the INVITE request times out, then the TDM call is transferred to the default TDM network destination, or the call is ignored. If a default TDM network destination is configured, then the TDM call is answered and immediately - transferred (unsupervised) to the default destination. -
Page 65: Tdm To Voip Failure - Tdm Cancel
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle TDM to VOIP Failure - TDM Cancel If the TDM network call terminates before the INVITE request is answered, then the gateway will cancel the INVITE request. SIP Device Gateway... -
Page 66: Voip To Voip Success - Redirect Routing
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to VOIP Success – Redirect Routing The gateway supports the ability to perform VOIP to VOIP Redirect Routing. In this case, the gateway simply responds to an incoming INVITE from a SIP peer with a 302 response. This call flow does not show any 1xx messages for the purpose of simplification. -
Page 67: Voip To Voip Success - Bridged Routing With Pass Through
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to VOIP Success – Bridged Routing with Pass Through The gateway supports the ability to perform VOIP to VOIP Bridged Routing. In this case, the gateway bridges two disparate signaling networks or devices. This call flow does not show any 1xx messages for the purpose of simplification. - Page 68 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle The VOIP to VOIP routing aspect of the gateway supports many of the same bridged routing call flows which are seen with VOIP to TDM and TDM to VOIP routing. This includes but is not limited to Re-INVITE, messages such as MWI and CPID, transfers involving the REFER method and FAX support .
-
Page 69: Voip To Voip Success - Bridged Routing With Transcoding
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to VOIP Success – Bridged Routing with Transcoding Transcoding is the ability of the gateway to transform RTP packets from one codec format to a different codec format. Transcoding is employed in VOIP to VOIP bridged routing when SIP Device A and SIP Device B would prefer to communicate with the gateway via differing codec formats. -
Page 70: Voip To Voip Failure - Bridged Routing With Pass Through
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP to VOIP Failure – Bridged Routing with Pass Through This scenario illustrates a failure in a VOIP to VOIP routing due to SIP Device B rejecting the INVITE. This case is a rejection due to a Busy SIP peer although the reason for the failure may be any one of the valid SIP error codes. -
Page 71: Hold, Unhold
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Hold, Unhold Section 0 describes how a VoIP call is placed on-hold and subsequently released from hold. When a VoIP call on the Gateway is placed on-hold, the state of the TDM network call is un- changed. -
Page 72: Voip Call Drop
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle VOIP Call Drop As soon as a BYE request is received from the VOIP device, the TDM call is terminated. SIP Device Gateway TDM Switch TDM Device 2-way RTP 2-way VP... -
Page 73: Tdm Call Drop
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle TDM Call Drop If a „disconnect‟ state is detected on the TDM network call (call terminates, dial-tone detected, disconnect-event), then the TDM call is terminated and a BYE request is sent. -
Page 74: Unsupervised Transfer Success - Voip Target - Refer
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Unsupervised Transfer Success - VOIP Target - REFER A VOIP device uses the REFER method to request that the gateway terminate the initial VOIP call and replace it with a new VOIP call. Note: SIP Device A may send the BYE immediately after it receives the 202 Accepted for the REFER request. -
Page 75: Unsupervised Transfer Failure - Voip Target - Refer
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Unsupervised Transfer Failure - VOIP Target - REFER If the VOIP destination responds with an error, then the TDM call is dropped. Note: SIP Device A may send the BYE immediately after it receives the 202 Accepted for the REFER request. -
Page 76: Unsupervised Transfer - Tdm Target
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Unsupervised Transfer – TDM Target This section contains the call scenarios in which a VoIP device is requesting a supervised transfer of one device on the TDM network to another device on the TDM network. In other words, the target of the transfer request from the VoIP network is on the TDM network. -
Page 77: Unsupervised Transfer Success - Tdm Target - Refer
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Unsupervised Transfer Success - TDM Target - REFER The gateway waits for a successful progress indication from TDM device C before completing the transfer. A successful progress indication is a timeout (no tones detected), voice activity, ring- back tone or an ISDN progress indication. -
Page 78: Unsupervised Transfer Failure - Tdm Target - Refer Error Response
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Unsupervised Transfer Failure - TDM Target – REFER Error Response The gateway waits for a successful progress indication. If an error-response is received from the TDM network, then the original TDM call is retrieved and the transfer fails. Note: SIP Device A may send the BYE immediately after it receives the 202 Accepted for the REFER request. -
Page 79: Unsupervised Transfer Failure - Tdm Target - Refer Busy Response
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Unsupervised Transfer Failure - TDM Target – REFER Busy Response The gateway waits for a successful progress indication. If a busy-response is received, then the original TDM call is retrieved and the transfer fails. A busy-response may be busy-tone, an ISDN busy-disconnect, or an ISDN busy-reroute request. -
Page 80: Supervised Transfer Success - Voip Target, Gateway Is Transferee
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer Success - VOIP Target, Gateway is Transferee A consultation transfer to a VOIP target replaces on VOIP endpoint with another on the TDM call. The gateway serves as the Transferee. -
Page 81: Supervised Transfer Success - Voip Target, Gateway Is Transferor
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer Success - VOIP Target, Gateway is Transferor The TDM device makes a consultation call to a new VOIP endpoint. The gateway serves as the Transferor. SIP Device B... -
Page 82: Supervised Transfer Success - Tdm Target, Gateway Is Transferee And Transferor
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer Success - TDM Target, Gateway is Transferee and Transferor SIP Device A makes a consultation call to TDM Device C for the purpose of transferring TDM device B to TDM device C. The Gateway severs as both the Transferee and the Transfer target. -
Page 83: Supervised Transfer Success - Tdm Target, Gateway Is Target
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer Success - TDM Target, Gateway is Target SIP Device B make a consultation call to TDM device C for the purpose of transferring SIP device A to TDM Device C. The Gateway serves as the Transfer Target. -
Page 84: Supervised Transfer - Tdm Target, Gateway Is Transferee And Target
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer – TDM Target, Gateway is Transferee and Target Supervised transfers of a call to a TDM device must be supported in a different manner than unsupervised transfers. Unsupervised transfers are handled completely by the Media Gateway. -
Page 85: Supervised Transfer Success - Tdm Target, Gateway Is Transferee And Target
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer Success - TDM Target, Gateway is Transferee and Target In the following diagram, SIP Device A is the transferor (transfer requestor), TDM Device B is the transferee, and TDM Device C is the transfer target. SIP Device A first establishes a call to TDM Device B (Dlg[A,B]). -
Page 86: Supervised Transfer Failure - Tdm Target - Canceled
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer Failure - TDM Target – Canceled The following diagram shows SIP Device A aborting the supervised transfer to TDM Device C. The original call between SIP Device A and TDM Device B is re-established. -
Page 87: Supervised Transfer Failure - Tdm Target - Canceled
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer Failure - TDM Target – Canceled If the VOIP device cancels the transfer, which could be a result of a ring-no-answer timeout, then the gateway retrieves the original call. -
Page 88: Supervised Transfer Failure - Tdm Target - Busy Response
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer Failure - TDM Target – Busy Response If a busy-response is received from the transfer-target, then the transfer fails and the original call is retrieved. SIP Device A... -
Page 89: Supervised Transfer Failure - Tdm Target - Error Response
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer Failure - TDM Target – Error Response If an error response is detected on the transfer, then the transfer fails and the original call is retrieved. SIP Device A... -
Page 90: Supervised Transfer Failure - Tdm Target Drops
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer Failure - TDM Target Drops If the target of the supervised transfer drops, then the gateway automatically re-establishes the call with the original TDM network party. SIP Device A... -
Page 91: Supervised Transfer Failure - Tdm Transferee Drops
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supervised Transfer Failure - TDM Transferee Drops If the transferee of the supervised transfer drops, then the gateway drops both the transferee and the transfer-target calls. SIP Device A Gateway... -
Page 92: Mwi - Voip To Tdm Success
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle MWI - VOIP to TDM Success A VOIP NOTIFY request may be made for Message-Waiting to request an MWI set/clear of a TDM network device. The NOTIFY request must specify the destination TDM network device in the To header (see section 0). -
Page 93: Mwi - Voip To Tdm Failure
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle MWI - VOIP to TDM Failure If the MWI set/clear fails, an error response is sent for the NOTIFY request. SIP Device Gateway TDM Switch TDM Device NOTIFY (Message-Summary) 100 Trying... -
Page 94: Mwi - Voip To Tdm Failure - Glare
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle MWI - VOIP to TDM Failure - Glare If the MWI set/clear fails because of a glare condition, an error response is sent for the NOTIFY request, and a new INVITE request is generated for the new call. -
Page 95: Mwi - Tdm To Voip Success
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle MWI – TDM to VOIP Success A VOIP NOTIFY request may be made for Message-Waiting to request an MWI set/clear of a VOIP network device. The NOTIFY request must specify the destination VOIP network device in the To header (see section 0). -
Page 96: T.38 Fax - Tdm To Voip
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle T.38 Fax - TDM to VOIP A TDM to VOIP T.38 Fax call is initiated by a fax machine calling a telephony port on the gateway. The SDP information placed in the INVITE request to the VoIP network includes the fax media type and control information. - Page 97 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle SIP Device Gateway TDM Switch TDM Device Originate Inbound INVITE 180 Ringing 200 OK Answered Answered 2-way RTP 2-way VP 2-way VP CNG Tone CNG Tone RFC2833 CNG CNG tone can be...
-
Page 98: T.38 Fax - Voip To Tdm
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle T.38 Fax – VOIP to TDM A VOIP device that supports T.38 Fax communication may specify the fax media type with a port number of zero in the SDP information contained in the original INVITE request. When this VOIP device places a TDM network call that reaches a fax machine, the call proceeds in the same manner as a voice call and the RTP stream for voice is started. - Page 99 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle When the VOIP device wishes to switch to T.38, it can change the audio stream to a T.38 stream: m=image 49533 udptl t38 a=T38FaxRateManagement:transferredTCF a=T38FaxUdpEC:t38UDPFEC...
- Page 100 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle SIP Device Gateway TDM Switch TDM Device INVITE 100 Trying 180 Ringing Originate Outbound 200 OK 2-way RTP 2-way VP 2-way VP V.21 Flags V.21 Flags Re-INVITE (image) 200 OK UDPTL T.38 Fax...
-
Page 101: 12. Proxy Monitoring
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle 12. Proxy Monitoring The gateway supports the use of a primary and a backup outbound proxy server. The gateway determines the connection-status of the primary proxy by periodically (period is configurable) sending an OPTIONS request to the primary proxy. - Page 102 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Gateway Primary Proxy Backup Proxy Requests sent to Primary OPTIONS Response OPTIONS Response OPTIONS Request times-out Requests sent to Backup OPTIONS Request times-out OPTIONS Response Requests sent to Primary...
-
Page 103: 13. Sip Authentication
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle 13. SIP Authentication Overview The gateway supports the use of SIP Authentication. SIP Authentication is based upon HTTP Authentication as specified in RFC 2617. SIP Authentication follows RFC 2617 closely with a few exceptions which are noted in section 22 of RFC 3261. -
Page 104: Example Www-Authenticate Header
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Example WWW-Authenticate Header The following shows an example „401 Unauthorized‟ response to an original INVITE. When the UAS requires authentication, it sends this response as opposed to a 200OK and includes the WWW-Authenticate header (if the UAS is a proxy it will send the „Proxy-Authenticate‟... -
Page 105: Example Authorization Header
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Example Authorization Header The following INVITE shows a UAC attempting a re-send of the original INVITE after having received a 401 Unauthorized challenge. The UAC inserts the „Authorization‟ header which was not present in the original request. -
Page 106: Invite Authentication Success - Gateway Is Uac
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle INVITE Authentication Success – Gateway is UAC The following shows the gateway acting as the client and sending an INVITE method to a SIP server device which requires authentication for the INVITE method. The SIP device challenges the gateway with a 401 Authentication message in response to the original INVITE. -
Page 107: Invite Authentication Failure - Gateway Is Uac
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle INVITE Authentication Failure – Gateway is UAC This message exchange depicts a case where the gateway is challenged by SIP device. In this exchange, the gateway re-sends the INVITE message with an Authorization header. The SIP device examines the Authorization header and subsequently rejects the INVITE. -
Page 108: Invite Authentication Success - Gateway Is Uas
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle INVITE Authentication Success – Gateway is UAS The following shows the gateway acting as the server and receiving an INVITE method. With Authentication enabled on the UAS side, the gateway challenges the client with a 401 Authenticate message in response to the original INVITE. -
Page 109: Invite Authentication Failure - Gateway Is Uas
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle INVITE Authentication Failure – Gateway is UAS This message exchange depicts a case where the gateway challenges a SIP device. In this exchange, the SIP Device re-sends the INVITE message with an Authorization header. The gateway examines the Authorization header and subsequently rejects the INVITE. -
Page 110: Register Authentication Success - Gateway Is Uac
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Register Authentication Success – Gateway is UAC A typical Authentication use case is the gateway acting as a client and attempting to register itself with a registration server. Registration servers often require SIP Authentication. If the Registration server also acts as a Proxy server it may challenge the REGISTER method with a 407 Authenticate as opposed to a 401 response. -
Page 111: 14. Calling Id Privacy
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle 14. Calling ID Privacy The DMG2000 series gateways support the privacy of Calling ID between SIP and ISDN endpoints. This is accomplished by translating between SIP privacy headers and ISDN APRI (Address Presentation Restriction Indicator) bits. -
Page 112: Gateway Configuration
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Gateway Configuration The gateway can be configured to enable or disable translation. When translation is enabled the gateway is configured to translate only „P-Asserted-Identity & Privacy‟, only „Remote-Party-ID‟ or to translate both. -
Page 113: Translation
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Translation The following subsections present the gateway‟s translation between SIP Privacy headers and ISDN APRI bits. SIP INVITE to ISDN SETUP Privacy Header Method: P-Asserted-Identity Input Output Privacy: APRI - Calling Party Number APRI –... - Page 114 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Privacy Header Method: Both Input Output Remote-Party-ID: Privacy: APRI - Calling Party Number APRI – Calling Party Name full don‟t care restricted restricted name don‟t care allowed restricted don‟t care...
-
Page 115: Isdn Setup To Sip Invite
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle ISDN SETUP to SIP INVITE Privacy Header Method: P-Asserted-Identity Input Output APRI – Calling Party Number APRI – Calling Party Name Privacy: allowed allowed none allowed restricted none restricted allowed... - Page 116 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Privacy Header Method: Both Input Output APRI – Calling Party Number APRI – Calling Party Name Privacy: Remote-Party-ID allowed allowed none allowed restricted none name restricted allowed restricted restricted full...
-
Page 117: 15. User To User Information
® Dialogic 1000 and 2000 Media Gateway Series SIP Compliance 15. User To User Information The DMG2000 series gateways support the transporting of UUI (User to User information) using a SIP header as described in “draft-johnston-cuss-sip-uu1-01.pdf” section 3.6. The gateway supports UUI information in the INVITE method, and the 180 Ringing and 200 OK responses. - Page 118 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle SIP Device DMG 2000 TDM Switch (ISDN) Invite (plus user-to-user header) 100 Trying SETUP (plus user-user IE) CALL PROC ALERTING (plus user-user IE) 180 Ringing (plus user-to-user header) CONNECT (plus user-user IE)
-
Page 119: Transfers Using Sip Refer
® Dialogic 1000 and 2000 Media Gateway Series SIP Compliance Transfers using SIP REFER When the DMG2000 receives a SIP REFER that contains UUI, the UUI is passed to the resulting SIP INVITE or ISDN SETUP. Supported call flows are as follows:... -
Page 120: Supported Encoding
® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle Supported Encoding The gateway supports two types of encoding in a user-user header: „string‟ or „hex‟. String Encoding String encoding uses a single ascii character to encode a single byte of data. For example, an ascii „U‟... -
Page 121: 16. Multipart Mime To Encapsulate Pstn Signaling
® Dialogic 1000 and 2000 Media Gateway Series SIP Compliance 16. Multipart MIME to encapsulate PSTN signaling The DMG2000 series gateways support encapsulation of PSTN signaling using multipart MIME bodies as presented in RFC 3204. This section describes the various PSTN signaling elements that the DMG2000 supports. - Page 122 ® Dialogic 1000 and 2000 Media Gateway Series SIP ComplianceDocSubtitle INVITE sip:4700@10.10.11.47 SIP/2.0 From:<sip:2042@10.10.11.114:5060;user=phone>;vnd.pimg.port=23;tag=5A533246 To:<sip:4700@10.10.11.47> Contact:<sip:2042@10.10.11.114:5060> Mime-Version: 1.0 Content-Type:multipart/mixed ;boundary=”?(boundary)*” Supported:replaces,early-session,100rel Allow:INVITE,ACK,OPTIONS,BYE,CANCEL,REGISTER,INFO,PRACK,REFER,NOTIFY Expires:120 Call-ID:01B246A660AA00460000000E@pbxgw.default.com CSeq:1 INVITE Max-Forwards:70 User-Agent:PBX-IP Media Gateway Via:SIP/2.0/UDP 10.10.11.114:5060;branch=z9hG4bKE194EDF Content-Length:291 --?(boundary)* Content-Type: application/SDP o=phone 15122 16488 IN IP4 10.10.11.114 c=IN IP4 10.10.11.114...
Need help?
Do you have a question about the 1000 and is the answer not in the manual?
Questions and answers