Home / Call flows that operators actually trace / CANCEL, BYE, and re-INVITE
CANCEL, BYE, and re-INVITE
CANCEL abandons an unanswered INVITE, BYE ends a confirmed dialog, and re-INVITE changes a dialog that already exists.
Learn in 5 minutes
- Pair 200 OK for CANCEL with 487 for the INVITE
- Use BYE only on a confirmed dialog
- Treat a mid-dialog INVITE as a re-INVITE and a possible target refresh
Visual
The dialog state decides the method. The branch decides whether CANCEL matches.
Worked example
Dissect a BYE This BYE assumes the dialog already exists. Find the CSeq and the To tag.
- Dissect the BYE.
- Confirm both tags are present.
- Read the CSeq number.
Fault
The 200 OK and the CANCEL crossed. The caller sends no BYE. The callee stays off hook and RTP continues.
A late CANCEL does not unwind a 200 OK. The UAS may answer 200 to the CANCEL and leave the dialog up.
Quiz
Ecosystem
Glossary, sister systems, and the integration seam for this room.
AI omni-channel agents A voice bot still needs a session. SIP creates, modifies, and ends sessions. Omni-channel, in the contact-center sense, means the same contact can also live on chat or another digital channel. Those channels do not replace the voice session. On Amazon Connect the platform owns the managed PSTN voice channel. Bridging an outside carrier into Connect with a Chime Voice Connector is not a supported pattern unless AWS reviews it. When an SBC forks the voice leg to a recorder, that fork is SIPREC, a different plane from the customer dialog.
AI agents A voice bot still needs a session. On Amazon Connect the platform owns the managed PSTN voice channel. Bridging an outside carrier into Connect with a Chime Voice Connector is not a supported pattern unless AWS reviews it. The FreeSWITCH manual page also describes SignalWire, founded by the FreeSWITCH team, as a hosted platform with AI agents behind REST APIs and SWML.
Sources and go deeper
- RFC 3261 — last checked 2026-10
- RFC 3261 §21 — last checked 2026-10
- RFC 3261 §8.1.1.7 — last checked 2026-10
- RFC 6141 — last checked 2026-10
- RFC 3261 §12 — last checked 2026-10
- RFC 3261 §13 — last checked 2026-10