05-16-2017 03:47 PM
05-16-2017 03:47 PM
We have set up a couple of Call Queues on Skype for Business online for one of my customers. It works ok, however there is an annoyance:
Incoming calls show the toast with a long name:
That name is the PrimaryUri of the hunt group.
In the on-prem version I am able to change that using PowerShell. However when using the LyncOnlineConnector, the Set-CsHuntGroup cmdlet uses the PrimaryUri as identifier, so there is no way to change it with that command.
Anyone has figure out how to change it the PrimaryUri of a call queue?
05-18-2017 06:11 AM
01-15-2018 05:31 PM
Haven't tried changing the GUID recently because the toast for incoming call shows my Call Queue Name now vs. Guid. MS updated Call Queues in November 2017. You might want to check out their YouTube channel for updated content on subject; https://www.youtube.com/watch?v=Qvoga8A0CbA
07-19-2018 05:27 AM
I have the same Problem. All created HuntGroups have this long an crazy Name. I can not find any way to change that. This is very sad.
I have opened a Microsoft Ticket and I am waiting for a Statement.
07-23-2018 05:38 AM
This is actual a bug. Microsoft is working on a solution. The Workarround is to add the SIP Address as Contact in your Buddylist. After that, the Diplay Name is presented. Or create a Outlook contact with that SIP-Address and give the contact the Name you want.
11-29-2018 11:20 AM - edited 11-29-2018 11:22 AM
Could you elaborate on how you did this? I've tried adding both the Call Queue contact to the S4BO contact list and creating a contactt in Outlok and have had no luck.
11-29-2018 01:34 PM
11-29-2018 01:51 PM - edited 11-29-2018 01:56 PM
Under the Outlook contact, did you specify the full address as "sip:firstname.lastname@example.org" or just "email@example.com"? Where did you specify the name? Under "Full Name" or "Display as" or both? Also does your Outlook contact share the same exact name as the Call Queue?
Thank you for your help!
11-29-2018 06:32 PM
03-29-2019 06:16 AM
@Leah_Hughes Unfortunatley not, this is a polycom specific bug. They are aware of the issue and are working on a fix in an "upcoming update".
04-17-2019 05:05 AM
EN-120233 should be resolved in firmware version 5.9.2 (https://community.polycom.com/polycom/attachments/polycom/VoIP/25695/1/uc-software-release-notes-5-9...
I've not been able to test it yet...
04-17-2019 05:38 AM
@Jef Vleugels So far so good. This is a great quality of life improvment!!!
by Voravut on May 13, 2020
by ThaiLam on May 08, 2020
by Greg Whitworth on May 07, 2020
by Corbin Meek on April 08, 2020
by Hiren_Shah on March 19, 2020
by Corbin Meek on January 13, 2020