System information

Polycom® Unified Communications Deployment Guide for Cisco Environments
80
For more information and examples on DMA scripting capabilities, refer to the DMA
Operators Guide.
10 Click OK.
Troubleshooting
This section provides assistance in troubleshooting any issues you may have with Polycom
DMA SIP Peering with VCS.
VCS 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 VCS SIP Peer destination may not be defined in any Sites in
DMA (or RPRM if integrated), so it denies the call.
Workaround: Add the VCS 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 VCS SIP
Peer to the Site Topology.
Calls from a Cisco VCS-registered endpoint are not able to connect to a DMA
registered endpoint or RMX
Possible Cause: The Cisco VCS endpoint’s IP Address may not be defined in the Site
Topology.
Workaround: Add the Cisco VCS endpoint’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 DMA to VCS using SIP may get denied
Possible Cause: When DMA forms the SIP Invite, it will use the format:
<extension/host>@<IP_Address/DNS name of configured SIP Peer>. VCS may not like this and
may prefer to see <extension/host>@<VCS domain/sub-domain>.
Workaround: In DMA under the External SIP Peer configuration, in the Destination Network
field, fill in the domain/sub-domain that VCS is responsible for. For example: