Using Tenant Partitioning, you can assign a separate music source to each tenant partition. A caller hears the music when a user places a call on hold. The tenant number that you assign to the called extension usually determines the music source that the user hears. With this capability, you can customize the music, or the messages, for the business needs of each tenant partition.
If the COR of the user extension that places the call on hold supports music-on-hold, a caller on hold hears the music source that is assigned to the partition at which the call initially terminates. For example, if the system first routes a call to an Communication Manager Messaging automated attendant, and then routes the call to the appropriate tenant partition, the caller who is on hold hears the music source of the Communication Manager Messaging automated attendant. The caller who is on hold does not hear the music source of the tenant partition to which the system routes the call. Likewise, if a caller in tenant partition 2 makes an out-going call that uses the trunk groups of tenant 3, the caller hears the music source that is assigned to tenant 3. If the COR of the called extension does not support music on hold, the caller hears nothing.
The maximum number of allowed music sources is the same as the maximum number of allowed tenant partitions. More than one tenant partition can use each music source.
The table shows which music-on-hold types that you can assign to each tenant partition.
Table 1: Types of music-on-hold
Type |
System response for a call who is on hold |
none |
Silence |
tone |
System-wide administered tone |
music |
This is the type of music that is associated with the administered port. The number of allowed music sources equals the number of allowed tenant partitions. Each partition can have its own music source. |