Most organizations are now aware of the new\nfederal laws regarding emergency calling in the United States but struggle to\nunderstand what they need to do or how to interpret those laws. How the laws\napply to your organization varies depending on several factors, two of which\nare particularly notable: the states in which you have physical bricks-and-mortar\nlocations, and the size of those sites. Some states apply rules that are even\nmore stringent than the federal laws, so organizations\u2019 obligations could differ\nacross geographies. The first step is to begin conversations with your legal counsel,\nto get advice on your organization\u2019s specific legal requirements.<\/p>\n\n\n\n
Up until this year, there were no federal laws governing how organizations in the U.S. ensure that emergency callers were properly served when dialing 911 from their internal phone systems. States were able to make their own rules, with the result that some had none at all, while others have had strict rules in place for some time. That changed starting in February 2020, with two new federal laws called Kari\u2019s Law and Ray Baum\u2019s Act<\/a>, bringing in minimum standards for enhanced emergency calling (E911) across the country. <\/p>\n\n\n\n These laws are designed to improve outcomes when 911 calls are made via the multi-line telephone systems (MLTS) such as the Private Branch Exchange (PBX) systems typically found in office buildings or academic institutions. <\/p>\n\n\n\n The good news is that Microsoft Teams can be\nconfigured to help organizations meet many of the key legal requirements, including:<\/p>\n\n\n\n
| Legal requirement<\/th>\n | How Teams solves it<\/th>\n<\/tr>\n |
|---|---|
| Eliminate the need for dial-out access codes for 911 calls (e.g., an additional \u20189\u2019 to get an external line). <\/td>\n | Teams will exempt all such prefixes by default for 911 calls when using either Calling Plans or Direct Routing. <\/td>\n<\/tr>\n |
| Notify on-premises staff or other responsible individuals (e.g. security personnel or campus police) when a 911 call is made. <\/td>\n | As an emergency call is placed, responsible parties can be notified with a chat message, added into the call (on mute, with the ability to unmute) or contacted at an external PSTN number.<\/td>\n<\/tr>\n |
| Providing a valid call back number to emergency services so that they can re-engage with the caller in the event the connection is lost. \n <\/td>\n | A direct dial number can be assigned for each Teams user. This number is displayed when dialing out to emergency services to allow a return call if required.<\/td>\n<\/tr>\n |
| Provide the caller\u2019s location so that they can be found if they become unresponsive and cannot speak. <\/td>\n | Teams leverages Location Information Services (LIS) to support emergency calling. LIS uses network identifiers such as subnets, switches and ports to pinpoint the location of the caller \u2013 down to the building, floor and desk area if required. The relevant physical address information is pre-programmed into Teams and is then automatically provided in the call to emergency services. <\/td>\n<\/tr>\n<\/table>\n\n\n\nThe importance of E911 Routing Services<\/h3>\n\n\n\nOnce Microsoft Teams is configured to meet E911 requirements, organizations must still purchase the Emergency Services Routing Proxy service (ESRP) through their existing SIP trunk provider or via a 3rd<\/sup> party such as Bandwidth.com or Intrado. These solution providers will read the location information provided by the Teams configuration and automatically route the calls to the closest emergency services dispatch center for the location of the user.<\/p>\n\n\n\n The new laws can seem complicated and they are set to become stricter in the years ahead, as additional requirements are introduced, but Teams can provide suitable solutions. At LoopUp<\/a>, we can help navigate the options available on Teams, assisting with configuration and migration. To find out more, contact a LoopUp specialist<\/a>.<\/p>\n\n\n\n To help organizations as they undertake this new journey, we recommend:<\/p>\n\n\n\n Jason is a Senior Director in LoopUp\u2019s consulting team. He is a Microsoft Certified Master, and has advised customers on Microsoft\u2019s unified communications solutions since 2010.<\/em><\/p>\n\n\n\n |