Managing locations for Unified-Communications-as-a-Service (UCaaS) deployments that scale into the hundreds or thousands of phones while supporting a large at-home or remote workforce can quickly escalate to a challenging task for any enterprise or UCaaS provider. Without the right automated E911 management technology, organizations may find that migrating to UCaaS requires additional administrative resources and time to effectively manage E911 locations for all users, and to maintain compliance with appropriate federal and state laws. A cost-effective and efficient solution for simplifying E911 location management is leveraging Next Generation 911 (NG911) technology. Read More >
The great migration from on-premises phone systems to cloud-based Unified-Communications-as-a-Service (UCaaS) increased in popularity this year. UCaaS capabilities seem to solve many UC-related administration and operational burdens although challenges remain, especially when it comes to Enhanced 911 (E911). With E911 compliance being of critical importance and one of the main E911 challenges for many enterprises, here is a high-level overview of the E911 rules and regulations that apply to a UCaaS environment, and how to plan an E911 strategy with E911 compliance in mind. Read More >
Intrado Life & Safety collaborated with UC Today to provide the Unified Communications (UC) community with an informative and educational video on meeting 911 Multi-Line Telephone Systems (MLTS) regulations in the United States. Read More >
One of the most pressing technology-related concerns in 911 today is quickly identifying the location of 911 callers. When 911 callers are at home and use a traditional landline to place a call, 911 call takers can automatically receive information about the location of the caller. However, emergencies do not always happen at home. They happen at school, work, and many other places. As a result, many of the calls 911 call takers receive pose location identification challenges. Read More >
Last updated: December 13, 2019
If your enterprise is migrating to Microsoft Teams, you can start using Dynamic E911, Microsoft’s new cloud-based E911 location tracking feature integrated in Teams, which is now generally available for all environments. With the FCC’s recent adoption of dispatchable location rules, Teams’ new location tracking feature comes at a perfect time. However, one question remains: how will your enterprise’s 911 calls and location information be routed?
When an emergency strikes, you pick up the phone and call 911. A helpful call taker confirms your address, gets the details of the emergency, and help arrives within minutes. Sounds simple, right?
If you’re dialing 911 from your office, a hotel or a remotely connected softphone, that simple interaction may actually be a pretty complex transaction. It requires multiple systems to integrate and communicate to get you the help you need. Intrado supports the journey of a 911 call from start to finish. Read on to find out what happens behind the scenes and learn about the technologies that enable enterprise 911.
Read More >
When we talk to enterprises about 911, we often hear about the E911 obstacles they face to making sure they can provide appropriate support to their users in a crisis. From roadblocks around awareness, to cost concerns, to management burden, the top three obstacles to enterprise 911 arise again and again in our conversations. Fortunately, enterprises can overcome these obstacles.
E911 Obstacle 1: Not Knowing that E911 is Broken
Perhaps the first obstacle enterprises face when it comes to 911, is knowing that they have a problem to begin with. When embarking on a transition to Unified Communications (UC), or implementing softphones, or adding another UC system to the mix, there are literally thousands of factors your IT team is considering. It’s easy to lose 911 in the shuffle.
Someone in distress, unable to speak, dials 911 from their VoIP system at the office. The Public Safety Answering Point (PSAP) receives the call with the following E911 location information: 123 Main Street, Marketing department, port 16. The PSAP then transmits the location data to first responders. However, once on-site, the emergency team finds a campus that consists of numerous multi-story buildings. Where is the Marketing department, and where is the location of port 16? First responders spend seconds, if not minutes, trying to pinpoint the precise location of the caller.
PSAPs need to transmit location information in a format that first responders can easily identify and understand. When seconds count and emergency teams need to find a person requiring immediate assistance, they simply don’t have time to figure out the location of a port or department within an enterprise’s facility.
Read More >