1、#CiscoLive#CiscoLiveTim Kratzke(Technical Leader)BRKCOL-3016Troubleshooting Video Endpoint Third Party Meeting Integrations 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveEnter your personal notes hereCisco Webex App 3Questions?Use Cisco Webex App to chat with the speaker

2、 after the sessionFind this session in the Cisco Live Mobile AppClick“Join the Discussion”Install the Webex App or go directly to the Webex spaceEnter messages/questions in the Webex spaceHowWebex spaces will be moderated by the speaker until June 9,2023.12343https:/ 2023 Cisco and/or its affiliates

3、.All rights reserved.Cisco PublicBRKCOL-3016Agenda 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public3rdParty Meeting OverviewLog Collection OverviewTroubleshooting WebRTCTroubleshooting MTRConclusionBRKCOL-30164 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoL

4、ive3rdParty Meetings,Where to Start?What service is being used?How does it connect?What features are available?5BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveGoogle MeetWebRTC basedRelies on the built in web browser capabilities6BRKCOL-3016WebRTCMedia 2023 Ci

5、sco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMicrosoft TeamsThree different options for interoperability with Microsoft Teams1.WebRTC2.VIMT/CVI3.Microsoft Teams Rooms(MTR)Options 1 and 2 work natively while MTR requires activating the device with Microsoft7BRKCOL-3016 2023 Cis

6、co and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMicrosoft TeamsWebRTC8BRKCOL-3016VIMTWebRTCWebex/SIPMSFTMediaMediaMediaBRKCOL-2058:Troubleshooting the Cisco Webex Video Integration for Microsoft Teams 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveZoomS

7、tandard SIP call to ZoomCRCVideo endpoint dials traditionally using SIP or WebexIn call controls implemented using underlying DTMF commands9BRKCOL-3016WebexSIPSIPSIPSIPSIPMediaMediaMediaMediaMediaBRKCOL-3004:Advanced Troubleshooting of Cisco Collaboration Video EndpointsAgenda 2023 Cisco and/or its

8、affiliates.All rights reserved.Cisco Public3rdParty Meeting OverviewLog Collection and OverviewTroubleshooting WebRTCTroubleshooting MTRConclusionBRKCOL-301610 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveLog CollectionBRKCOL-301611Devices Local Device Controls 2023 Cis

9、co and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveLog CollectionIssues and Diagnostics System LogsBRKCOL-301612 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveLog CollectionDownload LogsStart/Stop Extended LoggingBrowse Current FilesBRKCOL-301613 2023 Cis

10、co and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveExtended LoggingExtended LoggingEnables additional debugsLasts 10 minutesInclude Limited Packet CaptureStarts pcap which will filter out RTP mediaLasts 10 minutesInclude Full Packet CaptureCaptures all traffic including RTPLasts 3 mi

11、nutesInclude Rolling Packet CapturePcaps will rotate based on file sizeNo time limitBRKCOL-301614 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveCloud Log CollectionSend logs from deviceRequest logs from control hubAutomatic call logsCall-log contentsxconfig and xstatusca

12、llhistoryall.log and main.logBRKCOL-301615 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveLog Bundle Format/var/log/eventlogBRKCOL-301616Agenda 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public3rdParty Meeting OverviewLog Collection OverviewTroubleshooting

13、 WebRTCTroubleshooting MTRConclusionBRKCOL-301617 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveWhat is WebRTC?HTML 5 specifications built to operate within modern web browsers and allow real-time communication between peersSet of javascript APIs to allow interaction wit

14、h hardware such as cameras and microphonesEliminates the need for 3rdparty plugins to use applicationsApplications are responsible for implementing the WebRTC standard to fit their specific needs18BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveRoomOS and WebEn

15、gineWebEngine is the RoomOS browser framework based off of ChromiumWebRTC applications run within the WebEngine and utilize its built in supportLook and feel of these applications can vary significantlyMedia handling and limitations depending on the service handling the calls19BRKCOL-3016 2023 Cisco

