There is a lot of mis-information in this thread.
The situation is entirely valid. It means that the UAC does not support
session timer, but a proxy along the path would like to use session timer.
If the UAS is capable of supporting session timer, it should put a
Session-Expires header into the response with the refresher set to
"uas". The RFC seems silent in this case on whether a Supported:timer
should be inserted - I think it is irrelevant.
Doing as above will provide the session timer service that the proxy
desired. (It only takes one of the uac/uas to support it for it to work.)
Of course, if the UAS does not support session timer it will do nothing.
There will be no Session-Expires in the response and the proxy will
learn that it cannot have the session timer it desired.
Paul
saragadam krishna wrote:
Hi all
If UAS receives session refresh request without supported header and
with session-expires header and min-se header then what response UAS need to
send?
---------------------------------
Yahoo! for Good
Click here to donate to the Hurricane Katrina relief effort.
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
_______________________________________________
Sip-implementors mailing list
[email protected]
http://lists.cs.columbia.edu/mailman/listinfo/sip-implementors
