<div dir="ltr">Dear Sir,<br><br>My Asterisk server is sending periodically the below SIP packets<br><br>Retransmitting #4 (NAT) to <a href="http://68.62.168.138:5060">68.62.168.138:5060</a>:<br>OPTIONS <a href="http://sip:sarathb@68.62.168.138:5060">sip:sarathb@68.62.168.138:5060</a> SIP/2.0<br>
Via: SIP/2.0/UDP XX.XX.XX.XX:5060;branch=z9hG4bK37f337ed;rport<br>From: "asterisk" <sip:asterisk@XX.XX.XX.XX>;tag=as078bf319<br>To: <<a href="http://sip:sarathb@68.62.168.138:5060">sip:sarathb@68.62.168.138:5060</a>><br>
Contact: <sip:asterisk@XX.XX.XX.XX><br>Call-ID: 7c71f80736bb6506511056ce6c070a23@XX.XX.XX.XX<br>CSeq: 102 OPTIONS<br>User-Agent: Asterisk PBX<br>Max-Forwards: 70<br>Date: Tue, 02 Dec 2008 12:30:18 GMT<br>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY<br>
Supported: replaces<br>Content-Length: 0<br><br><br>---<br>Really destroying SIP dialog '7c71f80736bb6506511056ce6c070a23@XX.XX.XX.XX' Method: OPTIONS<br>[Dec 2 12:30:24] WARNING[6669]: rtp.c:891 ast_rtcp_read: RTCP Read too short<br>
Reliably Transmitting (NAT) to <a href="http://68.62.168.138:5060">68.62.168.138:5060</a>:<br>OPTIONS <a href="http://sip:sarathb@68.62.168.138:5060">sip:sarathb@68.62.168.138:5060</a> SIP/2.0<br>Via: SIP/2.0/UDP XX.XX.XX.XX:5060;branch=z9hG4bK34e06ad8;rport<br>
From: "asterisk" <sip:asterisk@XX.XX.XX.XX>;tag=as141b747c<br>To: <<a href="http://sip:sarathb@68.62.168.138:5060">sip:sarathb@68.62.168.138:5060</a>><br>Contact: <sip:asterisk@XX.XX.XX.XX><br>
Call-ID: 3d25b62565ea5f127a7769045f600a53@XX.XX.XX.XX<br>CSeq: 102 OPTIONS<br>User-Agent: Asterisk PBX<br>Max-Forwards: 70<br>Date: Tue, 02 Dec 2008 12:30:32 GMT<br>Allow: INVITE, ACK, CANCEL, OPTIONS, BYE, REFER, SUBSCRIBE, NOTIFY<br>
Supported: replaces<br>Content-Length: 0<br><br>I checked my system and found out that there is an extension (Type=friend) where ipaddr=68.62.168.138...I removed the ipaddr from the definition of the extension, reloaded the Asterisk but it still sending SIP packets...<br>
<br>Please let me know how to force my asterisk from sending such packets and if someone has an idea about similar problem<br><br>Regards<br></div>