| Scroll export button | ||||||||
|---|---|---|---|---|---|---|---|---|
|
| Info |
|---|
This guide walks you through the steps required to install Autotraces, custom applications packaged into a Dialplan which simplify the process of log/data collection. Created: July 2021 Updated: October 2021 Permalink: https://wildix.atlassian.net/wiki/x/rhjOAQ |
Table of Contents
Purpose of Using Autotraces
...
- Log in as a user on the system (Collaboration, mobile app, provisioned phone, etc)
- Dial the pilot number that you built
- Follow the prompts to start the trace in whichever mode you choose. More information on trace types can be found in the More Information section.
Usage
After the initial setup, the trace will be running in whichever mode you started it in. At this point, you should consider who will be creating incident reports and what options you would like them to have when they dial the pilot number. If you do not want users calling this number to have the option to completely stop the trace from running or to change the trace type, you should edit the Set portion of the Jump to Dialplan application to be in_admin_user. See More Information section of this guide for more details.
...
- The admin has installed and started the Autotraces as described above
- The admin informs the end users of the choice of how to generate an incident report
- End user has some issue and calls the pilot number built
- User is asked to stay on the line to generate an incident report
- System asks the user to record a message indicating what the issue was
- The call to Autotraces ends with the calling party
- The system stops the traces, creates a backup file of logs, and restarts the trace
- System emails the administrator information about the report (including recording)
- The administrator goes to Backup system tab of WMS on the PBX that the incident report was made and downloads the backup file that has all of the logs in it. See Contents of Trace section below for more information.
...