© 2006 Cisco Systems, Inc. All rights reserved.1 Connection 7.0 Serviceability Reports Todd Blaisdell.

© 2006 Cisco Systems, Inc. All rights reserved.2  Reports Overview  Reports Detail  What’s New in 7.0  Setting Report Configuration Parameters  Connection Reports Data Harvester Overview  Trouble Shooting  Serviceability Reports Screen Shots Agenda

© 2006 Cisco Systems, Inc. All rights reserved.5 Reports Overview Continued Reports in 2.1:  Phone Interface Failed Logon Report  Users Report  User Message Activity Report  Distribution Lists Report  User Lockout Report  Unused Voice Mail Accounts Report  Transfer Call Billing Report  Outcall Billing Detail Report  Outcall Billing Summary Report  Call Handler Traffic Report  System Configuration Report

© 2006 Cisco Systems, Inc. All rights reserved.6 Reports Detail  Phone Interface Failed Logon Report –Output includes the following information for every failed attempt to log on to Connection by phone:  User name, alias, caller ID, and extension of the user who failed to log on  Date and time that the failed logon occurred  Whether the maximum number of failed logons has been reached for the user  Users Report –Output includes the following information for each user:  Last name, first name, and alias  Information that identifies the Connection server associated with the user  Billing ID, class of service, and extension  Whether the account is locked  Whether the user has enabled personal call transfer rules  User Message Activity Report –Output includes the following information about messages sent and received, per user:  Name, extension, and class of service  Date and time for each message  Information on the source of each message  Action completed (for example, new message, message saved, MWI On requested, and so on)  Information on the number of new messages received for a user, and on the message sender  Dial out number and results

© 2006 Cisco Systems, Inc. All rights reserved.7 Reports Detail continued  Distribution Lists Report – Output includes the following information:  Name and display name of the list  Date and time the list was created  Date and time of the creation of the distribution list is given in Greenwich mean time.  A count of the number of users included in the list  If the Include List Members check box is checked, a listing of the alias of each user who is a member of the list.  User Lockout Report –Output includes user alias, the number of failed logon attempts for the user, credential type (a result of “4” indicates a logon attempt from the Connection conversation; a result of “3” indicates a logon attempt from a web application) and the date and time that the account was locked. –Note: Date and time of the lockout of the user account is given in Greenwich mean time.  Unused Voice Mail Accounts Report –Output includes user alias and display name, and the date and time that the user account was created. –Note: Date and time of the creation of the user account is given in Greenwich mean time.  Transfer Call Billing Report –Output includes the following information for each call:  Name, extension, and billing ID of the user  Date and time that the call occurred  The phone number dialed  The result of the transfer (connected, ring-no-answer (RNA), busy, or unknown)

© 2006 Cisco Systems, Inc. All rights reserved.8 Reports Detail continued  Outcall Billing Detail Report –Output includes the following information, arranged by day and by the extension of the user who placed the call:  Name, extension, and billing ID  Date and time the call was placed  The phone number called  The result of the call (connected, ring-no-answer (RNA), busy, or unknown)  The duration of the call in second  Outcall Billing Summary Report –Output is arranged by date and according to the name, extension, and billing ID of the user who placed the call, and is a listing of the 24 hours of the day, with a dial out time in seconds specified for each hour span.  Call Handler Traffic Report – Output includes the following information for each call handler, in rows for each hour of a day:  Total number of calls  Number of times each touchtone key was pressed  Extension  Invalid extension  Number of times the after greeting action occurred  Number of times the caller hung up  System Configuration Report –Output includes detailed information about all aspects of the configuration of the Connection system.

© 2006 Cisco Systems, Inc. All rights reserved.9 What’s New in 7.0  Five new reports in Miyazaki –Message Activity Report  This report shows how many messages are received by the system.  Message Types: –Email –Voice –Fax –Non Delivery Receipt –Delivery Receipt –Read Receipt –Mailbox Store Report  This reports displays information about all Mailbox Stores. The following information is displayed: –Display name –Server –Access Enabled –Number of Mailboxes –Current Size (in Kilobytes) –Maximum Size Before Warning (in Megabytes) –Last Error –Status –Deletable

© 2006 Cisco Systems, Inc. All rights reserved.10 What’s New in 7.0 continued –Port Activity Report  This reports displays all Port Activity. The following types of calls are reported: –Inbound Call –Outbound Amis –Outbound MWI –Outbound Notification –Outbound Trap –Dial Plan Report  This report displays all partitions within a Search Space and VMS location. –Dial Search Scope Report  This report displays all addressable objects within a Partition and Search Space.  Enhancements to several existing reports

