Telephony Architecture
Deploymentβ
Subphonic Transact maintain a cluster of SBCs per region, with multiple regions per geographic deployment.
Implementing the infrastructure as code ethos, whole new deployments now take just hours not days.
Integrationβ
Depending on customer requirements, Subphonic can provide multiple methods of integration.
Each integration is able to support a single customer trunk or multi tenant architecture.
Inlineβ
As the name suggests, Subphonic will sit inline with the existing call flow.
As well as new failover routes, the existing routing can be maintained for failover scenarios.

Tromboneβ
When routes from the Telco to the existing customer SBCs are unable to be updated, then a call trombone can be implemented. The unsecure call, loops from the customer SBCs to Subphonic to be secured and is returned to the source. The now secure call can be delivered to downstream devices.

Dynamic Mediaβ
With many channels to secure, only route media for calls that require a payment.
When the call is established, only SIP is routed through Subphonic while media uses the existing paths.
As soon as Transact is launched, Subphonic requests the media path and renegotiates routing ready for payment.
When payment is completed, the media is released.
