Help:-> Using install-ZAPHFC with an HFC chipset ISDN card & BRIstuff drivers.
Last edited: 29 March 2007
Make sure you have the latest version of install-ZAPHFC
The version of install-ZAPHFC that ships with TB is old and does not have TB specific code. When you run it for the first time download the new version then exit the script. Then re-run the updated script. If you want to download the script manually, you can get it from here.
You may find these provide some background information.... one, two, three and four
If you have other zap hardware get this running before running install-ZAPHFC. This may require that you leave the HFC hardware out of your system for the initial build (only seen on multi-port cards).
I've added code to install-ZAPHFC (from version 1.1.1.0) which should allow you to run the script on TB without needing any preparation.
Before you run install-ZAPHFC You would still benefit from:
- - Stopping asterisk (amportal stop)
If you have no other zaptel hardware then uncomment the dummy entry.
Then run install-ZAPHFC
If things don't start correctly:
- - Review the log file that is created during the build. You will find this saved as /etc/asterisk/install-zaphfc.log
Run the following from a command prompt:
for PROC in `ls -1 /proc/zaptel/`;do cat /proc/zaptel/$PROC|head -n 1;done
You should see all of the ISDN ports you have connected showing "ACTIVATED".
If they don't check:
- - Your ISDN service is live
Other Notes:
If you are using more than one single port HFC card, it appears safest to build with the Florz's patch especially if you see "empty HDLC frame or bad CRC received " in your logs.
This will mean you will be rolled back to a much earlier version of Asterisk. The safest being to use the tested Florz's build. Note: Florz' has not updated his patch for bristuff-0.3.0 in nearly a year. Please think very carefully before using it. Do not expect it to work well (if at all) with newer versions of zaptel (post 1.2.5).
I've not had any issues that I have not been able to resolve with Tribox and this script. And those issues I have found, or have been reported to me, I've included into the script. If you can't get things stable with Trixbox, then maybe consider using a version of AAH. If you are having a really hard time getting your cards to work then start with AAH 2.8 and build forward.
Add channels to FOP:
While you can use the ISDN ZAP channels in FreePBX without issue, FreePBX does not yet write these channels into the FOP configuration files. To do so edit /var/www/html/panel/op_buttons_custom.cfg and add the following section to it:
[Zap/x]
Position=z
Label="Zap x"
Extension=-1
Icon=3
Panel_Context=default
[Zap/y]
Position=z+1
Label="Zap y"
Extension=-1
Icon=3
Panel_Context=default
Where x & y are the channel numbers for your ISDN card and z is the position number (refer to /var/www/html/panel/op_buttons_additional.cfg). Restart Asterisk (amportal restart) to make the changes effective.
An example log file:
STARTED: Running ./install-ZAPHFC version 1.2.0.2 (5 December 2006) from /etc/asterisk/ on Tue Dec 5 22:50:41 GMT 2006
Command line:
HFC-PCI Card: 1 HFC-PCI (1397:2bd0) cards found
Asterisk: Found 1.2.13 installed.
Asterisk: Building Asterisk 1.2.13
BRIstuff: Patching with bristuff-0.3.0-PRE-1w
Shutdown: Asterisk shutdown.
Kernel version: 2.6.9-34.0.2.EL
Kernel directory: 2.6.9-34.0.2.EL-i686
Modules directory: /lib/modules/2.6.9-34.0.2.EL/extra
Link linux: lrwxrwxrwx 1 root 37 Dec 5 22:50 /usr/src/linux -> /usr/src/kernels/2.6.9-34.0.2.EL-i686
Link linux-2.6: lrwxrwxrwx 1 root 37 Dec 5 22:50 /usr/src/linux-2.6 -> /usr/src/kernels/2.6.9-34.0.2.EL-i686
Bristuff tar: Found. Not downloading
Bristuff dir: Previous install found. Removing.
Junghanns script: Running 22:50:53
Junghanns script: Finished 22:51:17
Zaptel build: -rw-r--r-- 1 root root 473987 Dec 5 22:51 zaptel.ko
Libpri build: lrwxrwxrwx 1 root root 13 Dec 5 22:52 libpri.so -> libpri.so.1.0
Zaphfc build: -rw-r--r-- 1 root root 133664 Dec 5 22:52 zaphfc.ko
Asterisk build: -rwxr-xr-x 1 root root 5698613 Dec 5 22:53 asterisk
modprobe.conf: Removing old zaphfc entry
modprobe.conf: Adding zaphfc entry
modprobe.conf: install zaphfc /sbin/modprobe --ignore-install zaphfc modes=0 && /sbin/ztcfg
sysconfig/zaptel: MODULES="$MODULES zaphfc" # HFC ISDN module
sysconfig/zaptel: #MODULES="$MODULES ztdummy" # UHCI USB Zaptel Timing Only Interface
proc: ZTHFC found in /proc/zaptel/3
Span 3: ZTHFC1 "HFC-S PCI A ISDN card 0 [TE] layer 1 ACTIVATED (F7)" AMI/CCS
zaptel.conf: Card 1 appears to be in /etc/zaptel.conf already.
zapata: zapata-BRI-HFC.conf include statement appears in /etc/asterisk/zapata.conf config.
FINISHED: Running ./zaphfc in /root/scripts on Tue Dec 5 22:55:33 GMT 2006
Command line help:
[root@pbx asterisk]# install-ZAPHFC -h
install-ZAPHFC:
- Install BRIstuff support.
- Builds zaphfc and configures one, or more, single port HFC cards.
- Builds qozap and configures a 4 port or an 8 port HFC card.
usage:
- zaphfc [-a
|-l ] [-B |-C ] [-R ] [-m 1|0[1|0[1|0[1|0]]] ] [-f t|u [-t 1|2|3|4] [-s 1|0[1|0[1|0[1|0]]]] ] - zaphfc -h
- zaphfc -V
Options:
- -a
: The version of Asterisk you want to patch with BRIstuff (e.g. 1.2.1)
The default is to use the version number from the currently installed Asterisk.
* if you specify both B & C options the last occurrence on the command line takes presidence
t (tested) the last tested patch will be applied (this may use an earlier * to do so).
u (un-tested) patch the latest version of BRIstuff (CAUTION).
Use 1 for NT mode and 0 for TE mode.
Specify one or more cards with card 1 as the rightmost digit. Examples:
-m 1 Card 1 in NT mode.
-m 10 Card 2 NT mode card 1 TE mode.
-m 11 Cards 2 & 1 in NT mode.
-m 1100 Cards 4 & 3 in NT mode cards 2 & 1 in TE mode.
Use 1 for Slave mode and 0 for Master mode. Only when built with Florz's patch.
Specify one or more cards with card 1 as the rightmost digit. Examples:
-s 1 Card 1 in Slave mode. (Assumes you have more than one card).
-s 10 Card 2 in Slave mode card 1 in Master mode.
-s 110 Cards 3 & 2 in Slave mode card 1 in Master mode.
-s 1110 Cards 4, 3 & 2 in Slave mode card 1 in Master mode.
as of 2.4.2007
install-ZAPHFC -a 1.2.14 installs asterisk 1.2.17, but the script fails so
cd /usr/src/bbristuff-0.3.0-PRE-1y-d and ./compile.sh - this works fine
You're right Junghanns have changed their numbering convention, which I missed.
They have also issued a new version of BRIstuff today so I'll review the last few versions and cross check against the build table.
EDIT: This is now fixed and includes today's update for BRIstuff.
Alan
install-ZAPHFC
Look here for more help.
Current version is 1.2.0.9 (3 April 2007)
I have tryed to run the install-ZAPHFC -f u, then the zaptel fails, without the -f u, everything is ok but I get theese errors:
zaphfc: empty HDLC frame or bad CRC received (framelen = 2, stat = 0xff, card = 0).
any solution?
regard
medum
You will need to roll back to an earlier build where the Florz' patch is known to work.
Alan
install-ZAPHFC
Look here for more help.
Current version is 1.2.0.9 (3 April 2007)
Hi Alan
I found that if your service provider of the ISDN do not set L1 permanent on you will get the error mentet above.
Regard
Medum
Can you add a bit more detail to this, e.g. country, telco , service and I'll add something to the help notes.
Alan
install-ZAPHFC
Look here for more help.
Current version is 1.2.0.9 (3 April 2007)
Hi Alan
I have a standard ISDN in Denmark with the main telco TDC. Ithink they as default don't have L1 permanet on.
I hav noticed this and tryed it out with a public switch and tryed to set on L1 perm in the switch and then no errors, and with L1 off then there is this errors.
A other thing I have noticed is that Trixbox can't see the status of the Asterisk, after it have been changed with install-ZAPHFC - in the main window it say unknown of the asterisk server, the same in system maint. Before the install-ZAPHFC it was ok, I have tryed it out with 3 different mashines. But the asterisk server is running and everything works well.
Regard
Medum
ist that possible to add the point for version .18 (whats in the version 2.2 included) in the script?
regards
Lord Z.
OK this is definitely going into the help file as an FAQ...
I think I'd better add this to the help as an FAQ... ;-)
My script integrates the right pieces together to build asterisk with HFC support.
For each version of asterisk I have to wait for Junghanns to release a version of BRIstuff for it. When they do I update and re-issue the script. If you want to speed things up you could check for new versions of BRIstuff (http://www.junghanns.net/downloads/?C=M;O=D) and give me a nudge (well it might make me feel wanted).
That said there's nothing to stop you using 2.1.17 with TB 2.2
Hi Alan,
I wanted do dive a bit deeper into the ISDN background information, but all four links you provide are dead. Is this a local issue with me or are the posts gone?
>>"You may find these provide some background information.... one, two, three and four"
In general - you saved ages of my life with this script -many many thanks
Ralph from Germany
Ralf
The links referred to posts on the TB site which were broken when the site moved platforms. I'll probably not be able to find them again so I'll remove them from the help file.
And its nice to be appreciated. Thanks.
Hi Alan,
I've read a lot of your posts concerning ISDN cards within Trixbox. All sounds very hopefull, helpfull and great :) But whatever I do, I can't get it to work! After multiple installs and several options tried I don't know what to do now. I hope you can help me.
I'm using a Dutch telco (KPN) for my ISDN-2 line.
After installation of TB 2.2 I'll stop asterisk and zaptel as you mentioned in your howto. After that I commented out all modules in /etc/syssconfig/zaptel
Then I ran install-ZAPHFC and I needed to choose a Asterisk version, I've chosen 1.2.17, because it was 1.2.18 and going a version higher wasn't appreciated :)
This took some time and after the script finished I went to FreePBX and created a SIP account for my X-lite. Calling gave me the message 'All circuits are busy, please try again later'. I went back to my PBX monitor and saw the "empty HDLC frame or bad CRC received " appeared on my screen.
There is only one single port ISDN card in this machine, although I tried your option for Florz's patch with install-ZAPHFC -f u, but when this finished I screwed my whole machine. In /proc/zaptel isn't anything left. And this is the result of service zaptel start:
[root@asterisk1 asterisk]# service zaptel start
Loading zaptel framework: [ OK ]
Waiting for zap to come online: [ OK ]
Loading zaptel hardware modules:
Loading zaphfc: FATAL: Module zaphfc not found.
FATAL: Error running install command for zaphfc
[FAILED]
No functioning zap hardware found in /proc/zaptel, loading ztdummypll
Loading ztdummypll: FATAL: Module ztdummypll not found.
[FAILED]
Running ztcfg: ZT_SPANCONFIG failed on span 1: No such device or address (6)
[FAILED]
What am I doing wrong? I tried 2 different pc's for installation, so it couldn't be a hardware issue, except for the ISDN card, but that one worked with Windows, so it's not dead.
I hope you have an answer to this issue, I'm really out of options. I also tried with TB 2.0 and older from the 1.x series.
Thanks in advance.
Kind regards,
Hans Middelhoek
Can you post a build log please (/etc/asterisk/install-zaphfc.log)?
Hello Alan,
I will post the build log asap. The machine in question is switch off atm.
Thanks for your reaction.
also, can you make it a log for a build without using the Florz's patch?
Hi Alan,
I will post the whole log history from my test machine. It was freshly installed and I've only done what I said. First without the -f parameter where I needed to select the Asterisk version to patch and after that, because it didn't work (error CRC HDLC etc), I ran the script with -f u. The newest log is at the top.
[root@asterisk1 asterisk]# cat install-zaphfc.log
STARTED: Running /usr/local/sbin/install-ZAPHFC version 1.3.0 (11 May 2007) from /etc/sysconfig on Thu May 24 22:30:42 CEST 2007
Command line: --help
HFC-PCI Chip: 1 port card found (1397:2bd0).
FINISHED: Running /usr/local/sbin/install-ZAPHFC in /etc/sysconfig on Thu May 24 22:30:42 CEST 2007
[root@asterisk1 asterisk]# cat install-zaphfc.log.1
STARTED: Running /usr/local/sbin/install-ZAPHFC version 1.3.0 (11 May 2007) from /etc/sysconfig on Thu May 24 22:30:35 CEST 2007
Command line:
HFC-PCI Chip: 1 port card found (1397:2bd0).
Asterisk: Found 1.2.17 installed.
Asterisk: Building Asterisk 1.2.17
BRIstuff: Patching with bristuff-0.3.0-PRE-1y-e
FINISHED: Running /usr/local/sbin/install-ZAPHFC in /etc/sysconfig on Thu May 24 22:30:39 CEST 2007
[root@asterisk1 asterisk]# cat install-zaphfc.log.2
STARTED: Running /usr/local/sbin/install-ZAPHFC version 1.3.0 (11 May 2007) from /etc/asterisk on Thu May 24 21:55:09 CEST 2007
Command line: -f u
HFC-PCI Chip: 1 port card found (1397:2bd0).
Asterisk: Found 1.2.17 installed.
Asterisk: Building Asterisk 1.2.17
BRIstuff: Patching with bristuff-0.3.0-PRE-1y-e
Shutdown: Asterisk shutdown.
Shutdown: Found zaphfc ...Unloading
Shutdown: Found zaptel ...Unloading
Shutdown: Found zttranscode ...Unloading
Shutdown: Found zaptel ...Unloading
Trixbox: Applying changes to allow build on Trixbox
Kernel version: 2.6.9-34.0.2.ELsmp
Kernel directory: 2.6.9-34.0.2.EL-smp-i686
Modules directory: /lib/modules/2.6.9-34.0.2.ELsmp/extra
Link linux: lrwxrwxrwx 1 root 41 May 24 21:55 /usr/src/linux -> /usr/src/kernels/2.6.9-34.0.2.EL-smp-i686
Link linux-2.6: lrwxrwxrwx 1 root 41 May 24 21:55 /usr/src/linux-2.6 -> /usr/src/kernels/2.6.9-34.0.2.EL-smp-i686
Bristuff tar: Found. Not downloading
Bristuff dir: Previous install found. Removing.
Junghanns script: Running 21:55:51
Junghanns script: Finished 21:57:18
Florz Patch: Downloading <a href="http://brightheadtechnology.com/other/aah/zaphfc_0.3.0-PRE-1o_florz-12.diff.gz" title="http://brightheadtechnology.com/other/aah/zaphfc_0.3.0-PRE-1o_florz-12.diff.gz">http://brightheadtechnology.com/other/aah/zaphfc_0.3.0-PRE-1o_flo...</a>
Zaptel build: -rw-r--r-- 1 root root 391788 May 24 21:58 zaptel.ko
Libpri build: lrwxrwxrwx 1 root root 13 May 24 21:58 libpri.so -> libpri.so.1.0
Florz Patch: Patching
Zaphfc build:
Asterisk build: -rwxr-xr-x 1 root root 5712545 May 24 22:00 asterisk
modprobe.conf: Removing old zaphfc entry
modprobe.conf: Adding zaphfc entry
modprobe.conf: install zaphfc /sbin/modprobe --ignore-install zaphfc modes=0 sync_slave=0 timer_card=0 && /sbin/ztcfg
sysconfig/zaptel: MODULES="$MODULES zaphfc" # HFC ISDN module
sysconfig/zaptel: #MODULES="$MODULES ztdummy" # UHCI USB Zaptel Timing Only Interface
proc: HFC-S not found in /proc/zaptel/
FINISHED: Running /usr/local/sbin/install-ZAPHFC in /etc/asterisk on Thu May 24 22:04:40 CEST 2007
[root@asterisk1 asterisk]# cat install-zaphfc.log.3
STARTED: Running /usr/local/sbin/install-ZAPHFC version 1.3.0 (11 May 2007) from /etc/asterisk on Thu May 24 21:54:41 CEST 2007
Command line: --help
HFC-PCI Chip: 1 port card found (1397:2bd0).
FINISHED: Running /usr/local/sbin/install-ZAPHFC in /etc/asterisk on Thu May 24 21:54:41 CEST 2007
[root@asterisk1 asterisk]# cat install-zaphfc.log.4
STARTED: Running /usr/local/sbin/install-ZAPHFC version 1.3.0 (11 May 2007) from /etc/sysconfig on Thu May 24 21:27:27 CEST 2007
Command line:
HFC-PCI Chip: 1 port card found (1397:2bd0).
Asterisk: Found 1.2.18 installed.
Asterisk: Building Asterisk 1.2.17
BRIstuff: Patching with bristuff-0.3.0-PRE-1y-e
Shutdown: Asterisk shutdown.
Shutdown: Found zaptel ...Unloading
Shutdown: Found zttranscode ...Unloading
Shutdown: Found zaptel ...Unloading
Trixbox: Applying changes to allow build on Trixbox
Trixbox: Removed rpm asterisk-1.2.18-3
Trixbox: Removed rpm zaptel-1.2.17.1-4
Kernel version: 2.6.9-34.0.2.ELsmp
Kernel directory: 2.6.9-34.0.2.EL-smp-i686
Modules directory: /lib/modules/2.6.9-34.0.2.ELsmp/extra
yum: Running yum to install kernel-smp-devel
Link linux: lrwxrwxrwx 1 root 41 May 24 21:29 /usr/src/linux -> /usr/src/kernels/2.6.9-34.0.2.EL-smp-i686
Link linux-2.6: lrwxrwxrwx 1 root 41 May 24 21:29 /usr/src/linux-2.6 -> /usr/src/kernels/2.6.9-34.0.2.EL-smp-i686
spinlock.h: File edited.
Bristuff tar: Downloading bristuff-0.3.0-PRE-1y-e.tar.gz
Junghanns script: Running 21:29:31
Junghanns script: Finished 21:30:57
Zaptel build: -rw-r--r-- 1 root root 391788 May 24 21:32 zaptel.ko
Libpri build: lrwxrwxrwx 1 root root 13 May 24 21:32 libpri.so -> libpri.so.1.0
Zaphfc build: -rw-r--r-- 1 root root 143089 May 24 21:32 zaphfc.ko
Asterisk build: -rwxr-xr-x 1 root root 5712545 May 24 21:34 asterisk
modprobe.conf: Adding zaphfc entry
modprobe.conf: install zaphfc /sbin/modprobe --ignore-install zaphfc modes=0 && /sbin/ztcfg
sysconfig/zaptel: Adding zaphfc entry
sysconfig/zaptel: MODULES="$MODULES zaphfc" # HFC ISDN module
sysconfig/zaptel: #MODULES="$MODULES ztdummy" # UHCI USB Zaptel Timing Only Interface
proc: ZTHFC found in /proc/zaptel/1
Span 1: ZTHFC1 "HFC-S PCI A ISDN card 1 [TE]"
zaptel.conf: Added config for Card 1 to /etc/zaptel.conf
zapata: Added statement to include zapata-BRI-HFC.conf config in /etc/asterisk/zapata.conf
zapata: Written basic config to zapata-BRI-HFC.conf
FINISHED: Running /usr/local/sbin/install-ZAPHFC in /etc/sysconfig on Thu May 24 21:39:23 CEST 2007
[root@asterisk1 asterisk]# cat install-zaphfc.log.5
STARTED: Running /usr/local/sbin/install-ZAPHFC version 1.3.0 (11 May 2007) from /root on Thu May 24 21:23:51 CEST 2007
Command line:
HFC-PCI Chip: 1 port card found (1397:2bd0).
Asterisk: Found 1.2.18 installed.
Asterisk: Building Asterisk 1.2.17
BRIstuff: Patching with bristuff-0.3.0-PRE-1y-e
FINISHED: Running /usr/local/sbin/install-ZAPHFC in /root on Thu May 24 21:24:58 CEST 2007
[root@asterisk1 asterisk]# cat install-zaphfc.log.6
STARTED: Running /usr/local/sbin/install-ZAPHFC version 1.3.0 (11 May 2007) from /usr/local/sbin on Thu May 24 21:22:33 CEST 2007
Command line:
HFC-PCI Chip: 1 port card found (1397:2bd0).
Asterisk: Found 1.2.18 installed.
FINISHED: Running /usr/local/sbin/install-ZAPHFC in /usr/local/sbin on Thu May 24 21:22:53 CEST 2007
Asterisk: Found 1.2.18 installed.
FINISHED: Running /usr/local/sbin/install-ZAPHFC in /root on Thu May 24 21:23:26 CEST 2007
[root@asterisk1 asterisk]# cat install-zaphfc.log.7
STARTED: Running /usr/local/sbin/install-ZAPHFC version 1.1.0.1 (1 May 2006) from /root on Thu May 24 21:22:27 CEST 2007
Command line:
HFC-PCI Card: 1 HFC-PCI cards found
Script: Script updated. Spawning with /usr/local/sbin/install-ZAPHFC
Thanks in advance.
The build with Florz's patches fails because zaphfc.ko does not build (as expected with 1.2.17).
The original build without Florz's patches against 1.2.17 worked.
For the ISDN errors reported
"empty HDLC frame or bad CRC received "
you might try checking you have no shared interrupts on your motherboard. Also moving the ISDN card to another slot might help here.
Hi Alan,
Thanks. I'll try again asap. Sounds worth a try :)
Hans
Hi Alan,
I tried another pc. It's an AMD Athlon XP 1700+ with 512MB DDR.
Freshly installed with TB 2.2, after installation I ran install-ZAPHFC and updated the script, than I interrupted the script and started it again with the new version.
I got a lot of the HDLC frame or bad CRC error, so I removed the soundcard and placed the ISDN card in the slot of the sound card.
Now I'm able to call and receive calls, but it isn't woking very nice, too bad. At a certain time, not sure when or after which event, I can't receive or make calls anymore. Calling out gives; "all lines are busy now, please try your call again later", and receiving calls will get a message from our dutch provider. Something like; "Because of technical issues this number can't be reached".
Than, when I call to my own number with my cell phone I get that message and after that I can call out again :?
A amportal restart and a service zaptel restart does work also, but this shoudn't happen. Do you've any clue in this?
Below I will post some logs and an error message when stopping zaptel:
May 29 10:00:44 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 3, stat = 0xff, card = 0). May 29 10:00:55 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 7, stat = 0xff, card = 0). May 29 10:01:05 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 6, stat = 0xff, card = 0). May 29 10:01:16 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 6, stat = 0xff, card = 0). May 29 10:01:38 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 7, stat = 0xff, card = 0). May 29 10:01:59 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 6, stat = 0xff, card = 0). May 29 10:03:33 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 6, stat = 0xff, card = 0). May 29 10:04:17 asterisk1 last message repeated 3 times May 29 10:04:27 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 4, stat = 0xff, card = 0). May 29 10:06:33 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 6, stat = 0xff, card = 0). May 29 10:06:44 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 6, stat = 0xff, card = 0). May 29 10:09:34 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 2, stat = 0xff, card = 0). May 29 10:09:55 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 7, stat = 0xff, card = 0). May 29 10:10:06 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 2, stat = 0xff, card = 0). May 29 10:10:17 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 6, stat = 0xff, card = 0). May 29 10:10:50 asterisk1 last message repeated 2 times May 29 10:12:01 asterisk1 kernel: zaphfc: empty HDLC frame or bad CRC received (framelen = 6, stat = 0xff, card = 0).
This message doesn't appear the whole time. When I can't make calls anymore this messages appears.
[root@asterisk1 log]# service zaptel restart
Unloading zaptel hardware drivers:
Unloading zaphfc: ERROR: Module zaphfc is in use
[FAILED]
Removing zaptel module: ERROR: Module zaptel is in use by zttranscode,zaphfc
[FAILED]
Loading zaptel framework: [ OK ]
Waiting for zap to come online: [ OK ]
Loading zaptel hardware modules:
Loading zaphfc: [ OK ]
Running ztcfg: [ OK ]
When everything is fine the /proc/zaptel/1 sais:
[root@asterisk1 log]# cat /proc/zaptel/1
Span 1: ZTHFC1 "HFC-S PCI A ISDN card 0 [TE] layer 1 ACTIVATED (F7)" AMI/CCS
1 ZTHFC1/0/1 Clear (In use)
2 ZTHFC1/0/2 Clear (In use)
3 ZTHFC1/0/3 HDLCFCS (In use
But when it isn't working anymore (after the error message mentioned above, it sais:
[root@asterisk1 log]# cat /proc/zaptel/1
Span 1: ZTHFC1 "HFC-S PCI A ISDN card 0 [TE] layer 1 DEACTIVATED (F6)" AMI/CCS
1 ZTHFC1/0/1 Clear (In use)
2 ZTHFC1/0/2 Clear (In use)
3 ZTHFC1/0/3 HDLCFCS (In use)
Mind the DEACTIVATED (F6), instead of ACTIVATED (F7)! Strange. When I saw the DEACTIVATED I called to my own number and I got the message from my operator "The number you're calling is temporarily unavailable because of technical issues, please move your call to a later moment", but then in dutch :)
After that the /proc/zaptel/1 gave the ACTIVATED message and I can make and receive calls again.
I think it's very very strange, but maybe you or someone else can think of something.
Thanks in advance. Your help is very appreciated (thus far).
Kind regards,
Hans Middelhoek
is out.
please can you update your scripted?
tnx
Trude
Hi Trude,
What do you mean by bristuff-0.3.0-PRE-1y-f is out? That there is a newer version? Can I fix that myself or does Alan need to update his script for the newer version of bri-stuff?
Thanks.
it supports now: asterisk-1.2.18, zaptel 1.2.17.1 and libpri 1.2.4
I hope somebody (Alan) will update the install script.
ospito: you'll find that the 1.2.14 asterisks will work with the Florz patch to stop the interrupt issues.
install-ZAPHFC -a 1.2.14 -f u -R
alan, I was wondering if it would be possible to make your script more modular, so that it would become easier to update it with the latest libpri, junghanns etc. what are your thoughts on that?
Done.
alan, I was wondering if it would be possible to make your script more modular, so that it would become easier to update it with the latest libpri, junghanns etc. what are your thoughts on that?
I'm not sure what you mean here....
However here's how I see the software flow:
- A version of Asterisk gets released
- Junghanns' releases a version of BRIstuff which includes a set of patches for this version of Asterisk and the current associated versions of Zaptel and Libpri.
- I add the relevant details to the script so that the new version of BRIstuff can be built.
If you mean modular in being able to add the details of a new release of BRIstuff, right now it only requires the addition/edit of two lines of code and the addition of a new version number in a few places.
Maybe I'm missing something?
Hello,
I had my TB 2.2 up and running with the Florz's patch and Asterisk 1.2.14 like Frost wrote.
@Frost
Weren't you the one from The Netherlands? And replied in a topic of lblokland? I read that one I think, I'm going to look for it... Yes you were :)
http://www.trixbox.org/forums/trixbox-forums/open-discussion/kern...
I got it to work with that topic, I needed to call KPN and asked for it, within 4 hours everything was set. With Florz's patch off course. All error messages disappeared after the KPN (Dutch telecom company) changed the setting for my ISDN line.
Because this installation was on one of my test pc's I was trying to install TB 2.2 on the server where it belongs :) And I saw Alan updated his script. I tried this first, but unfortunately the script can't finish, see below:
----------------------------------------------------- Building zaphfc in: /usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc ----------------------------------------------------- rm -f zaphfc.o *.ko *.mod.c *.mod.o .*o.cmd *~ rm -rf .tmp_versions make -C /usr/src/linux-2.6 SUBDIRS=/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc ZAP=-I/usr/src/bristuff-0.3.0-PRE-1y-e/zaptel modules make[1]: Entering directory `/usr/src/kernels/2.6.9-34.0.2.EL-i686' CC [M] /usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.o Building modules, stage 2. MODPOST *** Warning: "zt_register" [/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko] undefined! *** Warning: "zt_transmit" [/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko] undefined! *** Warning: "zt_receive" [/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko] undefined! *** Warning: "zt_ec_chunk" [/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko] undefined! *** Warning: "zt_unregister" [/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko] undefined! CC /usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.mod.o LD [M] /usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko make[1]: Leaving directory `/usr/src/kernels/2.6.9-34.0.2.EL-i686' /usr/local/sbin/install-ZAPHFC: line 271: cd: /usr/src/bristuff-0.3.0-PRE-1y-e/asterisk-1.2.18: No such file or directory ----------------------------------------------------- Building Asterisk in: /usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc ----------------------------------------------------- rm -f zaphfc.o *.ko *.mod.c *.mod.o .*o.cmd *~ rm -rf .tmp_versions make -C /usr/src/linux-2.6 SUBDIRS=/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc ZAP=-I/usr/src/bristuff-0.3.0-PRE-1y-e/zaptel modules make[1]: Entering directory `/usr/src/kernels/2.6.9-34.0.2.EL-i686' CC [M] /usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.o Building modules, stage 2. MODPOST *** Warning: "zt_register" [/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko] undefined! *** Warning: "zt_transmit" [/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko] undefined! *** Warning: "zt_receive" [/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko] undefined! *** Warning: "zt_ec_chunk" [/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko] undefined! *** Warning: "zt_unregister" [/usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko] undefined! CC /usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.mod.o LD [M] /usr/src/bristuff-0.3.0-PRE-1y-e/zaphfc/zaphfc.ko make[1]: Leaving directory `/usr/src/kernels/2.6.9-34.0.2.EL-i686' install -D -m 644 zaphfc.ko /lib/modules/`uname -r`/misc/zaphfc.ko ls: asterisk: No such file or directory ----------------------------------------------------- Setting up zaptel configuration ----------------------------------------------------- Cannot start: /sbin/ztcfg is missing. ----------------------------------------------------- Checking contents of /proc/zaptel for HFC-S ----------------------------------------------------- grep: /proc/zaptel/*: No such file or directory /usr/local/sbin/install-ZAPHFC: line 1205: [: -gt: unary operator expected A process for HFC-S was not found in /proc/zaptel/ directory Try rebooting, then run "cat /proc/zaptel/*" from a console prompt ----------------------------------------------------- This builds logfile is in /etc/asterisk/install-zaphfc.log -----------------------------------------------------
And in /etc/asterisk/install-zaphfc.log
STARTED: Running /usr/local/sbin/install-ZAPHFC version 1.3.1 (29 May 2007) from /etc/asterisk on Wed May 30 13:46:46 CEST 2007 Command line: HFC-PCI Chip: 1 port card found (1397:2bd0). Asterisk: Found 1.2.18 installed. Asterisk: Building Asterisk 1.2.18 BRIstuff: Patching with bristuff-0.3.0-PRE-1y-e Shutdown: Asterisk shutdown. Shutdown: Found zaptel ...Unloading Shutdown: Found wctdm ...Unloading Shutdown: Found wcfxo ...Unloading Shutdown: Found wcte11xp ...Unloading Shutdown: Found wct1xxp ...Unloading Shutdown: Found wct4xxp ...Unloading Shutdown: Found tor2 ...Unloading Shutdown: Found zttranscode ...Unloading Shutdown: Found zaptel ...Unloading Trixbox: Applying changes to allow build on Trixbox Trixbox: Removed rpm asterisk-1.2.18-3 Trixbox: Removed rpm zaptel-1.2.17.1-4 Kernel version: 2.6.9-34.0.2.EL Kernel directory: 2.6.9-34.0.2.EL-i686 Modules directory: /lib/modules/2.6.9-34.0.2.EL/extra yum: Running yum to install kernel-devel Link linux: lrwxrwxrwx 1 root 37 May 30 13:49 /usr/src/linux -> /usr/src/kernels/2.6.9-34.0.2.EL-i686 Link linux-2.6: lrwxrwxrwx 1 root 37 May 30 13:49 /usr/src/linux-2.6 -> /usr/src/kernels/2.6.9-34.0.2.EL-i686 spinlock.h: File edited. Bristuff tar: Downloading bristuff-0.3.0-PRE-1y-e.tar.gz Junghanns script: Running 13:49:45 Junghanns script: Finished 13:51:12 Zaptel build: UDEV Rules: zaptel.rules not found, installing. Libpri build: lrwxrwxrwx 1 root root 13 May 30 13:51 libpri.so -> libpri.so.1.0 Zaphfc build: -rw-r--r-- 1 root root 133092 May 30 13:51 zaphfc.ko Asterisk build: modprobe.conf: Adding zaphfc entry modprobe.conf: install zaphfc /sbin/modprobe --ignore-install zaphfc modes=0 && /sbin/ztcfg sysconfig/zaptel: Adding zaphfc entry sysconfig/zaptel: MODULES="$MODULES zaphfc" # HFC ISDN module sysconfig/zaptel: #MODULES="$MODULES ztdummy" # UHCI USB Zaptel Timing Only Interface proc: HFC-S not found in /proc/zaptel/ FINISHED: Running /usr/local/sbin/install-ZAPHFC in /etc/asterisk on Wed May 30 13:51:48 CEST 2007
Maybe I did something wrong myself, but I thought you would know.
Now I'm building with Florz's patch on 1.2.14 and everything went fine. I think I will use that because of stability.
Thank you all for your help.
i have the same problems.
on a fresh 2.2 install without Florz's Patch
Trude
This was my fault....
I had been caught out by an earlier BRIstuff update thinking it supported 1.2.18.
With the new version I missed updating a field in the 1.2.18 record I had created earlier.
I've corrected and released 1.3.1a
Hi Hans,
I think I've had the same problem.
Please read http://readlist.com/lists/lists.digium.com/asterisk-users/0/3721.... and go for workaround #3. I still have to thank Jeroen for that!
Regards,
Marcel Koster
I am in a new installation of trixbox 2.2. I have one HFC isdn card.
the line :
MODULES="$MODULES zaphfc" # HFC ISDN module
does not exist in this file (\etc\sysconfig\zaptel)
This line existed in Trixbox 2.0 same file.
Should I add this to continue installation ?
Also do I have to comment the ztdummy entry ?
Thank you
Dimitris
Dimitris
If you used install-ZAPHFC to configure your system then you should see an entry in the build log (see above) telling you what it did with \etc\sysconfig\zaptel. The log should also give you a clue to any build failures, if that's what happened.
Also do I have to comment the ztdummy entry ?
No, but I've always advocated only having those devices you have uncommented in \etc\sysconfig\zaptel. Once you have a 'real' zaptel device, you no longer need ztdummy.
Hi Alan,
What a wonderfull instruction this is!!!!
Still I have a problem.
After installing The quadbri with the use of your scrip, I do not see zapchanels in the following:
asterisk1*CLI> zap show status
Description Alarms IRQ bpviol CRC4
Wildcard TDM400P REV E/F Board 1 OK 0 0 0
quadBRI PCI ISDN Card 1 Span 1 [TE] (c RED 0 0 0
quadBRI PCI ISDN Card 1 Span 2 [TE] (c RED 0 0 0
quadBRI PCI ISDN Card 1 Span 3 [TE] (c RED 0 0 0
quadBRI PCI ISDN Card 1 Span 4 [TE] (c RED 0 0 0
I also do not know how to proceed in the GUI of trixbox to use the 4 ISDN channels an the 2 pstn channels that I have.
Could you please lead me in the good directions?
You probably need more info, so please let me know.
Thanks
Willy
Willy
Can you post the build log first please?
quote:
I'm not sure what you mean here....
However here's how I see the software flow:
1. A version of Asterisk gets released
2. Junghanns' releases a version of BRIstuff which includes a set of patches for this version of Asterisk and the current associated versions of Zaptel and Libpri.
3. I add the relevant details to the script so that the new version of BRIstuff can be built.
If you mean modular in being able to add the details of a new release of BRIstuff, right now it only requires the addition/edit of two lines of code and the addition of a new version number in a few places.
Maybe I'm missing something?
---
I guess you're right. I was wondering if there was any value in splitting the script itself from the variable information, so that both could be updated separately. But I guess that would only complicate matters more.
p.s. I still find the error I believe you mentioned fixing in the latest version of the script. I've opened another thread for it though, didn't want to hijack this one.
Hi Alan,
I have already reinstalled the Trixbox and managed now to get the LED's on the card to respond: green for the connected ISDN line.
However, the ISDN line is in PTP mode, the zapata-BRI-HFC.conf is in PTmP mode and trixbox is starting. When I change the PTmP to PTP and reboot, then asterisk is not starting up.
here the config files:
ZAPTEL.conf
# Autogenerated by /usr/local/sbin/genzaptelconf -- do not hand edit
# Zaptel Configuration File
#
# This file is parsed by the Zaptel Configurator, ztcfg
#
# It must be in the module loading order
# Span 1: WCTDM/0 "Wildcard TDM400P REV E/F Board 1"
fxsks=1
fxsks=2
# channel 3, WCTDM, inactive.
# channel 4, WCTDM, inactive.
# Global data
loadzone = us
defaultzone = us
# HFC CARD NOTE:
# When run for the first time the card numbers start from 1
# When run subsequently the card numbers start from 0
# Go figure!
# Span 2: ztqoz/1/1 "quadBRI PCI ISDN Card 1 Span 1 [TE] (cardID 0) Layer 1 DEACTIVATED (F0)"
span=2,1,3,ccs,ami
bchan=5-6
dchan=7
# Span 3: ztqoz/1/2 "quadBRI PCI ISDN Card 1 Span 2 [TE] (cardID 0)"
span=3,1,3,ccs,ami
bchan=8-9
dchan=10
# Span 4: ztqoz/1/3 "quadBRI PCI ISDN Card 1 Span 3 [TE] (cardID 0)"
span=4,1,3,ccs,ami
bchan=11-12
dchan=13
# Span 5: ztqoz/1/4 "quadBRI PCI ISDN Card 1 Span 4 [TE] (cardID 0)"
span=5,1,3,ccs,ami
bchan=14-15
dchan=16
_------------------------------------------------------------
zapata-BRI-HFC.conf
; Basic ISDN Card TE mode config
resetinterval=never
immediate=no
switchtype=euroisdn
signalling=bri_cpe_ptmp
pridialplan=dynamic
prilocaldialplan=local
nationalprefix=0
internationalprefix=00
usecallingpres=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=100
context=from-zaptel
group=0
channel => 5-6
channel => 8-9
channel => 11-12
channel => 14-15
_--------------------------------------------------------------
zapata.conf
;
; Zapata telephony interface
;
; Configuration file
[trunkgroups]
[channels]
language=en
context=from-zaptel
signalling=fxs_ks
rxwink=300 ; Atlas seems to use long (250ms) winks
;
; Whether or not to do distinctive ring detection on FXO lines
;
;usedistinctiveringdetection=yes
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=no
echotraining=800
rxgain=0.0
txgain=0.0
group=0
callgroup=1
pickupgroup=1
immediate=no
;faxdetect=both
faxdetect=incoming
;faxdetect=outgoing
;faxdetect=no
;Include genzaptelconf configs
#include zapata-auto.conf
group=1
;Include AMP configs
#include zapata_additional.conf
;Include BRI-HFC configs
#include zapata-BRI-HFC.conf
Here is the cli after set to ptp.
[root@asterisk1 ~]# genzaptelconf
STOPPING ASTERISK
Asterisk ended with exit status 0
Asterisk shutdown normally.
Asterisk Stopped
STOPPING FOP SERVER
safe_opserver: no process killed
/var/www/html/panel/safe_opserver: line 7: 3648 Killed $FOPWEBROOT/op_server.pl
FOP Server Stopped
Generating '/etc/zaptel.conf'
Generating '/etc/asterisk/zapata-auto.conf'
Unloading zaptel hardware drivers:
Unloading qozap: [ OK ]
Unloading wctdm: [ OK ]
Removing zaptel module: ERROR: Module zaptel is in use by zttranscode
[FAILED]
Loading zaptel framework: [ OK ]
Waiting for zap to come online: [ OK ]
Loading zaptel hardware modules:
Loading wctdm: [ OK ]
Loading qozap: [ OK ]
Running ztcfg: [ OK ]
SETTING FILE PERMISSIONS
Permissions OK
STARTING ASTERISK
Asterisk ended with exit status 1
Asterisk died with code 1.
Automatically restarting Asterisk.
Asterisk ended with exit status 1
Asterisk died with code 1.
Automatically restarting Asterisk.
mpg123: no process killed
-----------------------------------------------------
Asterisk could not start!
Use 'tail /var/log/asterisk/full' to find out why.
-----------------------------------------------------
Unable to connect to remote asterisk (does /var/run/asterisk/asterisk.ctl exist?)
[root@asterisk1 ~]#
Now after the "genzaptelconf" the whole asterisk is not starting anymore in both modes.
I will reinstall it again until I am on this point again, and wait for your answer.
I'll have it running again in 2 h.
Thanks for your help.
Willy
Willy
Have a look at Junghanns sample configs.
You'll find them under /usr/src/bristuff{version}/
Hy Alan,
Lots of thanks for your help, I can call out and in now via analog and isdn lines.
Great,
Willy
Hi Alan,
I have one ISDN HFC card on my Trixbox 2.2. After installing with your script Asterisk can’t find ISDN card any more. Below I will post install-zaphfc.log :
STARTED: Running /usr/local/sbin/install-ZAPHFC version 1.3.3 (14 June 2007) from /root on Fri Jun 15 20:51:04 EEST 2007
Command line: -M 1
HFC-PCI Chip: 1 port card found (1397:2bd0).
Asterisk: Found 1.2.18 installed.
Asterisk: Building Asterisk 1.2.18
BRIstuff: Patching with bristuff-0.3.0-PRE-1y-g
Shutdown: Asterisk shutdown.
Shutdown: Found zaptel ...Unloading
Shutdown: Found zttranscode ...Unloading
Shutdown: Found zaptel ...Unloading
Trixbox: Applying changes to allow build on Trixbox
Trixbox: Removed rpm asterisk-1.2.18-3
Trixbox: Removed rpm zaptel-1.2.17.1-4
Kernel version: 2.6.9-34.0.2.EL
Kernel directory: 2.6.9-34.0.2.EL-i686
Modules directory: /lib/modules/2.6.9-34.0.2.EL/extra
yum: Running yum to install kernel-devel
Link linux: lrwxrwxrwx 1 root 37 Jun 15 20:57 /usr/src/linux -> /usr/src/kernels/2.6.9-34.0.2.EL-i686
Link linux-2.6: lrwxrwxrwx 1 root 37 Jun 15 20:57 /usr/src/linux-2.6 -> /usr/src/kernels/2.6.9-34.0.2.EL-i686
spinlock.h: File edited.
Bristuff tar: Downloading bristuff-0.3.0-PRE-1y-g.tar.gz
Download: asterisk-1.2.18 downloaded.
Patch: asterisk-1.2.18 patched.
Download: zaptel-1.2.17.1 downloaded.
Patch: zaptel-1.2.17.1 patched.
Download: libpri-1.2.4 downloaded.
Patch: libpri-1.2.4 patched.
Zaptel build: -rw-r--r-- 1 root root 450220 Jun 15 21:09 zaptel.ko
Libpri build: lrwxrwxrwx 1 root root 13 Jun 15 21:10 libpri.so -> libpri.so.1.0
Zaphfc build: -rw-r--r-- 1 root root 133128 Jun 15 21:10 zaphfc.ko
Asterisk build: -rwxr-xr-x 1 root root 5716389 Jun 15 21:14 asterisk
modprobe.conf: Adding zaphfc entry
modprobe.conf: install zaphfc /sbin/modprobe --ignore-install zaphfc modes=0 && /sbin/ztcfg
sysconfig/zaptel: Adding zaphfc entry
sysconfig/zaptel: MODULES="$MODULES zaphfc" # HFC ISDN module
sysconfig/zaptel: #MODULES="$MODULES ztdummy" # UHCI USB Zaptel Timing Only Interface
proc: HFC-S not found in /proc/zaptel/
FINISHED: Running /usr/local/sbin/install-ZAPHFC in /root on Fri Jun 15 21:24:01 EEST 2007
and some errors from installing :
-----------------------------------------------------
Checking Zaptel and unloading zaptel modules
-----------------------------------------------------
/etc/sysconfig/zaptel: line 12: syntax error near unexpected token `)'
/etc/sysconfig/zaptel: line 12: `version)'
Shutdown: Found zaptel ...stopping
ERROR: Module zaptel is in use by zttranscode
Shutdown: Found zttranscode ...stopping
Shutdown: Found zaptel ...stopping
-----------------------------------------------------
Found Trixbox installed.
-----------------------------------------------------
0:revert /dev/tty9 ownership back to root
sed: ck_follow_symlink: couldn't lstat rc.d/rc.local: No such file or directory
-----------------------------------------------------
Building zaphfc in: /usr/src/bristuff-0.3.0-PRE-1y-g/zaphfc
-----------------------------------------------------
rm -f zaphfc.o *.ko *.mod.c *.mod.o .*o.cmd *~
rm -rf .tmp_versions
make -C /usr/src/linux-2.6 SUBDIRS=/usr/src/bristuff-0.3.0-PRE-1y-g/zaphfc ZAP=-I/usr/src/bristuff-0.3.0-PRE-1y-g/zaptel modules
make[1]: Entering directory `/usr/src/kernels/2.6.9-34.0.2.EL-i686'
CC [M] /usr/src/bristuff-0.3.0-PRE-1y-g/zaphfc/zaphfc.o
Building modules, stage 2.
MODPOST
*** Warning: "zt_register" [/usr/src/bristuff-0.3.0-PRE-1y-g/zaphfc/zaphfc.ko] undefined!
*** Warning: "zt_transmit" [/usr/src/bristuff-0.3.0-PRE-1y-g/zaphfc/zaphfc.ko] undefined!
*** Warning: "zt_receive" [/usr/src/bristuff-0.3.0-PRE-1y-g/zaphfc/zaphfc.ko] undefined!
*** Warning: "zt_ec_chunk" [/usr/src/bristuff-0.3.0-PRE-1y-g/zaphfc/zaphfc.ko] undefined!
*** Warning: "zt_unregister" [/usr/src/bristuff-0.3.0-PRE-1y-g/zaphfc/zaphfc.ko] undefined!
CC /usr/src/bristuff-0.3.0-PRE-1y-g/zaphfc/zaphfc.mod.o
LD [M] /usr/src/bristuff-0.3.0-PRE-1y-g/zaphfc/zaphfc.ko
make[1]: Leaving directory `/usr/src/kernels/2.6.9-34.0.2.EL-i686'
-----------------------------------------------------
Setting up zaptel configuration
-----------------------------------------------------
/etc/sysconfig/zaptel: line 12: syntax error near unexpected token `)'
/etc/sysconfig/zaptel: line 12: `version)'
Loading zaptel framework: [60G[ [0;32mOK [0;39m ]
Waiting for zap to come online: [60G[ [0;32mOK [0;39m ]
Loading zaptel hardware modules:
Loading tor2: [60G[ [0;32mOK [0;39m ]
No functioning zap hardware found in /proc/zaptel, loading ztdummypll
Loading ztdummypll: FATAL: Module ztdummypll not found.
[60G[ [0;31mFAILED [0;39m]
Running ztcfg: [60G[ [0;32mOK [0;39m ]
-----------------------------------------------------
Checking contents of /proc/zaptel for HFC-S
-----------------------------------------------------
grep: /proc/zaptel/*: No such file or directory
/usr/local/sbin/install-ZAPHFC: line 1324: [: -gt: unary operator expected
A process for HFC-S was not found in /proc/zaptel/ directory
Try rebooting, then run "cat /proc/zaptel/*" from a console prompt
-----------------------------------------------------
This builds logfile is in /etc/asterisk/install-zaphfc.log
-----------------------------------------------------
Regards,
Georgi
Hi Alan,
Installing this hfc card is now easy with the help of your great script.
I have an other question:
When I go into the CLI, then I see the following comments because I have only one ISDN line installed on this server:
== Primary D-Channel on span 3 down
== Primary D-Channel on span 4 down
== Primary D-Channel on span 5 down
How can I get rid of these D-Channel comments?
Dit there came an answer on the folowing from Medium on Sat, 04/21/2007:
An other thing I have noticed is that Trixbox can't see the status of the Asterisk, after it have been changed with install-ZAPHFC - in the main window of the asterisk server it says unknown, the same in system maint. Before the install-ZAPHFC it was ok, I have tried it out with 3 different machines. But the asterisk server is running and everything works well.
I have the same thing here.
Thank you Alan, and allso all the trixbox people for a great work.
Willy
The build errors are expected and catered for.
It looks like (my guess on a quick look through) is that you edited /etc/sysconfig/zaptel and now it is not read properly. As a result the zaptel service is not starting.
If this is the case fix the file and re-run with the config only switch.
Willy
Do you have a 4 port card? Are the other 3 ports connected to anything? If the answers are yes and no respectively then the messages won't go away.
I'm not sure about the status issue (I don't use TB)
Alan,
can I not un-comment unused ports in the zaptel or/and zapa config-files?
Thanks
Willy
Hi Alan,
All is working now. And I do not get any more remarks like this: == Primary D-Channel on span 3 down - in the CLI After I comeneted out the unused chanels in the: zapata-BRI-HFC.conf..
Reminder: only one port connected to the ISDN grid.
; Basic ISDN Card TE mode config
resetinterval=never
immediate=no
switchtype=euroisdn
signalling=bri_cpe
pridialplan=dynamic
prilocaldialplan=local
nationalprefix=
internationalprefix=
usecallingpres=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=100
context=from-zaptel
group=0
channel => 5-6
;channel => 8-9
;channel => 11-12
;channel => 14-15
Thanks,
Willy
Yes. You can always stop letting Asterisk know about them. :-)
I'm trying to get install-ZAPHFC to configure my card in NT mode. I've tried the switch -m1 (and even -m0 to see if it makes a difference), but the confirm build section always shows "TE mode" as how the card is to be configured.
At present I don't have my ISDN phone plugged into the card. Does that make a difference?
Thanks, PT
This is due to a bug introduced a couple of versions ago caused by the re-ordering a couple of function calls.
I've rolled-back those changes and released a 1.3.3a
If you re-run and run the new version you should find it runs as expected.
Hi Wizz/Alan,
I have modified install-ZAPHFC so that it installs "spandsp" and "rxfax" as well. It seems to be working on our machine but others mileage may vary. Now we can receive faxes clearly -- well the test ones went through ok. It remains to be seen how it holds up when people start using it on Monday :)
If anyone is interested the details on how to use install-ZAPHFC and get spandsp and rxfax working on Trixbox/Asterisk can be found here
Regards
Mark
Mark
What is the process required in addition to install-ZAPHFC?
Would these processes go into a script which allowed these modules to be built for anyone, irrespective if they used install-ZAPHFC or not (or indeed Trixbox or not)?
Fax now works!
Hi Alan
When I login in asterisk gui, admin mode first screen, then the first thing that I see is that "asterisk is not installed" in a big red rectangle, but asterisk is working fine. Before i installed the HFC card with install-ZAPHFC it was still showing asterisk working.
Server Status
Asterisk Not Installed
web server Running
cron server Running
secure shell server Running
Mysql Running
HUD Server Not Installed
The HUD server is not yest installed so it rightly shows not installed.
Do you have an Idee of the reason of this?
Thanks for a great script.
Willy
PS. this is what is installed: Asterisk 1.2.19-BRIstuffed-0.3.0-PRE-1y-h built by root @ asterisk1.local on a i686 running Linux on 2007-06-30 21:03:50 UTC Verbosity is at least 3
As I don't use TB I am guessing, but I think this is reporting that no asterisk rpm is installed. Which would be correct. This is because to build asterisk with HFC BRI support requires asterisk to be built from scratch after which you are no longer using rpm's.
Hi Alan,
The only process required in addition to running the script might be to run "yum install ghostscript". This could be included in your script as well.
Currently the spandsp and rxfax stuff are part of the install-ZAPHFC script but I suppose it won't be hard to remove the HFC specific stuff like downloading/compiling BRIStuff etc and just have the script patch and compile asterisk with spandsp and rxfax support.
If there is some demand for this I could edit the script so it just recompiles asterisk with spandsp and rxfax support and remove the hfc specific stuff.
Regards
Mark
Java application development
Online marketing Specialists
More than just broadband
Mark
My thinking was along the lines... install-ZAPHFC is about getting BRIstuff built. Its not platform or package (e.g. Trixbox) specific.
If your patch can run as a standalone script, irrespective of whether insatll-ZAPHFC had run or not, then this may be a better way to go.
p.m. a diff against the version you patched to me.
Has anyone ever succeeded in using install-ZAPHFC on Asterisk 1.4?
I have been trying to no avail. In order to use libh324m, I must use Asterisk 1.4. I tried Trisbox 2.2.3 and upgrade to Asterisk 1.4, then run install-ZAPHFC but it does not work. After some tweaking I could make HFC-S card recognized and I could run "pri show span 1" command via CLI, but the channel is always down. FYI, with plain Trisbox 2.2.3, install-ZAPHFC worked perfectly, giving me a system that has ISDN BRI connection for both incoming and outgoing (and yes the channel is up). I also tried installing Asterisk on Fedora 6 but could not succeed.
I wonder if the problem is in Florz's patch.At the first post of this thread Alan said Florz's patch only work with Zaptel version 1.2.5 or older, while install-ZAPHFC uses Zaptel version 1.4 when the asterisk is version 1.4.2.
Any idea?
BTW, in order to even finish running install-ZAPHFC on Asterisk 1.4.2, I modified the script by adding "./configure" to Asterisk_Build before make, and changin "if [ -f asterisk ]" to "if [ -f main/asterisk ]".
A few things:
- check/post the build log of the 1.4 build.
rm -f include/asterisk/build.h
Hi Alan,
I tied the folowing:
-To go straight from Trixbox 2.2.3 to * 1.4 you can use the -a switch and specify the version to build, the -l switch will list the version BRIstuff is available for.
I did "install-ZAPHFC -a 1.4.7" and this below is the end op the install
Could you pls coment on this? I might have done something wrong.
I am usinh the latest script.
........
........
rm -f include/asterisk/version.h
make[1]: Entering directory `/usr/src/bristuff-0.4.0-test2/asterisk-1.4.7.1/menuselect'
rm -f menuselect gmenuselect *.o
make[2]: Entering directory `/usr/src/bristuff-0.4.0-test2/asterisk-1.4.7.1/menuselect/mxml'
/bin/rm -f mxmldoc.o testmxml.o mxml-attr.o mxml-entity.o mxml-file.o mxml-index.o mxml-node.o mxml-search.o mxml-set.o mxml-private.o mxml-string.o libmxml.a mxmldoc doc/mxml.3 doc/mxmldoc.1 testmxml mxml.xml
/bin/rm -f mxmldoc-static libmxml.a
/bin/rm -f *.bck *.bak
/bin/rm -f config.cache config.log config.status
/bin/rm -f -r autom4te*.cache
make[2]: Leaving directory `/usr/src/bristuff-0.4.0-test2/asterisk-1.4.7.1/menuselect/mxml'
make[1]: Leaving directory `/usr/src/bristuff-0.4.0-test2/asterisk-1.4.7.1/menuselect'
cp -f .cleancount .lastclean
****
**** The configure script must be executed before running 'make'.
**** Please run "./configure".
****
make: *** [makeopts] Error 1
****
**** The configure script must be executed before running 'make'.
**** Please run "./configure".
****
make: *** [makeopts] Error 1
Asterisk build ***** FAILED: ***** No asterisk file found after build. Termintating script.
[root@asterisk1 ~]#
Thanks for all the work that you are putting in this project.
Willy
Willy
I've just reviewed Junghanns compile scripts for * 1.2 and 1.4 which are different.
I'll look to add an additional step in the 1.4 build process which should be out in an hour-or-so (will be 1.3.7).
{EDIT}1.3.7 is now on-line if you can test this please.
Hi Alan,
I tried again with the following result
I have to tel you that i started with Trixbox 2.2.1
make[1]: Leaving directory `/usr/src/bristuff-0.4.0-test2/asterisk-1.4.7.1/formats'
make[1]: Entering directory `/usr/src/bristuff-0.4.0-test2/asterisk-1.4.7.1/cdr'
for x in cdr_csv.so cdr_custom.so cdr_manager.so; do /usr/bin/install -c -m 755 $x /usr/lib/asterisk/modules ; done
make[1]: Leaving directory `/usr/src/bristuff-0.4.0-test2/asterisk-1.4.7.1/cdr'
make[1]: Entering directory `/usr/src/bristuff-0.4.0-test2/asterisk-1.4.7.1/funcs'
for x in func_base64.so func_callerid.so func_cdr.so func_channel.so func_curl.so func_cut.so func_db.so func_enum.so func_env.so func_global.so func_groupcount.so func_language.so func_logic.so func_math.so func_md5.so func_moh.so func_rand.so func_realtime.so func_sha1.so func_strings.so func_timeout.so func_uri.so; do /usr/bin/install -c -m 755 $x /usr/lib/asterisk/modules ; done
make[1]: Leaving directory `/usr/src/bristuff-0.4.0-test2/asterisk-1.4.7.1/funcs'
make[1]: Entering directory `/usr/src/bristuff-0.4.0-test2/asterisk-1.4.7.1/main'
for x in ; do /usr/bin/install -c -m 755 $x /usr/lib/asterisk/modules ; done
make[1]: Leaving directory `/usr/src/bristuff-0.4.0-test2/asterisk-1.4.7.1/main'
+---- Asterisk Installation Complete -------+
+ +
+ YOU MUST READ THE SECURITY DOCUMENT +
+ +
+ Asterisk has successfully been installed. +
+ If you would like to install the sample +
+ configuration files (overwriting any +
+ existing config files), run: +
+ +
+ make samples +
+ +
+----------------- or ---------------------+
+ +
+ You can go ahead and install the asterisk +
+ program documentation now or later run: +
+ +
+ make progdocs +
+ +
+ **Note** This requires that you have +
+ doxygen installed on your local system +
+-------------------------------------------+
WARNING WARNING WARNING
Your Asterisk modules directory, located at
/usr/lib/asterisk/modules
contains modules that were not installed by this
version of Asterisk. Please ensure that these
modules are compatible with this version before
attempting to run Asterisk.
app_addon_sql_mysql.so
app_callingpres.so
app_curl.so
app_cut.so
app_enumlookup.so
app_eval.so
app_flite.so
app_groupcount.so
app_math.so
app_md5.so
app_saycountpl.so
app_setcidname.so
app_setcidnum.so
app_setrdnis.so
app_txtcidname.so
cdr_addon_mysql.so
chan_features.so
chan_h323.so
format_au.so
format_mp3.so
format_pcm_alaw.so
pbx_functions.so
res_config_mysql.so
WARNING WARNING WARNING
Asterisk build ***** FAILED: ***** No asterisk file found after build. Termintating script.
[root@asterisk1 src]#
Thanks
Willy
Willy
That's OK, in the sense the test is probably looking for the wrong result.
If you would like me to ssh into your system to see what needs to be done then pm me.
Hi all,
I'm trying to get up my first Asterisk sever. The last step is to add ISDN support with a Beronet card.
I'm quite new to the Linux and Asterisk world so I have difficulties to follow and adapt the guide to my specific case (wich is still basic).
The goal is to add support of the Beronet Card to a freshlly installed Trixbox Server. Don't care if it's 2.0 or 2.2. Already tested both and both are fine.
The four port will be used on regular ISDN lines, mainly for inbound call.
My first question is do I need to install ZAPHFC or mISDN or both ?
What is the simpliest way to get it working ??
mISDN require a lot of stuff before get able to install : dependencies, kernel sources, ....
It seems that first launching ZAPHCF then mISDn installation of mISDN run better but i'm not sure it's the best way ?
Except this point, I'm really happy the way my server is comming alive. Thanks to the community for developping and supporting this great Asterisk project.
The authors of BRIstuff, who wrote the zaphfc/qozap drivers, added a test for the Beronet cards (a competitor) such that their code does not run with them.
Most people report that following the install process from the Beronet site works OK.
I've now understand that only installing misdn should do the job. So I digged in this way.
I've readed de Beronet manual but I've not understood everything... My biggest problem is that this guid seems to apply to general Linux and TrixBox come with lot of stuf preinstalled.
I don't want to make a big mix and hope it will finally work.
With final goal to make a tutorial for dummy like me, I written down all the steps I made. The next install from scratch I will add a section with what the machine returns.
It will be fine if an expert can check this, any comment will be appreciate. Specially tips for the following part ;)
# install trixbox 2.2
# run "yum -y update"
# wait for the 32 update to complete
# reboot your system by typing "reboot"
# type this command to check if you use SMP kernel "uname -r | grep -q smp && echo "Please install --smp-- kernel." "
# if it returns "Please install --smp-- kernel." type "yum install kernel-smp-devel -y "
# otherwise type "yum install kernel-devel -y "
# go to the usr folder with "cd /usr/src"
# get the last version of mISDN by entering "wget http://www.beronet.com/downloads/install-misdn-mqueue.tar.gz"
# extract the downloaded files "tar -zxvf install-misdn-mqueue.tar.gz"
# go to the folder "cd install-misdn-mqueue"
# run the installation script "make install"
# run the scan script "misdn-init scan"
# Save this information by running "misdn-init config"
The default settings of the card seems good. protocol 0x2 and laymask 0xf for the four ports.
Actually the installation of mISDN seems ok, it say something like 'installation complete".
But I can get the misdn (start, reload, show config working).
At page 46 of the Beronet installation they talk about an other script
http://www.beronet.com/downloads/install-asterisk.tar.gz1 who will install libpri, zaptel and asterisk. The script fails, so I follow the manual instruction who works well.
But, this replace my version of asterisk with an older who don't support some of the module and then crash when launching "amportal start".
So I wonder if this is usefull ? Do I really need to follow the guide and install a specific version of Asterisk from Beronet ?
Any help will be greatly appreciate.
good night
That sounds good.
But because this thread does not focus on misdn in any way I would suggest you re-post your message as a new thread so people do not get confused between zaphfc/qozap and misdn.
You right, I must not post here. I will not put some more confusion.
I spent my WE on it... I've already posted two other post... (sorry for the flood but, yesterday I became to be little bit nervous...).
You can read my two comment here :
http://www.trixbox.org/forums/trixbox-forums/open-discussion/tale...
and here
http://www.trixbox.org/forums/trixbox-forums/help/trixbox-beronet...
(i will not open a new topic because the last one is exactly the same issue.)
And the last version of my step-by-step guide is online here :
http://www.becyber.be/Thomas/Trixbox_BN4S0_guide_v2.html
Don't have ISDN line on site, I now need it to continue testing... I keep you informed.
Thank again for the reply
Hi Alan,
I've tried install-ZAPHFC and I get the message:
Resolving ftp.digium.com... 216.27.40.102
Connection to ftp.digium.com|216.27.40.102|:21... failed: Connection refused.
Failed to succesfully download asterisk-1.2.23. Exiting script.
Try re-running and using a different mirror (-M command line option)
I've managed to download using
wget http://ftp.digium.com/pub/asterisk/releases/asterisk-1.2.23.tar.g...
As I'm very new with trixbox and * I'm not sure if there is a problem only with my machine or not.
Tnx
BR
Mladen
It might not be your end. I've seen another script I use to keep Asterisk systems automatically up-to-date fail recently. I suspect Digium has disabled/lost their ftp server.
As the prompt suggested you could use another mirror or as a quick work-around change line 1095 to use http rather than ftp.
from: SRCURL[1]="ftp://ftp.digium.com/pub"
to: SRCURL[1]="http://ftp.digium.com/pub"
If this persists I'll change the next version to use http
It works well after chaging as per your instructions.
TNX a lot
Mladen
I had to make a new installation, a few days ago, but both the mirrors fails, what to do now, use mIsdn or is there a third mirror.
The new -M command line switch can be used to select another mirror. Currently there are only two mirror sites defined.
Regard
Medum
a few days ago, but both the mirrors fails,
See the posts immediately above yours.
The new -M command line switch can be used to select another mirror. Currently there are only two mirror sites defined.
I only knew about 2 mirrors when I added this feature. If you know more then let me know and I'll look at adding them.
Changed ftp to http as you had described - I am sorry - i will look more intence next time
now it works !
Regard
Medum

Member Since:
2006-05-31