Re: [sipx-users] SipX 3.8.1 to 4.0.1

2009-07-13 Thread Tony Graziano
I don't think so. I think 3.10 would be a first step and then 4.0x. The database between 3.8 and 3.10 was different and the same with 4.01. There is no schema upgrade for 4.0x that I know of that will do that directly without stepping through 3.10, though I may be wrong. What is their OS version?

[sipx-users] SipX 3.8.1 to 4.0.1

2009-07-13 Thread Austin Curry
Is it possible to upgrade from 3.8.1 to 4.0.1 directly? Are the backups that are made from within the web interface on 3.8.1 compatible with 3.10 and 4.0.1 I have a client on 3.8.1 that I tried to change the repo and upgrade, but the result was that there were no updates available? Thanks,

Re: [sipx-users] Integral load balancing

2009-07-13 Thread Scott Lawrence
On Mon, 2009-07-13 at 16:54 -0400, ingo...@netvision.an wrote: > Today we got partial load balancing - Redundant servers that only provide > critical processes in case Primary fails to do so. > The next step can be integral load balancing - Mirror servers that evenly > distribute all features/servi

[sipx-users] Integral load balancing

2009-07-13 Thread ingomar
Today we got partial load balancing - Redundant servers that only provide critical processes in case Primary fails to do so. The next step can be integral load balancing - Mirror servers that evenly distribute all features/services with Primary. ___ sip

Re: [sipx-users] No MOH by Redundant server

2009-07-13 Thread Scott Lawrence
On Mon, 2009-07-13 at 15:14 -0400, ingo...@netvision.an wrote: > Which other services are not supported by Redundant server? Essentially only call routing is redundant. > Will they be > in future releases? That varies by service, but most of the endpoint services (things that actually answer or

Re: [sipx-users] No MOH by Redundant server

2009-07-13 Thread ingomar
Which other services are not supported by Redundant server? Will they be in future releases? > [please do not reply to an existing message when starting a new topic- it messes up threading] > > On Mon, 2009-07-13 at 14:24 -0400, ingo...@netvision.an wrote: >> MOH not heard when Primary server is

Re: [sipx-users] No MOH by Redundant server

2009-07-13 Thread Scott Lawrence
[please do not reply to an existing message when starting a new topic- it messes up threading] On Mon, 2009-07-13 at 14:24 -0400, ingo...@netvision.an wrote: > MOH not heard when Primary server is offline and calls are handled by > Redundant. Currently only Primary provides MOH. That is correct -

[sipx-users] No MOH by Redundant server

2009-07-13 Thread ingomar
MOH not heard when Primary server is offline and calls are handled by Redundant. Currently only Primary provides MOH. ___ sipx-users mailing list sipx-users@list.sipfoundry.org List Archive: http://list.sipfoundry.org/archive/sipx-users Unsubscribe: http

Re: [sipx-users] Update centos server

2009-07-13 Thread Scott Lawrence
On Sat, 2009-07-11 at 17:35 +, Joseph L. Casale wrote: > >Hi Ortega, > > > >Thanks very much for the quick response. > > > >I donot have another centos could you send me the Centos-Base.repo please. > > > >Thanks in advance > > >From a CentOS box: > # yum whatprovides \*/CentOS-Base.repo > >

Re: [sipx-users] [sipX-dev] RPM install: no dependency on bind

2009-07-13 Thread Scott Lawrence
On Fri, 2009-07-10 at 15:08 -0700, Todd Hodgen wrote: > I wasn't aware that the ISO could be used as an update to an existing > version, as I thought it did a complete install of the Operating system and > all files. > > My example specifically was to have an ISO that does an UPDATE from an > exis

Re: [sipx-users] Problems with 4.0.1 Upgrade

2009-07-13 Thread Scott Richesson
Well I figured out a workaround. For some reason, the primary.xml.gz file was being retrieved uncompressed. So, yum saw the decompressed file, but was expecting it to be gzipped. Changing my proxy server not to request compression solved the problem. So, there is some problem with reque

Re: [sipx-users] Problems with 4.0.1 Upgrade

2009-07-13 Thread Picher, Michael
Another trick that works sometimes is to get rid of (move them out of the folder) your CentOS repo files, do a 'yum clean all' and then try the 'yum update' again with only the sipx repo file in the yum.repos.d folder. Mike From: sipx-users-boun...@list.sipfoundry.org [mailto:sipx-users-bou