Hello,
it looks like a bug in the server. The contact in the registrar doesn't
have methods="MESSAGE" parameter but this parameter shouldn't be
compared in this case. I'll look at it.
BTW, I recommend you to upgrade your server (you are using pre13) to the
latest CVS snapshot, it is more stable.
Jan.
On 23-05 15:54, magnus melin wrote:
Hallo
When trying to unregister SER response the 200 OK contact header contains
expire=3392 shouldent it be 0.
According to RFC 3261:
8. The registrar returns a 200 (OK) response. The response MUST
contain Contact header field values enumerating all current
bindings. Each Contact value MUST feature an "expires"
parameter indicating its expiration interval chosen by the
registrar. The response SHOULD include a Date header field.
Trace from the unregister:
Session Initiation Protocol
Request line: REGISTER sip:172.18.3.164;transport=UDP SIP/2.0
Message Header
Via: SIP/2.0/UDP
172.18.1.66:5061;branch=z9hG4bK7cd705dd53972643a94681a4ce431160
Contact: "w"
<sip:w@172.18.1.66:5061>;methods="MESSAGE";expires=0
Call-Id: de06a67588716c53ac5521929699d262(a)172.18.1.66
CSeq: 3 REGISTER
From: "w" <sip:w@e-horizon.se>;tag=8331
To: "w(a)e-horizon.se" <sip:w@e-horizon.se>
Content-Length: 0
Status line: SIP/2.0 200 OK
Message Header
Via: SIP/2.0/UDP
172.18.1.66:5061;branch=z9hG4bK7cd705dd53972643a94681a4ce431160
Call-Id: de06a67588716c53ac5521929699d262(a)172.18.1.66
CSeq: 3 REGISTER
From: "w" <sip:w@e-horizon.se>;tag=8331
To: "w(a)e-horizon.se"
<sip:w@e-horizon.se>;tag=a12148d613273d13cea75bbc18673103.bac8
Contact: <sip:w@172.18.1.66:5061>;q=0.00;expires=3392
Server: Sip EXpress router (0.8.11pre13 (i386/linux))
Content-Length: 0
Regards Magnus
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers