Why are remote sites that use Locations-Based Admission Control unable to receive Music On Hold in the initial release of Cisco CallManager 3.x and 4.x?
A. If you use Locations-Based Call Admission Control, users at remote sites (for example, across a WAN link) cannot use MoH. Remote site users cannot use this feature because bandwidth calculations across location boundaries do not take into account MoH streams. In place of MoH, these users receive Tone on Hold (ToH), and bandwidth calculations are then correct.
Related Questions
- Why are remote sites that use Locations-Based Admission Control unable to receive Music On Hold in the initial release of Cisco CallManager 3.x and 4.x?
- How does Music On Hold work after the Cisco CallManager 3.x and 4.x maintenance release?
- Which sign tend to hold/control their temper before exploding in anger?
