Actions4
Overview
This node interacts with the Voipmon API to retrieve VoIP call data based on specified criteria. Specifically, the 'Get Voip Calls' operation fetches call records filtered by parameters such as start and end times, caller and called numbers, connection status, and audit reasons. This node is useful for monitoring, auditing, and analyzing VoIP call activities within a given time frame or for specific callers.
Use Case Examples
- Retrieve all VoIP calls that started between two dates for a specific caller number.
- Fetch only connected calls for a given caller within a specified time range.
- Get call records filtered by caller, called number, and audit reason for compliance auditing.
Properties
| Name | Meaning |
|---|---|
| Start Time | Filters calls that started on or after this date and time. |
| End Time | Filters calls that started on or after this date and time (note: description seems duplicated, likely meant to filter calls ending by this time). |
| Start Time To | Optional filter to include calls that started on or before this date and time. |
| Call End | Optional filter to include calls that ended on or before this date and time. |
| Caller | The caller's phone number to filter the calls. |
| Called | Optional filter for the called phone number. |
| Audit Reason | Optional string to specify an audit reason for filtering calls. |
| Only Connected | Filter to include only connected calls or all calls. |
Output
JSON
cdr- Call detail records for the retrieved VoIP calls.
Dependencies
- Voipmon API
Troubleshooting
- Ensure that the required credentials (API URL, user, and password) are correctly configured to avoid authentication errors.
- Verify that the date-time parameters are correctly formatted and logically consistent (e.g., startTime <= endTime).
- If no calls are returned, check the filter parameters to ensure they match existing call records.
- Common error messages include connection timeouts, invalid URL, or authentication failures, which can be resolved by checking network connectivity, API endpoint correctness, and credential validity.