Forum Discussion
Caller ID
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 SaleemJan 31, 2017Microsoft Can this help? https://support.office.com/en-us/article/Set-the-Caller-ID-for-a-user-c7323490-d9b7-421a-aa76-5bd485f80583 - Jose MartinezJun 13, 2017Copper ContributorWe 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.
- Geoffrey PlankFeb 01, 2017Brass ContributorThat 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. - Mohamad SaleemFeb 01, 2017Microsoft Really appreciate your feedback. I am involving the necessary teams to have a look and fix. Also please follow the support ticket for fix resolution. Thanks again! 
 
- Danny SmithJan 31, 2017Copper ContributorDoes this only work with on-prem or can it be used for cloud based sfb? If it can be used for cloud based sfb am i required to use powershell? - Mohamad SaleemJan 31, 2017Microsoft yes, this for online and needs to be configured through Remote powershell.