Professional Documents
Culture Documents
omniPCX R9 MOCS
omniPCX R9 MOCS
Alcatel-Lucent Business Solutions for Mid-sized Enterprises & Alcatel-Lucent Corporate Solutions for Large Enterprises
OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
Alcatel-Lucent OmniPCX Enterprise Communications Server R9.0:................................ 4 1.1 OXE R9.0 Objectives ................................................................................ 4 1.2 SIP enhancements................................................................................... 4 1.2.1 NOE/SIP Dual stack for IP Touch ............................................................ 5 1.2.2 Telephony service level enhancement for 3rd party SIP endpoints..................... 5 1.2.3 SIP & strategic partners ................................................................... 5 1.2.4 SIP Device Management ...................................................................... 6 1.2.5 SIP Trunks optimization ...................................................................... 7 1.2.6 SIP Proxy enhancement when Com Server switchover................................... 7 1.2.7 DNS SRV (client) on OXE...................................................................... 8 1.2.8 Session timer using update method ........................................................ 8 1.3 Session Boarder Controller......................................................................... 9 1.3.1 Connectivity................................................................................... 10 1.3.2 Interoperability............................................................................... 10 1.3.3 Security ........................................................................................ 10 1.3.4 Quality of service: SLA enforcement and control....................................... 10 1.3.5 Use cases in OXE environment ............................................................. 11 1.4 Security.............................................................................................. 12 1.4.1 GD signalling encryption .................................................................... 12 1.4.2 Secured telnet access of Gateway Board ................................................. 12 1.4.3 802.1X TLS .................................................................................... 13 1.5 IP Foundation enhancements..................................................................... 13 1.5.1 IP ABC Trunk Group .......................................................................... 13 1.5.2 Calling Line Identity per IP domain........................................................ 14 1.5.3 Fax T38 for internal calls ................................................................... 16 1.5.4 VoIP tickets in real time & Health-Check................................................. 16 1.6 Multi-Time Zone per Com Server ................................................................ 17 1.7 Miscellaneous ....................................................................................... 18 1.7.1 Attendant display enhancement ........................................................... 18 1.7.2 Attendant Application 4059................................................................. 19 1.7.3 IP Desktop Softphone ........................................................................ 19 1.7.4 Free Desktop enhancement................................................................. 19 1.7.5 Call handling enhancement External call control via PIN code ...................... 20 1.7.6 Valenciano language support ............................................................... 20 1.7.7 Number of calls on DPNSS & DASS2 link................................................... 20 1.7.8 Increasing the amount of domain of management ...................................... 21 1.7.9 Networking compatibility ................................................................... 21 2 Genesys Entreprise Telephony Server (GETS)........................................................ 22 2.1 GETS for Microsoft Office Communicator....................................................... 22 3 Mobility Solutions ........................................................................................ 23 3.1 Remote extension: activation / de-activation ................................................. 23 3.2 WLAN: MIPT compatibility with Passive Com Server .......................................... 23 4 Infrastructure / Hardware evolution & obsolescence .............................................. 24 4.1 Hardware evolution / cost reduction & obsolescence management........................ 24 4.2 Introducing the PowerDsine 7024G .............................................................. 25
Page 2 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
Page 3 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
This document is the Release Note of the H2 2008's Global Offer for Large and Medium Enterprise market segments.
This document is intended to provide a synthesis of the commercial offer to persons involved in marketing, business development, sales and pre sales support activities for the launching and support of this commercial offer.
Also, the other topics are : IP foundations enhancements (IP_ABC on trunk group, Calling line identity per IP domain, etc) Multi-time zone offering Mobility solutions Session Border Controller ..and many others
Page 4 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
Based on IETF standards, SIP solutions facilitate deployments across any IP network topology and are compatible with Firewalls and Session Border Controller solutions. SIP provides also a manufacturer independence, offering a greater choice of applications and endpoints, together with the potential to reduce costs for equipment and the management of communication services.
1.2.2 Telephony service level enhancement for 3rd party SIP endpoints
The Alcatel-Lucent OmniPCX Enterprise R9.0 will offer interoperability with 3rd party SIP endpoints. In business environment (hunting group, baring, services by prefix, ) In an hospitality environment SIP endpoint monitoring (Association of advanced application with SIP sets)
interoperability only, and not the end user functionality or system interfaces provided by the devices themselves (ergonomics, audio including hands-free, IP infra, availability, security, manageability and serviceability, etc). Due to the progression of SIP requirements and market trend, Alcatel-Lucent is going to empowered the relationship with some partners (Thomson, Teledex, SIP wifi partner) to provide end-to-end solutions. Therefore, in correlation with the feature regarding the Telephony service level enhancement for SIP endpoints in OXE, strong integration and tests have to be scheduled with these partners.
For ALE Fix/SIP Device Management, the administrator should be able to create/modify/delete an OXE user for legacy devices (IP-Touch, Analog, DECT ...) and a SIP user for SIP device (SIP Thomson) through OmniVista 4760 Network Management GUI (for more information, refer to A4760 Product Description and Feature List). The DM Application Server is able to generate configuration files including device/user parameters set via DM GUI. On using HTTP(s) transport, the DM Application Server is able to update automatically devices by transferring software and files configuration to the devices. The transfer is initiated by the devices. For devices handled by OXE, on SIP users/ SIP devices management actions done by OXE administrator, the DM server is able to synchronize configuration parameters shared by DM and OXE. For devices handled by 3rd party SIP Call Server, no synchronization is provided between DM Server and 3rd party SIP Call server.
For all devices, configuration is based on transferring from DM server to devices configuration files formalism with XML or plain text.
SIP Devices Management global overview
Page 6 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
On scalability point of view, the dimensioning requirement is to be able to manage up to 16k devices or SIP users. In case of OmniVista 4760 already installed, it is able to be deployed on the same physical server. Security: HTTP(s) with SIP devices for transferring Device firmware and Device file configuration. Transfer is initiated by SIP device on reboot or by polling (Timeout is a parameter of the configuration file), so device updating is done asynchronously when SIP devices request the DM Management Server. License model:
A 4760 software lock corresponding to the DM application right. Several FlexLM licenses: quantitative per all SIP devices (ALE and 3rd party) and per 3rd party SIP device type.
Page 8 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
Compa ny
DMZ
Mobility Server
Page 9 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
1.3.1 Connectivity
Supports an Application Layer Gateway for Network Address Translator (NAT/PAT) of VoIP protocols. Also supports Hosted NAT traversal to connect remote SIP phones.
1.3.2 Interoperability
VoIP interoperability is often complicated because all products, which claim to be standard ,implement the protocols differently which results in interoperability issues SBC supports : - codec list management for better negotiation between endpoints - transcoding of DTMF (info to RFC4733) - protocol normalization: suppressing or translating some headers - codec transcoding (not used in OXE environment) - routing (multi-carrier, multi-IPPBX)
1.3.3 Security
it is a VOIP firewall (blocks data traffics) and cooperate with existing firewall devices in the DMZ. It uses an extensible policy engine to decide whether particular calls should be admitted, and may open pinholes in the Media Proxy function to allow media to pass through (or alternatively, the firewall may be statically configured to allow this). it performs a topology-hiding function to prevent customers or other service providers from learning details about how the enterprise network is configured, or how calls being placed to the enterprise are routed. They do this by rewriting VoIP signaling messages that traverse the SBC. They eliminate bad VoIP signalling and media protocol at the network boundary. Force media to traverse the SBC by changing SDP parameters in the SIP session.
do not exceed the limits imposed by the traffic policy. Fault tolerance, must ensure 99.999% (five nines) availability. Redundancy with transparency. Tracking the progress of each call for the purposes of billing, and producing Call Detail Reports on quality thanks to a QOS probe. RTP flow redirection for direct IP to IP flow if both endpoints are on the same side of the SB
providing NAT traversal, for Alcatel-Lucent proprietary protocols, as well as security, QoS, bandwidth management, routing functions
board by: Closing telnet access and remove telnet client to GD Configuration on demand from the Com Server
Now, with the Alcatel-Lucent OmniPCX Enterprise R9.0 IP ABC-F trunk group will provide: Same ABC-F level of service as current TDM ABC-F trunk group Direct RTP between sub-networks with CAC management ABC-F signaling and RTP flows encryption if Alcatel encryption solution is available at both end points belonging to different ABC sub-network.
Page 13 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
Possibility to manage heterogeneous numbering plan in the supra-network Compatible with current network services of the OmniPCX Enterprise (e.g. ARS, )
Page 14 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
CLI per IP domain is applicable for TDM and IP trunks (H323 and SIP). It replaces user CLI. CLI per IP domain can be used for following mobile device or users IP Touch 8 series and SIP phones Free desktop My IC IP softphone (mono node) DECT sets
CLI per IP domain may be used only for emergency calls. (when dialling 112, 911 etc), while user CLI is sent for all other type of calls. . See diagram below
Page 15 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
A new parameter is included in IP domain data: calling number CLI per IP domain is not applicable to internal calls .
R9 brings the possibility to use T38 also for internal calls This is to phase out smoothly the fax relay protocol and replace proprietary protocol by standard one when feasible. Limit: T38 for internal calls must be configured on all the nodes of an ABC network. Network including R7.1 or early version of R8 are not supported.
In addition to the Com Server role (main, standby, unknown, PCS), cumulative and instant Counters regarding OXE activities are provided by the OmniPCX Enterprises MIB: Available and unreachable N party conference resources (per IP domain), Number of in/out-service sets, CAC availability / CAC overrun per IP domain, Number of registered un-registered SIP sets,
This MIB will be accessible by GET SNMP (v1, v2 or v3) request from the supervisor. VoIP tickets in Real Time: Current VoIP tickets (including call duration, Nb Packets Sent, Nb Octets Sent, Nb Packets Received, Nb Octets Received, Nb Packets Lost Nb, Jitter ms, Latency ms, Incoming Calls Nb, Outgoing Calls Nb, Internal Calls Nb, Packet Loss rate ) are sent in real time to external supervisor. Buffer is available to store the VoIP tickets when the link between the supervisor and the Com Server is down. Documentation regarding the format of VoIP tickets and the real-time mechanism/protocol is available for our partners through Alcatel Application Partner Program.
In addition, because phone sets could be located in several countries where system /basic tones (dec, busy, ring back, ) and trunk parameters are different, it is necessary to manage these parameters per IP domain, in function of country characteristics. Tones and trunks parameters are defined in a file which is loaded during the system initialization or on demand by the technician. This multi-country facility is available from OXE R9.0.1. Restrictions: Display format choice (12 or 24 hour) remains a system option SIP sets display their own date and time. Application not compatible with Multi Time Zone OmniTouch Standard and Premium Edition (at statistic and calendar levels). MyAssistant, MyIC (call log), MyMessaging and API XML Framework of OmniTouch Unified Communication. Voice message deposit time with A4645 and A4635 Voice Mails (Note: new A8440 Voice Mail, compatible with OXE R9.0.1, is Multi Time Zone compatible). Free Desktop with Auto login/logoff. Entitys calendar uses local time but it is not dependant on an eventual system Daylight Saving Time. ARS mechanism depends on the system time. Past Time Performance and VoIP performance tickets do not take in account this new offset information. If time is updated by ISDN, the public interface has to belong to the default Time Zone. Due to very specific country parameters, centralization of Com Server is not always possible. Therefore, regarding design rules, refer to Pre-Sales design guide for additional information.
After forwarding, the called number will be displayed on the display of the user receiving the call. If the called number is associated to an abbreviated number and name, only the called number will be displayed. The requirement consists in displaying the called number instead of trunk group name.
configured in mono server. Defense mechanism Alcatel-Lucent OmniPCX Enterprise Communication Server authorizes up to 3 simultaneous accesses to its database. Around 45 seconds are necessary to allocate the 3 accesses to the new extensions. It requires approximately 15 minutes to allocate the Free Desktop Environment to sixty users. Free Desktop provides a protection mechanism to protect from overuse by reallocating users in queue. Users can know their waiting time and avoid move operation if they want. Compatibility with IP Desktop Softphone Move from / to IP desktop Softphone is possible from the Softphone GUI. The mobility is guaranteed within the same range of terminal. Therefore, a user can move from IP Desktop Softphone to IP Touch 4028 / 38 / 68 and 4029 / 39 hard-phones. Serviceability: import / provisioning To facilitate the deployments, provisioning of Free Desktop users rights is possible thru Excel or CSV files : the administrator can now add, modify users by importing/exporting new records directly from CSV, Excel files.
1.7.5 Call handling enhancement External call control via PIN code
For selected external numbers (e.g. long distant call), the user have to dial a Personal Identifier Number (1 to 8 digits). It is possible to request PIN code only when dialling from unauthorized phones. A user can make a call controlled by PIN code from any phone. PIN code is managed in function of COS of users.
Page 21 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
M icro so ft
or
MOC OCS
M y T W c o n f.
SIP /C S T A
GETS
(N O E ) CSTA
O m n iP C X E n te rp rise
Page 22 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
3 Mobility Solutions
3.1 Remote extension: activation / de-activation
The purpose of this feature is to deactivate/activate the remote set ringing when the remote extension is called. Several types of configuration can be done: The desk phone and the Remote Extension are configured in Twin-set mode (more common configuration mode, called one number reach) The desk phone is supervised by the Remote Extension The remote extension is not associated to desk phone but can be called directly or via call forward or overflow
Two new prefixes and new icons/ strings on the phone sets are provided for user to deactivate/activate remote set ringing when remote extension is called.
Dual ring on
User/ technician can manage the status of remote extension deactivation/activation by manager tools (mgr or 4760). The feature also gives the possibility for main set of twin-set to monitor and manage the status of remote extension deactivation/activation in case the secondary set is a remote extension. This feature is independent on Business and Private mode of GSM.
Item
CPU6 board OBCA2 card CPU7 board
EoL
2008 2008 2008
Substitute
Crystal CPU boards CPU7-2 ION2 CPU7-2
Comments
DPT1 board VH patch panel INT-IP board module VH patch panel 32XRJ45 VH patch panel 16XRJ45 VH patch panel CPU/INT
Crystal remote Media Gateway connection No more Law-A/Law Mu 2008 DPT1-2 conversion Voice Hub & WM1 items 2008 2008 2008 2008
Page 24 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
WM1 variable speed fan kit WM1 autonomy battery 1.2AH Cable TNLO/INT2m Cable TELCO 2x50pts5m FPROG card Flash boot SPA3 Flash bios VMP35 DECT coverage tool China
2008 2008 Cables 2008 2008 Technical Tools 2008 2008 2008 2008 Tool for programming CPU6 USA only
EoL: Substitute:
5 Launching strategy
5.1 Country availability
Alcatel-Lucent OmniPCX Enterprise R9.0 will be available worldwide. Possible restriction on component offer availability due to local approval issues are mentioned in
Page 25 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
5.2 Planning
Step ACTIS 13.1.0 Program step Date December 1,2008 Comment Availability for download for OmniPCX Enterprise R8.0, OmniTouch Contact Center Premium and Std Edition, etc Order acceptance, standard lead-time for shipments applies
Start of shipment
DR4
December 1, 2008
End of document
Page 26 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008
www.alcatel-lucent.com
Page 27 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008