Re: [asterisk-users] Unable to create channel of type 'DAHDI'(cause 0- Unknown)
On Fri, Jan 29, 2010 at 05:48:53PM -0500, sean darcy wrote: listu...@spamomania.co.uk wrote: On Thu, 2010-01-28 at 23:11 -0600, Karl Fife wrote: Appears completely resolved! No more home-spun patches! Thanks! -K It's *not* fixed here: DAHDI Version: 2.2.1 Echo Canceller: MG2 But as is depressingly the 'norm' for Asterisk it comes back to bitching about hardware 'buy an expensive Digium echo machine instead of a cheap one' rather than the fact that the core of Asterisk is rotten, buggy and the fix usually comes in the form of a developer arguing that it's somebody else's issue. Really - if Asterisk is 'The future of telephony' I can only assume that statement comes from the late 1800's. If you like echo, flaky connections, intermittent service and partially working DTMF coupled with a hefty hardware price tag then hey ho - Asterisk is your man Nice try, be great when it's finished. Sigh. OK you don't like asterisk - sorry. Obviously some other software works better for you. I'm glad. For at least some of us, asterisk works extremely well in demanding environments. But not perfectly. So the collegial help from the mailing list and bug spotting is quite important. Sorry you don't want to participate. FWIW, I also consider Asterisk's behaviour here buggy. http://svn.debian.org/viewsvn/pkg-voip/asterisk/trunk/debian/patches/dahdi-fxsks-hookstate?view=markup -- Tzafrir Cohen icq#16849755 jabber:tzafrir.co...@xorcom.com +972-50-7952406 mailto:tzafrir.co...@xorcom.com http://www.xorcom.com iax:gu...@local.xorcom.com/tzafrir -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Unable to create channel of type 'DAHDI'(cause 0- Unknown)
listu...@spamomania.co.uk wrote: On Thu, 2010-01-28 at 23:11 -0600, Karl Fife wrote: Appears completely resolved! No more home-spun patches! Thanks! -K It's *not* fixed here: DAHDI Version: 2.2.1 Echo Canceller: MG2 But as is depressingly the 'norm' for Asterisk it comes back to bitching about hardware 'buy an expensive Digium echo machine instead of a cheap one' rather than the fact that the core of Asterisk is rotten, buggy and the fix usually comes in the form of a developer arguing that it's somebody else's issue. Really - if Asterisk is 'The future of telephony' I can only assume that statement comes from the late 1800's. If you like echo, flaky connections, intermittent service and partially working DTMF coupled with a hefty hardware price tag then hey ho - Asterisk is your man Nice try, be great when it's finished. Sigh. OK you don't like asterisk - sorry. Obviously some other software works better for you. I'm glad. For at least some of us, asterisk works extremely well in demanding environments. But not perfectly. So the collegial help from the mailing list and bug spotting is quite important. Sorry you don't want to participate. sean -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Unable to create channel of type 'DAHDI'(cause 0- Unknown)
On 30/01/10 11:48 AM, sean darcy wrote: Sigh. OK you don't like asterisk - sorry. Obviously some other software works better for you. I'm glad. Don't worry, he/she's trolling, second post like that for the day :) Obviously has an issue with something, but rather than try and get it sorted he/she'd rather just bitch. -- Cheers, Matt Riddell Managing Director ___ http://www.venturevoip.com/news.php (Daily Asterisk News) http://www.venturevoip.com/exchange.php (Full ITSP Solution) http://www.venturevoip.com/st.php (SmoothTorque Predictive Dialer) -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Unable to create channel of type 'DAHDI' (cause 0 - Unknown)
Hi, I have a tdm22b (2 fxs / 2 fxo) When Asterisk is just started, outbound calls routing to fxo port, do not working with error: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) Inbound calls to fxo port work fine. After first inbound call, the outbound calls starts working. CentOS 5.4 asterisk 1.6.0.21-1 dahdi 2.2.1.-1 Can anybody help me to identify what is the possible cause of problem? Thanks, Walter. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Unable to create channel of type 'DAHDI' (cause 0- Unknown)
I have had the exact same problem for over a year on my server sporting the TDM800 but NOT on my server with the TE212P. Both servers run the same version of Linux, Asterisk and DHADI. The problem has remained consistent through all versions of DAHDI 2.0.x through 2.2.0.2, and every version of Asterisk which I have I've tried which includes various iterations of 1.6.0, 1.6.1, and 1.6.2. Currently 1.2.6.1. Surprisingly I also observe that I can even compile install NEW versions of Asterisk and/or DAHDI, and NOT observe the bug provided that I do NOT bounce the server. A developer (not an asterisk developer) named Jim Duda posted this issue to the list back in October of 08. (Asterisk 1.6.0-beta9 DAHDI 2.0.x originally for him). After what he described as considerable effort he found that by changing one line in chan_dahdi.c the issue appeared to be resolved (below). His simple patch (below) has works (for me too) as a stop-gap. I posted this the DEV list back January of 09, and the issue was reopened and then closed as 'fixed' . It would appear the issue needs to be re-reopened, as it's now appearing less specific to my hardware or configuration. https://issues.asterisk.org/view.php?id=13786 Duplicate issue to 13927 If I do not patch chan_dahdi (below), this is what I (still) observe: ONLY after a system reboot, any attempt(s) to dial from a device attached to an FXS port on my TDM800P, result in the following error : WARNING[2975]: app_dial.c:1502 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) == Everyone is busy/congested at this time (1:0/0/1) BUT after the first INBOUND call to any FXO port on the device, the FXS port works normally until the next reboot. (Asterisk 1.6.2.1 DAHDI 2.2.0.2 ( earlier ) Centos 2.6.18-164.11.1.el5 #1 SMP Wed Jan 20 07:39:04 EST 2010 i686 i686 i386 GNU/Linux Does anyone else observe this? Could it be specific to certain (mis)configurations? It's possible that others have the issue but do not know it. With any inbound call volume it may be nearly transparent :-) -Karl JIM's ONE-LINE FIX On line 8730 (I think it's still on this line) of chan_dahdi.c replace a return 0 with return 1. if (par.rxisoffhook) return 1; else - return 0; + return 1; - Original Message - From: Walter Arguello walter_argue...@yahoo.com To: asterisk-users@lists.digium.com Sent: Thursday, January 28, 2010 6:15 PM Subject: [asterisk-users] Unable to create channel of type 'DAHDI' (cause 0- Unknown) Hi, I have a tdm22b (2 fxs / 2 fxo) When Asterisk is just started, outbound calls routing to fxo port, do not working with error: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) Inbound calls to fxo port work fine. After first inbound call, the outbound calls starts working. CentOS 5.4 asterisk 1.6.0.21-1 dahdi 2.2.1.-1 Can anybody help me to identify what is the possible cause of problem? Thanks, Walter. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Unable to create channel of type 'DAHDI' (cause 0- Unknown)
Interesting. I had the same problem last Sept with a TDM800, DAHDI 2.2.0.2. Shaun Ruffel of Digium pointed me to https://issues.asterisk.org/file_download.php?file_id=22725type=bug which fixed it for me. This fix is already in 2.2.1. -- Barry On Thu, Jan 28, 2010 at 07:30:57PM -0600, Karl Fife wrote: I have had the exact same problem for over a year on my server sporting the TDM800 but NOT on my server with the TE212P. Both servers run the same version of Linux, Asterisk and DHADI. The problem has remained consistent through all versions of DAHDI 2.0.x through 2.2.0.2, and every version of Asterisk which I have I've tried which includes various iterations of 1.6.0, 1.6.1, and 1.6.2. Currently 1.2.6.1. Surprisingly I also observe that I can even compile install NEW versions of Asterisk and/or DAHDI, and NOT observe the bug provided that I do NOT bounce the server. A developer (not an asterisk developer) named Jim Duda posted this issue to the list back in October of 08. (Asterisk 1.6.0-beta9 DAHDI 2.0.x originally for him). After what he described as considerable effort he found that by changing one line in chan_dahdi.c the issue appeared to be resolved (below). His simple patch (below) has works (for me too) as a stop-gap. I posted this the DEV list back January of 09, and the issue was reopened and then closed as 'fixed' . It would appear the issue needs to be re-reopened, as it's now appearing less specific to my hardware or configuration. https://issues.asterisk.org/view.php?id=13786 Duplicate issue to 13927 If I do not patch chan_dahdi (below), this is what I (still) observe: ONLY after a system reboot, any attempt(s) to dial from a device attached to an FXS port on my TDM800P, result in the following error : WARNING[2975]: app_dial.c:1502 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) == Everyone is busy/congested at this time (1:0/0/1) BUT after the first INBOUND call to any FXO port on the device, the FXS port works normally until the next reboot. (Asterisk 1.6.2.1 DAHDI 2.2.0.2 ( earlier ) Centos 2.6.18-164.11.1.el5 #1 SMP Wed Jan 20 07:39:04 EST 2010 i686 i686 i386 GNU/Linux Does anyone else observe this? Could it be specific to certain (mis)configurations? It's possible that others have the issue but do not know it. With any inbound call volume it may be nearly transparent :-) -Karl JIM's ONE-LINE FIX On line 8730 (I think it's still on this line) of chan_dahdi.c replace a return 0 with return 1. if (par.rxisoffhook) return 1; else - return 0; + return 1; - Original Message - From: Walter Arguello walter_argue...@yahoo.com To: asterisk-users@lists.digium.com Sent: Thursday, January 28, 2010 6:15 PM Subject: [asterisk-users] Unable to create channel of type 'DAHDI' (cause 0- Unknown) Hi, I have a tdm22b (2 fxs / 2 fxo) When Asterisk is just started, outbound calls routing to fxo port, do not working with error: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) Inbound calls to fxo port work fine. After first inbound call, the outbound calls starts working. CentOS 5.4 asterisk 1.6.0.21-1 dahdi 2.2.1.-1 Can anybody help me to identify what is the possible cause of problem? Thanks, Walter. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Unable to create channel of type 'DAHDI'(cause 0- Unknown)
Appears completely resolved! No more home-spun patches! Thanks! -K - Original Message - From: Barry Miller asterisk-us...@notanet.net To: Asterisk Users Mailing List - Non-Commercial Discussion asterisk-users@lists.digium.com Sent: Thursday, January 28, 2010 10:40 PM Subject: Re: [asterisk-users] Unable to create channel of type 'DAHDI'(cause 0- Unknown) Interesting. I had the same problem last Sept with a TDM800, DAHDI 2.2.0.2. Shaun Ruffel of Digium pointed me to https://issues.asterisk.org/file_download.php?file_id=22725type=bug which fixed it for me. This fix is already in 2.2.1. -- Barry On Thu, Jan 28, 2010 at 07:30:57PM -0600, Karl Fife wrote: I have had the exact same problem for over a year on my server sporting the TDM800 but NOT on my server with the TE212P. Both servers run the same version of Linux, Asterisk and DHADI. The problem has remained consistent through all versions of DAHDI 2.0.x through 2.2.0.2, and every version of Asterisk which I have I've tried which includes various iterations of 1.6.0, 1.6.1, and 1.6.2. Currently 1.2.6.1. Surprisingly I also observe that I can even compile install NEW versions of Asterisk and/or DAHDI, and NOT observe the bug provided that I do NOT bounce the server. A developer (not an asterisk developer) named Jim Duda posted this issue to the list back in October of 08. (Asterisk 1.6.0-beta9 DAHDI 2.0.x originally for him). After what he described as considerable effort he found that by changing one line in chan_dahdi.c the issue appeared to be resolved (below). His simple patch (below) has works (for me too) as a stop-gap. I posted this the DEV list back January of 09, and the issue was reopened and then closed as 'fixed' . It would appear the issue needs to be re-reopened, as it's now appearing less specific to my hardware or configuration. https://issues.asterisk.org/view.php?id=13786 Duplicate issue to 13927 If I do not patch chan_dahdi (below), this is what I (still) observe: ONLY after a system reboot, any attempt(s) to dial from a device attached to an FXS port on my TDM800P, result in the following error : WARNING[2975]: app_dial.c:1502 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) == Everyone is busy/congested at this time (1:0/0/1) BUT after the first INBOUND call to any FXO port on the device, the FXS port works normally until the next reboot. (Asterisk 1.6.2.1 DAHDI 2.2.0.2 ( earlier ) Centos 2.6.18-164.11.1.el5 #1 SMP Wed Jan 20 07:39:04 EST 2010 i686 i686 i386 GNU/Linux Does anyone else observe this? Could it be specific to certain (mis)configurations? It's possible that others have the issue but do not know it. With any inbound call volume it may be nearly transparent :-) -Karl JIM's ONE-LINE FIX On line 8730 (I think it's still on this line) of chan_dahdi.c replace a return 0 with return 1. if (par.rxisoffhook) return 1; else - return 0; + return 1; - Original Message - From: Walter Arguello walter_argue...@yahoo.com To: asterisk-users@lists.digium.com Sent: Thursday, January 28, 2010 6:15 PM Subject: [asterisk-users] Unable to create channel of type 'DAHDI' (cause 0- Unknown) Hi, I have a tdm22b (2 fxs / 2 fxo) When Asterisk is just started, outbound calls routing to fxo port, do not working with error: Unable to create channel of type 'DAHDI' (cause 0 - Unknown) Inbound calls to fxo port work fine. After first inbound call, the outbound calls starts working. CentOS 5.4 asterisk 1.6.0.21-1 dahdi 2.2.1.-1 Can anybody help me to identify what is the possible cause of problem? Thanks, Walter. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Unable to create channel of type 'DAHDI'(cause 0- Unknown)
On Thu, 2010-01-28 at 23:11 -0600, Karl Fife wrote: Appears completely resolved! No more home-spun patches! Thanks! -K It's *not* fixed here: DAHDI Version: 2.2.1 Echo Canceller: MG2 But as is depressingly the 'norm' for Asterisk it comes back to bitching about hardware 'buy an expensive Digium echo machine instead of a cheap one' rather than the fact that the core of Asterisk is rotten, buggy and the fix usually comes in the form of a developer arguing that it's somebody else's issue. Really - if Asterisk is 'The future of telephony' I can only assume that statement comes from the late 1800's. If you like echo, flaky connections, intermittent service and partially working DTMF coupled with a hefty hardware price tag then hey ho - Asterisk is your man Nice try, be great when it's finished. -- _ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Unable to create channel of type 'DAHDI' (cause 0 - Unknown)
The reason for this is that 1.6.0 does not support dahdi. It was a mistake when it was listed as an included feature. The documentation for it has been removed in 1.6.0.1. If you need dahdi you need to go to 1.6.1. This is documented in this changelog: http://downloads.digium.com/pub/asterisk/ChangeLog-1.6.0.1 Brendan Martens On Oct 10, 2008, at 8:33 AM, Jim Duda wrote: Does anyone know what this error message means? Unable to create channel of type 'DAHDI' (cause 0 - Unknown) I've upgraded to 1.6.0 with dahdi 2.0. For some reason my outbound dahdi calls are not going through. At some point, it starts to work, but I don't know what the trigger is. Out of the blue, outbound calls start to work. I had been using asterisk-1.6-beta9 with zaptel without any problems. Thanks, Jim -- Executing [EMAIL PROTECTED]:1] Macro(SIP/111-b4e05610, dialout-dahdi,18005551212) in new stack -- Executing [EMAIL PROTECTED]:3] Set(SIP/111-b4e05610, DYNAMIC_FEATURES=outflash) in new stack -- Executing [EMAIL PROTECTED]:4] Dial(SIP/111-b4e05610, DAHDI/4/18005551212,40,tr) in new stack [Oct 10 08:29:10] WARNING[4365]: app_dial.c:1450 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 [EMAIL PROTECTED]:5] NoOp(SIP/111-b4e05610, Dial Status:CHANUNAVAIL) in new stack -- Executing [EMAIL PROTECTED]:6] Goto(SIP/111-b4e05610, s-CHANUNAVAIL,1) in new stack -- Goto (macro-dialout-dahdi,s-CHANUNAVAIL,1) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Unable to create channel of type 'DAHDI' (cause 0 - Unknown)
Brendan Martens wrote: The reason for this is that 1.6.0 does not support dahdi. It was a mistake when it was listed as an included feature. The documentation for it has been removed in 1.6.0.1. If you need dahdi you need to go to 1.6.1. That is incorrect. There was one small feature (the 'dahdichan' configuration option, used when creating a new-style chan_dahdi.conf instead of the format used by zapata.conf) that was mistakenly included in the sample config file in 1.6.0, which has how been removed in 1.6.0.1. The dahdichan config option is supported in 1.6.1. 1.6.0 fully supports DAHDI, and does not support Zaptel at all. -- Kevin P. Fleming Director of Software Technologies Digium, Inc. - The Genuine Asterisk Experience (TM) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Unable to create channel of type 'DAHDI' (cause 0 - Unknown)
I see, Thank you for the clarification. Brendan Martens On Oct 10, 2008, at 9:31 AM, Kevin P. Fleming wrote: Brendan Martens wrote: The reason for this is that 1.6.0 does not support dahdi. It was a mistake when it was listed as an included feature. The documentation for it has been removed in 1.6.0.1. If you need dahdi you need to go to 1.6.1. That is incorrect. There was one small feature (the 'dahdichan' configuration option, used when creating a new-style chan_dahdi.conf instead of the format used by zapata.conf) that was mistakenly included in the sample config file in 1.6.0, which has how been removed in 1.6.0.1. The dahdichan config option is supported in 1.6.1. 1.6.0 fully supports DAHDI, and does not support Zaptel at all. -- Kevin P. Fleming Director of Software Technologies Digium, Inc. - The Genuine Asterisk Experience (TM) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Re: [asterisk-users] Unable to create channel of type 'DAHDI' (cause 0 - Unknown)
Inbound calls on DAHDI work fine. At some point, outbound starts working. I just cannot figure out what the trigger is. At first, I thought the trigger was receiving at least one inbound call. But that isn't always true. Once it starts working, it seems to continue until a restart. Everything looks normal. I'm having trouble with outbound calls on channel 4 (attached to the PSTN). asterisk*CLI dahdi show channels Chan Extension Context Language MOH Interpret BlockedState pseudointernal default In Service 1internal default In Service 4incoming default In Service asterisk*CLI dahdi show channel 4 Channel: 4LI File Descriptor: 21 Span: 1 Extension: Dialing: no Context: incoming Caller ID: Calling TON: 0 Caller ID name: Mailbox: 100 Destroy: 0 InAlarm: 0 Signalling Type: FXS Kewlstart Radio: 0 Owner: None Real: None Callwait: None Threeway: None Confno: -1 Propagated Conference: -1 Real in conference: 0 DSP: no Busy Detection: no TDD: no Relax DTMF: no Dialing/CallwaitCAS: 0/0 Default law: ulaw Fax Handled: no Pulse phone: no DND: no Echo Cancellation: 128 taps (unless TDM bridged) currently OFF Actual Confinfo: Num/0, Mode/0x Actual Confmute: No Hookstate (FXS only): Onhook Jim Kevin P. Fleming wrote: Brendan Martens wrote: The reason for this is that 1.6.0 does not support dahdi. It was a mistake when it was listed as an included feature. The documentation for it has been removed in 1.6.0.1. If you need dahdi you need to go to 1.6.1. That is incorrect. There was one small feature (the 'dahdichan' configuration option, used when creating a new-style chan_dahdi.conf instead of the format used by zapata.conf) that was mistakenly included in the sample config file in 1.6.0, which has how been removed in 1.6.0.1. The dahdichan config option is supported in 1.6.1. 1.6.0 fully supports DAHDI, and does not support Zaptel at all. ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
[asterisk-users] Unable to create channel of type 'DAHDI' (cause 0 - Unknown)
Does anyone know what this error message means? Unable to create channel of type 'DAHDI' (cause 0 - Unknown) I've upgraded to 1.6.0 with dahdi 2.0. For some reason my outbound dahdi calls are not going through. At some point, it starts to work, but I don't know what the trigger is. Out of the blue, outbound calls start to work. I had been using asterisk-1.6-beta9 with zaptel without any problems. Thanks, Jim -- Executing [EMAIL PROTECTED]:1] Macro(SIP/111-b4e05610, dialout-dahdi,18005551212) in new stack -- Executing [EMAIL PROTECTED]:3] Set(SIP/111-b4e05610, DYNAMIC_FEATURES=outflash) in new stack -- Executing [EMAIL PROTECTED]:4] Dial(SIP/111-b4e05610, DAHDI/4/18005551212,40,tr) in new stack [Oct 10 08:29:10] WARNING[4365]: app_dial.c:1450 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 [EMAIL PROTECTED]:5] NoOp(SIP/111-b4e05610, Dial Status:CHANUNAVAIL) in new stack -- Executing [EMAIL PROTECTED]:6] Goto(SIP/111-b4e05610, s-CHANUNAVAIL,1) in new stack -- Goto (macro-dialout-dahdi,s-CHANUNAVAIL,1) ___ -- Bandwidth and Colocation Provided by http://www.api-digital.com -- asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
