Well i have several Asterisk installations where the "cause 34" still occurs. To be honest this error is driving me crazy since it occurs pretty much random.
Most of the time i can see the error on inbound zap<->zap (e.g. Software Fax running on a Server with a ISDN card) bridges. I have seen this error also on outbound calls from SIP phones (less likely) aswell. The only thing that helps is to restart the machine. Most of the time I am using the following components: IBM Hardware (X3200 or X3400) Junghanns Octobri or SWYX SX2 Quadbri (HFC4S chipset) Ubuntu 8.04 Server LTS Asterisk 1.4.21.2 (modified Debian VOIP packages, the cause 34 patch is included) freepbx 2.5.1 sample of /var/log/asterisk/messages: [Mar 3 14:23:42] WARNING[10960] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 14:24:11] WARNING[10962] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 14:38:16] WARNING[11036] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 14:38:41] WARNING[11038] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:18:52] ERROR[11119] chan_zap.c: What is wrong with you? You cannot use cause 34 number when in state 7! [Mar 3 15:28:41] WARNING[11142] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:29:27] WARNING[11149] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:29:38] WARNING[11151] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:30:06] WARNING[11153] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:30:09] WARNING[11155] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:34:38] WARNING[11190] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:35:00] WARNING[11192] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:37:23] WARNING[11196] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:38:29] WARNING[11198] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:39:31] WARNING[11211] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:40:17] WARNING[11219] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:41:12] WARNING[11229] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:41:17] WARNING[11231] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:41:36] WARNING[11241] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 15:42:00] WARNING[11247] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:01:24] WARNING[11307] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:02:59] WARNING[11312] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:04:26] WARNING[11316] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:05:44] WARNING[11318] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:15:09] WARNING[11333] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:15:37] WARNING[11335] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:16:10] WARNING[11337] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:16:50] WARNING[11339] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:17:07] WARNING[11344] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:18:28] ERROR[11346] chan_zap.c: What is wrong with you? You cannot use cause 34 number when in state 7! [Mar 3 16:20:04] WARNING[11360] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:20:34] WARNING[11362] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:21:51] WARNING[11366] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) [Mar 3 16:30:37] ERROR[11415] chan_zap.c: What is wrong with you? You cannot use cause 34 number when in state 7! [Mar 3 17:14:18] WARNING[11605] app_dial.c: Unable to create channel of type 'ZAP' (cause 34 - Circuit/channel congestion) So if i can do anything to solve this problem i am more than willing to help! greets mirko ---------------------------------------------------------------------- Message: 1 Date: Fri, 6 Mar 2009 17:31:39 +0000 From: Steve Davies <[email protected]> Subject: Re: [Bristuff-users] Is cause 34 still there ? To: Bristuff Users list <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset=ISO-8859-1 Sods law, I came across this on a PtP ISDN circuit for the first time just yesterday, but that system has not yet been patched. As far as I know this issue is fixed by the patch, which I have been using for quite a while now. Regards, Steve 2009/2/25 Gunnar Schaller <[email protected]>: > Hello Olivier, > On my side (only Asterisk 1.2) the cause 34 problem is gone away with > my patch for that. As Tzafrir included the Bugfix in his version there > should be no cause 34 error with that. > In PtP mode I never seen a cause 34 error. > I didn't try to contact Junghanns about this issue. Anybody out there > willing to try it? > > Regards, > Gunnar > > > >> Hi, > >> Several threads here dealt last year, with channels appearing as all busy >> though they shouldn't. >> It both concerned 1.2 and 1.4. >> See >> http://thread.gmane.org/gmane.comp.telephony.pbx.asterisk.bristuff.user/111/focus=124 > >> A workaround was found though I'm not aware it made its way into Junghann's >> bristuff repo: >> http://thread.gmane.org/gmane.comp.telephony.pbx.asterisk.bristuff.user/154/focus=158 > >> I re-installed 2 PtmP systems using a Xorcom's xr6 pre-version, that Tzafrir >> kindly handed to me. >> I think these xr6 pre-version includes a the workaround mentioned above but >> I can't check by myself. > >> My question are : >> Is anyone still hit by un-legitimate cause 34 ? >> Has someone met those message while in PtP ? ------------------------------ _______________________________________________ Bristuff-users mailing list [email protected] http://lists.three-dimensional.net/mailman/listinfo/bristuff-users End of Bristuff-users Digest, Vol 16, Issue 1 ********************************************* _______________________________________________ Bristuff-users mailing list [email protected] http://lists.three-dimensional.net/mailman/listinfo/bristuff-users
