3CX icon

3CX

Interact with 3CX telephony system
Join our community

Actions462

Overview

This node is designed to update the Anti Hacking Settings of a 3CX telephony system via its API. It allows users to configure various security parameters that help protect the system from hacking attempts by setting thresholds and durations for different types of suspicious activities. This node is beneficial in scenarios where administrators want to programmatically adjust security settings to respond to evolving threats or automate security policy enforcement.

Practical examples include:

  • Increasing the blacklist duration after detecting repeated unauthorized access attempts.
  • Adjusting the number of allowed authentication requests before triggering a security barrier.
  • Enabling or disabling the overall security defense program based on operational needs.

Properties

Name Meaning
Hack Auth Requests Number of authentication requests considered suspicious before action is taken.
Hack Barrier Amber Threshold value for the amber-level security barrier indicating moderate threat level.
Hack Barrier Green Threshold value for the green-level security barrier indicating low threat level.
Hack Barrier Red Threshold value for the red-level security barrier indicating high threat level.
Hack Blacklist Duration Duration (likely in seconds or minutes) for which an IP or user is blacklisted.
Hack Challenge Requests Number of challenge requests before further security measures are triggered.
Max Request Per Period Maximum number of requests allowed within a defined period to prevent flooding.
Security Defense Program Boolean flag to enable or disable the entire security defense mechanism.
Throttle Period Length Length of the time period over which request counts are measured for throttling.

Output

The node outputs JSON data representing the updated Anti Hacking Settings as returned by the 3CX API. The structure typically reflects the current configuration of all the above properties after the update operation. There is no indication that binary data is output by this node.

Dependencies

  • Requires connection to a 3CX telephony system API endpoint.
  • Needs an API authentication token or OAuth2 credential configured in n8n to authorize requests.
  • The base URL for the 3CX API must be provided in credentials, ensuring correct routing of API calls.

Troubleshooting

  • Common Issues:

    • Incorrect or missing API credentials will cause authentication failures.
    • Providing invalid numeric values (e.g., negative numbers) for thresholds may result in API errors.
    • Network connectivity issues to the 3CX server can prevent updates.

  • Error Messages:

    • Authentication errors typically indicate invalid or expired credentials; reconfigure the API key or OAuth token.
    • Validation errors from the API may occur if property values are out of acceptable ranges; verify input values.
    • Timeout or connection errors suggest network problems; check server availability and firewall settings.

Links and References

Note: The summary is based solely on static analysis of the provided source code and property definitions without runtime execution or dynamic import resolution.

Discussion