Windows: Follow the steps included in the Sign In tutorial. Mac: Follow.In Skype for Business 2016, click Tools, click Options (or click the Options icon), click General, and then select Full in the Logging in Skype for Business drop-down list. Exit the Office Communicator, Lync, or Skype for Business Client. Start Windows Task Manager, and then make sure that the Communicator.exe process is no longer running.Below you can find the instructions for your version of Lync client:Logging in to Skype for Business. You will use your Microsoft 365 organizational account to log into Skype for Business. Username for Faculty/Staff: netidutk.Skype for Business.
Skype For Business Logs For Mac Or LyncComing from a traditional Microsoft background, when I started with Lync I had no conception of voice, or SIP and spent the best part of my early career actively avoiding anything to do with the subject.I have never been officially trained on Lync or Voice over IP. This blog is mainly for myself but it may serve anyone who needs a refresher or who is beginning to enter the world of SIP and Skype for Business. Communicator 2011 For Mac or Lync 2011 for MacTo enable logging in the Office Communicator, click the menu icon in the left-upper corner of the OCS window and navigate to Tools > Options, then in Office Communicator - Options window navigate to General tab and check Turn on logging in Communicator under Logging:In the Lync 2010 window click on Preferences icon to access the Options menu, or click on the drop-down arrow next to it and navigate to Tools > Options, in the Lync Options window navigate to General tab and check Turn on logging in Lync under Logging:In the Lync 2013 window click on Preferences icon to access the Options menu, or click on the drop-down arrow next to it and navigate to Tools > Options, then in the Lync Options window navigate to General tab and under Logging in Lync select Full:In the Skype for Business window click on Options icon to access the menu, or click on the drop-down arrow next to it and navigate to Tools > Options, then in the Skype for Business Options window navigate to General tab and under Logging in Skype for Business select Full:Enabling logging in Communicator 2011 for Mac or Lync 2011 for MacIn the menu bar navigate to Communicator > Preferences or Lync > Preferences, then to General tab and check the Turn on logging for troubleshooting checkbox:Enable logging in Skype for Business for MacIn the menu bar navigate to Skype for Business > Preferences > General > click on the Collect Logs button.The log files on Windows machines are stored under: Compatible with Office 365, Skype for Business Server 2015, and Lync Server 2013.Windows: If Skype for Business does not start automatically, click Start -> All Programs -> Microsoft Office -> Skype for Business.I am Microsoft, why would I have this experience? But as a Skype consultant you’re expected to have knowledge of these systems to some degree if you are to integrate voice especially.I know I am never going to deploy or work on these other systems, but learning how the underlying protocols work gives you a firmer footing to deal with questions around it. I have never deployed or administered a Cisco or Avaya PBX system for instance because I just haven’t been in a situation where I have needed to. As a result, I often find it difficult to grasp some concepts on how things work outside of Lync / Skype for Business. There are still some areas where I feel I have gaps in my “data bank” as it were. Some might say this is the best way to learn, and while I agree to a point, there are times where I am in a room full of people and feel like the novice still.Granted almost every system has their own small modifications to the protocol (usually additional information only relevant to their system within the SIP message) but the core methods are pretty standardised. Both Cisco, Microsoft and others conform to at least SIP RFC 3261 an internet standards based protocol. SIP is just one of these protocols.![]() You open this log using Snooper, a tool included in the Skype for Business Debugging Tools. They are stored in log files on clients and can also be captured from the Server using centralised logging or using a network packet capture program such as Wireshark.With Skype for Business Online and Cloud PBX you lose some of this end to end traceability because you don’t have access to the Front End Servers, so all your troubleshooting is done using the client log file called Lync-UCCApi.UCCApiLog located in the local app data folder of the user’s profile. SIP messages are not located in Server Event Logs like most Microsoft applications. Hence the reason for this blog. I still struggle sometimes and get lost. SIP Messaging 101When you first open Snooper and parse the log file it can be quite daunting. It provides deep insight into a SIP conversation and it fundamental to troubleshooting communication problems within the Skype for Business ecosystem. Can i use cornstarch instead of flour for mac and cheeseTo explain what is going on here, there is a process flow view in Snooper (the purple icon top right with arrows) that provides a graphical view of a conversationThis view lists out the entire message transaction log of the conversation in order. Either way you end up with something like thisThis image shows you the complete conversation that happened between two parties. The called party or find the first invite in the conversation and right click to find related messages to the same conversation. You can do this by searching the log for unique values e.g. The trace tab gives you verbose information of the entire log file.The first thing you want to do is filter the log to show only to conversation you want to troubleshoot. Here, lists all the SIP messages captured by the log. Once the called parties endpoint accepts the INVITE it responds with a 200 OK message. The SIP Proxy then forwards the INVITE to the called parties SIP Proxy which then forwards to the called parties endpoint (if available). The INVITE contains information on who the endpoint is, who they are trying to contact and other information required in order to setup a call such as location information, supported methods and features. 183 SESSION PROGRESS is often referred to as Early Media. 101 PROGRESS REPORT is the result of the TRYING request. 100 TRYING means that the SIP Proxy is trying to proxy the communication to the called party. Events starting with 1xx are informational messages that provide an update to clients during a conversation. When the called party picks up the receiver, then the 200 OK message is sent by the called party and the ACK by the calling party. This is the point where both endpoints have enough information of each other in order to communicate and is often the point where you can guarantee that the called party will hear a ring tone. This is often referred to as Late Media. Eventually you will see a 180 RINGING message. Typically 183 messages contain SDP information which tells each client what codec to use and which media candidate to connect to. We can see it is an INVITE as the method is clearly displayed in BOLD and contains the SIP address of the called party as well as the protocol being used (SIP version 2.0). As a result, people can make sense of what is going on rather than having to convert hex to ASCII to find error codes etc.This image is an extract from the first INVITE message sent in a conversation. This is because the SIP protocol is an ASCII based protocol, meaning that it is a human readable format. Contents of a SIP MessageWhen you look at the body of a SIP Message it looks similar to e-mail. When the other party receives this message it responds with a 200 OK message and the call is then teared down and no longer valid. ![]() The USER-AGENT is the physical client the party is using to generate this conversation. This will increment as the conversation continues and is useful to determine where you are in a conversation when troubleshooting.The CONTACT header contains the identity of the party where responses should be sent to. Here 1 is displayed because it is the first message to be sent and the method used is INVITE. The CSEQ header is the Call Sequence identifier. This ID is used to identify all subsequent messages relating to this conversation. If it was UAS this would mean User Agent Server which would be the SIP Proxy server.The ALLOW header tells the other party what SIP methods the client supports. Noteworthy mention here is that UAC means User Agent Client e.g. The MS-KEEP-ALIVE header is also a Microsoft header that is used to keep connections alive when SIP is sent over the TCP network transport protocol. The MS-Conversation-ID is a Microsoft only header that is used to keep track of the conversation internally. Here we can see that the client supports features like transfer, escalation to conference, media bypass, early media, session timer etc. 2109 which relates to Skype for Business 2016 Click to Run Windows.The SUPPORTED headers contain information of what other methods and headers the client supports in this conversation. NOTIFY – Notify is used to alert an endpoint when the state of another endpoint changes. REFER – Refer is used to transfer a conversation from one endpoint to another like transferring from your desk phone to your mobile, or to another party entirely, or even voicemail UPDATE – This is used for when something changes in a conversation from the last setup configuration, such as changing codecs due to bandwidth etc. INFO – This is used for mid-session signaling information to be passed between clients You hang up before the called party answers CANCEL – this method is used to cancel a pending message / request e.g.
0 Comments
Leave a Reply. |
AuthorMassiel ArchivesCategories |