Which revision of FS/OpenZAP/Zaptel are you using respectively?<br><br>All the errors after your shutdown are not really clues they are just typical<br>things that happen when you close the socket but the endless D-READ FAIL sounds strange. How often does this happen?<br>
<br>We mostly have sangoma users so we have less info on Digium cards<br>but I can try to investigate your problem for you if you answer my first round of questions.<br><br><br><br><div class="gmail_quote">On Wed, Jul 22, 2009 at 10:16 PM, Alex Green <span dir="ltr"><<a href="mailto:alexg@etherstack.com">alexg@etherstack.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">On a number of occasions using openzap with libpri the D channel seems<br>
to some how lose synchronisation resulting in 'D-READ FAIL! []'.<br>
<br>
Background:<br>
-----------<br>
On one side is a very standard Linux box with Freeswitch and a TE110p<br>
card. The signalling is set up to be a Network E1. On the other side of<br>
the PRI coax cable is a box I am experimenting with has openzap<br>
interacting with a small application of my own. This side is set up to<br>
be a CPE E1 (using a TE210p). This problem has happened to me previously<br>
using freeswtich/openzap but scouring the internet has found nought. I<br>
am concerned that I have done something silly, but I have double checked<br>
everything. The error is printed from lpwrap_pri.c line 117.<br>
<br>
Symptoms:<br>
---------<br>
On freeswitch "D-READ FAIL! []" is just printed to screen over and over<br>
again. After issuing a shutdown the following clue is given after<br>
stopping mod_openzap:<br>
2009-07-22 17:11:07 [INFO] zap_io.c:257 zap_channel_destroy() Closing<br>
channel zt:1:30 fd:67<br>
2009-07-22 17:11:07 [INFO] zap_io.c:257 zap_channel_destroy() Closing<br>
channel zt:1:31 fd:68<br>
D-READ FAIL! []<br>
Error = -1<br>
Lpwrap Run Pri: : Bad file descriptor<br>
<br>
On Openzap (without freeswitch) the following happens:<br>
[CRIT] src/ozmod/ozmod_libpri/lpwrap_pri.c:122 __pri_lpwrap_read() span<br>
5 D-READ FAIL! []<br>
[ERROR] src/ozmod/ozmod_libpri/ozmod_libpri.c:88 s_pri_error() !!<br>
Received short I-frame (expected 4, got -3)<br>
[DEBUG] src/ozmod/ozmod_libpri/ozmod_libpri.c:812 process_event() EVENT<br>
[ALARM_TRAP][7][5:1] STATE [PROGRESS_MEDIA]<br>
[DEBUG] src/ozmod/ozmod_libpri/ozmod_libpri.c:821 process_event()<br>
Changing state on 5:1 from PROGRESS_MEDIA to RESTART<br>
[WARNING] src/ozmod/ozmod_libpri/ozmod_libpri.c:831 process_event()<br>
channel 5:1 (1:1) has alarms! [YELLOW/LOOP]<br>
[DEBUG] src/ozmod/ozmod_libpri/ozmod_libpri.c:812 process_event() EVENT<br>
[ALARM_TRAP][7][5:2] STATE [DOWN]<br>
...The last two are printed repeatedly.<br>
<br>
<br>
For some extra information I have summarised my setup below. Any help on<br>
this (surly I am not the first person to experience this!) is greatly<br>
appreciated. Many thanks, -alex<br>
<br>
<br>
<br>
Setup:<br>
------<br>
*Zaptel.conf*<br>
Box1 (Freeswitch Network E1) has 'span=1,1,0,ccs,hdb3'<br>
Box2 (Openzap CPE E1) has 'span=1,0,0,ccs,hdb3'<br>
I have experimented with crc4 on/off and timing of 1/2.<br>
<br>
*openzap.conf* similar on both sides.<br>
[span zt]<br>
number => 1<br>
trunk_type => e1<br>
b-channel => 1-15,17-31<br>
d-channel=> 16<br>
<br>
*openzap.conf.xml*<br>
Box1 (Freeswitch Network E1).<br>
<libpri_spans><br>
<span id="1"><br>
<param name="node" value="network"/><br>
<param name="switch" value="euroisdn"/><br>
<param name="dialplan" value="XML"/><br>
<param name="context" value="default"/><br>
</span><br>
</libpri_spans><br>
<br>
Box2 (Openzap CPE) passes the following to libpri (via zap_configure_span);<br>
"node", "cpe",<br>
"switch", "euroisdn",<br>
"dp", "unknown",<br>
"l1", "alaw",<br>
<br>
_______________________________________________<br>
FreeSWITCH-dev mailing list<br>
<a href="mailto:FreeSWITCH-dev@lists.freeswitch.org">FreeSWITCH-dev@lists.freeswitch.org</a><br>
<a href="http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/listinfo/freeswitch-dev</a><br>
UNSUBSCRIBE:<a href="http://lists.freeswitch.org/mailman/options/freeswitch-dev" target="_blank">http://lists.freeswitch.org/mailman/options/freeswitch-dev</a><br>
<a href="http://www.freeswitch.org" target="_blank">http://www.freeswitch.org</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>Anthony Minessale II<br><br>FreeSWITCH <a href="http://www.freeswitch.org/">http://www.freeswitch.org/</a><br>ClueCon <a href="http://www.cluecon.com/">http://www.cluecon.com/</a><br>
Twitter: <a href="http://twitter.com/FreeSWITCH_wire">http://twitter.com/FreeSWITCH_wire</a><br><br>AIM: anthm<br><a href="mailto:MSN%3Aanthony_minessale@hotmail.com">MSN:anthony_minessale@hotmail.com</a><br>GTALK/JABBER/<a href="mailto:PAYPAL%3Aanthony.minessale@gmail.com">PAYPAL:anthony.minessale@gmail.com</a><br>
IRC: <a href="http://irc.freenode.net">irc.freenode.net</a> #freeswitch<br><br>FreeSWITCH Developer Conference<br><a href="mailto:sip%3A888@conference.freeswitch.org">sip:888@conference.freeswitch.org</a><br><a href="http://iax:guest@conference.freeswitch.org/888">iax:guest@conference.freeswitch.org/888</a><br>
<a href="mailto:googletalk%3Aconf%2B888@conference.freeswitch.org">googletalk:conf+888@conference.freeswitch.org</a><br>pstn:213-799-1400<br>