1. Lync 2014
4/19/2017
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

2. Troubleshooting Lync 2013 with Enterprise Voice
Lync Conference 2013
4/19/2017
VOICE304
Troubleshooting Lync 2013 with Enterprise Voice
Name: Byron Spurlock
Title: Lync Technical Architect
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

3. Agenda Troubleshooting Approach Key Architecture Flows Tools - Demos
Common Scenarios
Monitoring Reports
Synthetic Transactions
Performance Counters - Appendix
Q&A

4. Troubleshooting Approach

5. Common Questions From Users From Administrators
Lync Conference 2013
4/19/2017
Common Questions
From Users
What was wrong with this call?
Why did I see a User Facing Diagnostic (UFD)?
I was just on a call and it dropped mid stream. Why?
From Administrators
How do I read these reports?
How can I determine what the value of X in a particular report means?
Where do I start?
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

6. Troubleshooting Approach
Network
WAN
Network Router \ Switch
Bandwidth
Policies
Wired \ Wireless
Server
Lack of Server Resources
Mis-Configuration
Client
Application Settings
Configuration
Internet Connection

7. Understanding The Challenges
Voice Quality Issues
Call Reliability
Audio Quality
Failed Calls
Dropped Calls
One Way Audio
Echo
Noise
Low Volume
Delayed Audio
Broken Up Audio
Distorted Audio
Network
Core Performance
Gateways
Devices

8. Key Architecture Flows Know the base foundation

9. Firewall: Edge

10. Conferencing Flow 5 2 4 6 1 3 7 SQL SQL Server® Backend SQL C3P/ HTTP
Conferencing Server Factory
C3P/
HTTP
Focus Factory
SQL Server® Backend
Scheduling
Client
CCCP/SIP
SQL 5
App Sharing Conf Server 2 4
Focus
Conferencing Client
CCCP/SIP
Web Conf Server
IM Conf Server
AV Conf Server
C3P/HTTP
SIMPLE/SIP 6
PSOM 1 3
(S)RTP 7
RDP/RTP

11. Voice Routing User habits Gateway selection (or not)
User Initiates Call
Normalization Rule
Dial Plan
User=phone
SIP URI
Global?
Emer. Call? No No
User habits
404: No matching rule
Call Park Orbit Range
Yes
Yes
Dialing Behaviors
Reverse Number Lookup
Routing & Authorization
No match
Match
Gateway selection (or not)
1. Vacant Number Range
2. Call Park Orbit Range
PSTN Usage
3. Voice Policy
Routes
Route
PSTN Usage
Location Policy
Mediation Server and Trunk Configuration
403: No route found
Announcement or Call Park Application
Gateway / IP-PBX / SIP Trunk
Inbound Routing
PSTN accommodations
External Endpoint Receives Call
UC Endpoint Receives Call 11

12. Lync 2013 Poster

13. Tools

14. Tools Voice Routing Test Tool ICE Warning Flag Decoder
PreCall Diagnostics
Central Logging Service
Audio Test Tool

15. Voice Routing Test Tool

16. Voice Routing Testing
Voice Routing Testing leverages test case scenarios to validate the a dial plan, voice policy, PSTN usage, and voice route
Formal Testing – Using defined numbers to be dialed and specifying the dial plan and voice policy in the test case. Verification that the results can be routed to the PSTN network
Informal Testing – Ad hoc
testing against any phone
number and any
voice route

17. Demo
Voice Routing Test Tool

18. ICE Warning Flag Decoder

19. What is an ICE Warning Flag?
ICE Protocol flags that are generated when a Lync voice call is placed. Composed in a Hexadecimal format in the MSDIAGNOSTICS section of a SIP Message.

20. ICE Warning Flags (example)
ms-diagnostics: 10032;source="mediationfqdn.contoso.com";reason="Media diagnostic information";component="MediationServer";ICEWarningFlags="Audio:ICEWarn=0x0,LocalSite= :51707,LocalMR= :54945,RemoteSite= :23371,RemoteMR= :58943,PortRange=49152:57500,LocalMRTCPPort=54945,RemoteMRTCPPort=58943,LocalLocation=2,RemoteLocation=1,FederationType=0"

