installation procedure version i1.605.16 c

Upload: miguel062555g

Post on 15-Feb-2018

220 views

Category:

Documents


0 download

TRANSCRIPT

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    1/24

    1

    TECHNICAL COMMUNICATION No. TC1349 Ed. 01

    OmniPCX Enterprise Nb of pages : 34 Date : 28 May 2010

    URGENT

    NOT URGENT TEMPORARY PERMANENT

    SUBJECT : INSTALLATION PROCEDURE FOR VERSION I1.605.16.c RELEASE 9.1

    This is the technical release of OmniPCX Enterprise with the version I1.605.16.c. It corresponds toRelease 9.1.

    It is available on Alcatel Business Partner Web Site (http://www.businesspartner.alcatel-lucent.com/)and on DVD only with the references 3BA 27730 ABAC (non secured version) and 3BA 27731 ABAC

    (secured version).Technical modes to change the release, new features, registered restrictions and controlled featuresare described in the installation procedure for version I1.605.16.c.

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    2/24

    2

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    3/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    Ed. 01 / 28 May 2010 3 TC1349

    CONTENTS

    1.1.1.1. APPLICATION DOMAINAPPLICATION DOMAINAPPLICATION DOMAINAPPLICATION DOMAIN ............................................................................................................................................................................................................................................................6666

    2.2.2.2. REFERENCE DOCUMENTSREFERENCE DOCUMENTSREFERENCE DOCUMENTSREFERENCE DOCUMENTS................................................................................................................................................................................................................................................6666

    3.3.3.3. FEATURES AND SPECIFIFEATURES AND SPECIFIFEATURES AND SPECIFIFEATURES AND SPECIFIC PROCESSC PROCESSC PROCESSC PROCESS ....................................................................................................................................................................................8888

    3.13.13.13.1 Features under PCS in version I1.605.16.cFeatures under PCS in version I1.605.16.cFeatures under PCS in version I1.605.16.cFeatures under PCS in version I1.605.16.c................................................................................................................................................................................................ 8888

    3.23.23.23.2 Features in testFeatures in testFeatures in testFeatures in test .................................................................................................................................................................................................................................................................................................................................................................... 8888

    4.4.4.4. CONTENT OF THE SOFTWCONTENT OF THE SOFTWCONTENT OF THE SOFTWCONTENT OF THE SOFTWARE PACKAGEARE PACKAGEARE PACKAGEARE PACKAGE....................................................................................................................................................9999

    5.5.5.5. LOADING THE SOFTWARELOADING THE SOFTWARELOADING THE SOFTWARELOADING THE SOFTWARE....................................................................................................................................................................................................................................13131313

    5.15.15.15.1

    Complete lComplete lComplete lComplete loading of the I1.605 version and the I1.605.16 and I1.605.16.coading of the I1.605 version and the I1.605.16 and I1.605.16.coading of the I1.605 version and the I1.605.16 and I1.605.16.coading of the I1.605 version and the I1.605.16 and I1.605.16.cpatchespatchespatchespatches ............................................................................................................................................................................................................................................................................................................................................................................................................ 13131313

    5.25.25.25.2 Sites with the "IP Touch Security" feature: Loading procedure ofSites with the "IP Touch Security" feature: Loading procedure ofSites with the "IP Touch Security" feature: Loading procedure ofSites with the "IP Touch Security" feature: Loading procedure of SSM andSSM andSSM andSSM andMSM boxes after upgrading in SI1.605.16.cMSM boxes after upgrading in SI1.605.16.cMSM boxes after upgrading in SI1.605.16.cMSM boxes after upgrading in SI1.605.16.c ............................................................................................................................................................................ 13131313

    5.2.1 Migration with SSM & MSM boxes in version 1.3.xx ........................................13

    5.2.2 Migration with SSM & MSM boxes in version 1.4.xx, 1.6.01, 2.x.0x .................14

    5.35.35.35.3 Swinst 2.58.0Swinst 2.58.0Swinst 2.58.0Swinst 2.58.0 ........................................................................................................................................................................................................................................................................................................................................................................ 14141414

    6.6.6.6. RESTRICTIONS AND REMRESTRICTIONS AND REMRESTRICTIONS AND REMRESTRICTIONS AND REMARKSARKSARKSARKS............................................................................................................................................................................................................14141414

    6.16.16.16.1 Loading the version with 40 GB or 60 GB hard disksLoading the version with 40 GB or 60 GB hard disksLoading the version with 40 GB or 60 GB hard disksLoading the version with 40 GB or 60 GB hard disks ........................................................................................................................ 14141414

    6.26.26.26.2 4760i availability and support4760i availability and support4760i availability and support4760i availability and support ................................................................................................................................................................................................................................................................ 15151515

    7.7.7.7. NEW FEATURES AVAILABNEW FEATURES AVAILABNEW FEATURES AVAILABNEW FEATURES AVAILABLE ON RELEASELE ON RELEASELE ON RELEASELE ON RELEASE 9.19.19.19.1....................................................................................................................17171717

    7.17.17.17.1 From I1.605.16.c versionFrom I1.605.16.c versionFrom I1.605.16.c versionFrom I1.605.16.c version ................................................................................................................................................................................................................................................................................................ 17171717

    7.1.1 SLI-2 boards ...................................................................................................17

    7.1.2 New Appliance Server HP DL320 G6 ..............................................................17

    7.1.3 New Appliance Server IBM X3250 M3 (Maokong) ..........................................18

    7.1.4 PCS download in parallel mode......................................................................18

    7.1.5 Wake up call customization ............................................................................18

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    4/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    TC1349 4 Ed. 01 / 28 May 2010

    7.1.6 Logs sent in real time......................................................................................19

    7.1.7 Dial By Name overflow to LDAP......................................................................19

    7.1.8 Unset the Redial Feature.................................................................................19

    7.1.9 DECT encryption on IBS/Crystal Hardware .....................................................19

    7.1.10 Voice mail password length.........................................................................20

    7.1.11 Cellular Voice Mail detection timer..............................................................20

    7.1.12 Supervision with Free Desktop ....................................................................20

    7.1.13 Call Transfer (USA Conference Mode) .........................................................21

    7.1.14 3 party conference (USA Conference Mode) ................................................21

    7.1.15 Management Event on Forward cancellation/activation ..............................21

    7.1.16 FlexOffice: forwarding cancelled .................................................................21

    7.1.17 UDP to TCP switching for long messages.....................................................22

    7.1.18 Multiple SIP gateways support using via header..........................................22

    7.1.19 SIP QoS tagging support..............................................................................22

    7.1.20 Force On Net...............................................................................................22

    7.1.21

    Interoperability with SBC 5.2.8 ....................................................................23

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    5/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    Ed. 01 / 28 May 2010 5 TC1349

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    6/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    TC1349 6 Ed. 01 / 28 May 2010

    1. APPLICATION DOMAIN

    WARNINGThis document applies to the OmniPCX Enterprise Release 9.1 in standardized version I1.605.16.c.

    Version I1.605.16.c makes a set of corrections available for sites already installed, new binariesfrom version I1.605.14.e and provides some new features.

    This document is based around a central document, the Release 9.1 installation procedure, andappendices which describe:

    The restrictions and remarks. The new features.

    Note

    The appendices below of previous installation procedures were removed from this document andreplaced by technical communications to make easier their search and their update:

    The comparison of licenses from R5.0 Ux.

    The migration from an OmniPCX 4400 to an OmniPCX Enterprise.

    The synchronization of the system after migration to an OmniPCX Enterprise with an ApplianceServer.

    The reminder of features released in previous releases.

    2. REFERENCE DOCUMENTS

    Technical communications:

    TC0150 Configuring the OmniPCX 4400 as "boot server" for IP Phones attached to networkedOmniPCX 4400

    TC0155 Compatibility of Alcatel 4635 with OmniPCX 4400 backplanes (Reminder of restrictions)

    TC0230 CPU6 Step2 board - 3BA23197 AA

    TC0259 Alcatel 4635 - Migration procedures

    TC0274 DECT Compatibilities

    TC0297 Change of external/internal ringing melodies in Release 4.2

    TC0298 Migration from Alcatel 4630 voice mail to Alcatel 4635 voice mail

    TC0328 Wrong initialization of "Antenna Diversity" after translating from Release 3.0 to Release 3.1,3.2M, 4.1, 4.1.1

    TC0336 Setting the T38 fax over IP application (with MP-102 version 4.0)

    TC0418 Compatibilities

    TC0487 Migration ACD-V1 to CCDistribution

    TC0594 Coupling a Bluetooth device on Alcatel IP Touch set 4068

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    7/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    Ed. 01 / 28 May 2010 7 TC1349

    TC0680 Risk of wrong negotiation of speed and duplex mode of Ethernet interfaces for INTIPs, GA &GD after software upgrades

    TC0682 Stop of dynamic patch delivery from Release 6.1.1

    TC0712 Modem, Fax, Data transparency over IP

    TC0777 Comparison of licenses from Release 5.0 Ux

    TC0778 Migration OmniPCX 4400 to OmniPCX Enterprise

    TC0779 Synchronization of the system after migration to OmniPCX Enterprise with Appliance Server

    TC0780 New hardware and features from Release 5.1

    TC0781 Migration of Mobile IP Touch from Release 1.x to Release 2.x

    TC0940 Technical release note for VoWLAN Release 3.0 offer

    TC0941 VoWLAN compatibility

    TC0944 Configuration, incidents & log files recovery

    TC1105 Alcatel 4059 MAC / IP - Installation procedure for version 5.1.1

    TC1106 Thomson ST20xx SIP sets deployment

    TC1108 Native SIP Call Controller: White list

    TC1195 Technical Release Note of VoWLAN 4.1 for OmniPCX Enterprise

    TC1212 CS-2 board introduction

    TC1235 Detailed list of all the ports and protocols used by OmniPCX Enterprise

    TC1243 Technical Release Note for OmniPCX Enterprise Release 9.1 - Version I1.605.12

    TC1244 Installation Procedure for version I1.605.12 - Release 9.1

    TC1246 Alcatel 4059 MAC / IP - Installation procedure for version 5.1.5

    TC1253 Alcatel 4635 - Installation procedure for version 5.4.6 - Release 5

    TC1254 Technical Release Note for Device Management Server 1.2.000.020

    TC1255 4008 / 4018 SIP set deployment with OmniPCX EnterpriseTC1256 Installation procedure for version 5.1.06.03.c - Release 5.1.1

    TC1271 Checks for integrity and authenticity of downloaded software

    TC1290 LLDP-MED on IP Touch sets

    TC1291 Technical Release Note for OmniPCX Enterprise Release 9.1 - Version I1.605.14.e

    TC1292 Installation Procedure for version I1.605.14.e - Release 9.1

    TC1308 Technical Release Note of VoWLAN 4.2.1 for OmniPCX Enterprise

    TC1319 Installing and using the OmniPCX Enterprise PC Installer v2.26 software

    TC1321 Patch2 for version 5.1.06.03.c Release 5.1.1

    TC1330 Booting issue of GD/GD2 or IP Terminals in OmniPCX Enterprise R9.1

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    8/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    TC1349 8 Ed. 01 / 28 May 2010

    3. FEATURES AND SPECIFIC PROCESS

    3.1 Features under PCS in version I1.605.16.c

    Authentication 802.1x TLS for IP Touch 40x8 sets

    DSLAM / Triple Play

    IBM Blade Center Quotation & Ordering process for BPs

    IP DR-Link on Passive Call Server - OmniPCX Enterprise Rel. 8.x and 9.0

    SIP Trunking

    VoWLAN on non-Alcatel-Lucent WLAN infra R9.1

    PCS = Premium Customer Support. The Premium Customer Support process allows the PartnerBusinesses to profit an assistance on features or products whose marketing was announced (DR3)but which are not launched yet on the market. The PCS process replaces the SDP (Specific DealProcess) previous process; refer to the eFlash EF_Marketing_003_260704.

    3.2 Features in test

    SIP Trunking.

    New carriers have begun a validation.

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    9/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    Ed. 01 / 28 May 2010 9 TC1349

    4. CONTENT OF THE SOFTWARE PACKAGE

    The software package contains the OmniPCX Enterprise I1.605.16.c application.

    The different versions of the OmniPCX Enterprise application modules are:

    Linux : 67.0

    Linux Package : 67.10

    swinst : 2.58.0

    PC Installer : 2.26

    OmniPCX Enterprise R9.1 : I1.605.16.c : I1.605 complete versionI1.605.16 static patchI1.605.16.c dynamic patchSI1.605.16.c secured patch (Note)

    Note

    The access to secured patch is only given on request after filing the appropriate document posted onBPWSSupport > Technical Support IP Telephony > Software download > Alcatel-Lucent OmniPCXEnterprise (including 4400)> Release 9.1 > Request for Security Patch Access.

    From Release 6.1.1, dynamic patches will be no more delivered. They are replaced

    by static patches ; refer to the technical communication TC0682 Stop of dynamicpatch delivery from Release 6.1.1.

    Reference of compatible CD-ROMs and DVD

    REMINDER

    As of Release 6.1, the software is only delivered on DVD.

    CD-ROM/DVD Reference MD5 checksums (1)Version I1.605.16.c(DVD) 27730 ABAC 2ffa7916f828ada3fd9238bb919511a6

    *Image_R91_I160516c.isoSecured Version SI1.605.16.c

    (DVD)27731 ABAC 3f99ed1f09af0ef80d40c34e0fe91e2a

    *Image_R91_Si160516c.isoSystem voice guides v5.3 3BA 57423 AAAG

    OmniVista 4760R5.1.06.03.c_Patch2 - Release

    5.1.1

    3BH 11632 AJAC a0c115fd1481754ecb32d084b4aef895*Image_4760_R510603c_Patch2.iso (2)

    SIP Device Management Server1.2.000.020 - Release 1.2

    3BH 11761 AAAD 392937c3530b40f1101d040631483065*image_dm_12000020.iso

    (1)Before installing the software, we strongly advise you to check the integrity and authenticity of thesoftware. For detailed information about checksums, please refer to the technical communication

    TC1271 Checks for integrity and authenticity of downloaded software.(2)

    This checksum concerns only the DVD containing the OmniVista 4760 software ReleaseR5.1.06.03.c_Patch2.

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    10/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    TC1349 10 Ed. 01 / 28 May 2010

    Note

    PSP software (Phone Set Programming) is not delivered with I1.605.16.c and SI1.605.16.c DVDversions.To get it, download the 5.0.000.540 version available on BPWS(https://www.businesspartner.alcatel-lucent.com), in section Technical Support Telephony /Download Software / Alcatel-Lucent OmniPCX Enterprise (including 4400) / Published / Phone SetProgramming.This version is compatible with OmniPCX Enterprise Release 9.1.

    List of binaries in version I1.605.16.c

    The new binaries of the version are in bold characters.

    Released R9.1 VersionsBinaries

    I1.605.14.e I1.605.16.c

    Binaries relative to system

    bios CPU5 Step3 (3)

    bios CPU6 Step2 (1) 3BA24095AAAB07_4.7bios CPU7 3BA 24115 AAAA16_3.02bios CS 10.14

    bios GD 10.14

    bios CS-2 (AMI) 3EU24009 AAAA01_9.0io1n 16

    io2 4.6

    io2n 5.17

    linux_patch 67.5 67.10

    obca 1.5

    pc_install 2.26

    swinst(2) 2.57.0 2.58.0

    Binaries relative to DECT

    dect4 7.9

    dect8 1.26

    ibs_appli_ng 48.07 49.03

    ibs_boot_ng 71ibsng 18.06

    rbsng 53.0

    startibsng 0.71

    Binaries relative to compression boards

    binintip_appli 14.20 14.23

    bindsintip 4.37.2

    bindsintip2 3.4 3.42

    intip_linux 1.16

    bootintip 6.10

    mg_appli 44.34.1 45.4

    binmcv 3.9.0binmcv2 3.4

    mg_version_country 1.11.11 1.11.12

    mg_linux 8.1

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    11/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    Ed. 01 / 28 May 2010 11 TC1349

    Released R9.1 VersionsBinaries

    I1.605.14.e I1.605.16.c

    mg_platform 8.4

    flashdriver 2.2

    dsp_firmware 81.00

    ioip 4.07

    lio_comp2 3.40

    rlio_comp2 3.27

    mg3 2.18 3.02

    intip3 2.18

    Binaries relative to sets

    bin40x8 4.20.60 4.20.70

    bindatanoe 4.20.60 4.20.70

    bin40x8G 4.50.60 4.20.71

    bindatanoeG 4.20.60 4.20.71

    noesip 2.00.81 2.01.10

    binnoeuax9 3.81.00

    binnoeua19 3.81.00

    jpn_4068 1.00.01

    jpn_40x8 1.00.00

    jpn_40x9 1.00.01

    kor_4068 2.00.00

    kor_40x8 2.00.00kor_40x9 2.01.00

    chi_4068 2.01.00

    chi_40x8 2.01.01

    chi_40x9 2.01.01

    ipphone 2.31

    tscip 5.2

    tscipv1S 3.0

    Secured binaries

    bin40x8 4.25.60 4.25.70

    bindatanoe 4.25.60 4.25.70

    bin40x8G 4.25.60 4.25.71

    bindatanoeG 4.25.60 4.25.71

    SM modules (Thales)(4)

    2.2.03

    mg_appli 44.84.1 45.4

    security Thalessign.verif.

    1.0

    security Thaleslibrary

    1.1.01 1.1.02

    mg3 2.68 3.02

    intip3 2.68 3.02

    Binaries relative to boards

    brapra 2.06c1nvgpa2 3.3

    c1nvua 4.9

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    12/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    TC1349 12 Ed. 01 / 28 May 2010

    Released R9.1 VersionsBinaries

    I1.605.14.e I1.605.16.c

    c1nvz32 3.0

    cpl2dpnss 1.11

    dpnss 2.3

    dpnssnv 2.2

    dpt1 2.05

    dsp_emtl24021 3.01

    dsp_gpa 2.01

    dsp_vgu 1.5

    dsp0Z32 1.02

    dsp1_gpa2 1.09dsp1nddi2 2.01

    dsp2_gpa2 1.10

    gpa2tns 1.10 1.11

    gpa 2.24

    intof 1.24 1.25

    intofssync 1.05

    intof2 2.2 2.3

    ivrZ24 2.0

    lia 4.17

    lioebbc2 3.05

    lio b/p/x 3.25mic2 2.31

    nddi 2.7

    nddi_in 2.7

    nddi2 2.21 2.22

    nprae 2.06

    pcm2_ru 1.6

    pra 2.06

    pra2 2.24

    rma 3.04.04

    tonesnv 3.0

    ua 3.13.9

    uscvg 2.9

    Binaries relative to attendants

    fbc 2.13

    mapacs2 2.01

    ta/mac 4.7

    ta/pac 2.01

    Binaries relative to 4760i

    4760i 2.3.01.00

    Binaries relative to VoWLAN

    noemipt_r2 109.025

    noemipt_r3 120.021

    1

    The delivery of a new CPU6 Bios requires to reboot the PABX after installing the dynamic patch.

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    13/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    Ed. 01 / 28 May 2010 13 TC1349

    2 You should connect to swinstto complete its installation.

    3

    CPU5 Step3 is no longer supported from Release 8.0.

    4

    SM Modules Thales: this is the reference seen in mgr.

    5. LOADING THE SOFTWARE

    5.1 Complete loading of the I1.605 version and the I1.605.16 and I1.605.16.cpatches

    To install the I1.605 complete version and the I1.605.16 and I1.605.16.c patches, refer to thetechnical communication TC1319 Installing and using the OmniPCX Enterprise PC Installer v2.26software.

    It is necessary to use the software OmniPCX Enterprise PC Installer v2.26 or higher duringthe complete installation with CS-2 (this software is available on BPWS) and GD-3.

    REMINDEREach Bios flashing operation requires to switch off the CPU6 with the M/A button totake it into account and a reboot of the PABX.

    5.2 Sites with the "IP Touch Security" feature: Loading procedure of SSM and MSMboxes after upgrading in SI1.605.16.c

    5.2.1 Migration with SSM & MSM boxes in version 1.3.xx

    CAUTIONSites using "IP Touch Security Solution" feature (Encryption) must follow a specific procedure toupdate the IP Touch security boxes.

    SSM & MSM downloading procedure after an upgrade in R9.1

    After upgrading in SI1.605.16.c and with the RUNTEL done, you must update the IP Touch Security

    boxes (MSM, SSM) as follows:1

    Check that the version 2.2.03 is managed in mgr.

    2 Enter the config.BTcommand.

    3

    Reboot (with Off/On button) each SSM and MSM boxto allow the downloading of the newbinary 2.2.03 (the config.BTfile has been modified to take in account the IP Touch Security in

    network feature. This enhancement is available only from the version 1.6.02).

    Notes

    If the system is duplicated, it should be better to stop the Stand-By CPU before installing the MainCPU.

    Encryption in network: For the link encryption (Inter node link) of SI1.605.16.c installations,generate the file config_BT.cfg at each activation or un-activation of the link encryption.

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    14/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    TC1349 14 Ed. 01 / 28 May 2010

    5.2.2 Migration with SSM & MSM boxes in version 1.4.xx, 1.6.01, 2.x.0x

    After upgrading in SI1.605.16.c and with the RUNTEL done, you must update the IP Touch Securityboxes (MSM, SSM) as follows:

    1

    Check that the version 2.2.03is managed in mgr.

    2 Update the SSM & MSM boxes. Two ways are available:

    either reboot (with Off/On button) each SSM and MSM box,

    or re-generate the Config_BT.cfgfile.

    3

    Check that each SSM and MSM box has been downloaded with the new version:

    enter the info vcommand (to be entered for each box).

    Note

    To connect from the CS to the active MSM, you must mandatory use the b option to indicate the CSphysical address.Example: telnet b @_IP_Physical_CS @_IP_MSM

    5.3 Swinst 2.58.0

    You should connect to swinstto complete the installation.

    6.

    RESTRICTIONS AND REMARKS

    6.1 Loading the version with 40 GB or 60 GB hard disks

    The initial loading of 40 GB or 60 GB hard disks must be performed with the installation of thecomplete version, of static patch and dynamic patch (i.e. with the PC installer application, at versiontelephone level, you should select I160516c).

    You must follow this procedure to be able to partition the disk otherwise after aswitch of a partition, the disk no longer restarts.

    The various references of the 40 GB disk are:

    For CPU6/CPU7 For CSCatalog reference 3BA 27013 3EH 76031Code 3BA 27013 ABAL 3EH 76031 ADAE

    Alcatel reference 1AF 11417 AAAA 1AF 11417 AAAAManufacturer reference MK4032GAX TOSHIBA MK4032GAX TOSHIBA

    For more details, refer to the technical communication TC0771 Installation of Toshiba 40 GB harddisks.

    The various references of the 60 GB disk are:

    For CPU6/CPU7 For CSCatalog reference 3BA 27013 3EH 76031

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    15/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    Ed. 01 / 28 May 2010 15 TC1349

    Code 3BA 27013 ABAN 3EH 76031 ADAFAlcatel reference 1AF 14826 AAAA 1AF 14826 AAAAManufacturer reference HTE 541660J9AT0 HITACHI HTE 541660J9AT0 HITACHI

    Installation is identical to 40 GB disks.

    6.2 4760i availability and support

    By default 4760i is not activated. To activate 4760i, you need to update the Use 4760i flag in

    System Parameter and reboot the CPU. Such activation option was no more available in followingPCX versions:

    R9.0: H1.301.38 up to H1.301.40

    R9.1: I1.605.12 up to I1.605.15

    With some support conditions, we have now fit back the 4760i option as of:

    R9.0: H1.301.41

    R9.1: I1.605.16

    The reintroduction of 4760i is done with following support conditions:

    Usage is reserved for pre-installation of PCX under Business Partner control and should not beused by End customer.

    No improvement is done or planned.

    No security update will be done (as stated in point 1, the 4760i tool is not designed forproduction environment and end customer usage).

    No update to support latest Windows OS or Java version is planned.

    Any minor and major issue which could be considered as rendered by other tool will berejected.

    This concerns for instance: graphical view of Device key management, backup

    4760i is mainly used to inject mass data through a grid management.

    End customer who needs to use a graphical interface to manage its PCX must be equipped of 4760software.

    Note

    To make easier the launching of one or several 4760i client version use this method:

    Install the related java version used by 4760i.

    Install 4760i software on your PC (4760iClient.exe), you will get the c:\4760ifolder.

    Rename it as c:\4760i_R9.1for instance.

    Copy c:\Program Files\Java\jre1.5.0_12folder toc:\4760i_R9.1\lib\ext\jre15

    Edit c:\4760i_R9.1\lib\ext\runconfig.bat

    Change the startup line :

    %START% ..javaw.exe

    by

    %START% jre15\bin\javaw.exe

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    16/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    TC1349 16 Ed. 01 / 28 May 2010

    This way:

    You can host several java versions on your PC and have a dedicated java for 4760i usage.

    You can install several 4760i versions and use one at a time.

    You have a better performance of the 4760i application.

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    17/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    Ed. 01 / 28 May 2010 17 TC1349

    7. NEW FEATURES AVAILABLE ON RELEASE 9.1

    For more information, refer to the System documentation.

    7.1 From I1.605.16.c version

    7.1.1 SLI-2 boards

    The new SLI-2 boards: SLI4-2, SLI8-2 and SLI16-2 are only supported from version I1.605.16.c.

    SLIx-2 board of Common Hardware rack:

    Allows the user to connect up to 16 Z devices (Analog sets or modems or fax machines).

    Offers CLASS facility to the users.

    Provides a new service - Calling Part Control [CPC].

    CPC (Calling Party Control) is a signal sent by a terminal to indicate that the "Calling Party" has hungup. It's usually called "Open Loop Disconnect".

    The CPC signal tells the SLI-2 board equipment that the outside party has hung-up, it is a veryimportant feature especially when communicating with voicemail or similar systems that need to stoprecording when the calling party hangs up.

    For more information, refer to the updated System documentation.

    7.1.2

    New Appliance Server HP DL320 G6

    The Hewlett Packard DL320 G6Appliance Server is only supported from versions I1.605.16.c andH1.301.42.a.

    Characteristics of Hewlett Packard DL320 G6Appliance Server reference 3BA27704CA: Form factor/height: Rack/1U

    1 Processor: Xeon E5504 Quad Core 2.0 GHz / 4MB L3 - 2 * 4.8 GT/s QPIs - no HT - noTurbo - 800MHz DDR3 - 80W

    Memory: 2GB PC3-10600 (1* 2GB dual-rank Unbuffered DIMM)

    Expansion slots: 1 * PCI-Express x4 low-profile + 1 * PCI-Express x16 - full length / full height

    Disk bays: 1 HDD S-ATA (Serial Advanced Technology Attachment) 160 GB 3"5 in SimpleSwap (SS) thus not Hot-swappable

    Maximum internal storage: 160 GB

    Network interface: 2 embedded GbE NICs

    Power supply: 1 x 400W non-redundant AC power Hot-swap components: HDD : NO

    Redundant array of independent disks (RAID) support: NO, not on Simple Swap model.

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    18/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    TC1349 18 Ed. 01 / 28 May 2010

    7.1.3 New Appliance Server IBM X3250 M3 (Maokong)

    The IBM X3250 M3 Appliance Server is only supported from version I1.605.16.c and H1.301.42.aminimum

    Characteristics of IBM X3250 M3 Appliance Server reference 3BA27582CA:

    Form factor/height: Rack/1U 1 Processor: Celeron G1101 2.26GHz/1066MHz DualCore

    Memory: 1GB (1x1GB, Single Rankx8) PC3-10600 CL9 ECC DDR3 1333MHz LP UDIMM

    Disk bays: 250 GB 7200 RPM 3.5"" Simple-Swap SATA II

    Network interface: 2 embedded GbE NICs

    Power supply: 1 x 351W non-redundant AC power

    Hot-swap components: HDD

    7.1.4

    PCS download in parallel mode

    As of version I1.605.16.c, OmniPCX Enterprise allows to perform the software update (immediate or

    scheduled) of many Passive Communication Servers in parallel mode instead of sequentially.Thissoftware download in parallel mode is provided by OmniVista 4760 R5.2 (not released yet).

    For more information on software update using OmniVista 4760, see section 9 Maintenance of theOmniVista 4760 Administrator Manual.

    7.1.5 Wake up call customization

    As of I1.605.16.c, the newWake Up Guide Optionsystem option is created for wake up call

    guide configuration. With the new option, users can manage and personalize the wakeup call guidein system independently on the 46x5 voicemail.This new system option is under System -> Other System Param. -> Local Features

    Parameters -> Wake Up Guide Optionwould provide 3 options to control the guide which

    would be used:

    If system option = 0 (default)

    We use voice mail both in wake up reminder execution and programming time.

    If system option = 1

    We never use voice mail in both cases

    If system option = 2

    We use voice mail during programming time and use voice guide at execution time.

    For more information, refer to the updated System documentation.

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    19/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    Ed. 01 / 28 May 2010 19 TC1349

    7.1.6 Logs sent in real time

    As of I1.605.16.c, a new feature provides ability to send Management logs to an external serverusing an application developed by Professional Services. This external server IP address and Portconfiguration can be configured underApplications -> Extern Management Logs.

    Management logs are being stored in history files as of current implementation. If External Server isconnected to OmniPCX Enterprise, OmniPCX Enterprise will send these logs in form of UDP packets.

    There will not be any acknowledgement for this data.

    7.1.7

    Dial By Name overflow to LDAPAs of I1.605.16.c, the new LDAP direct accesssystem option allows to perform the dial-by-

    name search directly in LDAP server instead of searching in local directory.

    This new system option is under System -> Other System Param. -> Systemparameters

    For more information, refer to the updated system documentation.

    7.1.8

    Unset the Redial Feature

    As of I1.605.16.c, the new Deactivate Redial Key system option for Redial Key allows to

    make the Redial key a manageable one. The Redial Key is made ineffective only if both the System

    option for Redial Key is forbidden and the parameter for Redial Prefix is also forbidden(RedialLast Number) in Phone feature COS.

    This new system option is under Specific Telephone Services -> Deactivate RedialKey.

    For more information, refer to the updated System documentation.

    7.1.9

    DECT encryption on IBS/Crystal Hardware

    As of I1.605.16.c (including the ibs_ng v49.03 encryption binary), Alcatel OmniPCX Enterpriseprovides three levels of security for establishing and maintaining DECT calls. These levels correspondto the following three modes:

    1 "Identity" mode

    2 "Authentication" mode

    3 "Encryption" mode

    Before Release 9.1, the system's security level is limited to "Authentication" mode fora DECT system in IBS configuration.

    Pre-requisites:

    Modification in the IBS software to open the DECT standard encryption as available on RBS.

    All RF bands, World Wide. Only with Crystal hardware (synchronisation by DTM needed).

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    20/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    TC1349 20 Ed. 01 / 28 May 2010

    OmniPCX Enterprise management to allow the user to set the DECT security level toencryption, the software encryption of the IBS is activated by a message from OmniPCXEnterprise.

    The encryption binary ( v49.03) is for IBS NG (not possible with "old" IBS 1G).

    MR100/200/300/400 mobiles must normally operate.

    Mobiles must be reinstalled to take into account the encryption.

    Actis software lock for DECT encryption.

    For more information, refer to the Technical Communication TC0274 DECT compatibilities.

    7.1.10

    Voice mail password length

    As of I1.605.16.c the maximum length of the administrative voice mail password is increased fromfour to eight characters while managing from mgr.

    7.1.11

    Cellular Voice Mail detection timer

    While calling a tandem (fixed set with a Mobile Remote extension twin set association), A problem ifthe External Cellular Client is unreachable (set switched off or out of coverage) the call isautomatically forwarded to the voice mail provided by the public operator (if activated) and the mainset stops ringing.

    As of I1.605.16.c, the new timer no. 373 can be configured in the PCX to bypass public operatorvoice mail forwarding and allow user to take the call from the main set.

    When the call presented to the External Cellular Client is answered before timer expiration, it isidentified as an automatic answer from the voice mail and the call is cancelled. The main setcontinues to ring. The user can take the call from the main set of the tandem.

    This feature is available for External Cellular Clients accessible through ISDN, H.323 and SIPtrunking.

    The call presentation to the twin set association depends on the timer no. 373.

    By default, timer no. 373 is set to 0.

    Timer value different to 0: the timer is activated and it allows to bypass the Cellular Client forwardedto voice mail.

    In case of MyIC mobile on Blackberry and Windows mobile, the feature CellularVoice Mail detection timer cannot be used. The timer no. 373 must be set to 0.This restriction will be resolved in a future patch.

    For more information, refer to the updated System documentation.

    7.1.12

    Supervision with Free Desktop

    As of I1.605.16.c, it is possible to move the supervised set to another node of the same networkwhen supervisor set is busy.

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    21/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    Ed. 01 / 28 May 2010 21 TC1349

    7.1.13Call Transfer (USA Conference Mode)

    As of I1.605.16.c, enabling USA Conference Mode allows to display the Transfer key on a setalready in conversation with a party.

    This parameter is under System -> Other System Param. -> Local Features

    Parameters.

    True: The call transfer can be initiated in conversation (one active call and no call on hold).

    The user must press the Transfer key to dial a directory number (consultation call) and pressthe Transfer key a second time to complete the call transfer.

    False (default option): The call transfer can only be initiated during a consultation call orthree-party conference. The Transfer key only appears during a consultation call.

    For more information, refer to the updated system documentation.

    7.1.14

    3 party conference (USA Conference Mode)

    As of I1.605.16.c, enabling USA Conference Mode allows to display the Conference key on a setalready in conversation with a party.

    This parameter is under System -> Other System Param. -> Local Features

    Parameters.

    True: The three-party conference can be initiated in conversation (one active call and no call

    on hold). The user must press the Conference key to dial a directory number (consultation call)and press the Conference key a second time to complete the three-party conference

    False(default option): The three-party conference can only be initiated during a consultation

    call. The Conference key only appears during a consultation call

    For more information, refer to the updated System documentation.

    7.1.15Management Event on Forward cancellation/activation

    As of I1.605.16.c, CMISE events are generated when a subscribers forward, DND, lock or overflowstates changed. No matter the state change comes from phone set or from management tools likemgr/4760, ACAPI will get the event and communicate with external applications. The external

    applications will receive these events and decide what to do.

    For more information, refer to the updated System documentation.

    7.1.16

    FlexOffice: forwarding cancelled

    As of I1.605.16.c, the newNOEIP INSERV Forwarding Cancelled system option allows to

    cancel the forward of a NOE IP set automatically, when the user comes back from out of service to inservice.

    This implementation is specific to making NOE IP sets out of service by using the prefix or deletingMAC address.

    So whenever the user makes the set out of service by using inserv/outserv prefix or deleting the MACaddress of the set and made back into service, then whatever forwarding is been enabled in the setwill be cancelled automatically.

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    22/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    TC1349 22 Ed. 01 / 28 May 2010

    The newNOEIP INSERV Forwarding Cancelled system option set to TRUE to validate the

    feature is under System option -> System parameters -> Other System Parameters-> Local Features Parameters.

    For more information, refer to the updated System documentation.

    7.1.17UDP to TCP switching for long messages

    As of I1.605.16.c, the newMove to TCP parameter is introduced in SIP proxy layer (SIP ->

    Proxy)

    True: Allows OmniPCX Enterprise switches to TCP automatically for SIP messages longer than

    1300 bytes (in compliance with RFC3261). It was OmniPCX Enterprise behavior in previousversions.

    False: Inhibits this behavior and force use of UDP only. It applies globally, for External

    Gateway, and as well for SIP Extension, SIP Device and SIP External Voice Mail.

    7.1.18Multiple SIP gateways support using via header

    As of version I1.605.16.c, on inbound calls, a new feature enables "Via" header checking in order toselect the proper external gateway to handle the call. It comes in addition to existing matching rules.

    Next, when an inbound request is received it is routed to the right external gateway using thefollowing rules:

    If the "P-Asserted-ID" header is present, and its domain part matches with the "RemoteDomain" of a given External Gateway, the call is processed using this gateway.

    If there isnt any "P-Asserted-ID" header, and the domain part of the "From" header matcheswith the "Remote Domain" of a given External Gateway, the call is processed using thisgateway.

    If one or several "Via" header are available, and the domain part of one of the URLs matcheswith the "Remote Domain" of a given External Gateway, the call is processed using thisgateway.

    Multiple gateways routing on "Via" header has to be activated withVia Header_ Inbound

    Calls Routing parameter under System -> Other System Param. -> SIPParameters.

    7.1.19

    SIP QoS tagging support

    As of I1.605.16.c, a new feature will provide ability to store the IP QoS parameters ("802.1 priority"and "TOS/Diffserv") in the SIP stack at the time of stack initialization, so that the stack can opensockets with the right QoS parameters.

    These parameters will be used for all SIP messages from OmniPCX Enterprise. The IP QoSparameters are fetched from the CPU IPs respective IP domain. If no IP domain is managed, thedefault domains IP QoS parameters are stored in the SIP stack.

    7.1.20

    Force On Net

    As of I1.605.16.c, Routing Applicationparameter is created in external gateway to enable the

    Force On Net feature. In this case OmniPCX Enterprise sends Invite message without SDP to anexternal SIP server provided by Professional Services. OmniPCX Enterprise may receive 302

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    23/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1

    Ed. 01 / 28 May 2010 23 TC1349

    responses from external SIP server for initial INVITE. In this case OmniPCX Enterprise will notconsider 302 as forwarded call. The forward notification (arrow [=>]) symbol) for internal forwardswill be removed from the display of the calling user, during the ringing state and also callingnumber alone be shown in display of called user. For external forwards also, arrow symbol will notbe displayed as it exists up to now in the calling user. And also for this feature 302 responses ismandatory from external SIP server.

    RestrictionWhen SIP device calls the external SIP server it receives the 302 response with forwarded number'sinformation. And also the user display will have the forward notification (arrow [=>]) symbol)because SIP device is treated as an external entity of OmniPCX Enterprise.

    7.1.21

    Interoperability with SBC 5.2.8

    As of version I1.605.16.c, OmniPCX Enterprise allows to interoperate with the SBC 5.2.8.

  • 7/23/2019 Installation Procedure Version i1.605.16 c

    24/24

    OmniPCX Enterprise

    INSTALLATION PROCEDURE FOR VERSIONI1.605.16.c RELEASE 9.1