kernel: zaphfc: empty HDLC frame or bad CRC received
Not sure if you're in the Netherlands (as I am) your nick seems to indicate that you might be.
In Holland (and I believe in the UK also) it is common practice by telecom providers (such as KPN) to 'drop' the ISDN D channel every X minutes (I believe it to be 5 minutes).
This results in the error you describe above. In my case I solved the issue by calling the KPN service number and requesting the D channel to the 'up' constantly. It took them 2 hours (great respone time, not sure if I was just lucky) to fix this & my problems were resolved.
Hi Frost,
thanks for your reply.
Yes I do live in the Netherlands :D
As you expected our telecom provider is KPN.
I called their customer service as soon as I read your message, but all they can tell me is that they will look into it and will call me back (in time)
These messages do appear a lot as soon as I connect the line to the computer.
Maybe you can give me some technical details so I can get things easier done with KPN support?
Leon
@rasker: I'm not sure that all UK telecom parties would do this, I just noticed a message in the past that seemed to indicate the same issue; that's why I mentioned the UK. If you do not have this error message showing up, your D channel should be fine!
@lblokland: It took me some convincing the helpdesk lady to make sure this got reported to an ISDN engineer. But after that it took a few hours & all was fine. Here's a reference to another person in the Netherlands with the same issue: http://www.threebit.net/mail-archive/asterisk-users/msg00788.html
good luck!
Hi Frost,
just got off the phone with the ISDN specialist from KPN.
They already changed the status of the D-channel to up 2 days ago.
As I look into the errors on the screen it continuesly tells me:
empty HDLC frame or bad CRC received (framelen = #, stat = 0ff, card = 0). where # is a different numer all the time.
When the line is connected, the other ISDN device, a normal quatrovox, won't function anymore.
Of course I already tried with the Quatrovox device disconnected, and restarted the asterisk box with only the computer connected.
That won't help.
Any suggestions?
Leon
lol yeah. It can be a biatch. More of an art than a science. Use this:
http://www.trixbox.org/modules/newbb/viewtopic.php?topic_id=1367&...
Roadkill's script pretty much covers my original description. Upgrade to udev .51 initially if you have problems loading the drivers for the card. Then go to .94 if you have to.
Rehan
BTW you might need to find a way to disable the ZapHFc drivers otherwise they will interfere with vISDN.
I tried a clean CD install of Trixbox 1.2 with the Cologne Chips HFC card installed in the box. A Dell Optiplex GX240 P4 1.6 768MB.
After all the initial reboots and setting the IP, I did the install-ZAPHFC -f t -R
chose Yes to download the updated script and settled for the 1.2.7 ver of Asterisk to patch with BRIstuff
I get the following:
zaphfc[0]: empty HDLC frame received
running ztcfg -vv I get:
Zaptel Configuration
=================
SPAN1: CCS/ AMI Build-out: 399-533 feet (DSX-1)
Channel map:
Channel 01: Clear Channel (Default) (Slaves: 01)
Channel 02: Clear Channel (Default) (Slaves: 02)
Channel 03: D-Channel (Default) (Slaves: 03)
3 channels configured.
So, it all looks ok?!
Doing a lspci I get:
02:08.0 Network Controller: Cologne Chips Designs GmbH ISDN Network Controller [HFC-PCI] (rev02)
I reboot the box. Tells me that Asterisk Died.
I try to configure and add the modules with freePBX.
When I try configure extensions, it says: This module requires access to the Asterisk Manager. Please ensure Asterisk is running and access to the manager is available.
I am a newbie and know very little about Linux and the recompile stuff.
Where did I go wrong? Can anyone help me please?
MadDogMike
:-o
hey medum,
just nanoed the file and rebooted, but same framing errors as before.
Asterisk doesn't die now!!
I used a softphone to call out on the BRI to my cellphone and it worked. I got the caller ID also. This happened only once, and never again...
Tried calling back to the Trixbox from the cellphone and just rings, no answer. Have setup IVR and greeting and tested it with 7777.
Now I get an occasional zaphfc[0]: received d channel frame with bad CRC inbetween the empty HDLC frames received.
Am now even more convinced we are on the right track.
Any other suggestions?
Thanks for the help so far.
MadDogMike
Please read through all the details listed in "If you're trying to get install-ZAPHFC working".
Alan
MadDogMike wrote:
hey medum,
just nanoed the file and rebooted, but same framing errors as before.
Asterisk doesn't die now!!
I used a softphone to call out on the BRI to my cellphone and it worked. I got the caller ID also. This happened only once, and never again...
Tried calling back to the Trixbox from the cellphone and just rings, no answer. Have setup IVR and greeting and tested it with 7777.
Now I get an occasional zaphfc[0]: received d channel frame with bad CRC inbetween the empty HDLC frames received.
Am now even more convinced we are on the right track.
Any other suggestions?
Thanks for the help so far.
MadDogMike
Hi
i get the same message "received d channel frame with bad CRC inbetween the empty HDLC frames received." but it work dont worry about message :)
Regards
Goran


Member Since:
2006-07-13