Different MOH sources for internal and external calls

[tweege]

have comm mgr 5.2. is it possible to have diff music on hold sources for internal and external calls? this is for all calls, not just ones running through a vector or anything like that.

 

[kyle555]

Good question. I know trunks and stations can each have their own tenant, and that you can set MOH on a per tenant basis.

I don't actually know if MOH is from the tenant of the station putting the call on hold, or the tenant of the thing being put on hold. If its the former, then no, you can't. If it's the latter, then yes, you can.

It would seem signs point to maybe...

"The tenant number that you assign to the called extension usually determines the music source that the user hears. "
"The caller who is on hold does not hear the music source of the tenant partition to which the system routes the call."

To me, that means if you come in a trunk and go to voicemail autoattendant, and to a station that places you on hold, you'll hear the voicemail trunk's tenant's music, not the music of the station that placed you on hold.

In the same vein, if a station on TN1 called a station in TN2, they should hear the music of TN1.
So, shouldn't a call terminating on trunk 1 in TN1 hear MOH1 if it terminates on station 2 in TN2 with MOH2? If so, having all your trunks in 1 tenant and all your stations in another should do it.

I wish I had the free time to test that to know for sure!

https://downloads.avaya.com/css/P8/documents/100171721

Multiple Music-on-Hold with Tenant Partitioning

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.