Re: [Sip-implementors] Identifying Session Refresh UPDATE

2010-11-08 Thread Sumit Jindal
-implementors-boun...@lists.cs.columbia.edu [mailto:sip-implementors-boun...@lists.cs.columbia.edu] On Behalf Of Priya Arya Sent: Monday, November 08, 2010 9:33 AM To: sip-implementors@lists.cs.columbia.edu Subject: [Sip-implementors] Identifying Session Refresh UPDATE Hi, I have one query regarding

Re: [Sip-implementors] Identifying Session Refresh UPDATE

2010-11-08 Thread Paul Kyzivat
An UPDATE is an UPDATE. The effect is strictly a function of its content. And as already mentioned, every UPDATE either refreshes the session timer, or disables it, regardless of what else it does. I suppose you might consider that an UPDATE that does nothing else must have been intended only

[Sip-implementors] Identifying Session Refresh UPDATE

2010-11-07 Thread Priya Arya
Hi, I have one query regarding the Session Refresh UPDATE. - Just by looking at PDU of UPDATE in a session, can it be idenitified that if this UPDATE is for session refresh or for updating the SDP parameters in the session. Actually RFC 4028 recommends the following : It is RECOMMENDED that

Re: [Sip-implementors] Identifying Session Refresh UPDATE

2010-11-07 Thread Tarun2 Gupta
@lists.cs.columbia.edu Subject: [Sip-implementors] Identifying Session Refresh UPDATE Hi, I have one query regarding the Session Refresh UPDATE. - Just by looking at PDU of UPDATE in a session, can it be idenitified that if this UPDATE is for session refresh or for updating the SDP parameters