ContributionsMost RecentMost LikesSolutionsRe: Desk phone no longer rings for Queue calls Thanks for the follow up. In my original description, I indicated the agents were ONLY logged in to the queues via the Soft Phone, not the Desk Phone, and yet the Desk Phone rang at the same time as the Soft Phone when a queue call came in.The queue's Ring strategy was set for 'Longest call wait'. Unfortunately, the behavior no longer works since the update, so there is no way to confirm it again now. It might be possible there was a misunderstanding with how things were ringing. Thanks for checking on any changes. I did find something interesting in testing, which you alluded to in your last reply. You indicated that all devices logged into the queue should ring in a Ring strategy of 'Ring All' setting. We use 'Longest call wait' setting and while testing for the above conditions, I noticed that the Desk Phone and the Soft Phone, when both logged into the same queue under the same extension appeared like two separate agents. That is, an incoming call to the queue considered the Desk Phone a separate user, ringing it first, while the Soft Phone remained silent. The next test call to the queue rolled over to the Soft Phone while the Desk Phone remained idle. I'm wondering if you can confirm this is the expected behavior for this setup/testing. Desk phone no longer rings for Queue calls Prior to the last update we had users whose Desk Phone would ring at the same time as their Soft Phone when they received a call in Queue. These users were logged into the queue via their Soft Phones only. Some of our agents prefer the Desk Phones and others the Soft Phones so all stations have both. Desk Phones are Yealink T54W, Soft Phonev4.2.1 Those who used the Soft Phones had a quick backup in case they had any problem with their headsets, they could just pick up a Hard Phone handset to answer a queue call. After the update, both phones appear to ring for direct calls to their extension, but not when the call comes in via a call queue. Was something updated that changed this behavior?