A student's open lab: learning and sharing, free for everyone.

SIP UniverseFree University

Home / NAT, ICE, and the ALG problem / Embedded addresses and NAT

Embedded addresses and NAT

SIP and SDP embed IP addresses. NAT rewrites the packet header and leaves those embedded addresses behind.

Learn in 5 minutes

  1. Find addresses in Via, Contact, and SDP c=
  2. Explain why a packet-header NAT does not fix those fields
  3. Treat a private connection address as non-routable from the public peer

Visual

Offer with a documentation address · study drawing · cyphermonkeylabs.com AliceNATCarrier INVITE INVITE 180 200

SVG HTML PNG

NAT sees the outer header. SIP and SDP also name addresses in the payload.

Worked example

Read a routable c= line Dissect the offer. c= uses the documentation address 203.0.113.10. The fault beside this lab is the private-address case.

  1. Press Dissect.
  2. Find c=.
  3. Compare it with Contact.

Fault

The carrier never sends RTP. The SDP connection line uses a private address, and that address is non-routable.

The address in c= is private and non-routable from 192.0.2.40. NAT rewrote the packet header, not the SDP body.

Quiz

NAT breaks SIP and SDP because


c= tells the peer


A 200 OK behind a broken c= line means


Contact is used for


Documentation address 203.0.113.10 is


A private address in c= is


Ecosystem

Glossary, sister systems, and the integration seam for this room.

Workforce management WFM forecasts volume and builds schedules. It consumes contact-center events. It does not parse Via headers. When a forecast is wrong, the SIP symptom is usually queue delay and 480 or carrier congestion, not a broken dialog ID.

Glossary · Ecosystem map · Ports · Troubleshooting

Sources and go deeper