Translations - Alcatel-Lucent OmniPCX Enterprise Manual

INSTALLATION PROCEDURE FOR VERSION
J1.410.34.c – RELEASE 10.0

12. TRANSLATIONS

CAUTION
− Do not create blank database.
− As of Release 5.1, the translation is automatically run after loading the OPS files.
− There is no automatic translation from Releases below 1.5.3 to Release 10.0. For all these
versions, it is essential to go via an intermediate translation in a release compatible with
translation to R10.0.
− Sites in A9.532 should first pass to A9.537.
− There is no automatic translation of Chorus data of Releases below R3.0. You should not restore
the Chorus data of Releases below R3.0 but perform manually a complete netadmin.
− There is no automatic translation from the Custom Release 3.0C (C1.580.1) to Release 10.0. It is
essential to carry out an intermediate translation with Custom Release 3.2-C2 (C1.762.18
minimum).
− As of Release 8.0.1, to take into account the provisioning limit evolutions, the translation creates
automatically a fictive shelf in which the virtual UA boards of ACT 19 (intended for the
assignment of IP sets) will be migrated.
This fictive shelf is created automatically with the first free shelf number in the translated
database.
In XL configuration, the number of fictive shelves dedicated to IP sets allocation can go up to 3.
− When migrating (use of photoconfig), Actis takes into account the creation of fictive shelves
dedicated to IP sets allocation.
− As of Release 9.0, all standard SIP sets must be declared with the SIP Extension type.
Standard SIP sets are no longer supported with the former "SIP Device" mode (formerly called
"External set"). Only items other than standard sets (Nokia sets in Dual mode, 4135 IP Conference
Phones, fax, video, etc.) should remain with the former "SIP Device" mode.
When migrating a system with "SIP Device" / "External set" to R9.0, the system moves these sets
into the new mode (SIP extension) automatically.
It is mandatory to declare Nokia sets, used in Dual mode with OXE, and OT4135
IP Conference Phones with type "SIP device".
Procedure to follow:
•
Export the SIP entities which are not standard SIP sets (Nokia sets in Dual mode, OT4135 IP
Conference Phones, fax, video, etc.) by OmniVista 4760(i) by using .prg as export format.
•
Remove these entities then migrate to R9.0.
•
Import again the items which have been previously exported: standard SIP sets are in "SIP
Extension" and the other SIP entities in "SIP Device".
Fictive shelves dedicated to IP sets allocation created automatically by the system
must in no way be changed by the management.
Ed. 02 / 22 June 2011
OmniPCX Enterprise
51 TC1449