Actions25
- Call Actions
- Dial Actions
- Media Actions
- Queue Actions
- Global recording Actions
- AI Actions
- Respond Actions
Respond → Respond To Auth
AI-generatedSummary
Send a SIP response based on authentication settings
Inputs
- authAction (required) — Action to take on authentication; choose from Allow, Verify Digest Password, Not Applicable, Challenge, Deny
- password (required) — Digest password for verification when authAction is 'verify_password'
- extension — Extension identifier for extension‑based authentication; leave empty for trunk dynamic address or when username derives the extension
- statusCode (required) — SIP status code to return (e.g., 401 for challenge, 403 for deny)
- reason (required) — Reason phrase for the response when authAction is 'deny' or 'challenge'
- options — Additional options for the response; currently supports a 'Request ID' field
Output shape
no body — success/failure only
The node sends a SIP response and does not return data to the workflow; success is indicated by the response being sent
Examples
Example 1: Challenge an unauthenticated SIP client
authAction: 'challenge', statusCode: 401, reason: '', options: {requestId: '12345'}