Håkon Nessjøen
2010-Feb-25 09:26 UTC
[asterisk-users] 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
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_principle: Can't fix up channel from 7 to 12 because 12 is already in use [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:11535 pri_dchannel: Ringing requested on channel 0/12 not in use on span 1 -- DAHDI/4-1 is ringing [Feb 25 10:18:17] 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:17] WARNING[17129]: chan_dahdi.c:11680 pri_dchannel: Answer requested on channel 0/7 not in use on span 1 [Feb 25 10:18:22] WARNING[17129]: chan_dahdi.c:10624 pri_fixup_principle: Whoa, there's no owner, and we're having to fix up channel 5 to channel 7 [Feb 25 10:21:44] WARNING[17129]: chan_dahdi.c:10661 pri_fixup_principle: Call specified, but not found? What would be the reason for things like this to happen? And are they really just warnings (as it says), or actual errors, where something bad is happening to the actual calls, or calls not acknowledged? H?kon
Håkon Nessjøen
2010-Mar-04 09:08 UTC
[asterisk-users] 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
Sometimes I get these in my kernel log: [3763662.549761] __sdla_bus_read_4:888: wanpipe PCI Error: Illegal Register read: 0x0040 = 0xFFFFFFFF [4014422.079673] __sdla_bus_read_4:888: wanpipe PCI Error: Illegal Register read: 0x0040 = 0xFFFFFFFF Anyone who knows what this is about? 2010/2/25 H?kon Nessj?en <haakon at avelia.no>> 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_principle: Can't fix up channel from 7 to 12 because 12 is > already in use > [Feb 25 10:18:12] WARNING[17129]: chan_dahdi.c:11535 pri_dchannel: > Ringing requested on channel 0/12 not in use on span 1 > -- DAHDI/4-1 is ringing > [Feb 25 10:18:17] 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:17] WARNING[17129]: chan_dahdi.c:11680 pri_dchannel: > Answer requested on channel 0/7 not in use on span 1 > [Feb 25 10:18:22] WARNING[17129]: chan_dahdi.c:10624 > pri_fixup_principle: Whoa, there's no owner, and we're having to fix > up channel 5 to channel 7 > > [Feb 25 10:21:44] WARNING[17129]: chan_dahdi.c:10661 > pri_fixup_principle: Call specified, but not found? > > What would be the reason for things like this to happen? > > And are they really just warnings (as it says), or actual errors, > where something bad is happening to the actual calls, or calls not > acknowledged? > > H?kon >-------------- next part -------------- An HTML attachment was scrubbed... URL: http://lists.digium.com/pipermail/asterisk-users/attachments/20100304/0dbdf23d/attachment.htm
Maybe Matching Threads
- Conneting Asterisk to Swyx pri
- NOTICE[180235]: chan_zap.c:7358 pri_dchannel: PRI got event: 6 on Primary D-channel of span 1
- chan_zap.c:8050 pri_dchannel: Ring requested on unconfigured channel 255/255 span 2
- PRI Behavior
- Disa not fully bridging outbound call