Filter
Top Products
278
Dialogic Corporation
If the GC_PARM_BLK contains an IPSET_LOCAL_ALIAS /
IPPARM_ADDRESS_TRANSPARENT parameter element with the value
"*", all bindings that
exist in the specified Registrar for the specified Alias are deleted, regardless of what application
created them.
4.22.2.9 Deregistering
The Dialogic
®
Global Call API provides the ability to deregister from a Gatekeeper/Registrar.
When deregistering, the application can decide whether to keep the registration information locally
or delete it. To deregister, an application uses the gc_ReqService( ) function and passes it a
GC_PARM_BLK that contains the following element:
IPSET_REG_INFO
IPPARM_OPERATION_DEREGISTER
and one of the following values:
• IP_REG_MAINTAIN_LOCAL_INFO – keep the registration information locally
• IP_REG_DELETE_ALL – delete the local registration information
See Section 4.22.4.2, “Deregistration Example”, on page 283 for more information.
SIP
A SIP application can specify the Registrar and Alias to deregister by including the following
parameter in the GC_PARM_BLK that is passed to gc_ReqService( ):
IPSET_REG_INFO
IPPARM_REG_ADDRESS
• value = IP_REGISTER_ADDRESS structure with reg_client and reg_server fields filled
in to indicate the desired Registrar address and Alias
Note: This parameter is optional. If it is not included in the GC_PARM_BLOCK, or if either of the
addresses in the IP_REGISTER_ADDRESS structure is not supplied, the most recently used
Registrar address and Alias are used by default.
If the GC_PARM_BLK does not contain any IPSET_LOCAL_ALIAS elements specifying
Transport Addresses to be deleted, all bindings previously created by this application for the
specified Alias will be removed from the Registrar.
If the GC_PARM_BLK contains an IPSET_LOCAL_ALIAS /
IPPARM_ADDRESS_TRANSPARENT parameter element with the value
"*", all bindings that
exist in the specified Registrar for the specified Alias are deleted, regardless of what application
created them.
4.22.3 Sending and Receiving Nonstandard Registration
Messages (H.323)
The Dialogic
®
Global Call API provides the ability to send nonstandard messages to and receive
nonstandard messages from the gatekeeper or registrar. To send nonstandard messages, the
application uses the gc_Extension( ) function. The first element must be set as described in
Section 9.2.15, “IPSET_MSG_REGISTRATION”, on page 523. Other elements are set as in