21. Demo
ICE Warning Flag Decoder

22. PreCall Diagnostics

23. PreCall Diagnostics Tool
The Lync PreCall Diagnostics Tool (PCD) is a client-based application that allows you to see how the current state of your network might impact the audio quality in an upcoming Enterprise Voice call.
PCD is most useful in situations where the last hop of a network is likely to be the weakest.

24. Demo
PreCall Diagnostic Tool

25. Centralized Logging Service (CLS)

26. Centralized Logging Service (CLS)
Replaces Lync Server Logging Tool
Enables IT admin to manage logging and search logs across all Lync Servers in a deployment centrally
Start, stop, and flush trace logging for any/all machines in a deployment from one place
Start/stop logging based on scenarios
See what logging is turned on per pool/machine for the entire deployment
Search trace logs based on specified parameters from a centralized place

27. CLS Architecture CLSAgent CLSController Runs on every Lync Server
Controls logging based on commands from CLSController
Manages log files to ensure drive space is not consumed, moves old logs to fileshare
CLSController
Sends Start, Stop, Flush, and Search commands to all the CLSAgents in the deployment
Aggregates search results from CLSAgents
Available on every Lync Server in “C:\Program Files\Common Files\Microsoft Lync Server 2013\ClsAgent”
CLSController FE
CLSAgent
Start, Stop, Search commands
Search results
Start, Stop, Search commands FE
CLSAgent
Search results
Start, Stop, Search commands
Search results FE
CLSAgent

28. Scenarios Logging is based on scenarios
Built in scenarios specify a group of components and log levels to be started and stopped together
AddressBook
AlwaysOn
ApplicationSharing
AudioVideoConferencingIssue
CAA
CLS
CPS
DeviceUpdate
HostedMigration
HybridVoice
IMAndPresence
IncomingAndOutgoingCall
LILRLegacy
LILRLYSS
LYSSAndUCS
MediaConnectivity
MeetingJoin
MonitoringAndArchiving
RGS SP
UserReplicator
Voic
WAC
XMPP

29. Components Logged by Scenarios
Scenario details can be discovered
$scenario=Get-CsClsScenario global/IncomingAndOutgoingCall
foreach ($sc in $scenario.provider) { $sc.name }
Get-CsClsScenario global/<ScenarioName> | Select -ExpandProperty Provider | Format-Table Name,Level,Flags -a
For scenario:
IncomingAndOutgoingCall
Component Name
Level
MediationServer
Info S4
Sipstack
TranslationApplication
OutboundRouting
InboundRouting
UserServices
Verbose

30. The “AlwaysOn” Scenario
What is it?
The special scenario “AlwaysOn” can be on all the time. It logs INFO level for many common components
When an issue occurs there may be enough info in the AlwaysOn component logs to debug the issue
This avoids having to turn on logging and repro the issue, which was always required in Lync Server 2010
If the logs from AlwaysOn are not sufficient, turn on the specific scenario relevant to your issue, repro the issue, and get a higher level of logging
At any given time, you can have one extra scenario enabled along with AlwaysOn
When do I use it?
All the time   
Keep in mind this is not enabled by default.

31. Examples Turn on a logging scenario Run a Search Working Log Locations
Start-CsClsLogging –Scenario AlwaysOn –Pools pool.contoso.com
Start-CsClsLogging –Scenario IncomingAndOutgoingCall -Pools pool.contoso.com
Run a Search
Search-CsClsLogging –OutputFilePath “c:\Logfiles\SearchResult.txt”
Search-CsClsLogging –Components “SIPStack”,”S4”,”UserServices” –OutputFilePath “c:\Logfiles\CompSearchResult.txt”
Working Log Locations
%TEMP%\Tracing -> C:\Windows\ServiceProfiles\NetworkService\AppData\Local\Temp\Tracing
-CacheFileNetworkFolder parameter for Set-CsClsConfiguration

