FreePBX 2.3 adds post-dial delay to Zaptel extension

wireguy's picture
Posted September 21st, 2007 by wireguy (tadpole)

Since I "upgraded" to FreePBX 2.3, calls from a Zaptel extension to a SIP extension no longer connect immediately, but have a post-dial delay of four or five seconds. I've proved that this is a FreePBX 2.3 "feature" by doing a clean Trixbox install, setting up a Zaptel and SIP extension and calling (without delay) from Zaptel FXS to SIP. Then "upgrade" to FreePBX 2.3 and the dreaded post-dial delay manifests itself.

Is this a known bug or can anyone suggest what may be causing this?

Also, if calling out from any extension through a Zap trunk to the PSTN, there is a similar delay, but I've found this has always been apparent, not just with version 2.3. It would still be good to have it working without the delay.


__________________


‹ Error symlink from modules failed Blind transfer context handling ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

my guess would be it's the

p_lindheimer's picture
On September 21st, 2007 p_lindheimer (Developer) said:

my guess would be it's the bad-number context that is generated so when you dial a number it is not immediately recognizing the call. In amportal.conf try:

AMPBADNUMBER=true

and then regenerate the dialplan (orange bar) and see if it goes away.
------------------------------------
Philippe Lindheimer - FreePBX Project Lead
http//freepbx.org - IRC #freepbx


__________________

Philippe Lindheimer - FreePBX Project Leader
FreePBX Training Opportunities - Click Here
Get Official Paid Support - Click Here


Almost correct

wireguy's picture
On September 22nd, 2007 wireguy (tadpole) said:

Unfortunately this suggestion did not make any difference. However, just to experiment, I then tried AMPBADNUMBER=false and voila! The post-dial delay on ZAP extension to other extension calls vanished.

Perhaps this should be the default setting in version 2.3?


oops, I meant false. And no

p_lindheimer's picture
On September 22nd, 2007 p_lindheimer (Developer) said:

oops, I meant false. And no this should not be the default setting. Most installations do not use zap phones, they are typically SIP based devices where this has no effect and thus benefit from this setting because it results in a much more user friendly result when people mis-dial numbers. However, the option is there for this case and a few others such as phones like Grandstream and SNOM that have a form of 'early dial' feature where this is required also.
------------------------------------
Philippe Lindheimer - FreePBX Project Lead
http//freepbx.org - IRC #freepbx


__________________

Philippe Lindheimer - FreePBX Project Leader
FreePBX Training Opportunities - Click Here
Get Official Paid Support - Click Here


Talking about ZAP phones,

Blackdog's picture
On September 23rd, 2007 Blackdog (tadpole) said:

Talking about ZAP phones, does anyone have any idea why '*0' cannot be dialled? I've had to change the speed dial prefix to *1 to get around it, and I have no idea why. The zaptel driver, or chan_zap.so is absorbing the '*0', I'm not completely certain of this, and if I press '*0' during a
call, it is sent as dtmf.. but if I attempt to dial *01 for a speed dial, asterisk immediately sends me a busy tone after the '*0'..


you probably don't want to

p_lindheimer's picture
On September 23rd, 2007 p_lindheimer (Developer) said:

you probably don't want to use *1 as your prefix as it is typically the default 'record on demand' feature code.
------------------------------------
Philippe Lindheimer - FreePBX Project Lead
http//freepbx.org - IRC #freepbx


__________________

Philippe Lindheimer - FreePBX Project Leader
FreePBX Training Opportunities - Click Here
Get Official Paid Support - Click Here