I have just installed a new box using Elastix 2.0.3 and a Digium TDM400P board populated with 4 FXO cards.

I configured all the channels as described in other threads.

I can receive and make calls BUT the problem is that there is a LONG (up to 15 seconds) wait time before the call is actually placed.

When looking at the asterisk console during a call placement I can see the following information appearing as soon as I dial:

-- Called g0/<<number>> 'outbound rule is working as g0 is the the assigned FXO group fir that type of call


Then, after up to 15 seconds later, I get:

-- DAHDI/1-1 is ringing

And the call gets completed.

Can anyone help me eliminate (or reduce) this waiting period?

Thank you in advance,
Jonas



Here are my configuration files:


dahdi-channels.conf
; Span 1: WCTDM/4 "Wildcard TDM400P REV I Board 5" (MASTER)
;;; line="1 WCTDM/4/0 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=0
context=from-zaptel
channel => 1
callerid=
group=0
context=default

;;; line="2 WCTDM/4/1 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=1
context=from-zaptel
channel => 2
callerid=
group=1
context=default

;;; line="3 WCTDM/4/2 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=1
context=from-zaptel
channel => 3
callerid=
group=1
context=default

;;; line="4 WCTDM/4/3 FXSKS (In use)"
signalling=fxs_ks
callerid=asreceived
group=2
context=from-zaptel
channel => 4
callerid=
group=2
context=default




chan_dahdi.conf

[trunkgroups]

[channels]
context=from-zaptel
signalling=fxs_ks
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=no
faxdetect=incoming
echotraining=800
rxgain=2.0
txgain=2.0
callgroup=1
pickupgroup=1

;Uncomment these lines if you have problems with the disconection of your analog lines
busydetect=yes
busycount=3


immediate=no
callprogress=yes


#include dahdi-channels.conf
#include chan_dahdi_additional.conf

Check if you have a extension number starting with you Outbound prefix, this could be a digit timeout. Example:

Route prefix: 9 + Number
Extension: 9111

Regard

I tried several numbers which use different outbound routes.

Channel 1 is associated to group 0.
Channels 2 and 3 with g1
And
Channel 4 with g2.

The delay occurs with all groups.

Regards,
Jonas

Please show us all your extension number and outbound prefix

EXTENSIONS:
8xx (801, 822, 880, etc)


RING GROUPS:
6xx (640, 641, etc)


OUTBOUND ROUTES:
Local calls:
[2-6]XXXXXXX
===> ZAP/g0

Long Distance:
0ZX|ZX[2-6]XXXXXXX
0|ZX[2-6]XXXXXXX
ZX[2-6]XXXXXXX
===> ZAP/g1

Mobile:
[7-9]XXXXXXX
===> ZAP/g2




Examples of numbers that I tried to call:
22593600 (out through g0)
81124000 (out through g2)

In both cases the outbound routes seemed to work as expected but there was this LONG connection delay.

Example:
Dialed: 22593600

System outputs:
-- Called g0/22593600 (outbound route ok)

about 15 seconds later:

-- DAHDI/1-1 is ringing (DAHDI/1-1 is associated to g0)

Only then the call is completed.



Thank you again,
Jonas

You are using a incorrectly use of number, asterisk is waiting for a interdigit timeout because you have several destination starting with the same number, for outbound call use a outbound prefix like 9 + number. For example:

9 + 22593600
9 + 81124000

You can change this just adding in the outbound route prefix: 9|. --> g0

Regard

Tried that ("9|.").

Same result.

I really don't think this is an outbout route problem since the system recognizes de outbound correclty and chooses the right trunk.
The problem occurs just after that when the trunk itself delays the completion of the call.

Thanks,
Jonas

Just updated to Elastix 2.2 with the hope of solving this problem.

Nothing yet.

Anyone?


I have seen others reporting the same problems but couldn't find fixes for it.

Example:
www.fonality.com/trixbox/forums/trixbox-...lay-when-dialing-out



PLEASE HELP !!!

ccroter,

Having put in many systems with 2.0.3 with PSTN, their are no known issues with dial-out times. This goes likewise for Elastix 2.2 (a few systems done now with PSTN).

All using the digium cards....

Have you set the correct country zones in /dahdi/system.conf for tones.
Have you setup opermode in modprobe.conf to match your country??

if you have these correctly setup, is their any reason you are using the from-zaptel context??? What happens if you put it back to the basics, and treat all the channels as G0 (and put the context back to default)....do you have the same delay in dialing out???

Regards

Bob

Hello Bob,
Thank you for your response.

This is in fact my first system using the TDM400P FXO board. In the past I only used T1/E1 boards.


Regarding the settings:

MODPROBE.CONF
alias eth0 r8169
alias scsi_hostadapter ahci
options wctdm opermode=BRAZIL


DAHDI/SYSTEM.CONF
# This file is parsed by the Dahdi Configurator, dahdi_cfg
#
# Span 1: WCTDM/4 "Wildcard TDM400P REV I Board 5" (MASTER)
fxsks=1
echocanceller=oslec,1
fxsks=2
echocanceller=oslec,2
fxsks=3
echocanceller=oslec,3
fxsks=4
echocanceller=oslec,4
# Global data
loadzone = br
defaultzone = br



I also changed the contect to default.




But, unfortunately, the result is the same. I'm still getting a 10 to 15 seconds delay until the other side begins to ring.


-- Executing [s@macro-dialout-trunk:19] Dial("SIP/801-00000001", "DAHDI/g0/25734747,300,") in new stack
-- Called DAHDI/g0/25734747
(the line above appears just as i end dialing)

-- DAHDI/1-1 answered SIP/801-00000001
(this line appears about 5 seconds later)

(the phone starts ringing about 10 seconds later)



I would really appreciate if you could try to help me finding what am i doing wrong.

Regards,
Jonas


Note: I have an IAX trunk connecting this server to another Elastix server. If I direct the same call to the IAX trunk it rings much much faster.