Guest

Cisco Unified Communications Manager (CallManager)

Troubleshooting MOH Registration Issues with Cisco CallManager

Document ID: 100269

Updated: Jan 09, 2008

   Print

Introduction

This document explains the recommended solutions when the Music On Hold (MoH) unregisters and re-registers with the Cisco Unified Communications Manager (CallMananger).

Prerequisites

Requirements

Cisco recommends that you have knowledge of Cisco Unified Communications Manager (CallManager).

Components Used

The information in this document is based on Cisco Unified Communications Manager (CallManager) 4.x/5.x/6.x/7.x.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Problem: kDeviceMgrRegisterWithCallManagerError: Connection error

The MoH server unregisters and re-registers intermittently with Cisco Unified Communications Manager, and the kDeviceMgrRegisterWithCallManagerError: Connection error with Cisco CallManager error message appears in the event log:

Event Type:	Error
Event Source:	Cisco IP Voice Media Streaming App
Event Category:	None
Event ID:	3
Date:		8/9/2007
Time:		8:19:10 AM
User:		N/A
Computer:	Cisco-123450B4BDC
Description:
Error: kDeviceMgrRegisterWithCallManagerError - Connection error with Cisco
CallManager.
  Trace Name: [CFB][172.10.1.2]
  App ID: Cisco IP Voice Media Streaming App
  Cluster ID: Cisco-123AF0B4BDC-Cluster
  Node ID: 172.10.1.2

Explanation: Device manager registered with the specified Cisco CallManager
and got a socket error or disconnect.

Recommended Action: No action is required; device recovery will handle this.

Solution

This error message is most likely a result of a problem with keepalives between the MoH server and the Cisco Unified Communications Mananger.

In order to overcome this issue, complete these steps:

  1. Reboot the Voice Media Streaming Application. Stop and start the IP Voice Media Streaming Application in the Control Center.

    Refer to Control Center for more information on how to start and stop various Cisco CallManager services.

  2. Reset the MoH server.

    Refer to the Resetting a Music On Hold Server section of Music On Hold Server Configuration for information on how to reset the MoH server.

Problem: MOH Server does not get Registered

After you upgrade from Cisco CallManager 4.1(3) to Cisco Unified Communications Manager 6.1(2), the MOH server is not registered with the Cisco Unified Communications Manager.

Solution

This isssue can occur when the Run Flag parameter under the MoH Server Configuration page is set as No. Set the Run Flag to No on the MoH server in order to disable MoH.

In order to resolve this issue, go to the Cisco Unified CM Administration page and choose Media Resources > Music on Hold Server and set the Run Flag to Yes. mohregistererror-01.gif

Related Information

Updated: Jan 09, 2008
Document ID: 100269