[asterisk-bugs] [JIRA] (ASTERISK-24710) Call forwarding to misc destination works only with first trunk if CID number is stated in dialing pattern

[Max Man (JIRA)]

     [ https://issues.asterisk.org/jira/browse/ASTERISK-24710?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Max Man updated ASTERISK-24710:
-------------------------------

    Attachment: call_forward_debug_23012015.txt

Please see the call_forward_debug_23012015.txt attached.
It was the incoming call, IVR answered it, than the internal extension number was dialed and call was forwarded to misc. destination (on no answer).

> Call forwarding to misc destination works only with first trunk if CID number is stated in dialing pattern
> ----------------------------------------------------------------------------------------------------------
>
>                 Key: ASTERISK-24710
>                 URL: https://issues.asterisk.org/jira/browse/ASTERISK-24710
>             Project: Asterisk
>          Issue Type: Bug
>      Security Level: None
>    Affects Versions: 13.0.1
>         Environment: FREEPBX Distro 6.12.65-22 tested on 13.0.1 & 11.05
>            Reporter: Max Man
>            Assignee: Max Man
>         Attachments: call_forward_debug_23012015.txt
>
>
> Found bug (not sure if it is asterisk core bug or freepbx bug) but I have the following route:
> {quote}
> exten => _*8[89]XXXXXXXXX/_XXX.,n,Macro(dialout-trunk,11,${EXTEN:8},,off)
> exten => _*8[89]XXXXXXXXX/_XXX.,n,Macro(dialout-trunk,2,${EXTEN:8},,off)
> {quote}
> And I use it to dial some MISC destinations, which are used as a call forward destinations (on no answer) for some extensions.
> When I have incoming call from number 89001234567 and it goes to MISC destination only first (11) trunk is dialing the number, if it gives congestion reply call goes to blackhole. Seems like on the second try (when 2 trunk should be used) the CID is not sent to the system so there no available route to proceed the call.
> If I remove _XXX. from route, both trunks serve the call.



--
This message was sent by Atlassian JIRA
(v6.2#6252)