System information

Polycom® Unified Communications Deployment Guide for Cisco Environments
58
CUCM SIP endpoint calls to DMA H323 endpoints may be denied due to
bandwidth
Possible Cause: When DMA invokes its SIP_to_H323 gateway feature, it is forced to look at
Bandwidth settings for H323. The CUCM SIP Peer destination may not be defined in any Sites
in DMA (or RPRM if integrated), so it denies the call.
Workaround: Add the CUCM node’s subnet to the customer’s site topology. DMA doesn’t look
at bandwidth parameters for SIP calls – only H323. It is recommended to add the CUCM SIP
Peer to the Site Topology.
Calls from a Cisco CTS are not able to connect to a DMA registered endpoint or
RMX
Possible Cause: The Cisco CTS IP Address may not be defined in the Site Topology.
Workaround: Add the Cisco CTS’s subnet or IP to the customer’s site topology in DMA under
Network => Site Topology => Sites or if DMA is integrated with RealPresence Resource
Manager, add it to the Site Topology there.
Calls from a Cisco CTS are not able to connect to a DMA Virtual Meeting Room
Possible Cause: DMA conference settings may be limiting the maximum bit rate for calls.
Workaround: In DMA under Admin => Conference Manager => Conference Settings, check
that the Default maximum bit rate (kbps) is at least 4096 for CTS immersive connectivity.