Actions27
- Call Actions
- Contact Actions
- Dialer Actions
- List Actions
- Report Actions
- User Actions
Overview
This node interacts with the Oki-Toki API to retrieve various reports, including the Routing Calls Log report. Specifically, the Routing Calls Log operation fetches SIP communication history within a specified date range, optionally filtered by queue ID, project ID, or user ID. This is useful for analyzing call routing performance and communication patterns in telephony systems.
Use Case Examples
- A call center manager wants to analyze SIP call routing logs between two dates to identify routing issues or call patterns.
- A telecom analyst needs to generate a report on SIP communication history filtered by specific project or user IDs for auditing purposes.
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 filters and pagination controls for the report, including limit, offset, queue ID, project ID, and user ID to refine the data retrieved. |
Output
JSON
json- The JSON response from the Oki-Toki API containing the routing calls log data based on the specified filters and date range.
Dependencies
- Requires an API key credential for Oki-Toki API authentication.
Troubleshooting
- Ensure the API credentials are correctly configured and valid to avoid authentication errors.
- Verify that the dateFrom and dateTo parameters are provided and formatted correctly as the API requires dates in YYYY-MM-DD format.
- If the report returns no data, check that the date range and filters (queue ID, project ID, user ID) are set correctly and correspond to existing data in the system.
- Handle API rate limits or network issues by implementing retry logic or checking connectivity.