RTPENGINE
A telecom engineering note from the field.
VoIP, SBC, SIP, WebRTC, Embedded Voice, Observability, SS7, AI Voice, RTPEngine
Telecom engineering, field notes, and research areas
This page is a technical map for writings and notes: SIP/SBC routing, WebRTC, embedded voice, observability, AI voice, call-center systems, Kubernetes signaling, FreeSWITCH, OpenSIPS, RTPEngine, SS7 learning, and practical case studies from call-flow debugging.
Field Notes
INVITE, REGISTER, BYE, CANCEL, response codes, route headers, authentication, trunk behavior, and call-flow notes from real traces.
RTP direction, advertised media IPs, NAT behavior, codecs, jitter, SRTP/RTP boundaries, RTPEngine behavior, and one-way audio notes.
Browser media behavior, ICE, STUN/TURN, SIP over WebSocket, WebRTC-to-SIP bridges, and debugging notes from browser voice experiments.
SIP endpoints, ESP/audio experiments, constrained-device call flows, RTP send/receive, microphone/speaker paths, and device-level debugging.
sngrep traces, Wireshark captures, RTP checks, response-code patterns, logs, metrics, and operational notes for understanding voice systems.
How proxies, SBCs, media servers, PBX systems, carriers, APIs, browser clients, and embedded endpoints fit together.
Latest Blog Posts
Case Studies
Codec list, SDP offer, RTP profile, and downstream carrier media requirements.
Connection IP, NAT, advertised media address, RTP timeout, firewall path, and RTPEngine direction.
Dispatcher and LCR routing strategy for carrier failure, timeout, route selection, and retry behavior.
Browser media, ICE, signaling gateway, RTP/SRTP conversion, and SIP trunk termination.
Recent Projects
Dispatcher, route failover, and carrier trunk testing.
Registration, dialplan behavior, NAT mapping, and RTP checks.
Device audio path, SIP registration, RTP receive/transmit, and auto-answer flow.
SIP over WebSocket, ICE behavior, and browser audio handling.
R&D
RFC notes, SIP/SDP references, SS7 learning, XMPP signaling, RTPEngine behavior, and architecture reading notes.
Small tests, failed attempts, audio experiments, browser voice tests, embedded VoIP trials, and things worth documenting later.
Deployment notes, backup notes, config notes, Git-backed documentation, server layout, recovery steps, and production checklists.
Things to write from real traces: rejected calls, route loops, codec mismatches, registration problems, and media failures.
Topics