We had a legacy v13 system that had been fine with conferences for years start doing this a few weeks ago. We went through the backup and restore to v15 last week and we have reports that it’s still happening. I think I caught a disconnect here, but I don’t know enough to discern. It seems to happen just 2-3 times per week, so watching and waiting is difficult.
Input on logging, monitoring, fixes appreciated.
-- Executing [425xxxxxxx@from-trunk:24] ExecIf("SIP/Bellevue-00000036", "1?Set(CHANNEL(hangup_handler_push)=crm-hangup,s,1)") in new stack
-- Executing [425xxxxxxx@from-trunk:25] Goto("SIP/Bellevue-00000036", "ivr-5,s,1") in new stack
-- Goto (ivr-5,s,1)
-- Executing [s@ivr-5:1] Set("SIP/Bellevue-00000036", "TIMEOUT_LOOPCOUNT=0") in new stack
-- Executing [s@ivr-5:2] Set("SIP/Bellevue-00000036", "INVALID_LOOPCOUNT=0") in new stack
-- Executing [s@ivr-5:3] Set("SIP/Bellevue-00000036", "_IVR_CONTEXT_ivr-5=") in new stack
-- Executing [s@ivr-5:4] Set("SIP/Bellevue-00000036", "_IVR_CONTEXT=ivr-5") in new stack
-- Executing [s@ivr-5:5] Set("SIP/BGIBellevue-00000036", "__IVR_RETVM=") in new stack
-- Executing [s@ivr-5:6] GotoIf("SIP/Bellevue-00000036", "0?skip") in new stack
-- Executing [s@ivr-5:7] Answer("SIP/Bellevue-00000036", "") in new stack
-- Executing [s@ivr-5:8] Set("SIP/Bellevue-00000036", "IVR_MSG=custom/Conference_IVR_04-23-19") in new stack
-- Executing [s@ivr-5:9] Set("SIP/Bellevue-00000036", "TIMEOUT(digit)=3") in new stack
-- Digit timeout set to 3.000
-- Executing [s@ivr-5:10] ExecIf("SIP/Bellevue-00000036", "1?Background(custom/Conference_IVR_04-23-19)") in new stack
-- <SIP/BGIBellevue-00000036> Playing 'custom/Conference_IVR_04-23-19.slin' (language 'en')
-- SIP/BGIBellevue-00000037 is ringing
-- Executing [s@ivr-5:11] WaitExten("SIP/Bellevue-00000036", "10,") in new stack