My First Asterisk Lab Was Mostly a Networking Lab
Two softphones and one Asterisk server were enough to show that a phone call is really several network problems stacked together: registration, signaling, media and NAT.
Asterisk
The RTP Port Range Is Part of the Deployment Contract
Media ports must agree across PBX configuration, firewall policy, containers and the surrounding network.
Killing sngrep Was Not Enough: Finding the Orphan Process Behind 80 ms Bursts
A long-running packet tool looked suspicious, but removing it did not fully restore 20 ms scheduling.
SIP Registration Success Does Not Mean Calls Will Work
REGISTER proves one control-plane exchange; it does not prove two-way media, codecs or call-state behavior.
Why Asterisk Was the Right PBX for the LOUP MVP
The first PBX needed to be inspectable, scriptable and easy to correlate with packet captures.
The Geography Was Larger Than the Firmware Optimization
Engineering time was being spent chasing tens of milliseconds in firmware while the media route crossed Bangladesh and Ohio twice.
Routing Calls Across Two PBXs Without Turning Kamailio into a PBX
A two-PBX lab clarified the boundary between SIP routing at the proxy and dialplan or application behavior inside the PBX.
Asterisk Dialplan Started Making Sense When I Treated It as Routing
The Asterisk dialplan felt less like telephony syntax once I treated contexts and extensions as a routing policy for calls.
Why a SIP 401 Response Usually Did Not Mean the Call Failed
Digest authentication made much more sense once I saw 401 as part of a challenge-response exchange rather than a generic failure code.
Why a Clean PBX Forwarding Trace Still Did Not Mean Zero Lag
After server cleanup, Asterisk forwarding became fast, but conversation still felt delayed.
The PBX Scheduler Bug That Looked Like an ESP32 Audio Bug
The device received media in repeating bursts that looked like a local queue or I2S starvation problem.
Reading My First SIP REGISTER and INVITE in Wireshark
SIP became much less mysterious once I stopped reading it as 'phone system traffic' and followed it as a text-based request and response protocol with explicit state transitions.
SIP Transactions and Dialogs Finally Made Call Flow Less Confusing
SIP became easier to debug once I stopped treating an entire call as one exchange and separated individual transactions from the dialog that ties them together.
systemd Logs Became Part of My VoIP Troubleshooting
Service state, bind failures and restart loops often explained a broken PBX before I needed to inspect a single SIP packet.
SIP Registration Expiry Explained Why Phones Disappeared After a While
A successful REGISTER is temporary state, so expiry, refresh timing and NAT mappings all matter if an endpoint is expected to remain reachable.
PBX Timer Underrun Can Sound Like an Endpoint Bug
Server scheduling can inject media timing problems even when embedded firmware has not changed.
Extension 3004 and 3005 Became Reference Endpoints
Named test identities make repeatable call scenarios easier to describe and automate.
Inbound DID Testing Proves a Different Route Than Extension-to-Extension Calls
External ingress adds routing and policy that a local PBX call does not exercise.
Reading RTP Sequence, Timestamp and Arrival Gaps Together
Packet loss, reordering and burst arrival can sound similar but require different fixes.
timerfd Gave Me 21–26 Ticks When I Needed About 50
Asterisk was configured for 20 ms media timing, yet packet forwarding arrived in scheduler-sized bursts.