Home / SIP core: messages, transactions, dialogs / Dialog identity
Dialog identity
A dialog is identified by Call-ID, the From tag, and the To tag, and the initial request has no To tag.
Learn in 5 minutes
- Name the three dialog-id components
- Tell an early dialog from a confirmed dialog
- Increment CSeq for a new request inside the dialog
Visual
No dialog exists until a response carries a To tag. BYE moves a confirmed dialog to terminated.
Worked example
Find the dialog id Dissect the 180. List the three values that identify the early dialog.
- Dissect the 180.
- Read Call-ID, From tag, and To tag.
- Note that 100 would not have been enough.
Fault
The UAC treats a second 180 with a different To tag as a retransmission of the first.
Same Call-ID and From tag with a different To tag is a different dialog. Forking does this on purpose.
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 3261 §12 — last checked 2026-10
- RFC 3261 §13 — last checked 2026-10
- RFC 3261 §8 — last checked 2026-10
- RFC 3261 §16 — last checked 2026-10