Might be worth trying 802.11r if your devices and access points support this. On unifi dashboard this is fast roaming. We have found that some customers this works better with than others so could definitely be worth an experiment
Have you tried the set all departments to holiday mode call script, and then limit to department at the bottom? This may work, i havent tried this myself however.
I have also experienced this issue, havent managed to find the cause or resolution. We ended up having to provision behind another sbc to get the device to register again.
Some customers yealink T54W on firmware 96.87.0.16 are showing the incorrect time. Looks like they have gone into DST time a week early. Anyone know how to recify this without having to manually go into each devices web gui?
Cheers
Hi Stuart,
We have had a few issues with the AX83H wifi phones being a router phone. We find that if we put them behind another hardwired router device or SBC we have much greater stability and quality
In the UK create a rule starting with 0, this means that any call to a uk mobile or landline should work. For international calls in the UK create a rule with 00. Assign this to your SIP trunk under route 1
You could try creating a department for this specific queue then have the log out of queue script in integrations assigned to that specific department. I havent tested this myself but may work
You do not have to assign a DID to a script to play a holiday message, leave the DID assigned to where it was, and have the holiday script run Upon recieving a call on a trunk.
if each indivudal board member has a DDI, send to Queue/ RG , then set the destination if no answer to forward to another queue with the secretaries in. Have this queue named as the name of the board member then this will display the queue name when the secretaries are called
We had a similar issue. For us the fix turned out that we couldnt use the Yealink AX83H's as router phones. We were getting lots of errors in the SBC logs. We we routed them behind a router phone on the LAN, this issue resolved itself.