Hi,
As per 3261, the text for Supported and Require is as below-
Supported:
If the UAC supports extensions to SIP that can be applied by the
server to the response, the UAC SHOULD include a Supported header
field in the request listing the option tags (Section 19.2) for those
On 06/24/2011 12:34 AM, Harbhanu wrote:
Hi,
As per 3261, the text for Supported and Require is as below-
Supported:
If the UAC supports extensions to SIP that can be applied by the
server to the response, the UAC SHOULD include a Supported header
field in the request listing the
I think the rule of thumb is Supported indicates what is supported
by UAC and Require indicates what needs to be supported by UAS
(otherwise it should reject the request)
In cases like session-timer you can see that Supported and Require
mean different things (because session-timer can be
Is it valid to interpret that an extension present
in 'Require' is also 'Supported' by the UAC?
No; see rfc4028.
In other words, is it mandatory to put an extension
in both headers, incase 'Require' is used for any
extension?
No; rfc3262 is an example of including Require 100rel within
On 06/24/2011 07:18 AM, Brett Tate wrote:
Is it valid to interpret that an extension present
in 'Require' is also 'Supported' by the UAC?
No; see rfc4028.
That's... bizarre :-)
--
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kflem...@digium.com | SIP:
Supported and Require are not formally linked.
For some options you can infer a logical connection.
When in doubt, be explicit.
Also note that Require:xyz means I require you to *support* xyz. It
does not mean I require you to *use* xyz or I intend to use xyz.
Thanks,
Paul
On
