--- title: "What E911 and legal requirements apply when an ISP adds voice?" topic: "E911 & Compliance" updated: 2026-05-06 canonical: https://acrobits.net/resources/knowledge-base/e911-legal-isp-voice/ summary: "You're an ISP considering adding voice service. The technology is the easy part. The regulatory obligations — particularly around 911 — are where providers get into trouble." --- # What E911 and legal requirements apply when an ISP adds voice? > You're an ISP considering adding voice service. The technology is the easy part. The regulatory obligations — particularly around 911 — are where providers get into trouble. You're an ISP considering adding voice service. The technology is the easy part. The regulatory obligations — particularly around 911 — are where providers get into trouble. This is a practical overview of what the FCC requires, what state commissions expect, and where [Cloud Softphone](/cloud-softphone/) fits in the compliance picture. This is not legal advice. Consult a telecom attorney for your specific situation. ## E911: The Non-Negotiable Requirement If you offer interconnected VoIP — meaning your subscribers can make and receive calls to/from the public telephone network — you have [E911](/voip-glossary/e911-location-reporting/) obligations. Period. The FCC doesn't distinguish between large carriers and small ISPs on this point. **Interconnected VoIP** is the trigger. If your service only allows app-to-app calls within your network, E911 rules don't apply. The moment a subscriber can dial a regular phone number, you're subject to 47 CFR Part 9. ### What E911 Requires RequirementWhat It Means Route 911 calls to the correct PSAPBased on the caller's location, not your server location Provide callback numberThe PSAP must be able to call the subscriber back Provide location informationAddress must reach the PSAP's dispatcher screen Register with a 911 service providerTypically Intrado, Bandwidth, or similar E911 aggregator For mobile softphone users, location is the hard part. A subscriber using your app could be anywhere — home, office, hotel, car. You need a mechanism to capture and update their location. ## RAY BAUM's Act: Dispatchable Location RAY BAUM's Act (2019, with enforcement deadlines phased through 2022) expanded the location requirement significantly. The key term is **dispatchable location** — an address validated to the point where emergency services can actually find the caller. For fixed locations (desk phones), this means a street address plus floor, suite, or room number. For mobile softphone users, compliance gets more complex: - **Device-based location** — The app can report GPS coordinates, but this requires user permission and doesn't work well indoors. - **User-registered address** — The subscriber enters their primary location. This is the baseline approach most VoIP providers use. - **Dynamic location updates** — The app updates the registered address when the subscriber moves. This is the gold standard but requires app-level support. Cloud Softphone supports location reporting that can feed into your E911 infrastructure. The app can prompt subscribers to update their registered address and report location data to your provisioning system. ## Kari's Law: Direct 911 Dialing Kari's Law (named after Kari Hunt, who was killed in a hotel while her daughter couldn't reach 911 because the hotel phone required dialing "9" first) requires: - **Direct dialing** — Users must be able to dial 911 without a prefix. No "9 + 911" or any access code. - **Notification** — A designated on-site contact must be notified when a 911 call is placed (applies to multi-line telephone systems). For softphone apps, direct dialing is straightforward — configure the dial plan so 911 routes directly. The notification requirement applies primarily to enterprise PBX deployments, not individual subscriber apps. ## CLEC Licensing: Do You Need One? **The general guidance:** - **Pure hosted VoIP (no facilities)** — Most states do not require a CLEC certificate for providers who don't own network facilities and are reselling SIP trunking from a licensed carrier. Some states require registration or a VoIP-specific authorization instead. - **Facilities-based service** — If you own switches, trunk lines, or interconnection points, you likely need a CLEC certificate in each state where you operate. - **FCC registration** — Regardless of state requirements, interconnected VoIP providers must file FCC Form 477 (broadband/voice deployment data) and contribute to the Universal Service Fund (USF). **Bottom line:** Don't assume you're exempt. Get a telecom attorney to review your specific service model and the states where you'll operate. ## STIR/SHAKEN: Caller ID Authentication If you're originating calls to the PSTN, you have STIR/SHAKEN obligations. This framework authenticates caller ID to combat robocalling. Provider SizeRequirement Large providers (100k+ subscribers)Full STIR/SHAKEN implementation with SIP Identity headers Small providers (Robocall Mitigation Program filing with FCC All providersMust be listed in the FCC's Robocall Mitigation Database For a deeper dive on STIR/SHAKEN implementation, see our [STIR/SHAKEN guide for white-label operators](/blog/cloud-softphone/stir-shaken-white-label/). ## USF Contributions Interconnected VoIP providers must contribute to the Universal Service Fund. The current contribution rate fluctuates quarterly (it was approximately 36% of interstate/international revenues as of early 2025 ). You report revenues and pay contributions based on a percentage of your interstate and international voice revenue. ## What Cloud Softphone Handles Cloud Softphone addresses the app-level compliance requirements: - **E911 location reporting** — The app can collect and transmit subscriber location data to your E911 service provider. - **Direct 911 dialing** — 911 routes directly without prefix, compliant with Kari's Law. - **E911 callback reliability via SIPIS** — If a 911 call drops, the PSAP calls back. Cloud Softphone uses [SIPIS](/voip-glossary/sipis/) — Acrobits' SIP Instance Server, routing wake signals across FCM, APNs, and Local Push — to ensure that return call rings through even when the app is running in the background. WebRTC-based softphones cannot make this guarantee. - **STIR/SHAKEN passthrough** — SIP Identity headers are supported at the protocol level. The regulatory obligations — USF contributions, FCC filings, state licensing, E911 provider contracts — remain your responsibility as the service provider. Cloud Softphone gives you the app-layer compliance pieces; you handle the business-layer obligations. ## Before You Launch Voice Service StepAction 1Consult a telecom attorney on CLEC/state requirements 2Register with the FCC Robocall Mitigation Database 3Contract with an E911 aggregator (Intrado, Bandwidth, etc.) 4Implement STIR/SHAKEN or file mitigation plan 5Set up USF contribution tracking and reporting 6Deploy a compliant softphone app with location reporting Step 6 is where [Cloud Softphone](/cloud-softphone/) fits. The regulatory filings, licensing, and fund contributions are on you — but the app that your subscribers actually use can be deployed in weeks at a fraction of what it would cost to build compliant push infrastructure in-house ($5K setup + ~$600/month vs. $500K–$1M+ year one for a custom build). Cloud Softphone works with any SIP softswitch — MetaSwitch, BroadSoft, FreeSWITCH, Asterisk, or your existing infrastructure. No stack migration required. Don't let compliance uncertainty delay your voice launch. Get the legal questions answered, then get the app deployed. { "@context": "https://schema.org", "@type": "Article", "headline": "E911 and Legal Requirements for ISPs Adding Voice", "description": "You're an ISP considering adding voice service. The technology is the easy part. The regulatory obligations — particularly around 911 — are where providers get into trouble.", "url": "https://acrobits.net/blog/cloud-softphone/e911-legal-isp-voice/", "datePublished": "2026-05-06T09:00:00Z", "dateModified": "2026-05-06T09:00:00Z", "author": {"@type": "Organization", "name": "Acrobits"}, "publisher": {"@type": "Organization", "name": "Acrobits", "url": "https://acrobits.net"} }