feat: blind call transfer via REFER (RFC 3515)#45
Merged
Conversation
Call::blind_transfer sends an in-dialog REFER with Refer-To; the transfer-progress NOTIFYs (message/sipfrag) arrive on the call's inbound_requests stream and are parsed with parse_sipfrag_status / is_final_sipfrag. Inbound REFER/NOTIFY now route to the owning Call instead of being auto-answered, so a consumer can reject a peer-initiated transfer or follow the sipfrag. Attended transfer (Replaces, RFC 3891) is not included. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GKGMQeftv6ztjoq1zXCL7g
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
What
Blind call transfer (RFC 3515) — the SIP signaling half of WaveKat Voice's call-transfer feature.
Call::blind_transfer(target)sends an in-dialogREFERwithRefer-Toand returns once the peer accepts (202).NOTIFYs (amessage/sipfragstatus line) are surfaced on the existingCall::inbound_requestsstream;parse_sipfrag_status/is_final_sipfragread the result so a consumer can drop its leg once the target answers.REFER/NOTIFYto the owningCall(instead of auto-200-ing them), so a consumer can also reject a peer-initiated transfer.Attended transfer (
Replaces, RFC 3891) is intentionally out of scope.Tests
refer.rsunit tests (Refer-To header, sipfrag parsing, finality threshold).stack::uarefer_sends_in_dialog_and_returns_202— asserts the in-dialog REFER carries the target and is a non-INVITE transaction.RFC-COVERAGE.md+ CHANGELOG updated.Consumed by wavekat-voice's blind-transfer PR, which patches to this branch until this releases.
🤖 Generated with Claude Code
https://claude.ai/code/session_01GKGMQeftv6ztjoq1zXCL7g