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

SIP UniverseFree University

Home / NAT, ICE, and the ALG problem / Media latching on an SBC

Media latching on an SBC

Many SBCs learn the remote RTP address from the first packet instead of trusting c=. That is deployment practice, and RFC 5853 is the requirements RFC.

Learn in 5 minutes

  1. Describe latching as learning RTP from the first packet
  2. Cite RFC 5853 as requirements, not as an algorithm
  3. Refuse to move the latch toward an unexpected source

Visual

First packet, not c= · study drawing · cyphermonkeylabs.com PhoneSBCCarrier INVITE INVITE 200 RTP

SVG HTML PNG

Latching is something many SBCs do. RFC 5853 collects requirements. It is not an IETF algorithm.

Worked example

Compare c= with the packet source Extract the INVITE and read c=. Then read the RTP note. The source port's address is not the c= address.

  1. Press Extract SIP and read c=.
  2. Read the RTP source in the text.
  3. State where a latching SBC sends return media.

Fault

c= says 203.0.113.10. The first RTP source is 198.51.100.30, which is not the phone side the SBC authenticated. Return media moves there.

Many SBCs learn the remote RTP address from the first packet instead of trusting c=. That is deployment practice. RFC 5853 is the requirements RFC, not an IETF algorithm.

Quiz

Media latching means


RFC 5853 is


If c= says 203.0.113.10 and the first RTP comes from 203.0.113.20, a latching SBC


An unexpected first-packet source should


When both ends implement candidate checks, the specified mechanism is


You document latching as


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.

Programmable communications APIs Twilio’s docs home is API reference, tutorials, and integration for Twilio products. Elastic SIP Trunking is the SIP-shaped product already cited in this lab. This page does not define the word CPaaS from an RFC. Read the vendor page before you copy a diagram that uses that word.

Glossary · Ecosystem map · Ports · Troubleshooting

Sources and go deeper