4 days ago

Version 5.0.0 - Jan 2026

Full release notes available via TCAP

UI/UX
  • Supporting multiple UCaaS vendors, platforms and services.
    • A Platform is defined as a distinct vendor or technology definition, such as Microsoft Teams or Zoom.  Service such as Direct Routing, or Operator Connect are defined as Services under the Platform.
    • A single number may be assigned and managed across multiple Platforms simultaneously.
  • New Data Tables
    • Data Table controls have been updated to provide a modern design and layout.
    • These now provide a consistent, yet extensible view to support new Platform Users/Numbers features. 
    • The ability to change layout, add/remove columns and export data remains.  Right click the table header or cell data to customize.
  • Failover Routing
    • Failover Routing ensures your calls always reach their destination. If the primary platform fails or is unavailable, calls automatically route to the next platform in your priority list.
    • Designed for customers looking to increase High Availability, ensuring their inbound and outbound calling services are always on.
    • Customers in scope of migrating between services can also benefit, allowing for that extra peace of mind during and following the initial migration period.
  • Branch Routing Groups
    • While TCAP inherently allows for outbound routing from multiple platforms, Branch Routing Groups allow you to receive calls on multiple platforms at the same time, ensuring the fastest response time and maximum availability for incoming calls.
    • Designed for customers migrating between services/locations, looking for that extra peace of mind and customers evaluating new UCaaS platforms.

API
  • With the evolution from legacy Numbers and Users, various endpoints within the TCAP API have been added, updated or retired. 
  • For full detail, please refer to the TCAP API Swagger Documentation.  
  • Please contact PingCo if you require access.