16、 and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveThird Party Meeting SettingsMust be enabled in Control Hub under devices-settingsFor WebRTC based calls,WebEngine must be enabled on the deviceFor devices connected via Webex edge,”Allow control hub to manage configuration”must also be

17、 enabled under device settings20BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveThird Party Meeting SettingsJoin shortcut icons can also be enabled/disabled on the device itself under UserInterface-Features21BRKCOL-3016 2023 Cisco and/or its affiliates.All righ

18、ts reserved.Cisco Public#CiscoLiveSend Logs to ProviderLogs can be uploaded directly to control hub and sent to the WebRTC provider via the device diagnostics menuCisco TAC does not have access to the WebRTC specific logs and the files that are collected are controlled by the meeting platform22BRKCO

19、L-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveSend Logs to Provider23BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveLog Troubleshooting OverviewLog bundles can provide useful information to troubleshoot WebRTC calls dependin

20、g on when they are collectedScheduling issuesConnection problemsGeneral call infoMedia statistics and overview24BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveSchedulingWebRTC based calls can be joined ad-hoc or scheduled just as a standard SIP or Webex meetin

21、g to leverage One Button to Push(OBTP)The bookings.txt file provides valuable information on how the call has been scheduled and can be used for troubleshooting purposes25BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveScheduling(booking.txt)26BRKCOL-3016*r Boo

22、kingsListResult Booking 1 Title:Cisco Live Test.*r BookingsListResult Booking 1 Organizer FirstName:Tim Kratzke*r BookingsListResult Booking 1 Organizer LastName:*r BookingsListResult Booking 1 Organizer Email:*r BookingsListResult Booking 1 Organizer Id:42174db8-07c1-4027-a9a1-784cfb56a8fb*r Bookin

23、gsListResult Booking 1 Time StartTime:2023-04-18T17:30:00Z*r BookingsListResult Booking 1 Time StartTimeBuffer:300*r BookingsListResult Booking 1 Time EndTime:2023-04-18T18:30:00Z*r BookingsListResult Booking 1 Time EndTimeBuffer:0.*r BookingsListResult Booking 1 BookingStatus:OK*r BookingsListResul

24、t Booking 1 BookingStatusMessage:*r BookingsListResult Booking 1 MeetingPlatform:GoogleMeet*r BookingsListResult Booking 1 Cancellable:False*r BookingsListResult Booking 1 Webex Enabled:False.*r BookingsListResult Booking 1 Encryption:BestEffort*r BookingsListResult Booking 1 Recording:Disabled*r Bo

25、okingsListResult Booking 1 DialInfo Calls Call 1 Number:https:/ BookingsListResult Booking 1 DialInfo Calls Call 1 Protocol:WebRTC*r BookingsListResult Booking 1 DialInfo ConnectMode:OBTP 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveCall HistoryAfter a WebRTC call is en

26、ded,an entry is added to the callhistory.txt file with basic call informationNotably absent from this is any media statistics or information commonly found for SIP or Webex callsThis can provide a good overview of call connection information and times27BRKCOL-3016 2023 Cisco and/or its affiliates.Al

27、l rights reserved.Cisco Public#CiscoLiveCall History(callhistory.txt)28BRKCOL-3016*r CallHistoryGetResult Entry 0 CorrelationId:gzk-tvpj-xpe*r CallHistoryGetResult Entry 0 RemoteNumber:https:/ CallHistoryGetResult Entry 0 CallbackNumber:https:/ CallHistoryGetResult Entry 0 DisplayName:gzk-tvpj-xpe*r

28、 CallHistoryGetResult Entry 0 Direction:Outgoing*r CallHistoryGetResult Entry 0 Protocol:WebRTC*r CallHistoryGetResult Entry 0 CallRate:0*r CallHistoryGetResult Entry 0 CallType:Video*r CallHistoryGetResult Entry 0 VideoUsed:True*r CallHistoryGetResult Entry 0 StartTime:2023-04-17T17:13:01*r CallHis

