Direct Routing Emergency Calling

Occasional Contributor

I recently watched


It was a great video but it left me with a question about emergency calling through direct routing when you don't care about dynamic location services. If you are using direct routing and don't care about dynamic locations do you still need to setup the emergency routing policy to specifically route 911 calls?


If you just have a normal voice route that captures the 911 digits is that sufficient to transfer the call to the carrier and then have them deal with the 911 call however they would?

1 Reply


Emergency routing policies do more than just trigger location identification. They define a number as an emergency number, which can have an impact on how devices behave as well.  For example, if a device (such as a Yealink T58 or a Poly CCX) is locked, and you tap the "emergency call" button or attempt to dial 911, you won't be able to.  In the US, that is illegal (see Kari's Law).


You can create an emergency policy that simply uses the existing routing policies, and not define any location information.  The call will still be routed to your on-premises SBC where it'll be handled.  The call will also be flagged as an emergency call using specific SIP headers.


Are you planning on implementing an E911 integration with a third party such as Intrado (formerly West)? If not, you will have to make sure your phone number location is updated with your local city/county to ensure the address information is at least to the building.


Out of curiosity, is there any reason you're not looking to build out the location data for dynamic location awareness?