Will this be incorporated into the VVX client? In this case is a VVX401 running 126.96.36.19968 but still displays GUID.
The Windows client does display the call group name.
Proper caller ID in SfB client toast for calls routed via Call Queue (and Auto Attendant): until now, caller ID for calls routed via Call Queue to the SfB client for Windows was not properly rendered (the Call Queue identifying GUID was displayed instead). With this new capability of the Windows client, the toast will appropriately indicate (when known) the caller’s originating phone number or user name, and the Call Queue name.
Please raise this via your Polycom reseller as a feature request via a Polycom sales engineer and provide a business proposal why this would be required.
Above is necessary in order to track this internally within Polycom and evaluate the request and prioritize this based on the feasibility and the general impact on other features.
Please ensure to provide some feedback if this reply has helped you so other users can profit from your experience.
Polycom Global Services
My Skype For Business Windows client shows the name of the queue when the call is from an outside phone, or the GUID (e.g. hg_3ea6f1f...) when the call is from another SfB Windows client.
Skype For Business Android client shows the queue name in both cases.
Can anyone provide an regarding what they see on their VVX phones for Caller ID with an incoming Call Queue call?
Is anyone any workaround to display the queue name instead of the SIP URI
On my Skype for business application I get the proper queue name where as on the VVX it shows the SIP URI. I even tried to add that SIP URI as contact but still outcome is same
I have tested on VVX 411, VVX 501, VVX 301 with ver 5.8.0 with same outcome