[SIPForum-discussion] Call Gets Answered During UPDATE?

qcorba qcorba at gmail.com
Thu Feb 18 15:21:01 UTC 2016


Oops.

Please see RFC3311. Hope that helps.

Heather Mayhan <heather.mayhan at ericsson.com> 於 2016年2月18日星期四 寫道:

> Qcorba,
>
>
>
> Thanks for that info, but I knew that.  My question is more of if the
> messaging for the UPDATE and ANSWER seem to overlap one another.
>
>
>
> My understanding from input yesterday is, all of the transactions to
> satisfy the UPDATE need to be completed before the 200 OK for the ANSWER is
> processed?
>
>
>
>
>
> *From:* qcorba [mailto:qcorba at gmail.com
> <javascript:_e(%7B%7D,'cvml','qcorba at gmail.com');>]
> *Sent:* Wednesday, February 17, 2016 23:52
> *To:* Heather Mayhan
> *Cc:* discussion at sipforum.org
> <javascript:_e(%7B%7D,'cvml','discussion at sipforum.org');>
> *Subject:* Re: [SIPForum-discussion] Call Gets Answered During UPDATE?
>
>
>
> 200 OK has CSeq header field which consists of a sequence number and a
> method.
>
>
>
> If it is an answer, the method is INVITE.
>
>
>
> If it is a reply to UPDATE, the method is UPDATE.
>
>
>
> Please see RFC3261 for details.
>
> Heather Mayhan <heather.mayhan at ericsson.com
> <javascript:_e(%7B%7D,'cvml','heather.mayhan at ericsson.com');>> 於 2016年2月18
> 日星期四 寫道:
>
> I have been trying to muddle through the question of, say you have a call
> IN PROGRESS, but not yet answered.
>
>
>
> SIP UPDATE method is being used several times during the call set up, and
> being sent end-to-end.
>
>
>
> What would the expected behavior be if the 200 OK indicating call ANSWER
> is received in between a SIP UPDATE and the corresponding 200 OK for that
> UPDATE?
>
>
>
> Would the 200 OK indicating call ANSWER prevail, or should the UPDATE be
> acknowledged before sending on 200 OK for ANSWER?
>
>
>
> Best regards,
>
> *Heather *
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20160218/078e725f/attachment-0002.html>


More information about the discussion mailing list