Forum Discussion
Caller ID
Appreciate the updates to the article!!
I've been following this as I've been helping customers directly on this. You could say this is a letter from the "front lines".
In my observations I noticed several difficulties though.
When customers have used the example for adding a LineUri and the tag for the policy is "LineUriTest" it was next to impossible to remove this policy. (Still trying to figure out how I'll remove it, see output below. I was however able to remove another policy that had a service number assigned. This policy Lineuritest was created by a customer with a user number and labeled LineUri. I recreated it in my tenant, and have reproduced the issue)
Identity : Tag:Lineuritest
Description : LineUriTest
EnableUserOverride : False
ServiceNumber : +14707050225
CallingIDSubstitute : LineUri
BlockIncomingPstnCallerID : False
Remove-CsCallingLineIdentity -Identity LineUriTest Set or Remove host tag instance is not allowed + CategoryInfo : NotSpecified: (:) [Remove-CsCallingLineIdentity], ArgumentException + FullyQualifiedErrorId : System.ArgumentException,Microsoft.Rtc.Management.Internal.RemoveCallingLineIdentityCmdlet + PSComputerName : admin2a.online.lync.com Remove-CsCallingLineIdentity -Identity "Lineuritest" Set or Remove host tag instance is not allowed + CategoryInfo : NotSpecified: (:) [Remove-CsCallingLineIdentity], ArgumentException + FullyQualifiedErrorId : System.ArgumentException,Microsoft.Rtc.Management.Internal.RemoveCallingLineIdentityCmdlet + PSComputerName : admin2a.online.lync.com
What I also noticed is there's not a cmdlet that would allow you to filter and find users utilizing a policy. You are relegated to use Get-CsOnlineUser and filter.
Also as a suggestion from being on the Concierge team, there's been a number of customers from small to medium sized businesses, that don't have the resources of someone with expertise in PowerShell to manage their users. It's a common complaint as to "why isn't there an interface for this?"
It might be best to add Caller ID amangement (since it's been a common request lately) to the Skype (for Business) admin center. This way customers can manage and apply those policies with ease.
In additon most customers we encounter don't have MsOnline Sign in assistant, AzureAD modules, then Skype for Business Modules installed, not to mention most Windows 7 users have not updated their PS to the correct version.
These tools in PowerShell are very handy and great for admin's with PS experience like myself, but for Medium to Small Business, this is quite the hill to climb in adopting these features. I'm not sure if there's an existing UserVoice on this but this would be extremely beneficial to the small and medium sized business sectors.
- TJ CornishApr 13, 2017Brass Contributor
Nathan, you're being very polite.
We have been working for two years to implement Skype For Business for our small company. Dialtone is relatively easy; doing normal PBX things (tenant dial plans, music on hold, caller ID manipulation, multiple line appearances, call park, etc.) is either not easy, or was until very recently or is still impossible.
I remember sitting in Tech Ed 2006 in a session about Office Communications Server, where the presenter demonstrated a phone ringing, and then - wait for it - he answered the call. Much ooing and aahing. We're 11 years on from that early attempt and are still begging for basic things to work (call park!?)
This will eventually be good, but calling the current state of MS Cloud PBX "bleeding edge" is being kind. Our cutover date is next week - God help me.