On Sun, 2008-12-14 at 20:00 +0100, Gijs Nelissen wrote: > Thanks for your instructions, indeed i was using multiple > repositories. I removed all and went for stable. > Install went fine (small rubygems dependency problem), but i managed > to fix that. > > Your instructions work fine until : > > [r...@voip sslkeys]# sipx_reset_cd > /usr/bin/sipx_reset_cd:13: DeprecationWarning: The sre module is > deprecated, please import re. > import os, commands, sys, sre, time, traceback, glob, signal, snack > Traceback (most recent call last): > File "/usr/bin/sipx_reset_cd", line 13, in <module> > import os, commands, sys, sre, time, traceback, glob, signal, > snack > ImportError: No module named snack
When you get an error setting up: Stop. For some reason, you're missing a python package you need. Try yum install newt-python > I am using an external dns server where i configured correct settings > (as on howto:dns page). > I self generated a certificate > with : /usr/bin/ssl-cert/gen-ssl-keys.sh > and /usr/bin/ssl-cert/install-cert.sh > > Now when i goto https://sip.domain.com i get this error : > > (Error code: ssl_error_rx_record_too_long) > > Configtest does pass, so i am one step closer to succesful > installation. > > > > Your 'stable' installation isn't stable at all. By the pastebin you > > send me, you have the .repo file downloaded as .repo.1, meaning you > > already had one with the same name in place. > > > > Check your /etc/yum.repo.d files for duplicates and remove the one > > that still has the unstable repo active. > > > > Let's try again: > > > > 0 - #> service sipxpbx stop -> stop it > > before remove. Make sure there are no left processes running with > > sipxchange UID - kill -9 them > > 1 - #> yum remove sipx\* -> to remove > > any left sipx related package > > 2 - #> dropdb -U postgres SIPXCONFIG -> to drop the config > > database > > 3 - #> cd /etc/yum.repo.d && rm sipx* -> to make sure no > > other sipx repo file will remain > > 4 - #> wget > > https://sipxecs.sipfoundry.org/pub/sipXecs/sipxecs-stable-fc.repo > > 5 - #> yum clean all > > 6 - #> rm -rf /etc/sipxpbx /var/sipxdata > > 7 - #> yum install sipxecs > > 8 - #> sipx_reset_cd or manually setup DNS and the SSL keys > > 9 - #> service sipxpbx configtest and if it's all good, start the service. > > > > Let's see how it goes. > > > > -MM > > > > > > On Sun, Dec 14, 2008 at 10:48 AM, Gijs Nelissen <[email protected]> wrote: > > > > > I am doing a clean install. A log of all my commands (clean install) > > > following this guide and trying stable > > > > > > Installation (stable) runs fine : http://www.pastebin.be/15418 > > > SSL keys, also ok : http://www.pastebin.be/15419 > > > Config check (sipxsupervisor problems on default install) : > > > http://www.pastebin.be/15420 > > > > > > Starting sipxpbx works fine : > > > > > > [r...@voip sslkeys]# /etc/init.d/sipxpbx start > > > > > > Starting sipXpbx: > > > Starting sipxsupervisor: [ OK ] > > > Starting httpd: [ OK ] > > > > > > When accessing the https://sipx.domain.com i get : > > > > > > (Error code: ssl_error_rx_record_too_long) > > > > > > > > > So stable : ssl_error_rx_record_too_long > > > Unstable : redirects to 8443, nothing there. > > > > > > What now ? > > > > > > > > > > > > > > > > https://sipx.yourdoamin.com:8443/sipxconfig/app > > > > > > > > is where you would normally find sipxconfig. > > > > > > > > You should make sure you did not install apache BEFORE install sipx, > > > > it installs its own. > > > > > > > > > > > > > > > Gijs Nelissen 12/13/08 1:14 PM >>> I tried installing on ubuntu > > > > > > > > > > > intreprid, mass dependancy errors and eventually (after fixing all > > > > dependencies) compile errors. > > > > > > > > After that i tried on fc9, resulting in yum dependancy hell. Thats > > > > when i noticed the package repositories have a fedora8 version. So > > > > there we went. > > > > > > > > Clean fc8 install, tried stable & unstable, both result in this error : > > > > > > > > [r...@voip sipxpbx]# /etc/init.d/sipxpbx configtest > > > > Checking TLS/SSL configuration: [ OK ] > > > > ...other tests... > > > > all [ OK ] > > > > Checking /tmp directory has correct permissions: [ OK ] > > > > Checking sipxsupervisor:Configuration file not found: > > > > '/etc/sipxpbx/alarm-config.xml' > > > > [FAILED] > > > > sipXpbx: > > > > sipXpbx: sipXpbx configuration problems found: > > > > sipXpbx: > > > > sipXpbx: Check sipxsupervisor > > > > sipXpbx: > > > > > > > > My sipx does start, so /etc/init.d/sipxpbx start works (after > > > > succesfully generating&installing ssl certificates). Now when i go to > > > > the sipx web interface > > > > > > > > https://my.server.url/ it redirects me to > > > > https://voip.digitalbase.eu:8443/sipxconfig > > > > > > > > Nothing is there. Apparently apache isn't even listening on 8443. > > > > Am i overseeing something here ? Is there a fix ? > > > > > > > > Kind regards > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > _______________________________________________ > > > 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 > > > > > > -- > Gijs Nelissen > > > > > > DB Logo > > > Digital Base > Broekstraat 36, 3001 Heverlee > T. +32 (0)16 36 00 31 - F. +32 > (0)16 36 00 39 > Mobile +32 (0)472 24 36 21 > E-mail: > [email protected] > New Website: www.digitalbase.eu - > www.digitalbase.be > > > > > > > The information in this e-mail and > any attachments to it are > confidential. > > The contents may not be copied or > used by anyone other than the > addressee and must not be further > disclosed without our permission. > If you have received this e-mail by > mistake, please notify the sender > immediately and delete this e-mail > and any attachments to it from your > systems. > > Warning: Although the company has > taken reasonable precautions to > ensure no viruses are present in > this e-mail, the company cannot > accept responsibility for any loss > or damage arising from the use of > this e-mail or any attachments to > it. > > > _______________________________________________ > 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
