Explore Cisco
How to Buy

Have an account?

  •   Personalized content
  •   Your products and support

Need an account?

Create an account

Jabber for Windows MSI Log Collection for Video Issues

Available Languages

Updated:September 5, 2013
Document ID:116338

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

This document describes how to collect MSI logs for video issues on Cisco Jabber for Windows.

Collect MSI Logs for Video Issues on Jabber

By default, MSI logs only warnings and errors to the Windows event log.

The logs can be found in the "Applications and Services Logs" subtree, under "Cisco MSI". In order to see more logs or to edit logs, log in as an Administrator, and navigate to \program files\cisco systems\media services interface\msi.ini and change "syslog;warn" to "syslog;info" or "syslog;debug". The word "syslog" remains from the original Unix version. In Windows, this means "log to the event log".

The same can be logged to a file in this manner:

"file;info;C:\\Windows\\TEMP\\msi.log".

Note: The capitalization must match the example and the backslashes need to be doubled because of the double quotes.

When the msi.ini file is changed, restart the Cisco Media Services Interface service in order to restart msid.exe.

Related Information

Revision History

Revision Publish Date Comments
1.0
05-Sep-2013
Initial Release
TAC Authored

Contributed by Cisco Engineers

  • Farbod Karami
    Cisco TAC Engineer.

Was this Document Helpful?

FeedbackFeedback

Contact Cisco

This Document Applies to These Products