Guest

Preview Tool

Cisco Bug: CSCsg39923 - Change MGCP gateway Domain Name only reset endpoints not whole gateway

Last Modified

Jul 04, 2017

Products (1)

  • Cisco Unified Communications Manager (CallManager)

Known Affected Releases

4.2

Description (partial)

Symptom:

Incoming and outgoing calls over an MGCP gateway fails randomly after changing gateway's domain name in CallManager.  Sometimes caller receives dead air.

Conditions:

The administrator changes the gateway domain name in CCM without stopping Gateway's mgcp service.

Related Community Discussions

VG224 - some ports show "unregistered" after changing domain name
hi, recently i have changed the domain name of a VG224, before the change, all ports shows "registered" from the CUCM. after I changed the domain name from VG224 and CUCM, the VG224 can be registered to CUCM, and some ports can register too...only serveral ports showing "unregistered" in the CUCM. But from the VG224, everything is normal. and call/ fax can be made successfully from those "unregistered" ports. anyone has idea what's going on? thanks.
Latest activity: Nov 18, 2013
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.