Quick Answer: Ofcom requires all VoIP providers to route 999 and 112 calls to emergency services with accurate caller location data. Fixed users: register address once. Nomadic users: customers must confirm they understand emergency services may not locate them without providing address manually. Resellers must validate this in writing at onboarding. Failure to comply risks Ofcom enforcement action (£5k-£50k fines) and customer liability if emergency response is delayed. Test emergency calling before launching any VoIP service.
Ofcom Emergency Calling and Caller Location Obligations
These obligations apply to all VoIP resellers and providers. Non-compliance is an Ofcom enforcement priority.
| Obligation | Regulatory Basis | Your Responsibility (Reseller) | Your Supplier Responsibility (VoIP Provider) | Customer Responsibility | Penalty for Non-Compliance |
|---|---|---|---|---|---|
| Emergency Call Routing (999, 112) | Electronic Communications (Universal Service) Regulations 2003 (as amended) | Ensure your supplier provides emergency routing. Document in SLA. Implement in your service terms. Educate customers. | Route all 999/112 calls to Police, Fire, Ambulance within 2 seconds. No call blocking or failure. Publish SLA commitment. | Notify emergency services of their location if nomadic. Know emergency number (999 or 112). | Ofcom enforcement notice. £5,000-£50,000 fine. Service termination order. Reputational damage. |
| Caller Location Data Submission (Fixed Users) | Ofcom Single European Code (BEREC guidelines) and UK regulations | Collect and validate customer address at onboarding. Update annually or when customer moves. Submit to supplier or emergency database. | Register location in emergency services database (e.g., Openreach E999 system or equivalent). Update within 24 hours of notification. | Provide accurate registered address. Notify reseller of address changes within 14 days. | Ofcom enforcement. Emergency services may not locate the caller. Customer liability for emergency response delays. |
| Nomadic User Acknowledgement | Ofcom guidance and BEREC guidelines | Obtain written confirmation from nomadic users (remote workers, mobile staff) that they understand emergency location services may not work. Document consent. | Ensure reseller collects and maintains nomadic user consent documentation. | Sign written acknowledgement that they understand 999 calls may not provide location to emergency services. Update location manually if calling 999 while mobile. | Reseller liability if customer not properly informed. Ofcom enforcement notice. |
| Testing and Validation (for Licensed Operators) | Ofcom Network Resilience and Emergency Calling Standards | If you operate the network (licensed ECN), test emergency routing quarterly. Document test results. Provide to Ofcom on request. If reseller, ensure supplier has testing plan. | Conduct quarterly tests of 999/112 routing. Publish test results. Maintain test documentation. | Cooperate with testing (e.g., call 999 in test window, confirm location reported to services). | Ofcom audit and enforcement. Loss of licence or operating permission (if applicable). |
| Transparency and Customer Communication | Ofcom Consumer Rights regulations | Provide clear, written notice to customers about emergency calling limitations (especially for nomadic users). Include in terms of service and onboarding materials. | Provide resellers with emergency calling statement for inclusion in customer terms. | Acknowledge receipt of emergency calling terms at sign-up. | Ofcom complaint investigation. Customer complaints scheme escalation. Reputational damage. |
Testing Checklist and Validation Procedures
Before deploying any VoIP service to customers, validate 999/112 routing and location submission in a test environment. This checklist ensures compliance.
| Test Scenario | Test Procedure | Expected Result | Validation Method | Pass/Fail Criteria | Evidence to Document |
|---|---|---|---|---|---|
| 999 Call Routing (Fixed User) | Dial 999 from test SIP phone registered to fixed address (office). Confirm call is answered by emergency services. | Call connects to Police, Fire, or Ambulance emergency answer point within 2 seconds. No delay or routing failure. | Test with supplier. Confirm call answered by live emergency service operator or test line operated by supplier. | PASS: Call answered within 2 seconds. FAIL: Call drops, delays, or routes to wrong service. | Call log (date, time, duration). Emergency answer point confirmation email. Supplier acknowledgement. |
| 112 Call Routing (Alternative Emergency Number) | Dial 112 from test SIP phone. Confirm equivalent routing to 999. | Call connects to same emergency services as 999 (Police, Fire, Ambulance). | Test with supplier. Confirm call answered. | PASS: 112 equivalent to 999 routing. FAIL: 112 not routed or routed differently. | Call log. Supplier confirmation. |
| Caller Location Data Submission (Fixed) | Verify that registered address (address of test phone) is submitted to Openreach E999 database or supplier emergency database. | Location data appears in emergency services backend within 24 hours of registration. Location matches registered address. | Request location lookup from supplier or Openreach. Provide test phone number. Confirm address appears in E999 system. | PASS: Address matches registered location. FAIL: Address missing or incorrect. | Email confirmation from supplier showing location data submission. Screenshot of E999 lookup (if accessible). |
| Nomadic User (Mobile User) 999 Call | Dial 999 from VoIP client on mobile phone (using cellular data or WiFi, not registered to fixed address). Confirm call routing and note location limitation. | 999 call connects. Emergency services cannot automatically locate mobile caller. Instructions provided to caller to provide manual location. | Test with supplier or in test environment. Confirm call completes and supplier has documented nomadic limitation. | PASS: Call completes; nomadic limitation documented. FAIL: Call fails or location data incorrectly provided. | Call log. Supplier’s nomadic user guidance. Evidence that customer was informed of nomadic limitation in onboarding. |
| Call Restoration after Service Failure | Simulate service outage (disable SIP trunk temporarily). Restore service. Retry 999 call. | Service restored and 999 calls route normally within SLA timeframe (typically <15 minutes). | Work with supplier. Confirm restoration procedure and timeframe. | PASS: Restoration <15 minutes; 999 calls normal. FAIL: Extended outage; emergency calling impaired. | Incident log. Supplier SLA documentation. Restoration time evidence. |
| Number Porting Scenario (Ported Number from PSTN) | Port a live PSTN phone number to VoIP. Confirm 999 calls from ported number work. Verify location data for ported number is updated. | Ported number can dial 999. Location data reflects new VoIP provider or is updated to correct address. | Work with supplier and number porting provider. Confirm 999 routing on ported number. Verify location in E999 if available. | PASS: 999 works on ported number; location updated. FAIL: 999 fails on ported number; location stale. | Porting completion confirmation. Call log from ported number. Location update evidence. |
| Multi-site Enterprise Scenario | Register multiple office locations under same customer account. Dial 999 from phone at each site. Confirm location data is site-specific (not central office). | 999 calls from each site route to local emergency services for that site. Location data matches site address, not central office address. | Test across sites. Confirm location submissions are unique per site, not aggregated. | PASS: Each site location correct. FAIL: All sites show central office location. | Multi-site location data confirmation. Call logs from each site. Location verification per site. |
Provider Compliance Comparison: Which VoIP Provider Meets Ofcom Standards?
When selecting a wholesale partner or white-label provider, verify their emergency calling and location compliance. This table compares common UK and international providers.
| Provider | 999/112 Routing Certified? | Location Data Submission Documented? | Nomadic User Guidance Provided? | Testing/Monitoring SLA? | Ofcom ECN Licensed? | Reseller-Friendly Compliance Support? | Recommendation |
|---|---|---|---|---|---|---|---|
| BT Cloud Voice | Yes. Ofcom-certified. | Yes. Automatic E999 submission. | Yes. Template provided to resellers. | Quarterly testing. 99.5% uptime SLA. | Yes. Licensed ECN. | Yes. Reseller portal includes compliance templates. | Strong. Tier-1 UK provider with proven compliance. |
| Vodafone VoIP and Operator Connect Partner | Yes. Ofcom-certified. | Yes. Location data integration. | Yes. Provided in service T&Cs. | Quarterly testing documented. | Yes. Licensed ECN. | Moderate. Support available but not reseller-focused. | Good. Larger provider; less reseller hand-holding. |
| Virgin Media Business VoIP | Yes. Ofcom-certified. | Yes. Location data managed by Virgin. | Yes. Standard terms. | Quarterly testing. | Yes. Licensed ECN. | Moderate. Enterprise-focused; SME resellers have less priority. | Good. Large player; compliance strong but less reseller support. |
| Zen Internet (Reseller Partner) | Yes. Ofcom-certified. | Yes. E999 integration confirmed. | Yes. Provided to resellers. | Testing documented. | Yes. Licensed ECN. | Yes. SME-friendly reseller programme with compliance support. | Strong. Good compliance; strong reseller support. |
| Gamma (Reseller Partner) | Yes. Ofcom-certified. | Yes. E999 integration. | Yes. Templates provided. | Quarterly testing. SLA documented. | Yes. Licensed ECN. | Yes. Strong reseller support; compliance playbooks available. | Strong. Top-tier reseller partner. Excellent compliance support. |
| Asterisk / FreePBX (Open Source, self-hosted) | No. Depends on provider routing traffic. Self-hosted = your responsibility. | Manual. Your responsibility to integrate with E999. | Your responsibility to document. | Your responsibility to test. | No. Unless you operate as licensed ECN. | N/A. You are the provider. | Not recommended for VoIP resellers without licensing and compliance resources. |
| Microsoft Teams Direct Routing (customer-managed SBC) | Yes. Customer routes via SBC to SIP trunk provider. | Customer responsible for location data submission via SIP trunk provider or Calling Plans provider. | Yes. Microsoft includes guidance in Teams Phone documentation. | Customer/reseller responsible for testing. | If using licensed SIP trunk provider, compliance through that provider. | Moderate. Microsoft provides guidance; reseller must own implementation with SIP provider. | Good for enterprise; requires reseller compliance expertise. |
Frequently Asked Questions
If my VoIP provider handles 999 routing, am I still liable for non-compliance?
Partially. The provider is responsible for routing infrastructure. You (reseller) are responsible for customer education, written consent (especially for nomadic users), and ensuring your customer documentation is accurate. If a customer doesn’t receive proper notice about nomadic limitations and an emergency call fails, you share liability. Always document customer consent in writing.
How often must I test emergency calling?
If you operate a licensed network (ECN), Ofcom requires quarterly testing. If you’re a reseller (your provider operates the network), testing is your provider’s responsibility. However, best practice is to test at least annually or when you add new customers or features. Document all tests.
Can I tell my nomadic users to call 999 and just manually provide their location?
Yes, but they must give informed written consent in advance. Your terms must clearly state: “Emergency services cannot locate you if you call 999 while mobile or outside your registered office. You must manually provide your location to the emergency operator.” Have customers sign this acknowledgement at onboarding.
What if my customer’s broadband fails during a 999 call?
VoIP cannot work without internet connectivity. This is a fundamental limitation. Your service T&Cs must state this. For critical customers (hospitals, security services), recommend dual connectivity (broadband + leased line) or a mobile backup. Some customers may prefer to maintain a legacy PSTN line as a backup until comfortable with VoIP reliability.
Do I need to tell customers about potential location accuracy issues (GPS drift, address mismatches)?
Yes. For nomadic users, explain that emergency location services are not precise. A WiFi location for a mobile user could place the caller at the WiFi hotspot, not their actual location. Transparency reduces liability. Consider recommending that mobile users call 999 from a landline at their current location whenever possible.
If a customer moves offices but forgets to notify me, is the old location data a problem?
Yes. Emergency services will route calls to the old address. Document that you have a process to capture address changes (e.g., annual audit, terms requiring 14-day notification). If a customer doesn’t update their address, you have documented process evidence but should make proactive outreach efforts.
Sources
Ofcom Emergency Calling and Caller Location Regulations
UK Government Electronic Communications Regulations
ETSI Emergency Call Standards (EN 301 941, TS 102 164)
ITU Emergency Calling and Location Recommendations
NCSC Cyber Security and Business Resilience
Partner Playbook: Emergency Calling Compliance Checklist
| Checklist Item | Responsible Party | Timeline | Evidence Required | Status |
|---|---|---|---|---|
| Verify wholesale partner has Ofcom ECN licence and emergency calling certification | Legal / Compliance | Before onboarding customers | Provider ECN licence copy. Emergency routing SLA documentation. | [ ] |
| Request provider’s emergency calling and location data procedure documentation | Technical / Compliance | Before service launch | Provider procedure document. Signed data processing agreement if applicable. | [ ] |
| Create fixed user address collection and verification process | Operations / Legal | Before first customer onboarded | Address form template. Data validation process documented. | [ ] |
| Create nomadic user written acknowledgement and consent form | Legal | Before first nomadic user onboarded | Signed acknowledgement form (template). Evidence of presentation to customers. | [ ] |
| Test 999 and 112 routing in test environment (fixed and nomadic scenarios) | Technical | Before service launch | Test results document. Call logs. Provider confirmation of location data submission. | [ ] |
| Include emergency calling limitations and procedures in Terms of Service | Legal | Before first customer onboarded | Updated T&Cs document with emergency calling section. Customer sign-off evidence. | [ ] |
| Train support team on emergency calling procedures and nomadic user handling | Training / Support Lead | Before service launch | Training materials. Support runbook with emergency calling procedures. Team sign-off. | [ ] |
| Schedule annual (or quarterly if licensed ECN) emergency calling testing | Compliance / Technical | Ongoing annual basis | Testing calendar. Results documentation each year. | [ ] |
Resell Hosted VoIP with BT Cloud Voice
Join The Network Union Reseller Programme. Earn commission on BT Cloud Voice, broadband and leased lines with full sales and provisioning support.
