Cisco CallManager attempts to stream the first MoH resource in the MRG to the device. If the first
resource is unavailable (due to server failure or lack of resources), Cisco CallManager then attempts to
use the next MoH resource in the MRG.
both transport types to ensure MoH redundancy for all endpoints in the network.
and critical real-time applications such as voice are not delayed or dropped. To ensure proper QoS for
voice traffic, the streams must be marked, classified, and queued as they enter and traverse the network
to give the voice streams preferential treatment over less critical traffic. MoH servers automatically mark
audio stream traffic the same as voice bearer traffic, with a Differentiated Services Code Point (DSCP)
of EF (ToS of 0xB8). Therefore, as long as QoS is properly configured on the network, MoH streams
will receive the same classification and priority queueing treatment as voice RTP media traffic.
deployed and configured, can support the anticipated call volume of the network. For this reason, it is
important to be aware of the hardware capacity for MoH resources and to consider the implications of
multicast and unicast MoH in relation to this capacity.
reached these limits, additional load could result in poor MoH quality, erratic MoH operation, or even
loss of MoH functionality.
MCS 782x (All models)
MCS 7830 (All models)
SPE-310
HP DL320
IBM xSeries 33x (All models)
G.729a
Wideband audio
20 MoH sessions
50 MoH sessions
MCS 7845 (All models)
HP DL380
IBM xSeries 34x (All models)
G.729a
Wideband audio
20 MoH sessions
250 MoH sessions