On Mar 25, 2010, at 6:34 AM, Scott Lawrence wrote:

> On Thu, 2010-03-25 at 10:03 +0800, Rhon wrote:
>> Hi,
>> 
>> I'm planning to install SipXecs-4.0.4 into a new server. Does anyone
>> here were able to successfully install SipXecs-4.0.4 on Fedora 11
>> 64bit machine?
> 
> The only way to do that would be to build from source.  Since we've
> never had all the dependencies built for F11, this is not something I'd
> expect to work smoothly.
> 
> For any production installation, sipXecs should be the only thing you
> use the box for; that being the case, there's no reason to pick the
> platform first and then install the application.  Save yourself trouble
> and go with one of the binary builds.
> 


I have built and run 4.0.4 and various more recent SVN versions on 32 and 64 
bit fedora 12. My original motivation was to integrate with a firewall but 
limitations/assumptions in the sipXecs stack made this impractical (there are 
various minor problems that prevent running on a box with connectivity on 
anything other than "eth0").

I'm still using F12 (64) bit for sipXecs development because my main 
development server is running that to support other projects. I have a 32 bit 
F12 VM I use for testing and deployment, and an actual small 32 bit physical 
box (a newer dual core Atom with an SSD, pretty slow but plenty good enough for 
my small deployment) that's a clone of the 32 bit F12 VM for production.

If you want to build on F11 or F12 I've posted the various issues I ran into 
building and some patches to this bug: 
http://track.sipfoundry.org/browse/XX-7487

My .02: If you just want to run it and don't need any of the stuff post 4.0.4 
follow Scott's advice and use their ISO, it is simple/straightforward and gets 
you running in minutes.

-Eric
_______________________________________________
sipx-users mailing list sipx-users@list.sipfoundry.org
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/

Reply via email to