How can an administrator stop Cisco Unified Communications Manager from advertising the OPUS codec for recording enabled devices?
Click on the arrows to vote for the correct answer
A. B. C. D.D.
https://www.cisco.com/c/en/us/support/docs/unified-communications/unified-communications-manager-callmanager/211297-Configure-Opus-Support-The OPUS codec is a high-quality audio codec that is used for real-time communications such as voice and video calls in Cisco Unified Communications Manager (CUCM). However, in some scenarios, the OPUS codec may not be desirable or may cause issues, such as when recording calls. If recording is enabled in CUCM, the system will advertise the OPUS codec to all endpoints, including recording-enabled devices, which can cause issues with the recording software.
To prevent CUCM from advertising the OPUS codec for recording-enabled devices, an administrator can follow one of the following methods:
A. Route recorded calls through Cisco Unified Border Element because it does not support OPUS. This solution involves routing recorded calls through a Cisco Unified Border Element (CUBE) before sending them to the recording software. CUBE does not support the OPUS codec, so it will not advertise it to any devices. However, this solution may not be practical or feasible in all scenarios, especially if there are multiple recording solutions or if CUBE is not part of the network.
B. Go to the phone's configuration page and set Advertise OPUS Codec to be false. This solution involves going to the configuration page of each recording-enabled phone and disabling the "Advertise OPUS Codec" option. This option is located in the "Media Configuration" section of the phone's configuration page. Disabling this option will prevent the phone from advertising the OPUS codec to CUCM, which will then not advertise it to any other devices. This solution may be time-consuming and may require manual configuration for each phone.
C. Integrate the Cisco Unified CM with a recording solution that does not support OPUS. This solution involves integrating CUCM with a recording solution that does not support the OPUS codec. This can be achieved by using a third-party recording software that does not support OPUS or by configuring CUCM to use its built-in media resources (such as software conference bridges) for recording instead of external recording solutions. This solution may require additional configuration and may not be suitable for all scenarios.
D. In CUCM Service Parameters set "Opus Codec Enabled to Enabled for all Devices Except Recording-Enabled Devices. This solution involves changing the "Opus Codec Enabled" parameter in the CUCM service parameters. This parameter is located under the "Clusterwide Parameters (System - RTP)" section. By setting this parameter to "Enabled for all Devices Except Recording-Enabled Devices," CUCM will only advertise the OPUS codec to non-recording-enabled devices. This solution is the most straightforward and can be applied globally to all devices without requiring manual configuration.
In summary, there are several ways to prevent CUCM from advertising the OPUS codec for recording-enabled devices. The best solution depends on the specific scenario and requirements of the network. Solution D is the most straightforward and can be applied globally, but other solutions may be more suitable in certain scenarios.