Hi, when doing the cvs export the PIN get's exportet too, isn't it ? If not, just export the users table (postgres db SIPXCONFIG), there you have the PIN's in encrypted format.
Best regards Stefan ________________________________________ Von: Josh McDonald [[email protected]] Gesendet: Dienstag, 3. November 2009 20:26 An: Weigel, Stefan; [email protected] Betreff: RE: [sipx-users] Problems after upgrade from 3 to 4.02 Thanks for the response. I have decided to give up on the upgrade and have configured a new sipx server in my virtual environment. The upgrade procedure seems to be poorly documented and scattered about on the wiki. I have imported the users from the old server but it seems it's not possible to import their previous PIN numbers. Does anyone know if this is possible? I would prefer not to set everyone's pin back to the default. Josh McDonald | Systems Administrator | Brammo, Inc. Email: [email protected] | www.brammo.com 550 Clover Lane | Ashland, OR 97520 Phone: 541.482.9555 ext. 339 | Mobile: 541.531.0005 | Fax: 541.552.0414 MCSA 2003 -----Original Message----- From: Weigel, Stefan [mailto:[email protected]] Sent: Tuesday, November 03, 2009 12:26 AM To: Josh McDonald; [email protected] Subject: AW: [sipx-users] Problems after upgrade from 3 to 4.02 Hi Josh, I also had some bad issues with upgrading from version 3.10 to 4.0.2. Further on I moved the whole environment to a new architecture (i386 -> x86_64) + new os (fedora8 -> CentOS 5.4). Check all of these points: * DNS setup should be working (check /etc/hosts for your hostname pointing to localhost, remove these entries) * When installing the RPM's with existing configuration files under /etc/sipxpbx some files will be merged. On my system the XML file sipxconfig-jetty.xml got corrupted due to a wrong merge. I edited the file manually. Further on there are some more files (there's a <filename>.configmergelog). * I checked the domain settings (some alias names wasn't there after upgrade) * Enable DEBUG logging on all services, stop sipxecs service, remove all log files and restart to see if there are any error which you can analyze Best regards Stefan ----------------------------------------------- Stefan Weigel Advanced IT-Professional Tel.: +49 89 2000 48 975 Fax: +49 89 2000 48 566 eMail: [email protected] Allianz Automotive Services GmbH Einsteinring 28 85609 Aschheim Germany http://www.allianz-warranty.com Geschäftsführung: Andreas Rösing, Horst Ziegler Amtsgericht München, HRB 175682 Für Umsatzsteuerzwecke: Ust-ID-Nr.: DE 262 617 720 ----------------------------------------------- -----Ursprüngliche Nachricht----- Von: Josh McDonald [mailto:[email protected]] Gesendet: Montag, 2. November 2009 21:00 An: [email protected] Betreff: [sipx-users] Problems after upgrade from 3 to 4.02 I'm encountering several issues after upgrading from 3 to 4.02. All of the services listed under the System > Server tab show as undefined and cannot be restarted or modified in any way. If I attempt to restart the services I receive the following error message: Error performing operations on services from host: sipx.brammo.main Also I'm receiving ruby errors via email. Below is an example: /usr/lib/ruby/1.8/net/http.rb:560:in `initialize': Connection refused - connect(2) (Errno::ECONNREFUSED) from /usr/lib/ruby/1.8/net/http.rb:560:in `open' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/lib/ruby/1.8/timeout.rb:48:in `timeout' from /usr/lib/ruby/1.8/timeout.rb:76:in `timeout' from /usr/lib/ruby/1.8/net/http.rb:560:in `connect' from /usr/lib/ruby/1.8/net/http.rb:553:in `do_start' from /usr/lib/ruby/1.8/net/http.rb:542:in `start' from /usr/lib/ruby/1.8/soap/netHttpClient.rb:115:in `start' from /usr/lib/ruby/1.8/soap/netHttpClient.rb:92:in `post' from /usr/lib/ruby/1.8/soap/streamHandler.rb:170:in `send_post' from /usr/lib/ruby/1.8/soap/streamHandler.rb:109:in `send' from /usr/lib/ruby/1.8/soap/rpc/proxy.rb:170:in `route' from /usr/lib/ruby/1.8/soap/rpc/proxy.rb:141:in `call' from /usr/lib/ruby/1.8/soap/rpc/driver.rb:178:in `call' from /usr/lib/ruby/1.8/soap/rpc/driver.rb:232:in `getCallHistory' from /usr/lib/ruby/gems/1.8/gems/sipXconfig-report-1.0.0/lib/report.rb:34:in `run' from /usr/bin/sipxconfig-report:133 Any Ideas? Josh McDonald | Systems Administrator | Brammo, Inc. Email: [email protected] | www.brammo.com 550 Clover Lane | Ashland, OR 97520 Phone: 541.482.9555 ext. 339 | Mobile: 541.531.0005 | Fax: 541.552.0414 MCSA 2003 -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Weigel, Stefan Sent: Monday, November 02, 2009 1:20 AM To: 'dan'; [email protected] Subject: Re: [sipx-users] yum problem Hi Dan, just check your files under /etc/yum.repos.d/. After I had to handle this bug I had to reinstall the the original release* package, which sipxecs-release-4.0.2.rpm was replacing. It overwrites the /etc/issue, /etc/redhat-release so yum functionality wasn't given. On CentOS 5.4 reinstall the centos-release-5-4.el5.centos.1 Best regards Stefan ----------------------------------------------- Stefan Weigel Advanced IT-Professional Tel.: +49 89 2000 48 975 Fax: +49 89 2000 48 566 eMail: [email protected] Allianz Automotive Services GmbH Einsteinring 28 85609 Aschheim Germany http://www.allianz-warranty.com Geschäftsführung: Andreas Rösing, Horst Ziegler Amtsgericht München, HRB 175682 Für Umsatzsteuerzwecke: Ust-ID-Nr.: DE 262 617 720 ----------------------------------------------- -----Ursprüngliche Nachricht----- Von: dan [mailto:[email protected]] Gesendet: Sonntag, 1. November 2009 00:17 An: [email protected] Betreff: [sipx-users] yum problem I just tried to do a yum update and found that I couldn't because it failed to find any repos for 5.2. I remember that there was a lengthy thread about the 4.0.2 upgrade breaking yum, but I didn't know that it had bit me until now. Here's some relevant info about my system (from memory, so might not be entirely correct). - originally installed from the 4.0.0 iso - upgraded periodically using yum update - I don't remember doing anything to customize Centos repos - system was at Centos 5.3 before it broke Now yum is pointing to the Centos 5.2 repos which have been deprecated and no longer exist. Question: Is there a way to repair my system, or will I need to re-install? -- Dan McDaniel [email protected] Key fingerprint = E295 0313 A68F B6D6 FF33 DE51 27F2 9B91 F68A 1241 _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/ _______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users sipXecs IP PBX -- http://www.sipfoundry.org/
