<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 12 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
{font-family:Verdana;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.E-MailFormatvorlage17
{mso-style-type:personal-reply;
font-family:"Calibri","sans-serif";
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:70.85pt 70.85pt 2.0cm 70.85pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=DE-CH link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Hi Hassan,<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>simply spoken, the error output gives you ISDN reason 34 which </span><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>indicates that there is no appropriate circuit/channel presently available to handle the call</span><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>. <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>First consideration: The available channels are exhausted by count (=your ingress channels exceed the possible egress channels) It would help to know what channel technology you use there, TDM/SS7 as well or other, and count setups in an SS7/SIP trace. I would try different hunting strategies here: first try from lowest to highest available so you should see free channels in the high range of your DAHDI spans.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Second consideration: The available channels are not exhausted but they are not available fast enough after clearing the previous call. Changing the hunting order to least recently used, will give more time to clear the state of a channel in all memory registers and the problem will only hit you at full load. However, a switch should be non blocking and allow to use all channels concurrently at a certain guaranteed number of call setups per second. Maybe your customer end is doing something sneaky and tries to initiate a float of calls at the very same millisecond and giving Asterisk a hard time by that to process them concurrently. I have seen automated dialers blast even big iron switches because in real life even on great-many-multi-E1-trunkgroups, there is always a shift in channels setup when humans are sitting at the CPE side. You should consider that there is a processing lag introduced by the machine it runs on (specs too low).<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Third consideration: You line interface board may be broken or the driver not correctly initialized so the firmware may not communicate with the DADHI/libSS7 driver correctly. The reason 34 may just be the default “catch all” exception that the driver API reports to Asterisk. I don’t know how to debug the DAHDI channel driver to a human readable log. Maybe some devs are currently not on holiday and can contribute to answer this or you call Digium support.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Fourth consideration: Are you using SQL CDRs? I have seen a case at a customer site where the channels is not freed up until the CDR writing is complete. By bad design in Asterisk, a database lag can affect your system badly and various timers will timeout before it can proceed the call. In this case you must tune your database (refer to slow queries log if you use MySQL…) or turn off sql cdr and parse the csv-cdr to have an asynchronous process not affecting your PBX anymore.<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>So long, <o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'>Florian<o:p></o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif"'><o:p> </o:p></span></p><p class=MsoNormal><span lang=EN-US style='font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'><o:p> </o:p></span></p><div style='border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm 4.0pt'><div><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=MsoNormal><b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Von:</span></b><span lang=EN-US style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'> asterisk-ss7-bounces@lists.digium.com [mailto:asterisk-ss7-bounces@lists.digium.com] <b>Im Auftrag von </b>Nyamul </span><span lang=DE style='font-size:10.0pt;font-family:"Tahoma","sans-serif"'>Hassan<br><b>Gesendet:</b> Freitag, 26. August 2011 08:51<br><b>An:</b> Asterisk SS7 List<br><b>Betreff:</b> [asterisk-ss7] Unable to create DAHDI err 34<o:p></o:p></span></p></div></div><p class=MsoNormal><o:p> </o:p></p><p class=MsoNormal>Hi,<o:p></o:p></p><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I just setup a new box last week, and for the past 2 - 3 days, it is giving the following problem:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'>app_dial.c:2196 dial_exec_full: Unable to create channel of type 'DAHDI' (cause 34 - Circuit/channel congestion)</span><o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>I get hundreds of these lines on the console. It is not that calls are not connecting at all, but some of them are connecting, and some are not. I am not sure why this is happening.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>"core show calls uptime" shows some calls are connected, varies randomly.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>"dahdi show channels" show that all channels are "In Service" and no channels are showing blocked.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>In "core set verbose 3" mode, I also see the following right after the error line posted above:<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal><span style='font-family:"Courier New"'>== Everyone is busy/congested at this time (1:0/1/0)</span><o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal>"dahdi_maint -s 1" output shows some errors, but they are not changing at all. They're static:<o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'>Span 1:</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'>>Framing Errors : 0:</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'>>CRC Errors : 0:</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'>>Code Violations : 96:</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'>>E-bit Count : 0:</span><o:p></o:p></p></div><div><p class=MsoNormal><span style='font-family:"Courier New"'>>General Errored Seconds : 85:</span><o:p></o:p></p></div></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Has anyone seen this before? Could someone please help?<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><p class=MsoNormal>Regards<o:p></o:p></p></div><div><p class=MsoNormal>HASSAN<o:p></o:p></p></div></div></div></body></html>