Name: Byron SpurlockTitle: Lync Technical ArchitectEmail: Byrons@Quadrantechnologies.comTwitter: @ByronSpurlock

Troubleshooting Lync 2013 with Enterprise Voice

VOICE304

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

Agenda

Troubleshooting Approach

Common QuestionsFrom UsersWhat 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 AdministratorsHow do I read these reports?How can I determine what the value of X in a particular report means?Where do I start?

Troubleshooting Approach

NetworkWANNetwork Router \ SwitchBandwidthPoliciesWired \ Wireless

ServerLack of Server ResourcesMis-Configuration

ClientApplication SettingsConfigurationInternet Connection

Failed Calls

Dropped Calls

One Way

AudioEchoNoise

Low Volume

Delayed Audio

Broken Up

Audio

Distorted Audio

Understanding The Challenges

Network Core Performance

Call Reliability

Audio Quality

Voice Quality Issues

Gateways Devices

Key Architecture FlowsKnow the base foundation

Firewall: Edge

Conferencing Flow

Focus

Conferencing Client

CC

CP/S

IPWeb Conf

Server

IM Conf Server

AV Conf Server

C3P/HTTP

SIMPLE/SIP

(S)RTPPSOM

Focus Factory

SQL Server® Backend

Scheduling

Client

CC

CP/S

IP

SQL

SQL

Conferencing Server FactoryC3P/

HTTP

1

2

3

4

5

6

7

App Sharing Conf Server

RDP/RTP

11

Voice Routing

Announcement orCall Park Application

1. Vacant Number Range

2. Call Park Orbit Range

DialingBehaviors

Routing &Authorization

Normalization RuleNormalization Rule

Normalization Rule

Dial Plan

PSTN UsagePSTN Usage

PSTN Usage

3. Voice Policy Routes

Route

RouteRoute

Route

External Endpoint Receives Call UC Endpoint Receives Call

User Initiates Call

User=phone

Yes

Global?No

SIP URI

Match

Reverse Number Lookup

No match

Mediation Server andTrunk Configuration

Gateway / IP-PBX / SIP Trunk Inbound Routing

404: No matching

rule

403: No route found

Yes

Emer.Call?

No

PSTN Usage

Location Policy

Call Park Orbit Range

User habits

Gateway selection (or not)

PSTN accommodations

Lync 2013 Poster

Tools

• Voice Routing Test Tool• ICE Warning Flag Decoder • PreCall Diagnostics • Central Logging Service• Audio Test Tool

Tools

Voice Routing Test Tool

Voice Routing TestingVoice 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

Demo

Voice Routing Test Tool

ICE Warning Flag Decoder

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.

http://gallery.technet.microsoft.com/office/ICE-Warning-Flag-Decoder-97058ef3

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

Demo

ICE Warning Flag Decoder

PreCall Diagnostics

PreCall Diagnostics ToolThe 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.

http://windowsitpro.com/lync/lync-precall-diagnostics-tool

Demo

PreCall Diagnostic Tool

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 centrallyStart, stop, and flush trace logging for any/all machines in a deployment from one placeStart/stop logging based on scenariosSee what logging is turned on per pool/machine for the entire deploymentSearch trace logs based on specified parameters from a centralized place

Centralized Logging Service (CLS)

26

CLSAgentRuns on every Lync ServerControls logging based on commands from CLSControllerManages log files to ensure drive space is not consumed, moves old logs to fileshare

CLSControllerSends Start, Stop, Flush, and Search commands to all the CLSAgents in the deploymentAggregates search results from CLSAgentsAvailable on every Lync Server in “C:\Program Files\Common Files\Microsoft Lync Server 2013\ClsAgent”

CLS Architecture

27

CLSControllerFE

CLSAgent

FE

CLSAgent

FE

CLSAgent

Start, Stop, Search commands

Start, Stop, Search commands

Start, Stop, Search comm

ands

Search results

Search results

Search results

Logging is based on scenariosBuilt in scenarios specify a group of components and log levels to be started and stopped together

Scenarios

28

AddressBookAlwaysOnApplicationSharingAudioVideoConferencingIssueCAACLSCPSDeviceUpdate

HostedMigrationHybridVoiceIMAndPresenceIncomingAndOutgoingCallLILRLegacyLILRLYSSLYSSAndUCSMediaConnectivity

