===================================
高扬/固网软件开发一部/中心研究院/中兴通讯
Tel : 87211
MSN : tzgynew@xxxxxxxxxxx
e_mail : gao.yang2@xxxxxxxxxx
Addr :南京市雨花台区紫荆花路68号 210012
===================================
| "Christer Holmberg"
<christer.holmberg@xxxxxxxxxxxx>
发件人: sip-bounces@xxxxxxxx 2009-03-10 23:15 |
|
Hi,
>>Regarding your second bullet, I don't even think that one should send
>>"nested" UPDATEs, if they don't have anything to do with the
>>re-INVITE. I think that is bad application design.
>>Non-related changes should be done outside the re-INVITE transaction.
>
>Sending UPDATE per RFC 4028 to refresh or audit the dialog is
>one of the times UPDATE may be tried while a re-INVITE is occurring.
True, but normally those UPDATEs are not going to modify session parameters.
So, yes, it may happen, but I think we should recommend against doing so.
Regards,
Christer
_______________________________________________
Sip mailing list https://www.ietf.org/mailman/listinfo/sip
This list is for NEW development of the core SIP Protocol
Use sip-implementors@xxxxxxxxxxxxxxx for questions on current sip
Use sipping@xxxxxxxx for new developments on the application of 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