32. Using ClsController .\ClsController (COMMAND) [(OPTIONS)] [(SCOPE)]
Description
-start
Starts trace session for given scenario. Mandatory option: scenario. Other valid option: duration
-stop
Stops trace session for given scenario. Mandatory and only valid option: scenario
-query
Query list of scenarios being traced. Valid options: None
-flush
Flush logs and make them available for searching immediately. Valid options: None
-update
Update the duration active (nondefault) scenario needs to be traced for. Mandatory and only valid option: duration
-search
Search logs. Results are returned in a text file. Valid options: starttime, endtime, components, uri, callid, phone, ip, loglevel, matchany, matchall, keepcache, correlationids -?
Will display command line usage along with scenario names

33. ClsController Options
Description
-scenario
Scenario name (Valid scenario names were given earlier)
-duration
Duration (in minutes) to trace the given scenario for. Default duration: 24 hours
-matchall
Specify this to require the search to match all criteria specified
-matchany
Specify this to require the search to match any criteria specified. This is the default.
-starttime
(timestamp) timestamp to search the log entries from
-endtime
(timestamp) timestamp to search the log entries to
-loglevel
(fatal | error | warn | info | verbose | noise)
This is the least severe log level to search on. For example, if 'warn' is specified search will be limited to 'warn', 'error' and 'fatal'
-components
List of comma separated component names to restrict the search scope
-phone
Phone number scope for search command. This needs to be exact match
-uri
URI scope for search command. This needs to be exact match
-callid
Call id scope for search command. This needs to be exact match
-ip
IP address scope for search command. This needs to be exact match

34. Demo
Central Logging Service

35. Audio Test Service

36. Audio Test Service Leveraged for client side
testing of Audio capabilities
User leaves audio recording
Snooper results

37. Audio Test Service Logs 1of 5
<02/17/2014|12:38: E50:1590 INFO :: Data Received :443 (To Local Address: :62437) 3844 bytes:
02/17/2014|12:38: E50:1590 INFO ::
SIP/ OK
ms-user-logon-data: RemoteUser
Via: SIP/2.0/TLS :62437;received= ;ms-received-port=22112;ms-received-cid=9497D00
Authentication-Info: TLS-DSK qop="auth", opaque="FDBCBDDB", srand="BA4FA844", snum="27", rspauth="a11a7798ac1503a43f12d024918da48ed4d6d589", targetname=“Server1.Contoso.com", realm="SIP Communications Service", version=4
FROM: "Spurlock,Byron
TO: "Audio Test
CSEQ: 1 INVITE

38. Audio Test Service Logs 2 of 5
CALL-ID: 9af1f616009d47e78bdf e21f0
RECORD-ROUTE: <sip:POOL01.Contoso.com:5061;transport=tls;ms-fe=Server03.Contoso.com;opaque=state:F;lr;received= ;ms-received-cid=90AD602>
RECORD-ROUTE: <sip:lync.Contoso.com:443;transport=tls;opaque=state:Ci.R9497d00;lr;ms-route-sig=ctpAEzburC4SrvL25Q37iYSgblGihzwCn8Wrk7wAQHG3VVGC9cs_yTzAAA>
CONTACT:
CONTENT-LENGTH: 1521
PRIORITY: Normal
SUPPORTED: Replaces
SUPPORTED: ms-dialog-route-set-update
SUPPORTED: gruu-10
SUPPORTED: timer
SUPPORTED: 100rel
CONTENT-TYPE: application/sdp

39. Audio Test Service Logs 3 of 5
ALLOW: ACK
ALLOW: CANCEL,BYE,INVITE,MESSAGE,INFO,SERVICE,OPTIONS,BENOTIFY,NOTIFY,PRACK,UPDATE
P-ASSERTED-IDENTITY: "Audio Test
SERVER: RTCC/ ATS/
SUBJECT: Test Call
Content-ID: 6f84e04a-653b-41e aefb3dfb
Ms-Conversation-ID: Ac8sD2LxJprQRZ0NRsG8WDrlpb/mWA==
ms-endpoint-location-data: NetworkScope;ms-media-location-type=Intranet
ms-diagnostics: 24100;Component="RTCC/ _ATS/ ";Reason="General diagnostic information.";CalleeICEWarningFlags="Audio:ICEWarn=0x400000,LocalSite= :39991,LocalMR= :50701,RemoteSite= :39469,RemoteMR= :58201,PortRange=49152:57500,LocalMRTCPPort=50701,RemoteMRTCPPort=58201,LocalLocation=2,RemoteLocation=1,FederationType=0";Source="dcpwplync01.Contoso.com"

