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