OXE R7.X to R9.X upgrade
-
klodjan bregu
OXE R7.X to R9.X upgrade
Hi,
First of all let me congratulate you regarding the "new face" of this forum.
As an "old" member in this forum I found all the time the solutions for my problems.
I wish you all the best.
This time I have a problem with a system (OXE MG R7.x)
The customer wants to expand the system with two IP Media Gateways.
When I manage the Add On in Actis, it requires the changing of release to a higher version, and I have done from R7.X to R9.1
After this, there comes out two other warnings:
- The OXE SW release is available for download on BPWS
- Please check the memory size of CS (CPU Aspen) which must be equiped with 256 Mo in R8.0
What I'm asking for is:
What I have to do exactly to upgrade this system?
Which are the steps to follow... the SW needed for this... etc
There are no other applications attached to this system, only telephony (simple configuration)
Attached you can find the Actis configuration for the existing system and the Add On for it
Your help will be very appreciated.
Kind regards,
Klodjan Bregu
First of all let me congratulate you regarding the "new face" of this forum.
As an "old" member in this forum I found all the time the solutions for my problems.
I wish you all the best.
This time I have a problem with a system (OXE MG R7.x)
The customer wants to expand the system with two IP Media Gateways.
When I manage the Add On in Actis, it requires the changing of release to a higher version, and I have done from R7.X to R9.1
After this, there comes out two other warnings:
- The OXE SW release is available for download on BPWS
- Please check the memory size of CS (CPU Aspen) which must be equiped with 256 Mo in R8.0
What I'm asking for is:
What I have to do exactly to upgrade this system?
Which are the steps to follow... the SW needed for this... etc
There are no other applications attached to this system, only telephony (simple configuration)
Attached you can find the Actis configuration for the existing system and the Add On for it
Your help will be very appreciated.
Kind regards,
Klodjan Bregu
You do not have the required permissions to view the files attached to this post.
-
no_wednesday
- Member
- Posts: 15
- Joined: 17 Nov 2009 08:20
Hi
- The OXE SW release is available for download on BPWS
I think this is only a Information that the software I1.605.12 is available at the Bussiness Partner WEB Site
- Please check the memory size of CS (CPU Aspen) which must be equiped with 256 Mo in R8.0
You have to check the Memory size of the Call-Server
Greetings
- The OXE SW release is available for download on BPWS
I think this is only a Information that the software I1.605.12 is available at the Bussiness Partner WEB Site
- Please check the memory size of CS (CPU Aspen) which must be equiped with 256 Mo in R8.0
You have to check the Memory size of the Call-Server
Greetings
-
klodjan bregu
I have done the order and also I added a
- 256MB RAM and
- CD-ROM/DVD --------- Reference ----------- MD5 checksums (1)
Version I1.605.12 (DVD) ------- 3BA 27730 AA ----- 6d9cb85e6929fa1820a8b1c3b32bc729 *Image_R91_I160512.iso
Secured Version SI1.605.12 (DVD) ----- 3BA 27731 AA ---- 2d661d48daa263df63c62d18a1d37b4c *Image_R91_SI160512.iso
System voice guides v5.3 --------- 3BA 57423 AA
Since I have not done such a thing before I'm a little bit unclear regarding the process of upgrade from R7.0 to R9.1
I kindly ask you to help me for the next steps to realize this project.
Is there any documentation that explains exactly the procedure of migration?
Which are the steps to follow in order to avoid the different problems that can be occurred?
Please find below the system details:
# The role of the CPU is MAIN
Application software identity
R7.0-f4.401-13-pl-c80s1
Business identification: R7.0
Release:
DELIVERY f4.401
Patch identification: 13
Dynamic patch identification: none
Country: pl
Cpu: c80s1
ACD VERSION
release : 6
bug_fixing : 1
protocol_id : 90
version_dy_hr_stat : 11
(1)xa000000> mgr
Regards,
Klodjan
- 256MB RAM and
- CD-ROM/DVD --------- Reference ----------- MD5 checksums (1)
Version I1.605.12 (DVD) ------- 3BA 27730 AA ----- 6d9cb85e6929fa1820a8b1c3b32bc729 *Image_R91_I160512.iso
Secured Version SI1.605.12 (DVD) ----- 3BA 27731 AA ---- 2d661d48daa263df63c62d18a1d37b4c *Image_R91_SI160512.iso
System voice guides v5.3 --------- 3BA 57423 AA
Since I have not done such a thing before I'm a little bit unclear regarding the process of upgrade from R7.0 to R9.1
I kindly ask you to help me for the next steps to realize this project.
Is there any documentation that explains exactly the procedure of migration?
Which are the steps to follow in order to avoid the different problems that can be occurred?
Please find below the system details:
# The role of the CPU is MAIN
Application software identity
R7.0-f4.401-13-pl-c80s1
Business identification: R7.0
Release:
DELIVERY f4.401
Patch identification: 13
Dynamic patch identification: none
Country: pl
Cpu: c80s1
ACD VERSION
release : 6
bug_fixing : 1
protocol_id : 90
version_dy_hr_stat : 11
(1)xa000000> mgr
Regards,
Klodjan
- tot3nkopf
- Alcatel Unleashed Certified Guru