MeetingJoinMonitoringAndArchivingRGSSPUserReplicatorVoiceMailWACXMPP

Components Logged by Scenarios

Scenario details can be discovered$scenario=Get-CsClsScenario global/IncomingAndOutgoingCallforeach ($sc in $scenario.provider) { $sc.name }

Get-CsClsScenario global/<ScenarioName> |Select -ExpandProperty Provider |Format-Table Name,Level,Flags -a

For scenario:IncomingAndOutgoingCall

29

Component Name Level

MediationServer Info

S4 Info

Sipstack Info

TranslationApplication Info

OutboundRouting Info

InboundRouting Info

UserServices Verbose

What is it?The special scenario “AlwaysOn” can be on all the time. It logs INFO level for many common componentsWhen an issue occurs there may be enough info in the AlwaysOn component logs to debug the issueThis avoids having to turn on logging and repro the issue, which was always required in Lync Server 2010If 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 loggingAt 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.

The “AlwaysOn” Scenario

30

ExamplesTurn on a logging scenarioStart-CsClsLogging –Scenario AlwaysOn –Pools pool.contoso.comStart-CsClsLogging –Scenario IncomingAndOutgoingCall -Pools pool.contoso.com

Run a SearchSearch-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

.\ClsController (COMMAND) [(OPTIONS)] [(SCOPE)]

Using ClsController

32

COMMAND 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

ClsController Options

33

OPTION 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

Demo

Central Logging Service

Audio Test Service

Leveraged for client side

testing of Audio capabilities

User leaves audio recording

Snooper results

Audio Test Service

36

Audio Test Service Logs 1of 5<02/17/2014|12:38:03.395 E50:1590 INFO :: Data Received -143.111.10.10:443 (To Local Address: 10.10.10.10:62437) 3844 bytes:02/17/2014|12:38:03.395 E50:1590 INFO :: SIP/2.0 200 OKms-user-logon-data: RemoteUserVia: SIP/2.0/TLS 10.9.174.84:62437;received=143.111.4.59;ms-received-port=22112;ms-received-cid=9497D00Authentication-Info: TLS-DSK qop="auth", opaque="FDBCBDDB", srand="BA4FA844", snum="27", rspauth="a11a7798ac1503a43f12d024918da48ed4d6d589", targetname=“Server1.Contoso.com", realm="SIP Communications Service", version=4FROM: "Spurlock,Byron O"<sip:bospurlock@Contoso.com>;tag=cefd4eaf92;epid=195459a138TO: "Audio Test Service"<sip:POOL01.Contoso.com@Contoso.com;gruu;opaque=srvr:Microsoft.Rtc.Applications.TestBot:DzPD-jQUjVOm4GG2tRYUFQAA>;tag=513a61a213;epid=2D2DEC799CCSEQ: 1 INVITE

Audio Test Service Logs 2 of 5CALL-ID: 9af1f616009d47e78bdf1923520e21f0RECORD-ROUTE: <sip:POOL01.Contoso.com:5061;transport=tls;ms-fe=Server03.Contoso.com;opaque=state:F;lr;received=10.111.218.62;ms-received-cid=90AD602>RECORD-ROUTE: <sip:lync.Contoso.com:443;transport=tls;opaque=state:Ci.R9497d00;lr;ms-route-sig=ctpAEzburC4SrvL25Q37iYSgblGihzwCn8Wrk7wAQHG3VVGC9cs_yTzAAA>CONTACT: <sip:ServerC01.Contoso.com@Contoso.com;gruu;opaque=srvr:Microsoft.Rtc.Applications.TestBot:58SPAWUUnFmqFdt1p8ce5AAA>;automata;actor="attendant";text;audio;video;imageCONTENT-LENGTH: 1521PRIORITY: NormalSUPPORTED: ReplacesSUPPORTED: ms-dialog-route-set-updateSUPPORTED: gruu-10SUPPORTED: timerSUPPORTED: 100relCONTENT-TYPE: application/sdp

