Hello All, Can the caller ID info for all users be the service number for the company? Dont want people calling back the number they see on the caller ID. Trying make sure all calls go through the auto attendant. We have nothing ON-PREM everthing is in the cloud for us. Thanks.

I second this request. Having the ability to manipulate outbound CallerId's would be a very nice feature to have, either to point at an OnPrem IVR, an Third Party IVR or a Skype Online IVR.

That support page regarding Caller ID needs to be updated. It was recently edited by someone to remove old PowerShell cmdlets, but they never added the new ones that would allow you to assign a Service number (like used for AA) to all users as their caller ID. Just read in the lead-in....it talks about changing the caller ID of users to a Service number, but the instructions and example are only about how to make the caller ID anonymous for all. This seems sloppy and I would expect more from Microsoft. Additionally, this evening I received confirmation that the new Caller ID PowerShell cmdlet are not working yet and SfB beta tech support looking into it. They said: "the code release is lagging behind the cmdlet release and engineering is investigating this." So, I guess just stay tuned. But what is frustrating is that a listing of the necessary cmdlets and instructions for working with Caller ID are not available anywhere online -- that is, except for the few on that incomplete page. I've been learning by trial and error, along with some help from tech support. This is such a basic need for anyone deploying SfB Cloud PBX company-wide. I just don't get why this appears to be such a difficult thing to implement...it should not require PowerShell, but be implemented and controlled from within the 365 tenant.

@Geoffrey Plank Thank you so much for this write-up! Mohamad SaleemThe entire section that Geoffrey wrote up about setting an outbound CID to a service number is not live on the page you referenced. That page omits what is below and only gives instructions on how to set your CID to anonymous (I had to come find this documentation by Geoffrey to get my company up and running): To Get Office 365 and CallerID Settings Info on an user: Get-CsOnlineUser -Identity "amos.marble@contoso.com" New-CsCallingLineIdentity – Creates a new Line Identity named “MainNumber” with a Service Number:New-CsCallingLineIdentity -identity MainNumber -Description MainNumber -Tenant xf4ddfe5-c94e-4418-a881-0e8bfXXXX6b -BlockIncomingPstnCallerID $false -CallingIDSubstitute Service -ServiceNumber 1XXXXXXXXXX New-CsCallingLineIdentity – Creates a new Caler ID policy for setting CallerID to Anonymous:New-CsCallingLineIdentity -identity MainNumber -Description MainNumber -Tenant af4xxxfe5-c94e-4418-a881-0exxxx6086b -CallingIDSubstitute Anonymous Set-CsCallingLineIdentity – Change an existing Caller ID Policy called "MainNumber" to use a different Service Number or Change from Anonymous to a Service number:Set-CsCallingLineIdentity -identity MainNumber -CallingIDSubstitute Service -ServiceNumber 1XXXXXXXXXX Grant-CsCallingLineIdentity– Assign Caller ID policy "MainNumber" to a user (need to refer to it as a “-PolicyName”):Grant-CsCallingLineIdentity -PolicyName MainNumber -Identity amos.marble@contoso.com –Tenant "af4dxxxx-c9xe-4418-a881-0e8bxxx086b" Remove-CsCallingLineIdentity - To remove an existing CsCallingLineIdentity policy (i.e, one named MainNumber):Remove-CsCallingLineIdentity -Identity MainNumber

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:LineuritestDescription : LineUriTestEnableUserOverride : FalseServiceNumber : +14707050225CallingIDSubstitute : LineUriBlockIncomingPstnCallerID : FalseRemove-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.

Can this help? https://support.office.com/en-us/article/Set-the-Caller-ID-for-a-user-c7323490-d9b7-421a-aa76-5bd485f80583

Caller ID | Microsoft Community Hub

27 Replies

David Wells
Copper Contributor
May 08, 2017
Is it possible for me to display the username and extension in the caller ID? For example 'First Last x1234'? Maybe the feature is on its way?
Mike Essen
Copper Contributor
Jan 31, 2017
I second this request. Having the ability to manipulate outbound CallerId's would be a very nice feature to have, either to point at an OnPrem IVR, an Third Party IVR or a Skype Online IVR.
- Mohamad Saleem
  Microsoft
  Jan 31, 2017
  Can this help? https://support.office.com/en-us/article/Set-the-Caller-ID-for-a-user-c7323490-d9b7-421a-aa76-5bd485f80583
  - Jose Martinez
    Copper Contributor
    Jun 13, 2017
    We received help from the OFFICE 365 Help Desk to assign our outbound caller ID for all users to be the Service number assigned to the Auto Attendant. It was not an easy process, and I had to get step-by-step help while using the PowerShell commands. At the end of the very long call, we tested the outbound caller ID, and it had worked. Unfortunately, two days later our outbound calling service stopped working for all user accounts and while using all devices (PC App, IOS App, and VoIP SfB phone). We have opened multiple tickets since June 1, 2017 (Office 365 Ticket #30126-5884593, Office 365 Ticket #30126-5866774, and Office 365 Ticket #30126-5265402) and the Tier 1 agents have troubleshot everything they could think of at their level. Initially, we were told the issue was a system-wide outage, but we have received conflicting emails from the Office 365 Support team indicating that in fact the issue was fixed on June 3, 2017. As of today Tuesday, June 13, 2017, the issue has not been fixed, and we have experienced a continuous outage on all outbound calling capability. We suspect the issue was brought on by the PowerShell Caller ID changes, but even attempting to remove the Service number from the Caller ID has not fixed the issue. At this point, our small staffing & recruiting company has suffered the consequences of relying on a single service that in fact has not provided us with the 99.9% uptime SLA and we have received NO HELP from the Microsoft Tier 2 or higher Engineers. At best we have received email responses at 1:02 AM because I guess it makes too much sense to conduct business during your client's hours of operation. We are extremely disappointed with the Skype for Business PSTN service.

Forum Discussion

Caller ID

27 Replies

Resources