Call Confirmation fails after Asterisk 1.4.24 upgrade?

Running FreePBX 2.5.1.2 currently. I upgraded asterisk from v1.4.22 to 1.4.24, and it appears that “call confirmation” in my ring group configurations no longer work! No other changes seem to have been made to the system other than the asterisk upgrade. (I haven’t yet tried downgrading to test…)

I only use this where my ring group mixes an external (cell phone) number and an internal extension. The cell phone rings properly, and I am prompted with the proper ‘incoming-call-1-accept-2-decline’ prompt. Upon pressing “1” (or any other digit) the call immediately disconnects!

I even hand-edited [macro-confirm] just to add a verbose log entry if the macro is properly receiving any digits, and it appears that somehow it’s dying when trying to process the DTMF? Aside from the apparently simple [macro-confirm], I’m not sure where else to troubleshoot. All other DTMF-invoked functions seem to still be working - VMX Locator, IVR, voicemails… and the call bridges properly if call confirmation is OFF.

Any advice as to where to fiddle to further test this?

here is the verbose CLI output for the call confirmation bits:


– Called BW-SIP-A/+16144043355
– SIP/10101-09e9eac0 is ringing
– SIP/BW-SIP-A-09f357e0 is making progress passing it to Local/[email protected],2
– Local/[email protected],1 is making progress passing it to Local/RG-623-16144043355#@from-internal-58ba,2
– SIP/BW-SIP-A-09f357e0 answered Local/[email protected],2
– Local/[email protected],1 answered Local/RG-623-16144043355#@from-internal-58ba,2
– Executing [[email protected]:1] Set(“Local/[email protected],1”, “LOOPCOUNT=0”) in new stack
– Executing [[email protected]:2] Set(“Local/[email protected],1”, “__MACRO_RESULT=ABORT”) in new stack
– Executing [[email protected]:3] Set(“Local/[email protected],1”, “MSG1=“incoming-call-1-accept-2-decline””) in new stack
– Executing [[email protected]:4] BackGround(“Local/[email protected],1”, “incoming-call-1-accept-2-decline|m|en|macro-confirm”) in new stack
– <Local/[email protected],1> Playing ‘incoming-call-1-accept-2-decline’ (language ‘en’)
– Executing [[email protected]:1] Macro(“Local/[email protected],2”, “hangupcall|”) in new stack
– Executing [[email protected]:1] ResetCDR(“Local/[email protected],2”, “vw”) in new stack
== Spawn extension (macro-dial, s, 7) exited non-zero on ‘Local/RG-623-16144043355#@from-internal-58ba,2’ in macro ‘dial’
– Executing [[email protected]:2] NoCDR(“Local/[email protected],2”, “”) in new stack
– Executing [[email protected]:3] GotoIf(“Local/[email protected],2”, “1?skiprg”) in new stack
– Goto (macro-hangupcall,s,6)
– Executing [[email protected]:6] GotoIf(“Local/[email protected],2”, “1?skipblkvm”) in new stack
– Goto (macro-hangupcall,s,9)
– Executing [[email protected]:9] GotoIf(“Local/[email protected],2”, “1?theend”) in new stack
– Goto (macro-hangupcall,s,11)
– Executing [[email protected]:11] Hangup(“Local/[email protected],2”, “”) in new stack

We’ve noticed the same issue after upgrading to 1.4.24.1. Prior versions worked fine but call confirm fails after the upgrade.

Did you find out any resolution?

Rob

None yet… haven’t downgraded to test as I haven’t had the ‘midnight-hours’ time to test…

There is a proposed Asterisk fix for this, if you are having this issue it would be great to try and test out the patch. You can find it here, and feedback on the Digium bug system would be great, or if you can’t, at least report back here.

http://bugs.digium.com/view.php?id=14940

thanks!

tested this and it appears to fix the issue:)

Anybody see this bug reappear with Asterisk 1.4.25.1? I saw it fixed in a patch https://issues.asterisk.org/file_download.php?file_id=22356&type=bug for * 1.2.24 and it worked just fine . . .

I have confirmed that this particular patch is in pbx.c per the Digium issue tracker for 1.25.1

TIA,

JPS