Skip to content

docs(agents): ephemeral-realm SIP credential test call workflow - #21

Merged
michaela-band merged 2 commits into
feat/sip-provisioningfrom
feat/sip-call-agent-workflow
Aug 4, 2026
Merged

docs(agents): ephemeral-realm SIP credential test call workflow#21
michaela-band merged 2 commits into
feat/sip-provisioningfrom
feat/sip-call-agent-workflow

Conversation

@michaela-band

Copy link
Copy Markdown
Contributor

Summary

  • Adds a ### Test SIP credentials end-to-end workflow to AGENTS.md documenting how an agent can verify SIP auth by placing a real call through Bandwidth
  • Uses an ephemeral realm + fresh credential so nothing existing is disrupted; both are torn down after the call
  • Captures the generated password once from credential create --plain, writes it to a chmod 600 temp file, and immediately unsets it from the environment — the password never touches a log or command line
  • Includes a signal-to-meaning table for common SIP responses (407 → re-INVITE, 200 OK, 403, 503) so an agent can interpret what happened without guessing
  • Notes the band number list limitation on Bandwidth Build accounts and the DNS propagation delay on newly-created realms

Why no band sip call command

The implementation would require invoking baresip (or another SIP UA) as a subprocess and managing a temp config file from Go. That's external tool coupling, subprocess management, and platform-specific behavior that doesn't fit the CLI's model — it's a pure API client. The AGENTS.md workflow documents the same recipe in a way that works with any SIP UA and doesn't add a fragile dependency to the binary.

Test plan

  • Read through the workflow in AGENTS.md and verify the shell commands are correct E2E (realm create → credential create → jq extract → temp file → baresip dial → cleanup)
  • Confirm the band number list Build caveat matches the existing note in the Build Registration section
  • Confirm PR is against feat/sip-provisioning, not main

🤖 Generated with Claude Code

Adds a self-contained agent workflow for verifying SIP credentials end-to-end
without disrupting existing realms or credentials. Covers the full lifecycle:
create an ephemeral realm + credential, capture the generated password once,
write a 600-permission temp accounts file, dial via a local SIP UA, and tear
everything down. Includes a signal-to-meaning table for common SIP responses
and notes on Build account number limitations.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@michaela-band
michaela-band requested review from a team as code ownersAugust 4, 2026 18:13
@bwappsec

bwappsec commented Aug 4, 2026

Copy link
Copy Markdown

Snyk checks have passed. No issues have been found so far.

StatusScan Engine Critical High Medium LowTotal (0)
Open Source Security0000 0 issues
Licenses0000 0 issues
Code Security0000 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

Comment threadAGENTS.md Outdated
@michaela-band
michaela-band merged commit 9664d46 into feat/sip-provisioningAug 4, 2026
2 of 3 checks passed
@michaela-band
michaela-band deleted the feat/sip-call-agent-workflow branch August 4, 2026 18:20
Sign up for freeto 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.

2 participants

@michaela-band@bwappsec