[asterisk-dev] cisco-check-cfg

[Kevin P. Fleming]

On 07/29/2011 08:32 AM, Hoggins! wrote:
> Hello list,
>
> I think there is a bug when we ask Asterisk to send a SIP NOTIFY. I use
> 1.8.5.0, and I try to send a "check-sync" event to my Cisco phones. It
> used to work, and now it doesn't anymore.
> Digging into the packets, I found that some headers are not the same in
> the NOTIFY requests sent by Asterisk :
>
> For a request like OPTIONS, I have the following headers :
>      From: "asterisk"<sip:asterisk at 192.168.34.10>;tag=as6cce8863
>      [...]
>      Contact:<sip:asterisk at 192.168.34.10:5060>
>
> But for a NOTIFY request, I get :
>      From: "asterisk"<sip:asterisk@[::1]:0>;tag=as7372802b
>      [...]
>      Contact:<sip:asterisk@[::1]:0>
>
> I'm no expert, but I guess the adresses are wrong, as the phone will try
> to answer on [::1] (are Cisco 79xx IPv6 capable), their own loopback
> address. The answer never returns to Asterisk, and I get a :
>
> [2011-07-29 14:07:49] WARNING[2184]: chan_sip.c:3622 retrans_pkt:
> Retransmission timeout reached on transmission
> 774d89fd4f10678829b20520787cd6f2@[::1]:0 for seqno 102 (Critical
> Request) -- See
> https://wiki.asterisk.org/wiki/display/AST/SIP+Retransmissions
> Packet timed out after 12160ms with no response
>
> I'm really sorry if this is not a bug, tunable somewhere. Please guide me.

That is most definitely a bug.

-- 
Kevin P. Fleming
Digium, Inc. | Director of Software Technologies
Jabber: kfleming at digium.com | SIP: kpfleming at digium.com | Skype: kpfleming
445 Jan Davis Drive NW - Huntsville, AL 35806 - USA
Check us out at www.digium.com & www.asterisk.org