10-09-2018 03:36 PM
10-09-2018 03:36 PM
is there a way to assign direct routing phone numbers to Auto Attendants or Call Queues. That seems to be an obvious function but I have not found any documentation. It always refers to service numbers.
10-09-2018 09:37 PMSolution
10-17-2018 01:46 PM
10-17-2018 09:41 PM
10-24-2018 12:18 PM
Sorry, for the late reply. I think we need to settle with call forwards at the SBC level for now. Migrating is not possible because it is a closed number block and there are still analog devices needed.
12-31-2018 03:57 AM
please I want Command lines to assign a Direct routing phone number to the Auto attendants and Call queues
01-02-2019 12:50 PM
Currently you can't set a phone number coming to Microsoft PBX via Direct Routing to an AA or CQ.
You can to it with a small trick by changing the PSTN number to a SIP URI.
01-24-2019 10:13 AM
Direct Routing customers requirement for Auto Attendant is growing daily and we are getting more and more questions as to WHEN it will be available. Nothing on the MSFT roadmap seems to speak to DR AA.
Can anyone at MSFT provide an estimated GA date for this feature (and Call Queues while we are at it)? Thank You
Gary (garywoods @ nuwave.com)
02-21-2019 01:42 PM
Here are some 'work around' I have done for some clients. I have setup direct routing and used auto attendants and call queues in O365/SfB online.
You have a couple options, either a message manipulation on the SBC to rewrite the TO header on the SIP invite to a service number assigned in the cloud (this can be a number simply acquired thru microsoft) and routing to MS via DR.
A second option is to go to a dummy user that is configured to forward all calls to the AA/CQ number.
A third option is to have your carrier with the sip trunk setup call forwarding for that specific number to the Microsoft service numbers.
I agree, customers definitely need this functionality with Teams. Auto attendant and call queues are an important piece to replacing legacy phone systems and transitioning 100% to Microsoft Teams.
With that being said, it does appear to be on the road map to be able to assign local PSTN numbers to call queues here (under Microsoft Teams - Call Queues) -
Hope this helps.
02-26-2019 11:32 AM
thank you for your suggestions.
The first option returns a 404 in all attempts I made.
The second option works
The third option is not an option with out carrier.
03-06-2019 03:50 PM
03-26-2019 04:25 PM
@gary woodsHello Gary,
on the launched item for CQs is the following sentence which was added in December 2018 I think:
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.
This makes we wonder what the status is considering we are approaching the end of that next quarter.
04-09-2019 11:15 AM
@Sascha Stops For everyone interested, the documentation for the feature is online:
04-15-2019 12:10 AM
04-15-2019 12:39 PM
@sasfbr We don't have it either. However seeing the documentation makes me think that it might not be long anymore.
04-22-2019 10:41 AM
@Sascha Stops I just looked, Org-wide settings > Resource Accounts is now in our tenant. I'll have to play with it a bit.
04-24-2019 12:48 AM
Was someone able to configure a direct routing number on the resource account? I have just tried it and got the following error:
Set-o365CsOnlineVoiceApplicationInstance -Identity testDirectRouting@xxxxxx -TelephoneNumber +32xxxxxxx
Your tenant is Disabled for this service. You are not permitted to use this cmdlet.
I'm guessing it is not rolled out yet on all tenants but can someone confirm?
04-24-2019 11:34 AM
@domienxylos: As long as you do not have submenu "Call Queue" and "Auto Attendant" in menu "Voice" in Teams portal, your tenant is not already migrated to the new CQ/AA. Migration of all tenants is ongoing. Just wait, until these two submenus are available and retry then.
04-25-2019 12:51 PM
When executing the 'Set-CsOnlineVoiceApplicationInstance' command I get the error 'The application instance does not have a valid license. I assigned the corresponding resource account an Enterprise E1 license with Phone System add-on.
Anything else I'm missing?
PS> Set-CsOnlineVoiceApplicationInstance -TelephoneNumber +31887769999 -Identity ******@pro****.nl
The application instance does not have a valid license.
+ CategoryInfo : PermissionDenied: (Set-CsOnlineVoiceApplicationInstance:String) [Set-CsOnlineVoiceApplicationInstance], UnauthorizedAccessException
+ FullyQualifiedErrorId : UnAuthorized,Microsoft.Rtc.Management.Hosted.Bvd.SetVoiceAppEndpointCmdlet
+ PSComputerName : admin1e.online.lync.com
05-09-2019 05:59 PM - edited 05-09-2019 06:00 PM
@Remco van Noorloos I am getting the same problem you mention here, unable to assign a direct routing number to a new resource account in teams. The resource account is licensed with E3 and Phone System add-on.
Have you been able to move past it?
05-14-2019 12:19 AM
Exactly the same problem with my tenant, resource account needs a direct dial number and has been licensed with E3 and phone and still the command to assign comes back with license invalid.
Please Microsoft, sort it out !
05-15-2019 04:04 AM
I found either a solution or a workaround. Instead of using Set-CsOnlineVoiceApplicationInstance, use Set-CsOnlineApplicationInstance -Identity RA_ADDRESS -OnPremLineURI +1xxxxxxxxxx. This worked for me when the Set-CsOnlineVoiceApplicationInstance gave the licensing error.
05-15-2019 07:31 AM
@SSchumacher_C1 Did you run anything else on-premise (new-cshybridapplicationendpoint) or is your setup a pure online one? Because I was able to run the command but still Teams is replying with a SIP 404 Not Found.
Thanks for your input!
05-15-2019 07:40 AM
Just want to add that I have had a response from the product group about this (via a really useful MVP guy - Thanks Matt..), this is what was said.
I believe there is an update for the docs to apply a Direct Routing number to the Resource account that should go out soon. The command should be: Set-CsOnlineApplicationInstance -Identity firstname.lastname@example.org -OnpremPhoneNumber tel:+14250000000
I'm about to test this my side, I'll update the post if it works.
05-15-2019 07:47 AM
Just a slight modification, the number can't have a "tel" at the front of it. So this just worked for me:
Set-CsOnlineApplicationInstance -Identity ReceptionAA@domain.com -OnpremPhoneNumber "+441234567890"
Hope this is useful.
05-15-2019 08:08 AM
05-15-2019 08:15 AM
05-15-2019 09:58 AM
I have been working with microsoft support, and we have narrowed down that you need to use set-csonlineapplicationinstance (no voice word), and they say you have to wait 24 hours, however i have done this and waited 24 hours, some have started working, whilst others havent.
Did you do anything else?
05-15-2019 11:12 AM
05-15-2019 11:13 AM
is this 24 hour wait period, you refer to, from the time you create the Csonlineapplicationinstance? We are working to create an AutoAttendant in hybrid scenario online.
so far have created the resource account online, cannot get phone number assigned to this object. tried with onpremphonenumber parameter suggested, but get an error the parameter does not exist.
and an onpremise cshybridapplicationendpoint object which i was able to get a phone number associated.
Any thoughts or ideas would be greatly appreciated!
05-15-2019 11:32 AM
05-15-2019 11:48 AM
@Joe Williams I have been burning the candle both ends at this, my life seems to be teams...
I have just tried one more command that i think i may have applied the other day to the resource account
grant-CsOnlineVoiceRoutingPolicy -Identity **resourceaccountname** -PolicyName **policyname**
I ran something on the other 2 accounts to get them working, but i cannot remember what, so trying to work it out now :(
05-15-2019 01:07 PM
05-15-2019 02:10 PM
05-15-2019 03:03 PM
I was able to get an auto-attendant working with a direct routing number using Set-CsOnlineApplicationInstance -Identity email@example.com -OnPremPhoneNumber "+1##########".
Worked like a charm on a resource account I created last week and licensed with Phone System and E1. Didn't need to grant a voice policy.
05-15-2019 11:35 PM
05-16-2019 08:45 AM
I created the resource accounts in the Teams Admin portal under org-wide settings. Not aware of any other way to create a resource account that can be used by auto-attendants or call queues.
05-16-2019 09:25 AM
05-16-2019 10:50 AM - edited 05-16-2019 11:04 AM
Yes, it definitely took a good amount of time for the object to begin working to some extent. Supposedly working for CCE, but cannot say for certain.
We are attempting in SfB Hybrid mode, and appears the call is hitting the online application instance via the sip2.lgw.skype.com gateway. we are seeing an attempt to REFER by the resource object created, to a user(s) configured for all calls, (temporary), in the Auto Attendant.
At which point we receive a 486 ProxyCall is not in connected state. and a verbal message of "Sorry, I couldn't help, please call back..."
Interesting situation though. Let you all know what we find out.
05-17-2019 04:15 PM
I have setup Teams with Direct Routing.
I have a ticket open, but haven't heard back, after I provided detail.
05-22-2019 11:41 AM
@John Joseph agreed, those are some of the same issues I have seen with some of our clients when connecting Advanced Calling Features (AA, CQ) to Teams endpoints.
The case I am attempting is SfBO Hybrid with on-prem PSTn to CLoud Auto Attendant, just to see if it would deliver to SfBO endpoint and it seems it will not. I do acknowledge MSFT has stated it is not supported to any other endpoints other than Teams.
Having said that it was almost working, the number delivers to the Auto Attendant fine through the hybrid application endpoint and resource account pairing, just would never deliver to user endpoints. Guess they are still working on that.
Thanks for the input.
05-22-2019 11:59 AM
@Joe Williams I have not tried an on prem PSTN number with CCE AA and CQ (sort of like hybrid) in a couple of months (so not with the new architecture), but back then it wasn't working. About a year or so ago, we did a bunch of testing with CCE using a SIP hand off (converting it to SIP at the SBC) and it mostly worked, but was inconsistent (sometimes it would fail) and it definitely isn't supported by Microsoft. It would be interesting to try a SIP hand off with Direct Routing, but since Microsoft says that on prem numbers are now supported as service numbers, we are putting our efforts there. I have had a ticket open (for almost a week now - first agent mysteriously disappeared and I was assigned a new agent on Monday) and am jumping through the hoops. I had to:
Since I have now completed these items; today, they agreed to escalate my ticket and told me to expect to hear from the escalation team in 24 to 72 hours (depending on workload).
05-22-2019 12:09 PM
Interesting, definitely good information for the Direct Routing to Teams scenarios, appreciate that.
with the Hybrid we are not technically sending via Direct Routing, or directly from the SBC. we are routing through the skype for business on-prem environment, using the new cshybridappplicationendpoint objects, so a little bit different. In the end, for our client I think we are going to table this particular method and explore other avenues of setting this up, at this point.