Tech

TAPI Reloaded

Published on:

February 15, 2013

TAPI (Telephony Application Programming Interface) has been a staple in connecting user programs with telephony hardware, evolving from physical devices to virtual software solutions. Widely adopted by the PBX industry, snom ONE also provides a TAPI service provider (TSP), with the latest version offering enhanced functionality. The new TSP supports both incoming and outgoing calls, including automatic call clearing even before the phone is picked up. It also includes a reconnection feature for lost connections, addressing internet reliability issues. Available for both 32 and 64-bit systems, users should ensure they install the correct version for their operating system.

TAPI is one of those die-hard standards from the 90s. Originally designed to deal with hardware installed in the PC, it has evolved over time into a more virtual piece of software that connects the user programs running on Windows with the devices that make phone calls.

Not much of a surprise, the PBX world has widely adopted TAPI. Almost all vendors of PBX systems offer a TAPI service provider that may be used with their PBX. This is like a device driver for the PBX.

snom ONE has its own TAPI service provider (TSP). While the first versions were very basic, the latest one now offers incoming calls. This is an important step forward, because a lot of CRM tools also offer a bridge to TAPI, essentially making the incoming call pop-up possible. But for outgoing calls the new TSP also has enhanced functionality, so calls can be cleared even though the user hasn't even picked up the phone. We found out that not only for SIP connections, but also for CSTA, the internet can be unreliable and the TSP needs to reconnect in case the connection gets lost.

Like before, we offer the TSP for 32 and 64-bit systems. Because of its origin from the 90s, you need to pick the right one for your Windows operating system, as there are dependencies in it. For more information and the latest version, visit our Wiki at http://wiki.snomone.com/index.php?title=Snom_ONE_TSP. If you have the snom ONE TSP installed, uninstall it first and install the new one.

Latest Articles

View All

Vodia Announces Integration with ElevenLabs Voice AI Platform

A streamlined integration connects the Vodia PBX with the ElevenLabs Voice AI Platform using a lightweight IVR JavaScript script and native SIP REFER for call transfers. Audio and call control are handled entirely through standard SIP signaling, while all conversational logic, prompts, voice selection, and routing rules are configured in the ElevenLabs dashboard. This approach removes the need for webhooks or WebSocket connections and keeps the PBX side intentionally minimal, making the deployment clean and production-ready.

January 22, 2026

Why Multi-Tenant Still Matters for MSPs

Multi-tenant architecture allows MSPs to manage multiple customers efficiently on a single, secure PBX while maintaining strict tenant isolation. By sharing infrastructure, MSPs can reduce operational costs, apply updates and security patches centrally, scale customers on demand, and onboard faster without increasing complexity. As cloud and SaaS models continue to dominate, a well-designed multi-tenant phone system provides the control, flexibility, and reliability MSPs need to support growth, evolving requirements, and modern communications workloads.

January 19, 2026

Start 2026 with a cloud PBX built for real-world deployments

A flexible, cloud-neutral PBX built for real-world deployments in 2026, Vodia supports MSPs, enterprises, and service providers with an open, SIP-compliant platform designed for scale. With Vodia PBX version 70 arriving in Q1 2026, the platform brings multi-tenant hosting, reuse of existing IP phones through centralized provisioning, built-in WebRTC softphones, transparent licensing, and partner-driven support, giving organizations full control over modern business telephony without lock-in or hidden costs.

January 13, 2026