09-12-2018 06:00 AM
09-12-2018 06:00 AM
How to create Call queue for Microsoft Teams (or Skype for Business Online), when phone number (line number / caller ID) should be used from Direct Routing?
I do not see Powershell way, and I do have option just to purchase new numbers from Microsoft directly, but I want to use existing numbers (that can not be ported to Microsoft), and are in use through Microsoft Teams – direct routing.
09-12-2018 06:16 AM
Unfortunately, it’s not possible to use service numbers via Direct Routing. Let’s hope it will be possible in the future, because as you say it’s not always possible to port just your switchboard number, for example.
In the meanwhile, do a static call forward of your switchboard number to the service number acquired from Office 365, that should work.
09-12-2018 06:42 AM
Are you sure? Where is documentation? If so, I can not find feature request on ideas site...
09-12-2018 09:07 AM
I just hope, because the way it is now with the service number in Office 365, it simply doesn’t work when using Direct Routing or CCE. Rebellions are built on hope, remember. :smiling_face_with_smiling_eyes: If it’s not on User Voice then you should put it there, I’ll vote for it.
09-12-2018 12:36 PMSolution
Yeah, so this is probably not supported, since others are asking the same...
11-27-2018 09:03 AM
Actually it is possible and works pretty well.
What you have to do is to get a service number from Microsoft and then create a call queue or auto attendant on Legacy SfB Portal using this service number.
After that, always that your gateway/sbc receives a call on the extension number (private number) that you want to use for the CQ/AA you send the call to MS Teams throught Direct Routing using as destination number, the number of the service number that you are using.
For instance, if someone dials 9999 internally, you must forward this call to +12122345678 (Microsoft's service number that you got).
As we are talking about Teams, it is important that all of the users on call queue (group) were already configured to use Teams as their native client.
I hope it helps!
11-27-2018 09:06 AM
Yeah, but we are talking about getting from on-prem through SIP trunk - my existing service numbers, to the Teams.., not buying them from Microsoft.
11-27-2018 09:10 AM - edited 11-27-2018 09:10 AM
No. You won't use the Microsoft's service number to nothing but just routing the calls internally using your SIP Trunk.
You could forward one of your DIDs to the service number, as example.
The difference is that it is not possible to configure your own DID directly on the call queue, so, you create a "transformation" on the destination number.
Always that someone dials your DID, you send the call to Microsoft's service number of your call queue.
11-27-2018 12:48 PM
So basically, you have to pay to Microsoft for a number and for voice minutes, and can not use your on-prem numbers, ISP and pricing.
That is something that we wait to support direct SIP Trunk for existing service numbers, etc., not doing forwarding/transformation ....
11-27-2018 08:44 PM - edited 11-27-2018 08:51 PM
Actually, you can use on-premises PSTN numbers with call queue. The trick is to convert the destination number to AA\CQ SIP URI Guid. There's no service numbers involved in this setup. I have done this for all of the Direct Routing deployments so far and works well too. I've written a blog about it. Have a look and see if that works for you
12-03-2018 03:26 PM
01-29-2019 11:31 AM
The blog article states "**This article does not applies to Direct Routing with Microsoft Teams."
Do you have this working with Direct Routing/Teams?
01-31-2019 06:12 AM
01-31-2019 06:12 AM
It seems that this is on the Microsoft road map..
Please see here
Check out the “Call Queues” Roadmap on the second URL
Microsoft Teams - Call Queues
Phase 1 of Call Queues is now available for Teams. The work primarily focused on enabling the same set of features previously available to Skype for Business Online. Additional work is ongoing for support for phone number usage via Direct Routing and is expected next quarter.
• Featured ID: 24174
• Added to Roadmap: 10/24/2017
• Last Modified: 1/29/2019
• Tags: Microsoft Teams
01-31-2019 07:06 AM
01-31-2019 07:06 AM
Yeah, it is funny, it is marked as "Launched" , but with note, that this important part will be in next quarter.
It will be much better if they communicate this feature as a separate entry in roadmap with current status..
02-02-2019 12:12 PM
04-15-2019 12:20 AM
But in our case the feature is not available yet in Teams Admin Center, we don't have the option "Resource Account" under "Org-wide settings". Can anyone confirm this?
05-16-2019 01:27 PM
@sasfbr You should see it now, it's supposed to be GA, i'm seeing it in both tenants i have.
05-16-2019 01:41 PM
I do confirm this is resolved and now working.
EU tenants, first release features.
1) Create resource account
2) Create auto-attendant or call queue, connect with resource account
Connect with powershell and:
3) assign phone number from on-premise / direct routing through cmdlet to resource account
05-16-2019 01:43 PM
05-21-2019 01:39 AM
Anybody else having issues with Audio (Media Flow) when using Direct Routing for a Call Queue. Inbound\Outbound PSTN calls work fine to the Teams User Direct Dial. However, when I call the Teams Call Queue (own number assigned to Resource Account), the call rings on the Teams client and can be answered but get no media flow either way?
05-21-2019 06:01 AM
05-21-2019 06:40 AM
Thanks. We are Direct Routing and haven't used MS provided service numbers.
We had been waiting for them to allow Direct Routing numbers for Call Queues which only went into GA recently so purposefully held off. Obviously, they still have a bit of work to do!
06-06-2019 07:10 PM
07-08-2019 10:07 AM
We are seeing the same issue when using on premises numbers for Direct Routing in a call queue.
07-09-2019 12:17 AM
Call is currently with Microsoft for investigation. Awaiting their feedback. It has been with them for a while. They are suggesting the issue is within their control.
Will update back here when I hear back.
07-23-2019 01:08 PM
OK - just checking to see if was Ribbon.
I've just downloaded the latest firmware which looks to have resolved the issue.