Try copying the httpd.conf file from the sipx folder to the apache
folder, this will then force the apache to run in the same instance as
previously loaded, or find the place where the old apache was and copy
it to there, as it will have been changed.
Scott Lawrence wrote:
On Tue, 2009-02-24 at 08:48 +0100, roberto visca wrote:
Hi there.
I've just installed sipXecs on my prod centos 5 server, where Apache
was already running. For what I can see, sipxecs pretend to fully
manage the web server. I tried to get the setup running as a virtual
server, but till now it can't.
Did someone faced this problem and know how to fix it?
There isn't a documented procedure (at least I don't know of one).
We expect that this problem will go away in sipXecs 4.2 - we will no
longer need any apache configuration.
It will be significantly easier on 4.0 - are you installing the 3.10.3
version now?
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
_______________________________________________
sipx-users mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-users
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users