[asterisk-users] did sometimes not working

Sebastian Reitenbach itlistuser at rapideye.de
Fri Jul 21 07:20:29 MST 2006


Hi,

I am here in Germany connected to the telephone system with a PRI interface:
00:0b.0 Network controller: Tiger Jet Network Inc. Tiger3XX Modem/ISDN 
interface. To let it work, I have read that I have to set the options 
overlapdial=yes and immediate=no in zapata.conf. here is my zapata.conf:

[channels]

language=en
context=from-pstn
;signalling=fxs_ks
signalling=pri_cpe ; pri_cpe = PRI slave ; pri_net = PRI master
switchtype=euroisdn
rxwink=300
callerid=asreceived
usecallerid=yes
nationalprefix=0
internationalprefix=00
localprefix=03381
callerid=asreceived
hidecallerid=no
callwaiting=yes
usecallingpres=yes
callwaitingcallerid=yes
threewaycalling=yes
transfer=yes
cancallforward=yes
callreturn=yes
echocancel=yes
echocancelwhenbridged=yes
echotraining=400
rxgain=0.0
txgain=0.0
overlapdial=yes
group=1
callgroup=1
pickupgroup=1
immediate=no
useincomingcalleridonzaptransfer=yes
channel => 1-15,17-31


but when I issue a reload chan_zap in the asterisk console, then I can see the 
following in the log output:

Jul 21 14:20:16 DEBUG[1345] config.c: Parsing /etc/asterisk/zapata-auto.conf
Jul 21 14:20:16 DEBUG[1345] config.c: 
Parsing /etc/asterisk/zapata_additional.conf
Jul 21 14:20:16 WARNING[1345] chan_zap.c: Ignoring signalling
Jul 21 14:20:16 WARNING[1345] chan_zap.c: Ignoring switchtype
Jul 21 14:20:16 WARNING[1345] chan_zap.c: Ignoring rxwink
Jul 21 14:20:16 WARNING[1345] chan_zap.c: Ignoring nationalprefix
Jul 21 14:20:16 WARNING[1345] chan_zap.c: Ignoring internationalprefix
Jul 21 14:20:16 WARNING[1345] chan_zap.c: Ignoring localprefix
Jul 21 14:20:16 WARNING[1345] chan_zap.c: Ignoring overlapdial
Jul 21 14:20:16 DEBUG[1345] chan_zap.c: Updated conferencing on 1, with 0 
conference users


I have no clue why it says it is ignoring the overlapdial option.

Jul 21 10:49:56 VERBOSE[3485] logger.c:     -- Accepting overlap call 
from '08153123450' to '96743' on channel 0/1, span 1
Jul 21 10:49:56 DEBUG[3063] devicestate.c: Changing state for Zap/1 - state 2 
(In use)
Jul 21 10:49:56 DEBUG[29238] app_queue.c: Device 'Zap/1' changed to state '2' 
(In use)
Jul 21 10:49:56 VERBOSE[29237] logger.c:     -- Starting simple switch 
on 'Zap/1-1'

so the last two digits are missing.

so about 80% of the incoming calls work well, but especially with one sender 
we have a problem, there is always the last digit missing. This is a 1-800 
service in the US, forwarding the call to our asterisk. As a workaround I 
configured it to call to XXXXX580 and have an inbound route set for XXXXX58 to 
the number I want to reach.

any idea what I can do? especially why it says it ignores the overlapdial 
parameter, and why it is accepting them nevertheless?
are there any timing parameters to tell asterisk to wait a second longer for 
the last digit? some rx.. tx.. parameters in the zapata.conf?

kind regards
Sebastian




More information about the asterisk-users mailing list