Introducing: Blue Jeans Command Center

  • 7
  • Announcement
  • Updated 7 months ago
  • (Edited)
We have been bursting at the seams to announce our *NEW* Command Center for Blue Jeans administrators. 

Command Center provides service intelligence to the IT administrator to help them embrace the power of cloud-based collaboration. With this new feature, IT administrators won’t have to sacrifice the visibility, measurement and controls they crave through metrics tracking and interactive reporting on both historical and live meetings. Key features include:

• Deployment Dashboard. Top-level graphs and charts display service utilization over time, geographical participant distribution, endpoint distribution, key feature utilization and top users or departments.

• Real-Time Metrics. Real-time meeting metrics include live meeting stats for troubleshooting, including: endpoint distribution and performance, in-meeting activities such as recording or content sharing, and quality metrics such as bitrate, jitter and packet loss.

• Historical Reports. Filtered by user-definable date ranges, historical reports deliver meeting- and endpoint-level metrics, with the option to export this data to Microsoft Excel or other business intelligence solutions.

Don’t Take Our Word For It, Hear It From a Customer:

“Probably the biggest benefit we have seen since using the Command Center is getting a 360-degree view of meetings,” said Michał Rączka, IT office and collaboration director of Naspers eCommerce. “Understanding the wheres and whens are valuable, but knowing how to make meetings better is key to making our jobs easier and helping the company run better.”

Left Wanting More?

Check out the optional Command Center Pro service, which adds real-time meeting visibility and the option to export data for analysis in Microsoft Excel or business intelligence solutions. Read more about Command Center Pro here
Photo of Community Team

Community Team, Community Admin

  • 5,652 Points 5k badge 2x thumb

Posted 4 years ago

  • 7
Photo of Marcin

Marcin

  • 168 Points 100 badge 2x thumb
Great news!

However, is there any place to find numeric values of the data presented as the graphs are not presented very wall and it is hard to tell the exact values from it.
Photo of Community Team

Community Team, Community Admin

  • 5,652 Points 5k badge 2x thumb
Hi Marcin - Were you referring to exporting the data from each graph? OR were you referring to the raw data in which you can export to .csv or .xls from the "All Meetings". I've included some screenshots below to help you navigate to the "export raw data". Please let me know if you need further details and we can set up a quick demo. 




Photo of Marcin

Marcin

  • 168 Points 100 badge 2x thumb
Thank you so much! This is great!

One more thing, do the details of "Video IN" and "Video OUT" represent the values at the endpoint?

If yes, could you please let me know how those details are exchanged between endpoint and BlueJeans infrastructure?

Many thanks for your help!
Marcin
Photo of Stuart Minchington

Stuart Minchington, Enterprise Solutions Engineer

  • 888 Points 500 badge 2x thumb
Hello Marcin,

The video in/out details refer to the bitrate that is negotiated between the endpoint and Blue Jeans during call setup. 

For example, during the initial call setup an endpoint will advertise it's ability to send & receive 1.5Mbps. This would be the maximum bitrate that the endpoint can support. 

However, the bitrate will fluctuate during the meeting for a number of reasons. The two most common reasons are:

  1. The bitrate will decrease if there is lack of physical movement in the meeting. The way video codecs work is that it will not retransmit the entire video image if there is lack of movement, which saves CPU power and bandwidth consumption. 
  2. Blue Jeans utilizes bandwidth management algorithms that can dynamically increase/decrease the bitrate based on the condition of the network. So if the network was congested and started dropping packets we have the ability to reduce the bitrate from 1.5Mbps to 768Kbps or lower if necessary. Once the network conditions improve the bitrate will increase.
The jitter and packet loss statistics are exchanged between the endpoint and Blue Jeans via RTCP, which is the Real-time Transport Control Protocol. This is a separate communication channel from the video feed itself that only sends statistical data.

Hope this helps!
Photo of Marcin

Marcin

  • 168 Points 100 badge 2x thumb
Thanks Stuart,

Just to clarify, the Video IN parameters are measured for the incoming stream to the endpoint, and Video OUT parameters are measured at BlueJeans infrastructure.

If understand it correctly it could be visualized as below:

Endpoint A <----------------> Blue Jeans <-----------------> Endpoint B
          Video IN           Video Out       Video Out            Video IN
          for A                     for A                 for B                     for B

Many thanks in advance.
Marcin
(Edited)
Photo of UNC Pharmacy

