I missed that the parameter was even in the trace. SipXtapi is only
looking at the headers. I will open an issue, and hopefully submit a
patch
Charlie
Marnus van Niekerk wrote:
Guys,
I had a look at section 10.3 item 8 as well and I disagree.
Each Contact value MUST feature an "expires"
parameter indicating its expiration interval chosen by the
registrar.
The key here is that it says "parameter" not "header" - the expires
MUST be a parameter in the Contact header, not a header on it's own.
Openser returns an expires parameter in the Contact header and
therefore is compliant.
It is the sipXtapi stack that does not handle it correctly.
M
Dale R. Worley wrote:
On Wed, 2006-11-08 at 22:36 -0600, Charlie Hedlin wrote:
I just read more of rfc3261 and it apears openSER is not compliant for
doing this, but we should probably still cope..
I just looked at section 10.3, item 8, and I agree with you.
I suppose the best way to handle this is to ignore the contact without
an expires parameter, and log an error at least at the ERR level.
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
|
_______________________________________________
sipxtapi-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipxtapi-dev/
