Telecom · VoIP · Conferencing

Tacodi — SIP & conference telephony (C++)

Sevendyne built a remote C++ engineering team for Tacodi, then that team worked with Tacodi’s product leads to design and ship SIP signalling, network phone interfaces, and call-control paths operators rely on in live meetings.

3-minute CTO brief

We staffed dedicated C++ engineers for Tacodi and seated them with the product team — standups on call-path bugs, PR reviews on signalling changes, and pairing with Tacodi tech leads on adapter layers. Conference products fail when SIP state and media paths are tangled. The team extended Tacodi’s C++ core with explicit call state machines, separated signalling threads from mixing, and adapter layers per network-phone interface — same engineering discipline as our Qt trading work, different domain.

Complexity: SIP lifecycle · hardware adapters · live calls
Not: A web UI wrapper around a third-party PBX
Lineage: Telecom delivery (Speechlogix partnership)

Native C++ · SIP · conference telephony

Session architecture

SIP INVITE/ACK/BYE and re-INVITE for hold/transfer run on control threads. Media bridges mix only after negotiated codecs are locked. Hardware phone events normalize through per-vendor adapters into the same FSM soft clients use.

Decision	Why
Explicit call FSM	Conference transfers stay auditable under production load
Adapter per phone interface	Field deployments vary; isolate vendor quirks
Call-ID correlated logging	Field support can trace one bad session end-to-end

Production outcomes

SIP and phone-interface modules shipped in conferencing products.
Native C++ depth beyond application-layer outsourcing.
Part of long-running telecom delivery lineage.

Download technical brief (PDF) Discuss a C++ / telecom programme