Module 1: Foundations

The Application Layer — HTTP, WebSockets, and gRPC

Learn about the application layer — http, websockets, and grpc

Duration: 7 minutes
Level: Intermediate
Lesson: 20

Why Application Protocols Matter for NOC Engineers

You might think a voice-focused NOC only needs SIP and RTP knowledge. But modern telecom platforms like Telnyx are API-first. Customers create calls via REST APIs, receive events via webhooks, stream real-time data over WebSockets, and internal services communicate via gRPC. When any of these break, it's a NOC incident.

HTTP: The Foundation of APIs and Webhooks

HTTP/1.1: One Request, One Response

HTTP/1.1 is a text-based request-response protocol. A client sends a request:

POST /v2/calls HTTP/1.1
Host: api.telnyx.com
Authorization: Bearer KEY123...
Content-Type: application/json

{"connection_id": "abc", "to": "+15551234567", "from": "+15559876543"}

The server responds:

HTTP/1.1 200 OK
Content-Type: application/json

{"data": {"call_control_id": "xyz", "call_leg_id": "leg1", ...}}

HTTP/1.1's limitation: one request per TCP connection at a time. To send multiple concurrent requests, you need multiple TCP connections (typically 6 per domain in browsers). Each connection incurs TCP + TLS handshake overhead.

Connection: keep-alive helps by reusing the same TCP connection for sequential requests, avoiding repeated handshakes. But requests are still serialized — head-of-line blocking at the HTTP level.

HTTP/2: Multiplexed Streams

HTTP/2 solves the multiplexing problem with streams — multiple concurrent request-response exchanges over a single TCP connection. Each stream has an ID, and frames from different streams are interleaved.

Key improvements:

  • Multiplexing: Many requests in flight simultaneously on one connection
  • Header compression (HPACK): Repeated headers are compressed, reducing bandwidth
  • Binary framing: No more text parsing — faster and less error-prone
  • Server push: Server can proactively send resources (less relevant for APIs)

HTTP/2 is used between Telnyx API servers and clients. It significantly reduces latency for customers making multiple API calls rapidly (e.g., creating a conference with many participants).

HTTP/3: UDP-Based with QUIC

HTTP/3 replaces TCP with QUIC — a UDP-based transport that includes its own reliability, encryption (TLS 1.3 built in), and multiplexing. The key advantage: no TCP head-of-line blocking. Lost packets only affect the specific stream they belong to, not all streams on the connection.

🔒 Full Course Content Available

This is a preview of the Telephony Mastery Course. The complete lesson includes:

  • ✅ Detailed technical explanations
  • ✅ Advanced configuration examples
  • ✅ Hands-on lab exercises
  • ✅ Real-world troubleshooting scenarios
  • ✅ Practice quizzes and assessments

🚀 Unlock Full Course Access

Preview shows approximately 25% of the full lesson content.