Retrieve exported user activities file |
|
| IT&Operations > Job Policies > Automatic user activities export |
This scenario illustrates how to retrieve an export file of a scheduled job.
Go to the configured FTP folder and check content of the UserActivities folder.
Generated files are tab separated CSVs, each row represents an entry except the first one which contains fields name.
Part of one of these files as an example
The Call Log Entry file contains: •Date when the TSS received the event •UId : Unique Identifier of the entry •Version of the event •Login of the user •Profile's name if the call log belongs to a shared profile •Extension PK: Phone extension of the remote party •Line: Target line's extension •Call Log Type: either Placed, Received or Missed •Type: Radio|VoIp •Redirection Number if call had been redirected •SipCallId of the call •Duration of the call •Threated : True if the user redialed the missed call
Notes Only users who have call log events reporting enabled have "complete" call log entries (with call-id and duration), other users will only have the version "000000000". If N turrets subscribe to the same line's notifications, every incoming call will appear N times. N missed if call is actually missed; N-1 missed and 1 received if call is picked up. To enable call log events reporting, see Reporting configuration
The call log event file contains: •Date when the TSS received the event •UId : Unique Identifier of the event •Version of the event •Relative entry: UId of the call log entry relative to the event's call •Login of the user •Event Type: either Established, Hold, Resume, Handfree or Loudspeaker
Note: Only user who have call log events reporting enabled have call log events. To enable call log events reporting, see Reporting configuration
The line coverage file contains: •Date when the TSS received the event •UId : Unique Identifier of the event •Version of the event •Local Extension of the covered/uncovered line •Login of the user •Event Type: either Covering or Not Covering
Note: Only user who have line coverage reporting enabled have line coverage events To enable line coverage reporting, see Reporting configuration
Tip: some spreadsheet software understand this format if you append "sep=\t" at the beginning of the file. |