[asterisk-users] Terrible dahdi_test results

[Gareth Blades]

On 15/05/14 16:28, Mike Leddy wrote:
> Hi Russ,
>
> I rebooted the machine loading dahdi_dummy in /etc/modules before
> the /etc/init.d/dahdi.
>
> Now dahdi_test shows a nearly perfect score:
>
> # dahdi_test
> Opened pseudo dahdi interface, measuring accuracy...
> 99.998% 99.990% 99.998% 99.996% 99.998% 99.998% 99.997% 99.997%
> 99.998% 99.997% 99.998% 99.997% 99.998% 99.998% 99.997% 99.998%
> 99.997% 99.997% 99.997% 99.998% 99.997% 99.998% 99.998% 99.997% ^C
> --- Results after 24 passes ---
> Best: 99.998% -- Worst: 99.990% -- Average: 99.997188%
> Cummulative Accuracy (not per pass): 99.997
>
> When I connect a live E1 to the card it does work but I get a fair
> number of:
>
> [May 15 15:10:39] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:10:42] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:10:43] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:10:43] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:10:43] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:10:45] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:11:01] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:11:01] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:11:06] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:11:12] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:11:12] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:11:12] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
> [May 15 15:11:13] NOTICE[4017] chan_dahdi.c: PRI got event: HDLC Bad FCS (8) on D-channel of span 1
>
> Resulting in:
>
> [May 15 15:10:34] NOTICE[4017] chan_dahdi.c: PRI got event: Alarm (4) on D-channel of span 1
> [May 15 15:10:39] NOTICE[4017] chan_dahdi.c: PRI got event: Alarm (4) on D-channel of span 1
> [May 15 15:10:43] NOTICE[4017] chan_dahdi.c: PRI got event: Alarm (4) on D-channel of span 1
> [May 15 15:10:44] NOTICE[4017] chan_dahdi.c: PRI got event: Alarm (4) on D-channel of span 1
> [May 15 15:10:45] NOTICE[4017] chan_dahdi.c: PRI got event: Alarm (4) on D-channel of span 1
> [May 15 15:11:13] NOTICE[4017] chan_dahdi.c: PRI got event: Alarm (4) on D-channel of span 1
> [May 15 15:11:17] NOTICE[4017] chan_dahdi.c: PRI got event: Alarm (4) on D-channel of span 1
> [May 15 15:11:22] NOTICE[4017] chan_dahdi.c: PRI got event: Alarm (4) on D-channel of span 1
>
> Not usable in production but getting a lot closer.
>
> Is there anything else that can be done to improve this ?
>
> Best regards,
>
> Mike
>
>

Check your span= line in you configuration. If your telco is providing 
clocking and you are set to generate it yourself then they go out of 
sync which generally causes errors like these. If you are set to be the 
clock master try changing it to see if it improves. It should either 
improve or not work at all.