3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

The node updates conference settings in a 3CX telephony system. It allows users to modify various parameters related to conference calls, such as enabling automatic calling of participants, setting PIN protection, configuring music on hold, and specifying external numbers or logos. This node is useful for administrators who want to programmatically manage conference call configurations within their telephony environment.

Practical examples include:

  • Automatically calling all participants when a conference starts.
  • Enabling or disabling PIN protection for secure access.
  • Setting a custom music track to play while participants wait.
  • Updating the conference logo or extension number dynamically.

Properties

Name Meaning
Auto Call Participants Boolean flag to enable or disable automatic calling of participants when the conference starts.
Enable Local MCU Boolean flag to enable or disable the local Multipoint Control Unit (MCU) functionality.
Enable Pin Boolean flag to enable or disable PIN protection for joining the conference.
Extension String representing the extension number associated with the conference.
External Numbers String containing external phone numbers allowed or related to the conference.
Id Numeric identifier of the conference settings record to update.
Logo Path String path or URL to the logo image used in the conference interface.
Music On Hold String specifying the music on hold track to play during the conference waiting period.
Pin Number String representing the PIN code required if PIN protection is enabled.
Zone String indicating the time zone or regional setting for the conference.

Output

The node outputs JSON data reflecting the result of the update operation on the conference settings. This typically includes confirmation of the updated fields or the full updated conference settings object returned by the 3CX API.

No binary data output is indicated.

Dependencies

  • Requires an active connection to a 3CX telephony system via its API.
  • Needs an API authentication token or OAuth2 credential configured in n8n to authorize requests.
  • The base URL for the 3CX server must be provided in credentials.
  • The node sends HTTP requests to the 3CX API endpoint /xapi/v1.

Troubleshooting

  • Common issues:

    • Invalid or missing API credentials will cause authentication failures.
    • Incorrect Id value may lead to "not found" errors when updating conference settings.
    • Providing invalid values for boolean flags or strings might cause validation errors from the API.
    • Network connectivity problems can prevent communication with the 3CX server.

  • Error messages and resolutions:

    • 401 Unauthorized: Check that the API key or OAuth2 token is correctly configured and has not expired.
    • 404 Not Found: Verify that the Id corresponds to an existing conference settings record.
    • 400 Bad Request: Ensure all required properties are valid and conform to expected formats.
    • Network Error: Confirm the 3CX server URL is reachable and correct.

Links and References

Discussion