search for: pri_fixup_principl

Hi, in a PRI setup, the receiving side is changing the B channel at proceeding. It seems this sometimes breaks some logic (pri_fixup_principle) and then the hangup kind of breaks, release is not answered and a restart cycle is triggered (by remote side). Anyone can help me debug this ? I've seen many posts with simmilar issues but no answer/solution. This is happening on Asterisk 1.2.16 + libpri 1.2.4 on a sangoma A104D. On a gener...

System have been working great for weeks, using an average 40 of 120 dahdi channels. But today, I suddenly see scary things like this: -- Moving call from channel 5 to channel 7 [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:10608 pri_fixup_principle: Can't fix up channel from 5 to 7 because 7 is already in use [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:11535 pri_dchannel: Ringing requested on channel 0/7 not in use on span 1 -- Moving call from channel 7 to channel 12 [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:10608 pri_fixup_...

Hi, I got a problem with PRI that I'm not sure how to solve. Asterisk sits between PABX and PRI. PRI is span 1 and PABX is span 2. After every single call (no matter in what direction) I get "pri_fixup_principle: Call specified, but not found?" and "pri_dchannel: Hangup on bad channel" messages and the channel in question is restarted. As far as I can see, all calls complete fine. What could cause this? I'd appreciate any help given. Here is the debug log. -- Goto (PRI_N...

...wing error: [Oct 6 10:56:20] ERROR[9794]: chan_zap.c:8250 zt_pri_error: !! Unexpected Channel selection 3 The call does complete as normal but after about 2 or 3 hours of calls passing through this setup i start receiving errors like the following: [Oct 6 10:55:25] WARNING[9794]: chan_zap.c:8074 pri_fixup_principle: Can't fix up channel from 63 to 92 because 92 is already in use [Oct 6 10:55:25] WARNING[9794]: chan_zap.c:9245 pri_dchannel: Hangup on bad channel 0/30 on span 3 [Oct 6 10:55:55] WARNING[9794]: chan_zap.c:8074 pri_fixup_principle: Can't fix up channel from 63 to 92 because 92 is alread...

...1: TE2/0/1 "T2XXP (PCI) Card 0 Span 1" (MASTER) group=0,11 context=from-pstn switchtype = euroisdn signalling = pri_cpe channel => 17-31 context = default group = 63 but when i add in channel 1-15 like: channel => 1-15,17-31 i receive all the time this message chan_dahdi.c:9438 pri_fixup_principle: Can't move call (DAHDI/3-1) from channel 3 to 2. It is already in use. WARNING[4264]: chan_dahdi.c:9558 pri_find_fixup_principle: Span 1: PRI requested channel 1/2 is not available. in span 2 there is no problem ; Span 2: TE2/0/2 "T2XXP (PCI) Card 0 Span 2" group=0,12 context=...

...- Hungup 'Zap/1-1' == No one is available to answer at this time -- Executing Congestion("SIP/739-5935", "") in new stack == Spawn extension (siplocalclients, 0916000739, 2) exited non-zero on 'SIP/739-5935' Oct 10 13:14:46 WARNING[7544]: chan_zap.c:7445 pri_fixup_principle: Call specified, but not found? Oct 10 13:14:46 NOTICE[7544]: chan_zap.c:8768 pri_dchannel: hangup, did not find cref 32777, tei 0 Oct 10 13:14:46 WARNING[7544]: chan_zap.c:8769 pri_dchannel: Hangup on bad channel 0/1 on span 1 Oct 10 13:14:50 WARNING[7544]: chan_zap.c:7445 pri_fixup_principle:...

...iware server. PRI appears to be okay. It keeps trying to move my call to a different channel...usually channel 1. This is the deal here: Moving call from channel 23 to channel 1 Then the following errors after no audio then hanging up manually: Mar 24 17:46:17 WARNING[1315]: chan_zap.c:7792 pri_fixup_principle: Call specified, but not found? Mar 24 17:46:17 WARNING[1315]: chan_zap.c:8874 pri_dchannel: Hangup on bad channel 0/1 on span 1 Using asterisk 1.2.5, zaptel 1.2.4, and libpri 1.2.2 as they are the current stable releases. I've tried changing the timing sources around. Incoming calls on th...

Hello everybody again. I have a warning message in the CLI: *CLI> Jun 12 17:34:29 WARNING[10593]: chan_zap.c:8463 pri_fixup_principle: Call specified, but not found? *CLI> Jun 12 17:34:29 WARNING[10593]: chan_zap.c:8463 pri_fixup_principle: Call specified, but not found I don't know what it means. Can you help with this??? Thankyou very much. Bye bye... -------------- next part -------------- An HTML attachment was s...

...-- Executing [h at from-inside-redir:1] Hangup("Zap/1-1", "") in new stack [Jan 25 17:51:49] == Spawn extension (from-inside-redir, h, 1) exited non-zero on 'Zap/1-1' [Jan 25 17:51:49] -- Hungup 'Zap/1-1' [Jan 25 17:51:49] WARNING[5412]: chan_dahdi.c:8615 pri_fixup_principle: Call specified, but not found? [Jan 25 17:51:49] WARNING[5412]: chan_dahdi.c:9759 pri_dchannel: Hangup on bad channel 0/2 on span 1 This says it is using DAHDI but it is actually still Zaptel as I have not had much success getting DAHDI to work on OpenSuSE, but that is another post for a later...

...2] Dial("SIP/223-00000021", "DAHDI/g1/066104 9303|30") in new stack -- Requested transfer capability: 0x00 - SPEECH -- Called g1/0661049303 -- Moving call (DAHDI/3-1) from channel 3 to 2. [Oct 21 17:43:27] WARNING[4264]: chan_dahdi.c:9438 pri_fixup_principle: Can't mo ve call (DAHDI/3-1) from channel 3 to 2. It is already in use. [Oct 21 17:43:27] WARNING[4264]: chan_dahdi.c:9558 pri_find_fixup_principle: Spa n 1: PRI requested channel 1/2 is not available. -- Hungup 'DAHDI/3-1...

...-- 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...

...-- 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...

...ot;, "ZAP/g1/8016196000") in new stack -- Called g1/8016196000 -- Zap/25-1 is making progress passing it to Zap/1-1 -- Zap/25-1 is ringing -- Zap/25-1 answered Zap/1-1 -- Hungup 'Zap/25-1' I also see this error Mar 4 06:07:21 WARNING[13946]: chan_zap.c:7069 pri_fixup_principle: Call specified, but not found? Mar 4 06:07:21 WARNING[13946]: chan_zap.c:7711 pri_dchannel: Ringing requested on channel 0/1 not in use on span 1 Extensions.conf exten => _6XXX,1,Answer exten => _6XXX,2,Dial(ZAP/g1/${EXTEN}) exten => _6XXX,3,congestion() Zapata.conf [channels] swit...

