WildixInstall

Summary

Hang up an active call on the Wildix PBX on behalf of a given user extension, identified by its SIP Call ID. An optional reason can be supplied.

Inputs

• authentication — Credential type used for the request: Bearer Token (default) or OAuth2.
• user (required) — Extension number of the user performing the action (e.g. 1001).
• sipCallId (required) — SIP Call ID of the call to hang up, taken from event data or from the List Active calls operation.
• hangupAdditionalFields — Optional collection. Currently only 'Reason', a free-text string describing why the call is being hung up.

Output shape

Not verifiable from the provided source; the pack only shows signatures, not the execute body. Likely the API response for the hang-up request returned as n8n item(s).

The source pack contains no execute implementation details (endpoint, response shape), so the exact returned fields are undocumented here. Errors from the Wildix API would surface as node errors.

Examples

Example 1: Terminate a call for extension 1001 after an incoming-call event trigger.

Resource: Call, Operation: Hang Up, User: 1001, SIP Call ID: {{ $json.sipCallId }}

Example 2: End a call and record why.

User: 1002, SIP Call ID from a List Active step, Additional Fields > Reason: 'Call flagged as spam'

Links

• n8n community nodes installation guide