FXO woes

Ended up changing PCI slots and rebuilding the box with a new distro of Asterix based on FC5… but not until I and our Asterisk supplier had spent many a moment scratching our heads…


That is interesting. Could you please post the relevant parts of your Zaptel.conf, zapata.conf & extensions.conf. Thank you. John t

Sure John,

zaptel.conf (full listing, cut and pasted verbatim):

Autogenerated by /usr/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 I Board 1”

channel 1, WCTDM, no module.

channel 2, WCTDM, no module.

channel 3, WCTDM, no module.


Global data

loadzone = us
defaultzone = us

zapata.conf (abbreviated listing):


channel => 4

ztcfg -vvv -d 8

Line 14: fxsks=4
Line 18: loadzone = us
Line 19: defaultzone = us

Zaptel Version: 1.4.6
Echo Canceller: MG2

Channel map:

Channel 04: FXS Kewlstart (Default) (Slaves: 04)

1 channels to configure.


Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.4.6
Zaptel Echo Canceller: MG2
ACPI: PCI Interrupt 0000:02:09.0[A] -> GSI 18 (level, low) -> IRQ 201
Freshmaker version: 73
Freshmaker passed register test
Module 0: Not installed
Module 1: Not installed
Module 2: Not installed
Module 3: Installed – AUTO FXO (FCC mode)
Found a Wildcard TDM: Wildcard TDM400P REV I (1 modules)
Registered tone zone 0 (United States / North America)
Registered tone zone 0 (United States / North America)
Zaptel Transcoder support loaded
Registered tone zone 0 (United States / North America)

Asterisk 1.4.4
Zaptel 1.4.6
CentOS 4.5 with Linux kernel 2.6.9-55.0.12.EL
gcc 3.4.6


Forgot my extensions.conf listing. This is largely the default from the install.

extensions.conf (abbreviated listing):


CONSOLE=Console/dsp ; Console interface for demo
IAXINFO=guest ; IAXtel username/password
TRUNK=Zap/g1 ; Trunk interface
TRUNKMSD=1 ; MSD digits to strip (usually 1 or 0)


; Lou testing
exten => s,1,Answer( )
exten => s,2,Background(dir-intro-fn)

exten => 611,1,Answer( )
exten => 611,2,Echo( )

exten => 1111,1,Dial(SIP/lou,20,rt)
exten => 1111,2,VoiceMail,u1111
exten => 1111,102,VoiceMail,b1111

exten => 2222,1,Dial(SIP/test,20,rt)
exten => 2222,2,VoiceMail,u2222
exten => 2222,102,VoiceMail,b2222

exten => 1001,1,Ringing
exten => 1001,2,Wait(2)
exten => 1001,3,VoicemailMain

; Lou note: number below changed for internet post but, dials real external number correctly.
exten => 4444,1,Dial(Zap/g1/1231234)
exten => 4444,2,Hangup()



That is a wild bug.

When a diagnostic tools tell you something is bust, it really doesn’t occur to me to test the device to see if it is working! I’ll have to do that from now on.

What inspired you?

I’ll need to dig into this later in the week.

Thank you:

John T

Oh, yes, on the subject of weird troubleshooting:The good people from X100P.com did get back to me. I had not included all of the lsmod output and they wanted to see it. The modules had loaded, but, fair enough, they could not see it.

But get this: Their suggestion was that I change channel => 1 in zapata.conf to channel=>1. They thought that the white spaces might be bad. In every example of the zapata.conf file that I have seen in a book or on the Web, including their site, the ‘=>’ always has spaces on either side. Oddly, it did not fix the problem. . .

Re: “That is a wild bug…What inspired you?”

It’s the story of my life in tech. It there is a weird bug, it always seems to find me.

Somewhere in the middle of the night between an strace listing and an Ohm meter reading it hit me that it had to work. I think the first time I tested it and it failed was due to the RJ-12 not “clicking” (a very tight fit on my setup) and that created a bit more delay in finding a solution.

Funny about the spaces. I tried that too during my earlier testing. With and without the ‘>’ too but, of course, that was not the issue.

Believe nothing that’s in software and only half of what’s been soldered. :slight_smile:

Good luck with your card.