[Asterisk-Dev] E1, crc-4 errors
The Traveller
traveler at xs4all.nl
Thu May 15 14:48:29 MST 2003
Yo Konrad,
After some more experimenting, I think I've found the solution.
In "/etc/zaptel.conf", I had:
span=1,0,0,ccs,hdb3
and have now replaced it by:
span=1,1,0,ccs,hdb3
As far as I understand, this instructs the drivers to use the other side
of the line as sync-source. This seems to have made the warnings go away
for me.
Grtz,
Oliver
On Tue, May 13, 2003 at 16:47:42 +0200, Konrad Gorski wrote:
> Nearly 100% of errors (99,999%) at any time, regardless of activity on
> line. Please see attached log from Telco operator. In
> /var/log/asterisk/messages it report no alarms, but by any PRI
> connection:
>
> May 13 15:29:03 WARNING[12301]: File chan_zap.c, Line 5314
> (zt_pri_error): PRI: Read on 67 failed: Unknown error 500;
>
> This kind of WARNING was few times reported on mailing list - w/o
> answers/explanations (?).
>
> E1 line w/o alarms, E100P LED green, zttool: No alarms, IRQ Misses:0, ..
> Make it sense experiment with switchtype?
> Till now switchtype=euroisdn.
> Telco use Lucent 5ESS, so I will try switchtype=5ess.
>
> Konrad
>
>
> -----Original Message-----
> From: asterisk-dev-admin at lists.digium.com
> [mailto:asterisk-dev-admin at lists.digium.com] On Behalf Of Mark Spencer
> Sent: Monday, May 12, 2003 3:21 PM
> To: asterisk-dev at lists.digium.com
> Subject: RE: [Asterisk-Dev] E1, crc-4 errors
>
> > Load < 3%. IRQ - OK. E1 line and cabling - OK: Asterisk on this line
> > works well as my office PBX. CRC errors are on Telco side only. I've
> > tested E1 line with another PBX (TELRAD) - 0% CRC errors on Telco
> > side.
>
> CRC4 calculations are made within the framer itself. How many errors do
> you get? Do they show up at particular time intervals? In your
> /var/log/asterisk/messages does it report the line going into alarm?
>
> Mark
>
> _______________________________________________
> Asterisk-Dev mailing list
> Asterisk-Dev at lists.digium.com
> http://lists.digium.com/mailman/listinfo/asterisk-dev
More information about the asterisk-dev
mailing list