Oki-Toki icon

Oki-Toki

Interact with Oki-Toki API (Calls, Contacts, Dialers, Lists, Reports, Users)
Join our community

Actions30

Overview

This node interacts with the Oki-Toki API to retrieve a routing calls log report. It fetches SIP communication history within a specified date range and supports additional filtering options such as limiting the number of results and pagination offset. This node is useful for analyzing call routing data, monitoring call flows, and auditing SIP communications in telephony systems.

Use Case Examples

  1. A telecom operator wants to generate a report of all SIP calls routed through their system between two dates to analyze call patterns and troubleshoot issues.
  2. A call center manager needs to extract routing call logs for a specific period to evaluate the performance and identify any routing problems.

Properties

Name Meaning
Date From Start date for the report, specifying the beginning of the date range for the routing calls log.
Date To End date for the report, specifying the end of the date range for the routing calls log.
Additional Fields Optional parameters to refine the report, including limit on the number of results, offset for pagination, and filters by queue ID, project ID, or user ID (depending on operation).

Output

JSON

  • json - The JSON response from the Oki-Toki API containing the routing calls log data, including details of SIP communication history within the specified date range and applied filters.

Dependencies

  • Oki-Toki API with an API key credential for authentication

Troubleshooting

  • Ensure the API credentials are correctly configured and valid to avoid authentication errors.
  • Verify that the date range parameters are correctly formatted as ISO date strings (YYYY-MM-DD).
  • If the API returns an error about unknown report operation, check that the operation parameter is set to 'routingCallsLog'.
  • Pagination parameters (limit and offset) should be within valid ranges to avoid empty or incomplete results.

Links

Discussion