On 11/18/13 11:31 PM, Vivek Gupta wrote:
> RFC section 10.2.1 says below:
>
> The Contact header field values of the request typically consist of SIP or
> SIPS URIs that identify particular SIP endpoints (for example, “
> sip:ca...@cube2214a.chicago.com”), but they MAY use any URI scheme.* A **SIP
Please find the attachment as well.
On Tuesday, 19 November 2013 12:05 PM, sampat patnaik
wrote:
Hi All,
Can anyone help me on this case...
We have a Mobile PBX solution, where we route the mobile to our VoIP platform
using SUD: OICK & TICK
We can call from and to MPBX from and to all
I think that cause equals 16 is "Normal call clearing", can't find
attachment, seems it's not allowed by mailing list.
2013/11/19 sampat patnaik
> Hi All,
>
> Can anyone help me on this case...
>
> We have a Mobile PBX solution, where we route the mobile to our VoIP
> platform using SUD: OICK &
Hi Vivek,
One of the use cases can be in IMS - wherein the SCSCF on the basis of some
service specific criteria redirects(302) the session attempt to a CS domain
endpoint. You can have a look at the call flow in section 10.4.3 of
following 3gpp spec :
http://www.3gpp.org/ftp/tsg_sa/wg3_security/T
