Marcus.Rothe@bertelsmann.de
2006-Apr-11 07:54 UTC
AW: [Asterisk-Users] Dial out on Zap: Can't fix up channel from 31 to 30 because 30 is already in use??
I'm not sure if it's the same problem but your error message likely the same. after i additing pridialplan=local in the zapata.conf i'm able to make outboundcalls (located in germany) marcus -----Urspr?ngliche Nachricht----- Von: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] Gesendet: Dienstag, 11. April 2006 16:33 An: asterisk-users@lists.digium.com Betreff: [Asterisk-Users] Dial out on Zap: Can't fix up channel from 31 to 30 because 30 is already in use?? Hi, I still cant dial out on Zap and I really have no clue why. I'm using Asterisk Asterisk 1.2.6 and Zaptel 1.2.5 with Digium card 4 ports, 31 channels each and able to receive incoming calls and fax perfectly. I've done this in my dial plan. exten => 111,1,Answer() exten => 111,n,Ringing() exten => 111,n,Wait(2) exten => 111,n,AbsoluteTimeout(30) exten => 111,n,Dial(Zap/G1/002212601574) exten => 111,n,NoOp(${DIALSTATUS}) exten => 111,n,Busy() exten => 111,n,Hangup() My zapata.conf is like this [channels] context=from-pstn group=0 switchtype=euroisdn overlapdial=yes faxdetect=no echocancel=yes echocancelwhenbridged=yes ; PRI port 1 (E1) ; context=1 group=1 signalling=pri_cpe channel=>1-15,17-31 And I've got this on my CLI: -- Accepting overlap call from '2212601571' to '111' on channel 0/31, span 1 -- Starting simple switch on 'Zap/31-1' -- Executing Answer("Zap/31-1", "") in new stack -- Executing Ringing("Zap/31-1", "") in new stack -- Executing Wait("Zap/31-1", "2") in new stack -- Executing AbsoluteTimeout("Zap/31-1", "30") in new stack -- Set Absolute Timeout to 30 -- Executing Dial("Zap/31-1", "Zap/G1/002212601574") in new stack -- Requested transfer capability: 0x00 - SPEECH -- Called G1/002212601574 -- Moving call from channel 31 to channel 30 Apr 11 16:27:06 WARNING[10322]: chan_zap.c:7745 pri_fixup_principle: Can't fix up channel from 31 to 30 because 30 is already in use Apr 11 16:27:06 WARNING[10322]: chan_zap.c:9046 pri_dchannel: Unable to move channel 30! -- Channel 0/30, span 1 got hangup request Apr 11 16:27:06 WARNING[10966]: app_dial.c:706 wait_for_answer: Unable to forward voice -- Hungup 'Zap/30-1' == Everyone is busy/congested at this time (1:0/0/1) -- Executing NoOp("Zap/31-1", "CHANUNAVAIL") in new stack -- Executing Busy("Zap/31-1", "") in new stack -- Channel 0/31, span 1 got hangup request == Spawn extension (from-pstn, 111, 7) exited non-zero on 'Zap/31-1' -- Executing NoOp("Zap/31-1", "") in new stack -- Executing Goto("Zap/31-1", "999") in new stack -- Goto (from-pstn,h,999) -- Hungup 'Zap/31-1' Could somebody give me a clue? Pim _______________________________________________ --Bandwidth and Colocation provided by Easynews.com -- Asterisk-Users mailing list To UNSUBSCRIBE or update options visit: http://lists.digium.com/mailman/listinfo/asterisk-users
Pimjai Wesnarat
2006-Apr-11 08:06 UTC
AW: [Asterisk-Users] Dial out on Zap: Can't fix up channel from 31 to 30 because 30 is already in use??
Hi Marcus!!!! Yesterday I tried that but it didn't work but today I tried again just as u said and it works!! Danke sch?n! Vielen Dank! Gru?, Pim Marcus.Rothe@bertelsmann.de wrote:> I'm not sure if it's the same problem but your error message likely the same. > after i additing pridialplan=local in the zapata.conf i'm able to make outboundcalls (located in germany) > > marcus > > -----Urspr?ngliche Nachricht----- > Von: asterisk-users-bounces@lists.digium.com [mailto:asterisk-users-bounces@lists.digium.com] > Gesendet: Dienstag, 11. April 2006 16:33 > An: asterisk-users@lists.digium.com > Betreff: [Asterisk-Users] Dial out on Zap: Can't fix up channel from 31 to 30 because 30 is already in use?? > > Hi, > > I still cant dial out on Zap and I really have no clue why. > I'm using Asterisk Asterisk 1.2.6 and Zaptel 1.2.5 with Digium card 4 ports, 31 channels each and able to receive incoming calls and fax perfectly. > > I've done this in my dial plan. > > exten => 111,1,Answer() > exten => 111,n,Ringing() > exten => 111,n,Wait(2) > exten => 111,n,AbsoluteTimeout(30) > exten => 111,n,Dial(Zap/G1/002212601574) exten => 111,n,NoOp(${DIALSTATUS}) exten => 111,n,Busy() exten => 111,n,Hangup() > > My zapata.conf is like this > > > [channels] > context=from-pstn > group=0 > switchtype=euroisdn > overlapdial=yes > faxdetect=no > echocancel=yes > echocancelwhenbridged=yes > > > ; PRI port 1 (E1) > ; context=1 > group=1 > signalling=pri_cpe > channel=>1-15,17-31 > > > And I've got this on my CLI: > > -- Accepting overlap call from '2212601571' to '111' on channel 0/31, span 1 > -- Starting simple switch on 'Zap/31-1' > -- Executing Answer("Zap/31-1", "") in new stack > -- Executing Ringing("Zap/31-1", "") in new stack > -- Executing Wait("Zap/31-1", "2") in new stack > -- Executing AbsoluteTimeout("Zap/31-1", "30") in new stack > -- Set Absolute Timeout to 30 > -- Executing Dial("Zap/31-1", "Zap/G1/002212601574") in new stack > -- Requested transfer capability: 0x00 - SPEECH > -- Called G1/002212601574 > -- Moving call from channel 31 to channel 30 Apr 11 16:27:06 WARNING[10322]: chan_zap.c:7745 pri_fixup_principle: > Can't fix up channel from 31 to 30 because 30 is already in use Apr 11 16:27:06 WARNING[10322]: chan_zap.c:9046 pri_dchannel: Unable to move channel 30! > -- Channel 0/30, span 1 got hangup request Apr 11 16:27:06 WARNING[10966]: app_dial.c:706 wait_for_answer: Unable to forward voice > -- Hungup 'Zap/30-1' > == Everyone is busy/congested at this time (1:0/0/1) > -- Executing NoOp("Zap/31-1", "CHANUNAVAIL") in new stack > -- Executing Busy("Zap/31-1", "") in new stack > -- Channel 0/31, span 1 got hangup request > == Spawn extension (from-pstn, 111, 7) exited non-zero on 'Zap/31-1' > -- Executing NoOp("Zap/31-1", "") in new stack > -- Executing Goto("Zap/31-1", "999") in new stack > -- Goto (from-pstn,h,999) > -- Hungup 'Zap/31-1' > > > > Could somebody give me a clue? > > > Pim > > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > _______________________________________________ > --Bandwidth and Colocation provided by Easynews.com -- > > Asterisk-Users mailing list > To UNSUBSCRIBE or update options visit: > http://lists.digium.com/mailman/listinfo/asterisk-users > > >
Apparently Analagous Threads
- Dial out on Zap: Can't fix up channel from 31 to 30 because 30 is already in use??
- AW: Dial out on Zap
- Dial out on Zap
- Getting: Can't fix up channel from 5 to 7 because 7 is already in use, and pri_dchannel: Answer requested on channel 0/7 not in use on span 1
- samba 3.4 ADS support broken on ipv6 networks ?