UNC Pharmacy

  • 232 Points 100 badge 2x thumb
I called Sales to inquire about this feature and was told that the Basic command center is free and already enabled automatically.  I tried logging out and back in and I also tried looking in the /scheduling page to enable it and I do not see it there.  How do I find this Command Center page?
UNC Pharmacy - great question and glad you're excited about Command Center. I am in touch with your Customer Success Manager now to get this solved by tomorrow (Friday). Thanks!
(Edited)
Photo of Brian

Brian

  • 524 Points 500 badge 2x thumb
Hey Guys! Im not sure if im just not seeing this, but where do i go to access the command center? 

Thanks in advance!
Hi Brian! Thanks for posting :) I am in touch with your Customer Success Manager as well. We are currently in BETA so all customers will be provisioned in late October. But, since you came to the right place, we will make sure this happens asap!
Photo of Stuart Minchington

Stuart Minchington, Enterprise Solutions Engineer

  • 888 Points 500 badge 2x thumb
Hello Marcin,

Actually, it is the other way round. The stats are laid out to be read from a Blue Jeans perspective. So, your diagram will read:

Endpoint A <----------------> Blue Jeans <-----------------> Endpoint B
          Video Out           Video In       Video In            Video Out
          for A                     for A                 for B                     for B
Photo of Marcin

Marcin

  • 168 Points 100 badge 2x thumb
Hi Stuart,

Many thanks for your clarification. Is it possible to get parameters of audio/video quality leaving Bluejeans to Endpoints? It is quite vital to see if the network between BlueJeans and Endpoint is affecting the quality of the call. Do you think that it is possible to get those stats in future versions of CommandCenter?

Many thanks in advance.
Marcin
Photo of Stuart Minchington

Stuart Minchington, Enterprise Solutions Engineer

  • 888 Points 500 badge 2x thumb
Hello Marcin,

There is a lot of this data stored within Command Center. If you click on the menu icon on the left and select "All Meeting Stats" you will receive a list of all your meetings. Select the meeting that you want to analyze and you will be presented with a list of Endpoints. From here, select the endpoint of interest and you will now have a screen containing two tabs: Call Characteristics and Summary Stats.

I have attached a screenshot of each tab. As you can see, the Call Characteristics tab gives you three graphs outlining the audio, video, and overall call quality metrics for loss, bitrate, jitter and the frames per second (fps) for the video feed.



The Summary Stats tab provides information related to the send/receive audio & video bitrate, which audio/video codec was used, whether the endpoint is behind a NAT or routing via a Proxy etc. It then provides a summary table of the stats found in the Call Characteristics tab.



Is there any other statistical information that you would like to see added to Command Center?
Photo of Karl Nurmi

Karl Nurmi

  • 80 Points 75 badge 2x thumb
"call quality" appears to be a number ( I have seen it between 2-4 so far).  What is the scale of this number?  What information and model is used to determine it?
Photo of Raphael

Raphael

  • 70 Points
It is likely an estimated MOS (Mean Opinion Score). Its range is 1 to 5, though I agree it would be interesting to learn more about how this estimate is computed.
Photo of Lee Snyder

Lee Snyder, Official Rep

  • 5,074 Points 5k badge 2x thumb
Hello!

The call quality score is on a 1-5 scale, 1 being poor and 5 meaning great. The call quality score is measured by the amount of network packet loss and endpoint suffered in the call.

Regards,
Lee - BlueJeans Support
Photo of Brett Smith

Brett Smith

  • 2,672 Points 2k badge 2x thumb
Hi @Marcin, just wanted to follow up on Stuarts response back to you. Is there any other statistical information that you would like to see added to Command Center? We want to make sure we provide this feedback to product and have it considered for future versions of CC.
Photo of Marcin

Marcin

  • 168 Points 100 badge 2x thumb
Hi Brett,

Thank you for coming back to me.

It seems that there are only statistic regarding the incoming stream to BJN.

As per every call leg (endpoint to BJN infrastructure), there are two streams and 2 points of entry/exit of the streams. It makes a total of 4 possible places where stats can be collected.

Having all the data, would be very helpful in case of any quality issues with videoconferencing as it makes it possible to check which call leg was generating quality issue.

Many thanks for your interest.

KInd regards,
Marcin
Photo of Stuart Minchington

Stuart Minchington, Enterprise Solutions Engineer

  • 888 Points 500 badge 2x thumb
