[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Sip] One chart //"UPDATE during Re-INVITE" discussion

Data (like Contact, Session-Expires, and etcetera) that was successfully updated by F3/F4 still apply after F7.  Thus F8 data should reflect (and can attempt to modify) adjustments made during F3/F4.



From: sip-bounces@xxxxxxxx [mailto:sip-bounces@xxxxxxxx] On Behalf Of gao.yang2@xxxxxxxxxx
Sent: Wednesday, March 11, 2009 11:47 PM
Cc: Gonzalo Camarillo; Christer Holmberg
Subject: [Sip] One chart //"UPDATE during Re-INVITE" discussion


      UAC                   UAS
       | session established |
       |                     |
       | F1  re-INVITE (SDP) |
       | F2 1xx-rel (SDP)    |
       | F3   UPDATE         |
       |<--------------------| Target refreshing
       | F4 2xx UPT          |
       |                     |
       | F5/6 Cancel/200OK   |
       | F7    487 INV       |
       | F7     ACK          |
       | F8  re-INVITE (SDP) |
       |-------------------->| Using which dialog state

F3/F4 is about target refreshing.

And if UAC sends Cancel UAS sends 487. The first Re-INVITE is discarded.

But if UAC sends another Re-INVITE, which dialog state should it use?

I think is the one refreshed by F3. That's the merit of regarding UPDATE/200OK's atomicity.

Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sip@xxxxxxxx for new developments of core SIP

[IETF Announce]     [IETF Discussion]     [Linux SCSI]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Photo]     [Yosemite News]    [Yosemite Photos]    [Free Online Dating]     [Linux Kernel]     [Linux SCSI]     [XFree86]     [Big List of Linux Books]

Add to Google Powered by Linux