Current Location ：
Coordinating Emergency Services Communication for Multi-Site Businesses
When emergency services attend an incident at a business site, the assumption is that the telephone number they call reaches the site itself. In a multi-site organisation that assumption frequently fails. The main number may route to head office, the site may have no published number of its own, or the call may reach a phone nobody recognises because it belongs to a shared communications system. Preparing for this costs very little and is worth doing properly.
The Assumption That Fails
Emergency services call the number they were given or the number on the premises. If the number listed on site belongs to a central switchboard in another city, or to a platform that rings a queue rather than a person, the response is delayed while the call is transferred and someone works out where the call came from. This is not a platform fault; it is a design consequence of centralising telephony without centralising identification.
What Each Site Should Have
- A number that rings directly at the site — Or at least a site-identifiable route that a receptionist answers immediately
- A posted site phone number — The number shown on site must be the number that reaches the site
- A current site address on file — With the carrier for every number associated with that site
- A named contact on site who knows the site layout — For the first few minutes of any emergency response
- An emergency access route — How responders reach the person who called, and which entrance
- A documented site emergency plan — Including who calls emergency services and from where
Where Centralisation Works Against You
Centralised call routing is commercially sensible and operationally sound for ordinary calls, but it can remove site identity from the telephone number. Three patterns cause most of the difficulty. A single main number across all sites means the number carries no site information. A per-site number routed to a central queue means the site is identifiable but the answering position is not. A number ported to a group that no longer includes that site means emergency services reach a disconnected number.
Making Identification Robust
A practical mitigation is a site-identification procedure that does not depend on the number. When a call is placed from any site, the receptionist or automated greeting should identify the site, so the receiving end knows where the call is before asking. Combined with a correctly registered address per number, this gives two independent routes to the right site rather than one, which is what makes the difference when the single route fails.
Keeping Records Current
The most common preparation failure is not doing anything. Addresses change, staff move, sites close, and numbers get reallocated, and none of these update the carrier records automatically. A scheduled review of registered addresses, site numbers, and emergency contact names, with the review actually performed and recorded, is what keeps the information usable. Include sites that have closed, because a number still routing to a closed site is a live problem rather than a historical one.
Testing the Response
- Call each site's published number from an external line — Confirm the site is reached, not head office
- Ask the answering position to identify the site immediately — The greeting or script should do this without prompting
- Confirm the registered address matches the site address exactly — Check with the carrier, not from an old invoice
- Verify emergency calling works from that site's own extensions — Not only from head office
- Review the emergency contact list for departed staff — Quarterly is sufficient for most estates
Redstone Approach
Redstone IP-PBX platforms support per-site extension numbering, per-site greetings that identify the location to callers, per-site emergency call routing, and central management that allows the whole estate to be verified from one place. Redstone can help produce a site-by-site verification record covering published numbers, registered addresses, and routing, so the estate's emergency communication is documented rather than assumed.
Redstone supports multi-site emergency communication preparation with per-site identification, routing verification, and a documented estate-wide verification record.
Redstone Systems, Inc. founded in Delaware, USA in December 2002, has been the ODM vendor for many well-known communications companies, serving the Southeast Asian market. In 2020, Redstone Systems will begin to return to the North America market with its self-developed brand.
Redstone has a complete product line of intelligent voice gateways, providing IP-PBXs, analog VoIP gateways (FXS/FXO), digital VoIP gateways (E1/T1), border appliances, and session boundary controllers (SBCs).
With advanced technology in digital signal processor (DSP), speech coding and speech processing, as well as efficient operational tools such as cloud remote management, auto provisioning, Redstone gateways are widely used in markets of enterprise communications, cloud communications, call centers, operators’ IMS/SIP trunks, bringing users friendly, efficient and reliable communication experience.
For more information about Redstone, You can follow us on Facebook, Linkedin, and Youtube to be the first to get the latest news.
