<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.0.10">
</HEAD>
<BODY>
Hi all,<BR>
<BR>
Does somebody know why no load modules to FXS? I used zaptel-1.0.7 version driver. <BR>
<BR>
[root@server1 zaptel-1.0.7]#<B> modprobe wctdm</B><BR>
ZT_CHANCONFIG failed on channel 3: Invalid argument (22)<BR>
Did you forget that FXS interfaces are configured with FXO signalling<BR>
and that FXO interfaces use FXS signalling?<BR>
<B>/lib/modules/2.4.21-27.EL/misc/wcfxs.o: post-install wcfxs failed<BR>
/lib/modules/2.4.21-27.EL/misc/wcfxs.o: insmod wctdm failed</B><BR>
You have new mail in /var/spool/mail/root<BR>
<BR>
<BR>
<B>/var/log/messages:</B><BR>
#######################<BR>
Jun 21 19:06:15 darthvaden kernel: Zapata Telephony Interface Registered on major 196<BR>
Jun 21 19:06:16 darthvaden kernel: PCI: Found IRQ 9 for device 02:09.0<BR>
Jun 21 19:06:16 darthvaden kernel: PCI: Sharing IRQ 9 with 00:1f.5<BR>
Jun 21 19:06:16 darthvaden kernel: Freshmaker version: 71<BR>
Jun 21 19:06:16 darthvaden kernel: Freshmaker passed register test<BR>
<B>Jun 21 19:06:16 darthvaden kernel: ProSLIC 3210 version 2 is too old<BR>
Jun 21 19:06:16 darthvaden kernel: Module 0: Not installed<BR>
Jun 21 19:06:16 darthvaden kernel: ProSLIC 3210 version 2 is too old<BR>
Jun 21 19:06:16 darthvaden kernel: Module 1: Not installed</B><BR>
Jun 21 19:06:16 darthvaden kernel: Module 2: Installed -- AUTO FXO (FCC mode)<BR>
Jun 21 19:06:16 darthvaden kernel: Module 3: Installed -- AUTO FXO (FCC mode)<BR>
Jun 21 19:06:16 darthvaden kernel: Found a Wildcard TDM: Wildcard TDM400P REV E/F (4 modules)<BR>
############################<BR>
<BR>
<B><TT>It's TDM22B device.</B><BR>
-> <BR>
<A HREF="http://www.digium.com/index.php?menu=product_detail&category=hardware&product=TDM400P&tab=details"><U>http://www.digium.com/index.php?menu=product_detail&category=hardware&product=TDM400P&tab=details</U></A> <BR>
<BR>
<BR>
<B>See below zaptel.conf: </B><BR>
<BR>
# <BR>
# Zaptel Configuration File <BR>
# <BR>
# This file is parsed by the Zaptel Configurator, ztcfg <BR>
# <BR>
# <BR>
# First come the span definitions, in the format <BR>
# span=<span num>,<timing>,<line build out <BR>
(LBO)>,<framing>,<coding>[,yellow] <BR>
# <BR>
# The timing parameter determines the selection of primary, secondary, and <BR>
# so on sync sources. If this span should be considered a primary sync <BR>
# source, then give it a value of "1". For a secondary, use "2", and so on. <BR>
# To not use this as a sync source, just use "0" <BR>
# <BR>
# The line build-out (or LBO) is an integer, from the following table: <BR>
# 0: 0 db (CSU) / 0-133 feet (DSX-1) <BR>
# 1: 133-266 feet (DSX-1) <BR>
# 2: 266-399 feet (DSX-1) <BR>
# 3: 399-533 feet (DSX-1) <BR>
# 4: 533-655 feet (DSX-1) <BR>
# 5: -7.5db (CSU) <BR>
# 6: -15db (CSU) <BR>
# 7: -22.5db (CSU) <BR>
# <BR>
# The framing is one of "d4" or "esf" for T1 or "cas" or "ccs" for E1 <BR>
# <BR>
# Note: "d4" could be referred to as "sf" or "superframe" <BR>
# <BR>
# The coding is one of "ami" or "b8zs" for T1 or "ami" or "hdb3" for E1 <BR>
# <BR>
# E1's may have the additional keyword "crc4" to enable CRC4 checking <BR>
# <BR>
# If the keyword "yellow" follows, yellow alarm is transmitted when no <BR>
# channels are open. <BR>
# <BR>
#span=1,0,0,esf,b8zs <BR>
#span=2,1,0,esf,b8zs <BR>
#span=3,0,0,ccs,hdb3,crc4 <BR>
# <BR>
# Next come the dynamic span definitions, in the form: <BR>
# dynamic=<driver>,<address>,<numchans>,<timing> <BR>
# <BR>
# Where <driver> is the name of the driver (e.g. eth), <address> is the <BR>
# driver specific address (like a MAC for eth), <numchans> is the number <BR>
# of channels, and <timing> is a timing priority, like for a normal span. <BR>
# use "0" to not use this as a timing source, or prioritize them as <BR>
# primary, secondard, etc. Note that you MUST have a REAL zaptel device <BR>
# if you are not using external timing. <BR>
# <BR>
# dynamic=eth,eth0/00:02:b3:35:43:9c,24,0 <BR>
# <BR>
# Next come the definitions for using the channels. The format is: <BR>
# <device>=<channel list> <BR>
# <BR>
# Valid devices are: <BR>
# <BR>
# "e&m" : Channel(s) are signalled using E&M signalling (specific <BR>
# implementation, such as Immediate, Wink, or Feature Group D <BR>
# are handled by the userspace library). <BR>
# "fxsls" : Channel(s) are signalled using FXS Loopstart protocol. <BR>
# "fxsgs" : Channel(s) are signalled using FXS Groundstart protocol. <BR>
# "fxsks" : Channel(s) are signalled using FXS Koolstart protocol. <BR>
# "fxols" : Channel(s) are signalled using FXO Loopstart protocol. <BR>
# "fxogs" : Channel(s) are signalled using FXO Groundstart protocol. <BR>
# "fxoks" : Channel(s) are signalled using FXO Koolstart protocol. <BR>
# "sf" : Channel(s) are signalled using in-band single freq tone. <BR>
# Syntax as follows: <BR>
# channel# => sf:<rxfreq>,<rxbw>,<rxflag>,<txfreq>,<txlevel>,<txflag> <BR>
# rxfreq is rx tone freq in hz, rxbw is rx notch (and decode) <BR>
# bandwith in hz (typically 10.0), rxflag is either 'normal' or <BR>
# 'inverted', txfreq is tx tone freq in hz, txlevel is tx tone <BR>
# level in dbm, txflag is either 'normal' or 'inverted'. Set <BR>
# rxfreq or txfreq to 0.0 if that tone is not desired. <BR>
# "unused" : No signalling is performed, each channel in the list remains <BR>
idle <BR>
# "clear" : Channel(s) are bundled into a single span. No conversion or <BR>
# signalling is performed, and raw data is available on the <BR>
master. <BR>
# "indclear": Like "clear" except all channels are treated individually and <BR>
# are not bundled. "bchan" is an alias for this. <BR>
# "rawhdlc" : The zaptel driver performs HDLC encoding and decoding on the <BR>
# bundle, and the resulting data is communicated via the master <BR>
# device. <BR>
# "fcshdlc" : The zapdel driver performs HDLC encoding and decoding on the <BR>
# bundle and also performs incoming and outgoing FCS insertion <BR>
# and verification. "dchan" is an alias for this. <BR>
# "nethdlc" : The zaptel driver bundles the channels together into an <BR>
# hdlc network device, which in turn can be configured with <BR>
# sethdlc (available separately). <BR>
# "dacs" : The zaptel driver cross connects the channels starting at <BR>
# the channel number listed at the end, after a colon <BR>
# "dacsrbs" : The zaptel driver cross connects the channels starting at <BR>
# the channel number listed at the end, after a colon and <BR>
# also performs the DACSing of RBS bits <BR>
# <BR>
# The channel list is a comma-separated list of channels or ranges, for <BR>
# example: <BR>
# <BR>
# 1,3,5 (channels one, three, and five) <BR>
# 16-23, 29 (channels 16 through 23, as well as channel 29 <BR>
# <BR>
# So, some complete examples are: <BR>
# e&m=1-12 <BR>
# nethdlc=13-24 <BR>
# fxsls=25,26,27,28 <BR>
# fxols=29-32 <BR>
# <BR>
fxsks=1,2 <BR>
fxoks=3,4 <BR>
#bchan=25-47 <BR>
#dchan=48 <BR>
#fxols=1-12 <BR>
#fxols=13-24 <BR>
#e&m=25-29 <BR>
#nethdlc=30-33 <BR>
#clear=44 <BR>
#clear=45 <BR>
#clear=46 <BR>
#clear=47 <BR>
#fcshdlc=48 <BR>
#dacs=1-24:48 <BR>
#dacsrbs=1-24:48 <BR>
# <BR>
# Finally, you can preload some tone zones, to prevent them from getting <BR>
# overwritten by other users (if you allow non-root users to open /dev/zap/* <BR>
# interfaces anyway. Also this means they won't have to be loaded at <BR>
runtime. <BR>
# The format is "loadzone=<zone>" where the zone is a two letter country <BR>
code. <BR>
# <BR>
# You may also specify a default zone with "defaultzone=<zone>" where zone <BR>
# is a two letter country code. <BR>
# <BR>
# An up-to-date list of the zones can be found in the file zaptel/zonedata.c <BR>
# <BR>
# Make sure that the FXS(green) modules are closest to the bracket if you <BR>
are looking at the side of the card with all of t#e electronic components. <BR>
<BR>
loadzone = us <BR>
#loadzone = us-old <BR>
#loadzone=gr <BR>
#loadzone=it <BR>
#loadzone=fr <BR>
#loadzone=de <BR>
#loadzone=uk <BR>
#loadzone=fi <BR>
#loadzone=jp <BR>
#loadzone=sp <BR>
#loadzone=no <BR>
defaultzone=us <BR>
<BR>
Can you help me? <BR>
<BR>
Greetings, <BR>
Alessandro </TT>
</BODY>
</HTML>