29、toryGetResult Entry 0 StartTimeUTC:2023-04-17T21:13:01Z*r CallHistoryGetResult Entry 0 EndTime:2023-04-17T17:14:39*r CallHistoryGetResult Entry 0 EndTimeUTC:2023-04-17T21:14:39Z*r CallHistoryGetResult Entry 0 DisconnectCauseOrigin:Internal*r CallHistoryGetResult Entry 0 DisconnectCauseType:LocalDisc

30、onnect*r CallHistoryGetResult Entry 0 Video Incoming PacketLoss:N/A*r CallHistoryGetResult Entry 0 Video Incoming PacketLossPercent:0*r CallHistoryGetResult Entry 0 Video Incoming MaxJitter:0 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMedia TroubleshootingWhile call h

31、istory does not retain any media statistics,this info can be gathered by capturing logs while the call is in progressOverall media stats will be present in the xstatus.txt log output during a callThis can be used in conjunction with a packet capture to take a detailed look at media informationHow me

32、dia is handled depends on the application therefor can differ between vendor call solutions29BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMedia Troubleshooting(xstatus.txt)30BRKCOL-3016*s WebRTC MediaChannels Client Channel 8 Direction:Incoming*s WebRTC Medi

33、aChannels Client Channel 8 Id:RTCInboundRTPVideoStream_1369139291*s WebRTC MediaChannels Client Channel 8 Netstat BytesReceived:19478145*s WebRTC MediaChannels Client Channel 8 Netstat JitterBufferDelay:0*s WebRTC MediaChannels Client Channel 8 Netstat JitterBufferEmittedCount:0*s WebRTC MediaChanne

34、ls Client Channel 8 Netstat PacketsLost:0*s WebRTC MediaChannels Client Channel 8 Netstat PacketsReceived:17605*s WebRTC MediaChannels Client Channel 8 Transport RTCP Local IpAddress:64.99.194.235*s WebRTC MediaChannels Client Channel 8 Transport RTCP Local Port:53226*s WebRTC MediaChannels Client C

35、hannel 8 Transport RTCP Local Protocol:UDP*s WebRTC MediaChannels Client Channel 8 Transport RTCP Remote IpAddress:142.250.82.113*s WebRTC MediaChannels Client Channel 8 Transport RTCP Remote Port:3478*s WebRTC MediaChannels Client Channel 8 Transport RTCP Remote Protocol:UDP*s WebRTC MediaChannels

36、Client Channel 8 Type:Video*s WebRTC MediaChannels Client Channel 8 Video DecoderImplementation:ExternalDecoder*s WebRTC MediaChannels Client Channel 8 Video FrameHeight:720*s WebRTC MediaChannels Client Channel 8 Video FrameWidth:1280*s WebRTC MediaChannels Client Channel 8 Video FramesDecoded:1826

37、*s WebRTC MediaChannels Client Channel 8 Video FramesPerSecond:30*s WebRTC MediaChannels Client Channel 8 Video KeyFramesDecoded:1*s WebRTC MediaChannels Client Channel 8 Video Protocol:video/VP8 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMedia Troubleshooting(Web)31B

38、RKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLivePacket Captures32BRKCOL-3016Packet captures are located in the“run”directory of log bundlesIn instances where the pcap file is too large it will not be includedIn those cases the pcap can be downloaded manually fro

39、m the system logs page in the web interface 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLivePacket Captures33BRKCOL-3016Telephony RTP RTP Streams 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLivePacket Captures(RTP Stream Overview)34BRKCOL-3016Inb

40、ound MediaOutbound Media 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveLogging(xstatus.txt)35BRKCOL-3016*s WebRTC MediaChannels Client Channel 8 Direction:Incoming*s WebRTC MediaChannels Client Channel 8 Id:RTCInboundRTPVideoStream_1369139291*s WebRTC MediaChannels Clien

41、t Channel 8 Netstat BytesReceived:19478145*s WebRTC MediaChannels Client Channel 8 Netstat JitterBufferDelay:0*s WebRTC MediaChannels Client Channel 8 Netstat JitterBufferEmittedCount:0*s WebRTC MediaChannels Client Channel 8 Netstat PacketsLost:0*s WebRTC MediaChannels Client Channel 8 Netstat Pack

