Communication systems
SIP/RTP, PBX infrastructure, real-time audio and protocol behavior.
REAZ ROMEN / SYSTEMS ENGINEER
I build where systems meet.
A device can work. A network can work. A backend can work. The harder problem is making them behave as one system.
I design, deploy, debug and operate systems across hardware, firmware, protocols, infrastructure and the interfaces used to run them.
FOLLOW ONE EVENTLOUP VOICE PATH
A call starts with a physical action. It does not stay in one layer.
One useful way to understand my work is to follow the event instead of the technology list. Signaling establishes the session; media follows its own real-time path; operational state sits across both.
CONTROL PLANEsession establishment
01Call controlphysical input
→
02Firmware statedevice logic
→
03Wi-Fi / IPnetwork path
→
04SIP / SDPsignaling
→
05PBX / routesession routing
MEDIA PLANEreal-time audio
AMic / codeccapture
→
BAudio framestiming / buffering
→
CRTPmedia transport
→
DRemote endpointplayout
OPERATIONS ACROSS THE PATH
device staterelease / OTAlogsmetricspacket traces
Simplified architecture view. Deeper project pages separate hardware, signaling, media, infrastructure and verification evidence rather than collapsing them into one “stack.”
SELECTED SYSTEMSComplete engineering inventory →
Systems, not portfolio cards.
Each entry opens into architecture, boundaries, implementation details and the evidence available for that system.
01LOUP Connected Voice Device
hardware → firmware → audio → Wi-Fi → SIP/RTP → fleet↗
02Telephony Infrastructure
endpoints → SIP/SDP → routing/PBX → RTP → packet evidence↗
03OTA Fleet Control Plane
artifact → identity → compatibility → rollout state → device↗
04Distributed Compute & Build Fabric
job intent → scheduler → nodes → execution → telemetry↗
05Wi-Fi CSI Presence Sensing
radio channel → CSI → features → storage → classification↗
06Environmental Intelligence
observations → ingestion → time-series data → operational view↗
07Network Flow Visualization
hosts → DNS / ingress → services → observed flows → drill-down↗
ENGINEERING RANGECONNECTED BY SYSTEM BEHAVIOR
Embedded devices
ESP32 firmware, hardware integration, audio paths, controls and lifecycle.
Distributed infrastructure
Compute, storage, orchestration, ingress, observability and recovery.
Sensing & intelligence
Wi-Fi CSI, RF-derived signals, environmental data and operational interfaces.
ENGINEERING NOTESAll writing →
The architecture diagram is usually the beginning.
I write about the parts that appear after a system is turned on: timing, broken assumptions, protocol behavior, deployment boundaries, observability and recovery.
ABOUT THE ENGINEER
I am most useful when the problem refuses to stay in one box.
My work usually sits somewhere between architecture and operation: map the path, make it observable, isolate the failing boundary, change the smallest useful thing, then verify the system again.