[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Sip] One chart //"UPDATE during Re-INVITE" discussion
Hi,
If the UAC receives the 487 and can't fallback to the
pre-reINVITE state, it sends a new re-INVITE with something that it
DOES supports. That is also described in Gonzalo's draft, I
belive.
And, you could have the same problem if the target refresh
was done already in the re-INVITE/18x. If the UAC then sends CANCEL, and can't
fall back, it will have to send a new re-INVITE.
I also think it is bad practise to do a target refresh in a
nested UPDATE, but that's a separate issue.
Regards,
Christer
Hi,
I just mean that if we treat F3 as sub-transaction of
F1, then after F7(ACK), UAC can discard refreshed dialog state in F3.
And it may make the two parts can not
communicate anymore in current dialog.
And IMO, this is a counterevidence for treating all UPDATE(during
Re-INVITE) as sub-transaction of Re-INVITE.
Gao
| "Christer Holmberg"
<christer.holmberg at ericsson.com>
2009-03-12 15:31
|
|
收件人
| <gao.yang2 at zte.com.cn>,
"SIP" <sip at ietf.org>, "SIPPING"
<sipping at ietf.org>
|
|
抄送
| "Gonzalo Camarillo"
<gonzalo.camarillo at ericsson.com>
|
|
主题
| RE: One chart //"UPDATE
during Re-INVITE" discussion |
|
In my opinion 487 should trigger whatever actions/rollback
that any other non-200 response sent by the UAS would.
Regards,
Christer
From: gao.yang2 at zte.com.cn
[mailto:gao.yang2 at zte.com.cn]
Sent: 12. maaliskuuta 2009
5:47
To: SIP; SIPPING
Cc: Christer Holmberg; Gonzalo
Camarillo
Subject: 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.
--------------------------------------------------------
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.
--------------------------------------------------------
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.