Unified Communications

Unified communications here is voice and meeting connectivity for a customer site: the endpoint, the calling or meeting platform, and the licensed path to the other person or room. Voice, video, and rooms. It is an engineering scope. It is not a telecom operator license.

The published scope can include IP telephony, SIP toward the contracted carrier, a customer-owned or subscribed PBX, Teams Phone when the license includes it, video, meeting rooms by model, a contact center when queues and hours are named, and collaboration endpoints sourced against a model number.

IP telephony is voice carried over the data network for the desk and shared endpoints the design names. The phone, the platform, and the network path all have to support that call.

An IP phone registers to the PBX or hosted service, places calls according to the dial plan, and sends voice as media across the network. Power, the voice VLAN where one is used, and authentication follow the platform. Support for every PBX or for Teams is not assumed from the word “IP phone”.

A PBX is the calling platform that registers endpoints and routes calls. In this scope it is a platform the customer will own or operate, or the hosted equivalent they subscribe to.

A hosted PBX is a calling service the customer subscribes to, operated under that provider’s agreement. Administration, features, and continuity follow that agreement. It is not automatically offered by Novatelia.

A customer-managed PBX is operated in the customer’s environment. A hosted PBX is a subscribed service under a separate provider agreement. Neither model is universally preferable. Endpoints, carrier integration, licensing, recording if it is contracted, and continuity are specified for the model that was chosen.

SIP trunking is the signaling arrangement that connects the calling platform to the carrier or hosted service the customer contracts. The media path is separate from the signaling. A SIP trunk is not itself a telecom license.

External calls need an authorized carrier or hosted service the customer contracts. Novatelia does not issue numbers and does not publish a carrier interconnection.

No carrier license is published. Public telecommunications, numbering, and related regulated services may require licenses depending on the jurisdiction and the service model. This page does not invent an Oman licensing category or claim operator status.

Existing numbers can be considered when the contracted provider supports them. Numbering rights are not assumed, and international calling rates are not published.

Teams Phone adds business calling to a Microsoft 365 tenant when the license and a supported PSTN arrangement are in place. The client or a supported endpoint uses Microsoft’s calling services and the customer’s approved configuration to reach the destination.

No. Teams meetings and Teams Phone are different. Teams Phone is specified only when that tenant’s license includes it.

No. Microsoft 365 is the tenant, mail, and collaboration suite. Teams Phone is the calling path when that tenant’s license includes it. The two are specified separately and linked.

Microsoft calling plans, Operator Connect, and Direct Routing are possible models where Microsoft and the provider currently support them for the customer’s country and tenant. They are not assumed to be available in Oman or across the GCC, and they are not assumed to share one SIP-trunk design.

No. A phone works with Teams only when that exact model is supported for the tenant’s configuration. The model number and the firmware matter.

A Teams or Zoom certificate is the manufacturer’s statement about an exact device model and a platform version. It is read from the manufacturer’s documentation for that model.

No. A Teams or Zoom label on a device is the manufacturer’s certification of that model, not a Novatelia credential.

A room design considers displays, a camera, microphones, speakers, a controller, the licensed platform, and the network and power. The final list follows a room survey and the supported models.

Microphones are selected for the room, the seating, and the platform. Coverage is confirmed in the room. A diagram on this page does not certify microphone coverage.

An endpoint is the user-facing device or application: a desk phone, a shared phone, a softphone, a Teams client, or a room system, identified by model where procurement depends on the model.

A session border controller is the boundary component used where the design needs one between the calling platform and the provider, for signaling, media, and security policy. It is specified when required. It is not drawn into every design.

Latency, jitter, packet loss, bandwidth, codec choice, quality-of-service classification, wired or wireless access, WAN performance, firewall and address translation, the carrier path, and the endpoint itself. A design objective, a measurement, a carrier commitment, and the caller’s experience are different facts.

Jitter is variation in the delay between voice packets. It is one input to how a call sounds. This page does not publish an acceptable jitter number as a guarantee.

Lost voice packets can be heard as gaps or distortion, depending on the codec and the loss. Zero packet loss is not promised.

Quality of service is the classification and queuing of voice traffic on the network the customer controls, so voice can be preferred over other traffic on that network. It does not govern the public internet or the carrier’s network beyond the contract the customer holds.

No. Voice quality depends on the path, the endpoint, and the carrier the customer contracts. A figure is not published on this page.

A contact center in this scope is a platform with queues, a named number of agents, and operating hours, reached through the approved calling path. It is included when those items are specified.

Agent count, hours, queue behavior, inbound and outbound scope, supervision, licensing, reporting, and any recording or privacy rule the customer requires. Real call volumes are not invented here.

Multiple sites can share a calling design when numbering, the provider, the WAN, administration, and local site conditions are specified. Global carrier availability and cross-border numbering rights are not assumed.

Administrative access, device credentials, account lifecycle, network segmentation, platform patching, logging, and access governance are specified for the platforms in scope. Call recording follows the customer’s privacy rules where recording is contracted.

TLS or SRTP can be used where the platform and the path support them and they are configured. Encryption of every SIP call is not assumed, because the carrier leg and the far end have to support it as well.

The room, the exact model, the firmware, the platform it is certified or supported for, the registration method, the licenses, and the support lifecycle. A certificate on the box is the manufacturer’s, for that model.

Where the agreement includes them, checks can cover endpoint registration, internal calling, authorized external calling, routing, audio, video meetings, device compatibility, failover that was specifically designed, emergency-calling configuration relevant to the provider, and the administration notes. A test result is recorded. This page does not show a pass log or a call-quality score.

Open the RFQ draft or contact Novatelia. An RFQ saves a browser draft. It does not publish a price, telecom provider status or quotation reference.