[Asterisk-Users] SIP Issues, debug attached

[Mark Spencer]

> SIP Debugging Enabled
> *CLI> DEBUG[2051]: File chan_sip.c, Line 401 (create_addr): Setting NAT on RTP to 0
> Interface is eth0
> IP Address is 172.16.17.7
> 11 headers, 1 lines
> XXX Need to handle Retransmitting XXX:
> NOTIFY sip:2111 at 172.16.17.51 SIP/2.0
> Via: SIP/2.0/UDP 172.16.17.7:5060;branch=4b0dd9a4
> From: "asterisk" <sip:asterisk at 172.16.17.7>;tag=4083ff58
> Contact: <sip:asterisk at 172.16.17.7>
> To: <sip:2111 at 172.16.17.51>
> Call-ID: 70067c4519aa10d161636c627959a811 at 172.16.17.7
> CSeq: 102 NOTIFY
> User-Agent: Asterisk PBX
> Event: message-summary
> Content-Type: text/plain
> Content-Length: 20
>
> Message-Waiting: no
>  (no NAT) to 172.16.17.51:5060

This is us transmitting a message waiting indicator.  We do this because
you have a mailbox=<foo> in your sip.conf somewhere.

> Sip read:
> SIP/2.0 200 OK
> Via: SIP/2.0/UDP 172.16.17.7:5060;branch=4b0dd9a4
> From: asterisk<sip:asterisk at 172.16.17.7>;tag=4083ff58
> To: sip:2111 at 172.16.17.51
> Call-ID: 70067c4519aa10d161636c627959a811 at 172.16.17.7
> CSeq: 102 NOTIFY
> Server: DTA SIP/0.11.7 NNOS/VR30
> Content-Length: 0

It was my understanding that the device receiving the NOTIFY did *not*
send a 200 OK back, but
http://www.ietf.org/internet-drafts/draft-ietf-sipping-mwi-02.txt suggests
that it does, although it does not provide an example of an unsolicited
NOTIFY, and upon closer inspection the Cisco also sends me the 200 OK.
The message is harmless, but I suppose we could make the channel hang
around until it received a 200 OK back.  At some point I think we just
need to implement retransmissions in one way or another.

Mark