Cisco MCS-7825-H3-IPC1, Руководство по обслуживанию

Страница: 415 / 974

6-181
Cisco Unified Communications Manager Managed Services Guide
OL-22523-01
Chapter 6 Cisco Unified Serviceability Alarms and CiscoLog Messages
Error-Level Alarms
To avoid this situation, set the priority of the media resources appropriately. This can be done only in the
Media Resource Group List and not in the Default List of the media resources. In any Media Resource
Group List all the Media Resource Groups have different priorities and during allocation the first Media
Resource Group is checked for availability of the requested type of the media devices. The first Media
Resource Group in the Media Resource Group List will have the highest priority, then the second one
and so on. To check all the Media Resource Groups and their priority go the Media Resources and Media
Resource Group List of Cisco Unified CM Administration page and click the appropriate Media
Resource Group List and check the Selected Media Resource Groups; the priority decreases from top to
bottom. Position the MTP or transcoder that you want to be selected for the basic functionalities in the
higher priority Media Resource Groups whereas the ones with more rare functionality can be positioned
in the Media Resource Groups with lower priority. RSVP Agent allocation may fail due to codec
mismatch between the end point and the RSVP Agent or MTP/transcoder.
A solution may be to configure the MTP/transcoder with all the supported codecs (as specified in the
user guide of the MTP/transcoder), but be aware that doing so might result in too much bandwidth being
allocated for calls. You'll need to weigh different factors such as the total amount of available bandwidth,
the average number of calls, approximate bandwidth use per call (not involving MTP/transcoder), and
so on, and accordingly calculate the maximum bandwidth that can be allocated per call involving an
MTP/transcoder and take that into consideration when configuring the supported codecs in the MTPs
and transcoders. A good idea is to configure the media devices with all the supported codecs and set the
region bandwidths to restrict too much bandwidth usage (refer to the Unified CM documentation for
details on region and location settings).
Also, there may be codec mismatch between the endpoint and the MTP/transcoders after considering the
region bandwidth between the MTP/transcoder and the endpoint. 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.
Another possible cause that an MTP/transcoder did not get allocated is because there was not enough
available bandwidth for the call. This can happen if the MTP/transcoder and endpoint belong to different
locations and the bandwidth that is set between the locations is already in use by other calls. Examine
the bandwidth requirements in your deployment to determine whether bandwidth between the locations
can be increased. However, note that increasing the bandwidth between these two locations means that
you may need to reduce the bandwidth between other locations.
Refer to the System Guide, SRNDs, and related Unified CM documentation for more details. Be aware
that reducing the bandwidth or removing the higher bandwidth codecs from configuration may result in
poor voice quality during call. Consider increasing the total amount of network bandwidth. Finally, if
RSVP Agent allocation fails due to MTP/transcoder not supporting RSVP functionality or capability
mismatch or all the resources being in use, consider installing additional MTP or transcoder devices
which support RSVP functionality.
RTMT_ALERT
A Real-Time Monitoring Tool (RTMT) process in the AMC service uses the alarm mechanism to
facilitate delivery of RTMT alerts in the RTMT AlertCentral or through email.
Cisco Unified Serviceability Alarm Definition Catalog
System/RTMT
Severity
ERROR