By using a performance monitoring solution and deploying monitoring agents to strategic locations, you can clearly see if a problem is related to the network and, if so, where a network problem is coming from. With proactive network monitoring software, you can detect problems as soon as they occur, long before they reach our end users. Network issues are very obvious with video calls, so you should avoid this. You can also use other network monitoring tools in the obkio software to get even more detailed network performance data. Continuously monitor the performance of your Amazon Chime, view network metrics from your Obkio dashboard, and receive automatic alerts for network issues. Device Monitoring: As mentioned in our Station 22 case study, even firewall issues, such as high CPU usage, can affect unified communications applications like Zoom. If you`re experiencing LAN issues for Zoom, use Obkio`s Network Device Monitoring solution to monitor and scan for network issues related to firewalls, routers, switches, Wi-Fi access points, and SNMP-enabled devices. Before you set up Amazon Chime, make sure you meet the following requirements. You can use the Amazon Chime SDK for JavaScript in conjunction with WebRTC to configure quality and bandwidth options for meeting sessions. It provides automatic and manual controls to adapt to changing network conditions. Finding the right balance between quality and performance can be a challenge when the customer`s network or processor is limited. As network reliability and available bandwidth decrease, qualitative and functional trade-offs must be made in real time to maintain the feasibility of the meeting.
This guide provides an overview of the challenges associated with devices and networks, degradation detection mechanisms, and mitigation measures for different levels of degradation. Amazon Chime uses Amazon Elastic Compute Cloud (Amazon EC2) and other AWS services on TCP/443 port. If your firewall is blocking TCP/443 port, you should include *.amazonaws.com in a whitelist or include AWS IP address ranges in the AWS General Reference for the following services: The only real way to avoid these issues is to monitor the network performance of your Amazon Chime application to proactively identify problems and determine their cause. and repair them as soon as possible. Traceroutes: Traceroutes is a powerful tool that allows you to gather more information about network issues. For more information about performance and potential network issues, Obkio also regularly runs traceroutes in both directions to identify hop-by-hop issues and track historical latency between hops. The network estimate comes from the browser`s webRTC metrics (you can view them during the call when you open Chrome chrome://webrtc-internals/). You can also get and save these metrics from MetricsDidReceive, as shown in our demo. In this case, the browser estimated the bandwidth at only 1 Mbps. Network issues can affect many different parts of your network, from the Internet, VoIP, firewalls, and unified communications applications like Amazon Chime. Obkio`s agents also detect network outages in 5 seconds and network degradation in one minute.
So we already know that network performance can affect Amazon Chime performance, but your network isn`t always responsible for voIP and video issues. Amazon Chime voice connectors have the following bandwidth requirements: Many of us now rely on video calls as our primary form of communication, many different applications are becoming increasingly popular, including Amazon Chime. To make sure you always have the best video and call quality during meetings, we`re going to show you how to monitor Amazon Chime network performance. A network problem can sometimes occur on your company`s network, on your service provider`s network, or elsewhere. We`ve all been on one of those endless conference calls with service providers where everyone seems to point the finger at others and blame someone else. By monitoring your network performance, you can determine whether your network is impacting Amazon Chime performance and, if so, how to fix it. In a previous article, we`ll go over the 7 reasons to monitor network performance – in this article, we`ll summarize some of the benefits of Amazon Chime network performance monitoring. Network problems can occur in many parts of your network. So, if you`re looking for troubleshooting, you need to know where to start.
Once you`ve gathered information about the network issues causing Amazon Chime jitter, excavators, or disconnections, you`re ready to start troubleshooting! When designing an app that shares audio and video, you need to determine which feature is most important to your end users. Just as responsive web design allows a single web application to adapt to changing screen sizes, the audio-video component of your app can also respond to changing device and network conditions. For example, in a collaborative meeting, it may be acceptable to elegantly downgrade it to an audio-only experience. However, in a presentation where the screen is split, the presenter`s audio and screen sharing video may be the most important. By now, you may have realized that some applications, such as VoIP and unified communications applications, are more sensitive to network performance than others. You are in an important video call and suddenly your video starts to delay, the voices at the other end sound robotic and suddenly your screen freezes. Amazon Chime simplifies its firewall requirements to minimize the likelihood of firewalls accidentally blocking media and reduce firewall management overhead. If you are responsible for firewall rules, read on to find out what changes are required in your firewall configuration to ensure that your access to Amazon Chime is not affected.
Amazon Chime has the following bandwidth requirements for the media it provides: Up and down bandwidth adjusts to 1.2 Mbps up (during presentation) and down (during viewing) to achieve high quality, depending on network conditions. This scales up to 320 kbps depending on network conditions. We tried to mitigate this impact by providing the configuration of delays (see github.com/aws/amazon-chime-sdk-js/blob/main/guides/11_Priority_Based_Downlink_Policy.md in Configuring Network Event Delays). In this case, I would recommend VideoPriorityBasedPolicyConfig.StableNetworkPreset, which tries to delay the downward movement and speed up the recovery. However, we found that this configuration should have more impact, so I would wait until #1921 to experience this configuration. We can leave that question open until then, :). The Amazon Chime web application supports the following web browsers. We do not currently support mobile browsers. To open the Amazon Chime web app, sign in to app.chime.aws/ in a supported browser.
Let`s move on to how you can easily and continuously monitor the performance of your Amazon Chime network. By default, the SDK uses NScaleVideoUplinkBandwidthPolicy, which monitors the number of meeting participants and automatically reduces maxBandwidthKbps as the number of remote video thumbnails increases. This can be customized by implementing a VideoUplinkBandwidth policy and setting it in the MeetingSessionConfiguration class. If possible, profile devices that have performance characteristics similar to those you expect from your end users. By default, the SDK uses AllHighestVideoBandwidthPolicy, but VideoAdaptiveProbePolicy is used when simulcasting is enabled. AllHighestVideoBandwidthPolicy subscribes to the best video quality of all participants and VideoAdaptiveProbePolicy tries to subscribe to videos based on the browser`s downlink estimate and delete videos if there is insufficient bandwidth. Amazon Chime users who join meetings through a SIP or H.323 room system. Steps are needed to ensure that room systems can join Amazon Chime meetings and that their access to the media subnet is not blocked by a firewall. The following destinations and ports are required if you are running Amazon Chime in your environment. If you haven`t already, get a free trial of Obkio`s network performance monitoring solution today! Hi @JunedBrilworks, unfortunately, estimating browser bandwidth can be a bit tricky, and although we have changed our logic to wait for it to see packet loss, among other things, to try to make it less sensitive, it still depends on the actual bit rate received, which is why the active logic of the speaker to change the resolution can crash it from time to time, if they lose a small package at the same time.