Two-Device Local Calling Is the Fastest Telephony Sanity Check
A small closed call loop isolates core SIP/RTP behavior before carrier and DID complexity is introduced.
PBX
Why the Firmware Has to Stay PBX-Agnostic
Hard-coding one PBX would turn infrastructure choice into a firmware release dependency.
Keep Device Firmware PBX-Agnostic
Firmware should consume SIP account and transport configuration without embedding one PBX vendor's deployment assumptions.
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 pbx Application Name Inside the Celery Command Is an Architecture Clue
What process entrypoints reveal about how telephony logic and background work connect.
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.
My First FreeSWITCH Lab After Getting Comfortable with Asterisk
FreeSWITCH forced me to separate the concepts I understood from Asterisk from the implementation details I had simply memorized.
PBX Registration Health Is Not Call Health
A green registration table can coexist with broken dialog routing or media.
What the celery -A pbx Command Reveals About Runtime Ownership
How the worker command ties infrastructure configuration to an application module.
Local PBX Testing Removes the Internet Before It Removes Complexity
A LAN test still exercises SIP, RTP, codecs and clocks while excluding WAN variability.
Five Devices and Twenty Devices Are Different Tests
Fleet size introduces registration churn, simultaneous calls and operational visibility that a pair cannot show.