+1
> -----Original Message----- > From: [email protected] [mailto:sipx-dev- > [email protected]] On Behalf Of Scott Lawrence > Sent: Tuesday, March 17, 2009 10:01 AM > To: Paul Mossman > Cc: [email protected] > Subject: Re: [sipX-dev] Using FreeSWITCH as the MOH server > > On Tue, 2009-03-17 at 09:44 -0400, Paul Mossman wrote: > > Hi all, > > > > Woof has pointed out that it would be pretty simple to implement a > MOH > > server with FreeSWITCH, though most of the effort would be getting > the > > new URI into sipXconfig: > > > > http://track.sipfoundry.org/browse/XECS-2312#action_36666 > > > > This would resolve XECS-2312. Not a huge benefit in itself, but I > > think we in general want to maximize our use of FreeSWITCH for media > > services. > > > > Before I raise an enhancement JIRA, does anyone have objections > and/or > > suggestions? > > I think it's too late in the release cycle to completely replace our > MOH > service, and that "fixing" the ability to put a conference on hold (and > play the moh audio into it) does not come close to justifying the > change. Indeed, I think that one could argue that kicking a user out > for trying to put a conference on hold is a feature (only 1/2 :-) ). > > I like the idea of moving the MoH service to Freeswitch post-4.0, but > not now. > > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev > Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev _______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
