So be early and log a little longer to make Sure you captured the issueĤ. we want to include the period where the issue occurred. Log File Folder: Output is going to be where you want your output log to be placedģ. (ignoring the Edit Tab) and follow these stepsġ. Use Figure 2 below to help with instructions (Skip tab2 in the middle, it will only confuse things) Once the call is finished chose “ stop scenario” (5)
In our case we are making a call to another user. Choose “ start scenario”, when you are ready to recreate issue. you should collect FE servers and Edge logs separately (3) Check the Front end server- or what ever sever you want logs from. This choice will work for most issues because we just need the S4 and Sip Stack Flags (2) Choose “Incoming and outgoing call” from the Drop Down. Choose the Stop and stop scenario (1) See Figure 1 Below YOUR GOING TO RECEATE YOUR ISSUE DURRING THIS STEP. BEGIN REPRODUCING AS SOON AS THE START SENARIO BUTTON You are going to see three tabs, Ignore the Edit One Your going to run a trace and get a copy of the trace. If youĪre just starting out, only pay attention to the first and third tab. Start the application C:\Program Files\Skype for Business Server 2015\Debugging Tools\ClsLogger.exeīefore I even get started, I will tell you three times during this article, “Ignore the middle tab”. Once you have the tool in your hand, you simply run the default install, and the tool will be created in the path: If you Download CLS logger, I will show you in just a few steps, how to get the logs you need. It is a natural thing to do to help users gets the logs they need, without the size that command line logging can yield. This CLSLogger should be made part of the SFB product. If you remember the Skype 2015 Resources tool kit, This kit contains CLSLogger And Snooper. However, it is made difficult by the need to use The command line. Logging in Skype for Business has a lot of potential. I have a video which complements this blog located at YouTube.
0 kommentar(er)
