Skip to content

Unify the StandIn calling-lane port on 9442 - #7

Merged
alaamh merged 1 commit into
mainfrom
chore/calling-port-9442
Aug 16, 2026
Merged

Unify the StandIn calling-lane port on 9442#7
alaamh merged 1 commit into
mainfrom
chore/calling-port-9442

Conversation

@alaamh

@alaamh alaamh commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Unifies the StandIn Microsoft Teams calling-lane (voice WebSocket) port on 9442 across the bridge.

What changed

  • src/config.ts: default PORT 8080 -> 9442 (docstring updated).
  • Dockerfile: EXPOSE 9442, HEALTHCHECK fallback ${PORT:-9442}.
  • .env.example: PORT=9442.
  • README.md, examples/basic-bridge/README.md: default port 9442; the Tailscale Funnel command now uses the path-mount form on the real route (tailscale funnel --bg --set-path /voice/msteams/stream http://127.0.0.1:9442/voice/msteams/stream) with a portless agent voice URL (wss:///voice/msteams/stream), since Funnel only serves 443/8443/10000.
  • website docs (getting-started, connecting-to-standin, configuration-reference): 9442 everywhere, same Funnel fix, cloudflared/ngrok/devtunnel examples point at 9442.
  • The WebSocket route path is unchanged (/voice/msteams/stream/{callId}); only the port number moved.

Version bump

  • 0.1.2 -> 0.1.3 (package.json and package-lock.json), because the code default changed.

Checks run locally

  • npm ci, npm run typecheck, npm test (45 pass), npm run build: PASS
  • website: npm ci && npm run build: PASS

Change the bridge's default PORT from 8080 to 9442 (code default, Dockerfile
EXPOSE and HEALTHCHECK, .env.example, README, examples, and the Starlight docs).
Replace the invalid Tailscale Funnel command (--https=8080) with the path-mount
form on the real route, /voice/msteams/stream, and make the documented agent
voice URL portless accordingly. Bump the package to 0.1.3.
@alaamh
alaamh merged commit 4855163 into main Aug 16, 2026
2 checks passed
@alaamh
alaamh deleted the chore/calling-port-9442 branch August 16, 2026 08:18
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