Dear Gonzalo Camarillo
Two sides can have different precondition, so it can be one side's precondition satisfied while the other's not.
And this will make the two sides have different session state.
But rollback the session state after 4xx, will make the session state clear.(if the modification is triggered by Re-INVITE)
If the modification is triggered by UPDATE(no matter during or outside Re-INVITE), it has nothing to do with Re-INVITE.
And if the other side can not accept it without user's permition(or with mandatory precondition), the other side should reject it by 504(defined in RFC3311).
But if it accept it, the modification would be committed.
Triggering a new modification with precondition using UPDATE is an interesting thing.(I recommend to do so using Re-INVITE)
The session modification would be committed in signal level, but suspended in media level. But the session state is clear.
yours Gao
| Gonzalo Camarillo <Gonzalo.Camarillo@xxxxxxxxxxxx>
发件人: sipping-bounces@xxxxxxxx 2009-02-26 21:01 |
|
Hi Christer,
> Assume that one side has indicated that his preconditions are met, but
> the other side has still not indicated it. What happens now if the
> re-INVITE fails?
endpoints always know what is the session "in use" because that is the
way their media tools are currently configured. Therefore, no matter
what the precondition state is, you always revert to the state your
media tools are in.
Of course, race conditions may be an issue, but not only in this
particular case. They are a general issue that needs to be resolved in a
general way.
Cheers,
Gonzalo
_______________________________________________
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
-------------------------------------------------------- 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 sip-implementors@xxxxxxxxxxxxxxx for questions on current sip Use sip@xxxxxxxx for new developments of core SIP
