If there was the ability to create a music-on-hold context when creating a new user/extension, then each user would have the ability to select their own music for personal conference rooms.
under the current design this would be problematic as every time the UI creates a new MOH class it locks out the reload option and puts PBX Manager in a pending restart mode. Changes requiring reload would not take effect until a restart could occur. With MTE this results in massive amount of support calls where changes are not taking effect.
additionally I think there is a limit to the number of unique moh classes, much less than 10,000 extensions I am sure. MOH is a resource module, which is unlike other module types. One would have to test the impact of 1000 MOH classes always running to see what sort of load this would create.
Thirdlane/Asterisk Support available
On a similiar note, is it possible to have a seperate parking area for each extension?
currently it isn't even possible to have a seperate parking area for each tenant without 3rd party software. Multi-context parking lots is slated for 1.6.1
Now that I think about it, a per extension parking lot doesnt make much sense does it? I mean if nobody else is capable of retrieving that call, wouldn't it be called on-hold?
The reason I think having separate parking areas for each extension would be a great feature is that each user can then have their own music/ announcements. The engineering guys can have their announcements and the sales guys can have their own music/announcements. To me that seems very useful and practical. This can be done on either a departmental level or on an individual level.
a seperate parking context for each extension means that no one else could unpark it, and therefore completely neuters the concept of parking.
Yeah, the light just went on. I thought it was a valid idea, but now I see it is not.