Summary:ASTERISK-21210: BRI locks up
Reporter:Lelio della Pietra (leliodp)Labels:
Date Opened:2013-03-06 05:37:47.000-0600Date Closed:2013-03-11 09:54:09
Versions: Frequency of
Environment:Asterisk, B410PAttachments:( 0) conf.tgz
( 1) log.txt
Description:Hello people,

Asterisk, B410P, today downloaded libpri from SVN v2314 and dahdi from SVN 10741. Default configuration (unmodified dist files, with just spans and SIP users configured) with four ISDN point-to-point spans (the configuration is automatically generated by a script of mine and it work perfectly on any other remote device except this one).

The endpoints are three Aethra Starvoice (one with two BRI and the other two with one BRI), supplied by British Telecom.

After some use, randomly, an ISDN channel locks up (once a time, not all simultaneously) and stops responding; each placed call returns a "Everyone is busy/congested at this time". A "dahdi restart" command solves the problem but, after some minutes, it happens again.

To get some debug data, I waited a channel lockup, enabled pri intense debug and placed a call through console, recording everything. The attached log (lines 249 and following) shows that there is a two-way traffic on the ISDN, but the call goes in congestion.

I'm locked up. Any ideas?
Comments:By: Richard Mudgett (rmudgett) 2013-03-06 10:12:45.816-0600

This looks like a duplicate of ASTERISK-21099

By: Rusty Newton (rnewton) 2013-03-08 12:35:21.727-0600

Can you verify that VERBOSE and DEBUG message types were set for the console, and if they were not, provide the log again? Despite you turning up the verbosity levels for both, I didn't see any messages of those types at all.

It may be easier to grab a log from the log file instead of capturing the CLI output. This would also help avoid the control characters you captured which makes things hard to read.


On the CLI you can also verify where debug logger message types are being written to with "logger show channels"

{quote} After some use, randomly, an ISDN channel locks up {quote}

So several calls go through fine before it locks up? Can you provide the same log as described above but demonstrating a call that works as well?

Looking at your chan_dahdi.conf file - I noticed that there is no configuration for switchtype, signaling, or channels. Did you grab the right file, or do you intend to use whatever defaults Asterisk may use when those are all undefined?

If you provide new configuration files, please remove all the sample file comments from them before providing them.. the sample comments are not useful for troubleshooting and just serve as noise.

By: Lelio della Pietra (leliodp) 2013-03-10 07:06:16.004-0500

I fixed the problem, it was a configuration mistake in the Starvoice, not an Asterisk problem (once fixed the config on the remote side, it works perfectly). Thank you to everybody for your support.