40. Audio Test Service Logs 4 of 5
Session-Expires: 1800;refresher=uas
Min-SE: 90
v=0
o= IN IP
s=session
c=IN IP
b=CT:
t=0 0
m=audio RTP/SAVP
c=IN IP
a=rtcp:52239
a=ice-ufrag:Pn74
a=ice-pwd:iw3stqmcpZnFy+x5o9uiKfZ2

41. Audio Test Service Logs 5 of 5
a=candidate:1 1 UDP typ host
a=candidate:1 2 UDP typ host
a=candidate:2 1 tcp-pass typ relay raddr rport 39991
a=candidate:2 2 tcp-pass typ relay raddr rport 39991
a=candidate:3 1 UDP typ relay raddr rport 54286
a=candidate:3 2 UDP typ relay raddr rport 54287
a=candidate:4 1 tcp-act typ relay raddr rport 39991
a=candidate:4 2 tcp-act typ relay raddr rport 39991
a=candidate:5 1 tcp-act typ srflx raddr rport 50515
a=candidate:5 2 tcp-act typ srflx raddr rport 50515
a=label:main-audio

42. Common Scenarios

43. Common Scenarios Audio Video Conferencing
Remote User – Enterprise Voice
Many Many More…

44. Scenario – Audio Video Conferencing

45. Conferencing 1 of 3
Authentication-Info: TLS-DSK qop="auth", opaque="FDBCBDDB", srand="0FBCE3F4", snum="7", rspauth="125a0197b19040c4eecc0e69bbdbb468afc8c23e", targetname="DCPWPLYNC03.Contoso.com", realm="SIP Communications Service", version=4
Content-Length: 2512
From: "Spurlock,Byron
To:
Call-ID: a0accf247e1a4ba68a0e8450ba96ff4a
CSeq: 1 SERVICE
Via: SIP/2.0/TLS :62437;received= ;ms-received-port=22112;ms-received-cid=9497D00

46. Conferencing 2 of 3 Content-Type: application/cccp+xml
- <response xmlns="urn:ietf:params:xml:ns:cccp"
mscp="
msci="
msci2="
cis="urn:ietf:params:xml:ns:conference-info-separator"
requestId=" "
C3PVersion="1"
code="success">

47. Conferencing 3 of 3
- <getConferencingCapabilities capability-version="0">
+ <mcu-types>
+ <pstn-bridging>
<conference-key-optional>true</conference-key-optional>
<anonymous-scheduling>true</anonymous-scheduling>
<default-admission-policy>anonymous</default-admission-policy>
<separator/>
<schedule-locked>true</schedule-locked>
<autopromote-allowed> </autopromote-allowed>
<default-autopromote>32768</default-autopromote>
<pstn-lobby-bypass-allowed>true</pstn-lobby-bypass-allowed>
<static-meeting-limit>1</static-meeting-limit>
<default-meeting-static>true</default-meeting-static>
<recording-allowed>false</recording-allowed>
<externaluser-recording-allowed>false</externaluser-recording-allowed>
<schedule-key-optional>true</schedule-key-optional>
<default-entry-exit-announcements>false</default-entry-exit-announcements>
- </getConferencingCapabilities>
</response>

48. Peak Time - Conferencing
<InboundStream Id="">
<Network><Jitter><InterArrival>1</InterArrival><InterArrivalMax>5</InterArrivalMax></Jitter>
<PacketLoss><LossRate> </LossRate><LossRateMax> </LossRateMax></PacketLoss>
<NoiseLevel>7167</NoiseLevel>
<QualityEstimates><Audio><RecvListenMOS> </RecvListenMOS>
<RecvListenMOSMin> </RecvListenMOSMin>
<NetworkMOS><OverallAvg> </OverallAvg><OverallMin> </OverallMin>
<DegradationAvg> </DegradationAvg>
<DegradationMax> </DegradationMax>
<DegradationJitterAvg> </DegradationJitterAvg>
<DegradationPacketLossAvg> </DegradationPacketLossAvg>
</NetworkMOS></Audio></QualityEstimates></InboundStream>

