Sending Request terminated status when Call is cancelled #409
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We observed that LiveKit SIP sometimes returned SIP status 486 Busy Here when a SIP caller canceled the call. This behavior was inconsistent with expected SIP cancellation handling.
Removed duplicate cancellation handling during ringing:
Cancellation logic was previously executed in multiple places — both during ringing and WaitMedia.
This caused incorrect status (like 486 Busy Here) to be returned when the call was simply canceled by the caller.
Updated closeWithCancelled() to consistently mark the call as CallCancelled.
Based on this status, the SIP response now correctly returns 487 Request Terminated, as per SIP spec for cancellations.
Updated attributes to reflect that as well