Hello Marcin,

If I understand correctly, you would like to collect similar stats from your point of entry/exit on the network in addition to the stats that we are able to collect on the Blue Jeans network?

If that is what you are asking, then that would require some type of on-premise solution on your end that Command Center would need access to in order to get the complete picture of the stats. 

Right now, we can provide 4 sets of stats: Video in & out, Audio in & out.
However, these stats are all collected on the Blue Jeans side as we do not have direct access to your network (which is a good thing :-D). 

From a troubleshooting perspective, when we need to pinpoint the source of a packet loss issue, then the only way we can see the complete picture is to have you run packet captures your internal and external Firewall interface. We would also run a capture on our infrastructure and use an application called Wireshark to figure out at which point do packets start dropping.
Photo of Wojciech Nawrot

Wojciech Nawrot

  • 200 Points 100 badge 2x thumb
Hi Stuart,
Audio/video IN stats make sense. At Bluejeans entry (or in other words at the end of the path between client and BJN infrastructure) some stats are calculated. The receiver (Bluejeans) knows how many packets were sent and how many packets were successfuly delivered. This allows for packet loss calculation for the whole path. Thanks to time stamping performed by the client, the receiver knows how much time it takes to deliver the packet and for a number of RTP packets jitter values can be computed. All this stats show what happens in the "channel" between the endpoint and Bluejeans backend.

If I properly understand, all audio/video OUT measurements are performed at BlueJeans boundary, where the path toward the client starts. Why do you perform measures at the beginning of the path rather than on its end at client side? Client is able to calculate loss and jitter using sequence numbers and timestamps. 

If the OUT measurements are performed at BlueJeans side we are also wondering  why there is usually so high packet loss or jitter between Bluejeans endpoint (the MCU) and the measurement point.
Please clarify.
Thank you in advance.
Regards
Wojtek
Photo of Stuart Minchington

Stuart Minchington, Enterprise Solutions Engineer

  • 888 Points 500 badge 2x thumb
Hi Wojtek,

I could be wrong, but I believe Marcin's question was whether we could collect stats locally on the client side, which would give us extra insight as to where the packet loss is actually occurring. 

The stats for Video Out and Audio Out is based on the RTP and corresponding RTCP data sent from Blue Jeans to the client/endpoint. When we transmit this RTCP data it starts within our data center, gets handed off to one of the ISP's that we peer with, traverses the Internet, and ends up on the client/endpoints network. The stats we receive for Audio/Video Out are responses from the endpoint that tells us "Hey! x percent of the data that you sent to me is missing". However, these stats are only collected on the Blue Jeans side, and not at any other point in the network between us and the endpoint, which makes it difficult to determine the exact point where the packet loss occurred. 

So, if we had additional points in the network where we could collect stats, then we could have deeper insight in to the performance and quality of the network(s) in-between Blue Jeans and endpoint. Today we can only say that loss exists somewhere in the direction of Blue Jeans ---> Endpoint (Audio/Video Out) and from the Endpoint ---> Blue Jeans (Audio/Video In). 

Right now, in order to pinpoint where the loss is occurring we would need to run a packet capture at as many points in the network as possible, ideally in the following areas: On the client itself, the client side internal & external Firewall interfaces, and on the Blue Jeans network.

From there we could analyze the outputs of each capture and determine the source of the issue.

I hope this helps clarify the way we gather the call stats.
(Edited)
Photo of Raphael

Raphael

  • 70 Points
Hi, I know this is an old post, but I'm just starting to use Command Center and find it a great resource.

One limitation I found is that exported CSVs do not contain all of the data that is shown in the web UI. Is there a way to include more data in exported endpoint CSVs, specifically for jitter and loss statistics? I've attached a screenshot to clarify:

Interestingly, the endpoints.csv file contains two columns "JitterMaxAI" and "JitterMaxVI" that are missing in the web UI – I believe those would be the two empty rows under "Max Jitter" in the above screenshot.

However, it's more important to me to have all data available in the CSV, as this is what I use for data analysis.

Thanks in advance,
Raphael
Photo of Radhika@BJsupport

Radhika@BJsupport, Official Rep

  • 6,026 Points 5k badge 2x thumb
Hi Raphael,

Thank you for your question. Currently we do not have highlighted data in downloaded CSV. I am submitting a feature request to our dev team to consider your requirement.

Thank you,

Radhika Chatur
BlueJeans Support Team