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. However, Dialogic does not warrant the accuracy of this information and cannot accept responsibility for errors, inaccuracies or omissions
that may be contained in this document.
®
INFORMATION IN THIS DOCUMENT IS PROVIDED IN CONNECTION WITH DIALOGIC
ESTOPPEL OR OTHERWISE, TO ANY INTELLECTUAL PROPERTY RIGHTS IS GRANTED BY THIS DOCUMENT. EXCEPT AS PROVIDED IN A
SIGNED AGREEMENT BETWEEN YOU AND DIALOGIC, DIALOGIC ASSUMES NO LIABILITY WHATSOEVER, AND DIALOGIC DISCLAIMS ANY
EXPRESS OR IMPLIED WARRANTY, RELATING TO SALE AND/OR USE OF DIALOGIC PRODUCTS INCLUDING LIABILITY OR WARRANTIES
RELATING TO FITNESS FOR A PARTICULAR PURPOSE, MERCHANTABILITY, OR INFRINGEMENT OF ANY INTELLECTUAL PROPERTY
RIGHT OF A THIRD PARTY.
Dialogic products are not intended for use in medical, life saving, life sustaining, critical control or safety systems, or in nuclear facility applications.
It is possible that the use or implementation of any one of the concepts, applications, or ideas described in this document, in marketing collateral
produced by or on web pages maintained by Dialogic may infringe one or more patents or other intellectual property rights owned by third parties.
Dialogic does not provide any intellectual property licenses with the sale of Dialogic products other than a license to use such product in accordance
with intellectual property owned or validly licensed by Dialogic and no such licenses are provided except pursuant to a signed agreement with
Dialogic. More detailed information about such intellectual property is available from Dialogic’s legal department at 9800 Cavendish Blvd., 5th Floor,
Montreal, Quebec, Canada H4M 2V9. Dialogic encourages all users of its products to procure all necessary intellectual property licenses
required to implement any concepts or applications and does not condone or encourage any intellectual property infringement and
disclaims any responsibility related thereto. These intellectual property licenses may differ from country to country and it is the
responsibility of those who develop the concepts or applications to be aware of and comply with different national license requirements.
Dialogic, Diva, Eicon, Eicon Networks, Dialogic Pro, EiconCard and SIPcontrol, among others, are either registered trademarks or trademarks of
Dialogic. Dialogic's trademarks may be used publicly only with permission from Dialogic. Such permission may only be granted by Dialogic’s legal
department at 9800 Cavendish Blvd., 5th Floor, Montreal, Quebec, Canada H4M 2V9. Any authorized use of Dialogic's trademarks will be subject to
full respect of the trademark guidelines published by Dialogic from time to time and any use of Dialogic’s trademarks requires proper
acknowledgement. Windows is a registered trademark of Microsoft Corporation in the United States and/or other countries. Other names of actual
companies and products mentioned herein are the trademarks of their respective owners.
This document discusses one or more open source products, systems and/or releases. Dialogic is not responsible for your decision to use open
source in connection with Dialogic products (including without limitation those referred to herein), nor is Dialogic responsible for any present or future
effects such usage might have, including without limitation effects on your products, your business, or your intellectual property rights.
Publication Date: November 2007
Document Number: 05-2239-009
PRODUCTS. NO LICENSE, EXPRESS OR IMPLIED, BY
Dialogic® Global Call IP Technology Guide – November 2007
IPSET_CALLINFO Parameter Set table: Added parm ID for optional H.245 channel
IPSET_CONFIG Parameter Set table: Added info on DiffServ field (DSCP)
IPSET_IPPROTOCOL_STATE Parameter Set table: Added parm for H.245 failure
IPSET_MSG_SIP Parameter Set table: Added IPPARM_SIP_METHOD parm ID
IPSET_SDP parameter set: New section
IPSET_SIP_RESPONSE_CODE Parameter Set table: Added
IPPARM_ACCEPT_RESP_CODE parm ID
IP_CAPABILITY data structure: Added new direction defines
Error Codes When Using H.323 section: Added new codes for H.245 channel error
Dialogic® Global Call IP Technology Guide — November 200717
Dialogic Corporation
Revision History
Document No.Publication DateDescription of Revisions
05-2239-005April 2005Call Control Library Initialization section : Added more detail about how to set
configuration items before calling gc_Start( )
Setting and Retrieving SIP Message Header Fields section: Rewritten to document
generic access mechanism and long header support
Sending OPTIONS Requests section: added note on inclusion of MIME SDP body
Responding to OPTIONS Requests section : Added information about automatic
inclusion of SDP in MIME body of OK responses
Sending NOTIFY Requests section: Corrected code example
Using H.323 Annex M Tunneled Signaling Messages : New section and subsections
Registration section: Reorganized subsections and added information on new SIP
registration capabilities
SIP Digest Authentication: New section and subsections
Debugging Global Call IP Applications chapter: Added note in two locations about
SIP stack parsing error log file
Global Call Functions Supported by IP section: Added entries for
gc_SetAuthenticationInfo( ) and new gc_util_... functions
IP-Specific Global Call Functions: New section to contain API reference pages for:
gc_SetAuthenticationInfo( ) (new function),
gc_util_copy_parm_blk( ) (new function),
gc_util_find_parm_ex( ) (new function),
gc_util_insert_parm_ref_ex( ) (new function),
gc_util_next_parm_ex( ) (new function),
INIT_IP_VIRTBOARD( )
INIT_IPCCLIB_START_DATA( )
Valid Extension IDs for the gc_Extension( ) Function table: Added note on parameter
order requirement when using IPEXTID_SENDMSG
gc_OpenEx( ) Variances for IP section: Added note about not closing and re-opening
channels (PTR# 32087)
gc_Start( ) Variances for IP section: Added information about how to reference
configuration data structure when calling function
Initialization Functions section: Eliminated section by moving information to API
reference pages in new IP-Specific Global Call Functions section
Summary of Parameter Sets and Parameter Usage table: Added two authentication
parameter IDs to IPSET_CONFIG. Added “deprecated” indication to all
parameters in the IPSET_SIP_MSGINFO set except IPPARM_SIP_HDR.
Added two new parameter IDs to IPSET_REG_INFO. Added six new entries for
IPSET_TUNNELEDSIGNALMSG parameter set.
IPSET_CONFIG Parameter Set table: Added
IPPARM_AUTHENTICATION_CONFIGURE and
IPPARM_AUTHENTICATION_REMOVE parameters
IPSET_SIP_MSGINFO section: Added note on deprecation of most parm IDs.
Added note about using extended gc_util_... functions with IPPARM_SIP_HDR
IPSET_SIP_MSGINFO Parameter Set table: Added “deprecated” indications to all
parameters except IPPARM_SIP_HDR
IPSET_REG_INFO Parameter Set table: Added IP_REG_QUERY_INFO value for
IPPARM_OPERATION_REGISTER parameter.
Added IPPARM_REG_AUTOREFRESH and IPPARM_REG_SERVICEID
parameters.
18Dialogic® Global Call IP Technology Guide — November 2007
Dialogic Corporation
Revision History
Document No.Publication DateDescription of Revisions
05-2239-005
(continued)
05-2239-004January 2005H.450.2 Blind Call Transfer Failure - Party B Rejects Call Transfer figure: Missing
IPSET_TUNNELEDSIGNALMSG parameter set: New section
GC_PARM_DATA_EXT data structure: New section
IP_AUTHENTICATION data structure : New section
IP_TUNNELPROTOCOL_ALTID data structure : New section
IP_VIRTBOARD data structure: Added new h323_msginfo_mask value for Annex M
IPCCLIB_START_DATA data structure: Added max_parm_data_size field
Failure Response Codes When Using SIP section: Added subsection for new SIP
Registration Error response codes
portion of figure restored
Endpoint Behavior in H.450.2 Supervised Call Transfer section: Added precondition
information, including parties in consultation call being in connected state
Call Transfer Scenarios When Using SIP: New section and subsections
Setting a SIP Outbound Proxy: New section
Configuring SIP Transport Protocol : New section and subsections
Retrieving Current Call-Related Information section: Added note about
acknowledging call before extracting information in H.323
Standard Call-Related SIP Message Header Fields table: Added entries for ten
additional headers
Standard Call-Related Headers for Outbound SIP Messages: New table showing
relationship between header s, Global Call functions, and SIP message types
Standard Call-Related Headers for Inbound SIP Messages: ANew table showing
relationship between SIP message types, Global Call event types, and headers
Setting Additional (Generic) SIP Message Headers: New section
Retrieving Additional (Generic) SIP Message Headers: New section
Using SIP Messages with MIME Bodies (SIP-T): New section and subsections
Global Call Events for Incoming SIP Messages that can Contain MIME Bodies table:
Added five additional message types. Event for 3xx to 6xx responses changed
from GCEV_TASKFAIL to GCEV_DISCONNECTED.
Global Call Functions for SIP MIME Messages Using IPSET_MIME table: Added
one function and five additional message types
Specifying Transport for SIP Messages: new section
Handling SIP Transport Failures: new section
Sending and Receiving SIP INFO Messages: New section and subsections
Sending and Receiving SIP OPTIONS Messages: New section and subsections
Using SIP SUBSCRIBE and NOTIFY Messages: New section and subsections
Specifying DTMF Support section : Clarified descriptions of bitmask values
Getting Media Streaming Status and Connection Information section: Added
information on getting local and remote RTP addresses
Call Transfer When Using SIP: New section and subsection
Sending a T.38 Fax in a Session Without Audio Established section: Corrected code
example (PTR#33979)
Receiving a T.38 Fax in a Session Without Audio Established section: Corrected
code example (PTR#34073)
Dialogic® Global Call IP Technology Guide — November 200719
Dialogic Corporation
Revision History
Document No.Publication DateDescription of Revisions
05-2239-004
(continued)
Host LAN Disconnection Alarms : New section and subsection
Debugging Global Call IP Applications chapter : Completely rewritten to describe new
RTF logging facilities
gc_AcceptInitXfer( ) Variances for IP section: Added SIP variances
gc_AcceptXfer( ) Variances for IP section: Added SIP variances
gc_Extension( ) Variances for IP section: Added IPEXTID_MSGINFO entry and
added SIP message type in entries for IPEXTID_RECEIVEMSG and IPEXTID_
SENDMSG in Valid Extension IDs for the gc_Extension( ) Function table
gc_GetCallInfo( ) Variances for IP section: Added info on SIP-specific forms of
origination address and destination address
gc_InitXfer( ) Variances for IP section: Added SIP variances
gc_InvokeXfer( ) Variances for IP section: Added SIP variances
gc_RejectInitXfer( ) Variances for IP section: Added SIP variances
gc_RejectXfer( ) Variances for IP section: Added SIP variances
gc_SetConfigData( ) Variances for IP: Added SIP variance about enabling call
transfer invoke acknowledge events
gc_Start( ) Variances for IP: Added bullet items with default value info for SIP MIME,
SIP outbound proxy, SIP transport protocol, SIP request retry, and SIP
OPTIONS access configuration items
INIT_IP_VIRTBOARD( ) section: Added info on SIP MIME enable, SIP outbound
proxy, SIP transport protocol, SIP request retry, and SIP OPTIONS access
Summary of Parameter Sets and Parameter Usage table: Added
IPPARM_REGISTER_SIP_HDR in IPSET_CONFIG set; IPSET_MIME and
IPSET_MIME200OK_TO_BYE sets (5 parameter IDs); IPSET_MSG_SIP set (2
parameter IDs); IPSET_RTP_ADDRESS set (2 parameter IDs); 10 parameter
IDs in IPSET_SIP_MSGINFO plus additional function and event information;
IPSET_SIP_REQUEST_ERROR (2 parameter IDs)
IP_ADDR structure description : Corrected structure name in text and typedef (was
IPADDR)
IP_VIRTBOARD structure description: Corrected data type of localIP field. Added
SIP MIME enable mask value and fields for SIP outbound proxy, SIP transport
protocol, SIP request retry, and SIP OPTIONS access enable.
RTP_ADDR structure description: New section
20Dialogic® Global Call IP Technology Guide — November 2007
Dialogic Corporation
Document No.Publication DateDescription of Revisions
05-2239-003September 2004General Conditions for Call Transfers section : New section
Using Fast Start and Slow Start Setup section: Added note about H.323 fast start
when no coder is specified (PTR#33321)
Summary of Call-Related Information that can be Set table: Added note that
GC_SINGLECALL must be used for Call ID and SIP Message Information fields.
Added entries for four additional SIP Message Information fields.
Retrievable Call Information table: Revised datatype for H.323 Call ID and added info
on SIP Call ID
Examples of Retrieving Call-Related Information section: Added code examples for
retrieving and parsing Call ID.
Supported SIP Message Information Fields table: Added entries for Call ID,
Diversion URI, Referred-By, and Replaces. Updated Contact URI entry to
indicate setting is supported.
Nonstandard Registration Message section: Corrected parameters and added code
example
gc_GetCallInfo( ) Variances for IP section: Added information on getting Call ID.
Added SIP-specific address formats (To URI and From URI)
gc_MakeCall( ) Variances for IP section: Added note about SIP timeout
Configurable Call Parameters When Using H.323 table: Corrected value names for
IPPARM_CONNECTIONMETHOD. Added entry for
IPSET_CALLINFO/IPPARM_CALLID.
Configurable Call Parameters When Using SIP table: Corrected value names for
IPPARM_CONNECTIONMETHOD. Added entry for
IPSET_CALLINFO/IPPARM_CALLID.
gc_Start( ) Variances for IP section: Added information on default board instances
and parameter values
Summary of Parameter Sets and Parameter Usage table: Updated info for
IPSET_CALLINFO/IPPARM_CALLID.
Added entries in IPSET_SIP_MSGINFO section for IPPARM_CALLID_HDR,
IPPARM_DIVERSION_URI, IPPARM_REFERRED_BY, and
IPPARM_REPLACES.
Added set/send info for IPSET_SIP_MSGINFO/IPPARM_CONTACT_URI.
IPSET_CALLINFO Parameter Set table: Updated description of IPPARM_CALLID.
Corrected value names for IPPARM_CONNECTIONMETHOD.
IPSET_SIP_MSGINFO Parameter Set table: Added entries for
IPPARM_CALLID_HDR, IPPARM_DIVERSION_URI,
IPPARM_REFERRED_BY, and IPPARM_REPLACES
Updated IPPARM_CONTACT_URI to indicate that setting is supported.
Added length defines for all parameters.
IP_VIRTBOARD structure description: Added default values to field descriptions
Revision History
Dialogic® Global Call IP Technology Guide — November 200721
Dialogic Corporation
Revision History
Document No.Publication DateDescription of Revisions
05-2239-002April 2004Summary of Call-Related Information that can be Set table : Added entries for Call
ID, MediaWaitForConnect, and PresentationIndicator.
Coders Supported for Host Media Processing (HMP) table: Corrected G.711 entries
to indicate VAD must be disabled (PTR 32576). Added row for G.729a.
Corrected frame size for G.729a+b. Added row for T.38. (PTR 32623)
Setting Busy Reason Codes: New section.
Example of Retrieving Call-Related Information section: Corrected both example
programs
Generating or Detecting DTMF Tones Using a Voice Resource: New section
Setting QoS Threshold Values and Retrieving QoS Threshold Values: Corrected
ParmSetID name in both code examples (PTR 32690)
Registration section: Corrected code example for SIP registration; added table to
map abstract registrar registration concepts to SIP REGISTER elements
Gatekeeper Registration Failure: New section.
Global Call Functions Supported by IP section: Added bullet to indicate support for
gc_GetCTInfo( )
gc_GetCTInfo( ) Variances for IP section: New section
gc_MakeCall( ) Variances for IP section: Clarified procedure for setting protocol to
use on multi-protocol devices. Added information to Forming a Destination
Address String section about specifying port address in TCP/IP destination
addresses.
gc_ReqService( ) Variances for IP section: Added SIP support for alias
gc_SetUserInfo( ) Variances for IP section: Added note about not using this function
to set protocol to use on multi-protocol devices.
gc_Start( ) Variances for IP section: Added note regarding network adaptor
enabling/disabling. Added information about initialization functions and
overriding defaults when appropriate.
Initialization Functions: New section
Summary of Parameter Sets and Parameter Usage table:
Added IPPARM_MEDIAWAITFORCONNECT, IPPARM_PRESENTATION_IND,
and IPPARM_PROGRESS_IND parameters to IPSET_CALLINFO
Added IPSET_H323_RESPONSE_CODE/IPPARM_BUSY_CAUSE parameter
Updated IPSET_LOCAL_ALIAS set entries to add SIP support
Added IPSET_SIP_RESPONSE_CODE/IPPARM_BUSY_REASON parameter
Parameter Set Reference section: Added and updated data type and size information
for all parameter sets in section
IPSET_CALLINFO section: Added entries for 3 new parameters
IPSET_H323_RESPONSE_CODE: New section
IPSET_REG_INFO section: Added row for IPPARM_REG_TYPE
IPSET_SIP_MSGINFO section: Added section for parameters used when setting
and retrieving SIP Message Information fields
IPSET_SIP_RESPONSE_CODE: New section
IP_VIRTBOARD structure description: Updated to refer to INIT_IP_VIRTBOARD()
initialization function. Added sup_serv_mask, h323_msginfo_mask, and
terminal_type fields (PTR 30491)
22Dialogic® Global Call IP Technology Guide — November 2007
Dialogic Corporation
Document No.Publication DateDescription of Revisions
05-2239-002
(continued)
05-2239-001September 2003Initial version of document.
IPADDR structure description: Added note that only supported ipv4 field value is
IP_CFG_DEFAULT. Added info about byte order for IPv4 addresses.
IPCCLIB_START_DATA structure description: Updated to refer to
IP-Specific Event Cause Codes chapter: Updated descriptions of the possible event
causes (PTR 31213:
Revision History
Dialogic® Global Call IP Technology Guide — November 200723
Dialogic Corporation
Revision History
24Dialogic® Global Call IP Technology Guide — November 2007
Dialogic Corporation
About This Publication
The following topics provide information about this publication.
• Purpose
• Applicability
• Intended Audience
• How to Use This Publication
• Related Information
Purpose
This publication documents the Dialogic® Global Call API for IP technology as it is implemented
in Dialogic
implementation in Dialogic
documents.
This guide is for users of the Dialogic
based IP H.323 or SIP technology. The Dialogic
and supports IP Media control capability. This guide provides Dialogic
specific information only and should be used in conjunction with the DialogicProgramming Guide and the Dialogic
generic behavior of the Dialogic
®
Host Media Processing Software Release 3.1LIN. The Dialogic® Global Call API
®
System Release software is documented in a separate set of
®
Global Call API who are writing applications that use host-
®
Global Call API Library Reference, which describe the
®
Global Call API.
®
Global Call API provides call control capability
®
Global Call API IP-
®
Global Call API
Applicability
This document version (05-2239-009) is published for Dialogic® Host Media Processing Software
Release 3.1LIN.
This document may also be applicable to other software releases (including service updates) on
Linux or Windows
determine whether this document is supported.
®
operating systems. Check the Release Guide for your software release to
Intended Audience
This guide is intended for:
• System Integrators
• Independent Software Vendors (ISVs)
• Value Added Resellers (VARs)
Dialogic® Global Call IP Technology Guide — November 200725
Dialogic Corporation
About This Publication
• Original Equipment Manufacturers (OEMs)
This publication assumes that the audience is familiar with the Windows
®
operating system and
has experience using the C programming language.
How to Use This Publication
This guide is divided into the following chapters:
• Chapter 1, “IP Overview”, gives a overview of VoIP technology and brief introductions to the
H.323 and SIP standards for novice users.
• Chapter 2, “Dialogic
Call API can be used with IP technology and provides an overview of the architecture.
• Chapter 3, “IP Call Scenarios”, provides some call scenarios that are specific to IP technology,
including scenarios for the call transfer supplementary service.
• Chapter 4, “IP-Specific Operations”, describes how to use Dialogic
perform IP-specific operations, such as setting call related information, registering with a
registration server, sending and receiving protocol-specific messages, etc.
• Chapter 5, “Third Party Call Control (3PCC) Operations and Multimedia Support”, describes
the Dialogic
®
application is not a direct participant in calls.
• Chapter 6, “Building Dialogic
building Dialogic
• Chapter 7, “Debugging Dialogic
debugging Dialogic
• Chapter 8, “IP-Specific Function Information”, documents functions that are specific to the IP
technology and describes additional functionality or limitations for specific Dialogic
Call API functions when used with IP technology.
• Chapter 9, “IP-Specific Parameters” provides a reference for IP-specific parameter set IDs and
their associated parameter IDs.
• Chapter 10, “IP-Specific Data Structures”, provides reference information for data structures
that are specific to the use of Dialogic
• Chapter 11, “IP-Specific Event Cause Codes” describes IP-specific event cause codes.
• Chapter 12, “Supplementary Reference Information” provides supplementary information
including technology references and formats for called and calling party addresses for H.323.
• A Glossary and an Index can be found at the end of the document.
®
Global Call API Architecture for IP”, describes how Dialogic® Global
®
Global Call API to
Global Call API library’s support for scenarios where the SIP call control
®
®
Global Call API applications that use IP technology.
®
Global Call API IP applications using RTF logging facilities.
Global Call API IP Applications” provides information for
®
Global Call API IP Applications” provides information for
Voice over IP (VoIP) can be described as the ability to make telephone calls and send faxes over IPbased data networks with a suitable Quality of Service (QoS). The voice information is sent in
digital form using discrete packets rather than via dedicated connections as in the circuit-switched
Public Switched Telephone Network (PSTN).
Currently, there are two major international groups defining standards for VoIP:
• International Telecommunications Union, Telecommunications Standardization Sector
(ITU-T), which has defined the following:
– Recommendation H.323, covering Packet-based Multimedia Communications Systems
(including VoIP)
• Internet Engineering Task Force (IETF), which has defined drafts of the several RFC (Request
for Comment) documents, including the following central document:
– RFC 3261, the Session Initiation Protocol (SIP)
1
The H.323 recommendation was developed in the mid 1990s and is a mature protocol.
SIP (Session Initiation Protocol) is an emerging protocol for setting up telephony, conferencing,
multimedia, and other types of communication sessions on the Internet.
1.2H.323 Overview
The H.323 specification is an umbrella specification for the implementation of packet-based
multimedia over IP networks that cannot guarantee Quality of Service (QoS). This section
discusses the following topics about H.323:
• H.323 Entities
• H.323 Protocol Stack
• Codecs
• Basic H.323 Call Scenario
• Registration with a Gatekeeper
• H.323 Call Scenario via a Gateway
Dialogic® Global Call IP Technology Guide — November 200729
Dialogic Corporation
IP Overview
1.2.1H.323 Entities
The H.323 specification defines the entity types in an H.323 network including:
Terminal
An endpoint on an IP network that supports the real-time, two-way communication with
another H.323 entity. A terminal supports multimedia coders/decoders (codecs) and setup and
control signaling.
Gateway
Provides the interface between a packet-based network (for example, an IP network) and a
circuit-switched network (for example, the PSTN). A gateway translates communication
procedures and formats between networks. It handles call setup and teardown and the
compression and packetization of voice information.
Gatekeeper
Manages a collection of H.323 entities in an H.323 zone controlling access to the network for
H.323 terminals, Gateways, and MCUs and providing address translation. A zone can span a
wide geographical area and include multiple networks connected by routers and switches.
Typically there is only one gatekeeper per zone, but there may be an alternate gatekeeper for
backup and load balancing. Typically, endpoints such as terminals, gateways, and other
gatekeepers register with the gatekeeper.
Multipoint Control Unit (MCU)
An endpoint that supports conferences between three or more endpoints. An MCU can be a
stand-alone unit or integrated into a terminal, gateway, or gatekeeper. An MCU consists of:
• Multipoint Controller (MC) – handles control and signaling for conferencing support
• Multipoint Processor (MP) – receives streams from endpoints, processes them, and
returns them to the endpoints in the conference
Figure 1 shows the entities in a typical H.323 network.
Figure 1. Typical H.323 Network
Terminal
LAN
Terminal
Terminal
MCU
Gatekeeper
Gateway
Router
PSTN
Internet or
Intranet
30Dialogic® Global Call IP Technology Guide — November 2007
Dialogic Corporation
Loading...
+ 574 hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.