Yes, you are right, I will fix that. Thanks for the report.
Jan.
On 18-06 12:13, Doug Raum wrote:
I'm starting to use the pa module, and noticed
that when it gets a SUBSCRIBE, the 200 response doesn't have an expires header, as it
should. (RFC 3265, 3.1.1)
SUBSCRIBE sip:vmail@192.168.0.5 SIP/2.0
Via: SIP/2.0/UDP voipdev3.zoom.com:33050;rport
From: <sip:8100100@192.168.0.5:5060>;tag=a67e989d-13c4-173-5ac26-24be
To: <sip:vmail@192.168.0.5>
CSeq: 1 SUBSCRIBE
Call-ID: b5bb80-a67e989d-13c4-173-5ac26-5440
Expires: 3600
Event: presence
Max-Forwards: 70
Supported: replaces
Contact: <sip:8100100@192.168.0.5:5060>
Content-Length: 0
SIP/2.0 200 OK
Via: SIP/2.0/UDP voipdev3.zoom.com:33050;rport=33050;received=192.168.0.10
From: <sip:8100100@192.168.0.5:5060>;tag=a67e989d-13c4-173-5ac26-24be
To: <sip:vmail@192.168.0.5>;tag=92462461b2a59d6c6be4b5af5841f077-b62f
CSeq: 1 SUBSCRIBE
Call-ID: b5bb80-a67e989d-13c4-173-5ac26-5440
Content-Length: 0
I haven't spent a lot of time looking at the code for pa, but should this be an easy
thing to fix?
Thanks,
--
Doug
_______________________________________________
Serusers mailing list
serusers(a)lists.iptel.org
http://lists.iptel.org/mailman/listinfo/serusers