Cisco Explorer 1540 Specifications Page 379

  • Download
  • Add to my manuals
  • Print
  • Page
    / 924
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 378
6-187
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
AnnunciatorNoMoreResourcesAvailable
No more Annunciator resources available.
Annunciator resource allocation failed for one or more of the following reasons: all Annunciator
resources are already in use; there was a codec or capability mismatch (such as the endpoint using one
type of IP addressing such as IPv6, while the Annunciator supports only IPv4) between the endpoint and
the Annunciator resource; not enough bandwidth existed between the endpoint and the Annunciator.
Facility/Sub-Facility
CCM_CALLMANAGER-CALLMANAGER
Cisco Unified Serviceability Alarm Definition Catalog
CallManager/CallManager
Severity
Warning
Parameter(s)
Media Resource List Name(String)
Recommended Action
If all the resources of the Annunciator are already in use, check to be sure that all the Annunciators 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 of the cluster. To check the registration
status go to the Media Resources > Annunciator menu and click the Find button. It will display all the
Annunciators with their status, device pool, and so on.
Check the status field to see 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 before the Publisher goes down.
Because the Subscriber may not be able to write to the database, the devices may still display 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 Annunciator allocation can fail due to codec mismatch or capability mismatch between the endpoint
and the Annunciator. If there is a codec mismatch or capability mismatch (such as the endpoint using
IPv6 addressing but Annunciator supporting only IPv4), an MTP or transcoder should be allocated. So,
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.
The Annunciator allocation may even fail after checking the region bandwidth between the regions to
which the held party belongs and the region to which the Annunciator 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
History
Cisco Unified Communications
Release Action
8.0(1) Changed severity level from Error to Warning.
Page view 378
1 ... 378 379 380 ... 924

Comments to this Manuals

No comments