Forum Discussion
Call Queues Preserving CallerID
We don't seem to be able to get the queue name to appear.
ITs good that we now get the caller number but under it we still have the GUID.
In the SfB Adim centre the queue names have an active directory error against them.
I have edited them and saved them but the AD error is still there!!
Any ideas??
Regards
James Lupton
Fixed now. After literally deleting the policy and recreating it over the course of 2 weeks (about 10 times deleting and recreating it), it finally stuck.
My outgoing caller ID still isn't working. Going on 2 weeks now with open ticket...
- I'm seeing this same issue. Was this resolved by you?
- https://techcommunity.microsoft.com/t5/Skype-for-Business-Blog/Announcing-new-capabilities-in-Auto-Attendant-and-Call-Queue/ba-p/122962/jump-to/first-unread-message#toc-hId-253362254
describes your warning message. you are in an split domain topology. see https://support.office.com/en-us/article/Set-the-Caller-ID-for-a-user-c7323490-d9b7-421a-aa76-5bd485f80583 under "Verify and start Windows PowerShell" how to connect your powershell to sfb online
Import-Module "C:\Program Files\Common Files\Skype for Business Online\Modules\SkypeOnlineConnector\SkypeOnlineConnector.psd1"
$credential = Get-Credential
$session = New-CsOnlineSession -Credential $credential
Import-PSSession $session
than you can run commands like new-cshybridapplicationendpoint and so on. i dont think this is the solution to your problem, because the call queues should work just fine in an online only enviroment.edit: sorry new-cshybrid... command is not for sfb online but for hybrid, like the command itselfs say.
Working as well here. I elevated this issue pretty high earlier in October and was told the fix was coming before the end of the year. Glad to see they followed through.
BUT! After Microsoft made the fix, they broke my outgoing caller ID settings. I have it set to display our main line (service number) as everyones outgoing caller ID (versus the Line Uri or Blocked). When Microsoft made this update, they broke this functionality. I have a ticket in, but wondering if any one else is having the same issue? Blocked and Line Uri are the only settings working at the moment...
OK got the phones back - The New Call Queue was not linked in with the auto attendant.
Having set up a new call queue, this now also has an AD error and is requesting a cmdlet to be run in powershell however, we do not have an on-premises system so what location are we meant to access with PowerShell??
Surely this should just work. It is certainly very unclear what we should do to get the Call Queue working properly.
Just lost all our phones - can't call into the office
What is going on!!
I don't see the user named as the calling queue and therefore can't edit that.
I have set-up a new caling queue but still get the same error message
- in the admin interface -> user overview, do you see a ne generated user with the queue name and the hg_XXX@yourdomain.com email? try to edit and save the queue, and see if the user is generated. if not, try to delete and recreate the queue.
Call support or try recreating it from scratch.
WE do not have an on-premises system just the online version. So not sure where we should powershell from or too!!
WE do not have an on-premises system just the online version!!
