Dialogic Dialogic Global Call IP IP Phone User Manual


 
132 Dialogic
®
Global Call IP Technology Guide — November 2007
Dialogic Corporation
IP-Specific Operations
4.4.1 Setting and Retrieving Disconnect Cause or Reason Values
Use the cause parameter in the gc_DropCall( ) function to specify a disconnect reason/cause to be
sent to the remote endpoint.
Note: When using SIP, reasons are only supported when a call is disconnected while in the Offered state.
Use the gc_ResultInfo( ) function to get the reason/cause of a GCEV_DISCONNECTED event.
This reason/cause could be sent from the remote endpoint or it could be the result of an internal
error.
IP-specific reason/cause values are specified in the eIP_EC_TYPE enumerator defined in the
gcip_defs.h header file.
4.4.2 Setting Busy Reason Codes
Both SIP and H.323 define request response codes that can be included in the failure response
messages that are sent when a local system cannot take additional incoming sessions. Global Call
allows applications to set SIP and H.323 busy code values on a virtual board level.
SIP and H.323 busy codes are configured independently, and the configuration of each can be
changed at any time. The busy codes are configured by calling gc_SetConfigData( ) using the
following parameter set ID and parameter ID:
for SIP: IPSET_SIP_RESPONSE_CODE and IPPARM_BUSY_REASON; see
Section 9.2.25, “IPSET_SIP_RESPONSE_CODE”, on page 532.
for H.323: IPSET_H323_RESPONSE_CODE and IPPARM_BUSY_CAUSE; see
Section 9.2.8, “IPSET_H323_RESPONSE_CODE”, on page 519.
4.4.2.1 Setting SIP Busy Code
For SIP, RFC3261 defines three applicable busy codes:
480 Temporarily Unavailable
The callee’s end system was contacted successfully, but the callee is currently unavailable. For
example, the callee may be not logged in, may be in a state that precludes communication, or
may have activated the “do not disturb” feature. This busy code is also returned by a redirect or
proxy server that recognizes the user identified by the Request-URI but does not currently have
a valid forwarding location for that user.
486 Busy Here
The callee’s end system was contacted successfully, but the callee is currently not willing or
able to take additional calls at this end system. This response should be used if the user could
be available elsewhere.
600 Busy Everywhere
The callee’s end system was contacted successfully, but the callee is busy and does not wish to
take the call at this time. This response should be used if the callee knows that no other end
system will be available to accept this call.