SOT
Enter Store

Solutions

Unified Communications & Telephony

SOT delivers seamless communication architectures tailored to operational needs. SOT offers dual deployment paths: scalable Cloud-Hosted PBX for modern agility, or secure On-Premises Physical PBX hardware for maximum local control. SOT also fully integrates video conferencing and public address systems.

Unified communications is the point where the network stops being infrastructure and becomes something people notice minute by minute. A call that breaks up or a meeting room that takes ten minutes to start is not read as a network problem — it is read as the organisation not working — which is why voice and video are held to a standard of reliability that ordinary data traffic is not.

Nearly all of that reliability is decided on the network rather than on the handset. Voice tolerates very little jitter and almost no loss, so it needs its own VLAN, quality-of-service marking that is honoured end to end, and enough PoE headroom that adding twenty telephones does not exceed a switch's power budget. Deployments that skip this work fine in testing and fail at scale, because contention only appears when the network is busy.

SOT designs the telephony, conferencing, paging and intercom systems together with the network that carries them, so the quality-of-service policy, the addressing and the power budget are one design rather than three assumptions.

What this covers

  • IP telephony and PBX

    On-premise, hosted or hybrid telephone systems with handsets, softphones, call routing, voicemail and call recording where it is required.

  • Meeting room video

    Room systems sized to the room — camera field of view, microphone pickup pattern and display size worked out from the seating plan rather than the room's square metreage.

  • Public address and voice alarm

    Zoned paging and background music, and voice alarm systems where evacuation messaging is a life-safety function rather than a convenience.

  • Door entry and intercom

    Audio and video intercoms at entrances, gates and reception, integrated with the access-control system so a release is logged like any other door event.

  • Quality of service

    Voice and video VLANs with DSCP marking honoured across switching and the WAN, which is where call quality is actually won or lost.

  • Contact centre

    Queueing, routing, IVR and reporting for teams whose job is answering the telephone rather than occasionally using one.

Explore in detail

Each of these has a page of its own — what it involves, what it covers, and the questions that decide the specification.

How we deliver it

  1. 01

    Site survey

    An engineer walks the site and records what is actually there — cable routes, containment, power, ceiling voids, existing equipment and its condition. Most of the cost overruns on a project of this kind are either discovered here or discovered late.

  2. 02

    Design and Bill of Quantities

    A drawn design and an itemised BoQ: every part, its quantity and its price, with the reasoning for the specification written beside it. You own the document whether or not you buy from us.

  3. 03

    Supply from Riyadh stock

    Equipment released against the BoQ from local stock where we hold it, or ordered directly from the vendor where we do not. Serial numbers are recorded against your project, so a warranty claim later does not depend on you having kept the paperwork.

  4. 04

    Installation and commissioning

    Our own engineers install, terminate, configure and test. The testing is documented — link certification, camera fields of view, failover checks — and the results are handed over as part of the file rather than described verbally.

  5. 05

    Handover and support

    As-built drawings, configuration backups, credentials and test results, plus training for whoever will run it day to day. Support and warranty are handled by the same team that installed it.

Standards and regulations

What a deployment is measured against. A consultant or a main contractor will check a proposal against these, so they are named rather than implied.

SIP (RFC 3261)
The session protocol nearly all IP telephony now uses. Sticking to it is what keeps handsets, trunks and platforms interchangeable instead of locking a site to one vendor's ecosystem.
IEEE 802.1p / DiffServ
Layer 2 and layer 3 quality-of-service marking. Marking traffic is easy; having every switch and router along the path honour the marking is the part that requires design.
IEC 60849 / EN 54-16
Sound systems for emergency purposes and voice alarm control equipment. A PA system used for evacuation messaging is a life-safety system and is held to these rather than to ordinary audio standards.
IEEE 802.3af / at
Power over Ethernet for handsets, intercoms and room devices — and the reason a telephony rollout has to be checked against the switch's total power budget rather than its port count.
CITC regulations
Saudi Communications, Space and Technology Commission rules bear on numbering, trunk provisioning and lawful interception where a system connects to the public network.

Sectors we deploy this in

Questions we get asked

Should I choose Cloud-Hosted or On-Premises PBX?

Cloud PBX suits organizations prioritizing scalability and lower upfront hardware cost; On-Premises PBX suits those needing maximum local control — SOT can assess which fits your operation.

Can SOT integrate video conferencing with an existing phone system?

Yes, SOT integrates video conferencing and public address systems with both cloud and on-premises PBX deployments.

Does SOT support multi-branch or multi-site phone systems?

Yes, both PBX deployment paths support multi-site extension and routing configurations.