Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 

After a new Hardware Conference Bridge is created in Cisco CallManager 3.x or 4.x, the Bridge fails to register with the correct Cisco CallManager

Core Issue

When a new Hardware Conference Bridge is configured in the Cisco CallManager located in a different site, the Bridge fails to register with the Cisco CallManager at that site. Instead, it registers with the Cisco CallManager located in the main site, which uses media resources over the wide area network (WAN) and consumes bandwidth.

Resolution

The show sccp connections details command displays the Skinny Client Control Protocol (SCCP) connection details, which includes the Bridge information.

In order to resolve this issue, make sure the Hardware Conference Bridge is registered to the correct Cisco CallManager. In order to register the Bridge to the local Cisco CallManager, create a new media resource group (MRG) and media resource group list (MRGL) and assign the bridge to the local MRGL.

Refer to Configuring Enhanced Conferencing and Transcoding for Voice Gateway Routers.

1429
Views
0
Helpful
0
Comments