On 2/23/14 8:32 PM, Aditya Kumar wrote:
> Hi,
> What is the use of UE keeping feature-tags in Contact Header of INVITE?
They indicate the features of the UAC at the time of the INVITE.
One commonly used here is isFocus.
> I see some UEs keeping. feature-tags in contact of REGISTER make sense...n
Hi,
What is the use of UE keeping feature-tags in Contact Header of INVITE?
I see some UEs keeping. feature-tags in contact of REGISTER make sense...not
sure about having it in INVITE?
also if UE wants why not it use "Feature-Caps "Header? I see as per rfc only
servers use this?
-Adi
___
> SIP calls are failing due to differing session versions
> received in the SDP of the 183 and 200ok messages. The
> MSC server releases the call immediately due to
> unexpected SDP version received in 200 OK.
> MSC will release the call. This is normal expected behavior.
It is not expected beh
Hi Brett,
Thank You for the analysis.Yes, it is true that even if UAC doesn't support
TIMER but as per RFC it must be ready to accept SESSION EXPIRY from UAS. Also i
would like to bring in your notice that BYE was sent within 4 secs.So i have
done detailed analysis and observed that
SIP
call
> I have read rfc 3261, which according to 17.2.3 the
> branch parameter in the topmost Via header field of
> the request should be examined to match requests to
> transactions. Cseq should only be checked if the
> branch parameter in the top Via header s not present.
Yes; the magic cookie matchin
> can B side respond to the timer offer with
> a new offer "before" answering the first one?
Yes.
> 200OK for INV is the last to be sent so if it
> supersedes the UPD/200OK transaction what's
> the point of putting session timer in UPDATE
> anyway ...
Among other reasons, it allows the proxies t
