>>> "IT Services" <[EMAIL PROTECTED]> 8/14/2008 3:00:30 PM >>> All the ruby packages are there.
the directory /usr/lib/ruby/gems/1.8/gems exists but the directory /usr/lib/ruby/gems/1.8/gems/sipxcallresolver-2.0.0 doesn't exist... I'm installing on an HP Proliant ML150 quad-core Xeon RAID1. I installed a 64-bit Centos OS so I didn't use the ISO since I think the ISO is a 32-bit version. I then followed the steps from the wiki to install sipx. I did use the ISO on an older PC for test purposes and it works, but I figured that since the HP server is capable of 64-bit, I should install the 64-bit OS. I could use the ISO but would I be "losing" something by using the 32-bit OS? <<<<<<<<>>>>>>>>>> Depends on the scalability you are looking for. If the install is going to service less than 500 users, I wouldn't hesitate using a 32-bit version if your hardware is healthy. 64-bit is nice to have, but the builds for that have just started be be ut out there. What you are doing is running 32 bit code on a 64 bit system, so I would imagine there are going to be issues. IF I WERE YOU, I'd use the Centos ISO installer: http://sipxecs.sipfoundry.org/pub/sipXecs/ISO/sipfoundry-3.10.2-centos5-i386.iso You can always revisit 64 bit when it is really needed for your environment. I think the plan is to support it on SuSE or at least have builds for it here. Doing a backup, and restoring it to a different system are not that difficult anymore from sipXconfig. Someone else might advise you what needs to be changed to make the ruby and other packages work, but as i see the repo, there isn't a 64bit version for Centos.
_______________________________________________ sipx-users mailing list [email protected] List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-users
