<div class="gmail_quote">On Wed, Jun 22, 2011 at 17:41, Wasim Baig <span dir="ltr"><<a href="mailto:wasim@convergence.pk">wasim@convergence.pk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div dir="ltr">You may be better off using chan_ss7 2.0, with clustering and mtp3d and put 8-16 E1 per box.<div><br></div></div></blockquote><div><br></div><div>Yes, we had used chan_ss7 in clustering setups, across 4 boxes, each doing 8 E1s. That was last year, using Asterisk 1.6.x and chan_ss7 1.2 / 1.3. The "high cps" crashes were constant. Moreover, when Asterisk on boxes 2, 3 and 4 (1 running mtp3d and 2, 3, 4 in sequential CICs) used to crash and restart, the 1st E1 on that particular box would always be "unallocated". We would have to stop all Asterisk instances, and start them backwards, like first #4, then #3 so and so on.</div>
<div><br></div><div>Have not used chan_ss7 2.0 yet. Is it going to improve the "high cps" crash that we experienced on Asterisk versions < 1.8?</div><div><br></div><div>Regards</div><div>HASSAN</div><div><br>
</div></div>