Actions76
- Applications Actions
- Asterisk Actions
- Bridges Actions
- Channels Actions
- Device States Actions
- Endpoints Actions
- Events Actions
- Mailboxes Actions
- Playbacks Actions
- Recordings Actions
- Sounds Actions
Recordings → Get Stored
AI-generatedOverview
This node interacts with the Asterisk PBX system via the Asterisk REST Interface (ARI) to manage various resources, including recordings. Specifically, the 'Get Stored' operation under the 'Recordings' resource retrieves stored recordings by their name. This is useful for scenarios where you need to access or manipulate existing call recordings within the Asterisk system, such as for playback, analysis, or archival purposes.
Use Case Examples
- Retrieve a specific stored recording by its name to play it back in a call flow.
- Fetch recording details for logging or auditing purposes.
- Use the recording name to manage or delete stored recordings programmatically.
Properties
| Name | Meaning |
|---|---|
| Recording Name | The name of the recording to retrieve. This is a required string input that specifies which stored recording to get. |
Output
JSON
recording- The details or data of the retrieved stored recording from Asterisk.
Dependencies
- Requires an Asterisk API key credential for authentication to the Asterisk REST Interface (ARI).
- Needs the base URL of the Asterisk ARI endpoint configured in the node credentials.
Troubleshooting
- Ensure the recording name provided matches exactly with the stored recording name in Asterisk; otherwise, the node may return an error or no data.
- Verify that the Asterisk API credentials and base URL are correctly configured to avoid authentication or connection errors.
- Common errors include 'Recording not found' if the recording name does not exist, or 'Unauthorized' if API credentials are invalid.
Links
- Asterisk REST Interface (ARI) Documentation - Official documentation for the Asterisk REST Interface, which this node uses to interact with Asterisk PBX.