- Joined
- Jun 9, 2021
- Messages
- 15
- Reaction score
- 2
Hello,
Recently we updated to v18, and since doing so, it seems every morning I get a call or email from our head receptionist that the main inbound queue has stopped sending calls to her phone, and the other phone the queue is assigned to ring to. Checking the logs, I see this error repeatedly:
Also, not sure if it's relevant, but the handsets they use are both SNOM D785.
Recently we updated to v18, and since doing so, it seems every morning I get a call or email from our head receptionist that the main inbound queue has stopped sending calls to her phone, and the other phone the queue is assigned to ring to. Checking the logs, I see this error repeatedly:
Rebooting the phones resolved this for a day, deleting and recreating the queue solved it for a day, but both times it went back to how it was the next morning. Prior to the update, there was no issue with the queue, and according to the webclient switchboard view, both extensions are logged into the queue. What might be causing this issue, and what solutions might I try?RTL:9612.3[Queue:80001] there's no route available to destination Extn:01015
[Flow] Target endpoint for 01015 is Extn:01015
Also, not sure if it's relevant, but the handsets they use are both SNOM D785.