π Weβre Hiring! Voice Engineer (L2/L3) at https://t.co/aCFxNa5qzp
πΉ SIP / VoIP / SBC
πΉ Microsoft Teams Telephony
πΉ PSTN, SIP Trunks & CCaaS
πΉ Wireshark & PCAP troubleshooting
π GIFT City, Gandhinagar, Gujarat
π’ Onsite | πΌ Full-time
π‘ Experience: 4+ years
π§΅π
most of my time lately is number porting, usage-based billing edge cases, and call quality monitoring for dialog365 β not glamorous, but it's where things actually break. if you're building any of that, say hi. what are you building?
I used to think teasing a feature early built anticipation. wrong β it just meant weeks of explaining delays to people who were waiting. now nothing gets posted until it's live and someone can actually use it.
unpopular opinion: chasing sub-300ms latency in voice agents is mostly wasted effort. people tolerate half a second of silence in normal conversation without noticing.
the money's better spent on turn-taking and interruption handling than shaving another 100ms off the pipe.
trying to decide whether siprtc should auto-failover to a backup STT provider on error, or just hard-fail and alert. auto-failover hides outages from users but if the backup is worse quality, they never know why calls got harder to transcribe. no clean answer yet.
trying to pick a default jitter buffer size for dialog365. 150ms feels safe on paper but I don't have real data on how many callers hit bad networks. tempted to ship it anyway and log drops to tune later.
i assumed more compute would fix latency spikes in voice pipelines. wrong β the bottleneck was queueing at the media server, not cpu. now i check queue depth before i ever add a box.
a voice agent should know when to stop automating. dialog365 has AI-native handoff to a human contact centre agent, so the call can move to a person when the conversation needs one.
iβm building dialog365 for the part after the voice AI demo: low-latency conversation, a choice of STT and TTS providers, and a clean handoff to a human agent when automation is no longer useful.
dialog365 voice agents support elevenlabs, microsoft, google and deepgram for STT and TTS. contact centres can choose the speech stack that fits their calls instead of being tied to one provider.
unpopular opinion: chasing sub-300ms latency in voice agents is mostly wasted effort. people tolerate half a second of silence in normal conversation without noticing.
the money's better spent on turn-taking and interruption handling than shaving another 100ms off the pipe.
trying to pick a default jitter buffer size for dialog365. 150ms feels safe on paper but I don't have real data on how many callers hit bad networks. tempted to ship it anyway and log drops to tune later.