E911 Compliance & Deployment
For organizations operating multi-line telephone systems, 911 readiness is more than being able to dial 911. The system must support direct 911 dialing without requiring the user to dial an access code (usually 9) to get an outside dial tone. It must also send appropriate emergency notification, and send to the PSAP the location information needed to identify the caller's location.
Kari's Law requires VOIP/MLTS phone systems to support direct 911 dialing and send on-site notification when a 911 call is placed whereas RAY BAUM'S Act requires sending dispatchable location information with 911 calls to PSAP. For multi-site organizations, maintaining that capability across locations, users, devices, and changes to the environment requires more than a one-time configuration. It requires routine compliance with user moves and changes to sync with the ALI database shared with your carrier.
E911 configuration can become difficult to manage when users move between locations, offices are reconfigured, new devices are added, or the voice environment changes. In a multi-site environment, location information can become outdated if changes to users, devices, network infrastructure, or telephone numbers are not reflected in the E911 database configuration.
The problem becomes more complicated when the organization operates multiple voice platforms or has a combination of on-premises and cloud-based systems. Cisco, Avaya, and Microsoft Teams environments can have different configuration requirements for emergency calling and location management.
Lumensoft Networks supports E911 as an ongoing maintenance and continuous operational requirement rather than a one-time deployment.
We assess your existing voice environment, site locations, floor maps, users, devices, and emergency calling configuration to identify gaps. Based on the environment, we can support implementation of:
The exact implementation depends on your voice platform, carrier, number of locations, and how users and devices are managed.
Lumensoft Networks supports E911 environments built around Cisco, Avaya, and Microsoft Teams. We work with leading E911 partners to deliver solutions for the customer's current environment rather than forcing a new platform simply to implement E911.
For organizations with multiple locations, the focus is maintaining accurate emergency calling and location information synced to environment changes.
E911 should not end when the initial configuration is completed. New users, device changes, office moves, network changes, and new locations can affect compliance with emergency location information. That is why we have designed our E911 service to support ongoing maintenance and continuous user monitoring for location changes.
Lumensoft Networks can support E911 through:
For multi-site organizations, we can assess the existing E911 environment, identify configuration and compliance gaps, and scope the work required to address them.
Tell us about your voice platform, number of locations, and current E911 environment. We will assess the requirements and determine the appropriate scope before pricing the engagement.
Does the rule apply to you?
Are you the manager, operator, or installer of a multi-line telephone system (MLTS)?
FCC MLTS rules do not apply.*
Continue to next question ↓
Was it installed after 2/16/2020?
Skip to "Rules apply" below ↓
Continue to next question ↓
The MLTS may be exempt as a legacy system. Has there been an upgrade to its hardware or software since 2/16/2020?
Continue to "Rules apply" below ↓
FCC MLTS rules do not apply to legacy MLTS; check state law.
Rules apply
* Certain rules still apply to MLTS manufacturers, importers, sellers, and lessors.
** Notification obligations may not apply in all circumstances — see FCC MLTS rules.
Where the rules apply, you must: enable direct 911 dialling with no additional digits; provide notification to a central location when a 911 call is made; and meet caller-location obligations — automated dispatchable location for on-premises fixed devices, and for mobile devices automated dispatchable location where technically feasible or an alternate location method where it is not.
How we work
Lumensoft Networks partners with E911 providers to provide E911 solutions based on the customer's voice environment, locations, carrier, and technical requirements. We provide the solution, deployment, configuration, testing, documentation, and ongoing management as required.
We work with E911 providers including Red Sky Technologies, 911 Secure, Bandwidth, and Intrado and select the appropriate solution based on the environment rather than trying to fit every customer into the same platform.
The assessment starts by understanding if you have an E911 solution and how it currently works in your environment.
The six phases
We review the existing voice environment, locations, users, devices, emergency calling configuration, and location information to identify gaps and determine the requirements for the E911 solution.
A practicing Solution Architect reviews the assessment findings and determines the technical requirements based on the existing environment.
We recommend the appropriate E911 solution and provide a scoped proposal covering the platform, deployment requirements, locations, implementation approach, and timeline.
We deploy and configure the E911 solution, build the required location information, coordinate testing, and validate emergency calling with the appropriate answering point.
We document the E911 configuration and provide operational procedures for managing users, devices, locations, and changes to the environment.
E911 configuration changes as the environment changes. Ongoing management can include location updates, user and device changes, testing, change control, and maintaining the E911 environment.
What you receive
How it is bought
The initial multi-site E911 gap assessment is free. We review the existing environment and determine the E911 solution, deployment requirements, and scope of work.
Deployment is scoped based on the voice platform, number of locations, existing configuration, carrier, and implementation requirements.
Ongoing E911 management is available as a managed engagement on a monthly retainer.
We assess the environment first, determine what is required, and then provide the solution, scope, and pricing.
Platforms
Delivery record
Compliance has been delivered at scale, including a 42-location, 8,100-user legacy PBX replacement standardized on a single platform, and a 10,000+ user voice platform migration in which PSAP line continuity was preserved throughout the cutover.
Multi-property portfolios under a single corporate contract.
Floor, wing and room-level location across clinical campuses.
Stations, platforms, depots and control rooms.
The obligation attaches regardless of industry.
E911 technology partners
Lumensoft Networks currently partners with the following vendors as a value-added reseller.
Common questions
A US federal law requiring every multi-line telephone system to permit direct 911 dialling without a prefix and to notify a central on-site location when a 911 call is placed. It applies to hotels, hospitals, offices, campuses and transit facilities.
Section 506 requires dispatchable location — a validated street address plus floor or suite detail — to be delivered with every 911 call, phased in by device type under 47 CFR §9.16.
Yes. Any organization using Teams as an MLTS must meet both obligations, including Teams Phone with Direct Routing or Calling Plans, and hybrid estates.
Possibly, but the exemption is narrower than most assume. Any upgrade to core hardware or software since then generally brings the system into scope, and state law may apply regardless.
Yes. Multi-property programmes run under a single corporate contract with deployment phased by site.
Annual testing, change control and regulatory updates under retainer. Compliance decays through moves, adds and changes, so governance is what actually keeps it in place.
No. We select and deploy what fits the environment and have no resale relationship influencing that choice.
The organization operating the multi-line telephone system, not the vendor who installed it. That responsibility cannot be transferred by contract. It covers direct 911 dialling without a prefix, on-site notification when a call is placed, and dispatchable location delivered with every call under RAY BAUM'S Act §506.
Related services
Compliance decays through moves, adds and changes rather than through neglect, which is why the governance retainer matters more than the deployment.
Kari's Law compliance across an entire portfolio, under one corporate contract.
Who We ServeFloor, wing and room-level dispatchable location across clinical campuses.
Who We ServeE911 scoped for stations, platforms, depots and control rooms.
ConsultancyEnterprise Infrastructure & Compliance — governance, standards and recovery readiness.
The free multi-site assessment reviews your position across every site under both statutes. There is no scoped project attached — if you are compliant, you will be told so.
