May 12 2020 11:39 PM
May 12 2020 11:39 PM
Last time I got that message:
Prevent/Fix: Update TeamsEmergencyCallRoutingPolicy to avoid emergency call failures
MC212627, Prevent or Fix Issues, Published date: May 12, 2020
Copy link To clipboard
Mark as unread
Action required by Jun 15, 2020
We have made a change where a "+" will no longer be inserted in front of dialed emergency numbers. For example, currently when a Teams user dials 911 then +911 would be sent as the emergency number, after this change then 911 will be sent as dialed. After June 15th, 2020, you will encounter issues with emergency calling if the NumberPattern in the OnlineVoiceRoute's used to route emergency calls aren't configured to match the dialed emergency number without a "+" being prefixed in front of the number.
How this will affect your organization:
You are receiving this message because our reporting indicates one or more users in your organization are using Dynamic Emergency Calling with Direct Routing. Please validate the NumberPattern parameter in the OnlineVoiceRoute's, that are being used to route emergency calls, are configured to match emergency numbers prefixed with and without a plus "+". For example, the regex for the number pattern should be something like ^\+?911 or .*. to ensure emergency calls can be routed that are formatted either as +911 or 911.
What you need to do to prepare:
To fix this problem you need to review your Direct Routing configuration to ensure it can match emergency numbers that are sent without a plus prefix (+).
My 911 Emergency dial string is in format 911, 911 Emergency dial mask is in format 1414566911 and Voice route for it is in format ^((^\+?1414566912)).
Am I setup correctly for incoming changes?
May 13 2020 06:26 AM
@msabat Depending what US state you are in, the configuration you posted (where you take 911 and normalize it to a +1XXXXXXXXXX number) could be very, very illegal. For most states in the US, 911 calls are NOT allowed to be redirected to an internal security/response team, unless that security/response team meets the same standards as the local 911 PSAP. Additionally, there are national E-911 laws beginning to take effect that will make your configuration illegal nationally as of March of 2021. 911 should be normalized to 911 only, and all voice routes for that must route the call to your local 911 PSAP or an E-911 emergency routing service that you are subscribed to. If you need alerting or for a security/response team to be conferenced in to the call, there are other - legal - ways of doing so through Emergency Calling Policies and an E-911 service.
May 13 2020 06:38 AM
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?
May 13 2020 07:05 AM
@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)$
May 15 2020 05:00 AM
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?