On Mar 16, 2012 6:31 AM, "Douglas Hubler" <[email protected]> wrote: > > On Thu, Mar 15, 2012 at 4:31 PM, Tony Graziano > <[email protected]> wrote: > >> P.P.S. We using the apache server now that's managed by the OS > >> instead of launching an apache instance with a separate config file. > > > > > > YAY! So this config change goes in the sipx config file. do you mean it will > > be moved into the apache config file or that we are o longer going to pull > > the apache rpm's in from sipfoundry's source, instead being able to use the > > OS specific version and writing the httpd to use the sipx specific config? > > That's what I think you kinda said anyway. > > We never built apache rpms, (at least not in a long time) but we'd > disable apache from starting when system restarts (chkconfig httpd > off) and we'd fail awkwardly if it was ever started by accident. Now > it's all ok. > > In case it wasn't made clear before, all services now have standard OS > start/stop/status capabilities > > e.g. > service sipxpark restart > or for you old schoolers (me) > /etc/init.d/sipxpark restart > > no need for sipxproc anymore. > > >> P.P.P.S This means we can remove https listener on sipxconfig or any > >> other internal service if we want and proxy them all thru single > >> apache server. I'll wait on this one. But it will definitely make > >> installing web certs easier if nothing else. > > > > > > WOOHOO! I think it will be easier for those of use who want to split the web > > interface from the sip interface on a system and be able to proxy web > > requests through commodity links. Does that make sense? > > I got the WOOHOO part, but not sure what "commodity links means". > Using commodity links (cable modem, DSL) for web interface and t1, fiber links for trunking and sip.
It simply makes it easier at a firewall level to have Apache configured in a standard way so that web traffic is more easily separated from sip traffic and being able to properly use inexpensive providers for applications which are not as latency sensitive. _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ -- LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 sip: [email protected] Helpdesk Customers: http://myhelp.myitdepartment.net Blog: http://blog.myitdepartment.net
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
