Andy Spitzer wrote: > Woof! > > On Mon, 12 Oct 2009 10:57:26 -0400, Damian Krzeminski > <[email protected]> wrote: > >> Andy Spitzer wrote: >>> Woof! >>> >>> On Fri, 09 Oct 2009 17:35:45 -0400, <[email protected]> wrote: >>> >>>> XX-6640 sipXivr renamed to "Voicemail and Auto Attendant" >>> >>> Also "Music On Hold", and soon "Personal Assistant" (Or whatever it will >>> be called) and "Conference Recording" (dunno why that's in there).. >>> >>> Hmm, lets just call it "Bag 'o Stuff" >>> >> I think those names are the compromise between the technical accuracy and >> readability anyway. I am not sure if "Bag 'o Stuff" would work - although >> we could add it to h4©k3r localization if someone writes it. >> >> That brings a question: Do we really need to pack all these functionality >> into a single service. >> That historically lead to various problems with either configuration or >> deployment. "Music on Hold" has just moved from "Park Service" so that >> does >> not make things worse - just different. >> But is "Personal Assistant" really there as well? >> D. > > Voicemail, AA and MOH all use the same FS "i...@..." extension to gain > control over the IVR and use FS as a media server. It makes sense for all > them to be in the same service as they leverage the same FS > configuration. They could be split out into their own services easily > enough. > > Personal Assistant got (will be) added because in phase 2 IVR will be > required to handle call screening, voice announce, etc., but phase 1 is > all about XMPP openfire integration. Does it make sense for this to be in > sipXivr...some hard thought should be given to this. > > Conference Recording got added...I don't know why. I guess someone > thought "conferencing uses FS" thus "sipXivr"! But the conference service > works on a totally different way than sipXivr, and scales differently too. > > I think the real answer is that adding to an existing service is MUCH > easier than creating a new one. Dealing with RPM's, spec files, > autoconfig, "magic" makefiles, sipxsupervisor XML files, etc. is > daunting. Adding the configuration for a new service takes much more time > than editing and existing one. For Java code, adding a thread to an > existing JVM is a snap compared with all that. For new stuff, its quick > and dirty and easy--and thus abused. >
I was reviewing notes from sipXconfig demo meeting - one of the requests is to move sipXivr to "Voicemail" bundle (from "Primary SIP Router" bundle). That's a trivial change and I am going to do that. 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. D. _______________________________________________ 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/