Audio Test Service Logs 3 of 5ALLOW: ACKALLOW: CANCEL,BYE,INVITE,MESSAGE,INFO,SERVICE,OPTIONS,BENOTIFY,NOTIFY,PRACK,UPDATEP-ASSERTED-IDENTITY: "Audio Test Service"<sip:RtcApplication-9addde3a-0d9a-45cb-b4bb-0efcd9401949@Contoso.com>SERVER: RTCC/4.0.0.0 ATS/1.0.100SUBJECT: Test CallContent-ID: 6f84e04a-653b-41e1-9762-0405aefb3dfbMs-Conversation-ID: Ac8sD2LxJprQRZ0NRsG8WDrlpb/mWA==ms-endpoint-location-data: NetworkScope;ms-media-location-type=Intranetms-diagnostics: 24100;Component="RTCC/4.0.0.0_ATS/1.0.100";Reason="General diagnostic information.";CalleeICEWarningFlags="Audio:ICEWarn=0x400000,LocalSite=143.111.4.11:39991,LocalMR=143.111.4.188:50701,RemoteSite=143.111.4.99:39469,RemoteMR=143.111.4.188:58201,PortRange=49152:57500,LocalMRTCPPort=50701,RemoteMRTCPPort=58201,LocalLocation=2,RemoteLocation=1,FederationType=0";Source="dcpwplync01.Contoso.com"

Audio Test Service Logs 4 of 5Session-Expires: 1800;refresher=uasMin-SE: 90v=0o=- 79 0 IN IP4 10.111.88.0s=sessionc=IN IP4 10.111.88.0b=CT:2000000t=0 0m=audio 52238 RTP/SAVP 112 111 0 8 116 13 118 97 101c=IN IP4 10.111.74.32a=rtcp:52239a=ice-ufrag:Pn74a=ice-pwd:iw3stqmcpZnFy+x5o9uiKfZ2

Audio Test Service Logs 5 of 5a=candidate:1 1 UDP 2130706431 10.111.25.44 52238 typ hosta=candidate:1 2 UDP 2130705918 10.111.25.44 52239 typ hosta=candidate:2 1 tcp-pass 6555135 143.111.6.188 50701 typ relay raddr 143.111.6.22 rport 39991a=candidate:2 2 tcp-pass 6555134 143.111.6.188 50701 typ relay raddr 143.111.6.22 rport 39991a=candidate:3 1 UDP 16647679 143.115.7.169 50836 typ relay raddr 10.111.88..0 rport 54286a=candidate:3 2 UDP 16647678 143.115.7.169 58895 typ relay raddr 10.111.88.0 rport 54287a=candidate:4 1 tcp-act 7076863 143.115.7.99 50701 typ relay raddr 143.111.6.22 rport 39991a=candidate:4 2 tcp-act 7076350 143.111.4.199 50701 typ relay raddr 143.111.6.22 rport 39991a=candidate:5 1 tcp-act 1684797951 143.111.6.22 39991 typ srflx raddr 10.111.88.0 rport 50515a=candidate:5 2 tcp-act 1684797438 143.111.6.22 39991 typ srflx raddr 10.111.88.0 rport 50515a=label:main-audio

Common Scenarios

• Audio Video Conferencing• Remote User – Enterprise Voice• Many Many More…

Common Scenarios

Scenario – Audio Video Conferencing

Conferencing 1 of 3Authentication-Info: TLS-DSK qop="auth", opaque="FDBCBDDB", srand="0FBCE3F4", snum="7", rspauth="125a0197b19040c4eecc0e69bbdbb468afc8c23e", targetname="DCPWPLYNC03.Contoso.com", realm="SIP Communications Service", version=4Content-Length: 2512From: "Spurlock,Byron O"<sip:bospurlock@Contoso.com>;tag=90fd761f75;epid=195459a138To: <sip:bospurlock@Contoso.com;gruu;opaque=app:conf:focusfactory>;tag=22AB9C2A76AF4CA3C5503A7A325362BBCall-ID: a0accf247e1a4ba68a0e8450ba96ff4aCSeq: 1 SERVICEVia: SIP/2.0/TLS 10.9.174.84:62437;received=143.111.4.59;ms-received-port=22112;ms-received-cid=9497D00

Conferencing 2 of 3Content-Type: application/cccp+xml- <response xmlns="urn:ietf:params:xml:ns:cccp" mscp="http://schemas.microsoft.com/rtc/2005/08/cccpextensions" msci="http://schemas.microsoft.com/rtc/2005/08/confinfoextensions" msci2="http://schemas.microsoft.com/rtc/2008/12/confinfoextensions" cis="urn:ietf:params:xml:ns:conference-info-separator" requestId="87495544" C3PVersion="1" from="sip:bospurlock@Contoso.com;gruu;opaque=app:conf:focusfactory" to="sip:bospurlock@Contoso.com" code="success">

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>2147516416</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>

