Comment on page
Select Logs at the top-center of the page. The Logs page will be displayed with a table of logs and the menu shown in Figure 1 below.
Figure 1: Logs navigation menu.
This menu is used to navigate the logs table below it. The following options are displayed:
1. Filter: Filters the log table to selected call types within the selected date range. Select the dropdown list to choose from the following options:
- All Logs. Default option. Displays logs for all call types.
- Inbound. Displays logs for only inbound calls.
- Outbound. Displays logs for only outbound calls.
- Transfer. Displays logs for only transfers.
2. Search: Allows you to search the logs for a specific phone number or application name. The log table will dynamically populate with results as users enter search criteria.
3. Date Range: Users can refine the time period for call log search results using the date picker. This feature allows users to select a pre-determined time interval, Last Week, This Week, Last Month, This Month, Last Quarter, This Quarter, or to set a custom date range.
4. Refresh: To refresh the log table with the most recent data, select the Refresh button (
5. Export: Select the Export button
to export the returned logs in CSV format.
Plum Fuse provides users with two different types of logs: session logs and call logs.
Session logs provide basic information about calls (e.g. the source/destination phone numbers, and call duration).
Session log data remains in Plum Fuse for one (1) year, on a rolling basis.
Call logs, or detailed call logs provide detailed information about the interactions that took place during a specific session.
Note: Detailed call logs are available for five (5) days. After that time, Fuse deletes the detailed call log.
Figure 2: The Session Logs Table.
Once an application begins to accept or make phone calls the call log table generates a list of call session logs. The table displays the following information about call sessions:
- 1.Application Name:* The name of the application logged for this call. Select this field header to sort by application name.
- 2.Destination: The number the application called, or the number end-users dialed to reach the application. Select this field header to sort by destination number.
- 3.Source/ANI:* Phone number/ANI where the phone call originated.
- 4.Start Time: Date and time when the phone call commenced. Select this field header to sort by call start time.
- 5.Duration: How long, in seconds and minutes, the phone call lasted.
- 6.Call Type: An icon indicates one of the following types of calls:
- () Inbound
- () Outbound
- () Transfer
- Clicking on the session log in the log table takes users to a new page that displays the detailed call log information. Users have the option to download the detailed call log data on this screen as well.
- 8.Download Log (): Select the icon to download a JSON file of the selected call log.
* The Application Name and Source/ANI fields were added in the Fuse 7.5 release and are not retroactive. Any logs generated prior to Fuse 7.5 will not include these fields.
"N/A" session logs
These logs indicate a call to a number that was not assigned to any application on the date and time recorded. No detailed calls logs are created for these calls.
To view a detailed record of interactions during a call, go to the Session Logs table and select the View Log icon (
) on a table entry. The Call Log page will be displayed, as shown in Figure 3.
Figure 3: Detailed call logs example.
A line-by-line call log will be displayed for the selected call. Each line corresponds to an interaction within the call.
On this page, the following items are of note:
- 1.The application name for the call.
- 2.An icon indicating the call type (inbound, outbound, transfer).
- 3.The ANI associated with the call.
- 4.The DNIS associated with the call.
- 5.The date and start time of the call.
- 6.A search box. Enter search terms to filter the call log to lines with matching terms. See the following section "The search box" for more info.
- 7.Select Downloadto download a JSON file containing the detailed call log.
- 8.The first line of each detailed call log states the type of call and the number it reached. If the call is a PCI call, "PCI" will be added before inbound/outbound/transfer in the log line (e.g., "PCI outbound call to...").
Detailed call logs are not created for numbers unassigned to any application. Attempting to view detailed logs for calls to these numbers will display the following notice:
Log details do not exist. No application was assigned to this number.
Figure 4 provides an example:
Figure 4: Notice displayed for calls to numbers unassigned to any application.
You can search for any words or characters that appear in any line of the detailed call log. The call log will dynamically filter to the search term(s) you enter. The total number of matching results will be displayed to the right of the search box.
The first log line that matches your search term(s) will be highlighted. You can navigate through following lines using the arrow buttons on the right side of the search box, as shown in Figure 5.
Figure 5: Example of using the search box in detailed call logs.
Each log line may contain an icon (e.g.,
, etc.) that displays additional information when you hover over it. The PCI symbol (
) appears any time a PCI number is listed in the logs.
If your application interacts with an API during a call, the request and response will be logged. Select the plus icon (
) on the left side of the log line to expand it and view full details, as shown in Figure 6.
Figure 6: Example of API request/response logging in detailed call logs.