agentsclimarketplace
Sign in

Voip sip calling workflow

Skill gaelic-ghost/socket/skills/voip-sip-calling-workflow

Build a native Apple VoIP calling app by separating CallKit or LiveCommunicationKit, PushKit, AVFAudio, SIP or WebRTC transport, and call-state ownership.From its SKILL.md

Install
npx -y skills add gaelic-ghost/socket --skill voip-sip-calling-workflow

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 6 stars6 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.4 KB, 446 tokens by cl100k_base, as published. Nobody here has run it

VoIP SIP Calling Workflow

Purpose

Build an Apple VoIP calling app without conflating system call presentation, audio-session activation, signaling, media transport, and account state.

Architecture

  • System integration: use CallKit or LiveCommunicationKit for call actions, system UI, and system coordination.
  • Wake-up: use PushKit VoIP notifications only for a real incoming call that is promptly reported through the supported calling framework.
  • Audio: use AVFAudio/AVAudioSession for activation, route changes, interruptions, Bluetooth, and media permissions.
  • Signaling and media: choose SIP, WebRTC, or another documented transport based on interoperability, NAT traversal, codec, security, and backend needs. SIP is a protocol lane, not an Apple calling UI API.
  • App state: own account identity, call state, reconnection, recording, retention, emergency-call policy, and end-to-end encryption explicitly.

Workflow

  1. Define incoming, outgoing, answer, decline, end, hold, mute, transfer, and failure state transitions before integrating UI.
  2. Report incoming calls to the system promptly, then start media only after the calling framework and audio system permit it.
  3. Design a transport adapter behind explicit call-state inputs and outputs; never let SIP registration or WebRTC callbacks become the global UI owner.
  4. Decide the fallback behavior separately for VoIP failure and cellular calling.
  5. Route default-calling or default-dialer eligibility to default-communication-app-workflow.

Validation

Test physical-device incoming/outgoing calls, background arrival, lock screen, audio route and interruption changes, reconnect, duplicate pushes, signaling failure, media failure, and user-visible fallback.

References

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 326,736. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.