Does anyone know how to get "genzaptelconf" to actually detect a Digium card with Thirdlane's ISO. I ran the command (as root) and it doesn't seem to do anything. I had an existing Thirdlane system and inserted a new PSTN card but the ports will not activate. By the way, "service zaptel start" starts Zaptel normally.
I will reinstall with the ISO to see if the card is detected by the system but I want to make sure that I can swap out cards in the future and have the system easily detect the new card.
Thanks,
Trey
Error compiling Zaptel Genzaptelconf
make
make[1]: Entering directory `/usr/src/zaptel-1.4.9.2'
You do not appear to have the sources for the 2.6.9-67.0.15.EL kernel installed.
make[1]: *** [modules] Error 1
make[1]: Leaving directory `/usr/src/zaptel-1.4.9.2'
make: *** [all] Error 2
thats a problem with your OS
thats a problem with your OS and running kernel, not a problem with thirdlane, asterisk, or even zaptel.
You need to install the
You need to install the -devel package for the kernel.
yum install kernel-devel (or kernel-PAE-devel, depending which kernel you're using).
Genzaptelconf
Everything Ok, but here:
[root@thirdlane zaptel-1.4.9.2]# service zaptel start
Loading zaptel framework: FATAL: Module zaptel not found.
[FAILED]
Waiting for zap to come online...Error: missing /dev/zap!
[root@thirdlane zaptel-1.4.9.2]# genzaptelconf
Notice: Configuration file is /etc/zaptel.conf
line 0: Unable to open master device '/dev/zap/ctl'
1 error(s) detected
I think this is useless
Thanks!!
Franklin
Genzaptelconf
Erick, I have a question for you.
I downloaded the thirdlane ISO PBX.
Why do I have to reinstall zaptel, kernel, etc?, I think this must be include and updated in the ISO.
I did everything you told me, but any result.
What do I have to do?
Help!!!
Genzaptelconf
Are you telling me thirdlane uses dadhi and not zaptel?
We are buying this product, so is important to me to know if is as good as others.
Please refer a sopport if you can do it.
Regards!!
you're buying the PBX
you're buying the PBX manager webmin module. The .iso is a matter of convenience (or inconvenience depending on your needs). Personally I never use the .iso for a litany of reasons. I install the OS, Install webmin, compile/install dahdi/asterisk, load the webmin module etc. Whether you choose to use the .iso has no real impact on the product itself (the management module). The module works with both zaptel and dahdi drivers. If you are building everything yourself you _may_ have some choice in which driver you are using (depending on which version of asterisk you install). Asterisk 1.2.x is zaptel only. Asterisk 1.4.0 through 1.4.21 uses zaptel only, Asterisk 1.4.22+ can use zaptel or dahdi, Asterisk 1.6.x is dahdi only.
Genzaptelconf
Thank you Erick, I will follow your recommendations later, but now I have a hurry.
I did this and its ok:
1.- ./install_prereq test
2.-./install_prereq install
3.- yum install gcc newt-devel libusb-devel
4.- yum install kernel kernel-devel
5.- reboot
./configure
# optional step: select custom configuration:
#make menuconfig
make
make install
# To install init scripts and config files:
#make config
#service zaptel start
#genzaptelconf
#reboot
IT'S CONFIGURE!!!
Regards!!!
Genzaptelconf
Erick, why asterisk do not see the channels after compiling zaptel
thirdlane*CLI> zap show channels
Chan Extension Context Language MOH Interpret
pseudo default en default
thirdlane*CLI>
remember I installed from ISO.
Thanks!!!
Zaptel modules
After compile I edit this file
/etc/sysconfig/zaptel
that has this
# TE410P - Quad Span T1/E1 Card (3.3v version)
#wct4xxp_ARGS="t1e1override=15" # Additional parameters for TE4xxP driver
# or use /etc/modprobe.d/zaptel or /etc/modprobe.conf .
#MODULES="$MODULES wcte12xp" # TE120P - Single Span T1/E1 Card
#MODULES="$MODULES wct1xxp" # T100P - Single Span T1 Card
# E100P - Single Span E1 Card
#MODULES="$MODULES wcte11xp" # TE110P - Single Span T1/E1 Card
#MODULES="$MODULES wctdm24xxp" # TDM2400P - Modular FXS/FXO interface (1-24 ports)
#MODULES="$MODULES wcfxo" # X100P - Single port FXO interface
# X101P - Single port FXO interface
MODULES="$MODULES wctdm" # TDM400P - Modular FXS/FXO interface (1-4 ports)
#MODULES="$MODULES wcusb" # S100U - Single port FXS USB Interface
#MODULES="$MODULES torisa" # Old Tormenta1 ISA Card
MODULES="$MODULES ztdummy" # Zaptel Timing Only Interface
#MODULES="$MODULES xpp_usb" # Xorcom Astribank Device
# Disables Astribank hotplug firmware loading
#XPP_HOTPLUG_DISABLED=yes
#
# Disables Astribank udev hook called when an astribank is added and ready
# or removed.
#ASTRIBANK_HOOK_DISABLED=yes
#
# Setup the configuration for the PRI module of the Astribank.
# Default: all E1,TE . See xpp/README.Astribank .
#XPP_PRI_SETUP='NUM/*/XPD-01=NT,E1'
# Extensions genzaptelconf are (base + channel_number)
# base is by default 6000:
#base_exten=6000
#
# There are a host of other variables you can set to affect
# genzaptelconf. See the beginning of the script.
Genzaptelconf
for you info
this my 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: ZTDUMMY/1 "ZTDUMMY/1 (source: Linux26) 1" (MASTER)
# Span 2: WCTDM/0 "Wildcard TDM400P REV I Board 1"
fxsks=1
fxsks=2
fxols=4
# Global data
loadzone = us
defaultzone = us
this my zapata-cannels.conf
; Autogenerated by /usr/local/sbin/genzaptelconf -- do not hand edit
; Zaptel Channels Configurations (zapata.conf)
;
; This is not intended to be a complete zapata.conf. Rather, it is intended
; to be #include-d by /etc/zapata.conf that will include the global settings
;
; Span 1: ZTDUMMY/1 "ZTDUMMY/1 (source: Linux26) 1" (MASTER)
; Span 2: WCTDM/0 "Wildcard TDM400P REV I Board 1"
;;; line="1 WCTDM/0/0"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 1
context=default
;;; line="2 WCTDM/0/1"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-pstn
channel => 2
context=default
;;; line="4 WCTDM/0/3"
signalling=fxo_ls
callerid="Channel 4" <6004>
mailbox=6004
group=5
context=from-internal
channel => 4
callerid=
mailbox=
group=
context=default
and this is zap.conf
[g0]
qualify=no
nat=no
context=from-outside
type=friend
;=description=PSTN
also do you intend to treat
also do you intend to treat the 2 lines as seperate trunks? or do you want to group them when dialing out?
Genzaptelconf
[root@thirdlane ~]# lsmod | grep zap
zaptel 200452 4 ztdummy,wctdm
crc_ccitt 2241 1 zaptel
[root@thirdlane ~]# cat /proc/zaptel/1
Span 1: WCTDM/0 "Wildcard TDM400P REV I Board 1" (MASTER)
1 WCTDM/0/0 FXSKS
2 WCTDM/0/1 FXSKS
3 WCTDM/0/2
4 WCTDM/0/3 FXOLS
I do not understand what's going on.
also, btw, comment out
also, btw, comment out ztdummy from your /etc/sysconfig file. It is not needed, your TDM400P has a timing device in it much more accurate than the RTC used by ztdummy.
Genzaptelconf
thirdlane*CLI> zap show channels
Chan Extension Context Language MOH Interpret
pseudo default default
Erick forgive my insistence, but what is next step?
I did everything you told me but no results.
Thanks!!!
Genzaptelconf
[root@thirdlane ~]# asterisk -rvvvvvvvvvvvvvvvvvvvv
Asterisk 1.4.18, Copyright (C) 1999 - 2008 Digium, Inc. and others.
Created by Mark Spencer
Asterisk comes with ABSOLUTELY NO WARRANTY; type 'core show warranty' for details.
This is free software, with components licensed under the GNU General Public
License version 2 and other licenses; you are welcome to redistribute it under
certain conditions. Type 'core show license' for details.
=========================================================================
-- Parsing '/etc/asterisk/asterisk.conf': Found
-- Parsing '/etc/asterisk/extconfig.conf': Found
Connected to Asterisk 1.4.18 currently running on thirdlane (pid = 3722)
Verbosity is at least 20
thirdlane*CLI>
This version is in .iso download from thirdlane page
get rid of the #include
get rid of the #include statements in zapata.conf and just put these in after all the general section definitions..
signalling=fxs_ks
callerid=asreceived
group=1
context=from-outside
channel => 1,2
context=default
signalling=fxo_ls
callerid="Channel 4"<6004>
mailbox=6004
group=5
context=from-inside
channel => 4
Genzaptelconf
I think this my problem, wctdm is sharing interrupts with libata
[root@thirdlane ~]# cat /proc/interrupts
CPU0
0: 146864 XT-PIC timer
1: 8 XT-PIC i8042
2: 0 XT-PIC cascade
5: 0 XT-PIC libata
7: 51 XT-PIC ehci_hcd, ohci_hcd
8: 1 XT-PIC rtc
10: 87339 XT-PIC libata, wctdm
11: 0 XT-PIC libata
12: 21 XT-PIC i8042
14: 458 XT-PIC ide0
65: 428 PCI-MSI eth0
NMI: 0
LOC: 146811
ERR: 0
MIS: 0
interrupt sharing will cause
interrupt sharing will cause audio problems but it would still be visible to asterisk. Perform the task i suggested on the 03/19/2009 - 13:40 thread.
this is a single processor single core no hyperthreading machine? Is this the centos 4.x based OS? Load the SMP kernel even though its not an smp processor, that will get you access to the APIC which will prevent interrupt sharing.
Genzaptelconf
It's visible to zapata, but asterisk do not see any channel, this a a ISO. image downloaded from thirdlane page. Your thread is 03/19/2009 - 13:40 or 03/19/2009 - 18:40? Anyway asterisk did no see the channels. Now we are trying with debian and asterisk 1.4.x
Yes, mi OS was centos 4.x in this machine:
ProLiant ML115 dual-core AMD Opteron 1000 series and single-core Athlon processors
We tried everything with not result in this hardware and the .iso.
Regards!!!
zapata.conf is not zaptel.
zapata.conf is not zaptel. zapata is part of the asterisk configs. Get rid of all those extra zap file crap in /etc/asterisk and just put the configuration manually into /etc/asterisk/zapata.conf like i keep suggesting. The reason asterisk isnt seeing your hardware is because its not LOADING a configuration file declaring channels and signalling.
Also if you dont want interrupt sharing you need to install the smp kernels and use those. The non smp kernels do not give you APIC support.
Genzaptelconf
Sorry Erik, I did mean zaptel.
Thank you four your help. I say again I did everything with no result. Someday I have to finish with this, I understood all you told me and I appreciate.
Regards!!!
compile zaptel
./configure
make menuselect
make
make config
service zaptel start
genzaptelconf
that should do it. The modules have to be loaded in order for genzaptelconf to work. The initial zaptel start will load ALL the modules as defined in '/etc/sysconfig/zaptel'. You will want to go back later and comment out every driver besides the one you need.