keywords: ip pbx voip gateway gsm gateway

×

Notice

The forum is in read only mode.
× Questions about A400/800/1200 Analog Interface Card

Card not reporting incoming call

16 years 3 months ago #655 by [email protected]
Hello

I plugged an A400P card with a single FXO module on it into a PC. The FXO module was moved from 1 to 4 (or 0 to 3) because the connector went undone on the original port 1. I'll solder it back on if this is the reason for the problem.

The card is detected OK by Linux CentOS 5.1, and lspci -v, but when I call in from another phone, the call is not reported in the Asterisk console. I tried the card in another PC, same result. I plugged the phone cord into an analog handset, and I can hear the dialtone.

What can be the cause of the OpenVox card not detecting a call?

Thank you.

Here's some outputs:

============= # dmesg
eth0: VIA Rhine II at 0xdfffff00, 00:50:ba:26:f7:81, IRQ 9.
eth0: MII PHY found at address 8, status 0x782d advertising 01e1 Link 45e1.
Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.4.7
Zaptel Echo Canceller: MG2
ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
Freshmaker version: 71
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 E/F (1 modules)
ACPI: PCI Interrupt Link [LNKC] enabled at IRQ 10
PCI: setting IRQ 10 as level-triggered
ACPI: PCI Interrupt 0000:00:07.5[C] -> Link [LNKC] -> GSI 10 (level, low) -> IRQ 10
[...]
Wildcard USB FXS Interface driver registered
Registered tone zone 2 (France)

============= # lspci -v
00:0f.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
Subsystem: Unknown device b100:0001
Flags: bus master, medium devsel, latency 64, IRQ 12
I/O ports at c400
Memory at dfffe000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2

============= # vi /etc/zaptel.conf:
fxsks=4
loadzone=fr
defaultzone=fr

============= # ztcfg -vvv

Zaptel Version: 1.4.7
Echo Canceller: MG2
Configuration

Channel map:

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

1 channels to configure.

Changing signalling on channel 3 from Unused to FXS Kewlstart

============= # cat zapata.conf
[channels]
language=fr
context=my-phones
usecallerid=yes
hidecallerid=no
immediate=no

signalling=fxs_ks
echocancel=yes
echocancelwhenbridged=yes
channel=3

============= # zttool

Zaptel Tool (C)2002 Linux Support Services, Inc.
âââââââââââââ⤠Wildcard TDM400P REV E/F Board 1 ââââââââââââââ
âââââââ â ââââââ
â â â â
â â Current Alarms: No alarms. â â
â â Sync Source: Internally clocked â â â
â â IRQ Misses: 0 â â® â
â â Bipolar Viol: 0 â â â
â â Tx/Rx Levels: 0/ 0 â â â
â â Total/Conf/Act: 4/ 2/ 0 â â â
â â ââââââââ â â â
â â 1234 â Back â â â â
â â TxA - - ââââââââ â â â
â â TxB - - â â® â
â â TxC - - â â â
â â TxD - - â â
â â ââââââââ â â
â â RxA - - â Loop â â â
â â RxB - - ââââââââ â â
â â RxC - - â â
â â RxD - - â â
âââââââ â âââââ
ââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââââ
Wildcard TDM400P REV E/F Board 1

============= # /etc/rc.d/init.d/asterisk restart
Shutting down asterisk: [ OK ]
Starting asterisk: [ OK ]

============= # asterisk -vvvvvvvvvvr

=> Asterisk doesn't show incoming call. So, went back to using channel "1" for zaptel.conf and zapata.conf:

============= # vi /etc/zaptel.conf:
fxsks=1
loadzone=fr
defaultzone=fr

============= # vi /etc/asterisk/zapata.conf
[channels]
language=fr
context=my-phones
usecallerid=yes
hidecallerid=no
immediate=no

signalling=fxs_ks
echocancel=yes
echocancelwhenbridged=yes
channel=1

============= # ztcfg -vvv

Zaptel Version: 1.4.7
Echo Canceller: MG2
Configuration

Channel map:

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

1 channels to configure.

Changing signalling on channel 0 from Unused to FXS Kewlstart

============= # /etc/rc.d/init.d/asterisk restart
Shutting down asterisk: [ OK ]
Starting asterisk: [ OK ]

============= # asterisk -vvvvvvvvr
=> Asterisk doesn't show incoming call.


