Home / Registration, DNS, and routing / Path and Service-Route
Path and Service-Route
Path is the inbound vector stored with a binding, and Service-Route is the outbound vector the registrar gives the UA.
Learn in 5 minutes
- Insert Path on REGISTER the way a proxy inserts Record-Route
- Use Service-Route as a preloaded Route for a new request
- Keep the two vectors from being swapped
Visual
Both headers look like Route URIs. They are learned at registration and they point in opposite directions.
Worked example
Which header is outbound? The 200 OK has both Path and Service-Route. Pick the one the UA will preload.
- Dissect the 200.
- Read Path.
- Read Service-Route.
Fault
The binding exists, and the INVITE for the UA is sent straight to 203.0.113.10. The edge that inserted Path never sees it, and the NAT binding is dead.
The Contact address was reachable only through the edge that registered it.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
CRM Screen pop uses data the contact center already has: ANI, DNIS, case id. Those values may arrive in SIP headers or in a CTI event after the call is up. The CRM is not a SIP element.
Sources and go deeper
- RFC 3327 — last checked 2026-10
- RFC 3261 §10 — last checked 2026-10
- RFC 3608 — last checked 2026-10