FEATUREDLatestOpenSIPSTOP STORIESVOIPWebRTC

SIP Dialog vs Transaction: The Critical Difference

Few things confuse people working with SIP more than the difference between a transaction and a dialog. Getting it straight makes call flows far easier to read and SIP problems far easier to debug. Both terms are defined in RFC 3261, the core SIP standard.

A transaction: one request and its responses

A SIP transaction is a single request plus every response to it. There are two kinds: INVITE transactions and non-INVITE transactions (REGISTER, BYE, OPTIONS and so on). Each transaction is identified by the branch parameter in the top Via header, which starts with z9hG4bK, together with the request method.

In a normal call:

  • INVITE → 100 Trying → 180 Ringing → 200 OK is one INVITE transaction.
  • The ACK that follows a 200 OK is not part of that transaction; it is sent separately, end to end. (If the call is rejected, the ACK for the error response does belong to the INVITE transaction.)
  • BYE → 200 OK, when the call ends, is another transaction.

Transactions are short-lived and handled by the transaction layer, which deals with retransmissions and timers.

A dialog: the relationship that lasts

A dialog is a peer-to-peer relationship between two SIP user agents that lasts for some time and contains many transactions. It is identified by three values: the Call-ID, the local tag and the remote tag (the tags in the From and To headers). The CSeq number orders requests within a dialog, but it is not part of the dialog’s identity.

  • For a call, a dialog is created by the 2xx response to the INVITE. A provisional response that carries a To tag, such as 180 Ringing, creates an early dialog first.
  • When a call is forked to several phones, one INVITE can produce several early dialogs.
  • The dialog ends when the call ends with BYE.
  • Calls are not the only dialogs: SUBSCRIBE and NOTIFY also create them (RFC 6665).

Everything that happens mid-call runs inside the dialog: a re-INVITE to put a call on hold or change codecs, or a REFER to transfer a call.

Where sessions fit in

A session is the media itself: the audio or video streams described by SDP in the offer and answer. The dialog is the signalling relationship that sets up and changes that session. Siperb’s knowledge base covers transactions, dialogs and sessions side by side.

Why it matters in practice

  • Debugging: a mid-call request with the wrong Call-ID or tags does not match any dialog, and the other side answers 481 Call/Transaction Does Not Exist. That one code explains many failed holds and transfers.
  • Proxies: SIP proxies can be stateless, transaction-stateful or dialog-stateful, which decides how much they can see and do.
  • Reading traces: tools such as sngrep group messages into dialogs, so you can follow a whole call at a glance.

Related reading

Updated 11 November 2026: corrected the call-flow example and the definition of a dialog, and added early dialogs, sessions and the 481 response.

Leave a Reply

Your email address will not be published. Required fields are marked *