42、etsReceived:17605*s WebRTC MediaChannels Client Channel 8 Transport RTCP Local IpAddress:64.99.194.235*s WebRTC MediaChannels Client Channel 8 Transport RTCP Local Port:53226*s WebRTC MediaChannels Client Channel 8 Transport RTCP Local Protocol:UDP*s WebRTC MediaChannels Client Channel 8 Transport R

43、TCP Remote IpAddress:142.250.82.113*s WebRTC MediaChannels Client Channel 8 Transport RTCP Remote Port:3478*s WebRTC MediaChannels Client Channel 8 Transport RTCP Remote Protocol:UDP*s WebRTC MediaChannels Client Channel 8 Type:Video*s WebRTC MediaChannels Client Channel 8 Video DecoderImplementatio

44、n:ExternalDecoder*s WebRTC MediaChannels Client Channel 8 Video FrameHeight:720*s WebRTC MediaChannels Client Channel 8 Video FrameWidth:1280*s WebRTC MediaChannels Client Channel 8 Video FramesDecoded:1826*s WebRTC MediaChannels Client Channel 8 Video FramesPerSecond:30*s WebRTC MediaChannels Clien

45、t Channel 8 Video KeyFramesDecoded:1*s WebRTC MediaChannels Client Channel 8 Video Protocol:video/VP8 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLivePacket CapturesWe can determine the SSRC by converting the channel ID from decimal to hexWebRTC MediaChannels Client Channe

46、l 8 Id:RTCInboundRTPVideoStream_6BRKCOL-301-0 x519b685b 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveLogging(osd.log)Relevant call setup and in call logging can be seen in the osd.log files for WebRTCCan be used to track media changes or see limite

47、d media information after a callGood when checking for error messages related to connection failures37BRKCOL-3016gui3781:Io2:(S)xcom WebRTC/Update State:connecting ID=166 gui3781:Io2:(S)xcom WebRTC/Update State:lobby ID=168 gui3781:Io2:(S)xcom WebRTC/Update State:connected ID=175 2023 Cisco and/or i

48、ts affiliates.All rights reserved.Cisco Public#CiscoLiveLogging(osd.log)38BRKCOL-3016*s WebRTC MediaChannels Client Channel 25 Direction:Outgoing*s WebRTC MediaChannels Client Channel 25 Id:RTCOutboundRTPVideoStream_997907521Io2:(S)Status WebRTC MediaChannels Client Channel25 Direction:OutgoingIo2:(

49、S)Status WebRTC MediaChannels Client Channel25 Id:RTCOutboundRTPVideoStream_997907521Io2:(S)Status WebRTC MediaChannels Client Channel25 Transport RTCP Local IpAddressIo2:(S)Status WebRTC MediaChannels Client Channel25 Transport RTCP Local Port:0Io2:(S)Status WebRTC MediaChannels Client Channel25 Tr

50、ansport RTCP Local Protocol:UnknownIo2:(S)Status WebRTC MediaChannels Client Channel25 Transport RTCP Local IpAddress:64.99.194.235Io2:(S)Status WebRTC MediaChannels Client Channel25 Transport RTCP Local Port:35751Io2:(S)Status WebRTC MediaChannels Client Channel25 Transport RTCP Local Protocol:UDPx

51、status.txtosd.log 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveLogging(osd.log)39BRKCOL-3016Io2:(S)Status WebRTC MediaChannels Client Channel25 Video FrameHeight:360Io2:(S)Status WebRTC MediaChannels Client Channel25 Video FrameWidth:640Io2:(S)Status WebRTC MediaChannel

52、s Client Channel25 Video FramesPerSecond:22Io2:(S)Status WebRTC MediaChannels Client Channel25 Transport RTCP Local Port:47465Io2:(S)Status WebRTC MediaChannels Client Channel25 Video FramesPerSecond:29Io2:(S)Status WebRTC MediaChannels Client Channel25 Video FramesPerSecond:30Io2:(S)Status WebRTC M

