[Asterisk-Users] Zap Channel error using 4-port FXO TDM400P

Darrin Johnson djohnson at isdomaininc.com
Tue Jul 6 12:19:30 MST 2004


I have been having some troubles with the zaptel channel on what appears to
be the inbound process.  The box is running the stable CVS code and has a
TDM400P 4-port FXO card in it for analog connectivity.  Channel 1 is the
only active port on the card at the moment as we only have one analog line.
What has been happening is that it looks like Asterisk has been detecting an
inbound call even though there is not inbound PSTN call.  A part of this
activity was generation of a CDR that would get logged.

After this error was detected I configured an extension to send incoming
calls to an extension that uses the NoCDR() application so that we do not
keep sending these bogus CDR's to the DB.

The messages displayed on the console window would report this activity at
varying intervals sometimes as short as 2 or 3 seconds over and over and
over again:

    -- Starting simple switch on 'Zap/1-1'
Jul  6 12:08:48 WARNING[-1418982480]: chan_zap.c:4706 ss_thread: CallerID
returned with error on channel 'Zap
/1-1'
    -- Executing NoCDR("Zap/1-1", "") in new stack
Jul  6 12:08:48 WARNING[-1418982480]: cdr.c:108 ast_cdr_free: CDR on channel
'Zap/1-1' not posted
Jul  6 12:08:48 WARNING[-1418982480]: cdr.c:110 ast_cdr_free: CDR on channel
'Zap/1-1' lacks end
    -- Executing Wait("Zap/1-1", "90") in new stack
  == Spawn extension (incoming-pstn, s, 2) exited non-zero on 'Zap/1-1'
Jul  6 12:08:56 DEBUG[-1418982480]: chan_zap.c:1717 zt_hangup: Hangup:
channel: 1 index = 0, normal = 21, cal
lwait = -1, thirdcall = -1
Jul  6 12:08:56 DEBUG[-1418982480]: chan_zap.c:1134 zt_disable_ec: disabled
echo cancellation on channel 1
Jul  6 12:08:56 DEBUG[-1418982480]: chan_zap.c:2097 zt_setoption: Set option
TDD MODE, value: OFF(0) on Zap/1
-1
Jul  6 12:08:56 DEBUG[-1418982480]: chan_zap.c:1077 update_conf: Updated
conferencing on 1, with 0 conference
 users
    -- Hungup 'Zap/1-1'

I thought that perhaps there was something on the analog line itself that
was causing Asterisk and FXO card to respond as if a call was inbound.  I
have pulled the analog line from the TDM400P and this is still occurring
which means that something between the TDM400P and Asterisk is either not
configured correctly or there is a code error.

In the archives I noticed some similar issues early one that had to do with
callprogress=yes and busydetect=yes, but neither of those things are set.
Is there a default for those?

The Zapata.conf file for this install looks like this (I have X'd out the
phone number of the configured channel for this email):

[channels]
context=incoming-pstn
signalling=fxs_ks

hidecallerid=no
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
rxgain=15.0
txgain=0.0

immediate=no
callerid="BrianHomePhone"<(XXX) XXX-XXXX>
channel => 1
callerid="NotYetConnected2"<(222) 222-2222>
channel => 2
callerid="NotYetConnected3"<(333) 333-3333>
channel => 3
callerid="NotYetConnected4"<(444) 444-4444>
channel => 4

Any thoughts or ideas on what might be the issue are greatly appreciated!

Thanks,

dj






More information about the asterisk-users mailing list