Skip to content

Feature/inbound accept decline#15

Open
smoghe-bw wants to merge 4 commits into
mainfrom
feature/inbound-accept-decline
Open

Feature/inbound accept decline#15
smoghe-bw wants to merge 4 commits into
mainfrom
feature/inbound-accept-decline

Conversation

@smoghe-bw

Copy link
Copy Markdown
Contributor

No description provided.

smoghe-bw and others added 4 commits July 15, 2026 15:09
Reworks the inbound-call flow onto the new gateway/SDK paradigm: the gateway
rides its accept decision and caller identity on the subscribe sdpOffer that
adds a call's track, and the SDK surfaces it as RtcStream.autoAccepted /
from / fromType on onStreamAvailable. There is no separate streamAvailable RPC
to correlate, so the two-phase ref juggling from the old branch is gone.

- App: onStreamAvailable connects straight through when s.autoAccepted, else
  stashes the stream and prompts. Accept is purely client-side (play the stream
  the gateway already bridged); decline ends the call via hangupConnection.
  onStreamUnavailable clears all inbound state.
- EndpointHandler: auto-accept toggle (a connect-time setMediaPreferences option),
  disabled once the endpoint exists; passes autoAccept into connect().
- IncomingCall: small presentational component + scss showing caller identity
  and Accept/Decline actions.
- package.json: bump bandwidth-rtc to ^0.6.0 for the reworked SDK.

There are no acceptStream/declineStream RPCs: accept needs no gateway signal and
decline reuses the existing hangup path, so no gateway change is required.

NOTE: bandwidth-rtc 0.6.0 is not yet published (this rides SDK PR #5). Test
locally via `npm link bandwidth-rtc`; regenerate package-lock.json once the SDK
release is cut.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant