[Home]

Summary:ASTERISK-17451: [patch] Odd Behavior when dialed sip channel doesn't exist
Reporter:Casey Morford (cmorford)Labels:
Date Opened:2011-02-21 10:56:53.000-0600Date Closed:2012-01-18 15:38:25.000-0600
Priority:MinorRegression?No
Status:Closed/CompleteComponents:Channels/chan_sip/General
Versions:1.8.2 Frequency of
Occurrence
Related
Issues:
Environment:Attachments:( 0) issue18860.patch
Description:I found this previous issue that seems to be similar to mine:

https://issues.asterisk.org/view.php?id=18708

but the reporter was referred to forum.  I believe the issue may be more than a support issue.

On asterisk 1.6.1.13, the Dial command simply fails on a non-configured extension and falls through the dialplan, terminating the call.

Using ChanIsAvail on the 1.6.1.13 system, I get an ${AVAILSTATUS} of 20, which is expected.

On 1.8.2.3 the call stays inside the Dial command with the output below and does not fail as expected.  The ${AVAILSTATUS} is 0 which doesn't appear to be appropriate.

If I stay on the phone, the __sip_xmit messages will repeat until I hang up.

It interesting to note that the bogus extension I dialed was 166 which shows up in the output below in the IP address.

****** ADDITIONAL INFORMATION ******

[Feb 21 08:57:07] WARNING[5710]: acl.c:698 ast_ouraddrfor: Cannot connect
[Feb 21 08:57:07] WARNING[5710]: chan_sip.c:3115 __sip_xmit: sip_xmit of 0x7f8208346110 (len 825) to 0.0.0.166:5060 returned -1: Invalid argument
[Feb 21 08:57:08] WARNING[4813]: chan_sip.c:3115 __sip_xmit: sip_xmit of 0x7f8208346110 (len 825) to 0.0.0.166:5060 returned -1: Invalid argument
[Feb 21 08:57:09] WARNING[4813]: chan_sip.c:3115 __sip_xmit: sip_xmit of 0x7f8208346110 (len 825) to 0.0.0.166:5060 returned -1: Invalid argument
[Feb 21 08:57:11] WARNING[4813]: chan_sip.c:3115 __sip_xmit: sip_xmit of 0x7f8208346110 (len 825) to 0.0.0.166:5060 returned -1: Invalid argument
[Feb 21 08:57:15] WARNING[4813]: chan_sip.c:3115 __sip_xmit: sip_xmit of 0x7f8208346110 (len 825) to 0.0.0.166:5060 returned -1: Invalid argument
[Feb 21 08:57:23] WARNING[4813]: chan_sip.c:3115 __sip_xmit: sip_xmit of 0x7f8208346110 (len 825) to 0.0.0.166:5060 returned -1: Invalid argument
[Feb 21 08:57:39] WARNING[4813]: chan_sip.c:3115 __sip_xmit: sip_xmit of 0x7f8208346110 (len 825) to 0.0.0.166:5060 returned -1: Invalid argument
[Feb 21 08:57:39] WARNING[4813]: chan_sip.c:3386 retrans_pkt: Retransmission timeout reached on transmission 3165a7b96089cbac4442070f70a64f75@172.16.20.1:5060 for seqno 102 (Critical Request) -- See doc/sip-retransmit.txt.
Packet timed out after 32000ms with no response
Comments:By: cmaj (cmaj) 2011-02-21 13:07:56.000-0600

I am seeing the exact same thing on 1.8.3-rc2, with ChanIsAvail() reporting AVAILSTATUS=0 for all channels, regardless of registration state. Dialed phantom phone exten shows up as IP address (in hex).
By: Elazar Broad (ebroad) 2011-02-21 14:52:21.000-0600

See the related bug. The fix that I am currently running is to comment out:

res = AST_DEVICE_UNKNOWN

in the else block. Let me know if that resolves the issue.


elazar
By: Casey Morford (cmorford) 2011-02-21 20:59:25.000-0600

That did not resolve my issue.  Still seeing the same behavior.
By: Stefan Schmidt (schmidts) 2011-04-06 03:19:13

Please try the uploaded patch if this resolves your issue.

thanks!

best regards

stefan
By: Terry Wilson (twilson) 2012-01-18 15:38:25.634-0600

This is already fixed in the 1.8 branch. Looks like it should go into a release 1.8.10.0. See revision 341314 in the 1.8 branch.