In a humorous way, this enhances my argument for a macintosh based port of sipx. I unfortunately do not have the capabilities to do it however ;)
On Jan 31, 2010, at 2:29 PM, Tony Graziano wrote: This is really a centos/hardware compatibility thing. Disable the onboard nic and throw a plain network card in it and it WILL work. Sipx is hardware agnostic for the most part. Its the linux compatibility which sipx is not involved in. ============================ Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ ----- Original Message ----- From: Charles <[email protected]> To: Tony Graziano <[email protected]> Cc: [email protected] <[email protected]> Sent: Sun Jan 31 17:26:36 2010 Subject: Re: [sipx-users] iso install issues Oh great.... Sorry to vent but this leads back to the question awhile back of how to make things simpler. I decided to change gears and get a small PC with a dual core so that I wouldn't have these potential problems that I was experiencing with the macintosh [which I can administer much better], so I wouldn't need to tweek in the first place and could go with the flow. Instead I end up with a box I know less of that I am now going to potentially need to tweek to get it running.... Before I got this box, I DID look at the hardware requirements on the wiki and there was no indication that there might be issues such as this FWIY its a Dell Inspiron Zeno. I will do some checking and see what I can find out. Hardware Requirements The Installation CD is made for standard Intel / AMD based systems (P4, Core Duo or equivalent) with a minimum of 512MB of RAM (more is recommended). It is not made for VIA CPUs (C3 or C7). For more detailed recommendations, see Hardware Requirements. Hardware Requirements Introduction The sipXecs IP PBX runs on standard Intel x86 servers able to run the Linux operating system. There is no additional special hardware required. In particular, no special gateway cards are needed as all gateways are external. Because of the distributed and multi-threaded architecture, sipXecs IP PBX directly profits from dual / quad core CPUs. RPMs are available for CentOS, SuSE, and some Fedora versions. An ISO installation image is available for CentOS (both 32 and 64 bit). See CD Installation of sipXecs. Recommendation for a Production System For a reasonably performing system we recommend the following configuration. This is a rough guide line for a production system. Media server performance profits from a dual / quad CPU system (dual / quad core CPUs) and lots of memory (2GB - 4GB). Pentium 4 or Xeon processor @ 1.8 GHz or higher (For a test system even a P III will work fine) Minimum of 1 GB of memory with sufficient swap space (2 GB RAM or more preferred) 18 GB to 36 GB disk recommended (dependent on required voicemail storage) The sipXecs IP PBX supports an unlimited number of voicemail boxes, and the total number of hours of recorded messages is determined by the size of the harddisk. As a rule, for every minute of recorded messages you will need 1 MB of disk space (About 3 hours per 10 GB of disk space). Charles On Jan 31, 2010, at 2:12 PM, Tony Graziano wrote: There is still an issue with the Centos OS not having an adequate driver for your network card. This happens frequently when the hardware or chipsets are new and the distro has not caught up yet. You should be able to search the centos forums for your hardware and centos 5.2 and see if there is a workaround. Other workarounds would be to install the latest version of centos as a base install (like 5.4) if it supports your network card, then add the sipx repo and install sipx that way Caution: Doing this may require some tweaking and some would warn against doing so. Plainer hardware usually generates no issues, but extra small hardware or extra management capabilities make this problematic at time (especially with the new Intel management stuff). On Sun, Jan 31, 2010 at 5:01 PM, Charles <[email protected]> wrote: I see a local loopback but no eth0 listed when I run ifconfig On Jan 31, 2010, at 1:53 PM, Tony Graziano wrote: Methinks he is using mac hardware. If this is the case, he should go to the centos or redhat forums to see if his NIC is supported. Copying the needed files to CD or USB and mounting would be the only real method to get that working. It might also be a kernel patch or even unsupported. This is an ongoing thing with mac hardware at certain hardware revisions. On Sun, Jan 31, 2010 at 3:54 PM, Eric Varsanyi <[email protected]> wrote: It sounds like maybe the kernel isn't finding your network card (unsupported, broken, ?); the configuration scripts get generated for every found card. On an existing system if you change the mac address of a card (by swapping it for instance) you can end up with the card showing up as eth1 or eth2 (which sipxecs cannot handle), but this doesn't sound like that issue. Did anaconda (the RHEL/fedora installer) ask you about setting up the card early on in the install? If it didn't that's a good clue it didn't see one. You can also use ctl-alt-f3 to switch to a text console (while the installer is running) and run 'ifconfig -a' to see if you have an 'eth0'. -Eric On Jan 31, 2010, at 1:05 PM, Charles wrote: > I am trying to run install with the 4.0.4 ISO on a new machine and am > getting an abort after the DNS entry screen. It doesn't matter if I > choose, no or yes for the this should be my or shouldn't be my DNS server > page. > > The error message is: > > sipxecs-setup could not find network file > /etc/sysconfig/network-scrips/ifcg-eth0 > > On previous setups, I used the sipx server to run the DNS. > > Ideas? > > Charles > _______________________________________________ > 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/ -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec. -- ====================== Tony Graziano, Manager Telephone: 434.984.8430 Fax: 434.984.8431 Email: [email protected] LAN/Telephony/Security and Control Systems Helpdesk: Telephone: 434.984.8426 Fax: 434.984.8427 Helpdesk Contract Customers: http://www.myitdepartment.net/gethelp/ Why do mathematicians always confuse Halloween and Christmas? Because 31 Oct = 25 Dec. _______________________________________________ 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/
