disconnect cause：KickedFromLocus (INACTIVE)

[qiang.xia.kty]

hello 

my device：room kit plus is registered with Cisco Cloud Server

However, my device will often automatically disconnect during the meeting. The call history and disconnection reasons are as follows. Does anyone know how to solve this problem?

*r CallHistoryGetResult Entry 1 CallbackNumber: "spark:25188823012@webex.com"
*r CallHistoryGetResult Entry 1 DisplayName: "25188823012"
*r CallHistoryGetResult Entry 1 Direction: Outgoing
*r CallHistoryGetResult Entry 1 Protocol: Spark
*r CallHistoryGetResult Entry 1 CallRate: 6000
*r CallHistoryGetResult Entry 1 CallType: Video
*r CallHistoryGetResult Entry 1 VideoUsed: True
*r CallHistoryGetResult Entry 1 EncryptionType: "AES-256-GCM"
*r CallHistoryGetResult Entry 1 BookingId: ""
*r CallHistoryGetResult Entry 1 Duration: 1810

*r CallHistoryGetResult Entry 1 StartTime: "2022-01-14T03:07:42"
*r CallHistoryGetResult Entry 1 StartTimeUTC: "2022-01-14T03:07:42Z"
*r CallHistoryGetResult Entry 1 EndTime: "2022-01-14T03:37:52"
*r CallHistoryGetResult Entry 1 EndTimeUTC: "2022-01-14T03:37:52Z"
*r CallHistoryGetResult Entry 1 DaysAgo: 0
*r CallHistoryGetResult Entry 1 DisconnectCause: "KickedFromLocus (INACTIVE)"
*r CallHistoryGetResult Entry 1 DisconnectCauseCode: 0
*r CallHistoryGetResult Entry 1 DisconnectCauseOrigin: Spark
*r CallHistoryGetResult Entry 1 DisconnectCauseType: RemoteDisconnect

[Eric Ingram]

I'm seeing this and yet to get answer from TAC who wants more logs that all say KickedFromLocus (INACTIVE)".  If anyone knows what this is please advise.  Thanks!!

I've checked FW logs and we see disconnection coming from Cisco media nodes subnet.  Someone at Cisco should know what this means.  

[qiang.xia.kty]

I have a similar problem with my device, have you had it recently, has Cisco tac responded?

[eservcoll]

Same. Anyone get back to you yet from TAC?

[eservcoll]

Doesn't appear this has been resolved. Still happening. I do now see the below once in a while though. Most of the time only KickedFromLocus.

KickedFromLocus (Locus inactive after mercury reconnect)

TAC also did respond to a ticket. Nothing was solved, response was, yes we can see it disconnect.

[eservcoll]

Another screenshot showing the different times. We had a similar issues years ago when using on prem servers. But those timeouts were at exactly 15 min intervals. these drops are random. This pic is a good one as it shows drops ranging from 4 min up to an hour. Have other locations that go up to 4 hours. If the times were consistent...