>From the "Moh-uri" thread...
On Thursday, July 07, 2011 11:34 AM , Andy Spitzer <[email protected]> wrote: > The characters after the "~~mh~" have the following meanings: > (empty) use original park server music > (/var/sipxdata/parkserver/music/) > l use local_stream://moh (defined in local_stream.conf.xml) > p use portaudio_stream:// (defined in portaudio.conf.xml) > u{user} use per user music ({data}/moh/{username}) > n music source "None", so just hangup. Silence might also > work. Would it make sense to also have a "per-user group" (or per branch) MoH as well? This would be useful in cases where users at different physical locations (but on the same server) or in different departments needed to have different on-hold music/recordings. It would fill the gap between having to have users either set for the system-wide MoH, and having to set individuals' MoH over and over for a shared MoH recording that doesn't make sense for system-wide use. I was thinking that per-user group would probably be better than per-branch, since there is already a tab for MoH in user groups and an upload page similar to the user's MoH page could be added. An option to use the group MoH could be added to the "Audio Source" pulldown for the user MoH page. Besides adding an additional MoH uri to the aliases, adding group moh directories and related additions to the freeswitch XML templates, and customizations to the sipXconfig gui to configure these, what else would be involved?
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
