Dialogic Global Call IP Benutzerhandbuch

268

Dialogic Corporation

See the Dialogic

 Global Call API Programming Guide for more information about the operation 

of GCAMS and the Dialogic

 Global Call API Library Reference for more information about 

GCAMS functions. 

In an H.323 network, a Gatekeeper manages the entities in a specific zone and an endpoint must 
register with the Gatekeeper to become part of that zone. In a SIP network, a Registrar manages a 
set of associations or bindings between Addresses-of-Record and actual endpoint addresses for a 
domain. The Dialogic

®

 Global Call API provides applications with the ability to perform endpoint 

registration. These capabilities are described in the following topics: 

The Dialogic

®

 Global Call API provides a number of options for registration and manipulation of 

registration information. The Dialogic

®

 Global Call API simplifies and abstracts the network RAS 

messages in H.323 and REGISTER messages in SIP. 

When using the Dialogic

®

 Global Call API to perform endpoint registration, the following general 

conditions and restrictions apply: 

An application must use an IPT board device handle to perform registration. A board device 
handle can be obtained by using gc_OpenEx( ) with a devicename parameter of “N_iptBx”. 

When using the gc_ReqService( ) function, two mandatory parameter elements, 
GCSET_SERVREQ / PARM_REQTYPE and GCSET_SERVREQ / PARM_ACK, are 
required in the GC_PARM_BLK parameter block. These parameters are required by the 
generic service request mechanism provided by Dialogic

®

 Global Call API and are not sent in 

any registration message. 

When setting H.323 alias or SIP Transport Address information, the gc_ReqService( ) 
function can include more than one address in the GC_PARM_BLK associated with the 
function. Prefixes are ignored for SIP. 

Registration operations cannot be included in the preset registration information using 
gc_SetConfigData( ). 

In H.323, the following operations (and the corresponding RAS messages) are supported: 

locating a gatekeeper via unicast or multicast (RAS messages: GRQ/GCF/GRJ) 

registration (RAS message: RRQ)