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

Welcome to Cisco Support Community. We would love to have your feedback.

For an introduction to the new site, click here. And see here for current known issues.

New Member

Moh not in use - gives errors anyway

We are not using Moh on our CallManager 3.2, however, everytime someone is put on hold, the Application Event Log records this error: UNKNOWN_ALARM:MohNoMoreResourcesAvailable [source: Cisco CallManager, Event ID: 3]

Everything works as expected but our logs are jammed full! Any ideas on how to get rid of this error?

1 ACCEPTED SOLUTION

Accepted Solutions
Silver

Re: Moh not in use - gives errors anyway

If you are running CallManager 3.3(2) the following bug might exlain this behavior.

CSCeb54528 Bug Details

Headline MohNoMoreResourcesAvailable errors when MoH is not configured

First Found-in Version 3.3(2)

First Fixed-in Version 3.3(2)FP02, 3.3(3.8), 3.3(3)ES04, 3.3(2)ES39, 3.3(3)SR02, 3.3(2)FP1.6, 3.3(2)ES49

Symptom:

The following error is logged to the Application Event Log

Event Type: Error

Event Source: Cisco CallManager

Event Category: None

Event ID: 3

Date: 7/2/2003

Time: 2:03:36 AM

User: N/A

Computer: ServerName

Description:

Error: UNKNOWN_ALARM:MohNoMoreResourcesAvailable -

App ID: Cisco CallManager

Cluster ID: CMName-Cluster

Node ID: x.x.x.x

Explanation:

Recommended Action: .

Condition:

This has been observed in CallManager version 3.3(2) Support Patch C. It has

seen in the latest Engineering Special at the time of this submission,

3.3(2)ES34. This BUG is related to having the IP Voice Media Streaming

Application

deactivated.

Workaround:

The only workaround is to enable MoH.

5 REPLIES
Gold

Re: Moh not in use - gives errors anyway

Turning off the MOH services without deconfiguring the system for MOH will result in this exact error; basically that CallManager searched for a MOH server and wasn't able to find one, and fell back to tone-on-hold.

Look on the phones themselves and on their device pools to see if they have User or Network MOH sources defined. If they do, redefine them as "". For good measure, make sure that the Media Resource Group List and its underlying Media Resource Groups contain no MOH servers, otherwise I think CallManager might fall back to the clusterwide-default MOH source, which is usually #1.

New Member

Re: Moh not in use - gives errors anyway

Everything you have suggested is the way it is set; the default Device Pool is in use and has "none" as it's "User Hold Audio Source" and "Network Hold Audio Source". In fact, there are no other options. I've looked at a couple phones specifically and they are set the same way, then retested and the errors came back.

Same with MRG and MRGL's - Moh is not included.

Any other ideas? Thanks for your time.

Silver

Re: Moh not in use - gives errors anyway

If you are running CallManager 3.3(2) the following bug might exlain this behavior.

CSCeb54528 Bug Details

Headline MohNoMoreResourcesAvailable errors when MoH is not configured

First Found-in Version 3.3(2)

First Fixed-in Version 3.3(2)FP02, 3.3(3.8), 3.3(3)ES04, 3.3(2)ES39, 3.3(3)SR02, 3.3(2)FP1.6, 3.3(2)ES49

Symptom:

The following error is logged to the Application Event Log

Event Type: Error

Event Source: Cisco CallManager

Event Category: None

Event ID: 3

Date: 7/2/2003

Time: 2:03:36 AM

User: N/A

Computer: ServerName

Description:

Error: UNKNOWN_ALARM:MohNoMoreResourcesAvailable -

App ID: Cisco CallManager

Cluster ID: CMName-Cluster

Node ID: x.x.x.x

Explanation:

Recommended Action: .

Condition:

This has been observed in CallManager version 3.3(2) Support Patch C. It has

seen in the latest Engineering Special at the time of this submission,

3.3(2)ES34. This BUG is related to having the IP Voice Media Streaming

Application

deactivated.

Workaround:

The only workaround is to enable MoH.

New Member

Re: Moh not in use - gives errors anyway

Thank you... that is it. We are in fact running 3.3(2) and that describes it exactly!

New Member

Re: Moh not in use - gives errors anyway

Just to add to this, this bug is fixed in CM 3.3(3) SR2.

140
Views
5
Helpful
5
Replies
CreatePlease login to create content