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 retrieve call log information for a given user. The "Get Call Log" operation under the "Users" resource fetches detailed call records associated with a specified directory number (Dn) and request identifier. This is useful in scenarios where you want to analyze call history, monitor call activity, or generate reports based on call logs from the 3CX system.

Practical examples include:

  • Fetching call logs for a specific user extension to audit call activity.
  • Integrating call data into CRM systems for enhanced customer interaction tracking.
  • Automating call report generation for management review.

Properties

Name Meaning
Dn The directory number (extension) to query call logs for. Usage format: dn={dn}. This identifies the user whose call log is being retrieved.
Request Id A unique identifier for the request. Usage format: requestId={requestId}. This may be used for tracking or correlating requests within the 3CX system.

Output

The node outputs JSON data containing the call log details retrieved from the 3CX system for the specified user. The structure typically includes information such as call timestamps, call duration, caller and callee numbers, call direction (incoming/outgoing), and call status. If the node supports binary data output (e.g., recordings), it would be included accordingly, but this is not indicated in the provided code snippet.

Dependencies

  • Requires an API key credential for authenticating with the 3CX telephony system.
  • Needs the 3CX server URL configured in the credentials to form the base API endpoint.
  • The node uses the 3CX REST API v1 (/xapi/v1) to perform operations.
  • Proper OAuth2 authentication setup is necessary to authorize API requests.

Troubleshooting

  • Missing or invalid credentials: Ensure that the API key and server URL are correctly configured in the node's credentials.
  • Invalid Dn or Request Id: Verify that the directory number and request ID values are correct and exist in the 3CX system.
  • Network issues or incorrect server URL: Confirm that the 3CX server URL is reachable and correctly formatted without trailing slashes.
  • API rate limits or permission errors: Check if the API user has sufficient permissions and that rate limits are not exceeded.
  • Common error messages will relate to authentication failures, invalid parameters, or connectivity problems. Resolving these usually involves verifying credentials, input values, and network access.

Links and References

Discussion