[Home]

Summary:ASTERISK-13974: Cannot make outbound call through analog trunk
Reporter:colynd (colynd)Labels:
Date Opened:2009-04-17 02:03:09Date Closed:2011-06-07 14:00:30
Priority:MajorRegression?No
Status:Closed/CompleteComponents:Channels/chan_dahdi
Versions:Frequency of
Occurrence
Related
Issues:
Environment:Attachments:
Description:Cannot make outbound calls. inbound works fine. Also same outbound rules work with Asterisk 1.4.x and zaptel(using AsteriskNow 1.0.2).

Asterisk version is actually 1.6.0.9

DAHDI Version: 2.1.0.4 Echo Canceller:

This is what I get in the log when I try to dial out:

[Apr 17 08:48:47] WARNING[5632] chan_dahdi.c: Unable to determine channel for data trunk_1/0117831508
[Apr 17 08:48:47] WARNING[5632] app_dial.c: Unable to create channel of type 'DAHDI' (cause 0 - Unknown)
Comments:By: Leif Madsen (lmadsen) 2009-04-21 21:31:47

Please provide additional information on how to reproduce this issue. What hardware are you using? What is your configuration for DAHDI? What is the dialplan used to make the call?
By: ivan77 (ivan77) 2009-04-30 04:18:03

I have same problem. I am using openvox a800p - 4fxo's and i cannot make outbound calls when i configure Outbound Calling Rules using Asterisk GUI. It works fine if outbound route is configured manually (in extensions.conf). i am getting following errors:


   -- Executing [9995@DLPN_dp_first:1] Macro("SIP/1001-008646a0", "trunkdial-failover-0.3|DAHDI/trunk_1/9995||trunk_1|") in new stack
   -- Executing [s@macro-trunkdial-failover-0.3:1] GotoIf("SIP/1001-008646a0", "0?1-fmsetcid|1") in new stack
   -- Executing [s@macro-trunkdial-failover-0.3:2] GotoIf("SIP/1001-008646a0", "0?1-setgbobname|1") in new stack
   -- Executing [s@macro-trunkdial-failover-0.3:3] Set("SIP/1001-008646a0", "CALLERID(num)=1001") in new stack
   -- Executing [s@macro-trunkdial-failover-0.3:4] GotoIf("SIP/1001-008646a0", "0?1-dial|1") in new stack
   -- Executing [s@macro-trunkdial-failover-0.3:5] Set("SIP/1001-008646a0", "CALLERID(all)=") in new stack
   -- Executing [s@macro-trunkdial-failover-0.3:6] Goto("SIP/1001-008646a0", "1-dial|1") in new stack
   -- Goto (macro-trunkdial-failover-0.3,1-dial,1)
   -- Executing [1-dial@macro-trunkdial-failover-0.3:1] Dial("SIP/1001-008646a0", "DAHDI/trunk_1/9995") in new stack
[Apr 30 11:03:01] WARNING[7426]: chan_dahdi.c:8368 dahdi_request: Unable to determine channel for data trunk_1/9995
[Apr 30 11:03:01] WARNING[7426]: app_dial.c:1237 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown)
 == Everyone is busy/congested at this time (1:0/0/1)
   -- Executing [1-dial@macro-trunkdial-failover-0.3:2] GotoIf("SIP/1001-008646a0", "0 > 0 ?1-CHANUNAVAIL|1:1-out|1") in new stack
   -- Goto (macro-trunkdial-failover-0.3,1-out,1)
   -- Executing [1-out@macro-trunkdial-failover-0.3:1] Hangup("SIP/1001-008646a0", "") in new stack
 == Spawn extension (macro-trunkdial-failover-0.3, 1-out, 1) exited non-zero on 'SIP/1001-008646a0' in macro 'trunkdial-failover-0.3'
 == Spawn extension (DLPN_dp_first, 9995, 1) exited non-zero on 'SIP/1001-008646a0'
------------------------------------------------------------------------------------
i am using Asterisk 1.4.24.1


By: Leif Madsen (lmadsen) 2009-05-04 08:35:27

I'm closing this issue for now due to lack of a response from the original reporter. Additionally, for the 2nd reporter, use of OpenVox cards is going to make debugging this extremely difficult; if you can reproduce with a Digium card then please have a bug marshal on IRC (irc.freenode.net, channel #asterisk-bugs) reopen this issue.

Otherwise, I'd encourage you to move this to the asterisk-users mailing list. Thanks!
By: Leif Madsen (lmadsen) 2009-08-28 08:41:57

Reopening issue per CrawZ on IRC.

Hey, that rhymes, thank god I'm not a mime!
By: Tzafrir Cohen (tzafrir) 2009-09-01 13:21:04

Do you have KS or LS signalling?
By: Russell Bryant (russell) 2009-09-10 22:10:57

Given the lack of detail demonstrating otherwise, I'm assuming that this is most likely just a configuration issue.  Please pursue this through the various user support forums.  Thanks.