I am running CCM 5.1 (unicast) and running into the issue where the MOH source only works for a few phones (ie: operator). If i dial the operator and get put on hold, i will hear the MOH file so i know the file is working.
however, when a different user dials the operator and gets put on hold, she doesnt hear anything.
i have double checked the settings on her phone as well as mine and they match but she doesnt hear the MOH file when she gets put on hold.
This also happens on other extensions as well. Is there a global setting for MOH where it is applied to all phones in the cluster?
If i go to Find and list Music On hold audio files, it lists the moh file i want as In use for file status.
MTP is a medie resource under MRG which belongs to MRGL, MTP has nothing to do with your issue. You need to ensure that the MRGL assigned to the phone in question has Device Pool that has MRGL --> MRG which lists the MOH server. The MOH can be assigned to multiple MRGs and MRGs can be assigned to multiple MRGLs, same thing with Device Pool/MRGL.
I would not advise to blindly configuring MRG/MRGLs as these control which resources are invoked by whom and a good planning need to take place, especially if you have remote locations.
You lost me, your original post was about MOH, yet you are concerned with MTP. These have nothing to do with each other, Media Termination Potin (MTP) has nothing to do with MOH.
Perhaps you mean MRGL as that's what gets assigned to Device Pool, then yes adding MRGL to Device Pool will solve your issue, however as I pointed out eariler ensure that the MRGL is local with local resoures preferred.
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...
The below trick might come handy when you have to add a new node to a cluster but you don't have or is unsure of the security password for the publisher. This procedure has been around for ages.
1) Login into the CLI of the Publisher.