PBX and IP telephony systems in Saudi Arabia

How a business phone system works

When someone dials your main number, the carrier delivers the call over a SIP trunk or a legacy line to the PBX. The PBX looks at the number dialled, the time of day and any rules you have set, and sends the call to a person, a group, an auto-attendant menu or voicemail. Handsets, softphones and mobile apps register with the PBX as extensions, and outgoing calls take the reverse path. Everything in between runs on your network, so the quality of a call is the quality of that network.

That is simple in principle, but the decisions are many: where the PBX lives, how many calls at once the trunks must carry, what happens when the internet or the building power fails, and which other systems need to place or receive calls. We work through these first, because they set the cost and the risk.

What a modern system includes

An IP PBX (on-premises or hosted) handles extensions, call routing, voicemail, call recording where lawful and required, and reports. External calls come through SIP trunks from a licensed local carrier, with analog or ISDN lines retained where a site still needs them.

Some lines must keep working when the data network fails: lift emergency phones, alarm communicators, and certain emergency lines. We identify those during design and give them a path that does not depend on a single switch or power supply.

Hotels and hospitals

Hotel systems integrate with the property management system for check-in and check-out, room status, wake-up calls and call charging. Hospitals need fast internal paging, DECT or Wi-Fi handsets for staff on the move, and integration with nurse call so a patient call reaches the right person. We define each integration and test it with the system owner before go-live.

Hosted or on-premises PBX

Hotels and hospitals usually choose on-premises or hybrid because the integrations and the need to keep lines alive during outages weigh heavily. Small offices often choose hosted for simplicity.

Trunks, numbers and lines

External calls come from a licensed local carrier. Planning covers how many simultaneous calls the trunks must carry (typically sized from the busiest hour and the number of users), which numbers are kept or ported, how a caller reaches a department after hours, and how emergency calls are handled. Direct inward numbers can be assigned to key people, while everyone else is reached through the main number. For critical sites we ask for two trunks from different paths, or one trunk plus a cellular backup gateway.

Analog lines are not gone. Lift phones, alarm communicators, fax machines and some emergency telephones still need them. Gateways convert them to SIP, with their own battery backup where the line must work during a power cut. We identify these lines at survey stage and keep a list of what depends on them.

Handsets and mobility

• Desk phones: powered over Ethernet, with the features the role needs, from a basic handset to a receptionist console.
• Softphones: apps on a computer or mobile, useful for hybrid working; they need a reliable headset and network.
• DECT: cordless handsets over a dedicated radio system, with good battery life and a clear voice; well suited to hotels, warehouses and wards.
• Wi-Fi handsets: use the building's wireless network, so that network must be designed for voice, as described in Wi-Fi and wireless links.
• Mobile extensions: a mobile app or a gateway makes staff reachable on one extension number wherever they are.

Network readiness and voice quality

Voice is sensitive to delay, jitter and packet loss. As a planning figure, one call uses about 80–100 kbps of network capacity each way with the common codecs, and the total depends on how many calls run at once. The bandwidth is rarely the issue; the issue is priority. We place phones on a voice VLAN, apply quality-of-service marking and queueing at the switches and the router, give phones PoE with enough budget, and check that the internet link has the capacity and stability if calls go outside through a hosted provider. Where wireless handsets are used, roaming between access points must complete without dropping a call.

Survivability and power

A phone system must work when other things fail. We write down which extensions and lines must survive a network failure, a power cut, a server fault and a lost trunk, and design for each: local survivability units at branches, analog fallback lines on critical extensions, a second trunk path, and battery or UPS power for the PBX, the core switch and the PoE switches serving the handsets. Without this, a power cut can disconnect the reception desk and the lift phones at once. The wider approach is covered under power continuity.

Integration with other systems

A phone system becomes more useful when it talks to the rest of the building. Intercom stations can ring desk phones and be answered like any call, and the same extension can open the door. Nurse call can deliver patient calls to DECT or Wi-Fi handsets. Public address can be paged from a phone. In hotels the property management system exchanges check-in, room status, wake-up calls and charging with the PBX. Wireless networks carry the mobile handsets, and video surveillance alerts can ring a guard's phone. Each integration is defined in writing, tested with the system owner and documented.

Commissioning and handover checklist

• Every extension called internally and externally, with audio checked in both directions.
• Inbound and outbound calls tested on each trunk, with caller ID and number format correct.
• Call flows tested: hours, after-hours, holidays, queues, hunt groups and voicemail.
• Behaviour tested during a network, power and trunk failure, compared with the survivability plan.
• Emergency calling and lift or alarm lines tested end to end.
• Integrations (PMS, nurse call, intercom, paging) tested with the system owner.
• Call recording, where used, checked for retention and access rules.
• Directory, user guides, administrator accounts and backups handed over, with training for the receptionists and the administrator.

Common mistakes and how to avoid them

• Leaving voice on the default network: voice with no priority breaks up whenever someone downloads a large file. Use a voice VLAN and QoS.
• Forgetting analog dependencies: lifts, alarms and gates may be wired to old lines. List them at survey stage.
• A single trunk for the whole site: one failure removes all external calls. Provide a second path where the risk justifies it.
• No plan for moves and changes: staff turnover leaves wrong names on directories. Agree who maintains the system.
• Underestimating recording rules: recorded calls have legal and privacy requirements. Define the basis before enabling.
• Skipping end-user training: transferring a call or using voicemail is a common source of complaints. Train the receptionists first.

Maintenance and testing

A planned visit covers backup of the PBX configuration, software updates in a controlled window, checks of the trunk status and call quality reports, tests of survivability and fallback lines, battery checks, and a review of unused or wrongly set extensions. Moves, adds and changes are handled as requests: new users, departures, group changes and holiday schedules. Reports show where calls are lost or abandoned, which helps adjust the routing. Our maintenance service covers the scheduled and the on-request work.