Communications

SIP trunking in Jordan.

Connect the phone system you already have to modern voice services — and stop paying for legacy lines.

Keep the PBX. Replace the lines.

If your phone system is working and supported, replacing it is often unnecessary. What usually needs replacing is what connects it to the outside world — physical lines billed per channel, provisioned slowly, and fixed to one building.

SIP trunking delivers those voice channels over your data connection instead. The PBX stays, the handsets stay, the numbers stay. What changes is cost, flexibility and how quickly capacity can be adjusted.

What SIP trunking gives you

Elastic capacity

Add or remove concurrent call channels as demand changes, instead of ordering physical lines weeks in advance.

Number portability

Keep your existing published numbers. Porting is planned and scheduled so there is no unreachable window.

DID ranges

Blocks of direct dial numbers for individuals, departments, campaigns or sites, routed however you choose.

Failover routing

Automatic diversion of inbound calls if the primary site or connection becomes unreachable, configured in advance.

Multi-site consolidation

One trunk serving several locations, with internal dialling between them and calls routed centrally.

Lower line costs

Legacy per-line rental replaced by channels over existing connectivity, typically with better call rates.

Sizing it properly

Concurrent calls, not total users.

Size a SIP trunk

The most common mistake is buying channels based on headcount. What matters is how many calls are actually in progress simultaneously at your busiest point — which for most businesses is far fewer than the number of staff, and for contact centres is far more predictable than people expect.

We size from real call data where it exists, and from realistic modelling where it does not, then leave headroom for peaks rather than for averages.

  • Peak concurrency measured or modelled, not guessed from headcount.
  • Bandwidth calculated for the codec in use, with headroom.
  • Firewall and SBC configuration verified for SIP and RTP handling.
  • QoS applied so voice is not competing with file transfers.
  • Failover destination defined before it is needed.

SIP trunking questions

Will our existing PBX support SIP?
Most systems from the last decade do, sometimes requiring a licence or module. Older TDM systems may need a gateway to convert between technologies. We check your specific platform and version before proposing anything.
Can we port our numbers?
Usually yes. We verify portability for your specific number ranges and current carrier first, then schedule the port. Numbers are ported in a planned window so that inbound calling is not interrupted.
How much bandwidth do we need?
It depends on the codec and the number of concurrent calls, but voice is far less demanding than most people assume — the requirement is consistency and prioritisation rather than raw capacity. We calculate it as part of the design.
What if we want to replace the PBX later?
The trunk moves with you. Many customers use SIP trunking to modernise cost and flexibility first, then migrate to a cloud PBX later as a separate, lower-risk step.

Related solutions

Still paying for legacy phone lines?

Send us your current line setup and call volumes. We'll show you what SIP replaces and what it saves.

Talk to an Expert Get a Quote