Scott wrote: > On Tue, 2009-07-14 at 08:56 +0200, Damian Krzeminski wrote: > > > SCS is a commercial product based on sipXecs, if your > Outlook add-on > > does not use any features that are SCS only it would be a great > > addition to sipXecs suite. > > I am sure users would be grateful to have this > functionality no matter > > how it's called but it does look a bit strange if we commit > the code > > that mentions SCS in many places in UI. > > Is there any way the SCS/sipXecs can be made configurable > at some point? > > It already is - the autoconf variable @SIPXECS_NAME@ is set > to the correct name at build time.
To use @SIPXECS_NAME@ I think we'd need to build the plugin (and its installer) as part of the sipXecs (Linux) build. The Windows version of Preflight is a product of the sipXecs build. It has some C code that's cross-compiled for Windows, and includes an installer (NSIS). Moving the "Click to Call" plugin into the sipXecs build is something worth considering. @SIPXECS_NAME@ is just another reason for doing so. -Paul [email protected] _______________________________________________ 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/
