Re: Pls clarify on session timer

"Avasarala Ranjit-A20990" <[email protected]>
Newsgroups gmane.ietf.sipping,gmane.ietf.sip
Message-ID <[email protected]>
Hi Prakash
 
The Server sends a 420 when it doesn't support "timer" option-tag. so
its working fine when you remove it from your request.
 
As per section 7.1 of RFC 4028, the UAC SHALL include a Require header
with option-tag as "time" in the initial INVITE when it wants the server
to support session timer - but this does not necessarily mean that UAC
wants the server to perform refresh - but only wants the server to
support the session timer.
 
but if the UAC includes a Proxy-Require header with value as "timer", in
the initial INVITE then the server MUST support "session-timer" in order
to process the request.
 
But again as per RFC Require and Proxy-Require headers are not
recommended to be used - but a UAC needs to include "Session-Expires"
header field to indicate to the server to apply Session Timer.

Regards 
Ranjit 
 

________________________________

From: [email protected] [mailto:[email protected]] On
Behalf Of Prakash Ganesan
Sent: Friday, March 13, 2009 5:08 PM
To: [email protected]; [email protected]
Subject: [Sipping] Pls clarify on session timer


Hi All,
I am facing a problem with the session timer.
 
The refesh re-invite contains header field Require: timer and my server
is rejecting the request with 420 bad extension. When I remove the
header field Reqire: timer, it is working fine. 
I am bit confused with the section 7.1 Generating an Initial Session
Refresh Request, in RFC 4028 it is referring to the first SIP invite or
the first session refresher (re-Invite)


-- 
Cheers
Prakash

_______________________________________________
Sipping mailing list  https://www.ietf.org/mailman/listinfo/sipping
This list is for NEW development of the application of SIP
Use [email protected] for questions on current sip
Use [email protected] for new developments of core SIP
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.