Hi, Here is a short description of previous threads :
Symptoms Users cannot issue any outgoing call though Basic Rate Interface lines are not all busy. Each time this happens, logs show "WARNING[26083] app_dial.c: Unable to create channel of type 'Zap' (cause 34 - Circuit/channel congestion)" (from /var/log/asterisk/full). Environment Either : A - 1.4.17-BRIstuffed-0.4.0-test6 (olivier) B- "last 3 versions of asterisk 1.2 bristuffed" (paco) C- 0.3.0-PRE-1y-p or 0.3.0-PRE-1y-k (gunnar) Frequency No message during a couple of days then up to 30 messages a day. Restarting Asterisk (asterisk -rx "restart when convenient") restores outgoing call capability for a new period of time. Steps to reproduce symptoms: None identified at the moment Investigations: Direction 1 : "Energy saving mode" This issue might occur because Telco are entering energy-saving mode (Michiel). Forbidding this energy saving mode fixed this. We're using the same Telco (France Telecom) in 5 locations. Problems occur in a single location where brand new BRI lines were provisioned. Obviously, every morning, lines were inactive for last several hours, so lines should be "asleep". In spite of that, we had no message for the first call in the morning. 1. Where can you read about energy-saving mode in ISDN BRI access ? 2. How can you check Telco enabled energy-saving mode ? For me, it is very difficult to any reliable data from Telco on this. Having a way to check things on my own would be very useful. 3. Beside Michiel, who has ever cured these symptoms after forbidding energy-saving mode ? 4. Why does this occur in 2008 ? Is this a new trend in Telco habbits ? BRI lines are here for years. Direction 2 : reporting to Software editor Has someone filed a bug report to Junghanns ? If positive, is there anything ongoing on this ? Should this be also handled to Digium ? Regards
_______________________________________________ Bristuff-users mailing list [email protected] http://lists.three-dimensional.net/mailman/listinfo/bristuff-users
