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.
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.
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.
B2BUA call control applies the service rules; integration and operational tools make those rules manageable in the network.
The B2BUA tracks each SIP session as supplementary services are applied. VoLTE and VoWiFi calls use the same call-control foundation.
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.
PCF/PCRF and OCS hooks connect call treatment with QoS and real-time charging. Validate the trigger sequence against the commercial service being offered.
SBC and IMS-core interfaces carry the call. Northbound APIs connect provisioning and service configuration to OSS/BSS.
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.
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.
These views show where TAS connects to the IMS core, how subscribers configure services and what the operations team integrates.

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

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

Operational integrations: KPIs/metrics, SNMP traps, logs (ELK), provisioning API/GUI, MRF, CDR export.
Compare the call flows, feature interactions and charging triggers on the existing and target TAS before changing live routing.
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.
Blue/green upgrades, SLO guardrails and health-checked components. SRE runbooks and dashboards included.
The scope can cover a core supplementary-service deployment, wider service integration or the operating model for a geographically redundant service.