Peak Time - Conferencing<InboundStream Id=""><Network><Jitter><InterArrival>1</InterArrival><InterArrivalMax>5</InterArrivalMax></Jitter><PacketLoss><LossRate>0.470875</LossRate><LossRateMax>0.762646</LossRateMax></PacketLoss><NoiseLevel>7167</NoiseLevel><QualityEstimates><Audio><RecvListenMOS>2.010000</RecvListenMOS><RecvListenMOSMin>1.000000</RecvListenMOSMin><NetworkMOS><OverallAvg>1.970000</OverallAvg><OverallMin>1.500000</OverallMin><DegradationAvg>0.970000</DegradationAvg><DegradationMax>1.450000</DegradationMax><DegradationJitterAvg>0.000000</DegradationJitterAvg><DegradationPacketLossAvg>0.990000</DegradationPacketLossAvg></NetworkMOS></Audio></QualityEstimates></InboundStream>

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

Scenario – Remote User Enterprise Voice

Snooper Trace – External Call

Enterprise Call – Snooper Trace02/17/2014|14:23:06.038 E50:1590 INFO :: Data Received -10.111.74.68:5061 (To Local Address: 172.18.33.47:63179) 785 bytes:02/17/2014|14:23:06.038 E50:1590 INFO :: SIP/2.0 101 Progress ReportAuthentication-Info: TLS-DSK qop="auth", opaque="B9541370", srand="6F7D598E", snum="61", rspauth="b8e909e2f2bf0e21688c65c3bd47dfa6c7feb9b5", targetname=“Server03.Contoso.com", realm="SIP Communications Service", version=4Content-Length: 0Via: SIP/2.0/TLS 172.18.33.47:63179;ms-received-port=63179;ms-received-cid=30364E00From: "Spurlock,Byron O"<sip:bospurlock@Contoso.com>;tag=059860159b;epid=195459a138To: <sip:+17134941831@Contoso.com;user=phone>Call-ID: 6f69ca6598d343f3a039e68336ed55e6CSeq: 1 INVITEms-diagnostics: 12006;reason="Trying next hop";source=“Server03.Contoso.com";PhoneUsage="Default Usage";PhoneRoute="External Calling";Gateway="10.111.121.64";appName="OutboundRouting"Server: OutboundRouting/4.0.0.0

Remote User Enterprise Voice 1/4PerfMon Counter SetsMax-Forwards: 70From: <sip:<userName>@contoso.com>;tag=38849ad51a;epid=92a17ee2ceTo: <sip:+12075550184@contoso.com;user=phone>Call-ID: b611ecca854b47c78b82aade563ef0d0CSeq: 1 INVITEContact: <sip: <userName>@contoso.com;opaque=user:epid:1dRPOJppUlG-Qszig4EXYgAA;gruu>Content-Disposition: session; handling=optional; ms-proxy-2007fallbackv=0o=- 0 0 IN IP4 208.115.110.145s=sessionc=IN IP4 208.115.110.145b=CT:99980t=0 0m=audio 56796 RTP/AVP 114 9 112 111 0 8 116 115 4 97 13 118 101

