03-13-2018 02:04 AM
03-13-2018 02:04 AM
I saw that Microsoft has already implemented extension dialing in Microsoft Teams.
But I was wondering if it could be possible for me to let multiple users use one phone number ( maybe a service number) to make calls. Because In my current system from 3CX I have one Sip trunk configured with a phonenumber that all my users can call with. This is because internal routing is done by assigning extensions to my users. This way they are unique within my company, but when they call to the outside world, they call through that single phonenumber. I was wondering if this will be available in Microsoft Teams and if so how I can implement this?
07-30-2018 11:17 PM
You are looking for "Microsoft Teams Call Queues". It's targeted for Q2 in the Office 365 Roadmap but currently not launched: https://products.office.com/en-US/business/office-365-roadmap?filters=%26freeformsearch=Call%20Queue...
07-31-2018 12:07 PM
The attendant feature gives the ability to dial by name...
You can also create a new CsCallingLineIdentity via PowerShell and then grant users access to that identity. Basically the number that shows up via caller id.
07-31-2018 12:18 PM
@Damon Betlow Thanks yes well aware that one can dial by name and also change the caller ID. There does not seem to be an solution for incoming pstn callers to dial an extension though. Yes I also know you can make a dial plan so internal users can dial an extension, which works well bytw.
It would be great if Microsoft would enable the Auto Attendant to search a custom attribute that I could enable on my users in AD called "PSTN Extension", and when one uses the auto attendant be allowed to dial or say the extension just like you can with the name and searching that attribute. This would satisfy the needs of many company's and be very simple to manage on the admin side,
08-02-2018 04:41 AM
Every voice enabled users in SfB / Teams has his own DID. I cannot see a benefit to dial the DID of the auto attendant if the caller knows the DID (extension) of the specific user. The auto attendant helps the caller finding a person or team (call queue) by name or skill (call queue).
08-02-2018 04:56 AM
@Andreas Exner Some benefits listed below:
For the most part enabling extensions from the auto attendant and internally for that matter is a way to assist in the transition or modernizing existing PSTN setups for many companies, but time is required to change processes and marketing material.
08-02-2018 05:53 AM
Let's try not to mix too many things.
From an internal client or phone, you can use extensions for dialing: https://blogs.technet.microsoft.com/cloudready/2017/08/01/skype-for-business-online-extension-dialin...
You can adopt your existing numbering plans and extension to the cloud PBX by using number porting or on premise call handling, to protect your investments in existing stuff.
Internal users with a softphone will use the name or buddy list for dialing. Or simply the contact and presence information from all supported documents, apps, etc. That's a change you will see with any UC solution because it's one of the major benefits.
The external caller won't know the extension if you are not like to publish your DID. Maybe in legacy PBX it was common that not every users had a DID, but an internal extension. With SfB/Teams we have a DID for every voice enabled user and every external caller is able to call the user if he knows the DID. That's a part of the changes. If you like to "hide" users from the directory (auto attendant) and keep the DID in privat, you are right. That's a challenge. Do you see a blocker here? Is there no way to replace that with call queues, for example?
08-08-2018 10:08 PM
09-18-2018 05:20 PM
04-12-2019 02:11 AM
Hi there, any update on this topic ?
Moreover is the Teams Extension calling working like Skyper for Business (as described in the "Skype for Business Unleashed" book ?
I done several tests but it seems not
07-31-2019 11:38 AM
08-21-2019 02:56 AM
@emiliaus When you implemented your fix in your SBC, how did you deal with the Line URI in Teams? I'm assuming you didn't use the same Line URI (e.g. +12334567890;ext=101 , +12334567890;ext=102 , etc...) because I can't get that to work. Did you assign a made-up number range in Teams and just do translation in the SBC or did you just assign extensions in Teams (e.g. tel:102;phone-context=siteA)? Really curious to know how you solved this. I'm struggling with it.
11-21-2019 12:16 AM
@Riegs we've solved our problem assigning to Teams users just the internal 4 digit extension (i.e.: Set-CsUser -Identity firstname.lastname@example.org -EnterpriseVoiceEnabled $true -OnPremLineURI tel:1234). Then we linked our internal PBX to the SBC via a Sip trunk and we configured it to route all calls from the PBX to those extensions to Microsoft Teams.
In this way the Teams user is identified by the "fake" DID (1234) and it can be reached by the SIP INVITE message coming from the PBX.
Please note that the Teams users that instead require also a valid DID, the extension dialing doesn't work: the extension is not used by Teams, so we had to add a map on the SBC.
So, for example if I have userA with "-OnPremLineURI +12334567890;ext=1234" and userB with "-OnPremLineURI ext=1235", on the SBC I have to map number 1234 to +12334567890. In this way internal phones (of my PBX) can reach both Teams users just dialing their extensions 1234 or 1235.
I hope this can help you guys.
11-23-2019 07:33 AM
02-12-2020 05:48 AM
@Phillip Lyle I can confirm that this works now with the cloud Auto attendant. However I have implemented it only for our inbound callers. Internal numbering is based on numbers we got from MS so, no way to do it by using dial plans, plus I am trying to introduce a different paradigm to internal users for communicating inside the company and using antiquated extension calling is not the way to go. I have to say though that MS has really dropped the ball on device firmware for Teams and there's no way for adding favorite contacts on said devices now but, I've seen somewhere that that may change.
02-12-2020 06:24 AM
by Mercedes Green on March 31, 2020
by Adityo Prabhaswara H. on September 08, 2019
by chris_morgan on August 22, 2019
by MicrosoftTeamsTeam on May 29, 2020
by Sankalp_Jain on April 02, 2020
by Paul Cannon on November 04, 2019