[asterisk-bugs] [JIRA] (ASTERISK-20793) Recall dial tone doesn't start upon hookflash transfer request

[Shaun Ruffell (JIRA)]

    [ https://issues.asterisk.org/jira/browse/ASTERISK-20793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=200837#comment-200837 ] 

Shaun Ruffell commented on ASTERISK-20793:
------------------------------------------

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.
                
> Recall dial tone doesn't start upon hookflash transfer request
> --------------------------------------------------------------
>
>                 Key: ASTERISK-20793
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-20793
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>          Components: Core/Channels
>    Affects Versions: 1.8.20.0
>         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.
>            Reporter: Igor Kravets
>            Assignee: Igor Kravets
>         Attachments: full.txt
>
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira