Microsoft has updated the Teams admin center and you can now create the Shared Calling policy without PowerShell. BUT, I don't see a way to enable voice for users without PowerShell. To create Shared Calling Policy: Go to Voice > Shared calling policies. Select Add to create a new Shared Calling policy. Enter a unique name and description for the policy. Select the resource account that you want to use for this policy. Select Add emergency callback numbers. From the side panel, select the Phone number type and Assigned phone number. Once you've added the emergency callback number, select Add. Select Save.
Hi i followed your instruction and got the user setup fully i can receive call with the autoattendant but i try to make a call i get that i am not setup to use this calling feature any assistance will be appreciated
I would check that no step was missed. That's what I would do if you would schedule a remote IT support call. Common issues is wrong licensing, not enabling voice, and not enabling billing properly. Of course, could be an issue with setting the Shared Calling policy itself.
This is an excellent step-by-step, thank you! I am trying to select a toll-free auto-attendant phone number but I'm getting the "you don't have enough credits..." message. In my licenses I have 10000000 available licenses next to Communications Credits. What am I doing wrong? I want to have a 800 or 888 or similar number.
It basically means you’ve configured something wrong. Most likely a licensing issue or did not turn on billing properly. Also check that you enabled enterprise voice for the user.
Thanks Bogdan. We received this error from the code in step 6. Any ideas what we're doing wrong? Set-CsPhoneNumberAssignment : Cannot process argument transformation on parameter 'LocationId'. Cannot convert value to type System.String. At line:4 char:41 + ... eNumberAssignment -LocationId $CivicAddress.DefaultLocationId -PhoneN ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : InvalidData: (:) [Set-CsPhoneNumberAssignment], ParameterBindingArgumentTransformationEx ception + FullyQualifiedErrorId : ParameterArgumentTransformationError,Set-CsPhoneNumberAssignment
It's difficult to troubleshoot this just for this alone. It might be as simple as an extra space or location may not match. We might be able to figure it out in a 30 minute call. Reach out using the link in the description.
You mentioned in the video that a company that does a lot of calling can get a pre-paid calling plan instead of pay-as-you go. What is the name of the prepaid calling plan and can it still be shared?
The limitations now are that you have to use a PAYG calling plan with the Main Auto Attendant phone number that you set up that will be used for the Shared Calling. At least for the US and the UK. If you really need a lot of outbound calling, consider just getting direct numbers for users. It's much easier to set up as well. Depending on the size of your team, some users can have direct calling (DID) phone numbers with standard domestic calling plans and other users can be on a Shared Calling Plan that has a PAYG plan attached to it.
You can port in your existing number to Microsoft. The emergency callback is included from Microsoft with your license. It’s used for Shared Calling Plan because users don’t have unique (direct) numbers. So that emergency number is used if a user on the Shared Calling Plan calls 911. Point is, that number is not customer-facing and doesn’t need to (and can’t) match your main business number
Thank you for that step by step explanation. I believe the Shared Calling Policy GUI is working now. But it is in the new main menu "Settings and policies" at the top, not below Voice.
They changed the gui recently, you still have the old. policies are moved for the whole of teams and are now all together under a main menu Setting and Policies. No longer under voice
It’s in the video description. Let me know if you need more clarity on that. There’s only one number but you can easily setup additional number to forward to one auto attendant. Setup another auto attendant and there will be an option to redirect the call to the main auto attendant.
Hello. On my company we just need to use outbound calls. Can I use Shared calling? We will not have auto attendant, just a group of users who will call to users. Thanks
Yes, Shared Calling Plan would work for that. You'll still setup an auto attendant. Just a placeholder. There's no cost savings in not having an inbound phone number.
@ApexOneTech So, create an auto attendant still. And calling plan would be pay as you go, communication credits or a normal phone plan? And at the end define a call policy. Is that correct? Sorry for all questions. Thanks in advance
Hi Bogdan- does this have to be a pay as you go calling plan? Using NTS as plan provider and getting ready to set this up for several customers using same provider.
No, doesn’t have to be pay-as-you-go. That’s just one of the two calling plans if you use Microsoft as your PSTN carrier. PAYG is most cost effective. I’m not familiar with NTS, but with Teams Phone, there are basically to other main options for calling PSTN carrier rather Microsoft: 1, using your own carrier with Operator Connect or 2, using own carrier with Direct Routing. There’s a great PDF from Microsoft here: learn.microsoft.com/en-us/microsoftteams/cloud-voice-landing-page
Had this working inbound and outbound for two different customers with Temp Numbers provided by Direct Routing company while waiting for my customers numbers to be ported into that same company- as soon as the numbers were ported in - we unassigned the temp numbers and replaced with newly ported in numbers and it broke everything. I have since setup the companies all over again with teams phone shared calling and performed identical steps for both- however now One company works for inbound and outbound shared calling with no problem, and the other company only inbound is working- Outbound using teams is not working and gives the message about the user not licensed for anything outside of the organization. Any thoughts on what I can check - a step i might have missed specific to outbound- I have done the EnterpriseVoiceEnabled repeatedly for the user I am testing- no dice!
what the hell is this BS from MS? I just want to add a phone number for the company so that customers can ring me. I want that to be connected to teams. Why the hell do I need to use powershell for that? This is the most awkward MS nonsense ever.
lol I know. This is only if you want to use the Shared Calling Plan. You don’t have to go this route. It’s much simpler to just use direct numbers. You set up an Auto Attendant, attach a voice app number to it, and now you can use that as your business number and as your caller id when you dial out.
@@ApexOneTechI'm applying this shared plan, because it cheaper but also because there was absolutely no way I managed to keep the outbound caller ID the main phone number when having ddi/call plan per user. Some people would see my main number, some people would see my ddi nummer when calling them. No logic in it why. Also can't get pay-as-you-go call plan with an NCE sub working. I have a ticket open for 4 months now, but they are not really responsive or helpful. Sounds like there's are no credits on it, but the whole point of the nce plan is to pay afterwards.
@@DJIrvinCee You can get everyone who has a direct plan to also have the main business phone number caller ID by creating a Call Queue. That's probably the easiest way so far.
Yes, you can set up extension numbers in Teams Phone in general. However, I haven't done so with a Shared Calling Plan. But I do plan to make a future video on extensions. This may be helpful to you if you need to do this right away: techcommunity.microsoft.com/t5/microsoft-teams/dialing-by-extension/m-p/4002624
I would also enjoy a video on setting up extensions. I've tried a few things and the dial by extension is not working as expected (Except for on an Iphone). Currently have a ticket open with Microsoft to see why it isn't provisioning.
Microsoft has updated the Teams admin center and you can now create the Shared Calling policy without PowerShell. BUT, I don't see a way to enable voice for users without PowerShell.
To create Shared Calling Policy:
Go to Voice > Shared calling policies.
Select Add to create a new Shared Calling policy.
Enter a unique name and description for the policy.
Select the resource account that you want to use for this policy.
Select Add emergency callback numbers. From the side panel, select the Phone number type and Assigned phone number. Once you've added the emergency callback number, select Add.
Select Save.
Thank you. That was helpful.
You, Sir, are my hero for today- thanks so much! Excellent walkthrough!
Glad I can help!
Hi i followed your instruction and got the user setup fully i can receive call with the autoattendant but i try to make a call i get that i am not setup to use this calling feature any assistance will be appreciated
I would check that no step was missed. That's what I would do if you would schedule a remote IT support call. Common issues is wrong licensing, not enabling voice, and not enabling billing properly. Of course, could be an issue with setting the Shared Calling policy itself.
@@ApexOneTech thanks i will recheck
This is an excellent step-by-step, thank you! I am trying to select a toll-free auto-attendant phone number but I'm getting the "you don't have enough credits..." message. In my licenses I have 10000000 available licenses next to Communications Credits. What am I doing wrong? I want to have a 800 or 888 or similar number.
Nevermind! I found where I can buy the credits. All set, thanks again!
Yup. And you can also use a credit card billing account instead of communication credits.
Did anyone else ever get a "sorry we cannot complete your call at this time please try again later" after going through these steps?
It basically means you’ve configured something wrong. Most likely a licensing issue or did not turn on billing properly. Also check that you enabled enterprise voice for the user.
@@ApexOneTechhow to enable enterprise voice ?
Can you delete the trial after 7 days??
Yes
Thanks Bogdan. We received this error from the code in step 6. Any ideas what we're doing wrong?
Set-CsPhoneNumberAssignment : Cannot process argument transformation on parameter 'LocationId'. Cannot convert value
to type System.String.
At line:4 char:41
+ ... eNumberAssignment -LocationId $CivicAddress.DefaultLocationId -PhoneN ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Set-CsPhoneNumberAssignment], ParameterBindingArgumentTransformationEx
ception
+ FullyQualifiedErrorId : ParameterArgumentTransformationError,Set-CsPhoneNumberAssignment
It's difficult to troubleshoot this just for this alone. It might be as simple as an extra space or location may not match.
We might be able to figure it out in a 30 minute call. Reach out using the link in the description.
Great and complete steps. I've watched many videos, but yours is by far the most comprehensive and complete. Sending you a bucket full of thanks.
Thank you very much! Glad it I could help.
You mentioned in the video that a company that does a lot of calling can get a pre-paid calling plan instead of pay-as-you go. What is the name of the prepaid calling plan and can it still be shared?
The limitations now are that you have to use a PAYG calling plan with the Main Auto Attendant phone number that you set up that will be used for the Shared Calling. At least for the US and the UK. If you really need a lot of outbound calling, consider just getting direct numbers for users. It's much easier to set up as well. Depending on the size of your team, some users can have direct calling (DID) phone numbers with standard domestic calling plans and other users can be on a Shared Calling Plan that has a PAYG plan attached to it.
How come you need to make a second number for emergency call back? if you port the number to your business number, can you make them the same #?
You can port in your existing number to Microsoft. The emergency callback is included from Microsoft with your license. It’s used for Shared Calling Plan because users don’t have unique (direct) numbers. So that emergency number is used if a user on the Shared Calling Plan calls 911. Point is, that number is not customer-facing and doesn’t need to (and can’t) match your main business number
Thank you for the walk through!! It was very informative and easy to follow. Definitely got my sub.
Keep it up
Thanks for the sub!
Thank you for that step by step explanation.
I believe the Shared Calling Policy GUI is working now.
But it is in the new main menu "Settings and policies" at the top, not below Voice.
You're right! It is working now. I'm not sure what you meaning by "Settings and Policies" but I actually see it under Voice > Shared calling polices.
They changed the gui recently, you still have the old. policies are moved for the whole of teams and are now all together under a main menu Setting and Policies. No longer under voice
Great video. Question where do I find the power shell input text? Also can you have multiple numbers going into one auto attendant?
It’s in the video description. Let me know if you need more clarity on that. There’s only one number but you can easily setup additional number to forward to one auto attendant. Setup another auto attendant and there will be an option to redirect the call to the main auto attendant.
Hello. On my company we just need to use outbound calls. Can I use Shared calling? We will not have auto attendant, just a group of users who will call to users. Thanks
Yes, Shared Calling Plan would work for that. You'll still setup an auto attendant. Just a placeholder. There's no cost savings in not having an inbound phone number.
@ApexOneTech So, create an auto attendant still. And calling plan would be pay as you go, communication credits or a normal phone plan? And at the end define a call policy. Is that correct? Sorry for all questions. Thanks in advance
Hi Bogdan- does this have to be a pay as you go calling plan? Using NTS as plan provider and getting ready to set this up for several customers using same provider.
No, doesn’t have to be pay-as-you-go. That’s just one of the two calling plans if you use Microsoft as your PSTN carrier. PAYG is most cost effective. I’m not familiar with NTS, but with Teams Phone, there are basically to other main options for calling PSTN carrier rather Microsoft: 1, using your own carrier with Operator Connect or 2, using own carrier with Direct Routing. There’s a great PDF from Microsoft here: learn.microsoft.com/en-us/microsoftteams/cloud-voice-landing-page
@@ApexOneTech thank you so much for the quick reply!😇
Had this working inbound and outbound for two different customers with Temp Numbers provided by Direct Routing company while waiting for my customers numbers to be ported into that same company- as soon as the numbers were ported in - we unassigned the temp numbers and replaced with newly ported in numbers and it broke everything. I have since setup the companies all over again with teams phone shared calling and performed identical steps for both- however now One company works for inbound and outbound shared calling with no problem, and the other company only inbound is working- Outbound using teams is not working and gives the message about the user not licensed for anything outside of the organization. Any thoughts on what I can check - a step i might have missed specific to outbound- I have done the EnterpriseVoiceEnabled repeatedly for the user I am testing- no dice!
what the hell is this BS from MS? I just want to add a phone number for the company so that customers can ring me. I want that to be connected to teams. Why the hell do I need to use powershell for that? This is the most awkward MS nonsense ever.
lol I know. This is only if you want to use the Shared Calling Plan. You don’t have to go this route. It’s much simpler to just use direct numbers. You set up an Auto Attendant, attach a voice app number to it, and now you can use that as your business number and as your caller id when you dial out.
@@ApexOneTechI'm applying this shared plan, because it cheaper but also because there was absolutely no way I managed to keep the outbound caller ID the main phone number when having ddi/call plan per user.
Some people would see my main number, some people would see my ddi nummer when calling them.
No logic in it why.
Also can't get pay-as-you-go call plan with an NCE sub working. I have a ticket open for 4 months now, but they are not really responsive or helpful.
Sounds like there's are no credits on it, but the whole point of the nce plan is to pay afterwards.
@@DJIrvinCee You can get everyone who has a direct plan to also have the main business phone number caller ID by creating a Call Queue. That's probably the easiest way so far.
@@ApexOneTech I'll give that a try.
Hi, can we assign extension number to user, if yes, how can we do it. Thanks
Yes, you can set up extension numbers in Teams Phone in general. However, I haven't done so with a Shared Calling Plan. But I do plan to make a future video on extensions. This may be helpful to you if you need to do this right away: techcommunity.microsoft.com/t5/microsoft-teams/dialing-by-extension/m-p/4002624
I would also enjoy a video on setting up extensions. I've tried a few things and the dial by extension is not working as expected (Except for on an Iphone). Currently have a ticket open with Microsoft to see why it isn't provisioning.