Accept-Contact : explicit/required feature tags must be supported

[GoogleCodeExporter]

According to RFC 3041 [Caller Preferences for the Session Initiation Protocol 
(SIP)], explicit/required feature tags of the Accept-Contact header must be 
supported.

------------------
RFC 3841 page 6

The precise behavior depends heavily on whether the "require" and "explicit" 
parameters are present.  When both of them are present, a proxy will only 
forward the request to contacts which have explicitly indicated that they 
support the desired feature set.  Any others are discarded.  As such, a UAC 
should only use "require" and "explicit" together when it wishes the call to 
fail unless a contact definitively matches.  It's possible that a UA supports a 
desired feature, but did not indicate it in its registration.  When a UAC uses 
both "explicit" and "require", such a contact would not be reached.  As a 
result, this combination is often not the one a UAC will want.

---------------------

This means that those feature tags must be inserted into the register.
As a consequence, a new registration must be performed upon feature tags change.

Original issue reported on code.google.com by lemordan...@gmail.com on 30 Apr 2015 at 10:11

[GoogleCodeExporter]

This issue was closed by revision cf674e440bcf.

Original comment by lemordan...@gmail.com on 30 Apr 2015 at 10:25

• Changed state: Fixed

[GoogleCodeExporter]

This issue was closed by revision 7e9216687dcd.

Original comment by lemordan...@gmail.com on 1 May 2015 at 4:50

[GoogleCodeExporter]

This issue was closed by revision 155741f17792.

Original comment by lemordan...@gmail.com on 5 May 2015 at 1:36

[GoogleCodeExporter]

This issue was closed by revision 155741f17792.

Original comment by lemordan...@gmail.com on 7 May 2015 at 8:02