Call Confirm Issues?

Hey guys,
I don’t know if this is a new issue or not but all of a sudden over the weekend I realized that the call confirm in my queues has stopped working? It now just connects my calls directly to the first user that answers (instead of requiring to press 1 before connecting). I have tested it in the Find Me / Follow Me on the Extension level and that works :man_shrugging:. Could this be a bug???
I’m on FreePBX version 14.0.13.33 and Asterisk version 16.9.0

Here is part of the asterisk CLI log
Executing [[email protected]:3] Return (" PJSIP/XXX-0000104b ", “”) in new stack

Executing [[email protected]:20] Return (" PJSIP/XXX-0000104b ", “”) in new stack

Executing [Queue#@from-internal:30] Set (" PJSIP/XXX-0000104b ", " __CFIGNORE=TRUE ") in new stack

Executing [Queue#@from-internal:31] Set (" PJSIP/XXX-0000104b ", " __FORWARD_CONTEXT=block-cf ") in new stack

Executing [Queue#@from-internal:32] Set (" PJSIP/XXX-0000104b ", " __SIGNORE=TRUE ") in new stack

Executing [Queue#@from-internal:33] Set (" PJSIP/XXX-0000104b ", " __QC_CONFIRM=1 ") in new stack

Executing [Queue#@from-internal:34] GotoIf (" PJSIP/XXX-0000104b ", " 1?QVQANNOUNCE:NOQVQANNOUNCE ") in new stack

Goto (from-internal,Queue#,35)

Executing [Queue#@from-internal:35] Set (" PJSIP/XXX-0000104b ", " __FORCE_CONFIRM=PJSIP/XXX-0000104b ") in new stack

Executing [Queue#@from-internal:36] Set (" PJSIP/XXX-0000104b ", " SHARED(ANSWER_STATUS)=NOANSWER ") in new stack

Executing [Queue#@from-internal:37] Set (" PJSIP/XXX-0000104b ", " __CALLCONFIRMCID=XXX ") in new stack

Executing [Queue#@from-internal:38] Set (" PJSIP/XXX-0000104b ", " __ALT_CONFIRM_MSG=default ") in new stack

Executing [Queue#@from-internal:39] Set (" PJSIP/XXX-0000104b ", " VQ_CONFIRMMSG= ") in new stack

Executing [Queue#@from-internal:40] ExecIf (" PJSIP/XXX-0000104b ", " 0?Playback(, ) ") in new stack

Executing [Queue#@from-internal:41] QueueLog (" PJSIP/XXX-0000104b ", " Queue#,1591101683.6302,NONE,DID, ") in new stack

Executing [Queue#@from-internal:42] Set (" PJSIP/XXX-0000104b ", " QAANNOUNCE= ") in new stack

Executing [Queue#@from-internal:43] Set (" PJSIP/XXX-0000104b ", " VQ_AANNOUNCE= ") in new stack

Executing [Queue#@from-internal:44] Set (" PJSIP/XXX-0000104b ", " QMOH= ") in new stack

Executing [Queue#@from-internal:45] Set (" PJSIP/XXX-0000104b ", " VQ_MOH= ") in new stack

Executing [Queue#@from-internal:46] ExecIf (" PJSIP/XXX-0000104b ", " 0?Set(__MOHCLASS=) ") in new stack

Executing [Queue#@from-internal:47] ExecIf (" PJSIP/XXX-0000104b ", " 0?Set(CHANNEL(musicclass)=) ") in new stack

Executing [Queue#@from-internal:48] Set (" PJSIP/XXX-0000104b ", " QMAXWAIT=300 ") in new stack

Executing [Queue#@from-internal:49] Set (" PJSIP/XXX-0000104b ", " VQ_MAXWAIT= ") in new stack

Executing [Queue#@from-internal:50] Set (" PJSIP/XXX-0000104b ", " QUEUENUM=Queue# ") in new stack

Executing [Queue#@from-internal:51] Set (" PJSIP/XXX-0000104b ", " QUEUEJOINTIME=1591101684 ") in new stack

Executing [Queue#@from-internal:52] Queue (" PJSIP/XXX-0000104b ", " Queue#,t,300, ") in new stack

2 Likes

Please make sure your PBX is up to date.

Please post a full call trace using pastebin, instructions here: https://wiki.freepbx.org/display/SUP/Providing+Great+Debug#ProvidingGreatDebug-AsteriskLogs-PartII

Are you sending to an extension in queue or external cell phone number? Confirm only works with cell. You can try call as dialed and have the confirm on follow me but idk. Looks like youre ignoring call forwarding as well?

@PitzKey Thank you for your help below is a full call log of what happened.

https://pastebin.com/00ZZHtr0

@partgenius Currently in my test queue I only have a cellphone.

Have you tried suffixing a # to the end of your FMFM? Maybe to the extension in the queue? Have not tried these, but low effort.

+1
This is literally my same exact issue which started at the same time, about 2 days ago.
Using FreePBX 15.0.16.53
Asterisk Version: 16.9.0

Nothing changed with the queue, i created a new queue with the same settings. No joy.
I have 1 static agent, a cellphone number.

Call Confirm doesn’t work - the call just goes directly to the cell number.
I tried changing it to an extension to test - same issue regardless.

Help!

Looking at the log, this seems to be a bug.

Please try to update your PBX, and if it’s up to date, please report this bug: issues.freepbx.org

1 Like

Hi

from my testing and reports from customers its an issue with the email on outbound routes, Ive raised a Bug https://issues.freepbx.org/browse/FREEPBX-21565

and if you do the OPPOSITE to what is being said here but rever ‘core’ module back to 14.0.28.60 if on 14 ir what ever was core in 15 before teh change was made to add routes and all should work till bug is resolved.

1 Like

heres the dodgy code and example of console out put

14.0.28.61: FREEI-1284: added feature to send out an email when an Outbound Route is dialed

Works as no email macro
exten => s,n,Dial(${OUT_${DIAL_TRUNK}}/${OUTNUM}${OUT_${DIAL_TRUNK}_SUFFIX},${TRUNK_RING_TIMER},${DIAL_TRUNK_OPTIONS}b(func-apply-sipheaders^s^1))

Fails as email macro called
exten => s,n,Dial(${OUT_${DIAL_TRUNK}}/${OUTNUM}${OUT_${DIAL_TRUNK}_SUFFIX},${TRUNK_RING_TIMER},${DIAL_TRUNK_OPTIONS}b(func-apply-sipheaders^s^1,(${DIAL_TRUNK}))M(send-obroute-email^${DIAL_NUMBER}^${MACRO_EXTEN}^${DIAL_TRUNK}^${NOW}^${CALLERID(name)}^${CALLERID(number)}))

-- IAX2/TRUNK_out-11079 is making progress passing it to Local/[email protected];2
-- IAX2/TRUNK_out-11079 is making progress passing it to Local/[email protected];2
-- IAX2/TRUNK_out-11079 is ringing
-- IAX2/TRUNK_out-11079 is making progress passing it to Local/[email protected];2
-- Local/[email protected];1 is ringing
-- IAX2/TRUNK_out-11079 answered Local/[email protected];2
-- Executing [[email protected]:1] Set("IAX2/TRUNK_out-11079", "LOOPCOUNT=0") in new stack
-- Executing [[email protected]:2] Set("IAX2/TRUNK_out-11079", "__MACRO_RESULT=ABORT") in new stack
-- Executing [[email protected]:3] NoOp("IAX2/TRUNK_out-11079", "default and arv= ") in new stack
-- Executing [[email protected]:4] ExecIf("IAX2/TRUNK_out-11079", "1?Set(ARG1=)") in new stack
-- Executing [[email protected]:5] ExecIf("IAX2/TRUNK_out-11079", "1?Set(ALT_CONFIRM_MSG=)") in new stack
-- Executing [[email protected]:6] Set("IAX2/TRUNK_out-11079", "MSG1=incoming-call-1-accept-2-decline") in new stack
-- Executing [[email protected]:7] BackGround("IAX2/TRUNK_out-11079", "incoming-call-1-accept-2-decline,m,en,macro-confirm") in new stack
-- <IAX2/TRUNK_out-11079> Playing 'incoming-call-1-accept-2-decline.slin' (language 'en')



-- IAX2/TRUNK_out-82 is making progress passing it to Local/[email protected];2
-- IAX2/TRUNK_out-82 is making progress passing it to Local/[email protected];2
-- IAX2/TRUNK_out-82 is ringing
-- Local/[email protected];1 is ringing
-- IAX2/TRUNK_out-82 is making progress passing it to Local/[email protected];2
-- IAX2/TRUNK_out-82 answered Local/[email protected];2
-- Executing [[email protected]:1] GotoIf("IAX2/TRUNK_out-82", "0?sendEmail") in new stack
-- Executing [[email protected]:2] NoOp("IAX2/TRUNK_out-82", "email notifications disabled..exiting.") in new stack
-- Executing [[email protected]:3] MacroExit("IAX2/TRUNK_out-82", "") in new stack
-- Local/[email protected];1 answered SIP/2000-00000074
-- Stopped music on hold on SIP/2000-00000074
-- Channel IAX2/TRUNK_out-82 joined 'simple_bridge' basic-bridge <2b2a3557-a8c7-4ab9-b671-98641b101a3a>
-- Channel Local/[email protected];1 joined 'simple_bridge' basic-bridge <d601f7bc-22ad-4bfa-b042-f8d1d7b6d2b8>
-- Channel Local/[email protected];2 joined 'simple_bridge' basic-bridge <2b2a3557-a8c7-4ab9-b671-98641b101a3a>
-- Channel SIP/2000-00000074 joined 'simple_bridge' basic-bridge <d601f7bc-22ad-4bfa-b042-f8d1d7b6d2b8>
1 Like

I have just tested the extension level Call Confirm and that does work.

Thanks @cyberco for submitting the report.

Seems to work ok for followme and ringgroups
Seems that it’s queues that’s affected

We too have just discovered this issue. Our instance is entirely untouched except for automatic updates (More or less set and forget). Realised last week that the Call Confirm messages were not playing nor prompting to hit 1 to accept, 2 to decline or 3 for caller ID. Before I touched anything it was calling, but not playing any messages (You could still hit 1/2/3 to perform said action). I then restarted the entire server and now its just directly connecting the calls (No configuration changes). It is affecting all 4 Queues that are setup identical (all on 4 different inbound routes, with differences only in who the calls are forwarded to and some time conditions).

We’re on PBX: 15.0.16.53 with System Version: 12.7.6-2002-2.sng7. All modules were up to date when I performed a check just prior to posting this.

This was our last set of major updates from the update email sent by our system on 23/05/2020:

There are 26 modules available for online upgrades
areminder 15.0.14.22 (current: 15.0.14.20)
asteriskinfo 15.0.10 (current: 15.0.9)
backup 15.0.10.3 (current: 15.0.8.94)
callback 15.0.9 (current: 15.0.8)
certman 15.0.23 (current: 15.0.22)
core 15.0.12.8 (current: 15.0.9.94)
endpoint 15.0.27.23 (current: 15.0.27.16)
faxpro 15.0.8.9 (current: 15.0.8.8)
filestore 15.0.3.8 (current: 15.0.3.7)
framework 15.0.16.52 (current: 15.0.16.49)
miscdests 15.0.2.10 (current: 15.0.2.9)
paging 15.0.4.22 (current: 15.0.4.21)
pagingpro 15.0.1.19 (current: 15.0.1.16)
parking 15.0.15.1 (current: 15.0.15)
parkpro 15.0.12.7 (current: 15.0.12.6)
pms 15.0.2.47 (current: 15.0.2.45)
queues 15.0.18 (current: 15.0.17)
recording_report 15.0.4.25 (current: 15.0.4.24)
restapps 15.0.19.4 (current: 15.0.19.3)
sangomacrm 15.0.14.44 (current: 15.0.14.43)
sipsettings 15.0.6.27 (current: 15.0.6.25)
sms 15.0.6 (current: 15.0.4)
sysadmin 15.0.13.19 (current: 15.0.13.18)
userman 15.0.28 (current: 15.0.23)
vmblast 15.0.11.4 (current: 15.0.11.3)
voicemail 15.0.18.14 (current: 15.0.18.13)

Hi anyone having the issue check https://issues.freepbx.org/browse/FREEPBX-21565 as there is a fix on the edge track now.

Testing this has flagged an issue with the route email agi https://issues.freepbx.org/browse/FREEPBX-21587 but thats a simpel fix for now just remove the @on line 102

1 Like

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