Preview Tool

Cisco Bug: CSCup29823 - Edge: status of UCM neighbour zones is misleading / optimistic

Last Modified

Nov 27, 2020

Products (3)

  • Cisco TelePresence Video Communication Server Software
  • Cisco TelePresence Video Communication Server Model
  • Cisco Expressway

Known Affected Releases


Description (partial)

On the /cucmlookup and /zones pages the SIP status of neighbour zones to UCMs is shown. On the /editzones it has the State.

Edge neighbour zones towards UCMs are configured with Monitor peer status set to "No".

Provided the VCS can resolve the Peer address to an IP address it shows the status / state as "Active". 

An administrator I might be forgiven for assuming that this meant that the VCSc could happily communicate with the UCM, and indeed was doing so.

For edge zones: 
Either the VCSc should say something like "address resolvable" instead of "Active", or it should actually try to communicate with the UCM to determine that as a minimum establish a connection to the server. This would help a little with diagnosing routing issues, invalid DNS settings, certificate problems (for TLS connections) etc.

This could be achieved by setting the Monitor peer status to "Yes".

Otherwise the VCS admin won't see a problem until an Edge device fails to connect.

VCS / Expressway running MRA
Bug details contain sensitive information and therefore require a account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.