06-24-2019 09:03 AM
06-24-2019 09:03 AM
I've got about half of my organization upgraded to Teams with Direct Routing.
On Friday I upgraded 138 more users, and first thing this morning I'm getting reports from more than a dozen users that they don't have the dial pad and can't make outbound calls. Inbound calls to their PSTN number are working.
Is there anything I can do to find out why this has taken 60+ hours and still isn't working?
Accounts are all licensed with E5 and checking them in the Teams panel, they look like other users that things are working for. Get-CsOnlineUser output also looks the same.
06-24-2019 09:10 AM
06-24-2019 09:51 AM
06-24-2019 10:43 AM
@adam deltinger That kind of makes me crazy. We'd been told previously by Teams Product Management that 40 hours is the maximum queue processing depth.
We're at 65 hours now and I have 54 out of 138 users who have reported no dial pad. :(
06-24-2019 01:29 PM
06-24-2019 05:18 PM
At this point, I have yet to find a single user out of the 138 users migrated that has the Dial Pad available to them.
Inbound calls to their PSTN numbers all work.
Internal calls, meetings, etc all work.
None of them can place an outbound PSTN call.
We've tried having 10 users sign out of all devices for 15 minutes, then sign back in on a single device. No change.
Support has been ... useless so far.
It's pretty frustrating that there isn't a separate support channel when there's a back end problem like this.
06-24-2019 06:28 PM
06-24-2019 10:31 PM
@Ron Prague Please make sure that users have AllowCalling policy enabled, are on Teams-Only policy,
have voice routing policy.
here are the powershell commands:
Grant-CsTeamsCallingPolicy -PolicyName Tag:AllowCalling -Identity firstname.lastname@example.org
Grant-CsTeamsUpgradePolicy -PolicyName UpgradeToTeams -Identity email@example.com
Grant-CsOnlineVoiceRoutingPolicy -Identity "firstname.lastname@example.org" -PolicyName "XYZ"
After that wait some time and restart teams client.