3CX icon

3CX

Interact with 3CX telephony system

Actions462

Overview

This node integrates with the 3CX telephony system to update dial code settings. It allows users to modify various dial code configurations such as billing codes, caller ID visibility, hotdesking, intercom, queue statuses, voicemail, and more. This is useful in scenarios where an organization needs to programmatically adjust telephony dial codes to reflect changes in call routing, user status, or feature access without manual intervention in the 3CX management console.

Practical examples include:

  • Automatically updating dial codes for different call queues based on business hours.
  • Changing the dial code for hiding caller ID when privacy policies change.
  • Adjusting hotdesking dial codes dynamically for flexible office environments.

Properties

Name Meaning
Dial Code Billing Code The dial code used for billing purposes.
Dial Code Hide Caller ID The dial code to hide the caller's ID during calls.
Dial Code Hotdesking The dial code enabling hotdesking functionality.
Dial Code Hotel Access The dial code granting hotel access features.
Dial Code Intercom The dial code used for intercom calls.
Dial Code Logged In Queue The dial code representing the logged-in queue status.
Dial Code Logged Out Queue The dial code representing the logged-out queue status.
Dial Code Out Office The dial code indicating out-of-office status.
Dial Code Park The dial code used to park a call.
Dial Code Pickup The dial code used to pick up a parked call.
Dial Code Profile Status The dial code reflecting the user's profile status.
Dial Code Unpark The dial code used to unpark a call.
Dial Code V Mail The dial code for accessing voicemail.

Each property expects a string value representing the dial code to be set for that particular function.

Output

The node outputs JSON data containing the response from the 3CX API after attempting to update the dial code settings. The structure typically includes confirmation of updated fields or error messages if the update failed.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the 3CX telephony system.
  • The node uses the base URL configured in the credentials to send requests to the 3CX API endpoint /xapi/v1.
  • Proper network access to the 3CX server is necessary.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Invalid dial code values may result in API errors or rejected updates.
    • Network connectivity issues to the 3CX server can prevent successful requests.
  • Error Messages:

    • Authentication errors typically indicate invalid or expired API tokens; reconfigure credentials.
    • Validation errors from the API suggest incorrect dial code formats; verify input values.
    • Timeout or connection errors imply network problems; check server availability and firewall settings.

Links and References

Discussion