53、ediaChannels Client Channel25 Video FramesPerSecond:29Io2:(S)Status WebRTC MediaChannels Client Channel25 Video FrameHeight:540Io2:(S)Status WebRTC MediaChannels Client Channel25 Video FrameWidth:960Io2:(S)Status WebRTC MediaChannels Client Channel25 Video FramesPerSecond:30Io2:(S)Status WebRTC Medi

54、aChannels Client Channel25 Video FramesPerSecond:29Io2:(S)Status WebRTC MediaChannels Client Channel25 Video FrameHeight:720Io2:(S)Status WebRTC MediaChannels Client Channel25 Video FrameWidth:1280Io2:(S)Status WebRTC MediaChannels Client Channel25 Video FramesPerSecond:30 2023 Cisco and/or its affi

55、liates.All rights reserved.Cisco Public#CiscoLiveManual WebRTC Calling40BRKCOL-3016For manual call testing,xcommands can be used to initiate a WebRTC based call to the provider of choice with the below commandsSee for full API documentationxCommand WebRTC Join Type:MSTeams Url:xCommand WebRTC Join T

56、ype:GoogleMeet Url:API DocumentationExample 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveExample 1:Unable to Join MS Teams WebRTCProblem Description:We have multiple systems connected via Edge for Devices which fail when attempting to join a Microsoft Teams meeting via

57、OBTP(WebRTC).The call attempts to connect and an error message is displayed saying“Were sorry,weve run into an issue”.Tested Webex and Zoom meetings and they are working fine.42BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveResolution:Unable to Join MS Teams W

58、ebRTC14:46:53.280+00:00 appl3888:CuilApp1:User root/internal/phoenix-system about to execute command/WebRTC/Join BookingId:webex-2 Title:Type:MSTeams Url:from localhost.14:46:53.280+00:00 appl3888:APPL_Rpc I:Started WebRTC call CorrelationID=URL=Title=14:48:07.379+00:00 appl3888:WebRTCCall I:Ended W

59、ebRTC call43BRKCOL-301614:46:54.875+00:00 gui3579:INFO:WebEngine:Started loading https:/ gui3579:INFO:WebEngine:Succeeded loading https:/ gui3579:INFO:WebEngine:Started loading https:/ Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveResolution:Unable to Join MS Teams WebRTC44BR

60、KCOL-3016After the call is initiated and the WebRTC application is loaded,the web client tries to reach out to .The DNS resolution can be seen working normally however any communication to the resolved address cannot complete the TCP handshake.Eventually the process times out and an error is present

61、ed in the Teams WebRTC application.In this instance traffic was only allowed externally to specific IP addresses and this one was missing from the allowed list.Agenda 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public3rdParty Meeting OverviewLog Collection OverviewTroubleshooting WebR

62、TCTroubleshooting MTRConclusionBRKCOL-301645 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMTR vs RoomOSContainerized OS runs within RoomOS 11Android container runs MTR softwareHandles all user interaction and callingRoomOS still maintains direct control over hardware an

63、d networking46BRKCOL-3016RoomOS 11Android container Hardware 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMTR Registration OptionsAll MTR devices register to Microsoft Teams Admin Center(TAC)Devices can also be registered with control hub for additional features and man

64、agement/troubleshooting optionsControl Hub registration can be done at the time of setup or at any point following on the device settings pageRegistration is done with the normal process using 16 digit activation key47BRKCOL-3016Teams Admin CenterWebex Control Hub 2023 Cisco and/or its affiliates.Al

65、l rights reserved.Cisco Public#CiscoLiveMTR Device AccessDirect device access varies depending on if control hub is used for registrationIf Control Hub is not connected at the time of setup,user will be prompted to configure a username and passwordThis can be changed at a later time in Teams Admin C

66、enterIf the device is connected to Control Hub,the local admin account will be locked down and the device can be accessed directly from Control Hub48BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMTR Device Settings LockBy default all MTR systems lock the loca

67、l UI from making any settings changesFor non-Control Hub attached systems,these can be accessed by manually entering the admin credentials on the touch screenFor control hub devices,these settings are locked completely until the configuration is changedThis lock can be disabled by setting UserInterf

