Filter
Top Products
307
Dialogic Corporation
Source address is “sip:” URI, destination address is “sips:” URI
In this scenario, the transport protocol of initial INVITE is TLS and Global Call acts as TLS client.
Global Call will always use a “sip:” URI as local contact URI unless the application specifically
changes it, which means that the subsequent incoming request message should use UDP because
local URI is “sip:”.
The following figure illustrates an initial INVITE transaction where TLS is specified via a “sips:”
URI as the destination address. Note that the BYE transaction is UDP because the source address is
given as a “sip:” URI.
Figure 54. TLS with “sip:” Source Address and “sips:” Destination Address
App TLS
Client
Global Call
INVITE sips:friend@remote.com SIP/2.0
To:<sips:friend@remote.com>
From:<sip:user@local.com>
Via: SIP/2.0/TLS xxxxxx
Contact: <sip:user@local.com>
200 OK
To:<sips: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>
200 OK
From:<sips:friend@remote.com>
To:<sip:user@local.com>
Via: SIP/2.0/UDP xxxxxx
GCEV_DROPCALL
GCEV_RELEASECALL
gc_ReleaseCall()
gc_DropCall()
GCEV_CONNECTED
gc_MakeCall()
destination.address =
"sips:friend@remote.com"
origination.address =
"sip:user@local.com"
With TLS client configuration.
gc_Start()
App TLS
Server
Global Call
gc_Start()
GCEV_OFFERED
gc_Answer()
GCEV_ANSWERED
GCEV_DROPCALL
gc_ReleaseCall()
GCEV_RELEASECALL
With TLS server configuration.
gc_DropCall()
BYE
From:<sips:friend@remote.com>
To:<sip:user@local.com>
Via: SIP/2.0/UDP xxxxxx
GCEV_DISCONNECTED