3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node interacts with the 3CX telephony system, specifically allowing users to delete an SBC (Session Border Controller) entity identified by its unique name. It is useful in scenarios where administrators need to programmatically remove SBC configurations from their 3CX system, such as during cleanup operations or automated management of telephony infrastructure.

Properties

Name Meaning
Name The unique key (Name) of the SBC entity to delete. Supports expressions like {{$json.Name}}.
If Match Optional ETag header value for concurrency control. Used to ensure the SBC has not changed since last retrieval.

Output

The node outputs JSON data representing the result of the delete operation. Typically, this will be a confirmation of successful deletion or an error message if the deletion failed. There is no indication that binary data is output.

Dependencies

  • Requires an API authentication token credential to connect securely to the 3CX server.
  • Needs the base URL of the 3CX server configured in credentials.
  • The node sends HTTP requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Common issues:

    • Deletion fails if the specified SBC name does not exist.
    • If the "If Match" ETag header is provided but does not match the current resource version, the request may be rejected to prevent accidental overwrites.
    • Network or authentication errors if the API token or server URL is misconfigured.

  • Error messages:

    • 404 Not Found: The SBC with the given name was not found.
    • 412 Precondition Failed: The ETag provided in "If Match" does not match the current resource state.
    • 401 Unauthorized: Authentication failed due to invalid or missing API credentials.

To resolve these, verify the SBC name, optionally update or omit the ETag header, and confirm correct API credentials and server URL.

Links and References

Discussion