68、ace/SettingsMenu/Mode to“unlocked”49BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMTR Log CollectionMTR logs can be collected a variety of waysOn DeviceControl Hub(if connected)Teams Admin CenterDevice and Control Hub collected logs use the familiar bundle fo

69、rmat with some additionsTeams Admin Center logs contain a small subset of Microsoft Teams client specific logging50BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMTR Logging(Traditional Device Logs)51BRKCOL-3016 2023 Cisco and/or its affiliates.All rights rese

70、rved.Cisco Public#CiscoLiveTeams Admin Center LogsLogs can be downloaded from Teams Admin Center under the“Teams Rooms for Android”devices pageThis will queue a download action which can take some time before completingStatus can be checked and downloaded once available under the“History”tab52BRKCOL

71、-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMTR Logging(Teams Admin Center Logs)53BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMTR Log File Overview(logcat.log)Essentially the”all.log”for the Android instance of MTRAll ot

72、her more specific logcat files also dump to logcat.logRotates from logcat.log(newest)to logcat.log.4(oldest)No equivalent of x.first as seen in standard RoomOS logging54BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMTR Log File Overview(logcat-cisco.log)Loggi

73、ng of interaction between MTR and RoomOSGood place to track issues with settings changes initiated through the MTR UI55BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMTR Log File Overview(xstatus.txt)New lines added for version information and configuration st

74、ateCall state tracking to hook into other system functions56BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveWeb Interface57BRKCOL-3016Additional MTR section containing version informationAccess to config and status pages as normalOther pages for features that d

75、o not apply to MTR deployments removed 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMTR Log Files Additional NotesBoth callhistory.txt and bookings.txt are not populated as they normally would be for RoomOS meetingsAll other system logs function normally however you wil

76、l not see most MTR specific actions such as calls or whiteboarding loggedAnything in MTR that interacts with hardware(such as connecting a presentation source)will still be reflected in the regular logs58BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveDebugging

77、 Limitations59BRKCOL-3016No extended loggingNo call controlDirect log access still providedNo native pcap ability 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveManually Enable Extended Logging60BRKCOL-3016Extended logging and pcaps can be manually enabled through xAPI co

78、mmands or via the“Developer API”section in the webUISee for more info on options 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveMTR Logging LevelsAdditional debugging can be enabled for MTR logs via device menus61BRKCOL-3016 2023 Cisco and/or its affiliates.All rights res

79、erved.Cisco Public#CiscoLive3rdParty Meeting ProcessingIn order for Microsoft Exchange to process Webex or other 3rdparty meeting invites to the resource mailbox,the following settings must be applied via PowerShell to the room mailboxProcessExternalMeetingMessagesThis must be set to$true to process

80、 meeting requests that originate outside of the Exchange organization.This is a requirement to process external Teams meetings and third-party meetings.DeleteCommentsThis must be set to$false to ensure that text in the message body of the incoming meeting request is not deleted.This is a requirement

81、 to process external Teams and third-party meetings to provide the One Touch Join experience.62BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLive3rdParty Meeting ProcessingAdditionally,the individual services must be enabled on the device under 63BRKCOL-3016Examp

82、les 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveExample 1:MTR Calls Failing to ConnectProblem Description:We have a Webex Board Pro in MTR mode that will no longer connects to incoming our outgoing calls.The call attempts to join but immediately disconnects.When callin

83、g to a person it says“Were sorry,we couldnt connect your call”.65BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveResolution:MTR Calls Failing to Connect04-21 16:29:05.920 1165 4862 I Calling:CallNavigation:ProcessId:1165,Thread:Pool-CallInitialization-Thread-16

84、,Showing fullscreen incoming call:12504-21 16:29:08.779 1165 4908 E EndpointsAppData:ProcessId:1165,Thread:Pool-Auth-Thread-281,Failed to fetch SkypeToken from Authz endpoint.errorCode:UserLicenseNotPresentForbidden,message:User Login.Teams is disabled in user licenses 66BRKCOL-3016SolutionSolution:

85、License had been removed from the device at some point after registration and needed to be re-added through the admin portal under Users Active Users Licensing and Apps 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveExample 2:System Freezing on MTR InstallProblem Descript

