I would say that you'll want to verify the driver versions and firmware
for zaptel/dahdi, libpri and wanpipe
On 4/19/2010 5:53 PM, Bruce N wrote:
I will do that. But do you think the calls were actually attempted and it
wasn't a zaptel driver issue or an Asterisk problem?
Regards,
Bruce
Date: Mon, 19 Apr 2010 17:31:22 -0400
From: [email protected]
To: [email protected]
Subject: Re: [on-asterisk] Where to look for PRI failiure causes?
Did you check with the carrier? They'll probably have a record of it as
well.
Jim
On 4/19/2010 5:20 PM, Bruce N wrote:
Thanks for the input Jim and Leo.
Jim:
- At the time no channels were being used either inbound or outbound.
Inbound was failing or not reaching the system (I can't see any CDR
but I didn't have any debug turned ON pri at the time to see if it
hits the system or not)
- This is a full weight 23 channel pri with 24th as the D-Channel.
- So, where do we go from here to check why B-Channels weren't
available when none of them were being used?
Leo:
Nothing really alarming in /var/log/messages except for these (In fact
nothing at all related to span 1):
Apr 16 19:32:13 pbx ntpd[3190]: synchronized to 209.167.68.100, stratum 2
Apr 16 20:49:33 pbx kernel: wanpipe2: Module 6: Line disconnected on
span 2!
Apr 16 20:49:34 pbx kernel: wanpipe2: Module 6: Line connected on span 2!
Apr 16 21:13:59 pbx ntpd[3190]: synchronized to 208.80.96.70, stratum 2
Note: above only concern span 2 which is an analog Sangoma A400DE
card and not the PRI as the PRI is on span 1. It's only alarming to me
because the IP addresses are not known to me. But I am guessing those
are just used for NTP??!!
Thanks,
Bruce
Date: Mon, 19 Apr 2010 17:15:13 -0400
From: [email protected]
To: [email protected]
Subject: Re: [on-asterisk] Where to look for PRI failiure causes?
That cause code actually sounds pretty useful to me.
How many channels of PRI do you have?
How many channels were in use at that time?
Congestion would cause that sort of error, where the D-channel is
looking for a B-channel to assign a call to, and can't find any free.
Jim
On 4/19/2010 4:55 PM, Bruce N wrote:
Hi again,
This morning there was a blip on a PRI service with a Sandoma
A101DE card. I think it was effecting both outbound and inbound.
Asterisk restart was done wit `amportal restart` and service was back
on. So, I doubt it was a Telco issue.
Due to urgency of business hours there was no time to do tests and
turn on debug and now I am looking through the logs to find the cause.
Where should one look for details of this sort of a problem:
The only thing related I found was in /var/log/asterisk/full and
that is:
[2010-04-19 08:45:50] WARNING[29707] app_dial.c: Unable to create
channel of type 'ZAP' (cause 34 - Circuit/channel congestion)
Which is really not useful.
Thanks,
Bruce
_________________________________________________________________
Hotmail& Messenger are available on your phone. Try now.
http://go.microsoft.com/?linkid=9724461
--
--
Jim Van Meggelen
[email protected]
http://www.oreillynet.com/pub/au/2177
"A child is the ultimate startup, and I have three.
This makes me rich."
Guy Kawasaki
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Videos that have everyone talking! Now also in HD! MSN.ca Video.
<http://go.microsoft.com/?linkid=9724460>
--
--
Jim Van Meggelen
[email protected]
http://www.oreillynet.com/pub/au/2177
"A child is the ultimate startup, and I have three.
This makes me rich."
Guy Kawasaki
--
_________________________________________________________________
Live connected. Get Hotmail& Messenger on your phone.
http://go.microsoft.com/?linkid=9724462
--
--
Jim Van Meggelen
[email protected]
http://www.oreillynet.com/pub/au/2177
"A child is the ultimate startup, and I have three.
This makes me rich."
Guy Kawasaki
--
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