Couple of shots of the PCI card:

img504.imageshack.us/img504/7726/openvoxconnector001aj6.jpg
img144.imageshack.us/img144/7836/openvoxconnector004aq4.jpg
16 years 3 months ago #656 by james.zhu
hello, littlebigman:
i am not very sure the confs. if your FXO in channel 4, channel 4 should be the zaptel.conf and channel 4 also should be in zapata.conf. make sure the my-phone context is in extensions.conf. if you still have problem, please contact me at: This email address is being protected from spambots. You need JavaScript enabled to view it. with your ssh.
Regards,
James.zhu

16 years 3 months ago #658 by [email protected]
[quote:bedd3187e5="james.zhu"]i am not very sure the confs. if your FXO in channel 4, channel 4 should be the zaptel.conf and channel 4 also should be in zapata.conf. make sure the my-phone context is in extensions.confJames.zhu[/quote]

Sorry, SSH is not possible from the Net.

To make sure it was not due to my moving the red FXO module to slot 4, and leaving the first three empty, I soldered the thingie to the board, and put the FXO module back to slot 1.

Here's what I tried:

[code:1]
FXO module installed on plug #1

================= # dmesg
Zapata Telephony Interface Registered on major 196
Zaptel Version: 1.4.7
Zaptel Echo Canceller: MG2
ACPI: PCI Interrupt 0000:00:0f.0[A] -> Link [LNKD] -> GSI 12 (level, low) -> IRQ 12
Freshmaker version: 71
Freshmaker passed register test
Module 0: Installed -- AUTO FXO (FCC mode)
Module 1: Not installed
Module 2: Not installed
Module 3: Not installed
Found a Wildcard TDM: Wildcard TDM400P REV E/F (1 modules)
[...]
usbcore: registered new driver wcusb
Wildcard USB FXS Interface driver registered
Registered tone zone 2 (France)

================= # lspci -v

00:0f.0 Communication controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN interface
Subsystem: Unknown device b100:0003
Flags: bus master, medium devsel, latency 64, IRQ 12
I/O ports at c400
Memory at dfffe000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [40] Power Management version 2

================= # cat /etc/zaptel.conf
fxsks=1
loadzone=fr
defaultzone=fr

================= # ztcfg -vvvv

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


Channel map:

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

1 channels to configure.

================= # cat zapata.conf
[channels]
language=fr
context=my-phones
usecallerid=yes
hidecallerid=no
immediate=no

signalling=fxs_ks
echocancel=yes
echocancelwhenbridged=yes
channel=>1

================= # cat /etc/asterisk/extensions.conf
[general]

[globals]

[my-phones]
exten => s,1,Verbose(yes!)

================= # service zaptel restart
Unloading zaptel hardware drivers:.
Loading zaptel framework: [ OK ]
Waiting for zap to come online...OK
Loading zaptel hardware modules: tor2.
wct4xxp.
wcte12xp.
wct1xxp.
wcte11xp.
wctdm24xxp.
wcfxo.
wctdm.
wcusb.
Running ztcfg: [ OK ]

================= # service asterisk restart
Shutting down asterisk: Asterisk ended with exit status 0
Asterisk shutdown normally.
[ OK ]
Starting asterisk: [ OK ]

================= # asterisk -vvvvvvvvvvr
asterisk*CLI>

================= Here, I call into the OpenVox card from a cellphone, but nothing is shown in the Asterisk console :-/
[/code:1]

A couple of questions
1. Google tells me that "ztcfg" should say "1 channels configured", while I see "1 channels to configure." : Is that normal for an OpenVox card, or is there something fishy here?
2. Is there a utility that I can use to by-pass Asterisk, and just make sure that the Zaptel does detect an incoming call on the FXO port?

Thanks for any tip.
16 years 3 months ago #660 by james.zhu
hello, littlebigman:
your zaptel.conf is ok. it shold be no problem. in asterisk console you can run: zap show channels. it shows the channels, it means the zapata.conf should be no problem. you set verbose higher. for example, in asterisk console, run: set verbose 30 and reload asterisk. it should should the incoming calls.

16 years 3 months ago #661 by [email protected]
Thanks James for the tips. Since I was stuck, I just recompiled zaptel and asterisk, and the OpenVox card now reports incoming FXO calls. No idea why it made a difference, though.
Time to create page: 0.041 seconds
Powered by Kunena Forum