86、ion:We are deploying MTR on new devices and the installation process is freezing when downloading the MTR-A image.Multiple users with devices in different locations are reporting the same issue.67BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveResolution:System

87、 Freezing on MTR Install*s Apps FirstTimeWizard Topics MTR InstallMTR State:CurrentlyOn*s SystemUnit Extensions Microsoft InCall:False*s SystemUnit Extensions Microsoft State:Disabled*s SystemUnit Extensions Microsoft Supported:True*s SystemUnit Extensions Supported:True68BRKCOL-3016MTR extension is

88、 not present in the log bundle and not currently running according to the xstatus.txt output 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveResolution:System Freezing on MTR Installswupgrade2551:SoftwareUpgrade W:HTTP(1)Error:(Could not resolve host:)swupgrade2551:Softwar

89、eUpgrade I:Download#1 failed:Could not resolve host: url:https:/ I:Download#15 failed:Could not resolve host: url:https:/ lookup was failing when the system attempted to download the MTR extension,causing the download process to try and fail repetitively.2023 Cisco and/or its affiliates.All rights r

90、eserved.Cisco Public#CiscoLiveExample 3:MTR Registration FailingProblem Description:We are registering new MTR devices but the registration process is failing with an error stating Teams cannot be accessed.70BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveResol

91、ution:MTR Registration FailingLogonUserWatcher:received intent action:com.microsoft.teams.ipphone.admin.agent.CURRENT_LOGON_USERLogonUserWatcher:userInfo:authenticatedUsers:accountType:ENTERPRISE,cloudType:PUBLIC_CLOUD LogonUserWatcher:teamsIdentifier:deviceId:91ff0075-a133-376c-88ae-ad83e7d51277Log

92、onUserWatcher:userInfo value:UserInfousageMode=personalUser LogonUserWatcher:userid(9b844f15-c759-4a35-91a4-0e47f2702b59)with teamsIdentifier GetRecoveryCommands:canRunWithState:false,manageabilityLevel:HealthyI EnrollOperation:Enroll operation startedMSALService:AADSTS53003:Access has been blocked

93、by Conditional Access policies.The access policy does not allow token issuance.71BRKCOL-3016SolutionSolution:Conditional access policies have been enabled but inTuneonboarding is not configured for this device thus the registration is denied.A similar error would also be present if onboarding was de

94、nied based on Intune parametersAgenda 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public3rdParty Meeting OverviewLog Collection OverviewTroubleshooting WebRTCTroubleshooting MTRConclusionBRKCOL-301672 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveKey Point

95、s to RememberDetermine the meeting platform usedFor WebRTC based calls,pull logs while call is in progressReference osd.log for more detailed WebRTC call informationFor MTR devices,remember to configure credentials and unlock settingsMTR logs can be collected from device,Control Hub,and Teams Admin

96、Center73BRKCOL-3016 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLiveFill out your session surveys!Attendees who fill out a minimum of four session surveys and the overall event survey will get Cisco Live-branded socks(while supplies last)!74BRKCOL-3016These points help you

97、 get on the leaderboard and increase your chances of winning daily and grand prizesAttendees will also earn 100 points in theCisco Live Challenge for every survey completed.2023 Cisco and/or its affiliates.All rights reserved.Cisco PublicContinue your educationVisit the Cisco Showcase for related de

98、mosBook your one-on-oneMeet the Engineer meetingAttend the interactive education with DevNet,Capture the Flag,and Walk-in LabsVisit the On-Demand Library for more sessions at www.CiscoL you#CiscoLive 2023 Cisco and/or its affiliates.All rights reserved.Cisco Public#CiscoLive77Gamify your Cisco Live

99、experience!Get points Get points for attending this session!for attending this session!Open the Cisco Events App.Click on Cisco Live Challenge in the side menu.Click on View Your Badges at the top.Click the+at the bottom of the screen and scan the QR code:How:123477 2023 Cisco and/or its affiliates.All rights reserved.Cisco PublicBRKCOL-3016#CiscoLive