Summary:ASTERISK-08524: ZAP channels dies after a while (a week or close) of asterisk usage
Reporter:Anton Vazir (vazir)Labels:
Date Opened:2007-01-09 01:40:17.000-0600Date Closed:2011-06-07 14:03:06
Versions:Frequency of
Description:After a while of normal operation (usually from few days up to a week), all ZAP lines, become silent, until full restart of drivers, zaptel and asterisk.
Usage - Office PBX, 24x analogue lines, over Rhino channels bank, connected via Sangoma or Digium E1/T1 card.


NO any abnormal asterisk console reports, notices or warnings. Looks like problem is not in the asterisk core but in Zaptel core, since plain asterisk stop/start does not resolve the problem. Problem also confirmed by another user - Edwin Groothuis on the -dev mailing list.
Comments:By: Serge Vecher (serge-v) 2007-01-09 08:45:47.000-0600

anything changes if verbose / debug is turned up?

By: jmls (jmls) 2007-01-09 09:03:55.000-0600

when you say "all zap lines become silent" is this inbound, outbound or both ?

By: Anton Vazir (vazir) 2007-01-09 10:07:06.000-0600

I have debug 10 and verbose 10 levels. Nothing there...
I can't say right now if inbound hang too, server have 8xinbound (fxo) lines and 24xFXS (channel bank) lines. I can see "Ringing" messages like everything is ok - bu in real there is nothing, no ring no dialtone upon pickup.
SIP phones - works OK

By: Edwin Groothuis (mavetju) 2007-01-09 14:36:03.000-0600

Let me describe what happened:

A call came in on the PRI, and was forwarded towards my SIP phone. The caller heard the ringing tone, I heard the phone ringing. I answered the phone, and didn't hear anything on the line. The caller kept hearing the ringing tone.

All next incoming calls via the PRI had the same behaviour. All next outgoing calls via the PRI didn't work. The console didn't show anything interesting (verbose level 3, debug level 1).

A full restart of asterisk (stopping of asterisk, unload of the zaptel drivers, reload of the zaptel drivers and starting of asterisk) was the only way to resolve it.

By: Anton Vazir (vazir) 2007-01-09 15:11:13.000-0600

Looks even worse than I thought initially. Than 1.4 cannot be used for any ZAP links yet. Hopefully more users will confirm regarding the bug.

By: Serge Vecher (serge-v) 2007-01-09 15:32:07.000-0600

ok, what happens if you use code from 1.4 svn? Also, post the console log here anyway.

By: Edwin Groothuis (mavetju) 2007-01-09 15:44:58.000-0600

I used the 1.4 branch released on christmas morning, and after that I used the 1.4 branch from 4 january:


By: Tzafrir Cohen (tzafrir) 2007-01-20 07:41:31.000-0600

Does it work correctly with (zaptel, asterisk/libpri) of 1.2 of a ceretain version?

mavetju, vasir: do you describe the same system? the same hardware? What zaptel hardware is it, exactly?

By: Edwin Groothuis (mavetju) 2007-01-20 15:54:23.000-0600

The machine has two 5V TE4xx cards in it (410 or 405, Quad BRI), but only one is in use (defined in the zaptel.conf, configured in zapata.conf and hooked up). It is configured as an E1 (full 31 channels), 2 as Customer equipment, 2 as Network equipement.

By: Kyle Gordon (kylegordon) 2007-01-23 15:29:55.000-0600

I have one lowly Wildcard X101P using Zaptel 1.4.0 from source, and am experiencing the same issues on Asterisk 1.2.13~dfsg-2 (Debian), with libpri1.2 1.2.4-1 (Debian). Randomly, quite often as well (several times a day), Asterisk will stop hearing incoming calls. It has happened after a call many times, and I have experienced Asterisk forwarding a call to a SIP phone for two rings before cutting it off. The caller reported that it rang out for several minutes before they gave up.

Any attempts to make an outbound call after that are met with congestion.

The workaround is to stop asterisk, rmmod zaptel and wcfxo, modprobe wcfxo and start asterisk again. Not optimal.

By: Serge Vecher (serge-v) 2007-02-26 13:13:22.000-0600

vazir: is this still an issue with latest 1.4 svn for asterisk/zap/libpri?

By: Anton Vazir (vazir) 2007-02-26 21:00:58.000-0600

Yes, it's still an issue. Though, with 1.2 this was happening for me more often than with 1.4, and without need to reload kernel modules (as i remember, but that was a long time ago, and I'm not sure that i never had cases, when modules reload were required), that's why i've posted two bugreports, one for a case (this), when asterisk restart cures the situation, and another - (9081) when kernel module reload is required to restore an operation.
Please note that installations do not require libpri, since all of the operation is fxo/fxs.

By: Anton Vazir (vazir) 2007-02-28 03:35:40.000-0600

So it did happen again today -this time ALL ZAP channels died. Only driver reload helped. SIP are ok. I was unable to leave a system in the state for a long time - cannot leave office without telephones. I'll send a packed full-log (unfortunatelly recorded AFTER that happen to the support@digium.com

By: Serge Vecher (serge-v) 2007-02-28 08:20:15.000-0600

as I've mentioned in the other note, Digium support will handle this further. Please reopen the bug only at their direction. Thanks.