Peer-to-Peer Desktop Sharing Session Reports
Peer-to-peer desktop sharing sessions can also be referred to as Skype for Business or Lync desktop sharing. Reports include data only for successful peer-to-peer desktop sharing sessions. If the end date of the session is null, MessageStats does not include the session.
The following table describes the reports found in the Peer-to-Peer Desktop Sharing folder:
Comparing MessageStats Reports to the Microsoft Native Reports
If you compare information from the MessageStats report to the native Microsoft Lync or Skype for Business reports, you will see some important differences.
MessageStats reports include only successful sessions or messages. Native reports include all sessions and messages, including those which failed.
In the Microsoft native reports, the session count is based on the session starting time. In the MessageStats reports, the session count is based on the session end time. For example, if a session started on Jan 1 and ended on Jan 2, the native reports show the session on Jan 1, but the MessageStats reports will count the session on Jan 2. For ongoing sessions that cross the date boundary, the sessions are counted after the session is completed and has a session end time. A session is not counted if the session end time is blank.
MessageStats counts the same session for different media types if multiple media were used. The Microsoft native reports also count the same session in different media reports. For example, if there was a session in which both audio and desktop sharing were used. the Microsoft native reports and the MessageStats reports count the session in the audio session report and the desktop sharing session report.
The exception is when audio and video are used in the same session. The Microsoft native reports will show two different sessions but the MessageStats reports count the session as a video session and show the media used as audio-video.
In addition to appearing in the Enterprise Voice reports, enterprise voice calls are included in the peer-to-peer session details reports along with audio, video, and desktop-sharing sessions. However, the IM (instant messaging) and file transfer sessions only appear in the separate IM and File Transfer reports and are not included in the peer-to-peer session reports.
For more information about how chargeback for enterprise voice calls are calculated see Calculating Enterprise Voice Chargeback Costs .
The native Microsoft Lync peer-to-peer activity reports include enterprise voice, IM, and file transfer sessions in addition to the peer-to-peer audio, video and desktop sharing sessions.
The MessageStats Peer-to-Peer Audio Call Usage, Peer-to-Peer Video Call Usage, and Peer-to-Peer Audio Desktop Sharing Session Usage reports now include public sessions, so they can be compared to the Microsoft native reports. You can also use the Peer-to-Peer Session Details report and set the appropriate Session Type filter to compare MessageStats results to the native reports.
Appendix A: Configuring RPC through a Firewall
This appendix provides a procedure that you can use to configure Remote Procedure Call (RPC) on your Edge server through a firewall. The procedure assumes that you are using a Microsoft ISA Server as your firewall software. If you are using another firewall solution, the concepts behind the procedure are still valid.
Federations are stored on the Skype for Business or Lync Edge server which is in the DMZ. If you want the federated domains to be automatically discovered, you must open certain ports in the firewall to allow the information be retrieved from the Edge server.
If your security policies do not allow you to provide access to the Edge server, you can manually add your federated domains to the report pack so that users in these domains are correctly reported. For information about manually adding federated domains, see Identifying Federated Domains .
There are three parts to the process:
Creating Credentials on the Edge Server
To gather from the Skype for Business or Lync Edge server, you must create another account on the Edge server that has the same credentials (same user name and password) as the service account used to run the report pack gathering tasks such as the Default Lync & Skype for Business or the Lync & Skype for Business Servers and Users gathering task.