Post
Networking layers for voice troubleshooting
The OSI model is a troubleshooting map, not a claim that every VoIP feature fits neatly into one layer.
| Layer | Voice-relevant examples | Failure symptoms |
|---|---|---|
| 1 Physical | Power, cabling, fibre, radio signal | Device offline, flapping link |
| 2 Data link | Ethernet, Wi-Fi, VLAN, QoS markings | Wrong VLAN, poor Wi-Fi, dropped frames |
| 3 Network | IPv4/IPv6, routing, NAT, firewalls | No route, unreachable service, one-way media |
| 4 Transport | UDP, TCP, TLS sessions, ports | Blocked port, retransmissions, handshake failure |
| 5 Session | SIP dialogs, registration, call state | Calls fail to establish or disconnect unexpectedly |
| 6 Presentation | Codec, encryption, encoding, SDP formats | Incompatible codec, TLS/media negotiation failure |
| 7 Application | PBX logic, dial plan, voicemail, provisioning | Wrong route, missing feature, bad credentials |
A practical call path
handset -> switch/Wi-Fi -> router/NAT -> firewall/SBC -> carrier/PBX
Check the path in that order, then split the investigation into two tracks:
- Signalling: registration, call setup, authentication, routing, and negotiation.
- Media: RTP reachability, codec agreement, packet loss, jitter, and delay.
Common traps
- A ping test proves little about UDP media.
- A registered phone can still have a broken inbound route.
- A successful SIP call can still have blocked RTP.
- QoS markings only help when every relevant hop preserves and acts on them.
- VPNs and tunnels can change MTU, routing, address visibility, and packet timing.