09-24-2013 12:51 PM - edited 03-18-2019 01:51 AM
I've seen this a few times on one specific C40 consistently, it seems to appear after select conferences connect, I see it several time over and over in the xhistory. Our MCU does all the calling, so the codec in the room doesn't do anything, but auto answers the incoming call from the bridge. The default call protocol being used by the bridge is H.323, the codec isn't configured for SIP at this time. The dialing and call back numbers are that of the codec itself.
*h xHistory CallLogs Call 3153 CallId: 296
*h xHistory CallLogs Call 3153 Protocol: "Sip"*h xHistory CallLogs Call 3153 Direction: Incoming
*h xHistory CallLogs Call 3153 CallType: Audio*h xHistory CallLogs Call 3153 RemoteNumber: "sip:100@x.x.175.82"
*h xHistory CallLogs Call 3153 CallbackNumber: "sip:100@x.x.175.82"*h xHistory CallLogs Call 3153 DisplayName: "100"
*h xHistory CallLogs Call 3153 CallRate: 768*h xHistory CallLogs Call 3153 DisconnectCauseValue: 1
*h xHistory CallLogs Call 3153 DisconnectCause: ""*h xHistory CallLogs Call 3153 DisconnectCauseType: LocalDisconnect
*h xHistory CallLogs Call 3153 DisconnectCauseCode: 0*h xHistory CallLogs Call 3153 DisconnectCauseOrigin: SIP
*h xHistory CallLogs Call 3153 StartTime: "2013/09/24 12:07:02"*h xHistory CallLogs Call 3153 Duration: 0
*h xHistory CallLogs Call 3153 Encryption: "Aes-128"*h xHistory CallLogs Call 3153 BookingId: ""
All of our conferences are scheduled via TMS 14.2.2, with a VCS X7.2.2. C40 is currently running TC5.6, waiting on TC6.3.
Solved! Go to Solution.
01-14-2014 08:24 PM
Oh, I didn't even notice the link in the earlier reply, blended into the text too well. I'll take a look, thanks.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide