Skip to content
Telecom · Flagship

Telephony Application Server (TAS)

A subscriber enables forwarding, barring or another supplementary service. OVOO TAS applies those choices to IMS, VoLTE and VoWiFi calls, resolving feature interactions and connecting call control to policy and charging.

Carrier-gradeLow-latency SIP signalingHorizontally scalable

Decide which service takes precedence

When several services apply to one subscriber, their order changes the outcome of the call. Define that treatment in TAS, then validate the interaction between subscriber configuration, call state and PCF/OCS decisions.

  • • Which supplementary service takes precedence
  • • How subscriber settings reach call control
  • • When policy and charging triggers are raised
  • • What operations can trace after a call

The controls behind supplementary services

B2BUA call control applies the service rules; integration and operational tools make those rules manageable in the network.

Control the IMS call state

The B2BUA tracks each SIP session as supplementary services are applied. VoLTE and VoWiFi calls use the same call-control foundation.

Resolve competing services

Forwarding, barring and other services can affect the same call. The interaction engine orders and gates them so the result follows the configured service rules.

Connect policy and charging

PCF/PCRF and OCS hooks connect call treatment with QoS and real-time charging. Validate the trigger sequence against the commercial service being offered.

Integrate network and subscriber systems

SBC and IMS-core interfaces carry the call. Northbound APIs connect provisioning and service configuration to OSS/BSS.

Trace a service decision

Structured logs, tracing and service-level indicators help operations follow the call-control path. Dashboards and alerts support investigation when the observed treatment differs from the intended service.

Release changes under operational control

Use containers, GitOps and blue/green deployment with upgrade and rollback procedures. The operating scope includes the runbooks needed by the team responsible for voice services.

See the network and provisioning boundaries

These views show where TAS connects to the IMS core, how subscribers configure services and what the operations team integrates.

TAS overview diagram

TAS overview

High-level architecture: LRF/MMTel, SIP Service Broker, provisioning stack, MRF, IMS Core connectivity.

SIP-based user configuration diagram

SIP-based user configuration

Self-provisioning with SIP feature codes (activate/deactivate services via TAS).

Integration view diagram

Integration view

Operational integrations: KPIs/metrics, SNMP traps, logs (ELK), provisioning API/GUI, MRF, CDR export.

Validate service behaviour before changing the primary TAS

Compare the call flows, feature interactions and charging triggers on the existing and target TAS before changing live routing.

1) Interop first, replace later

Start as a service broker in front of your current TAS/SBC. Mirror flows, validate features and charge triggers, then promote OVOO TAS to primary.

  • • Parallel run (shadow/canary)
  • • Policy/OCS hook validation
  • • Automated checks & rollback

2) Cut over against agreed operating criteria

Blue/green upgrades, SLO guardrails and health-checked components. SRE runbooks and dashboards included.

  • • Deterministic feature ordering
  • • Session continuity & retries
  • • Structured tracing & SLIs

Define the TAS delivery scope

The scope can cover a core supplementary-service deployment, wider service integration or the operating model for a geographically redundant service.

Foundation

  • B2BUA core & supplementary services
  • Initial PCF/OCS integration
  • Observability & basic HA
Request scope

Scale

  • Service Broker integration & interaction engine
  • Zero-downtime upgrades
  • Runbooks & SRE practices
Request scope

Enterprise+

  • Geo-redundancy & compliance triggers
  • Advanced policies & governance
  • Managed SRE or full handover
Request scope
Discuss TAS