Alcatel-Lucent OmniPCX Enterprise Manual
  1. Manuals
  2. Brands
  3. Alcatel-Lucent Manuals
  4. Network Hardware
  5. OmniPCX Enterprise
  6. Manual

Alcatel-Lucent OmniPCX Enterprise Manual

Hide thumbs Also See for OmniPCX Enterprise:
Table of Contents

Advertisement

Quick Links

TECHNICAL COMMUNICATION
OmniPCX Enterprise
URGENT
NOT URGENT
SUBJECT : INSTALLATION PROCEDURE FOR VERSION J1.410.34.C – RELEASE 10.0
This is the technical release of OmniPCX Enterprise with the version J1.410.34.c. It corresponds to
Release 10.0.
It is available on Alcatel-Lucent Business Portal (https://businessportal.alcatel-lucent.com) and on DVD
with the references 3BA 27740 AAAB (non secured version) and 3BA 27741 AAAB (secured version).
Technical modes to change the release, new features, registered restrictions and controlled features
are described in the installation procedure for version J1.410.34.c.
No. TC1449
Nb of pages : 108
TEMPORARY
1
Ed. 02
Date : 22 June 2011
PERMANENT

Advertisement

Table of Contents
loading

Related Manuals for Alcatel-Lucent OmniPCX Enterprise

Summary of Contents for Alcatel-Lucent OmniPCX Enterprise

  • Page 1 TEMPORARY PERMANENT SUBJECT : INSTALLATION PROCEDURE FOR VERSION J1.410.34.C – RELEASE 10.0 This is the technical release of OmniPCX Enterprise with the version J1.410.34.c. It corresponds to Release 10.0. It is available on Alcatel-Lucent Business Portal (https://businessportal.alcatel-lucent.com) and on DVD with the references 3BA 27740 AAAB (non secured version) and 3BA 27741 AAAB (secured version).

  • Page 3: Table Of Contents

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 CONTENTS APPLICATION DOMAIN ...............9 REFERENCE DOCUMENTS............9 INTRODUCTION TO RELEASE 10.0 ..........11 New hardware..................11 New features ..................11 3.2.1 Increasing provisioning level ................11 3.2.2 Localization.....................11 3.2.3 Terminals......................11 3.2.4 SIP Enhancement ....................11 3.2.5...
  • Page 4 7.5.1 ABC-F2 trunk group compatibility summary ...........29 7.5.2 Number of compressors/algorithms that can be used with INTIPx and GDx/GAx ........................29 Alcatel-Lucent 4635 voice mail compatibility .......... 30 Hardware compatibility ................31 7.7.1 CPU boards ....................31 7.7.2 Common Hardware CPU boards ..............32 7.7.3...
  • Page 5 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 7.10 OEM/External equipment compatibility........... 39 7.10.1 UPS......................39 7.10.2 V24 over IP ("Moxa" unit) ................39 7.10.3 T38 Fax over IP ....................39 7.10.4 SIP Survivability ...................40 7.10.5 LLDP-MED on IP Touch sets................40 CLIENT INFORMATION..............40...
  • Page 6 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 10.2 Updating R5.1.x, R6.x, R7.x, R8.0.x, R9.x to R10.0 ........46 10.3 OmniPCX 4400 migration to R10.0 ............47 10.3.1 Use of the hardware or software key ............47 10.3.2 Crystal hardware compatibility with an Appliance Server......47 11.
  • Page 7 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 16.1.5 Time-outs (from R3.0)..................55 16.1.6 Accounting (from R3.0) ................55 16.1.7 Filter table (from R3.0) ................55 16.2 Reminder for networked sites migrating from Release < 7.x ....55 16.3 Additional management for IO2N ............55 16.4 Synchronization ..................
  • Page 8 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 TC1449 Ed. 02 / 22 June 2011...

  • Page 9: Application Domain

    − 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 Appliance Server. − The reminder of features released in previous releases.
  • Page 10 TC1458 One way VoIP calls or white calls on installation with INTIP3A boards behind firewalls and TC1479 OmniVista 4760 - Installation procedure for version 5.2.01.03.d - Release 5.2 TC1500 Technical release note for MyICPhone in an OmniPCX Enterprise R10 Hotel environment - Release R200 version 01.026.5 TC1501 OmniVista 8770 - Installation procedure for version 1.0.20.01.b - Release 1.0...

  • Page 11: Introduction To Release 10.0

    − a new installation, − an evolution from R5.0 Lx, R5.x, R6.x, R7.x, R8.x, R9.0, R9.1 to R10.0 − a migration from OmniPCX 4400 to OmniPCX Enterprise R10.0 controlled by OmniPCX 4400 CPU type or Appliance Server (AS). New features from Release 10.0.

  • Page 12: Security

    3.2.8 Serviceability − Remote download evolution Features under PCS If one of the following features has to be implemented on an OmniPCX Enterprise, contact Technical Support for the deployment: − SIP TLS/sRTP for external SIP Gateway Features availability in progress −...

  • Page 13: Content Of The Software Package

    Business Portal Customer Support > Technical Support > Software download > OmniPCX Enterprise > OmniPCX Enterprise > All Release > Generic > Request for Security Patch Access. From Release 6.1.1, dynamic patches will be no more delivered. They are replaced by static patches;...
  • Page 14 PSP software (Phone Set Programming) is not delivered with J1.410.34.c and SJ1.410.34.c DVD versions. PSP software is available on Business Portal (https://businessportal.alcatel-lucent.com) in section Customer Support > Technical Support > Software Download > OmniPCX Enterprise > OmniPCX Enterprise > Phone Set Programming.
  • Page 15 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Released R10.0 Versions Binaries J1.410.34.c rlio_comp2 3.27 3.35 intip3 3.35 Binaries relative to sets noeip 4.31.00 bin40x8 4.31.00 dat40x8 4.31.00 noe40x8 4.31.00 noeipG 4.31.01 bin40x8G 4.31.01 dat40x8G 4.31.01 noe40x8G 4.31.01 noesip4018 2.10.90...
  • Page 16 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Released R10.0 Versions Binaries J1.410.34.c c1nvgpa2 c1nvua c1nvz32 cpl2dpnss 1.11 dpnss dpnssnv dpt1 2.05 dsp_emtl24021 3.01 dsp_gpa 2.01 dsp_vgu dsp0Z32 1.02 dsp1_gpa2 1.09 dsp1nddi2 2.01 dsp2_gpa2 1.10 gpa2tns 1.11 2.24 intof 1.24...

  • Page 17: Before Starting

    The table below shows all the applications and functionalities which are no more provided by OmniPCX Enterprise R10.0, whatever hardware used. Migration batches exist including a specific rate, which have been defined and taken into account automatically by Actis R16.1.
  • Page 18 VoWLAN R1.x VoWLAN R5.x TC1418 (1) VPS35 board is replaced by the VPU6 board for any migration towards OmniPCX Enterprise R10.0. (2) The boards are not authorized on the nodes of a network. LIOE boards are in phase out from Release 6.1. They are no more supported by Release 10.0.

  • Page 19: Applications And Functionalities Dependent On Cpus And Hardware Platform Used

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Applications and functionalities dependent on CPUs and hardware platform used Depending on the type of CPU (CPU6 Step2/CPU7, Appliance Server, Call Server in rack) and the hardware platform used (Crystal or common hardware), certain applications or functionalities are not authorized.

  • Page 20: Voip Network Conformity Check

    175 and no lock 200). If you make a migration to OmniPCX Enterprise, you will be able to see locks 82, 175 and 200. During this migration, if you update the number of DECT sets, only locks 82 and 175 will change, the lock 200 will keep the value of the number of DECT sets present in OmniPCX 4400 configuration.

  • Page 21: Conditions For Installation In Network

    J1.410.34.c – RELEASE 10.0 Example: OmniPCX 4400 with 50 DECT sets: Lock 82 = 50. Migration to OmniPCX Enterprise: Lock 82 = Lock 175 = 50 Lock 200 = 50. If you change the number of DECT sets from 50 to 60: =>...
  • Page 22 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Network interworking Each node of a network must be in Release 8.0 or higher if one of conditions below exist on one of node of the network: • A R8.0 node or higher in XL mode •...

  • Page 23: Installation Of Release 10.0 In Network With Releases 5.1.X, 6.X, 7.X And

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 As of Release 7.0, the number of entities and IP domains changes to 1000 (in Releases < 6.2, the number of entities is 255 and the number of IP domains is 128).

  • Page 24: Audit/Broadcast

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 • R9.0 : H1.301.24 • R8.0.1 : G1.503.9 − The H323 Inter-node protocol parameter must be set to Yes. − The Direct RTP (in network) parameter must be set to Yes.

  • Page 25: Delay (In One Direction) Introduced By Ip Gateways

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Support of transit function (4) Support of direct RTP function LIO P/B/X COMP6 (1) (2) Not applicable LIO P/B/X COMP2 (2) Not applicable LIOE (3) INTIP or INTIP2 GD or GA GD3, GA3 or INTIP3 (1) The LIO P/B/X-COMP6 board is not compatible in R6.x and R7.x.

  • Page 26: Abc-F2 Compatibility Depending On The Hardware And The Type Of Configuration Used (With Or Without Compressed Voice)

    INTIPx) for voice and Fax T38. • The management of H323 direct RTP on OmniPCX Enterprise must be carefully enabled since all H323 terminals of the installation must be able to reroute the H245 RTP flow called "Empty Terminal Capability Set" or "Voice Path Replacement".
  • Page 27 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 • In mixed configurations, ie with IP connections between NGP and GD/INTIP boards, only a single compression & decompression is authorized in case G723 is used, due to delay considerations. In case of G729, a double compression & decompression will correspond to a MOS of 3.4.

  • Page 28: Table Of Abc-F2 Compatibility

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 7.4.2 Table of ABC-F2 compatibility In case a Release 10.0 node (J1.410.34.c minimum) is connected in VoIP ABC-F2 (with or without compression) with another node in Release lower or equal to Release 10.0, there is no restriction as the Direct RTP in network is used.

  • Page 29: Network & Voip Compatibility

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Network & VoIP compatibility 7.5.1 ABC-F2 trunk group compatibility summary Release 10.0 Observation < Release 5.0 Ux ABC trunk group only No progressive migration to a network Release 5.0 Ux UTF-8 compatibility: set the New Local Name Release 5.0 Lx...

  • Page 30: Alcatel-Lucent 4635 Voice Mail Compatibility

    5.4.9 5.3.1 5.4.9 Notes − VPS35 board is replaced by the VPU6 board for any migration towards OmniPCX Enterprise R10.0. − IMAP (A4635 version 5.2.6 or higher) and VPIM (A4635 version 5.1.4) require 64 MB of RAM. TC1449 Ed. 02 / 22 June 2011...

  • Page 31: Hardware Compatibility

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 − Any problem found on a mini or intermediate version as regards maximum version must be the subject of a realignment of the maximum version before escalating the problem. Hardware compatibility As of Release 5.1, the mixing of hardware (crystal hardware &...

  • Page 32: Common Hardware Cpu Boards

    7.7.3 Appliance Server Only Alcatel-Lucent recommended Appliance Servers are to be used. Status Phase to "Out": no more in OmniPCX Enterprise catalog O = Supported by the Release and in catalog = Supported by the Release but no more in catalog...
  • Page 33 IBM X306 Alcatel-Lucent Reference: 3BA 27582 AB Its installation can be carried out only as of PC Installer v2.17. CAUTION It must be ordered only via Alcatel-Lucent. IBM X306M Alcatel-Lucent Reference: 3BA 27582 AC (Note) Its installation can be carried out only as of PC Installer v2.21.

  • Page 34: Hard Disk Capacity

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Note The "Load Balancing" mode is supported by these models. In migrating a system with Appliance Server from a release less than 8.0, check that it has 1 GB of memory.

  • Page 35: Ngp Boards

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Compatibility at 100 Mbits of VH and WM1 shelves for use of CPU6 Step2 and CPU7 boards. The CPU7 board is not allowed in a VH cabinet. All types of shelves are or will be compatible at 100 Mbits. For VH and WM1 cabinets, compatibility...

  • Page 36: Int1/Int2 Boards

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 INTIP3A boards provide up to 120 compressors. If Soft-MSM feature is used, then the maximum number of compressor is 60. The V24 console cable for NGP boards is the same as the one used for CS / GD boards.

  • Page 37: Subdevices & Ip Phone Compatibility (Reprom Reference/Binary Version)

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Subdevices & IP Phone compatibility (Reprom reference/Binary version) Type Reprom Reference Subdevice 2G Asynchronous V24 (4083 ASM) V24/V110/V14 V24 A1 3.01 Asynchronous V24 (4083 ASP) V24/V110/V120 V24 A2 2.06 Asynchronous V24 MAC/PC MPC 3.10...

  • Page 38: Application Compatibility

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Application compatibility Applications Minimum version (Note 1) Released version PC Installer (Note 2) 2.26 Security Center / Personalization center 1.2.01 1.2.01 A4058 (SBC) No more supported A4059 (Multimedia operator) 5.1.2 5.2.5...

  • Page 39: Oem/External Equipment Compatibility

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Applications Minimum version (Note 1) Released version TAPI Premium Server R3 3.2.2 3.3.4 TSAPI Premium Server 6.3.0 / 6.3.1 (Note 4) 6.4.7 XML Web Services Same as OTUC / OT 8400 ICS...

  • Page 40: Sip Survivability

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 T38 Fax over SIP operation is supported with the MP-112 equipment. The transfer in TCP mode is not allowed, the UDP one must be used. From Release 9.0 on, an analog set behind a MP-118 must be set as "SIP Extension". A fax behind a MP-118 will remain in "SIP Device"...

  • Page 41: Reminder Of Changes Appeared In Release 8.0 And 8.0.1

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Reminder of changes appeared in Release 8.0 and 8.0.1 − Dial by name with IME (Input Method Editor) on 40x8 and 40x9 sets. − Localization of softkeys on 40x8 and 40x9 sets.

  • Page 42: Preparation

    Ensure that you have the voice guides required in Release 10.0. 9.2.1 System voice guides The version of system voice guides compatible with the OmniPCX Enterprise R10.0 is v5.3 CD-ROM reference: 3BA 57423 AAAG. The following files are provided on the CD-ROM: −...
  • Page 43 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 They can be downloaded from the Business Portal section Customer Support > Technical Support > Software Download > OmniPCX Enterprise > 4645. The following languages are available: Country Code Law A Law μ...

  • Page 44: Ops

    INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 The Actis version for the OmniPCX Enterprise is R16.1, the catalog is referenced E16. The locks are based on a software key which is unique. This software key is calculated according to the licenses and the physical number of the CPU.

  • Page 45: Rebuilding The Database Before Saving

    − The shelves already created in position 18 and 19 must be moved before the translation. If this is not done, they will not start. In fact, when migrating from OmniPCX 4400 to OmniPCX Enterprise R10.0 with change of CPU 4400 by an Appliance Server, there is an automatic translation of shelves created in these 2 positions.

  • Page 46: Saving Actis Files In The Image Of The Site

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 As the IP addressing plan has changed since Release 3, it is not possible to reuse the Chorus data from a previous version in its current state. The restoration of Chorus data from a release lower than 3.0 is possible only in the case of a intermediate translation in Release ≤...

  • Page 47: Omnipcx 4400 Migration To R10.0

    If this is not done, they will not start. In fact, when migrating from OmniPCX 4400 to OmniPCX Enterprise R10.0 with change of CPU 4400 by an Appliance Server, there is an automatic translation of shelves created in these 2 positions. This automatic translation does not exist if the CPU of type 4400 is retained.

  • Page 48: Security Activated By Default During A Installation

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 11.1.1 Security activated by default during a installation As of Release 6.2, the first standard installation, a list of security levels are displayed before any other configuration is possible. This list proposed in a menu on the first login on Call Server, makes it possible to sensitize the Partner Business on the policy of security which he will have chosen for the system.

  • Page 49: Using The Remote Download

    Read the system CPUID This method is to be applied in particular in the case of an Appliance Server not controlled via Alcatel-Lucent (no marking on the server). 11.1.5 Creating a blank database A blank database should only be created for CPU installation on a new site...

  • Page 50: Restoring The Database And Site Tickets

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 password SoftInst option 7 Database tools option 2 Create an empty database Enter country name example "zb" for Zimbabwe 11.2 Restoring the database and site tickets login swinst password SoftInst option 4 Backup &...

  • Page 51: Translations

    OmniPCX Enterprise 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.

  • Page 52: Installing Ops Files

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 − As of Release 10.0, the Direct RTP mode (in network) is automatically enabled and the relative parameter removed. The same is done for H323 Internode Protocol system parameter. − As of Release 10.0, the system boolean to activate the application 4760i is set automatically to False and then removed (the application is no more supported).

  • Page 53: Updating The Beta Test Systems

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 13. UPDATING THE BETA TEST SYSTEMS All the Release 10 beta test sites should evolve to released version J1.410.34.c. 14. SYSTEM MANAGEMENT Use the menu swinst/System management. 14.1 Declaring the automatic start-up of the telephone...

  • Page 54: Compulsory Minimum Additional Database Management

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 16. COMPULSORY MINIMUM ADDITIONAL DATABASE MANAGEMENT 16.1 Reminder for sites migrating from Release < 3.0 16.1.1 IP addressing plan (from R3.0) The new management of the IP interfaces in OmniPCX 4400 does not allow default declaration of all the interfaces of all the possible network nodes.

  • Page 55: Time-Outs (From R3.0)

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 16.1.5 Time-outs (from R3.0) Control the value of time-out 144 (Timeout for distributed call). It must be greater than or equal to 600. Control the value of time-out 188 (Timer for Release of set reserved by attendant). It must be greater than 3000;...

  • Page 56: Synchronization

    In this document, "Direct RTP" corresponds to "Direct RTP in network". In all nodes of the sub-network the Direct RTP parameter must be set to Yes. In an OmniPCX Enterprise R10.0 system, this parameter is removed (validated by default). 16.5.2 Frame VoIP (Enhanced quality voice) The Frame VoIP parameter (Enhanced quality voice in previous versions) must be identical on each node of a network.

  • Page 57: Direct Rtp For H323 Terminals

    16.5.4 Inter-node protocol H323 The H323 Inter-node protocol parameter must be set to Yes in all nodes of the sub-network. In an OmniPCX Enterprise R10.0 system, this parameter is removed (validated by default). 16.5.5 Pre-login (V120) As of Release 5.1, the pre-login path as changed as regards Unix versions. It is located under the DHS3bin/servers or usr2/servers directory.

  • Page 58: Checking Correct Operation

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 SSM & MSM downloading procedure after an upgrade in R10.0 After upgrading in SJ1.410.34.c and with the RUNTEL done, you must update the IP Touch Security boxes (MSM, SSM) as follows: 1 Check that the versions 3.3.03 for bin_SM or 3.3.05 for bin_SM2 is managed in mgr.
  • Page 59 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 Faced with a board initialization problem, check that the value MTU in the IP Parameters is correctly managed at 256. − Check conference type management. Coming from Release 4.1 or 4.11, it is not possible to retain two types of conference: for example the programmed conference and the conference directed with modulo circuit 30.
  • Page 60 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION J1.410.34.c – RELEASE 10.0 TC1449 Ed. 02 / 22 June 2011...
  • Page 61 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION APPENDIX 1 J1.410.34.c – RELEASE 10.0 NEW HARDWARE AND FEATURES NEW HARDWARE AND FEATURES CONTENTS INTRODUCTION ................3 NEW HARDWARE AND FEATURES FROM RELEASE 10.0 ....3 2.1. New hardware..................3 2.1.1. eZ32-2 board ....................3 2.2.
  • Page 62 OmniPCX Enterprise APPENDIX 1 INSTALLATION PROCEDURE FOR VERSION NEW HARDWARE AND FEATURES J1.410.34.c – RELEASE 10.0 TC1449 Ed. 02 / 22 June 2011...

  • Page 63: Introduction

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION APPENDIX 1 J1.410.34.c – RELEASE 10.0 NEW HARDWARE AND FEATURES INTRODUCTION Consult the Marketing documentation available on Business Portal. REMINDER The main features included in previous releases are detailed in the technical communication TC0780 New hardware and features from Release 5.1.

  • Page 64: Terminals

    OmniPCX Enterprise APPENDIX 1 INSTALLATION PROCEDURE FOR VERSION NEW HARDWARE AND FEATURES J1.410.34.c – RELEASE 10.0 2.2.3. Terminals 2.2.3.1. MIPT OmniTouch 8118 and 8128 handsets As of Release 10.0, the new OmniTouch 8118 and 8128 WLAN handsets are supported (the support is also available on R9.0 and R9.1).

  • Page 65: Sip Enhancement

    SIP Enhancement 2.2.4.1. New SIP improvement for interworking with Open Touch Solution As of Release 10.0, new SIP improvements allow the interworking of OmniPCX Enterprise in the new Open Touch Solution. 2.2.4.2. SIP Trunk enhancement: CLI display with From header, even if P-Asserted-ID header is available (Incoming call) Up to R9.1, Call Presentation mechanism does not scope with all situations because all carriers do...

  • Page 66: Security

    • A new parameter Re-transmission number for INVITE is introduced in the SIP proxy object: Its default value is 2. Saying that, it takes now 2s before OmniPCX Enterprise considers that no response has been received and call has failed. In case of a SIP trunking call to an external gateway using ARS, the call will overflow to an alternate route managed in the current route list faster than with previous software releases.

  • Page 67: Applications

    5.2.3. 2.2.7.2. OmniPCX Enterprise PC Installer on Windows 7 32bits As of Release 10.0, the OmniPCX Enterprise PC Installer 3.2 is compatible with Windows 7 OS (Professional Edition 32-bit System). The OmniPCX Enterprise PC Installer version 3.2 is retro compatible with all OmniPCX Enterprise releases.

  • Page 68: Features Under Pcs

    The TLS protocol protects SIP signaling and the SRTP protocol (two keys: one key is used to encrypt sent voice flow and an other key is used to encrypt received flows) protects voice flows. TLS can be used to secure SIP Trunks configured on the OmniPCX Enterprise to a Carrier or Service Provider network (Public SIP Trunking).
  • Page 69 • As of Release 10.0, the TLS/SRTP (two keys) is not available in an ABC-F network, if a Public SIP Trunks is secured with TLS and SRTP on a OmniPCX Enterprise node in Release 10.0, network encryption (meaning encryption over OmniPCX Enterprise ABC IP network) between nodes mustn’t be activated.

  • Page 70: Features Availability In Progress

    OmniPCX Enterprise APPENDIX 1 INSTALLATION PROCEDURE FOR VERSION NEW HARDWARE AND FEATURES J1.410.34.c – RELEASE 10.0 SIP Trunks secured with TLS and RTP and ABC IP Network Encryption SIP Trunks secured with TLS and SRTP and ABC IP Network without Encryption 2.4.

  • Page 71: Call Routing Groups

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION APPENDIX 1 J1.410.34.c – RELEASE 10.0 NEW HARDWARE AND FEATURES 2.4.2. Call Routing Groups 2.4.3. NOE in SIP with or without TLS protocol encapsulation Ed. 02 / 22 June 2011 TC1449...
  • Page 72 OmniPCX Enterprise APPENDIX 1 INSTALLATION PROCEDURE FOR VERSION NEW HARDWARE AND FEATURES J1.410.34.c – RELEASE 10.0 TC1449 Ed. 02 / 22 June 2011...
  • Page 73 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION APPENDIX 2 J1.410.34.c – RELEASE 10.0 REMARKS & RESTRICTIONS REMARKS & RESTRICTIONS CONTENTS SYSTEM..................3 COMMUNICATION SERVERS ............6 2.1. Call Server CPU ..................6 2.2. Appliance Server ..................7 2.3. Blade Center..................... 8 2.4. OmniPCX 4400 CPU ................. 8 2.5.
  • Page 74 OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 6.4. NGP boards .................... 14 VOIP..................16 ABC-F IP TRUNK GROUP............19 SIP .....................19 10. SETS ..................21 10.1. IP Phone V1 – V1S................... 21 10.2. IP Phone V2 (e-Reflexe)................21 10.3.

  • Page 75: System

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION APPENDIX 2 J1.410.34.c – RELEASE 10.0 REMARKS & RESTRICTIONS SYSTEM − Bios for Call Server CPU-CS. As of Release 5.1, the Call Server (CS board) Bios version is higher than 8.17. This version allows access to certain Bios functions (the main one being the Ethernet boot) which could not be accessed from the R5.0 Lx since only R&D knew the password.
  • Page 76 OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 Initializing Intel(R) Boot Agent GE v1.2.16P7 PXE 2.0 Build 083 (WfM 2.0) Press Ctrl+S to enter the Setup Menu. Version 1.23.1109. Copyright (C) 2007 American Megatrends, Inc.
  • Page 77 If this is not done, they will not start. In fact, when migrating from OmniPCX 4400 to OmniPCX Enterprise R5.1.x, R6.0.x or R6.1.x with change of CPU 4400 by an Appliance Server, there is an automatic translation of shelves created in these 2 positions. This automatic translation does not exist if the CPU of type 4400 is retained.

  • Page 78: Communication Servers

    OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 − NAT/PAT is globally not compatible with the different elements of the system (e-CS, GD, IP- Phones). − Pre-login (V120). • Since Release R5.1, the path for the pre_login is different from the previous Unix versions.

  • Page 79: Appliance Server

    APPENDIX 2 J1.410.34.c – RELEASE 10.0 REMARKS & RESTRICTIONS 2.2. Appliance Server Only Alcatel-Lucent recommended Appliance Servers are to be used. Model References IBM X305 Alcatel-Lucent Reference: 3BA 00438 AA IBM reference (in case of external purchase): Model Type : 8673-62X...

  • Page 80: Blade Center

    In a standard installation of an IBM X3250 M2, the following message is displayed. It states that any hard disk larger than 80 GB will not be used to its real capacity. Alcatel-Lucent e-Mediate Linux installation +-------------------+ Disk size +--------------------+ Disk too big : use optimized up to 80000MB only.

  • Page 81: Save And Restore On Usb Key

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION APPENDIX 2 J1.410.34.c – RELEASE 10.0 REMARKS & RESTRICTIONS − CPU6 Step2 functions at 100 Mbits Full Duplex. − You can manage the mode and the rate CPU7 boards. The setting of CPU7 board and of the port of the switch on which the CPU7 board is connected, must be the same.

  • Page 82: Spatial Redundancy

    OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 SPATIAL REDUNDANCY − In case of CS, the Main and Standby Call Server must not be located in the same rack. − Do not use SLANX4 but an external switch (LANX16-1 or customer switch) in order to be able to unplug a Call Server without disturbing other elements.

  • Page 83: Power Supply

    Server switch-over is about 10 to 20 seconds. • The 4008 / 4018 sets in SIP mode on OmniPCX Enterprise cannot be used in a spatial redundancy configuration. This limitation will be removed in a future patch of Release 9.1.

  • Page 84: Ip Crystal Media Gateway

    OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 IP CRYSTAL MEDIA GATEWAY In the document the name "INTIPA or B" concerns the INTIP board as well as the INTIP2 board. − Only one Voice Hub or M1 or M2 cabinet is supported for the IP Crystal Media Gateway in the main zone.

  • Page 85: Media Gateway

    Release 9.0: one containing the encryption mechanisms and one without. As for the IP Touch sets since Release 6.2, the generic OmniPCX Enterprise versions provide the binaries without the encryption mechanisms, whereas the binaries with these mechanisms will be available in the corresponding secured patch.

  • Page 86: Remote Connection Towards Gd/Ga/Intip Boards

    OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 6.3. Remote connection towards GD/GA/INTIP boards 6.3.1. Release 9.0 before patch H1.301.38 For safety reasons, telnet access towards GD/GA/INTIP boards has been disabled. The remote access towards INTIP boards remains available using the cpl_online command.
  • Page 87 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION APPENDIX 2 J1.410.34.c – RELEASE 10.0 REMARKS & RESTRICTIONS NGP binaries (secured or not) are systematically signed. This signature is verified in all cases by Call Server (mode protect or bypass). Resources provisioning on Common Hardware NGP boards:...

  • Page 88: Voip

    In a network with R8.x nodes, there must not be LIOE and TSC-LIOE boards. − Direct RTP H323. The management of H323 direct RTP on OmniPCX Enterprise must be carefully enabled since all H323 terminals of the installation must be able to reroute the H245 RTP flow called "Empty Terminal Capability Set"...
  • Page 89 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION APPENDIX 2 J1.410.34.c – RELEASE 10.0 REMARKS & RESTRICTIONS − For a GDx/GAx/INTIPx, the number of trunks in a trunk group must not be managed. You must retain the default configuration (30 trunks created). The limitation of compressors will be carried out by managing the VPN TS % in the trunk group or by the "VPN Call Limitation"...
  • Page 90 OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 • If Fax behind GD or INTIP are used, verify and manage if necessary value 7 in "V21 Jitter Buffer Length" under "IP/Fax parameters": all GDs and INTIP must be rebooted to validate this value •...

  • Page 91: Abc-F Ip Trunk Group

    SIP set, compared with the SIP standard (use of many OmniPCX Enterprise prefixes, etc.). Only the sets mentioned in the SEPLOS "white list" (refer to the technical documentation...
  • Page 92 OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 "white list" continue to be supported with the basic level of service offered by the SIP standard (functioning equivalent to R8.0). When migrating a system with "SIP Device" / "External set" to R9.0, the system moves these sets into the new mode (SIP extension) automatically.

  • Page 93: Sets

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION APPENDIX 2 J1.410.34.c – RELEASE 10.0 REMARKS & RESTRICTIONS − Support of 4008/4018 sets in SIP mode. Refer to technical communication TC1255 4008 / 4018 SIP set deployment with OmniPCX Enterprise for detailed information regarding the deployment of these sets in an enterprise network.

  • Page 94: Alcatel Series 8 & 9 Sets

    OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 These new modules are marked "Add-on UA/IP" on the packaging and on the label pasted under the module. 10.3. Alcatel series 8 & 9 sets −...
  • Page 95 Alcatel-Lucent recommends not to use these two technologies simultaneously. − You can connect up to 3 Electronic Add-On modules. These modules cannot be mixed with the other types of Add-on modules.

  • Page 96: Mipt 300&600 Handsets

    OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 From Release 6.1, the available configurations are: • one Add-on module 10 keys • one Add-on module 40 keys • one Add-on module 40 keys + one Add-on module 10 keys •...

  • Page 97: Dect

    − MIPT handsets support codecs G711 and G729A. − MIPT handsets supports the WEP, WPA and WPA2-PSK − As of Release 8.0, VoWLAN offer operates around Alcatel-Lucent IP Touch 310&610 (MIPT 310&610) handsets, integrating the NOE protocol (New Office Environment) and compatible with or without Mobile IP Touch SVP Server (SVP Server).

  • Page 98: Ua Extender 4051/4052

    The IP Touch Security feature works with a secured patch, delivered in complement of the generic version. To get this secured patch, a request must be made on Alcatel-Lucent Business Partner Website. This secured patch has the same name as the generic delivery to which it is referred preceded by the letter S (for Security).

  • Page 99: Sip Tls For External Gateway

    UA/NOE communications. The IPsec protocol protects UA/NOE signaling and the SRTP protocol protects the sent and received voice flows. As of OmniPCX Enterprise Release 10.0, SIP TLS/SRTP protocols are supported to secure SIP Trunks configured on the OXE to a Carrier or Service Provider network (Public SIP Trunking in ISDN mode).

  • Page 100: Omnivista 4760I

    13.2. OmniVista 4760i This application is no more supported and can’t be activated anymore. Use mgr or OmniVista 4760 to configure the OmniPCX Enterprise. In case of upgrade to Release 10.0, the application will be deactivated, if previously activated. 13.3.

  • Page 101: Directory

    Bellcore. • Some telephones only displayed the calling number and not the calling name. • Alcatel-Lucent can't test and maintain a list of compatible telephone because there are thousands of different phones. Business Partner should contact Professional Services to undertake the validation of specific telephones on a case-by-case basis. Telephone vendors should contact the Alcatel-Lucent Business Partner Program to carry out such validation of their product.
  • Page 102 In Release 8.0.1, a new client_ldap tool is available. It performs an LDAP search on telnet access. You don't need anymore to give LDAP parameters, such tool use actual OmniPCX Enterprise configuration and requires only to specify the Entity Id.

  • Page 103: Boards

    OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION APPENDIX 2 J1.410.34.c – RELEASE 10.0 REMARKS & RESTRICTIONS If the UTF-8 field is completed in user data with the same information as Latin name, the search of name in the directory, using "Call by name", will give a double result ( Latin name + UTF-8 name).
  • Page 104 OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 − Customized ringing melody. The customized ringing file is limited to 16 melodies. − T0 interface on Media Gateway. • T0 "network mode" is only supported with the BRA board. Refer to the technical...
  • Page 105 OmniPCX Enterprise INSTALLATION PROCEDURE FOR VERSION APPENDIX 2 J1.410.34.c – RELEASE 10.0 REMARKS & RESTRICTIONS ♦ R2 detection + DTMF Q23/Q23X Detection + Tone (single and dual) Detection: payload of 5 % for R2: maximum 20 detections for R2 when no Tone Detection,...
  • Page 106 OmniPCX Enterprise APPENDIX 2 INSTALLATION PROCEDURE FOR VERSION REMARKS & RESTRICTIONS J1.410.34.c – RELEASE 10.0 • ACT 99 can't be synchronizing. − RMA. • No hardware remote reset of the e-CS in case of an Appliance Server. − eRMA. •...
  • Page 107 All the phone services are lost when changing from a local call towards a public call. − MOXA Box. The MOXA box is used to increase the number of serial ports of OmnipCX Enterprise. The aim of this Release 6.1 feature is to make easier the configuration of serial ports of the box: single management of information in mgr instead of two distinct programs (mgr and npadm).
  • Page 108 − Installation of ACT shelves in computer cabinets. OmniPCX Enterprise ACT shelves must be installed in computer cabinets closed and equipped with fans. They must comply with the same CEM and safety standards as the OmniPCX Enterprise ACT shelves: •...

Table of Contents