Summary:	ASTERISK-24710: Call forwarding to misc destination works only with first trunk if CID number is stated in dialing pattern
Reporter:	Max Man (maxman)	Labels:
Date Opened:	2015-01-22 04:04:42.000-0600	Date Closed:	2015-02-25 09:21:55.000-0600
Priority:	Major	Regression?
Status:	Closed/Complete	Components:
Versions:	13.0.1	Frequency of Occurrence
Related Issues:
Environment:	FREEPBX Distro 6.12.65-22 tested on 13.0.1 & 11.05	Attachments:	( 0) call_forward_debug_23012015.txt
Description:	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.
Comments:	By: Matt Jordan (mjordan) 2015-01-22 15:25:52.026-0600 We require a complete debug log to help triage the issue. This document will provide instructions on how to collect debugging logs from an Asterisk machine for the purpose of helping bug marshals troubleshoot an issue: https://wiki.asterisk.org/wiki/display/AST/Collecting+Debug+Information By: Rusty Newton (rnewton) 2015-02-10 16:56:12.784-0600 Max, can you provide the additional debug? From your description it isn't clear how to reproduce the issue. We can't do anything without a clear, step by step description of how to reproduce the issue, or debug that would show the issue clearly. By: Max Man (maxman) 2015-02-11 01:32:52.396-0600 Please see the call_forward_debug_23012015.txt attached. It was incoming call, IVR answered it, then the internal extension number was dialed and call was forwarded to misc. destination (on no answer). By: Rusty Newton (rnewton) 2015-02-25 09:21:25.018-0600 Well, you didn't follow the instructions provided as there are no "DEBUG" entries in your log. {noformat}    -- Executing [continue@macro-dialout-trunk:2] Set("SIP/INCOMING-TRUNK-0000007b", "CALLERID(number)=") in new stack {noformat} Your issue probably has something to do with why CallerID is being set to nothing here. Yet, there is not enough information to tell what is happening without DEBUG messages, more dialplan and a packet capture of the related call. At this point I'd consider this issue technical support and not a bug report. You haven't demonstrated a bug in Asterisk. The Asterisk issue tracker is not the appropriate place to handle support requests. I recommend collecting a debug log as described and a corresponding packet capture of the call taking place -  then FreePBX users in the [FreePBX community|http://community.freepbx.org/] can help you determine whether there is a bug with FreePBX dialplan. If they determine that it is not a bug in dialplan then at that point you should have enough information to know whether it is a bug in Asterisk or not. At that point feel free to request that we re-open the issue. You can contact a bug marshal in #asterisk-bugs or #asterisk-dev on irc.freenode.net. Thanks.