Re: interworking(1/2) of INVITE and UPDATE

Hi Shinji,

I feel your charts seems the same as RFC3311 and O/A draft.

Could you tell us more about your problem?

Thanks,

Gao

===================================
 Zip    : 210012
 Tel    : 87211
 Tel2   :(+86)-025-52877211
 e_mail : [email protected]
===================================

[email protected] 写于 2010-04-22 16:23:12:

> Hi all,
> 
> At this chance, I want to hear your opinion about the
> interworking of INVITE and UPDATE.
> 
> This is related to chapter 4 in a offeranswer draft,
> 
> Regarding "5.1 Sending an UPDATE" of RFC3311, Paul said that
> "this language itself is non-normative and is justified as
> a corollary of 3261."
> 
> I think so, but these descriptions are also very messy.
> About the timing when UA can send an UPDATE request,
> at last I think as the following,
> 
>        A                               B
>       *|                               |*
>       *|ini/re-INVITE(offer)           |*
>        |------------------------------>|
>        |                1xx-rel(answer)|
>        |<------------------------------|
>        |PRACK                          |
>        |------------------------------>|
>        |                     200(PRACK)|
>        |<------------------------------|
>       *|                               |*<-- after this pont, UA may
>       *|                               |*    send UPDATE with offer
>       *|                               |*
> 
>        A                               B
>       *|                               |*
>       *|ini/re-INVITE(no offer)        |*
>        |------------------------------>|
>        |                 1xx-rel(offer)|
>        |<------------------------------|
>        |PRACK(answer)                  |
>        |------------------------------>|
>        |                     200(PRACK)|
>        |<------------------------------|
>       *|                               |*<-- after this pont, UA may
>       *|                               |*    send UPDATE with offer
>       *|                               |*
> 
> Do you have any questions or comments?
> 
> Regards,
> Shinji
> _______________________________________________
> Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
> This list is for NEW development of the application of SIP
> Use [email protected] for questions on current sip
> Use [email protected] for new developments of core SIP
> 



--------------------------------------------------------
ZTE Information Security Notice: The information contained in this mail is solely property of the sender's organization. This mail communication is confidential. Recipients named above are obligated to maintain secrecy and are not permitted to disclose the contents of this communication to others.
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the originator of the message. Any views expressed in this message are those of the individual sender.
This message has been scanned for viruses and Spam by ZTE Anti-Spam system.

_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email protected] for questions on current sip
Use [email protected] for new developments of core SIP