Use this page to create a Session Detail report.
Use this page to create a Session Summary report.
This page contains the:
Fields common to the Call Detail, Session Summary, and Session Detail reports
Date and Time group
|
Button |
Description |
|---|---|
|
Predefined Values |
The options are:
|
|
Last |
Limits the report to a given number of days or hours. Enter that number of days or hours in the associated text field, then select Days or Hours from the associated drop-down list. You can enter a whole number from 1 to 99. The number of days is calculated from midnight to 11:59 p.m. For example, if the current time is 3:00 p.m. on Wednesday and you enter a 3 in this field and select Days from the drop-down, the report will include all activity starting on Monday at midnight through the end of the current day. |
|
Between |
Limits the report to a specified range of dates. The default range covers a seven day time span that ends with the current date and time. If you want a different range of dates:
|
The amount of data available for this report depends on the setting for call data records in the Call/Session Retention Period field in the Report Database Record Data group on the Report Data Configuration page.
For example, if the value is set to 14, you can enter a start date that is two weeks before the current date. If the value is set to 7, you can only check for the previous week.
Optional Filters group
In any text field:
All searches are case insensitive unless otherwise noted.
You can replace one or more characters with a wildcard. To replace one character, use
_(underscore). To replace any number of characters, use a%(percent sign).For example,
car_matchesCart
orcars
, whileCar%matchesCart
,cars
,Cart Rentals
,Car Rentals
,CARPET
, and so on.To specify multiple keywords, any one of which will result in a match, use the
,(comma) search operator to separate the keywords. For example, to find all calls that came from either 111-555-1212 or 222-555-1214, you would enter tel:1115551212,tel:2225551214 in the Originating # field.To specify that a keyword should NOT appear in record, use the
~(tilde) search operator in front of the keyword. For example, to find all calls that did NOT come from 111-555-1212, you would enter ~tel:1115551212 in the Originating # field.To specify that multiple keywords must all appear in a record for it to be a match, use the
+(plus sign) search operator in front of the keyword.You can combine wildcards and search operators. For example, if you want to eliminate all calls that originated from numbers in the 408 and 303 area codes, you would enter ~tel:303%+~tel:408% in the Originating # field.
|
Field or Link |
Description |
|---|---|
|
Reset |
Restores the default filter settings and displayed column settings. The default columns are:
Note:
When you click this link, Experience Portal restores the defaults for all filters, even those that are not displayed if the section is collapsed. |
|
Avaya Experience Portal |
If your installation has multiple Experience Portal systems that use a shared database, this field lists all of the available systems. The options are:
|
|
Media Server |
The name of the media server that handled the session. The options are:
|
|
Application Server Application Name |
The name or URL of the application server that handled the session. The options are:
Note:
This filter only works for applications compiled with Orchestration Designer 4.0 or later. |
|
more >> |
Displays the rest of the optional report filters. Note:
The rest of the fields in this group do not display until you click this link. |
|
Show Column |
Each filter has an associated check box under this header. To show a particular piece of information in its own column in the report, select its associated Show Column check box. To hide that piece of information, clear the associated check box. |
|
Average ASR % |
The average percentage of utterances that were recognized by the Automatic Speech Recognition (ASR) server. Any Average ASR values of 30 or less are displayed in red, unless there were no speech inputs in the session. The options are:
|
|
Recognized Utterances Recognized Number of Utterances |
The number of utterances that were correctly recognized during the session. The options are:
|
|
Total Utterances/Interactions Total Number of Utterances |
The total number of utterances made by the caller during the session. For sessions of type HTML, this value represents the number of user interactions with the mobile application. That is the number of HTML pages fetched. Note:
This value does not include Dual-tone multi-frequency (DTMF) responses. The options are:
|
|
Average Confidence |
The average confidence level achieved while recognizing utterances. The options are:
|
|
First Prompt Latency |
The number of milliseconds after Avaya Experience Portal received the call before the initial prompt began playing.
Note:
The First Prompt Latency value includes both the time it took Avaya Experience Portal to answer the phone as well as the time it took the first application page to load and request that a prompt be played. The options are:
|
|
Average Prompt Latency |
The average time, in milliseconds, after the caller issued a speech command before the subsequent prompt began playing. The options are:
|
|
Duration |
The length of the session in seconds. Note:
The duration of a session includes call timeouts and other overhead operations that are not included in any particular call. Therefore, the duration of an entire session may be greater than the sum of the call durations that took place during that session. The options are:
|
|
Highest Page Loading Latency Highest Page Latency Time |
The number of milliseconds that it took for Avaya Experience Portal to retrieve the slowest application page from the application server The options are:
|
|
Highest Page Loading Latency (URL) URL |
The URL of the VoiceXML page that was the slowest to load. |
|
Lowest ASR Recognition % |
The lowest percentage of utterances that were recognized by the ASR server for any page used in the session. The options are:
|
|
Lowest ASR Recognition (Recognized Utterances) Number Of Recognized Utterances For Lowest ASR Page Number of Recognized Utterances |
The number of correctly recognized utterances made on the page with the lowest percentage of correctly recognized utterances. The number of correctly recognized utterances made on the page shown in the URL field. The options are:
|
|
Lowest ASR Recognition (Total Utterances) Total Utterances For Lowest ASR Page Total Number of Utterances |
The total number of utterances made on the page with the lowest percentage of correctly recognized utterances. The total number of utterances made on the page shown in the URL field. The options are:
|
|
Lowest ASR Recognition (URL) Lowest ASR Page URL URL |
The URL of the VoiceXML page with the lowest number of recognized utterances. |
|
Maximum Consecutive Recognition Errors |
The maximum number of times in a row that an utterance was not recognized during a session. Note:
This value tracks the maximum consecutive number of recognition errors, not the total number of recognition errors for a given utterance. For example, if the caller had to repeat the word "brokerage" twice on the first menu and three times on the second menu, then this field would display 3. The options are:
|
|
ASR Session ID |
The Session ID on the ASR server.
This is the MRCP session ID if the ASR server uses the MRCP protocol.
Note:
When multiple ASR servers are used, the ASR Session ID field contains only the first Session ID. To find all of the ASR Session IDs, examine the Speech events in the Session Transcription. |
|
TTS Session ID |
The Session ID on the Text-to-Speech (TTS) server. This is the MRCP session ID if the TTS server uses the MRCP protocol. |
|
Performance Trace |
Whether there is a performance trace log available for this session. The options are:
|
|
Session Source |
How the session started. The options are:
For more information on the web service methods, see the The Application Interface web service chapter in the Administering Avaya Experience Portal guide. |
|
Session Type |
The options are:
|
|
Session Transcription |
Whether there is a session transcription log available for this session. The options are:
|
|
Slot |
The session slot number, used by Avaya Experience Portal to uniquely identify the session. This slot number is included in the name of the associated logs on the media server. The options are:
|
|
Start Page Name |
The name of the first page that the session accessed on the speech server. |
|
Exit Page |
The VoiceXML or CCXML page where the disconnect event occurred. |
|
Exit Info #1 |
Optional information regarding the termination of the session. The application developer determines the value for this field. For example, this field contains the customer ID if the Dialog Designer application developer stores the customer ID in the exitInfo1 field of the session variable. |
|
Exit Info #2 |
Optional information regarding the termination of the session. The application developer determines the value for this field. For example, this field contains the customer ID if the Dialog Designer application developer stores the customer ID in the exitInfo2 field of the session variable. |
|
Exit Reason |
The reason why the session ended. The application developer determines the value for this database field by setting the exitReason field of the session variable. If the application does not pass a value, this field defaults to Application exited. |
|
VoiceXML Page Cache Hits |
The number of times a VoiceXML page was retrieved from the cache during the session. The options are:
|
|
VoiceXML Page Requests |
The number of VoiceXML pages that were requested during the session. The options are:
|
|
Session ID |
The unique identifier for the session assigned by the media server. Note:
This field is case-sensitive. |
|
Parent ID |
When sessions are related, the session id of the starting session. Applications can set the Parent ID by using the exit variable exitParentID. This can be used to logically link sessions to a single parent session to facilitate the generation of end-to end-reports. Note:
Not all applications are written in a way that supports this feature. In order for the value to be populated, the Orchestration Designerdeveloper must save the original session ID and store the session ID in each related session by setting the field exitParentId in the session variable. For more information, see Orchestration Designer documentation. |
|
Dialog ID |
The unique global identifier given to every dialog belonging to the session. |
|
Application |
The name of the application. |
|
ASR Server |
The name of the ASR server that handled the session and the number of seconds that it was used. Multiple servers are separated by a comma. |
|
TTS Server |
The name of the TTS server that handled the session and the number of seconds that it was used. Multiple servers are separated by a comma. |
|
<< less |
Collapses the Optional Filters group. |
Fields common to the Call Detail, Session Summary, and Session Detail reports
|
Start Time Start Date/Time |
The date and time that the session started. |
|
Total Sessions |
The total number of sessions that match the specified filter criteria. |
|
View Session Details icon |
To view the details for a particular session, click this icon at the end of the row. Avaya Experience Portal displays the Session Details page. |
Report Type group
The report type or types you want to summarize by.
The options are:
Session Averages displays the Session Averages group.
Highest Page Loading Latency displays the Highest Page Loading Latency group.
Lowest ASR Recognition displays the Lowest ASR Recognition group.
Exit Page displays the Exit Page group.
Exit Info #1 displays the Exit Info #1 group.
Exit Info #2 displays the Exit Info #2 group.
Exit Reason displays the Exit Reason group.
Topic displays the Topic group.