<div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote">On Tue, Sep 3, 2013 at 4:25 AM, S, Kantharuban IN MAA SL <span dir="ltr"><<a href="mailto:kantharuban.s@siemens.com" target="_blank">kantharuban.s@siemens.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div lang="EN-US" link="blue" vlink="purple"><div><p class="">
Hi List,<u></u><u></u></p><p class=""> The below error caused the Asterisk to crash, if anyone have idea on this please reply,(Asterisk version :1.8.9)<u></u><u></u></p><p class=""><u></u> <u></u></p><p class="">
[Sep 2 15:59:53] WARNING[24418] channel.c: Codec mismatch on channel SIP/18202-0002d011 setting write format to ilbc from ulaw native formats 0x4 (ulaw)<u></u><u></u></p><p class="">[Sep 2 15:59:53] WARNING[24418] channel.c: Unable to find a codec translation path from 0x4 (ulaw) to 0x400 (ilbc)<u></u><u></u></p>
<p class="">[Sep 2 15:59:53] WARNING[24418] chan_sip.c: Asked to transmit frame type ilbc, while native formats is 0x4 (ulaw) read/write = 0x4 (ulaw)/0x4 (ulaw)<u></u><u></u></p><p class="">[Sep 2 15:59:53] WARNING[24418] channel.c: Codec mismatch on channel SIP/18202-0002d011 setting write format to ilbc from ulaw native formats 0x4 (ulaw)<u></u><u></u></p>
<p class="">[Sep 2 15:59:53] WARNING[24418] channel.c: Unable to find a codec translation path from 0x4 (ulaw) to 0x400 (ilbc)<u></u><u></u></p><p class="">[Sep 2 15:59:53] WARNING[24418] chan_sip.c: Asked to transmit frame type ilbc, while native formats is 0x4 (ulaw) read/write = 0x4 (ulaw)/0x4 (ulaw)<u></u><u></u></p>
<p class="">[Sep 2 15:59:53] WARNING[24418] channel.c: Codec mismatch on channel SIP/18202-0002d011 setting write format to ilbc from ulaw native formats 0x4 (ulaw)<u></u><u></u></p><p class="">[Sep 2 15:59:53] WARNING[24418] channel.c: Unable to find a codec translation path from 0x4 (ulaw) to 0x400 (ilbc)<u></u><u></u></p>
<p class="">[Sep 2 15:59:53] WARNING[24418] chan_sip.c: Asked to transmit frame type ilbc, while native formats is 0x4 (ulaw) read/write = 0x4 (ulaw)/0x4 (ulaw)<u></u><u></u></p><p class="">[Sep 2 15:59:53] WARNING[24418] channel.c: No path to translate from SIP/18252-0002d010 to SIP/18203-0002d01e<u></u><u></u></p>
<p class="">[Sep 2 15:59:53] WARNING[24418] channel.c: Can't make SIP/18252-0002d010 and SIP/18203-0002d01e compatible<u></u><u></u></p><p class="">[Sep 2 15:59:53] WARNING[24418] features.c: Bridge failed on channels SIP/18252-0002d010 and SIP/18203-0002d01e<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] chan_dahdi.c: Ignoring any changes to 'userbase' (on reload) at line 23.<u></u><u></u></p><p class="">[Sep 2 16:00:00] WARNING[4970] chan_dahdi.c: Ignoring any changes to 'vmsecret' (on reload) at line 31.<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] chan_dahdi.c: Ignoring any changes to 'hassip' (on reload) at line 35.<u></u><u></u></p><p class="">[Sep 2 16:00:00] WARNING[4970] chan_dahdi.c: Ignoring any changes to 'hasiax' (on reload) at line 39.<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] chan_dahdi.c: Ignoring any changes to 'hasmanager' (on reload) at line 47.<u></u><u></u></p><p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: No valid transports available, falling back to 'udp'.<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! PLEASE NOTE: Setting 'nat' for a peer/user that differs from the global setting can make<u></u><u></u></p><p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,<u></u><u></u></p><p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! use the global 'nat' setting and do not set 'nat' per peer/user.<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! (config category='analog-fxs-gateway' global force_rport='Yes' peer/user force_rport='No')<u></u><u></u></p><p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! PLEASE NOTE: Setting 'nat' for a peer/user that differs from the global setting can make<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users<u></u><u></u></p><p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! use the global 'nat' setting and do not set 'nat' per peer/user.<u></u><u></u></p><p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! (config category='S0-gateway' global force_rport='Yes' peer/user force_rport='No')<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! PLEASE NOTE: Setting 'nat' for a peer/user that differs from the global setting can make<u></u><u></u></p><p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! the name of that peer/user discoverable by an attacker. Replies for non-existent peers/users<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! will be sent to a different port than replies for an existing peer/user. If at all possible,<u></u><u></u></p><p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! use the global 'nat' setting and do not set 'nat' per peer/user.<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] chan_sip.c: !!! (config category='S2M-gateway' global force_rport='Yes' peer/user force_rport='No')<u></u><u></u></p><p class="">[Sep 2 16:00:00] WARNING[4970] pbx.c: Extension '_0.', priority 42 in 'outgoing', label 'UP' already in use at priority 33<u></u><u></u></p>
<p class="">[Sep 2 16:00:00] WARNING[4970] pbx.c: Extension '_0.', priority 45 in 'outgoing', label 'DOWN' already in use at priority 36<u></u><u></u></p><p class="">[Sep 2 16:00:01] WARNING[5180] acl.c: Cannot connect<u></u><u></u></p>
<p class=""><u></u> <u></u></p><p class=""><br></p></div></div></blockquote><div style>It looks like you performed a 'sip reload' during an active call and Asterisk crashed. There have been numerous bug fixes to the 1.8 and later branches to address this kind of issue - since you're running a version of Asterisk 1.8 that is 20 months old, there is a good likelihood that any issue you are facing has already been fixed. Upgrading to a more recent version of 1.8 may be your best course of action.</div>
<div style><br></div><div style>In any case, a log file only showing WARNING messages is often not sufficient for debug a problem, much less a crash. There are explicit instructions on the Asterisk wiki [1] on how to obtain the correct information when Asterisk crashes. If this happens again, please obtain a backtrace using the instructions and file an issue on the Asterisk issue tracker [2].</div>
<div style><br></div><div style>[1] <a href="https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace">https://wiki.asterisk.org/wiki/display/AST/Getting+a+Backtrace</a></div><div style><br></div><div style>[2] <a href="https://issues.asterisk.org/jira">https://issues.asterisk.org/jira</a></div>
<div style><br></div><div style>Thanks</div><div style><br></div><div style>Matt</div></div><div><br></div>-- <br><div dir="ltr"><div>Matthew Jordan<br></div><div>Digium, Inc. | Engineering Manager</div><div>445 Jan Davis Drive NW - Huntsville, AL 35806 - USA</div>
<div>Check us out at: <a href="http://digium.com" target="_blank">http://digium.com</a> & <a href="http://asterisk.org" target="_blank">http://asterisk.org</a></div></div>
</div></div>