Office Communicator and Windows Messenger Logging


What I post below comes from my teammate Jason, I have been trying to get him to start blogging with me. If you find this information useful send me an email with the subject: GET JASON A BLOG!

 
Windows Messenger 5.0/5.1 (HKEY_CURRENT_USER\Software\Microsoft\Tracing)
==========================================================
To generate a logfile, you must to set the EnableFileTracing registry value =1, exit and restart Windows Messenger
 
RTCDLL        The tracing registry key for the SIP protocol conversation, limited authentication information, 
and DNS queries made by client during automatic configuration
RTCIMSP      The tracing registry key for the Instant Messaging Service Provider. 
UI API calls. Useful when data on the wire looks correct, but information is not correctly displayed within the application 
 
Office Communicator 2005 (HKEY_CURRENT_USER\Software\Microsoft\Tracing)
==========================================================
To generate a logfile, you must to set the EnableFileTracing registry value =1, exit and restart Communicator.
LCAPI            The tracing registry key for the SIP protocol conversation, limited authentication information, 
and DNS queries made by client during automatic configuration. All the lower level SIP traffic is logged to this file.
LCIMSP         The tracing registry key for the IM Service Provider. This contains logging for IM and Presence activities
 
Toml LCS Kid

Comments (2)
  1. Paul Brombley says:

    Toml,

    You forgot to mention to use the RTCMON tool in the Reskit to display the files. This now makes it much easier to follow the trace.

Comments are closed.

Skip to main content