On Thu, Jul 15, 2010 at 4:16 PM, Tony Graziano wrote:
> I would have bumped to 4.0.4 before going to 4.2.
>
I just finished upgrading and testing my production box. Everything appears
to be working as expected. Here's the upgrade path I took: 4.0.1 >> 4.0.2 >>
4.0.4 >> 4.2.0.
Thanks for your he
in the event there are schema changes.
On Thu, Jul 15, 2010 at 8:54 PM, Tim Byng wrote:
> On Thu, Jul 15, 2010 at 4:16 PM, Tony Graziano <
> tgrazi...@myitdepartment.net> wrote:
>
>> Its not an issue. There is a JIRA I opened on that. If it were me, nd its
>> not, I would have bumped to 4.0.4 be
On Thu, Jul 15, 2010 at 4:16 PM, Tony Graziano wrote:
> Its not an issue. There is a JIRA I opened on that. If it were me, nd its
> not, I would have bumped to 4.0.4 before going to 4.2.
>
Thanks for the reply. Just curious...why do you recommend going to 4.0.4
first? I can still do this if need
Its not an issue. There is a JIRA I opened on that. If it were me, nd its
not, I would have bumped to 4.0.4 before going to 4.2.
Tony Graziano, Manager
Telephone: 434.984.8430
Fax: 434.984.8431
Email: tgrazi...@myitdepartment.net
LAN/Telephony/Security and Control Sys
I just applied updated from 4.0.1 to 4.2.0 on a copy of my production
server. Everything appears to be working as expected. However, I did get
some warnings and errors and wanted to make sure everything is OK.
Before applying the update, I updated my sipxecs.repo with the following:
[centos-5-bas
