Dialogic Dialogic Global Call IP IP Phone User Manual


 
306
Dialogic Corporation
2. If the E_SIP_DefaultTransport field in the IP_VIRTBOARD structure is ENUM_TCP, only
TCP will be used as transport protocol. No TLS will be used in the initial INVITE.
Global Call will always use a “sip:” URI as the local contact URI unless this is specifically changed
by the application.
The following figure illustrates an initial INVITE with TLS where both source and destination
addresses use the “sip:” scheme. In this case, the DNS resolves the required transport to be TLS.
Note that in the 200 OK to the INVITE, the Contact URI has changed to the “sips:” scheme, which
causes the subsequent ACK and BYE transactions to use TLS transport.
Figure 53. TLS with “sip:” Source Address and “sip:” Destination Address
App TLS
Client &
Server
Global Call
INVITE sip:friend@remote.com SIP/2.0
To:<sip:friend@remote.com>
From:<sip:user@local.com>
Via: SIP/2.0/TLS xxxxxx
Contact: <sip:user@local.com>
200 OK
To:<sip:friend@remote.com>
From:<sip:user@local.com>
Via: SIP/2.0/TLS xxxxxx
Contact: <sips:friend@remote.com>
ACK
To:<sips:friend@remote.com>
From:<sip:user@local.com>
Via: SIP/2.0/TLS xxxxxx
Contact: <sip:user@local.com>
BYE
To:<sips:friend@remote.com>
From:<sip:user@local.com>
Via: SIP/2.0/TLS xxxxxx
200 OK
To:<sips:friend@remote.com>
From:<sip:user@local.com>
Via: SIP/2.0/TLS xxxxxx
GCEV_DROPCALL
GCEV_RELEASECALL
gc_ReleaseCall()
gc_DropCall()
GCEV_CONNECTED
gc_MakeCall()
destination.address =
"sip:friend@remote.com"
origination.address =
"sip:user@local.com"
With TLS client and server configuration,
UDP is default transport.
No outbound proxy is configured.
gc_Start()
App TLS
Client &
Server
Global Call
With TLS client and server configuration,
UDP is default transport.
No outbound proxy is configured.
gc_Start()
DNS resolves remote.com
transport to be TLS.
GCEV_OFFERED
gc_Answer()
Contact: <sips:friend@remote.com>
GCEV_ANSWERED
GCEV_DISCONNECTED
gc_DropCall()
GCEV_DROPCALL
gc_ReleaseCall()
GCEV_RELEASECALL