<div>have you check the PRI crossover cable?</div><br clear="all">Juan.<br>Linux User #441131<br>
<br><br><div class="gmail_quote">On Mon, Feb 21, 2011 at 2:35 PM, Juan David Diaz <span dir="ltr"><<a href="mailto:juanchonk@gmail.com">juanchonk@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Ooops, my bad I Did not read the zaptel config file correctly, my apologize.<div class="im"><div><br></div><div><span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px">span=1,0,0,esf,b8zs<br>
bchan=1-23<br>dchan=24<br><i>span=2,1,0,esf,b8zs<br>bchan=25-47<br>dchan=48</i></span></div></div><div> <br clear="all">Juan.<br>Linux User #441131<div><div></div><div class="h5"><br>
<br><br><div class="gmail_quote">On Mon, Feb 21, 2011 at 2:34 PM, Juan David Diaz <span dir="ltr"><<a href="mailto:juanchonk@gmail.com" target="_blank">juanchonk@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span style="border-collapse:collapse;font-family:arial, sans-serif;font-size:13px"><div>Your message was:</div><div><br></div><div>----------------------------------------------------</div><div>
Here you go:<br><br>/etc/zaptel.conf:<br>loadzone = us<br>defaultzone=us<br><br>span=1,0,0,esf,b8zs<br>bchan=1-23<br>dchan=24<br>span=2,1,0,esf,b8zs<br>bchan=25-47<br>dchan=48<br><br>#Added 2nd 2xT1 card<br>span=3,0,0,d4,ami<br>
e&m=49-72<br>span=4,0,0,d4,ami<br>fxoks=73-96</div></span><br clear="all">---------------------------------------------<br><div><br></div><div>mmmmm, I would change the timing sources of the spans:</div><div><br></div>
<div>
span=1,1,0,esf,b8zs</div><div><br></div><div>span=2,2,0,esf,b8zs</div><div><br></div><div><br></div><div>Have you try to plug the PRI into another Span that has been working properly??</div><div><br></div><div>Regards.</div>
<div><br></div><div>Juan.<br>Linux User #441131<div><div></div><div><br>
<br><br><div class="gmail_quote">On Mon, Feb 21, 2011 at 2:23 PM, Dean Hoover <span dir="ltr"><<a href="mailto:kb7qdi@gmail.com" target="_blank">kb7qdi@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
This doesn't represent the 2nd span?<br>
<div><br>
span=2,1,0,esf,b8zs<br>
bchan=25-47<br>
dchan=48<br>
<br>
</div><font color="#888888">Dean<br>
</font><div><div></div><div><br>
<br>
On Mon, Feb 21, 2011 at 1:18 PM, Juan David Diaz <<a href="mailto:juanchonk@gmail.com" target="_blank">juanchonk@gmail.com</a>> wrote:<br>
> I don't see any problem...... but, i don't see the 2nd SPAN @ zaptel:<br>
> yellow alarm on span 2<br>
><br>
> regards.<br>
><br>
><br>
> Juan.<br>
> Linux User #441131<br>
><br>
><br>
> On Mon, Feb 21, 2011 at 2:11 PM, Dean Hoover <<a href="mailto:kb7qdi@gmail.com" target="_blank">kb7qdi@gmail.com</a>> wrote:<br>
>><br>
>> Here you go:<br>
>><br>
>> /etc/zaptel.conf:<br>
>> loadzone = us<br>
>> defaultzone=us<br>
>><br>
>> span=1,0,0,esf,b8zs<br>
>> bchan=1-23<br>
>> dchan=24<br>
>> span=2,1,0,esf,b8zs<br>
>> bchan=25-47<br>
>> dchan=48<br>
>><br>
>> #Added 2nd 2xT1 card<br>
>> span=3,0,0,d4,ami<br>
>> e&m=49-72<br>
>> span=4,0,0,d4,ami<br>
>> fxoks=73-96<br>
>><br>
>> ---------------------------------------<br>
>><br>
>> /etc/asterisk/zapata.conf:<br>
>> [channels]<br>
>> group=1<br>
>> context=default<br>
>> signalling=pri_cpe<br>
>> switchtype=qsig<br>
>> channel=>1-23<br>
>><br>
>> group=2<br>
>> context=twtelecom-in<br>
>> signalling=pri_cpe<br>
>> switchtype=5ess<br>
>> echocancel=yes<br>
>> channel=>25-47<br>
>><br>
>> group=3<br>
>> context=definity-in<br>
>> signalling=em_w<br>
>> channel=>49-72<br>
>><br>
>> group=10<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>73<br>
>><br>
>> group=11<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>74<br>
>><br>
>> group=12<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>75<br>
>><br>
>> group=13<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>76<br>
>><br>
>> group=14<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>77<br>
>><br>
>> group=15<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>78<br>
>><br>
>> group=16<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>79<br>
>><br>
>> group=17<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>80<br>
>><br>
>> group=18<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>81<br>
>><br>
>> group=19<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>82<br>
>><br>
>> group=20<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>83<br>
>><br>
>> group=21<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>84<br>
>><br>
>> group=22<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>85<br>
>><br>
>> group=23<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>86<br>
>><br>
>> group=24<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>87<br>
>><br>
>> group=25<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>88<br>
>><br>
>> group=26<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>89<br>
>><br>
>> group=27<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>90<br>
>><br>
>> group=28<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>91<br>
>><br>
>> group=29<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>92<br>
>><br>
>> group=30<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>93<br>
>><br>
>> group=31<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>94<br>
>><br>
>> group=32<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>95<br>
>><br>
>> group=33<br>
>> context=testivr-in<br>
>> signalling=fxo_ks<br>
>> threewaycalling=yes<br>
>> transfer=yes<br>
>> channel=>96<br>
>><br>
>> ---------------------------<br>
>><br>
>> On Mon, Feb 21, 2011 at 12:58 PM, Juan David Diaz <<a href="mailto:juanchonk@gmail.com" target="_blank">juanchonk@gmail.com</a>><br>
>> wrote:<br>
>> > Dean,<br>
>> > what's your zaptel & Zapata config_<br>
>> > regards<br>
>> > Juan.<br>
>> > Linux User #441131<br>
>> ><br>
>> ><br>
>> > On Mon, Feb 21, 2011 at 1:44 PM, Dean Hoover <<a href="mailto:kb7qdi@gmail.com" target="_blank">kb7qdi@gmail.com</a>> wrote:<br>
>> >><br>
>> >> We are running Asterisk version 1.4.23-1, libpri-1.4.9 and<br>
>> >> zaptel-1.4.12.1 and two Digium TE220Ps. Debugs are set to 10.<br>
>> >><br>
>> >> We have a T1 PRI connected to the telco. Over the last 4-5 days, we<br>
>> >> have getting Yellow/Red alarms coming from the T1 PRI. The other two<br>
>> >> ports in use are connected to internal test switches (Avaya<br>
>> >> Legend/Avaya Definity), and are not showing any errors.<br>
>> >><br>
>> >> /var/log/asterisk/messages reports:<br>
>> >> [Feb 21 12:21:56] NOTICE[4795] chan_dahdi.c: PRI got event: Alarm (4)<br>
>> >> on Primary D-channel of span 2<br>
>> >> [Feb 21 12:21:56] DEBUG[4795] chan_dahdi.c: Got event Alarm (4) on<br>
>> >> D-channel for span 2<br>
>> >><br>
>> >> /var/log/syslog reports:<br>
>> >> Feb 21 12:21:56 asterisk kernel: [509981.796536] wct2xxp: Setting<br>
>> >> yellow alarm on span 2<br>
>> >> Feb 21 12:21:56 asterisk kernel: [509981.796562] timing source auto<br>
>> >> card<br>
>> >> 0!<br>
>> >> Feb 21 12:21:56 asterisk kernel: [509981.813535] timing source auto<br>
>> >> card<br>
>> >> 0!<br>
>> >> Feb 21 12:22:01 asterisk kernel: [509986.813869] wct2xxp: Clearing<br>
>> >> yellow alarm on span 2<br>
>> >><br>
>> >> Intensive PRI debugging does not show any errors prior to the alarm.<br>
>> >><br>
>> >> The other part to this is for a while it was pretty intermittent. One<br>
>> >> day we would get it 2 times, another 8-12 times. Today, however, it<br>
>> >> seems to be happening around every 11-13 minutes. Before this<br>
>> >> started, there were no errors for the 6 days prior.<br>
>> >><br>
>> >> The first response from the telco 4 days ago said that it was an issue<br>
>> >> on their T3, then came back saying we were sending something to reset<br>
>> >> the circuit, but I interpret "PRI got event" as meaning we received<br>
>> >> something from them.<br>
>> >><br>
>> >> They put a COM tracer in our building, on that circuit, since Friday<br>
>> >> afternoon. They took it with them to examine the results this<br>
>> >> morning, and are supposed to call me when they know something.<br>
>> >><br>
>> >> While they are doing that, I want to make sure that I have all the<br>
>> >> information I need in order to diagnose it. I haven't found a way to<br>
>> >> trace the actual B8ZS/ESF frames, and was wondering if there was a way<br>
>> >> for me to log those events. It's not that I don't trust them, but by<br>
>> >> the same token I haven't changed anything on my end, the other port on<br>
>> >> the Digium card isn't reporting an issue, and a complete shutdown of<br>
>> >> the Asterisk server didn't change the results.<br>
>> >><br>
>> >> Any advice would be greatly appreciated.<br>
>> >><br>
>> >> Dean Hoover<br>
>> >> Milwaukee, Wisconsin<br>
>> >><br>
>> >> --<br>
>> >> _____________________________________________________________________<br>
>> >> -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
>> >> New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
>> >> <a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
>> >><br>
>> >> asterisk-users mailing list<br>
>> >> To UNSUBSCRIBE or update options visit:<br>
>> >> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
>> ><br>
>> ><br>
>> > --<br>
>> > _____________________________________________________________________<br>
>> > -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
>> > New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
>> > <a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
>> ><br>
>> > asterisk-users mailing list<br>
>> > To UNSUBSCRIBE or update options visit:<br>
>> > <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
>> ><br>
>><br>
>> --<br>
>> _____________________________________________________________________<br>
>> -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
>> New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
>> <a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
>><br>
>> asterisk-users mailing list<br>
>> To UNSUBSCRIBE or update options visit:<br>
>> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
><br>
><br>
> --<br>
> _____________________________________________________________________<br>
> -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
> New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
> <a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
><br>
> asterisk-users mailing list<br>
> To UNSUBSCRIBE or update options visit:<br>
> <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
><br>
<br>
--<br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
<a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
<br>
asterisk-users mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
</div></div></blockquote></div><br></div></div></div>
</blockquote></div><br></div></div></div>
</blockquote></div><br>