---
title: "Is location permission required for a mobile VoIP app?"
topic: "E911 & Compliance"
updated: 2026-07-09
canonical: https://acrobits.net/resources/knowledge-base/is-location-permission-required-for-mobile-voip-app/
summary: "A mobile VoIP app does not inherently need location permission. The main exception is emergency calling: if your app supports 911 calling in the United States, it must provide a dispatchable location for emergency calls, which typically means requesting OS location access or offering a manual registered-address alternative. Apps deployed outside the United States, or in configurations where E911 is handled upstream, may not need location permission."
---

# Is location permission required for a mobile VoIP app?

> A mobile VoIP app does not inherently need location permission. The main exception is emergency calling: if your app supports 911 calling in the United States, it must provide a dispatchable location for emergency calls, which typically means requesting OS location access or offering a manual registered-address alternative. Apps deployed outside the United States, or in configurations where E911 is handled upstream, may not need location permission.

A mobile VoIP app does **not** inherently need location permission. The main exception is emergency calling: if your app supports 911 calling in the United States, it must provide a dispatchable location for emergency calls, which typically means requesting OS location access or offering a manual registered-address alternative. Apps deployed outside the United States, or in configurations where [E911](/voip-glossary/e911-location-reporting/) is handled upstream, may not need location permission.

## When location permission is required

Any softphone intended to support 911 in the US falls under the FCC's RAY BAUM'S Act dispatchable location mandate, which took effect for fixed and nomadic multi-line telephone systems (MLTS) and interconnected VoIP services in phases through 2021. The rule requires that the caller's dispatchable location, a civic address specific enough for first responders to reach them, travel with the 911 call to the PSAP.

  - **GPS / device location**. The most precise source. On both iOS and Android, reading GPS coordinates requires an explicit user grant. Without it the app cannot transmit a real-time location.

  - **HELD (HTTP Enabled Location Delivery)**. The app can query a Location Information Server (LIS) using HELD (RFC 5985) to obtain a civic address; this may work without GPS if the carrier's LIS can derive location from IP, Wi-Fi, or cell data. Some carrier and device combinations still require OS location permission to provide accurate data to the LIS.

  - **IP-to-civic-address fallback**. Coarse IP geolocation is generally insufficient for PSAP routing and does not satisfy the dispatchable location standard.

Kari's Law (also FCC-mandated) is a related but separate requirement: it prohibits PBX systems from requiring a dialing prefix to reach 911. It does not govern location data.

## When location permission is not required

  - **International deployments**. Apps deployed outside the US serve jurisdictions with different emergency frameworks (UK 999, EU 112, etc.). OS location permission for emergency dispatch is not universally mandated and the FCC rules do not apply.

  - **Fixed-location registrations**. If your platform pre-registers a civic address for each subscriber (e.g., a desk-phone replacement at a known office address) and passes it to the carrier at account creation, the app may not need real-time location access.

  - **BYO-provider configurations where E911 is handled upstream**. Operators whose [SIP trunking provider](/resources/knowledge-base/mobile-app-sip-trunking-isp/) manages all E911 routing and location delivery at the carrier layer may configure the softphone without exposing location APIs. The trunk provider handles that responsibility; verify their compliance posture before relying on this.

  - **Non-interconnected VoIP**. Apps that deliberately do not connect to the PSTN and cannot reach 911 are exempt from FCC E911 rules, though they should display the required warning to users about 911 limitations.

## How softphone apps handle location permission

Many softphone platforms address this at the SDK or platform level instead of leaving it to each operator:

  - **Permission prompt at setup**. The app requests location access during onboarding, explaining why it is needed for emergency services. iOS and Android both require a clear rationale string in the permission dialog.

  - **Location-reporting feature**. Acrobits Cloud Softphone includes a built-in [location reporting for 911 services](/features/location-reporting-for-911-services/) feature that handles HELD-based location delivery through the Inteliquent carrier integration, removing the compliance burden from individual operators.

  - **Manual address entry fallback**. If the user denies location permission, a properly implemented app prompts them to enter a registered address. This satisfies the dispatchable location requirement for fixed or predictable work locations.

  - **User disclosure**. FCC rules also require VoIP providers to notify subscribers of any 911 service limitations. This is separate from the technical location mechanism.

US ISPs and VoIP service providers can review the [E911 legal requirements for ISPs offering voice service](/resources/knowledge-base/e911-legal-isp-voice/).

{
  "@context": "https://schema.org",
  "@type": "FAQPage",
  "mainEntity": [
    {
      "@type": "Question",
      "name": "Is location permission required for a mobile VoIP app?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "A mobile VoIP app does not inherently need location permission. The main exception is emergency calling: if your app supports 911 calling in the United States, it must provide a dispatchable location for emergency calls, which typically means requesting OS location access or offering a manual registered-address alternative. Apps deployed outside the United States, or in configurations where E911 is handled upstream, may not need location permission."
      }
    },
    {
      "@type": "Question",
      "name": "What is the RAY BAUM's Act dispatchable location requirement for VoIP?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "The FCC's RAY BAUM's Act requires that interconnected VoIP services and MLTS transmit a dispatchable location: a specific civic address usable by first responders: alongside every 911 call. For mobile softphones this generally means GPS or HELD-based location delivery, requiring OS location permission or a carrier-level location service."
      }
    },
    {
      "@type": "Question",
      "name": "Can a VoIP app avoid requesting location permission?",
      "acceptedAnswer": {
        "@type": "Answer",
        "text": "Yes, in several scenarios: international deployments not subject to FCC rules, fixed-location accounts with a pre-registered civic address, or configurations where the SIP trunk provider handles all E911 location delivery upstream. Non-interconnected VoIP that explicitly cannot dial 911 is also exempt, though user disclosure of 911 limitations is still required."
      }
    }
  ]
}