
The decoding of port 443 can have false positive matches for different packet types. So now you can have the plugin running all the time and still troubleshoot TLS handshaking issues on port 443. This also makes the plugin better To be used with the latest release of Wireshark (however, the plugin should work with higher than Wireshark 1.0)Ĭhanged the naming of the plugin to LYNC_SKYPE_PLUGIN.īig updates to RTP and STUN classification to fix detection issues.Ĭorrected some issues with decoding 0x0013 Data Attribute encapsulated data.Īdded TLS pass-through to the Wireshark default SSL dissector for Hello, Handshaking, and Application data. If you enter “lync_skype_plugin” in the Filter bar, only the traffic that is being decoded by the Lync Plugin will be displayed. (Edit->Preferences->Protocols->LYNC_SKYPE_PLUGIN) Port numbers can be changed within Wireshark Preferences. This Wireshark plugin dissects dynamically assigned RTP and RTCP traffic by using ports allocated in STUN requests.ĭissector can be turned on/off within Wireshark Preferences. This Wireshark plugin dissects traffic on Microsoft Lync Edge port 443 (STUN, RTCP, RTP) This Wireshark plugin dissects STUN/TURN traffic on Microsoft Lync Edge port 3478 (STUN, RTCP, RTP) Captures can be taken on the Edge server (Capturing AV Edge External traffic, and Internal Interface traffic), or it can also be used on the client side for decoding This Wireshark plugin is designed to dissect Lync AV Edge and Internal Edge AV traffic. The plugin has been written based on the specifications in the following Lync / Skype for Business servers or also on Lync / Skype for Business client machines to allow you to see exactly how ICE/TURN/STUN negotiation and RTP/RTCP traffic is being sent. So I created a LUA plugin for Wireshark that does this job. The standard protocol decoders within Wireshark do not correctly decode a lot of the ICE/TURN/RTP/RTCP traffic created by Lync / Skype for Business clients and servers. Microsoft Lync / Skype for Business Wireshark Plugin
