PORTFOLIO

Selected Project Experience

Architecture and delivery across telecom, AI voice and full-stack systems. Client identities, recordings and proprietary data are omitted. Screenshots are representative product interfaces from platforms designed in this practice.

Contact center dashboard with queues, live calls and agent status
CASE STUDY

Multi-tenant CCaaS and IPPBX platform

A cloud contact-center product needed one codebase that could host many tenants without mixing call data, agent state or recordings.

Challenge. Isolate tenants, keep SIP and media reliable, and give supervisors a live view of queues, campaigns and agent activity.

Architecture. FreeSWITCH for media, NestJS APIs, Vue 3 consoles, PostgreSQL, Redis, JWT auth and WebSocket events. Prometheus for operational metrics.

What shipped. SIP extensions, queues, IVR, inbound/outbound campaigns, recordings, CDR, DID routing, billing logs and supervisor dashboards.

FreeSWITCHNestJSVue 3PostgreSQLRedis
Discuss a similar CCaaS build →
AI voice operations console with transcript, SIP metadata and call flow
CASE STUDY

Multilingual AI voice and IVR

Voice automation had to work in English, Hebrew and Yiddish, on real phone calls, not only in a web demo.

Challenge. Keep latency acceptable, preserve SIP signalling, and allow a clean handoff from the agent to a human queue when the conversation needed it.

Architecture. FreeSWITCH/SIP for the call path, speech-to-text, LLM decisioning, text-to-speech, and transfer rules back into IVR or agents.

What shipped. Language-aware IVR, telephony integration and automation that could complete or escalate a live call.

AI VoiceSIPFreeSWITCHIVRLLM
Discuss a similar AI voice project →
Cloud PBX admin portal with extensions, trunks and DID routing
CASE STUDY

Self-hosted UnifiedPBX business phone system

Teams that do not want a per-seat hosted PBX still need IVR, queues, recording, WebRTC and tenant isolation on infrastructure they control.

Challenge. Package a complete business phone system — routing, recording, analytics and browser calling — without locking the customer into a hosted vendor.

Architecture. Asterisk 22 core, SIP trunks, time-based routing, call recording policies, CDR, Prometheus dashboards and a browser softphone.

What shipped. IVR, queues, ring groups, failover, role-based access, JWT APIs and multi-tenant data isolation.

Asterisk 22SIPWebRTCCDRMulti-tenant
Discuss a cloud or self-hosted PBX →
Browser WebRTC softphone with in-call controls and keypad
CASE STUDY

WebRTC softphone inside the product

Agents and office users needed to place and receive calls from the browser, without installing a desktop softphone.

Challenge. Bridge SIP and WebRTC, keep hold/transfer/mute reliable, and attach the call to CRM notes in the same screen.

Architecture. Browser media, SIP/WebRTC gatewaying, presence, and an application UI for contacts, keypad and wrap-up notes.

What shipped. In-app calling that sits next to the rest of the business workflow instead of a separate phone client.

WebRTCSIPSoftphoneCRM
Discuss a WebRTC softphone →
Insurance · Dialer · CRM

Insurance contact center and dialer

Multi-tenant insurance CRM with campaign dialers, agent workflows, appointments and policy-related processes on FreeSWITCH, Asterisk, OpenSIPS, Angular, Node.js and MySQL.

Confidential client. Outcome: one platform for outreach, queueing and back-office work instead of disconnected tools.

Real estate · IVR · Campaigns

Real-estate engagement platform

Contact-center and CRM workflows for property teams: broadcasting, IVR, campaign setup, DID and DNC management, with FreeSWITCH at the telephony layer.

Confidential client. Outcome: lead handling and calling lived in the same operating system.

VoIP · SIP · Linux

Yamot / VoIP platform engineering

VoIP infrastructure and application-side communication workflows: routing, server-side engineering and SIP operational work on Linux.

Focused on production routing rather than a demo PBX.

Python · JavaScript · APIs · SaaS

Full-stack communication products

Web applications, APIs, dashboards and business systems integrated with realtime communication infrastructure — including ERP-adjacent telecom operations work.

The software layer is designed with the telephony layer, not after it.

DELIVERY FOCUS

What matters beyond the demo

Reliability

Call routing, failure paths, monitoring and operational visibility.

Maintainability

Clear boundaries, documentation and manageable integrations.

Scalability

Architecture that can evolve with tenants, traffic and product requirements.

Need a similar system?

Send the current stack and the outcome you need. The first reply is an architecture-minded review.

Discuss Your Project