49. Off Peak Time - Conferencing
<InboundStream Id="">
<Network><Jitter><InterArrival>2</InterArrival><InterArrivalMax>8</InterArrivalMax></Jitter>
<PacketLoss><LossRate> </LossRate><LossRateMax> </LossRateMax></PacketLoss>
<NoiseLevel>26</NoiseLevel>
<QualityEstimates><Audio><RecvListenMOS> </RecvListenMOS>
<RecvListenMOSMin> </RecvListenMOSMin>
<NetworkMOS><OverallAvg> </OverallAvg>
<OverallMin> </OverallMin>
<DegradationAvg> </DegradationAvg>
<DegradationMax> </DegradationMax>
<DegradationJitterAvg> </DegradationJitterAvg><DegradationPacketLossAvg> </DegradationPacketLossAvg></NetworkMOS></Audio></QualityEstimates></InboundStream>

50. Scenario – Remote User Enterprise Voice

51. Snooper Trace – External Call

52. Enterprise Call – Snooper Trace
02/17/2014|14:23: E50:1590 INFO :: Data Received :5061 (To Local Address: :63179) 785 bytes:
02/17/2014|14:23: E50:1590 INFO ::
SIP/ Progress Report
Authentication-Info: TLS-DSK qop="auth", opaque="B ", srand="6F7D598E", snum="61", rspauth="b8e909e2f2bf0e21688c65c3bd47dfa6c7feb9b5", targetname=“Server03.Contoso.com", realm="SIP Communications Service", version=4
Content-Length: 0
Via: SIP/2.0/TLS :63179;ms-received-port=63179;ms-received-cid=30364E00
From: "Spurlock,Byron
To:
Call-ID: 6f69ca6598d343f3a039e68336ed55e6
CSeq: 1 INVITE
ms-diagnostics: 12006;reason="Trying next hop";source=“Server03.Contoso.com";PhoneUsage="Default Usage";PhoneRoute="External Calling";Gateway=" ";appName="OutboundRouting"
Server: OutboundRouting/

53. Remote User Enterprise Voice 1/4
PerfMon Counter SetsMax-Forwards: 70
From:
To:
Call-ID: b611ecca854b47c78b82aade563ef0d0
CSeq: 1 INVITE
Contact: <sip:
Content-Disposition: session; handling=optional; ms-proxy-2007fallback
v=0
o=- 0 0 IN IP
s=session
c=IN IP
b=CT:99980
t=0 0
m=audio RTP/AVP

54. Remote User Enterprise Voice – 2/4
a=candidate:RVe1AuhxobPEwFDgYqBzJ8nl5vntofS4rnotr5E8Z1U 1 p6ws7wYJioXkgVwF0sQzyw UDP
a=candidate:RVe1AuhxobPEwFDgYqBzJ8nl5vntofS4rnotr5E8Z1U 2 p6ws7wYJioXkgVwF0sQzyw UDP
a=candidate:kmclxGgIOHZ5uHpiwod6Paa7GuZhvObH9645kR57fJw 1 vHMsvL8TfBDYplWUcT1Iaw TCP
a=candidate:kmclxGgIOHZ5uHpiwod6Paa7GuZhvObH9645kR57fJw 2 vHMsvL8TfBDYplWUcT1Iaw TCP
a=candidate:ARSbz17KVDCKJsVk1FEI8yds49P7hdS7Pz7unidpn+0 1 U8jWmquvW+usL6V4dRpPFw UDP
a=candidate:ARSbz17KVDCKJsVk1FEI8yds49P7hdS7Pz7unidpn+0 2 U8jWmquvW+usL6V4dRpPFw UDP
a=candidate:hX1xn5LNhrXdUYZeJBi0TMahMVdn0YhYoO4xSgJIgSc 1 n3WhQS9pjzIdzKnSwUe2eQ TCP
a=candidate:hX1xn5LNhrXdUYZeJBi0TMahMVdn0YhYoO4xSgJIgSc 2 n3WhQS9pjzIdzKnSwUe2eQ TCP
a=candidate:FCn6Kmwij+Fzz87HpJ27MqlofJLD2iQwjO6pK+vKvd8 1 6MH8o37XC6WebAwkJ/zqmw UDP
a=candidate:FCn6Kmwij+Fzz87HpJ27MqlofJLD2iQwjO6pK+vKvd8 2 6MH8o37XC6WebAwkJ/zqmw UDP

