Don_Gilletti@logitech.com wrote:
Greetings,
I seem to be having some trouble with the pa module on SER 0.10.99-dev0 running on Fedora 3.
I can REGISTER fine, and issuing a SUBSCRIBE results in a 200 OK response (and NOTIFYs being generated by the server).
However, both the 200 OK response to the SUBSCRIBE and the NOTIFY messages are all missing a Contact header field.
Here's the messages:
====================================================== Session Initiation Protocol Request-Line: SUBSCRIBE sip:dontest@172.17.76.25 SIP/2.0 Method: SUBSCRIBE Resent Packet: False Message Header To: sip:dontest@172.17.76.25 From: sip:don@172.17.76.25;tag=b029225f Via: SIP/2.0/UDP 172.17.84.29:5060;branch=z9hG4bK-d87543-671970329-1--d87543-;rport Call-ID: 7f37841cd1635a0b CSeq: 1 SUBSCRIBE Contact: sip:don@172.17.84.29:5060 Expires: 600 Max-Forwards: 70 Accept: application/pidf+xml Event: presence Content-Length: 0
Session Initiation Protocol Status-Line: SIP/2.0 200 OK Status-Code: 200 Resent Packet: False Message Header To: sip:dontest@172.17.76.25;tag=44274c5ba0cc60268b6a1c7eb3de8672-9325 From: sip:don@172.17.76.25;tag=b029225f Via: SIP/2.0/UDP 172.17.84.29:5060;branch=z9hG4bK-d87543-671970329-1--d87543-;rport=5060 Call-ID: 7f37841cd1635a0b CSeq: 1 SUBSCRIBE Server: Sip EXpress router (0.10.99-dev0 (i386/linux)) Content-Length: 0
Session Initiation Protocol Request-Line: NOTIFY sip:don@172.17.84.29:5060 SIP/2.0 Method: NOTIFY Resent Packet: False Message Header Via: SIP/2.0/UDP 172.17.76.25;branch=z9hG4bKaebf.9fd37101.0 To: sip:don@172.17.76.25;tag=855dae7f From: sip:dontest@172.17.76.25;tag=44274c5ba0cc60268b6a1c7eb3de8672-0ddd CSeq: 3 NOTIFY Call-ID: b063ea763c2f6d3d Content-Length: 245 User-Agent: Sip EXpress router(0.10.99-dev0 (i386/linux)) Event: presence Content-Type: application/pidf+xml Subscription-State: active;expires=594 Message body
======================================================
I've been looking at all the documentation I can find, and I can't seem to find out why these are being omitted.
Is there something wrong w/my configuration? (see below) Any suggestions why this might be ocurring?
don_g
This is probably a deficiency in the PA module code. I'll take a look.
Jamey