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