You might try an ISO install to a fresh machine... walk before you run. On Thu, Feb 9, 2012 at 2:44 PM, Berthold Rühl <[email protected]> wrote:
> I cant get an installation without apache, but currently i'm reinstalling > the server with the standard centos... afterwards i'll try to remove > apache, etc with yum and then install sipxecs with all dependencies... > maybe this will work... > > ---------------------------------------------------------------- > Absenderinformation: > > Berthold Rühl > > *Rettungsassistent / Stud. med.* > * > * > *Führichstr.15* > *45147 Essen* > *Tel.: 0177-3838516* > *Fax.:**0201-426395859* > *E-Mail: [email protected]* > > Am 09.02.2012 um 20:37 schrieb Berthold Rühl: > > I had a preinstalled v-server from which I removed apache. Afterwards i > downloaded the repo as described in Wiki and installed sipXecs using yum. > The firewall has been disabled. While checking the httpd.conf files i > reckognized that Port 8443 is not mentioned anywhere... > Is it possible to manually create a vhost, pointing to the directory > containing the interface-files? > Iso-Installing is not possible, because i'm using a v-server... > > Regards > ---------------------------------------------------------------- > Absenderinformation: > > Berthold Rühl > > *Rettungsassistent / Stud. med.* > * > * > *Führichstr.15* > *45147 Essen* > *Tel.: 0177-3838516* > *Fax.:**0201-426395859* > *E-Mail: [email protected]* > > Am 09.02.2012 um 20:29 schrieb Tony Graziano: > > Explain your install method. Sipx starts Apache running jetty. If you > manuall y installed and had Apache installed and running before installing > sipx you might consider installing from ISO. > > You should inspect /var/log/sipxpbx/sipxconfig.log for information why it > would not connect. > > Perhaps a firewall config (iptables)? > On Feb 9, 2012 2:15 PM, "Berthold Rühl" <[email protected]> wrote: > >> Hi, >> i just installed sipxecs on a vserver running centos 5. After the >> Installation i tried to access the webinterface and got redirected to https >> port 8443 but the webinterface didn't open because my browser was unable to >> connect to that port. >> Can you tell me which directory has to be accessed by the webserver? >> >> Thank you >> _______________________________________________ >> 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].**net<[email protected]> > > Helpdesk Customers: > http://myhelp.myitdepartment.**net<http://myhelp.myitdepartment.net/> > Blog: http://blog.myitdepartment.net > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > > > > _______________________________________________ > sipx-users mailing list > [email protected] > List Archive: http://list.sipfoundry.org/archive/sipx-users/ > -- Michael Picher, Director of Technical Services eZuce, Inc. 300 Brickstone Square**** Suite 201**** Andover, MA. 01810 O.978-296-1005 X2015 M.207-956-0262 @mpicher <http://twitter.com/mpicher> www.ezuce.com ------------------------------------------------------------------------------------------------------------ Hope to see you at the sipX CoLab! http://www.sipfoundry.org/sipx-colab A gathering for - open source users, eZuce customers & eZuce partners Get the inside track on 4.6 and a glimpse at the future of sipXecs!
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users/
