Guest

Preview Tool

Cisco Bug: CSCvh97869 - support a dedicated management interface for voice gateways in a future version of PCA

Last Modified

Feb 22, 2018

Products (1)

  • Cisco Prime Collaboration

Known Affected Releases

11.6

Description (partial)

Symptom:
Customer would like to use two loopback address on a voice gateway. First loopback would be dedicated for management (SNMP, SSH etc.), the 2nd one for voice traffic (MGCP, SIP, SCCP, RTP etc.).

Currently, PCA see both interfaces when discovering the gateway with the MGCP loopback but unable to get SNMP trap information from the devices because gateway uses the management loopback for SNMP.  If the same device is instead manually discovered using the management loopback, MGCP TI traffic utilisation does not work.

Feature request : customer wants PCA to manage the device using the dedicated management loopback and still get T1 MGCP trunk utilisation information or at the very least manage the device using the MGCP loopback and be able to recognize traps sent from the management loopback

Conditions:
enhancement request
Bug details contain sensitive information and therefore require a Cisco.com 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.