- For conference with 4 or less video feeds:

The required bandwidth for each participant (in Mbps) = (A*1+B*0.172)*1.2+0.1

A is the number of 1080p video feeds (A = 0 or 1);

B is the number of participants excluding A. (B= Total number of participants - A);

1.2 represents the consideration of extra video bandwidth cost such as packet headers;

0.1 represents the bandwidth for audio.

- For conference with more than 4 video feeds:

The required bandwidth for each participant (in Mbps) = X*0.172*1.2+0.1

X is the number of total participants;

1.2 represents the consideration of extra video bandwidth cost such as packet headers.

0.1 represents the bandwidth for audio.

- For conference with screen sharing on:

The required bandwidth for each participant (in Mbps) = (X*0.172+0.512)*1.2+0.1

X is the number of total participants,

1.2 represents the consideration of extra video bandwidth cost such as packet headers.

0.1 represents the bandwidth for audio.

Note:

The above calculation applies to bandwidth required for each participant. To estimate the bandwidth required for UCM6300 series, please consider the number of participants and add them together.

For 1080p video: 1Mbps/15fps.

For 720p video: 512kbps/15fps.

For 360p video, 172kbps/15fps.

For screen sharing, 512kbps/5fps.

The above configurations can be modified per user’s preferences and it may impact the overall max number of allowed conference attendees depending on the trade-offs between video quality and max number of attendees.

Navigate to PBX Settings->General Settings and configure the "Conference Voice Quality" option. If set to “Full Band HD Voice”, 48KHz sampling rate will be used for Opus codec and the audio quality using Opus will be notably better.

Note:

When "Full Band HD Voice" is selected, "Max Number of Video Feeds" in the Call Features->Video Conference->Conference Settings page is currently limited to 4. Pending enhancements in future firmware releases may possibly lift this performance limit.

UCM6300 series use rsync and port 873 for LDAP syncing. There is currently no way to modify this port number. Regardless of this, UCM6300 series can still retrieve LDAP phonebooks from the UCM6200 series/UCM6510 without needing to modify the LDAP sync port on the UCM6200 series/UCM6510. However, the UCM6200 series/UCM6510 are currently unable to retrieve phonebooks from UCM6300 series. This will be addressed in a later UCM6200 series/UCM6510 firmware.

- NACK:

By enabling negative-acknowledgement (NACK), the UCM6300 series will retransmit packets that have been lost in the initial transmission to repair the media stream.

- NACK+RTX:

It’s a mechanism based on NACK, which means it relies on RTCP packets to find out which packets are lost first. For NACK, it will retransmit based on the original packet. With RTX, a special payload is used to retransmit the packets that a NACK request indicated as lost. Retransmitted packets are sent in a different stream from the original media stream. The payload of the retransmission packet contains the payload header of the retransmission followed by the payload of the original packet. RTX retransmits using an extra ssrc, which will be marked in SDP during negotiation.

NACK+RTX can have more accurate statistics and it’s recommended for RemoteConnect users if there is packet loss during usage.

Enabling NetEQ on the UCM6300 series helps reduce the effects of packet loss on audio received by the UCM.

It is a dynamic jitter buffer and error concealment algorithm used for hiding the negative effects of network jitter and packet loss. It helps keep latency as low as possible while maintaining the highest voice quality.

Note:

Enabling NetEQ will help with minimizing the effects of packet loss on audio received by the UCM6300 series. If there is packet loss in the audio sent from UCM to an endpoint, then the endpoint will need to handle it with its own packet loss mitigation implementation. NetEQ is used in WebRTC for audio QoS purposes. As such, UCM6300 series’ Grandstream Wave, which uses WebRTC, comes with NetEQ support.

This is because the UCM6300 series use self-signed certificate for web server by default. To avoid this issue, you could use UCM RemoteConnect plan for the UCM6300 series, which will provide domain name for the UCM. When users access Wave Web or admin accesses UCM Web portal, the web server will trust it and allow access.

You could also purchase domain name and certificate from other parties. Then upload the certificate to UCM6300 series web UI->System Settings->HTTP Server->Certificate Settings.