It is the question that comes up late in almost every phone system evaluation, usually from whoever is responsible for health and safety rather than from IT: if a member of staff picks up a desk phone and dials 119, what actually happens?
The answer for a properly configured cloud phone system is: the call connects, exactly as it would from any other line. But “properly configured” is doing real work in that sentence, and the differences between VoIP and an old copper line are worth understanding before you need them rather than during an emergency.
Jamaica’s Emergency Numbers
Three numbers matter for most businesses:
- 119 — Police
- 110 — Fire Brigade and Ambulance
- 911 — also recognised in Jamaica and routed to emergency services, largely because so many people arrive expecting the North American number
A business phone system should pass all three through without requiring a prefix, without a delay, and from every extension including ones that are otherwise restricted from making outside calls.
Why VoIP Emergency Calling Is Different
A copper line is tied to a physical address by definition. The pair of wires runs to your building; the exchange knows where it terminates. Location is a property of the line itself.
A VoIP extension has no such tie. The same extension can be on a desk in New Kingston in the morning, on a laptop in Mandeville that afternoon, and on a mobile app in another country the following week. That mobility is the main reason businesses move to the cloud, and it is precisely what breaks the old assumption. The network cannot infer where the caller is from the call itself.
This creates three practical requirements.
1. Every extension needs a registered service address
Your provider should hold a physical address against each number or extension, and it should be the address where the phone actually sits. When a business moves office, adds a branch, or gives a new remote worker an extension, that record has to be updated. A great many businesses complete an office move and update everything except this.
2. Emergency dialling must bypass every restriction
If you have applied call restrictions — and most businesses should — make sure the rules explicitly permit 119, 110 and 911 from every extension, including phones in reception areas, warehouses, and rooms where outbound calling is otherwise blocked. This is a common and serious configuration mistake: a phone locked down to internal calls only, which cannot reach emergency services at all.
3. It must work when the internet does not
This is the honest limitation of any internet-based phone service. If the connection is down and there is no failover, the desk phone cannot place any call, emergency or otherwise. It is the reason every business should know what its fallback is — a mobile on the premises at minimum, and ideally a second connection. Options are covered in failover and redundancy and backup power.
The Remote Worker Problem
Staff working from home present the sharpest version of this. An extension registered to the head office address, used by someone in another parish, will not automatically tell emergency services where that person is.
Reasonable practice:
- Register the actual working address for permanently remote staff, rather than the office.
- Tell staff plainly that in an emergency at home, a mobile phone is the correct thing to reach for. This should be written into your remote-working policy, not assumed.
- Review it when people move. The record is only as good as its last update.
None of this is a reason to avoid cloud phones. It is a reason to be deliberate about a detail that copper handled invisibly.
What to Ask a Provider Before You Sign
Five questions, and the answers should be immediate:
- Do 119, 110 and 911 connect from every extension, with no prefix?
- What address is held against my numbers, and how do I update it?
- Are emergency numbers exempt from outbound call restrictions by default?
- What happens to an emergency call if my internet is down?
- Can I test it safely?
A provider that cannot answer these clearly is telling you something useful about how carefully the rest of the service is put together. The broader version of this checklist is in verifying your provider is licensed.
How to Test Without Wasting Emergency Resources
Do not dial 119 to see what happens. Emergency lines are a scarce public resource and a test call occupies a call-taker who may be needed elsewhere.
Instead, ask WOCOM to run a routing verification from our side. We can confirm that an emergency-dialled call from your extension is classified and routed correctly, and that the registered address is right, without placing a live call to emergency services. This takes a few minutes and should be repeated after any office move, any new site, and any significant change to your dial plan.
Put It in Your Onboarding
The most reliable safeguard is not technical. New staff should be told, on their first day, what to dial in an emergency and from which device. Phone systems change; the muscle memory of picking up the nearest handset does not. A one-line note in the induction pack has prevented more problems than any configuration setting.
To review emergency dialling on your WOCOM system, or to have your service addresses checked, call 876-326-1212, message us on WhatsApp, or start from the Cloud PBX page.
Continue exploring
Ready to upgrade your communications?
Talk to our team about the right solution for your business.
Book a Demo Contact SalesEverett Kildare is WOCOM's voice and infrastructure specialist, with more than 25 years of experience designing and running carrier-grade voice, SIP and virtualization infrastructure. Holding a BSc in Information Technology, he has built, secured and migrated phone systems for businesses of every size. Everett writes WOCOM's technical coverage of SIP trunking, cloud PBX, contact centres, business continuity and migration.