Oops, misspell. I meant Wanpipe 3.5.18, the most current stable version as I checked today<div><br></div><div><br><br><div class="gmail_quote">On Wed, Feb 2, 2011 at 23:05, Moises Silva <span dir="ltr"><<a href="mailto:moises.silva@gmail.com">moises.silva@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">You are on a quite old version of wanpipe, several RBS related bugs<br>
were fixed after that. Can you upgrade?<br>
<br>
Moises Silva<br>
Senior Software Engineer<br>
Sangoma Technologies Inc. | 100 Renfrew Drive, Suite 100, Markham ON<br>
L3R 9R6 Canada<br>
t. 1 905 474 1990 x128 | e. <a href="mailto:moy@sangoma.com">moy@sangoma.com</a><br>
<div><div></div><div class="h5"><br>
<br>
<br>
On Wed, Feb 2, 2011 at 10:37 PM, Christian Cabrera <<a href="mailto:ccabrera@gmail.com">ccabrera@gmail.com</a>> wrote:<br>
> Hello,<br>
> One of my customers is experiencing something really weird: at bootup,<br>
> random channels from his E1 appears with a RxC CAS of "BLOCK". If I restart<br>
> wanrouter, then the channels randomly switch but we never get the 30<br>
> channels as IDLE at the same time.<br>
> System was working fine, then they reported some noise was getting into the<br>
> lines. Now the E1 won't even take calls. I've posted a pastebin of what the<br>
> dahdi_tool looks like after restarting wanrouter several times (each time<br>
> channels get random block/idle status). The url<br>
> is <a href="http://pastebin.com/xGB3XCTE" target="_blank">http://pastebin.com/xGB3XCTE</a><br>
> The specs of what I'm using:<br>
> Asterisk 1.4.36<br>
> Dahdi 2.4.0<br>
> Wanpipe 3.5.8<br>
> Sangoma AFT-A101c : SLOT=0 : BUS=48 : IRQ=177 : CPU=A : PORT=PRI : V=25<br>
> E1 is from Axtel<br>
> Ballum has been changed to dismiss the chance of that being the problem.<br>
> Dahdi_tool reports no alarms and when trying to dial out, a timeout occur (I<br>
> can see the mfcr2 debug in the console and I get no ring on the destination<br>
> phone).<br>
> As a side note: the E1 gets conencted into an standard PBX and works fine:<br>
> no noise nor anything bad happens. As soon as I get it into Asterisk, weird<br>
> things start to happen.<br>
> Could the card have gone bad? Let me know what can I do to debug as for<br>
> obvious reasons the E1 stays connected into the Alcatel during all work<br>
> hours.<br>
> Regards,<br>
> Christian Cabrera<br>
><br>
</div></div>> --<br>
> _____________________________________________________________________<br>
> -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
><br>
> asterisk-r2 mailing list<br>
> To UNSUBSCRIBE or update options visit:<br>
> <a href="http://lists.digium.com/mailman/listinfo/asterisk-r2" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-r2</a><br>
><br>
<font color="#888888"><br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-r2 mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-r2" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-r2</a></font></blockquote></div><br></div>