Forum Discussion
Update TeamsEmergencyCallRoutingPolicy to avoid emergency call failures
That is setup only between Teams and Cisco CUCM.
On CUCM we replace that +1xxxxxxxxx to standard 911.
My question is do I have correct configuration right now.
Is my voice route pattern corect - ^((^\+?1414566912))?
Does Teams send 911 cals with + or not right now?
msabat My previous point remains: there should be no reason to perform translations like you're doing. The call should simply have a DNIS of 911 from the time it is normalized in Teams, to the DNIS on the Direct Routing invite, all the way to the invite to CUCM. Perhaps there's a Calling Search Space configuration that requires you do it this way, but there's not a single deployment I've been involved with that has mirrored this setup.
To your question on the normalization, no. If you want a voice route to catch numbers with, or without, a leading plus, it would look like this: ^(\+)?(911)$
- msabatMay 15, 2020Brass Contributor
Thank You.
I have one more question.
I setup Emergency Routing Policies and assigned them to Sites with subbnets.
So any user that cover correct subnet will use Emergency Routing Policy assigned to site.
But I also have to set couple users with Emergency Routing Policy. If these users move to site with setup Emergency Routing Policy will they use it?
Should I turn on "Dynamic emergency calling" in their Emergency Dialing Policy?