FreePBX | Register | Issues | Wiki | Portal | Support

Queue with FollowMe - Too Late. Bug?

(Itzik) #1


In a recent update, if you have a virtual extension in a queue with follow me and confirm calls enabled, once you press 1 to accept the call, you get the “too late announcement”. So to reproduce this, I went to a server that the modules weren’t updated yet:

Call trace:
macro-confirm in extensions_additional.conf:

Everything works great.

I went ahead and updated the modules to:
framework 14.0.11

Now it’s not working…
Call trace:
Looking at the call trace you see:

[2019-05-15 08:13:24] VERBOSE[5550][C-0000908d] file.c: <Local/12128885500@from-internal-000064ab;1> Playing 'incoming-call-1-accept-2-decline.slin' (language 'en')
[2019-05-15 08:13:24] VERBOSE[5580][C-0000908d] bridge_channel.c: Channel SIP/AdTran-Primary-000109c2 joined 'simple_bridge' basic-bridge <79b06009-1719-4706-8d1e-d6bc1a0733e7>
[2019-05-15 08:13:24] VERBOSE[5559][C-0000908d] bridge_channel.c: Channel Local/12128885500@from-internal-000064ab;2 joined 'simple_bridge' basic-bridge <79b06009-1719-4706-8d1e-d6bc1a0733e7>
[2019-05-15 08:13:28] VERBOSE[5550][C-0000908d] pbx.c: Executing [1@macro-confirm:1] GotoIf("Local/12128885500@from-internal-000064ab;1", "1?toolate,1") in new stack
[2019-05-15 08:13:28] VERBOSE[5550][C-0000908d] pbx_builtins.c: Goto (macro-confirm,toolate,1)
[2019-05-15 08:13:28] VERBOSE[5550][C-0000908d] pbx.c: Executing [toolate@macro-confirm:1] Set("Local/12128885500@from-internal-000064ab;1", "MSG2="incoming-call-no-longer-avail"") in new stack
[2019-05-15 08:13:28] VERBOSE[5550][C-0000908d] pbx.c: Executing [toolate@macro-confirm:2] Playback("Local/12128885500@from-internal-000064ab;1", ""incoming-call-no-longer-avail"") in new stack
[2019-05-15 08:13:28] VERBOSE[5550][C-0000908d] file.c: <Local/12128885500@from-internal-000064ab;1> Playing 'incoming-call-no-longer-avail.slin' (language 'en'

macro-confirm in extensions_additional.conf:

So I compared both macros and the only difference is on line 12.

exten => 1,1,GotoIf($["${DB_EXISTS(RG/${ARG3}/${UNIQCHAN})}"="0" & "${SHARED(ANSWER_STATUS,${FORCE_CONFIRM})}"=""]?toolate,1)


exten => 1,1,GotoIf($[$[("${DB_EXISTS(RG/${ARG3}/${UNIQCHAN})}"="0") | ("${SHARED(BLKVM,${UNIQCHAN})}"="")] & "${SHARED(ANSWER_STATUS,${FORCE_CONFIRM})}"=""]?toolate,1)

So in a attempt to fix things on my own, I went ahead a replaced the “|” with a “&”, like this:

exten => 1,1,GotoIf($[$[("${DB_EXISTS(RG/${ARG3}/${UNIQCHAN})}"="0") & ("${SHARED(BLKVM,${UNIQCHAN})}"="")] & "${SHARED(ANSWER_STATUS,${FORCE_CONFIRM})}"=""]?toolate,1)

Ran core reload, tested a call, and now I am able to take calls again.
Is this a bug?


(Matthew Jensen) #2

I’m pretty sure this is a bug. I’m experiencing a similar (and I think related) problem also on The problem is that the bug report got closed as a duplicate of a bug that was fixed in But if you look at both bug reports, they are describing opposite problems. I think the fixing of one caused the other.

The initial problem which is not the same as yours:
Your problem, but it is no longer being fixed:

Further details from a post I made here:

(Itzik) #3

Fixed in core

(system) closed #4

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.