I have a customer who is having an issue that I'm not sure how to solve just yet, and was wondering if I could get some opinions on what to look for.
Recently, this customer has had issues with their Attendant Console users where previously everything was working correctly. As of last week, logged in Attendant Console users were not having calls dispatched to the queue. Incoming calls were hitting the "always route" DN and getting forwarded to the Unity DN that plays the after-hours message, as though no attendant console users were logged in. No errors appeared upon launch of the AC application, and call control shows as up. They had their status set as online when this occurred. If an attendant took their phone off-hook during this issue, their DN showed as off hook in AC as you would expect it to. I had the customer restart the TCD service, and this got around the issue temporarily but it continues to occur several time per day, always requiring a restart of the TCD service.
I did not find any entries in the event logs of the publisher reflecting the service state change, but the TCD trace logs reflect a few lines that I think may point to the issue since they reflect an issue with JTAPI as it relates to the AC pilot point. I'm attaching the file. If anyone has any suggestions, please let me know. This is on CallManager 4.1.3 sr4d.