Cisco Explorer 1540 Specifications download pdf (Page 435)

100

101

6-243

Cisco Unified Communications Manager Managed Services Guide, Release 8.0(1)

OL-20105-01

Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages

Warning-Level Alarms

of MOH server are already in use; No matching codecs or capability mismatch between the held party

and MOH server; Not enough bandwidth between the held party and MOH source; No audio stream

available for the MOH server.

Facility/Sub-Facility

CCM_CALLMANAGER-CALLMANAGER

Cisco Unified Serviceability Alarm Definition Catalog

CallManager/CallManager

Severity

Warning

Recommended Action

If all the resources of the MOH servers are already in use, check to be sure that all the MOH servers that

belong to the Media Resource Groups of the indicated Media Resource Group List and Default List are

configured and registered in all the applicable Unified CM nodes. To check the registration status go to

the Media Resources > Music On Hold Server menu and click the Find button. It will display all the

MOH servers with their status, device pool, and so on.

Check the status field to discover whether it is registered with Unified CM. Note that the display on the

status field is not a confirmation that the device is registered to Unified CM. It may happen in a Unified

CM cluster that the Publisher can only write to the Unified CM database and the Publisher goes down.

Because the Subscriber may not be able to write to the database, the devices may still display as

registered in Unified CM Administration after they are actually unregistered. However, if the Publisher

is down that should generate another alarm with higher priority than this alarm.

The MOH allocation can also fail due to codec mismatch or capability mismatch between the endpoint

and the MOH server. If there is a codec mismatch or capability mismatch (such as the endpoint using

IPv6 addressing but MOH server supporting only IPv4), an MTP or transcoder should be allocated. If

the MTP or transcoder is not allocated then either MediaResourceListExhausted (with Media Resource

Type as Media termination point or transcoder) or MtpNoMoreResourcesAvailable alarm will be

generated for the same Media Resource Group List and you should first concentrate on that alarm.

The MOH allocation may even fail after checking the region bandwidth between the regions to which

the held party belongs and the region to which the MOH server belongs. Increasing the region bandwidth

may be a solution to the problem, but that decision should be made after careful consideration of the

amount of bandwidth you're willing to allocate per call between the set of regions.

You'll need to weigh different factors such as the total amount of available bandwidth, the average

number of calls, the average number of calls using the MOH servers, approximate bandwidth use per

call, and so on, and accordingly calculate the region bandwidth. Another possible cause is that the

bandwidth needed for the call may not be available. This can occur if the MOH server and endpoint

belong to different locations and the bandwidth that is set between the locations is already in use by other

calls.

History

Cisco Unified Communications

Release Action

8.0(1) Severity changed from Error to Warning.

1 ... 434 435 436 ... 924

Comments to this Manuals

No comments

Cisco Explorer 1540 Specifications Page 435

Comments to this Manuals

Related products and manuals for Digital Video Recorders (DVR) Cisco Explorer 1540