I don&#39;t see any problem...... but, i don&#39;t see the 2nd SPAN @ zaptel: <div><br></div><div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; "><i>yellow alarm on <b>span 2</b></i></span></div>

<div><br></div><div><div><font class="Apple-style-span" face="arial, sans-serif"><span class="Apple-style-span" style="border-collapse: collapse;"><br></span></font></div><div><span class="Apple-style-span" style="border-collapse: collapse; font-family: arial, sans-serif; font-size: 13px; ">regards.<br>

</span><br></div><div><br></div><div>Juan.<br>Linux User #441131<br>
<br><br><div class="gmail_quote">On Mon, Feb 21, 2011 at 2:11 PM, Dean Hoover <span dir="ltr">&lt;<a href="mailto:kb7qdi@gmail.com">kb7qdi@gmail.com</a>&gt;</span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">

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&amp;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=&gt;1-23<br>
<br>
group=2<br>
context=twtelecom-in<br>
signalling=pri_cpe<br>
switchtype=5ess<br>
echocancel=yes<br>
channel=&gt;25-47<br>
<br>
group=3<br>
context=definity-in<br>
signalling=em_w<br>
channel=&gt;49-72<br>
<br>
group=10<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;73<br>
<br>
group=11<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;74<br>
<br>
group=12<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;75<br>
<br>
group=13<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;76<br>
<br>
group=14<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;77<br>
<br>
group=15<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;78<br>
<br>
group=16<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;79<br>
<br>
group=17<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;80<br>
<br>
group=18<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;81<br>
<br>
group=19<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;82<br>
<br>
group=20<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;83<br>
<br>
group=21<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;84<br>
<br>
group=22<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;85<br>
<br>
group=23<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;86<br>
<br>
group=24<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;87<br>
<br>
group=25<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;88<br>
<br>
group=26<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;89<br>
<br>
group=27<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;90<br>
<br>
group=28<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;91<br>
<br>
group=29<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;92<br>
<br>
group=30<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;93<br>
<br>
group=31<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;94<br>
<br>
group=32<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;95<br>
<br>
group=33<br>
context=testivr-in<br>
signalling=fxo_ks<br>
threewaycalling=yes<br>
transfer=yes<br>
channel=&gt;96<br>
<br>
---------------------------<br>
<div><div></div><div class="h5"><br>
On Mon, Feb 21, 2011 at 12:58 PM, Juan David Diaz &lt;<a href="mailto:juanchonk@gmail.com">juanchonk@gmail.com</a>&gt; wrote:<br>
&gt; Dean,<br>
&gt; what&#39;s your zaptel &amp; Zapata config_<br>
&gt; regards<br>
&gt; Juan.<br>
&gt; Linux User #441131<br>
&gt;<br>
&gt;<br>
&gt; On Mon, Feb 21, 2011 at 1:44 PM, Dean Hoover &lt;<a href="mailto:kb7qdi@gmail.com">kb7qdi@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; We are running Asterisk version 1.4.23-1, libpri-1.4.9 and<br>
&gt;&gt; zaptel-1.4.12.1 and two Digium TE220Ps.  Debugs are set to 10.<br>
&gt;&gt;<br>
&gt;&gt; We have a T1 PRI connected to the telco.  Over the last 4-5 days, we<br>
&gt;&gt; have getting Yellow/Red alarms coming from the T1 PRI.  The other two<br>
&gt;&gt; ports in use are connected to internal test switches (Avaya<br>
&gt;&gt; Legend/Avaya Definity), and are not showing any errors.<br>
&gt;&gt;<br>
&gt;&gt; /var/log/asterisk/messages reports:<br>
&gt;&gt; [Feb 21 12:21:56] NOTICE[4795] chan_dahdi.c: PRI got event: Alarm (4)<br>
&gt;&gt; on Primary D-channel of span 2<br>
&gt;&gt; [Feb 21 12:21:56] DEBUG[4795] chan_dahdi.c: Got event Alarm (4) on<br>
&gt;&gt; D-channel for span 2<br>
&gt;&gt;<br>
&gt;&gt; /var/log/syslog reports:<br>
&gt;&gt; Feb 21 12:21:56 asterisk kernel: [509981.796536] wct2xxp: Setting<br>
&gt;&gt; yellow alarm on span 2<br>
&gt;&gt; Feb 21 12:21:56 asterisk kernel: [509981.796562] timing source auto card<br>
&gt;&gt; 0!<br>
&gt;&gt; Feb 21 12:21:56 asterisk kernel: [509981.813535] timing source auto card<br>
&gt;&gt; 0!<br>
&gt;&gt; Feb 21 12:22:01 asterisk kernel: [509986.813869] wct2xxp: Clearing<br>
&gt;&gt; yellow alarm on span 2<br>
&gt;&gt;<br>
&gt;&gt; Intensive PRI debugging does not show any errors prior to the alarm.<br>
&gt;&gt;<br>
&gt;&gt; The other part to this is for a while it was pretty intermittent.  One<br>
&gt;&gt; day we would get it 2 times, another 8-12 times.  Today, however, it<br>
&gt;&gt; seems to be happening around every 11-13 minutes.  Before this<br>
&gt;&gt; started, there were no errors for the 6 days prior.<br>
&gt;&gt;<br>
&gt;&gt; The first response from the telco 4 days ago said that it was an issue<br>
&gt;&gt; on their T3, then came back saying we were sending something to reset<br>
&gt;&gt; the circuit, but I interpret &quot;PRI got event&quot; as meaning we received<br>
&gt;&gt; something from them.<br>
&gt;&gt;<br>
&gt;&gt; They put a COM tracer in our building, on that circuit, since Friday<br>
&gt;&gt; afternoon.  They took it with them to examine the results this<br>
&gt;&gt; morning, and are supposed to call me when they know something.<br>
&gt;&gt;<br>
&gt;&gt; While they are doing that, I want to make sure that I have all the<br>
&gt;&gt; information I need in order to diagnose it.  I haven&#39;t found a way to<br>
&gt;&gt; trace the actual B8ZS/ESF frames, and was wondering if there was a way<br>
&gt;&gt; for me to log those events.  It&#39;s not that I don&#39;t trust them, but by<br>
&gt;&gt; the same token I haven&#39;t changed anything on my end, the other port on<br>
&gt;&gt; the Digium card isn&#39;t reporting an issue, and a complete shutdown of<br>
&gt;&gt; the Asterisk server didn&#39;t change the results.<br>
&gt;&gt;<br>
&gt;&gt; Any advice would be greatly appreciated.<br>
&gt;&gt;<br>
&gt;&gt; Dean Hoover<br>
&gt;&gt; Milwaukee, Wisconsin<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; _____________________________________________________________________<br>
&gt;&gt; -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
&gt;&gt; New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
&gt;&gt;               <a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
&gt;&gt;<br>
&gt;&gt; asterisk-users mailing list<br>
&gt;&gt; To UNSUBSCRIBE or update options visit:<br>
&gt;&gt;   <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; _____________________________________________________________________<br>
&gt; -- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" target="_blank">http://www.api-digital.com</a> --<br>
&gt; New to Asterisk? Join us for a live introductory webinar every Thurs:<br>
&gt;               <a href="http://www.asterisk.org/hello" target="_blank">http://www.asterisk.org/hello</a><br>
&gt;<br>
&gt; asterisk-users mailing list<br>
&gt; To UNSUBSCRIBE or update options visit:<br>
&gt;   <a href="http://lists.digium.com/mailman/listinfo/asterisk-users" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-users</a><br>
&gt;<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>