Remote User Enterprise Voice – 2/4a=candidate:RVe1AuhxobPEwFDgYqBzJ8nl5vntofS4rnotr5E8Z1U 1 p6ws7wYJioXkgVwF0sQzyw UDP 0.830 192.168.1.145 2002 a=candidate:RVe1AuhxobPEwFDgYqBzJ8nl5vntofS4rnotr5E8Z1U 2 p6ws7wYJioXkgVwF0sQzyw UDP 0.830 192.168.1.145 2003 a=candidate:kmclxGgIOHZ5uHpiwod6Paa7GuZhvObH9645kR57fJw 1 vHMsvL8TfBDYplWUcT1Iaw TCP 0.190 208.115.110.145 51100 a=candidate:kmclxGgIOHZ5uHpiwod6Paa7GuZhvObH9645kR57fJw 2 vHMsvL8TfBDYplWUcT1Iaw TCP 0.190 208.115.110.145 51100 a=candidate:ARSbz17KVDCKJsVk1FEI8yds49P7hdS7Pz7unidpn+0 1 U8jWmquvW+usL6V4dRpPFw UDP 0.490 208.115.110.145 56796 a=candidate:ARSbz17KVDCKJsVk1FEI8yds49P7hdS7Pz7unidpn+0 2 U8jWmquvW+usL6V4dRpPFw UDP 0.490 208.115.110.145 58970 a=candidate:hX1xn5LNhrXdUYZeJBi0TMahMVdn0YhYoO4xSgJIgSc 1 n3WhQS9pjzIdzKnSwUe2eQ TCP 0.250 69.193.68.231 19114 a=candidate:hX1xn5LNhrXdUYZeJBi0TMahMVdn0YhYoO4xSgJIgSc 2 n3WhQS9pjzIdzKnSwUe2eQ TCP 0.250 69.193.68.231 19114 a=candidate:FCn6Kmwij+Fzz87HpJ27MqlofJLD2iQwjO6pK+vKvd8 1 6MH8o37XC6WebAwkJ/zqmw UDP 0.550 69.193.68.231 20176 a=candidate:FCn6Kmwij+Fzz87HpJ27MqlofJLD2iQwjO6pK+vKvd8 2 6MH8o37XC6WebAwkJ/zqmw UDP 0.550 69.193.68.231 20177

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

Remote User Enterprise Voice – 4/402/09/2011|09:29:53.944 17F8:14CC INFO :: Data Received - 208.115.110.143:443 (To Local Address: 192.168.1.138:49383) 824 bytes:02/09/2011|09:29:53.944 17F8:14CC INFO :: SIP/2.0 101 Progress Reportms-user-logon-data: RemoteUserAuthentication-Info: TLS-DSK qop="auth", opaque="A4F8937E", srand="AB7AAF72", snum="639", rspauth="84d3431ade0f862db4856530ffc6b95b845d5c67", targetname="frontendfqdn.contoso.com", realm="SIP Communications Service", version=4Content-Length: 0Via: SIP/2.0/TLS 192.168.1.138:49383;received=69.193.68.231;ms-received-port=49383;ms-received-cid=40C0A00From: "bob"<sip:bob@contoso.com>;tag=38849ad51a;epid=92a17ee2ceTo: <sip:+12075550184@contoso.com;user=phone>Call-ID: b611ecca854b47c78b82aade563ef0d0CSeq: 1 INVITEms-diagnostics: 12006;reason="Trying next hop";source="mediationfqdn.contoso.com";PhoneUsage="Local";PhoneRoute="ContosoAll";Gateway="192.168.5.20";appName="OutboundRouting"Server: OutboundRouting/4.0.0.0

Identifies route taken

Monitoring Reports

Lync Server 2013 Monitoring Server roleDefine deployment using Topology BuilderRun Lync Server deployment tool using the configuration information defined by Topology Builder

Monitoring Server databasesBuilt on Microsoft SQL Server® database software

Microsoft SQL Server 2008 R2 Enterprise EditionMicrosoft SQL Server 2008 R2 Standard EditionMicrosoft SQL Server 2012 Enterprise EditionMicrosoft SQL Server 2012 Standard Edition

SQL Server Reporting ServicesRequired in order to deploy Monitoring Server Reports

Technically optional to deploy……but not really.

Monitoring Components

58

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

Enabling Monitoring

59

Optional for Lync Server 2013Contains 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

Monitoring Server Reports

60

Sample Monitoring Report

61

Sample Monitoring Report

62

What does

this tell us?

Synthetic Transactions

Health ConfigurationManagement PacksUsed 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 TransactionsUsed to verify that users are able to complete common tasks.Provide Rich Logging for greater detail

Synthetic TransactionsTest-CSOutboundCall – Validates policies, signaling and media to the PSTNTestCSPSTNPeertoPeerCall – Establishes call between two Lync users over PSTNTest-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 callTest-CsAVEdgeConnectivity (AVEdgeConnectivity) – Test edge server is able to accept connections for peer to peer callsTest-CsExumConnectivity (ExumConnectivity) – Confirms users are able to connect to Unified Messaging

Q&A

Appendix

Performance Counters

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

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

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

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

© 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.