Woof! On Wed, 14 Oct 2009 15:55:27 -0400, Damian Krzeminski <[email protected]> wrote:
> What occurred to me is that in 4.2 if administrator wants any of the > features provided by sipXivr they need to enable Voicemail role. In 4.0 > one could have MoH and use external voicemail, or use AutoAttendant and > no > voicemail. In 4.2 it's going to be all or nothing. Well, yes--and no. Just because sipXivr is running, one should still be able to use external voicemail, and one should still be able to use AA but not VM, or MOH but not AA or VM. Running the service shouldn't be the same as using the service--in better words: Just because sipXivr is running and COULD provide all of MOH, AA and VM, it won't unless calls are directed to it for those purposes. Perhaps it's the "Voicemail" role that is misnamed, and should be "IVR Services" roll instead. Or one could call it "Unified Messaging" Role (NOT!!!!!) Perhaps the features need to be split out from a service/process. If a particular feature (aka role) is selected, the process that performs that role is started...but one process can have more than one feature. This was previously the case with sipXvxml (AA and VM), and sipXpark (MOH and Park), so nothing new there. But conceivably, one can have AA running today on host "A", VM running on host "B", and MOH running on host "C". All three would run sipXivr and FreeSWITCH, but the mappingrules/aliases would be the difference between which box took which calls. --Woof! _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev sipXecs IP PBX -- http://www.sipfoundry.org/
