asterisk users - Jul 2006 - overlapdial and DID not always working

Hi,

another try with a hopefully better subject.

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. I am using asterisk 1.2.7.1 and zaptel 1.2.5. To let DID work, I 
have 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

Sebastian Reitenbach ha scritto:
> 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 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.
This is "normal", some parameter cannot be changed with reload, the
only way to change them is stop asterisk and restart (stop now,
restart asterisk, you found all parameters correct).
This message is like "ouch you are reloading the configuration, but i
cannot change this parameter by this way!"

Good job.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20060724/6c839f77/signature.pgp

Sebastian Reitenbach ha scritto:
> 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?
I found the same indentical problem, the trouble was the switchtipe, i
am using "national" and i switched to "unknown".

Why? in italy with "Telecom" the pri channel sometime is doing
overlap, sometime no... hehe :-) so you can miss the non "radical"
part of the number! and i think this depends on the kind of the
"caller"...

The parameter overlapdial is accepted, you are wrong (see my previous
email).

Bye.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20060724/5a97344f/signature.pgp

Sebastian Reitenbach wrote:
> 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?
chan_zap cannot change the overlapdial option on a reload.  It can only 
do it on a unload/load.

-- 
Now accepting new clients in Birmingham, Atlanta, Huntsville, 
Chattanooga, and Montgomery.

Hi,
> 
> This is "normal", some parameter cannot be changed with reload,
the
> only way to change them is stop asterisk and restart (stop now,
> restart asterisk, you found all parameters correct).
> This message is like "ouch you are reloading the configuration, but i
> cannot change this parameter by this way!"
ok, good to know that I do not need to worry, I can live with that.
> 
> Good job.
thanks. but I still do not know why sometimes the last digit or last digits 
are missing :(

Sebastian

Hi,
> > 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?
> 
> I found the same indentical problem, the trouble was the switchtipe, i
> am using "national" and i switched to "unknown".
I have switchtype set to euroisdn.
I'll go and try others. maybe that will fix it.
> 
> Why? in italy with "Telecom" the pri channel sometime is doing
> overlap, sometime no... hehe :-) so you can miss the non
"radical"
> part of the number! and i think this depends on the kind of the
> "caller"...
> 
> The parameter overlapdial is accepted, you are wrong (see my previous
> email).
and I shall not forget to fully restart the system (:

thanks
I'll let you know whether it will work or not.

kind regards
Sebastian

> 
> I found the same indentical problem, the trouble was the switchtipe, i
> am using "national" and i switched to "unknown".
> 
is "unknown" allowed for switchtype?
when I take a look here: 
http://www.voip-info.org/wiki/index.php?page=Asterisk+config+zapata.conf
then there is no unknown switchtype?

jut curious

kind regards
Sebastian

Sebastian Reitenbach ha scritto:
>> I found the same indentical problem, the trouble was the switchtipe, i
>> am using "national" and i switched to "unknown".
>>
> is "unknown" allowed for switchtype?
> when I take a look here: 
> http://www.voip-info.org/wiki/index.php?page=Asterisk+config+zapata.conf
> then there is no unknown switchtype?
I am wrong... sorry :-) pridialplan not switchtype!

Ok... this is:

the number on the PRI is always:

XXXXXXXYYY where XXXX is the "radical" and YYY is the local number

this is wath is working for me:
switchtype = national
pridialplan = unknown
prilocaldialplan = unknown
overlapdial = yes

pridialplan = unknown -> ok
pridialplan = national -> missing YYY on some call

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url :
http://lists.digium.com/pipermail/asterisk-users/attachments/20060725/5772c9c8/signature.pgp

Hi,

> 
> I am wrong... sorry :-) pridialplan not switchtype!
> 
> Ok... this is:
> 
> the number on the PRI is always:
> 
> XXXXXXXYYY where XXXX is the "radical" and YYY is the local
number
> 
> this is wath is working for me:
> switchtype = national
> pridialplan = unknown
> prilocaldialplan = unknown
> overlapdial = yes
> 
> pridialplan = unknown -> ok
> pridialplan = national -> missing YYY on some call
just setting pridialplan = unknown, leaving the others untouched, does not let 
me dial out anymore, theres always all channels congested.
 
but I have the switchtype set to euroisdn, so I'll try later in hte evening
or
tomorrow moring, when nobody will call.

kind regards
Sebastian