Question for EX/MX Multi-Site License and Call Detail

dgauthier · ‎09-12-2014

When a user conferences two (2) or three (3) endpoints...how does the call detail appear in the EX/MX endpoint via xHistory. I am trying to understand if the call detail shows that the conference creator show the other endpoints linked to the conference created...please advise...thx.

Wayne DeNardi · ‎09-14-2014

Here's a quick xHistory grab of an EX90's <Endpoint 1> multi-site call to two other endpoints, <Endpoint 2> and <Endpoint 3>:

Here's the EX90's call logs:

*h xHistory CallLogs Call 904 BookingId: "" *h xHistory CallLogs Call 904 CallId: 9 *h xHistory CallLogs Call 904 CallPriority: None *h xHistory CallLogs Call 904 CallRate: 768000 *h xHistory CallLogs Call 904 CallType: Video *h xHistory CallLogs Call 904 CallbackNumber: "h323:<Endpoint 2>" *h xHistory CallLogs Call 904 Direction: Outgoing *h xHistory CallLogs Call 904 DisconnectCause: "" *h xHistory CallLogs Call 904 DisconnectCauseCode: 0 *h xHistory CallLogs Call 904 DisconnectCauseOrigin: Internal *h xHistory CallLogs Call 904 DisconnectCauseType: LocalDisconnect *h xHistory CallLogs Call 904 DisconnectCauseValue: 1 *h xHistory CallLogs Call 904 Dismissed: True *h xHistory CallLogs Call 904 DisplayName: "<Endpoint 2>" *h xHistory CallLogs Call 904 Duration: 16 *h xHistory CallLogs Call 904 Encryption: "Aes-128" *h xHistory CallLogs Call 904 Protocol: "H323" *h xHistory CallLogs Call 904 RemoteNumber: "h323:<Endpoint 2>" *h xHistory CallLogs Call 904 StartTime: "2014/09/15 10:08:18"

*h xHistory CallLogs Call 905 BookingId: "" *h xHistory CallLogs Call 905 CallId: 10 *h xHistory CallLogs Call 905 CallPriority: None *h xHistory CallLogs Call 905 CallRate: 768000 *h xHistory CallLogs Call 905 CallType: Video *h xHistory CallLogs Call 905 CallbackNumber: "h323:<Endpoint 3>" *h xHistory CallLogs Call 905 Direction: Outgoing *h xHistory CallLogs Call 905 DisconnectCause: "" *h xHistory CallLogs Call 905 DisconnectCauseCode: 0 *h xHistory CallLogs Call 905 DisconnectCauseOrigin: Internal *h xHistory CallLogs Call 905 DisconnectCauseType: LocalDisconnect *h xHistory CallLogs Call 905 DisconnectCauseValue: 1 *h xHistory CallLogs Call 905 Dismissed: True *h xHistory CallLogs Call 905 DisplayName: "<Endpoint 3>" *h xHistory CallLogs Call 905 Duration: 8 *h xHistory CallLogs Call 905 Encryption: "Aes-128" *h xHistory CallLogs Call 905 Protocol: "H323" *h xHistory CallLogs Call 905 RemoteNumber: "h323:<Endpoint 3>" *h xHistory CallLogs Call 905 StartTime: "2014/09/15 10:08:28"

and the coresponding call log from <Endpoint 3>:

*h xHistory CallLogs Call 3333 BookingId: "" *h xHistory CallLogs Call 3333 CallId: 168 *h xHistory CallLogs Call 3333 CallPriority: None *h xHistory CallLogs Call 3333 CallRate: 768000 *h xHistory CallLogs Call 3333 CallType: Video *h xHistory CallLogs Call 3333 CallbackNumber: "h323:<Endpoint 1>" *h xHistory CallLogs Call 3333 Direction: Incoming *h xHistory CallLogs Call 3333 DisconnectCause: "Normal" *h xHistory CallLogs Call 3333 DisconnectCauseCode: 16 *h xHistory CallLogs Call 3333 DisconnectCauseOrigin: Q850 *h xHistory CallLogs Call 3333 DisconnectCauseType: RemoteDisconnect *h xHistory CallLogs Call 3333 DisconnectCauseValue: 2 *h xHistory CallLogs Call 3333 Dismissed: True *h xHistory CallLogs Call 3333 DisplayName: "<Endpoint 1>" *h xHistory CallLogs Call 3333 Duration: 9 *h xHistory CallLogs Call 3333 Encryption: "Aes-128" *h xHistory CallLogs Call 3333 Protocol: "H323" *h xHistory CallLogs Call 3333 RemoteNumber: "<Endpoint 1>" *h xHistory CallLogs Call 3333 StartTime: "2014/09/15 10:08:27"

There really isn't anything that identifies that this is a multi-site call in the call logs.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

dgauthier · ‎09-15-2014

Wayne,

Thanks...I am familiar with the xHistory...your one sentence "there really isn't anything that identifies...". That was my suspicion...just wanted additional feedback to ensure I was not over looking anything. The only 'tie-in' factor is the close proximity to the endpoint start times and that would still be an assumption.

Appreciate the feedback.

Wayne DeNardi · ‎09-16-2014

Even then, looking at the start times, doesn't necessarily guarantee that you'll get all multisite calls.

You'll miss all the ones where the 2nd site is dailled in later, or part way through a call, or a disconnect and re-dial during a call.

In short, there's nothing in the xhistory that indicates the call was using the multi-site feature.

Wayne
--
Please remember to rate responses and to mark your question as answered if appropriate.

Wayne

Please remember to mark helpful responses and to set your question as answered if appropriate.

dgauthier · ‎09-17-2014

Wayne, I agree with you. I would need to make assumptions as to when a calls with close start times are candidate calls for a multi-site call. Not a perfect science...but 95% good.