Not passing dialed digits to the DAHDI channel on outbound c

Asterisk Asterisk Support
1

Hi all! I am setting up a new box to replace my old Asterisk system and am completely stumped here. Below is the console output when I attempt to make an outbound call… Essentially it’s opening up the channel, I get a dial tone but it’s not passing the digits I entered. Does anyone have an idea why this is? I’ve compared the configs for both systems and can’t see where anything is different - other than the old system using Zap instead of DAHDI. At the dial tone I can dial the number again and get the call to go out but I can’t figure why the number is being stripped.

– Executing [XXXXXXX@DLPN_mcsd:1] Macro(“SIP/104-0000002c”, “trunkdial-failover-0.3,DAHDI/1/,trunk_1,”) in new stack
– Executing [s@macro-trunkdial-failover-0.3:1] GotoIf(“SIP/104-0000002c”, “0?1-fmsetcid,1”) in new stack
– Executing [s@macro-trunkdial-failover-0.3:2] GotoIf(“SIP/104-0000002c”, “0?1-setgbobname,1”) in new stack
– Executing [s@macro-trunkdial-failover-0.3:3] Set(“SIP/104-0000002c”, “CALLERID(num)=XXX-XXX-XXXX”) in new stack
– Executing [s@macro-trunkdial-failover-0.3:4] GotoIf(“SIP/104-0000002c”, “1?1-dial,1”) in new stack
– Goto (macro-trunkdial-failover-0.3,1-dial,1)
– Executing [1-dial@macro-trunkdial-failover-0.3:1] Dial(“SIP/104-0000002c”, “DAHDI/1/”) in new stack
– Called 1/ (Where did my number go???)

Here is the my local calling rule

[CallingRule_Local]
exten = _XXXXXXX,1,Macro(trunkdial-failover-0.3,${trunk_1}/${,${EXTEN:0})},trunk_1,)

and as you can see it is not set to strip any digits…

I’d be most appreciative of ANY help!

Darcy

2

It appears that your running freepbx? trixbox?

This is what was passed to the macro… “trunkdial-failover-0.3,DAHDI/1/,trunk_1,”

This line is suspect to me… exten = _XXXXXXX,1,Macro(trunkdial-failover-0.3,${trunk_1}/${,${EXTEN:0})},trunk_1,)

Notice how it contains 1 open parenthesis , yet there are two close parenthesis.

I also dont understand this part: ${,${EXTEN:0})}, not sure what it is trying to do, but I would think if it is just to pass the extension, then it should just read ${EXTEN}. I suspect Asterisk doesn’t know what to do with it or atleast what it thinks, is causing it to return nothing, which is what is being seen in the line that was passed to the macro.

3

Thanks for the reply… I am using the asterisk gui… the dialing rules were built by default so I too have no idea what it’s actually doing there… I know the :0 references how many digits to strip off a number but I don’t know what the ,$ is about. I’ll try removing the ,$ and closing that parathesis and see if I get anywhere.

4

Stripped the local dialing rule down to this:

[CallingRule_Local]
exten = _XXXXXXX,1,Macro(trunkdial-failover-0.3,${trunk_1}/${EXTEN},trunk_1)

And then I noticed that I had two different local calling rules, the other one was more explicit as exten = _XXXXXXX! and probably better but I went ahead and deleted that rule in case it was just getting confused about which rule to use.

Then I reloaded and made a successful test call!!!

Thank you mazzic for helping me see what was right in front of my face :smile: I get blind to the weirdness after awhile and kept thinking there was something in the trunkdial macro that was causing the problem!