[asterisk-users] Source of SIP "Remote host can't match request NOTIFY"

[Olivier]

I've been lucky enough to catch a NOTIFY/SUBSCRIBE sequence which ended with
such 481 reply. (I don't have the slightest why NOTIFY is replied with 481
error, but that's another topic).

Anyway, my question remains :
Do you think message "Remote host can't match request NOTIFY to call" should
be improved to "Remote host 192.168.41.231 can't match request NOTIFY ..."
as, even with verbosity of 10, original message won't give any clue to find
the responding host ?


Regards



2008/9/29 Olivier <oza-4h07 at myamail.com>

> Hi,
>
> I've got a lot of Remote host can't match request NOTIFY.
> I've read
> http://lists.digium.com/pipermail/asterisk-users/2008-May/210709.html .
>
>
>
> Recommendation is "
>
> enable SIP debug to see what packets are causing
> this, and if it's voicemail notifications, turn them off in sip.conf
>
>
> How would you proceed to get those debug ?
>
> The exact message is :
> WARNING[2990]: chan_sip.c:12900 handle_response: Remote host can't match request NOTIFY to call '7fba0a0c3b6a3c4b3078da9d4b4e505d at 192.168.52.31'. Giving up.
>
> As this 192.168.52.31 adresse is my Asterisk server address, I don't have a clue to focus debugging on the device that replies 481 to Asterisk.
> Unfortunately, I've got several dozens of devices and all with QUALIFY=yes.
>
> So in 60 seconds, I get hundred of SIP debug lines.
>
> Is there a smart way to handle this ?
> Something like "SIP DEBUG 481" ?
>
> Anyway, do you think it could make sense to ask (or develop) a more explicit WARNING message such as
>
> "Remote host 192.168.52.123 can't match ..." ?
> Cheers
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20080929/e7fafd61/attachment.htm