Hunt Group "Temporarily unavailable", Hunt Group functionality stops working after a while

[paulsk]

Set-up info:

• 3CX Version 18.0 (Build 965)
• Server OS Debian GNU/Linux 10 (buster) - Came with the 3cx iso
• Is the 3CX Server Hosted and where? On-Premises, VM
• IP Phone Make/Model/Firmware version, Yealink T46S
• Provisioning Method: Local
• Trunk Provider or VoIP Gateway Make/Model, Local telecom provider SIP VOIP trunk (tet.lv)
• Has the Firewall Checker passed: Everything passes, except for SIP ALG, that is confirmed to be turned off on our Mikrotik router, it has been that way since day 1 and worked fine for us so far.
• Are custom Phone Templates being used: No

In-going call set-up is somewhat like this: Customer calls our main DID, that is assigned to -> Call Flow App(ext.89), this determines a bunch of logic(time/date related) and then depending on circumstances forwards to either Ring group A(ext. 80) or Ring Group B (ext. 81).
Both ring groups are set-up as hunt-groups and have a "last-resort" forward to a different physical building(external number), if nobody picks up.

The problem: at some point the ring group virtual extension marks itself as "unavailable"(?) then all the calls go the "last resort" route to the different building. Rebooting the 3cx host fixes this for a few hours, then the problem reappears. I have verified both Ring Groups exhibit this behavior. Interestingly, doing the firewall check also reboots some services, but does not fix the problem like a full host reboot would.

I have attached an anonymized log file excerpt.

 

[leejor]

You said the calls were to go to extension 80, or 81, I assume, setup as dummy extensions (it would be interesting to see the options as to how these are set up). Why in the log does it mention Extension 11?

08/18/2022 12:15:00 PM - L:3.1[Line:10000<<++37125713031] failed to reach HuntGrp:81, reason Temporarily Unavailable
08/18/2022 12:15:00 PM - [CM503026]: Call(C:3): Route 1 to HuntGrp81[] is not active (Busy/Not registered)
08/18/2022 12:15:00 PM - [Flow] Target endpoint for 11 is Extn:11
08/18/2022 12:15:00 PM - [Flow] Call(C:3): has built target endpoint: HuntGrp:81 for call from L:3.1[Line:10000<<++37125713031]
08/18/2022 12:15:00 PM - [Flow] Target endpoint for 81 is HuntGrp:81

 

[paulsk]

Thanks for replying! Ext 11 is a receptionist, that's a member of the hunt group. 80 and 81 are indeed just ring groups, not regular extensions. I had a chat with the employees and looks like the issue has disappeared just as inexplicably as it appeared. I would have loved to get to the bottom of it, but looks like it's not reproducible for now.