The Asterisk detects the analog phone hangup slowly

Hi all, I met a problem when using an analog card.
The enviroment is CentOS release 5 (Final) + Asterisk 1.4.13 + Zaptel 1.4.8 + Synway FXM-8A/PCI analog card.
The driver for Synway FXM-8A/PCI is SynAst-1.0.0.0.

My problem is: Asterisk take at least 1.2 seconds to got the hangup signal after I put down the handset of the analog phone under the analog card. 1.2 seconds is too
long, and the provider of FXM-8A/PCI reported that the card can detect the hangup signal in 400 milliseconds, so maybe the problem is the zaptel driver or the asterisk?

Here is my zaptel.conf

fxsls=1
fxsls=2
fxols=3
fxols=4
fxols=5
fxols=6
fxols=7
fxols=8

loadzone = cn
defaultzone = cn

and this is the zapata.conf

[trunkgroups]

[channels]
context=default
switchtype=national
signalling=fxo_ls
rxwink=300 ; Atlas seems to use long (250ms) winks
usecallerid=yes
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
canpark=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=0.0
txgain=0.0
group=1
callgroup=1
pickupgroup=1

immediate=no
busycount=6
hanguponpolarityswitch=yes
callprogress=yes

#include zapata-channels.conf

and, here is the zapta-channels.conf

;Server ID is 2

signalling=fxs_ls
group=0
context=outside_line
channel =>1

signalling=fxs_ls
group=0
context=outside_line
channel =>2

signalling=fxo_ls
group=0
context=bank
callerid="603" <603>
channel =>3

signalling=fxo_ls
group=0
context=bank
callerid="604" <604>
channel =>4

signalling=fxo_ls
group=0
context=bank
callerid="605" <605>
channel =>5

signalling=fxo_ls
group=0
context=bank
callerid="606" <606>
channel =>6

signalling=fxo_ls
group=0
context=bank
callerid="607" <607>
channel =>7

signalling=fxo_ls
group=0
context=bank
callerid="608" <608>
channel =>8

Thanks all.

The project is in China, and we haven't connect to the PSTN, it is a closed system.
And the IP phone does not get this problem.

i] Last edited by Jimmy at 2009-12-19 10:12 [/i

hi:
you have to set the driver with china mode when load the driver. modprobe fxm8XXX opermode=CHINA and set the country to china in indication.conf.
regards!
James.zhu

Thank you, James.

Here is my case:

The card driver of Synway, fxm8apci does not provide such module parameter opermode. it provides only the four parameters:
module_param(debug, int, 0600);
module_param(battthresh, int, 0600);
module_param(alawoverride, int, 0600);
module_param(ECHO_OPEN, int, 0600);

=========================================
[root@mymailserver ~]# lsmod | grep zaptel
zaptel 191108 19 fxm8apci
crc_ccitt 6337 1 zaptel
==========================================
here is the /etc/asterisk/indications.conf

[general]
country=cn ;default location

[cn]
description = China
; Reference: http://www.itu.int/ITU-T/inr/forms/files/tones-0203.pdf
ringcadence = 1000,4000
dial = 450
busy = 450/350,0/350
ring = 450/1000,0/4000
congestion = 450/700,0/700
callwaiting = 450/400,0/4000
dialrecall = 450
record = 950/400,0/10000
info = 450/100,0/100,450/100,0/100,450/100,0/100,450/400,0/400
; STUTTER - not specified
stutter = 450+425

=====================================================

The problem still existed.

I don't know how to do now, could James and somebody others help me?

You are using sanway card, so I think you should ask them for help.

Yes, you are right. We have asked SynWay for help, but they thought it was the zaptel or asterisk, not theirs.
Something proves that their card works well, the card get and pass the on/off hook signal immediately.

I have insert some debug information into the zaptel-1.4.12, and here is the messages in /var/log/messages


[root@localhost ~]# vim /var/log/messages
Dec 20 15:29:37 localhost kernel: Leave __zt_hooksig_pvt
Dec 20 15:29:37 localhost kernel: FXM8APCI Interrupt Time

---

= 1216
Dec 20 15:29:41 localhost kernel: shfxm: Card 5 Going on hook
Dec 20 15:29:41 localhost kernel: Enter __zt_hooksig_pvt
Dec 20 15:29:41 localhost kernel: Leave __zt_hooksig_pvt
Dec 20 15:29:41 localhost kernel: FXM8APCI Interrupt Time

---

= 1217
Dec 20 15:29:47 localhost kernel: shfxm: Card 5 Going off hook
Dec 20 15:29:47 localhost kernel: Enter __zt_hooksig_pvt
Dec 20 15:29:47 localhost kernel: Leave __zt_hooksig_pvt
Dec 20 15:29:47 localhost kernel: FXM8APCI Interrupt Time

---

= 1217
Dec 20 15:29:55 localhost kernel: shfxm: Card 5 Going on hook
Dec 20 15:29:55 localhost kernel: Enter __zt_hooksig_pvt
Dec 20 15:29:55 localhost kernel: Leave __zt_hooksig_pvt
Dec 20 15:29:55 localhost kernel: FXM8APCI Interrupt Time

---

= 1217
Dec 20 15:30:03 localhost kernel: shfxm: Card 5 Going off hook
Dec 20 15:30:03 localhost kernel: Enter __zt_hooksig_pvt
Dec 20 15:30:03 localhost kernel: Leave __zt_hooksig_pvt
Dec 20 15:30:03 localhost kernel: FXM8APCI Interrupt Time

---

= 1215
Dec 20 15:30:05 localhost kernel: shfxm: Card 5 Going on hook
Dec 20 15:30:05 localhost kernel: Enter __zt_hooksig_pvt
Dec 20 15:30:05 localhost kernel: Leave __zt_hooksig_pvt
Dec 20 15:30:05 localhost kernel: FXM8APCI Interrupt Time

---

= 1216
Dec 20 15:30:07 localhost kernel: shfxm: Card 5 Going off hook

from above, shfxm, the driver name of FXM8APCI card, got the on/off hook signals, and send this to the zaptel __zt_hoosig_pvt immediately. It is too hard for me to hack the zaptel and asterisk, , I am not very familiar with them.
Any ideas?