Yeastar Multi-Site PABX Dubai —
One System. Every Branch. Every Desk.

The Transfer That Never Happens

A customer calls your Dubai office asking for the accounts team — and accounts sits in your India branch. So reception says "let me take your number," WhatsApps the branch on a personal phone, and hopes someone calls back. Two locations, two phone numbers, two systems, and every cross-office handover happening outside the company, invisible and unrecorded. It is not a people problem. It is what happens when each site runs its own island of telephony.

The fix is structural: stop buying a PABX per location. One system carries every office, every extension appears in one directory, and that Dubai call transfers to the India branch desk — or a mobile app — in three digits, like the whole company sits on one floor.

The Second Location, Hour by Hour — What Go-Live Actually Looks Like

8:40 AM. The courier box from our Dubai office is on the new reception desk: phones already configured, labelled by name, a small PoE switch, one page of pictures. 9:15. Switch powered, phones plugged into the internet the landlord already provided — each one finds the head-office system on its own and lights up with its extension. Nobody at the new site touches a setting. 10:05. First test: the branch dials three digits and head-office reception answers. Then the other way. Then a transfer, handed across the city like a handoff across a desk. 11:30. The branch's own local line, terminated on a small gateway at the site, goes live — local calls out show the local number, and the number your customers already know keeps working. 12:00. A customer calls the main company number and asks for someone who sits at the new branch. Reception says "one moment" — and the new office takes its first real call, on day one, as part of the company it always was.

That is the whole event. No engineer camped at the branch for a week, no second system to learn, no new number to print. The second location opening next month becomes the second location answering next month — which is why that scenario sits on this page with its own button above.

What Each Branch Actually Needs

Three things: a working internet connection, IP phones on desks, and a PoE network switch to power them. That is the complete branch bill of materials — no server, no wall box, no engineer resident on site. Opening a new location becomes a phones-and-network job you can schedule in an afternoon.

Where a branch needs its own local identity — a local India number on outbound caller ID, or analog lines kept for resilience — an FXO gateway at that site connects local lines into the same central system. Local face, one brain. And it works both ways: the same branch can present the Dubai head-office number when calling your UAE customers — decided simply by which route the call takes. The gateway range is part of the same Yeastar family: see our Yeastar VoIP gateways.

Treat numbers as strategy, not plumbing. The main company number stays published once, forever, and rings wherever you decide — head office by default, a branch by time of day, a queue that spans both. Each branch can hold its own local number for its own market, terminated locally on a gateway, while still living inside the one system. Direct numbers can point at a person's extension so a key account always lands on the right desk, whichever site that desk is in this year. And when a branch moves premises, its number moves with the system's routing — not with the wiring — which is the quiet end of the "new office, new number, reprint everything" tax.

When the Internet Dies — Planning, Not Promises

A centralised system depends on the centre, so we design for failure instead of pretending it cannot happen. The ladder looks like this: UPS power on the head-office comms rack, so a power cut is not an outage. A second internet line at HQ from a different provider, so one carrier's bad day is not yours. Yeastar Hot Standby — a second appliance mirroring the first, taking over if the primary fails. And for businesses that want the centre itself out of the building, the same system as the Software Edition on server infrastructure, or per-branch local-line fallback through FXO gateways so a site can still dial out on analog lines.

What we will not do is promise zero downtime — nobody can honestly. What we design and test with you is how fast recovery happens, and which calls keep working in the meantime.

What honest design looks like per site: head office earns the deepest ladder — UPS as a floor, dual internet where the business case holds, and for operations that justify it, a standing second unit. A branch's ladder is simpler because its risk is simpler: if its internet fails, its local gateway line can still carry local calls out while the link is down, and the company number keeps answering at head office regardless — callers hear a business, not an outage. A home worker's failover is the pocket: desk phone down, the mobile app is the same extension. We write this ladder into the proposal, site by site, so the day something breaks you are executing a plan, not inventing one.

Which Edition Carries a Multi-Site Business

What actually drives the model choice, in order: total extensions across every site including the home workers you will add by year two; concurrent calls at the busiest hour, which multi-site estates hit sooner than single offices because inter-site calls count too; and trunk count once each branch's local lines join the party. A two-site, thirty-person company sits comfortably in the range's entry sizing; five sites and a hundred-plus people is mid-range territory with expansion headroom; and once an estate turns into a fleet — many sites, hundreds of users, its own server room — the Software Edition on your hardware scales past any appliance ceiling. We size on your eighteen-month picture, not your moving-day headcount, because re-boxing a phone system is the one cost this architecture exists to delete.

For most UAE multi-site businesses our recommendation is the Software Edition at head office — one system licensed to your actual size, from 10 to 10,000 extensions, expandable in place by licence, running on your own server, virtual machine or cloud account, or delivered as a pre-loaded appliance that arrives installed and ready to rack. Every branch registers to it, and growth never means replacing the system. Where a customer specifically prefers a P-Series box, the appliances carry the same design — one unit at head office, every branch registered to it — and we supply and support both paths. And where a branch is genuinely separate — different licence, different ownership — a small system of its own still fits; we will tell you honestly which pattern your structure needs, and price both.

Multi-Site & Remote Working — Straight Answers