- Posts: 4058
- Joined: 02 Feb 2006 10:41
- Location: Germany & Romania
- Contact:
There are several methods for upgrade. (as I remember they are covered in Sys DOC--->System services--->Call Server Installation).
I prefer the following:
-install new linux version on inactive partition
-install the call handling on inactive partition
-install the static patch on inactive partition
-install the dynamic patch (if available) on inactive partition
-database translation
-swich to inactive version
I prefer the following:
-install new linux version on inactive partition
-install the call handling on inactive partition
-install the static patch on inactive partition
-install the dynamic patch (if available) on inactive partition
-database translation
-swich to inactive version
I prefer the following:
-install new linux version on inactive partition
-install the call handling on inactive partition
-install the static patch on inactive partition
-install the dynamic patch (if available) on inactive partition
-copy linux data
-copy database incl. translation
-swich to inactive version
Don't forget to copy the Linux data - otherwise you will have access via Console only after the version switch
-install new linux version on inactive partition
-install the call handling on inactive partition
-install the static patch on inactive partition
-install the dynamic patch (if available) on inactive partition
-copy linux data
-copy database incl. translation
-swich to inactive version
Don't forget to copy the Linux data - otherwise you will have access via Console only after the version switch
-
JoelO
- frank
- Alcatel Unleashed Certified Guru

- Posts: 3386
- Joined: 06 Jul 2004 00:18
- Location: New York
- Contact:
When you will download the MAIN release of the one you are going to install, there are a couple of PDF files.
One of them explain the step by step upgrade process. I meant.. almost the step-by-step.
But those are must-read documents, so you can see the new features, etc etc.. Although, it will not list the new features form 7.x to 9.x, but only from 8.0.1 to 9.x
One of them explain the step by step upgrade process. I meant.. almost the step-by-step.
But those are must-read documents, so you can see the new features, etc etc.. Although, it will not list the new features form 7.x to 9.x, but only from 8.0.1 to 9.x
Code Free Or Die
-
klodjan bregu
have downloaded from BPWS the last version as below:
OXE R9.1 Software - I1.605.14.e version (including complete version, static and dynamic patch)
And I followed this procedure:
In order to avoid the several problems may be occurred during the migration, I replaced the existing HDD with a new one (20GB)
I changed the RAM from 128 to 256 MB and using PC Installer v2.26 I installed Linux + Call Handling
The procedure finished with the message: successful standard installation
I rebooted the system
I made an Empty DB by swinst
I put the new OPS files by swinst
And the system was correctly migrated from R7.0 to R9.1
After that i tried to restore the configuration (that of R7.0) but it was not possible. I get some errors...
May be the DB configuration of R7.0 is not compatible in R9.1
I stacked in this step and I don't know what to do
Is there any thing I missed?
Any suggestion?
Regards,
Klodjan
OXE R9.1 Software - I1.605.14.e version (including complete version, static and dynamic patch)
And I followed this procedure:
In order to avoid the several problems may be occurred during the migration, I replaced the existing HDD with a new one (20GB)
I changed the RAM from 128 to 256 MB and using PC Installer v2.26 I installed Linux + Call Handling
The procedure finished with the message: successful standard installation
I rebooted the system
I made an Empty DB by swinst
I put the new OPS files by swinst
And the system was correctly migrated from R7.0 to R9.1
After that i tried to restore the configuration (that of R7.0) but it was not possible. I get some errors...
May be the DB configuration of R7.0 is not compatible in R9.1
I stacked in this step and I don't know what to do
Is there any thing I missed?
Any suggestion?
Regards,
Klodjan
