Not a good day for 3cx here. We upgraded to V8 Friday, all seemed to go well. This morning got reports we weren't getting any calls, customers getting upset, but outbound calls are no problem. I tried calling in from my cell, just rings, no IVR pickup. Thought it was the Grandstream 4104, rebooted, the same. Looked at 3cx admin console, noticed the System extensions for the IVR where not regeistered. Looked at services, IVR running, restarted it, IVR now working and answering properly. IVR Logs show these errors repeating during the time it wasn't answering (phone numbers readacted): 17:07:12.519|8868|(0):Error! Module '3CX.com.OSBinet'. Error ID 302. URLhttp://localhost:5484/(S(xt3n2hrct2uwtz550xss0pep))/dr.aspx?dr=806&to=806&from=XXXXXXXXXX 17:07:43.488|8868|.\api\VXItelImpl.cpp(148):IvrDll, VXItelImpl::Impl::IntrnTransfer(), Error! Error of 'From_XXXXXXXXXX_To_806_Menu_806_#0/62' session transferring to sip:firstname.lastname@example.org:5060. Status: NEAR_END_DISCONNECT. Transfer error. Session stopped 1. Any Ideas? 2. Can we have the inbounds fall back to an operator extension should the IVR not pickup for any reason? 3. Any plans to have a watchdog service to monitor and restart any hung 3cx service, or perhaps on a schedule? We may setup a nightly restart of the IVR service as we did with the fax service in V7 because of stability issues. We may revert back to V7 if this happens again, as the upgrade to V8 was for stability improvements(specifically with fax), but the IVR is critical and never had issues in V7.