© 2006 Cisco Systems, Inc. All rights reserved.11 Setting Report Configuration Parameters  All report parameter settings are found on the System Settings > Advanced > Reports page in Cisco Unity Connection Administration.  Cisco Unity Connection is automatically set to gather and store data from which you can generate reports. The following parameters can be adjusted, depending on the report output that you want to generate. –Enable Audit Log  This setting enables and disables the audit log. If this setting is disabled, stored procedures will stop writing to the audit log. –Maximum Events Allowed in Audit Log  Enter the maximum number of audit events allowed in the audit log table. When the maximum threshold is reached, the oldest events will be removed to make room for new ones. Enter a number between 1 and 100,000. Default Setting: 100,000. –Enable Security Log  This setting enables and disables the security log. If this setting is set to disabled, stored procedures will stop writing to the security log. –Maximum Events Allowed in Security Log  Enter the maximum number of audit events allowed in the audit log table. When the maximum threshold is reached, the oldest events will be removed to make room for new ones. Enter a number between 1 and 100,000. Default Setting: 100,000. –Milliseconds Between Data Collection Cycles  Set by default to 30 minutes (1,800,000 milliseconds). This setting controls the amount of time Connection waits between cycles of gathering report data. –Days to Keep Data in Reports Database  Set by default to 180 days. Note that even if you specify more than this number of days in the time range for the report you are generating, the number of days of data is limited by what you set here. –Maximum Records in Report Output  Set by default to 25,000 records. The maximum value allowed for this field is 30,000 records. If the report you want to generate exceeds the maximum number of records allowed, you can generate the report in pieces, for example by reducing the date range or number of user accounts included in each iteration. –Minimum Records Needed to Display Progress Indicator  Set by default to 2,500 records. The maximum value allowed for this field is 10,000 records. The purpose of the progress indicator is to warn you if the report you request is large and likely to take a long time to complete. In Connection, reports are generated from within a browser, and the browser session must be kept open while the report is being generated. Depending on the size of the database, and the type of report being generated, a report can take a long time to generate; meanwhile, you will be unable to use the browser, and must keep the Connection Administration session open

© 2006 Cisco Systems, Inc. All rights reserved.12 Connection Reports Data Harvester Overview  The Connection Reports Data Harvester is a service used to populate the reports database. –An engine that parses log files created by Connection, parses data from the log lines and places the parse results in the Reports database.  It is also used to delete rows from the reports database  The Connection Reports Data Harvester service can be started/stopped from the CUC Serviceability page->Tools->Control Center  The Reports database (rpt_dbs) can be found at /common/var-connection- 7.0.0.xxxx/db/

© 2006 Cisco Systems, Inc. All rights reserved.13 Trouble Shooting  Logs –Tomcat Logs  Located in /var/opt/cisco/connection/log  diag_Tomcat_xxxxxxxx.uc  Turn on the Micro Trace – CuService –Data Harvester Logs  Located in /var/opt/cisco/connection/log  diag_CuReportDataHarvester_xxxxxxxx.uc  Turn on the Micro Trace – ReportDataHarvester  Reports Database –The Reports database is not replicated. For an A/A system, both Reports databases are read and the information is combined.

© 2006 Cisco Systems, Inc. All rights reserved.14 Trouble Shooting Continued  Things to look for if no data in reports: –Make sure the Reports Harvester is active.  Go to Cisco Unity Connection Serviceability->Service Management and make sure that the Connection Reports Data Harvester service is active. Also check the running time, make sure it is not zero.  Check the Milliseconds Between Data Collection Cycles value under Cisco Unity Connection Administration->System Settings >Advanced >Reports –Check the Reports database for valid data.  This can be done by using a database tool such as dbaccess.  To access the Reports database from dbaccess, use the following command: –dbaccess unityrptdb@ciscounity  The documentation that describes the schema for the Reports database: –CUC 7.0 Data Dictionary Reports Database (EDCS-690830)  The following are the tables in the reports database are used by the serviceability reports:

© 2006 Cisco Systems, Inc. All rights reserved.15 Trouble Shooting Continued  Phone Interface Failed Logon Report –vw_TuiLoginFailures  Message Traffic Report –vw_MessageActivity  Port Activity Report –vw_PortActivity  Subscriber Message Activity Report –vw_SubscriberMessage  Call Handler Traffic Report –vw_CallHandlerTraffic  Outcall Billing Detail Report –vw_OutcallBilling  Outcall Billing Summary Report –vw_OutcallBilling  Transfer Call Billing Report –vw_TransferCallBilling

© 2006 Cisco Systems, Inc. All rights reserved.1 Connection 7.0 Serviceability Reports Todd Blaisdell.

Similar presentations

Presentation on theme: "© 2006 Cisco Systems, Inc. All rights reserved.1 Connection 7.0 Serviceability Reports Todd Blaisdell."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

© 2006 Cisco Systems, Inc. All rights reserved.1 Connection 7.0 Serviceability Reports Todd Blaisdell.

Similar presentations

Presentation on theme: "© 2006 Cisco Systems, Inc. All rights reserved.1 Connection 7.0 Serviceability Reports Todd Blaisdell."— Presentation transcript:

Similar presentations

About project

Feedback