Hi Thanks for that - my comment around using SIPXConfig was more because it uses a single port. Having a single port makes life a lot easier, especially if you want to expose any of the services outside your internal network. This is aligned with your future thinking where the web services interface is decoupled from the various SIPX modules so I guess in time...
Also, do these all work in current 4.2 version? Regards Justin On Tue, Feb 15, 2011 at 11:58 PM, George Niculae <[email protected]> wrote: > On Tue, Feb 15, 2011 at 12:53 PM, Justin Menga <[email protected]> > wrote: > > Hi > > > > I notice some capability to add voicemail deletion via web services has > been > > created - http://track.sipfoundry.org/browse/XX-9036 - > > Right, check this: > http://wiki.sipfoundry.org/display/sipXecs/Web+Service+APIs > (http://wiki.sipfoundry.org/display/sipXecs/Voicemail+Web+Service) > > > better IMO if it was exposed via the SIPXConfig RESTful API, given this > > already provides basic voicemail support via RSS and supports other > > functions. > > The intent is to unify all of them but not under sipXconfig, see: > http://wiki.sipfoundry.org/display/sipXecs/Web+Service+API+Unification > > George > _______________________________________________ > sipx-dev mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-dev/ >
_______________________________________________ sipx-dev mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-dev/