55. Remote User Enterprise Voice – 3/4
a=cryptoscale:1 client AES_CM_128_HMAC_SHA1_80 inline:LdrtV/jRXmdUtT4B7q4wf0H2nnoULlwIYA3Pjesw|2^31|1:1
a=crypto:2 AES_CM_128_HMAC_SHA1_80 inline:Ov/D89GRsNLnGhLvmzKHBeZd4OgZaqaTsiGpGfFC|2^31|1:1
a=crypto:3 AES_CM_128_HMAC_SHA1_80 inline:EWaGm7ejfZREz2lh678C3N4EGMj7lMeWx0AFQEYA|2^31
a=maxptime:200
a=rtcp:58970
a=rtpmap:114 x-msrta/16000
a=fmtp:114 bitrate=29000
a=rtpmap:9 G722/8000
a=rtpmap:112 G7221/16000
a=fmtp:112 bitrate=24000
a=rtpmap:111 SIREN/16000
a=fmtp:111 bitrate=16000
a=rtpmap:0 PCMU/8000
a=rtpmap:8 PCMA/8000

56. Remote User Enterprise Voice – 4/4
02/09/2011|09:29: F8:14CC INFO :: Data Received :443 (To Local Address: :49383) 824 bytes:
02/09/2011|09:29: F8:14CC INFO :: SIP/ Progress Report
ms-user-logon-data: RemoteUser
Authentication-Info: TLS-DSK qop="auth", opaque="A4F8937E", srand="AB7AAF72", snum="639", rspauth="84d3431ade0f862db ffc6b95b845d5c67", targetname="frontendfqdn.contoso.com", realm="SIP Communications Service", version=4
Content-Length: 0
Via: SIP/2.0/TLS :49383;received= ;ms-received-port=49383;ms-received-cid=40C0A00
From:
To:
Call-ID: b611ecca854b47c78b82aade563ef0d0
CSeq: 1 INVITE
ms-diagnostics: 12006;reason="Trying next hop";source="mediationfqdn.contoso.com";PhoneUsage="Local";PhoneRoute="ContosoAll";Gateway=" ";appName="OutboundRouting"
Server: OutboundRouting/
Identifies route taken

57. Monitoring Reports

58. Monitoring Components
Lync Server 2013 Monitoring Server role
Define deployment using Topology Builder
Run Lync Server deployment tool using the configuration information defined by Topology Builder
Monitoring Server databases
Built on Microsoft SQL Server® database software
Microsoft SQL Server 2008 R2 Enterprise Edition
Microsoft SQL Server 2008 R2 Standard Edition
Microsoft SQL Server 2012 Enterprise Edition
Microsoft SQL Server 2012 Standard Edition
SQL Server Reporting Services
Required in order to deploy Monitoring Server Reports
Technically optional to deploy……but not really.  58

59. Enabling Monitoring
Unified data collection agents are automatically installed and activated on each Front End server. We do not need to configure a server to act as the Monitoring server. Each Front End server already functions as a Monitoring server. We need to install and configure a database to act as the backend data store for monitoring data 59

60. Monitoring Server Reports
Optional for Lync Server 2013
Contains out-of-the-box reports
Usage, call diagnostic information, and media quality information, based on CDR/CER and QoE data stored in the CDR and QoE databases
Reports generated with SQL Server Reporting Service 60

61. Sample Monitoring Report61

62. Sample Monitoring Report
What does this tell us? 62

63. Synthetic Transactions

64. Health Configuration Management Packs Synthetic Transactions
Used with System Center Operations Manager (SCOM)
Component and User Management Pack (Event logs, PerfMon Counters, CDR/QoE data)
Active Monitoring Management Pack (uses Synthetic Transactions)
Synthetic Transactions
Used to verify that users are able to complete common tasks.
Provide Rich Logging for greater detail

