> 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 can 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 principal 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` 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 what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.