...On my CLI it looks something like this: -- Executing Dial("Zap/1-1", "Zap/g1/02601591") in new stack -- Requested transfer capability: 0x00 - SPEECH -- Called g1/02601591 -- Moving call from channel 1 to channel 2 Apr 6 11:08:08 WARNING[5854]: chan_zap.c:7745 pri_fixup_principle: Can't fix up channel from 1 to 2 because 2 is already in use Apr 6 11:08:08 WARNING[5854]: chan_zap.c:9046 pri_dchannel: Unable to move channel 2! -- Zap/2-1 is proceeding passing it to Zap/1-1 Apr 6 11:08:22 NOTICE[5849]: chan_iax2.c:5691 update_registry: Restricting registration fo...

...On my CLI it looks something like this: -- Executing Dial("Zap/1-1", "Zap/g1/02601591") in new stack -- Requested transfer capability: 0x00 - SPEECH -- Called g1/02601591 -- Moving call from channel 1 to channel 2 Apr 6 11:08:08 WARNING[5854]: chan_zap.c:7745 pri_fixup_principle: Can't fix up channel from 1 to 2 because 2 is already in use Apr 6 11:08:08 WARNING[5854]: chan_zap.c:9046 pri_dchannel: Unable to move channel 2! -- Zap/2-1 is proceeding passing it to Zap/1-1 Apr 6 11:08:22 NOTICE[5849]: chan_iax2.c:5691 update_registry: Restricting registration fo...

...to set channel 2 (index 0) to linear mode. -- Zap/0:2-1 answered SIP/2352-9056 -- Channel 0/2, span 1 got hangup request -- Hungup 'Zap/0:2-1' == Spawn extension (from-internal, 2352, 1) exited non-zero on 'SIP/2352-9056' May 25 12:41:27 WARNING[22467]: chan_zap.c:7797 pri_fixup_principle: Call specified, but not found? I have changed my local dial plan settings etc. to no avail. The only way I can get it to consistently work is by defining the group as having only ONE channel forcing it to always use channel one. The Altigen system never moves the call, it stays on channel 1....

...ast_log(LOG_WARNING, "Received SETUP_ACKNOWLEDGE on unconfigured channel %d/%d span %d\n", PRI_SPAN(e->setup_ack.channel), PRI_CHANNEL(e->setup_ack.channel), pri->span); } else { chanpos = pri_fixup_principle(pri, chanpos, e->setup_ack.call); if (chanpos > -1) { ast_mutex_lock(&pri->pvts[chanpos]->lock); pri->pvts[chanpos]->setup_ack = 1; /* Send any queued digits */...

...ot more debugging info as this is a live service and needed restarting ASAP. Today I had a similar crash: -- Hungup 'DAHDI/0:5-1' [Feb 25 10:42:09] NOTICE[11222]: pbx_spool.c:349 attempt_thread: Call completed to DAHDI/g1/07973734513 [Feb 25 10:42:09] WARNING[7827]: chan_dahdi.c:12124 pri_fixup_principle: Call specified, but not found? [Feb 25 10:42:09] WARNING[7827]: chan_dahdi.c:13293 pri_dchannel: Hangup on bad channel 0/5 on span 1 One thing that is interesting here is that it's refering to channel 'DAHDI/0:5-1', when the channels are normally referred to as 'DAHDI/5-1'...

...e same vaules on a second call there is the DTMF problem again. Sometimes the DTMF tones are choppy at the other end of the line. There is also a Warning with outbound calls only: -- Called G1/016080... -- Moving call from channel 2 to channel 31 May 5 12:45:33 WARNING[1403]: chan_zap.c:7744 pri_fixup_principle: Can't fix up channel from 2 to 31 because 31 is already in use May 5 12:45:33 WARNING[1403]: chan_zap.c:9045 pri_dchannel: Unable to move channel 31! -- Zap/31-1 is ringing -- Zap/31-1 answered Zap/2-1 But everything is ok and working on not moblie connections My actual settings:...

...is PBX -> traditional phone) doesn't work at all. I get the following messages: --- -- Executing Dial("SIP/8403-5b0f", "Zap/g1/1311") in new stack -- Requested transfer capability: 0x00 - SPEECH -- Called g1/1311 Mar 31 12:45:34 WARNING[23193]: chan_zap.c:7792 pri_fixup_principle: Call specified, but not found? Mar 31 12:45:34 WARNING[23193]: chan_zap.c:9046 pri_dchannel: Unable to move channel 1! Don't know what to do if second ROSE component is of type 0x6 XXX Invalid Progress indicator value received: 14 -- Zap/1-1 is ringing Don't know what to do if second...