Hi guys, Did you get some explanation? I'm suffering the exact issue. It could be I need some additional dependencies than before?
Regards, Elder On Mon, Jul 25, 2011 at 7:59 AM, Soeren Malchow (MCon) < [email protected]> wrote: > Dear Shaun, > > First, thanks for you answer > > The installed dahdi driver is the latest one from the asterisk.orginstalled > via APT. > > There is no command pri show channels. Maybe the signaling is wrong ? but I > never had to use other signaling than pri_cpe on euroisdn. > > I can also install from source, I will investigate the signalling first, > will let you know what happens > > Regards > Soeren > > > > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Shaun Ruffell > Sent: Monday, July 25, 2011 6:15 PM > To: Asterisk Users Mailing List - Non-Commercial Discussion > Subject: Re: [asterisk-users] dahdi channels busy/congested > > On Mon, Jul 25, 2011 at 08:43:02AM +0000, Soeren Malchow (MCon) wrote: > > Dear all, > > > > i have a problem with a system running > > > > - Ubuntu 10.04 ( all updates done ) > > - ii asterisk 1:1.8.5.0-1digium1~lucid > Open Source Private Branch Exchange (PBX) > > - ii asterisk-dahdi 1:1.8.5.0-1digium1~lucid > DAHDI devices support for the Asterisk PBX > > > > I also use freepbx 2.9 for the configuration. > > > > Hardware is a Dell R410 and a Digium Wildcard > > > > wcte12xp+ d161:8000 Wildcard TE121 > > > > The status is as follows, > > - all drivers are loaded and the E1 card shows a GREEN LED and no > > alarms > > - asterisk is up > > - the provider is Bharti Airtel in India > > - the configuration was copied from my PBX in germany and slightly > > modified, that is a asterisk 1.4 though > > > > <--snip--> > > root@pbx01]: ~/backup/asterisk # dahdi_cfg -f -t -vv DAHDI Tools > > Version - 2.2.1 > > > > DAHDI Version: 2.2.1 > > This seems like an old version of the driver if the package is based on > 1.8.5... but I don't think that by itself is what is causing your problems. > > > Contents of dahdi-channels.conf > > > > group=0 > > context=from-pstn > > switchtype=euroisdn > > signalling=pri_cpe > > group=0 > > channel => 1-15,17-31 > > context=default > > group=63 > > > > And no matter whether i call in or out it does not work, from > > internally i get the following error ( parts of the phonenumbers are > > removed ) > > > > -- Executing [s@macro-dialout-trunk:20] Dial("SIP/1990-00000001", > > "DAHDI/g0/9560XXXXXX,300,") in new stack [Jul 25 14:10:31] WARNING[6121]: > chan_dahdi.c:5098 dahdi_confmute: DAHDI confmute(0) failed on channel 1: > Invalid argument > > -- Couldn't call DAHDI/g0/9560XXXXXX [Jul 25 14:10:31] > > WARNING[6121]: chan_dahdi.c:5098 dahdi_confmute: DAHDI confmute(0) > > failed on channel 1: Invalid argument [Jul 25 14:10:31] WARNING[6121]: > > chan_dahdi.c:5041 restore_gains: Unable to restore gains: Invalid > argument [Jul 25 14:10:31] WARNING[6121]: chan_dahdi.c:4724 reset_conf: > Failed to reset conferencing on channel 1: Invalid argument > > -- Hungup 'DAHDI/1-1' > > == Everyone is busy/congested at this time (0:0/0/0) > > -- Executing [s@macro-dialout-trunk:21] NoOp("SIP/1990-00000001", > "Dial failed for some reason with DIALSTATUS = CHANUNAVAIL and HANGUPCAUSE = > 0") in new stack > > -- Executing [s@macro-dialout-trunk:22] Goto("SIP/1990-00000001", > "s-CHANUNAVAIL,1") in new stack > > -- Goto (macro-dialout-trunk,s-CHANUNAVAIL,1) > > -- Executing [s-CHANUNAVAIL@macro-dialout-trunk:1] > Set("SIP/1990-00000001", "RC=0") in new stack > > -- Executing [s-CHANUNAVAIL@macro-dialout-trunk:2] > Goto("SIP/1990-00000001", "0,1") in new stack > > -- Goto (macro-dialout-trunk,0,1) > > -- Executing [0@macro-dialout-trunk:1] Goto("SIP/1990-00000001", > "continue,1") in new stack > > -- Goto (macro-dialout-trunk,continue,1) > > -- Executing [continue@macro-dialout-trunk:1] > GotoIf("SIP/1990-00000001", "1?noreport") in new stack > > -- Goto (macro-dialout-trunk,continue,3) > > -- Executing [continue@macro-dialout-trunk:3] > > NoOp("SIP/1990-00000001", "TRUNK Dial failed due to CHANUNAVAIL > > HANGUPCAUSE: 0 - failing through to other trunks") in new stack > > The invalid argument results from the call to confmute *appear* to me like > the channel was never set into AUDIOMODE, which from a quick scan of code > would only be the case if PRI support was not enabled in chan_dahdi, and > then that would have resulted in an error when setting the signalling to > pri_cpe. So I'm not quite sure. My best guess is that there is some issue > with how the package was created (especially given the old version of DAHDI > reported with then 1.8 branch of Asterisk). > > Is there any DAHDI related output in 'dmesg'? What is the output of "pri > show channels" on the asterisk command line? Are you able to install from > source? > > -- > Shaun Ruffell > Digium, Inc. | Linux Kernel Developer > 445 Jan Davis Drive NW - Huntsville, AL 35806 - USA Check us out at: > www.digium.com & www.asterisk.org > > -- > _____________________________________________________________________ > -- Bandwidth and Colocation Provided by http://www.api-digital.com -- New > to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > 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 -- > New to Asterisk? Join us for a live introductory webinar every Thurs: > http://www.asterisk.org/hello > > 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 -- New to Asterisk? Join us for a live introductory webinar every Thurs: http://www.asterisk.org/hello asterisk-users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
