problems getting openzap compiled for use with freeswitch
I am following the wiki page here http://wiki.freeswitch.org/wiki/OpenZAP#Zaptel_Installation setup is on Ubuntu 9.0.4 using the debian method, when I run module-assistant build zaptel-source the compilation fails as below, not sure what I am missing, reading further FS wiki pages and googling haven't enlightened me, any suggestions? I am trying to get 2x X100P's working dh_testdir dh_testroot rm -f *-stamp # Delete the generated bristuff symlinks: rm -f -f cwain.[ch] qozap.[ch] zaphfc.[ch] ztgsm.[ch] # Add here commands to clean up after the build process. rm -rf modexamples rm -f tonezones.txt rm -f version.h rm -rf debian/fake # * Makefile does not exist when running svn-buildpackage # as the source tree is not there. # FIXME: This will fail with an ugly warning on the clean of the # modules build. However only fter the actuual clean. [ ! -f Makefile ] || /usr/bin/make dist-clean || true make[1]: Entering directory `/usr/src/modules/zaptel' make: Entering an unknown directory make: Leaving an unknown directory rm -f torisatool rm -f fxotune fxstest sethdlc-new ztcfg ztdiag ztmonitor ztspeed zttest ztscan rm -f *.o ztcfg tzdriver sethdlc sethdlc-new rm -f libtonezone.so libtonezone.a *.lo /usr/bin/make -C /usr/src/linux ARCH=i386 SUBDIRS=/usr/src/modules/zaptel/kernel HOTPLUG_FIRMWARE=yes KBUILD_OBJ_M="pciradio.o tor make[2]: Entering directory `/usr/src/linux-headers-2.6.28-11-server' CLEAN /usr/src/modules/zaptel/kernel CLEAN /usr/src/modules/zaptel/kernel/.tmp_versions make[2]: Leaving directory `/usr/src/linux-headers-2.6.28-11-server' make[2]: Entering directory `/usr/src/modules/zaptel/kernel/xpp/utils' rm -f *.o init_fxo_modes print_modes perlcheck zt_registration.8 xpp_sync.8 lszaptel.8 xpp_blink.8 zapconf.8 zaptel_hardware.8 make[2]: Leaving directory `/usr/src/modules/zaptel/kernel/xpp/utils' make: Entering an unknown directory make: Leaving an unknown directory make[1]: Leaving directory `/usr/src/modules/zaptel' #rm -f debian/manpage.links debian/manpage.refs debian/*.8 dh_clean /usr/bin/make -f debian/rules kdist_clean kdist_config binary-modules make[1]: Entering directory `/usr/src/modules/zaptel' dh_testdir dh_testroot rm -f *-stamp # Delete the generated bristuff symlinks: rm -f -f cwain.[ch] qozap.[ch] zaphfc.[ch] ztgsm.[ch] # Add here commands to clean up after the build process. rm -rf modexamples rm -f tonezones.txt rm -f version.h rm -rf debian/fake # * Makefile does not exist when running svn-buildpackage # as the source tree is not there. # FIXME: This will fail with an ugly warning on the clean of the # modules build. However only fter the actuual clean. [ ! -f Makefile ] || /usr/bin/make dist-clean || true make[2]: Entering directory `/usr/src/modules/zaptel' make: Entering an unknown directory make: *** menuselect: No such file or directory. Stop. make: Leaving an unknown directory make[2]: [clean] Error 2 (ignored) rm -f torisatool rm -f fxotune fxstest sethdlc-new ztcfg ztdiag ztmonitor ztspeed zttest ztscan rm -f *.o ztcfg tzdriver sethdlc sethdlc-new rm -f libtonezone.so libtonezone.a *.lo /usr/bin/make -C /usr/src/linux ARCH=i386 SUBDIRS=/usr/src/modules/zaptel/kernel HOTPLUG_FIRMWARE=yes KBUILD_OBJ_M="pciradio.o tor make[3]: Entering directory `/usr/src/linux-headers-2.6.28-11-server' make[3]: Leaving directory `/usr/src/linux-headers-2.6.28-11-server' make[3]: Entering directory `/usr/src/modules/zaptel/kernel/xpp/utils' rm -f *.o init_fxo_modes print_modes perlcheck zt_registration.8 xpp_sync.8 lszaptel.8 xpp_blink.8 zapconf.8 zaptel_hardware.8 make[3]: Leaving directory `/usr/src/modules/zaptel/kernel/xpp/utils' make: Entering an unknown directory make: *** ppp: No such file or directory. Stop. make: Leaving an unknown directory make[2]: *** [clean] Error 2 make[2]: Leaving directory `/usr/src/modules/zaptel' #rm -f debian/manpage.links debian/manpage.refs debian/*.8 dh_clean for templ in ; do \ cp $templ `echo $templ | sed -e 's/_KVERS_/2.6.28-11-server/g'` ; \ done for templ in `ls debian/*.modules.in` ; do \ test -e ${templ%.modules.in}.backup || cp ${templ%.modules.in} ${templ%.modules.in}.backup 2>/dev/null || true; \ sed -e 's/##KVERS##/2.6.28-11-server/g ;s/#KVERS#/2.6.28-11-server/g ; s/_KVERS_/2.6.28-11-server/g ; s/##KDREV##/2.6.28-11.42 done dh_testdir dh_testroot dh_clean -k cp -a /usr/src/modules/zaptel/debian/generated/* . ./configure checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking how to run the C preprocessor... gcc -E checking for a BSD-compatible install... /usr/bin/install -c checking whether ln -s works... yes checking for GNU make... make checking for grep... /bin/grep checking for sh... /bin/bash checking for ln... /bin/ln checking for wget... /usr/bin/wget checking for grep that handles long lines and -e... (cached) /bin/grep checking for egrep... /bin/grep -E checking for ANSI C header files... yes checking for sys/types.h... yes checking for sys/stat.h... yes checking for stdlib.h... yes checking for string.h... yes checking for memory.h... yes checking for strings.h... yes checking for inttypes.h... yes checking for stdint.h... yes checking for unistd.h... yes checking for initscr in -lcurses... yes checking curses.h usability... yes checking curses.h presence... yes checking for curses.h... yes checking for initscr in -lncurses... yes checking for curses.h... (cached) yes checking for newtBell in -lnewt... no checking for usb_init in -lusb... no configure: creating ./config.status config.status: creating build_tools/menuselect-deps config.status: creating makeopts config.status: creating build_tools/make_firmware_object configure: *** Zaptel build successfully configured *** make MODULES_EXTRA="ds1x1f opvxa1200 wcopenpci cwain qozap zaphfc ztgsm" SUBDIRS_EXTRA="vzaphfc oslec" modules KERNEL_SOURCES=/usr make[2]: Entering directory `/usr/src/modules/zaptel' make -C /usr/src/linux ARCH=i386 SUBDIRS=/usr/src/modules/zaptel/kernel HOTPLUG_FIRMWARE=yes KBUILD_OBJ_M="pciradio.o tor2.o toris make[3]: Entering directory `/usr/src/linux-headers-2.6.28-11-server' gcc -o /usr/src/modules/zaptel/kernel/makefw /usr/src/modules/zaptel/kernel/makefw.c /usr/src/modules/zaptel/kernel/makefw /usr/src/modules/zaptel/kernel/pciradio.rbt radfw > /usr/src/modules/zaptel/kernel/radfw.h Loaded 42096 bytes from file CC [M] /usr/src/modules/zaptel/kernel/pciradio.o /usr/src/modules/zaptel/kernel/makefw /usr/src/modules/zaptel/kernel/tormenta2.rbt tor2fw > /usr/src/modules/zaptel/kernel/tor2fw. Loaded 69900 bytes from file CC [M] /usr/src/modules/zaptel/kernel/tor2.o CC [M] /usr/src/modules/zaptel/kernel/torisa.o CC [M] /usr/src/modules/zaptel/kernel/wcfxo.o CC [M] /usr/src/modules/zaptel/kernel/wct1xxp.o CC [M] /usr/src/modules/zaptel/kernel/wctdm.o /usr/src/modules/zaptel/kernel/wctdm.c: In function 'wctdm_proslic_getreg_indirect': /usr/src/modules/zaptel/kernel/wctdm.c:671: warning: format not a string literal and no format arguments CC [M] /usr/src/modules/zaptel/kernel/wcte11xp.o CC [M] /usr/src/modules/zaptel/kernel/wcusb.o CC [M] /usr/src/modules/zaptel/kernel/zaptel-base.o /usr/src/modules/zaptel/kernel/zaptel-base.c: In function 'zt_ppp_xmit': /usr/src/modules/zaptel/kernel/zaptel-base.c:1751: warning: comparison of distinct pointer types lacks a cast /usr/src/modules/zaptel/kernel/zaptel-base.c:1814: warning: comparison of distinct pointer types lacks a cast LD [M] /usr/src/modules/zaptel/kernel/zaptel.o CC [M] /usr/src/modules/zaptel/kernel/ztd-eth.o CC [M] /usr/src/modules/zaptel/kernel/ztd-loc.o CC [M] /usr/src/modules/zaptel/kernel/ztdummy.o /usr/src/modules/zaptel/kernel/ztdummy.c: In function 'ztdummy_hr_int': /usr/src/modules/zaptel/kernel/ztdummy.c:203: error: 'struct hrtimer' has no member named 'expires' make[4]: *** [/usr/src/modules/zaptel/kernel/ztdummy.o] Error 1 make[3]: *** [_module_/usr/src/modules/zaptel/kernel] Error 2 make[3]: Leaving directory `/usr/src/linux-headers-2.6.28-11-server' make[2]: *** [modules] Error 2 make[2]: Leaving directory `/usr/src/modules/zaptel' make[1]: *** [binary-modules] Error 2 make[1]: Leaving directory `/usr/src/modules/zaptel' make: *** [kdist_build] Error 2 -- Harondel J. Sibble Sibble Computer Consulting Creating Solutions for the small and medium business computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice)
Harondel J. Sibble scribbled:
I am following the wiki page here
http://wiki.freeswitch.org/wiki/OpenZAP#Zaptel_Installation ... the compilation fails as below,
Zaptel is old. DAHDI is now the way to go. If you have the headers installed for the kernel you are currently using, try this. 1. http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux... 2. tar -xzf dahdi-linux-complete-current.tar.gz 3. cd dahdi-linux-complete-<whatever> 4. make all 5. make install 6. make config (First time only! Modify config files in /etc/dahdi) If this works, please add a DAHDI section to the wiki. If you want to use a Debian package instead of compiling the latest from scratch, try the dahdi-linux package. -- Russell Mosemann
On 12/29/2009 01:14 PM, Russell Mosemann wrote:
Harondel J. Sibble scribbled:
I am following the wiki page here
http://wiki.freeswitch.org/wiki/OpenZAP#Zaptel_Installation ... the compilation fails as below,
Zaptel is old. DAHDI is now the way to go. If you have the headers installed for the kernel you are currently using, try this.
1. http://downloads.asterisk.org/pub/telephony/dahdi-linux-complete/dahdi-linux... 2. tar -xzf dahdi-linux-complete-current.tar.gz 3. cd dahdi-linux-complete-<whatever> 4. make all 5. make install 6. make config (First time only! Modify config files in /etc/dahdi)
If this works, please add a DAHDI section to the wiki. If you want to use a Debian package instead of compiling the latest from scratch, try the dahdi-linux package.
Or you could ask Tzafrir in #asterisk where the latest and greatest dahdi deb packages are as he is afaik the maintainer. Regards, Patrick
Harondel J. Sibble wrote:
I am trying to get 2x X100P's working
Provided you are aware that a lot of users have problems getting X100xP cards to work on their hardware (either due to some issue with the PCI bus, or the Silicon Labs DAA chips not supporting the POTS line to which they are connected)... here's what I did to compile Dahdi (the new name for Zaptel) from source: 1. Download and unpack the Dahdi tarball 2. make all ; make install ; make config 3. cd /etc/dahdi/ ; vi system.conf: #Per FS wiki: "Tones should be configured in OpenZAP and not in zaptel. FreeSWITCH uses its libteletone for tones generation and detection, and does not rely on zaptel tones configuration. Therefore it does not matter which country zone is configured in zaptel. Make sure that you have loaded your country-specific tones at /etc/openzap/tones.conf" #loadzone = fr #defaultzone = fr fxsks=1 4. vi modules; add "wctdm" 5. /etc/init.d/dahdi start 6. lsmod to check loaded modules 7. dahdi_cfg -vvv ; dahdi_scan ; dahdi_test -v 8. ls -la /proc/dahdi/ ; cat /proc/dahdi/1 The next step, which I haven't done yet, is compiling OpenZap so it talks to Dahdi/Zaptel, which talks to the actual hardware. -- View this message in context: http://old.nabble.com/problems-getting-openzap-compiled-for-use-with-freeswi... Sent from the Freeswitch-users mailing list archive at Nabble.com.
On 30 Dec 2009 at 4:18, Fred-145 wrote:
Provided you are aware that a lot of users have problems getting X100xP cards to work on their hardware (either due to some issue with the PCI bus, or the Silicon Labs DAA chips not supporting the POTS line to which they are connected)... here's what I did to compile Dahdi (the new name for Zaptel) from source:
Not an issue in this machine, the 2 cards worked fine with asterisk now and dahdi previously.
The next step, which I haven't done yet, is compiling OpenZap so it talks to Dahdi/Zaptel, which talks to the actual hardware.
I'd love to hear your feedback on that when you do. I'm hoping to get this up and running this weekend, but currently more committed to getting zrtp working with the tivi client on my windows mobile phone. It's giving a registration forbidden message, but I don't see anything on the fs_cli to indicate it's even connected :-( -- Harondel J. Sibble Sibble Computer Consulting Creating Solutions for the small and medium business computer user. help@pdscc.com (use pgp keyid 0x3AD5C11D) http://www.pdscc.com (604) 739-3709 (voice)
participants (4)
-
Fred-145
-
Harondel J. Sibble
-
Patrick
-
Russell Mosemann