3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node integrates with the 3CX telephony system, specifically allowing users to create a new SBC (Session Border Controller) resource. The "Create Sbc" operation enables adding an SBC configuration by providing details such as network information, credentials, and device identifiers. This is useful in scenarios where you want to automate the provisioning or management of SBCs within a 3CX environment, for example, when setting up new telephony infrastructure or scaling existing deployments.

Practical examples include:

  • Automatically registering new SBC devices during deployment.
  • Managing SBC configurations programmatically as part of a larger telephony automation workflow.
  • Integrating 3CX SBC creation into CI/CD pipelines for telephony infrastructure.

Properties

Name Meaning
Display Name The display name assigned to the SBC for identification purposes.
Group The group or category under which the SBC is organized.
Has Connection Boolean indicating whether the SBC currently has an active connection.
Local IPv4 The local IPv4 address of the SBC device.
Name The internal or technical name of the SBC.
Password The password used for authenticating the SBC.
Phone MAC The MAC address of the phone associated with the SBC.
Phone User Id Numeric identifier for the user of the phone connected to the SBC.
Provision Link URL or link used for provisioning the SBC device.
Public IP The public IP address of the SBC device.
Version The version string of the SBC firmware or software.

Output

The node outputs JSON data representing the response from the 3CX API after creating the SBC. This typically includes confirmation details about the newly created SBC, such as its ID, status, and any metadata returned by the API. There is no indication that binary data is output by this node.

Dependencies

  • Requires an API key credential for authenticating with the 3CX server.
  • The node expects a base URL for the 3CX API server, configured in the credentials.
  • The 3CX API must be accessible from the n8n instance running this node.

Troubleshooting

  • Common issues:
    • Authentication failures due to incorrect or missing API credentials.
    • Network connectivity problems preventing access to the 3CX API endpoint.
    • Validation errors if required properties are missing or incorrectly formatted.
  • Error messages:
    • Unauthorized or 401 errors indicate invalid API credentials; verify and update the API key.
    • 404 or endpoint not found errors suggest incorrect base URL configuration.
    • 400 Bad Request errors usually mean some input property values are invalid or missing; check all required fields.

Links and References

Discussion