[Home]

Summary:DAHTOOL-00063: Recall dial tone doesn't start upon hookflash transfer request
Reporter:Igor Kravets (megaboots)Labels:
Date Opened:2012-12-13 15:38:25.000-0600Date Closed:2014-08-01 16:18:36
Priority:MajorRegression?
Status:Closed/CompleteComponents:General
Versions:Frequency of
Occurrence		Constant
Related
Issues:
Environment:AsteriskNOW 1.5. Observed on 1.4, 1.6, 1.8 asterisk from latest yum + custom build of 1.8.20. Tested with dahdi_drivers 2.6, 2.5 from yum and custom built.Attachments:( 0) 0001-zonedata-Ensure-all-zones-have-a-default-DAHDI_TONE_.patch
( 1) full.txt
Description:When using hookflash with threewaycalling and transfer on dahdi FXS channels, we get no Recall dial tone indication
on the channel which requested flash tranfer. Just silence instead. So operator isn't sure if the call has been put on hold.

Following error message is logged:

[2012-12-14 01:31:12] WARNING[15423]: sig_analog.c:3249 __analog_handle_event: Unable to start dial recall tone on channel 3

I've tried different indications. Different dahdi drivers. Problem observed on openvox A400P and Digium AEX2400.
Comments:By: Rusty Newton (rnewton) 2012-12-14 17:11:16.771-0600

Hi, please read through https://wiki.asterisk.org/wiki/display/AST/Asterisk+Issue+Guidelines and https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information

Please provide an Asterisk full log with VERBOSE and DEBUG messages enabled at level 5 or above during the time the issue happens. Please attach that to the issue and point out where the issue occurs (though we should be able to find it by the message you included in the description).

Use 'Enter Feedback' when you have done this. Thanks!
By: Igor Kravets (megaboots) 2012-12-17 06:18:28.297-0600

Call from extension 995 (dahdi/3) to ext 996 (dahdi/4). 996 lifts handset, 995 presses hookflash. 996 gets holded. 995 doesn't hear recall tone.

[2012-12-17 16:01:59] WARNING[31575] sig_analog.c: Unable to start dial recall tone on channel 3
By: Igor Kravets (megaboots) 2012-12-17 06:21:20.425-0600

Did upload full log of the event. Please check full.txt attachment. Thank you.
By: Richard Mudgett (rmudgett) 2012-12-17 11:25:35.682-0600

Please attach the chan_dahdi.conf and the DAHDI system.conf files.  I think the dial recall tone is not defined for your country in the DAHDI zonedata.c.
By: Igor Kravets (megaboots) 2012-12-18 09:54:54.113-0600

Yes, problem was resolved by changing zone settings to 'us' back from 'ru' in /etc/dahdi/system.conf
loadzone=us
defaultzone=us

Sorry for blaming asterisk for that. Thank you for your help, please close the issue :)
By: Igor Kravets (megaboots) 2012-12-18 09:56:56.483-0600

No recall dial tone for 'ru' zone in dahdi. Change defaultzone=us in /etc/dahdi/system.conf fixes the issue.
By: Shaun Ruffell (sruffell) 2012-12-18 12:53:33.224-0600

Hi Igor.  Looking at http://www.itu.int/ITU-T/inr/forms/files/tones-0203.pdf I don't see a recall tone defined for the Russian Federation.  Is it valid to copy in the "fcc" settings into that zone?
By: Shaun Ruffell (sruffell) 2012-12-18 13:03:14.413-0600

Unless you tell me otherwise, it already looks like there are other zones that don't have DIALRECALL specified and just copy in the fcc cadence. I'll do that here and update dahdi-tools.
By: Shaun Ruffell (sruffell) 2012-12-18 13:37:28.554-0600

Igor, I've attached a patch to DAHDI-Tools that should allow you to restore your zone to "ru" and use a defaulted recall tone.

You should be able to apply it on top of your DAHDI-Tools source like:
{{wget "https://issues.asterisk.org/jira/secure/attachment/45773/0001-zonedata-Ensure-all-zones-have-a-default-DAHDI_TONE_.patch" -O - | patch -p1}}

Then rebuild / reinstall DAHDI-Tools and you should be good.


By: Igor Kravets (megaboots) 2012-12-19 09:55:52.648-0600

Patch works. Now i get recall dial tone on transfer even when zone settings are set to 'ru'.

Thank you!
By: Shaun Ruffell (sruffell) 2014-08-01 15:12:16.111-0500

Russ, this might be something that can be checked / applied / closed.