Zaptel Madness

[dad311]

Ive came to the end of my troubleshooting and need some fresh ideas.

Last week, I had a Zapmicro card that stopped providing dial tone, The card would answer calls (via fxs), but no dial tone (via fxo). I rebooted the machine and then no dial tone AND now not answering calls.

Best guess was that the Zapmicro card went bad. I replaced the Zapmicro (without a fxo module) but the machine will still not answer a call.

FYI, also found the power supply was overheating due to seized fan.

At this point Im starting to think I have two bad Zapmicro cards, but I have a hard time believing both cards are bad with the exact same issue.

Ive also noticed that no Zap commands are available in the Asterisk CLI, but the status panel shows Zaptel is running.

Asterisk log files show no activity went the fxs is ringing.

Also, if the fxo module is install, during boot up I see messages stating 0 volts detected on fxo module. Maybe a bad module???

Details...............

* Asterisk Source Version : 1.4.21.2
* Zaptel Source Version : 1.4.12.1
* Libpri Source Version : 1.4.7
* Addons Source Version : 1.4.7


Output of ztcfg:
root@pbx:~ $ ztcfg -vvv

Zaptel Version: 1.4.12.1
Echo Canceller: MG2
Configuration
======================


Channel map:

Channel 01: FXS Kewlstart (Default) (Slaves: 01)
Channel 02: FXS Kewlstart (Default) (Slaves: 02)
Channel 03: FXS Kewlstart (Default) (Slaves: 03)
Channel 04: FXS Kewlstart (Default) (Slaves: 04)

4 channels to configure.


Zaptel * ONLINE

 

[jmullinix]

After you changed the cards, did you run dahdi_genconf?

 

[darmock]

Actually you mean genzaptelconf right?


Tom

 

[dad311]

Yes, I have ran getzaptelconf -v several times.

 

[dad311]

Progress, I believe something is hosed with the original 2 yr old load. I just loaded PBXiaf Purple (Asterisk 1.8) and now my Zapmicro is answering.

Still no dial tone from my fxo module, but I believe thats just a bad module.

 

[blanchae]

Now that you are using Purple, you can say good-bye to zap, you are using dahdi now. Go over to this thread and follow the instructions to run the dahdi_report script and post the output called dahdi-information.txt here.

 

[dad311]

The fxs module has a small burn mark. I'm assuming one of the many storms we got last week killed the module. However, I'm still wondering why Zaptel software got hosed. Oh well, the PBX needed upgraded anyway. Moving on......


Power supply fan was locked up. I pulled the sticker and plug off the fan and put two drops of Harley-Davidson clutch oil inside. Fan is now working and very quite. Should work for 10k miles. LOL

Fxo module is fried, going to use old linksys pap2 adapter instead.

Final repair cost $0, Mom will be happy!

 

[Linetux]

Zaptel didn't get hosed. It didn't load because it didn't have anything to talk to.

 

[dad311]

Zaptel didn't get hosed. It didn't load because it didn't have anything to talk to.

I had 1 fxo and 2 fxs modules, none worked. I pulled the bad fxo, re-ran the genzaptelconf setup and fxs modules still would not work.