The Future of Telco
Starts With TCAP
100% automated. 100% simple. TCAP makes telecommunication faster, easier, and more scalable.
Why Telcos and MSPs Use TCAP
Eight core functions, tri-tiered billing, and holistic integration make TCAP the easiest way to add Teams Calling to your offerings.
The UI is built on our open API. This means that carriers can simulate and replicate all functions of TCAP into their own systems should they require it. The UI is white labelled and capable of being reproduced and customised on a per telco basis. No other platform has this capability.
The Database contains the data sets for the platform. Storing configuration, billing, and other required data. This database can be separated per country / telco and per customer if security and sovereignty requirements mandate this.
The SBC’s are the voice routing and call termination behind TCAP. We are vendor agnostic and will work with existing SBC infrastructure or allow you to leverage our cloud powered SBC’s.
The Engines of TCAP are the driving modules of orchestration into MS Teams, Office 365 and Operator Connect. The Engines also connect and utilise the Graph API. The power of the TCAP engines allow for further integration into other business systems and surfacing of other solutions to the TCAP platform. Our roadmap of features uses the power of the Engines module to allow for a rapid speed to market for new products or additional automation of existing offerings.
The API is the core foundation of TCAP. Everything is built within the API first. This is critical to our scalability and integration capability. The API is fully documented using Swagger.