[Asterisk-Users] PRI issues
Kevin Smith
kevin.smith at mercury.net
Fri Mar 31 12:26:11 MST 2006
Mike, here is the interrupts (sorry for the formatting)
CPU0 CPU1 CPU2 CPU3
0: 117 174878327 0 0 IO-APIC-edge timer
1: 0 928 0 0 IO-APIC-edge i8042
8: 0 1 0 0 IO-APIC-edge rtc
9: 0 0 0 0 IO-APIC-level acpi
11: 0 0 0 0 IO-APIC-edge cpqphp
12: 0 3525 0 0 IO-APIC-edge i8042
14: 0 6264322 0 0 IO-APIC-edge ide0
169: 0 704988 0 0 IO-APIC-level cciss0
177: 0 48262108 0 0 IO-APIC-level eth0
193: 0 699441691 0 0 IO-APIC-level wct4xxp
NMI: 0 0 0 0
LOC: 174914618 174914617 174914616 174914615
ERR: 0
MIS: 0
Doug,
As for how the connection is connected. Yes, it is a PRI from a
provider. I switched the span to use the telco for the timing. So now my
zaptel.conf looks like this:
span=1,1,0,esf,b8zs. I realized that was still 0 and I never changed
that after I sent the e-mail. I was using asterisk for testing before we
hooked the PRI in and it was one of those "overlooked" items.
Thanks,
Kevin
Michael Welter wrote:
> Post your 'cat /proc/interrupts' for us.
>
> Kevin Smith wrote:
>> Hi everyone,
>>
>> I have been having some problems lately with our PRI and Asterisk, or
>> maybe it is just me. It happens once maybe twice a day, but when some
>> of our customers are calling in, the phone just drops on them. I
>> pulled the information below from the log from one that happened. I
>> notice why it is happening, but I can't seem to figure out a way to
>> stop it from happening. I also notice that it is saying I don't have
>> a D channel defined. I am not sure why it is saying that either.
>> Below are my zapata.conf files.
>>
>> If anyone has any suggestions/ideas it would be greatly appreciated.
>>
>> Thanks,
>> Kevin
>>
>> /etc/asterisk/zapata.conf
>> switchtype=national
>> defaultzone=us
>> context=default
>> signalling=pri_cpe
>> group=1
>> channel => 1-23
>> dchannel=24
>> callerid=asreceived
>>
>>
>> /etc/zapata.conf
>> span=1,0,0,esf,b8zs
>> bchan=1-23
>> dchan=24
>>
>>
>>
>> Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Bad FCS
>> (8) on Primary D-channel of span 1
>> Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Bad FCS
>> (8) on Primary D-channel of span 1
>> Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Abort
>> (6) on Primary D-channel of span 1
>> Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Abort
>> (6) on Primary D-channel of span 1
>> Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Bad FCS
>> (8) on Primary D-channel of span 1
>> Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Bad FCS
>> (8) on Primary D-channel of span 1
>> Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Bad FCS
>> (8) on Primary D-channel of span 1
>> Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Abort
>> (6) on Primary D-channel of span 1
>> Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: HDLC Abort
>> (6) on Primary D-channel of span 1
>> Mar 29 17:08:18 DEBUG[15151] chan_zap.c: Exception on 19, channel 2
>> Mar 29 17:08:18 DEBUG[15148] chan_zap.c: Exception on 18, channel 1
>> Mar 29 17:08:18 DEBUG[15148] chan_zap.c: Got event Alarm(4) on
>> channel 1 (index 0)
>> Mar 29 17:08:18 NOTICE[24038] chan_zap.c: PRI got event: Alarm (4) on
>> Primary D-channel of span 1
>> Mar 29 17:08:18 WARNING[24038] chan_zap.c: No D-channels available!
>> Using Primary channel 24 as D-channel anyway!
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 3: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 3
>> Mar 29 17:08:18 DEBUG[15151] chan_zap.c: Got event Alarm(4) on
>> channel 2 (index 0)
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 4: Red Alarm
>> Mar 29 17:08:18 WARNING[15151] chan_zap.c: Detected alarm on channel
>> 2: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 4
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 5: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 5
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 6: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 6
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 7: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 7
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 8: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 8
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 9: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 9
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 10: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 10
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 11: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 11
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 12: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 12
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 13: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 13
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 14: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 14
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 15: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 15
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 16: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 16
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 17: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 17
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 18: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 18
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 19: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 19
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 20: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 20
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 21: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 21
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 22: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 22
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Detected alarm on channel
>> 23: Red Alarm
>> Mar 29 17:08:18 WARNING[24039] chan_zap.c: Unable to disable echo
>> cancellation on channel 23
>>
>> _______________________________________________
>> --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
>>
>>
>
More information about the asterisk-users
mailing list