> For the complete documentation index, see [llms.txt](https://cc.docs.landis.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cc.docs.landis.cloud/reports/recordings.md). # Recordings Navigate to Analytics & Reports | Recordings Displays a list of calls that were recorded. Recordings call be played from this report. For report options (e.g., filtering), See [Report Options](/appendix/report-options.md) | Column | Description | | ------------------------ | ----------------------------------------------------------------------------- | | "..." | Button that displays actions that can be performed on that record. | | Direction | Direction of call (Inbound/Outbound). | | Start | Start date/time of call. | | End | End date/time of call. | | When | Start time of call in relation to the current date/time. | | Caller Name | Name of caller. | | Caller Number | Number of caller. | | Callee Name | Name of user that received the call. | | Callee Number | Number of user that received the call. | | Length | Length of call/recording | | OU | Displays the organization unit where the interaction detail record is stored. | | Recording Mode | Call setting policy recording mode that was configured for the OU object. | | Recorded User | User principle name of recorded user. | | Recording File Reference | Recording folder and file name in Azure blob storage. | | Recording | Recording playback | | Scenario Id | Unique Id of interaction | | Score Status | Quality management score status. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cc.docs.landis.cloud/reports/recordings.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.