65. Synthetic Transactions
Test-CSOutboundCall – Validates policies, signaling and media to the PSTN
TestCSPSTNPeertoPeerCall – Establishes call between two Lync users over PSTN
Test-CsP2PAV (P2PAV) – Confirms that users are able to make peer to peer calls (signal only)
Test-CsAVConference (AvConference) – Test users are able to create an AV conference call
Test-CsAVEdgeConnectivity (AVEdgeConnectivity) – Test edge server is able to accept connections for peer to peer calls
Test-CsExumConnectivity (ExumConnectivity) – Confirms users are able to connect to Unified Messaging

66. Q&A

67. Appendix

68. Performance Counters

69. PerfMon Counters Reference
Lync Conference 2013
4/19/2017
PerfMon Counters Reference
\LS:MediationServer - Outbound Calls(*)\- Current
\LS:MediationServer - Outbound Calls(*)\- Total established
\LS:MediationServer - Outbound Calls(*)\- Total attempts
\LS:MediationServer - Outbound Calls(*)\- Total rejected due to load
\LS:MediationServer - Outbound Calls(*)\- Total INVITEs sent to gateway
\LS:MediationServer - Outbound Calls(*)\- Active priority calls
\LS:MediationServer - Outbound Calls(*)\- Active media bypass calls
\LS:MediationServer - Outbound Calls(*)\- Total outbound media bypass calls
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

70. PerfMon Counters Reference
\LS:MediationServer - Inbound Calls(*)\- Current
\LS:MediationServer - Inbound Calls(*)\- Total established
\LS:MediationServer - Inbound Calls(*)\- Total attempts
\LS:MediationServer - Inbound Calls(*)\- Total rejected due to load
\LS:MediationServer - Inbound Calls(*)\- Total INVITEs sent to proxy
\LS:MediationServer - Inbound Calls(*)\- Active priority calls
\LS:MediationServer - Inbound Calls(*)\- Active media bypass calls
\LS:MediationServer - Inbound Calls(*)\- Total inbound media bypass calls

71. PerfMon Counters Reference
Lync Conference 2013
4/19/2017
PerfMon Counters Reference
\LS:MediationServer - Media Relay\- Candidates Missing
\LS:MediationServer - Media Relay\- Media Connectivity Check Failure
\LS:MediationServer - Health Indices\- Load Call Failure Index
\LS:MediationServer - Global Counters\- Current audio channels with PSM quality reporting
\LS:MediationServer - Global Counters\- Total failed calls caused by unexpected interaction from the Proxy
\LS:MediationServer - Global Counters\- Current number of ports opened on the gateway side
\LS:MediationServer - Global Counters\- Total number of timer timeouts that are exceeding the predefined threshold
\LS:MediationServer - Global Per Gateway Counters(*)\- Total failed calls caused by unexpected interaction from a gateway
© 2013 Microsoft Corporation. All rights reserved. Microsoft, Windows, and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.

72. PerfMon Counters Reference
\LS:AVMCU - Informational\AVMCU - Total MRAS Request
\LS:AVMCU - Informational\AVMCU - Total MRAS Request error
\LS:AVMCU - Informational\AVMCU - Total MRAS Responses Received
\LS:AVMCU - Informational\AVMCU - Total MRAS Requests Rejected
\LS:AVMCU - Informational\AVMCU - Total MRAS Timeout Exceptions
\LS:AVMCU - Informational\AVMCU - Total MRAS Failure Response Exceptions
\LS:AVMCU - Informational\AVMCU - Total MRAS Real Time Exceptions
\LS:AVMCU - Informational\AVMCU - Total MRAS Generic Exceptions
\LS:CAA - Planning\CAA - Total incomplete calls
\LS:CAA - Planning\CAA - Total Calls Received
\LS:CAA - Planning\CAA - Current calls
\LS:CAA - Planning\CAA - Total calls successfully transferred to the conference
\LS:CAA - Planning\CAA - Total calls failed to transfer to the conference

73. 4/19/2017 4:42 PM
© 2014 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.
© 2010 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.
The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS PRESENTATION.