omniPCX R9 MOCS

Alcatel-Lucent OmniPCX Enterprise Communication Server RELEASE NOTE for R9.0 North America December, 2008

Alcatel-Lucent Business Solutions for Mid-sized Enterprises & Alcatel-Lucent Corporate Solutions for Large Enterprises

8AL020033503DRASA_ed01 December, 2008

OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

1

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 .............................................................. 25Page 2 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

5

Launching strategy....................................................................................... 25 5.1 Country availability ................................................................................ 25 5.2 Planning ............................................................................................. 26

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.

1 Alcatel-Lucent OmniPCX Enterprise Communications Server R9.0:1.1 OXE R9.0 ObjectivesFor 2008 and 2009, the product strategy of the Alcatel Enterprise is to improve the SIP offering , and SIP openness of our solution, such as: SIP enhancements IP Foundation enhancement including the IP/ABC trunk-group for Large Installed base protection and Multi-Time Zone for Large centralized configuration. Security with certification for vertical markets & encryption solution enhancement Health-check & real-time monitoring enhancements

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

1.2 SIP enhancementsThe Alcatel-Lucent OmniPCX Enterprise R9.0 will allow to integrate, with its SIP openness, multimedia session handling & services offer to compliant endpoints such as IP Phone, PDAs, Smart-phones, PC Soft-phone, etc In addition, devices supporting SIP could handle advanced services such as dual-mode mobility solution, presence, IM, collaboration, Moreover, to be in line with large customer market and centralization trend, it is necessary to increase the OXE Product Limit regarding the number of third party SIP endpoints. With the OmniPCX Enterprise R9, we can now support up to 5000 SIP endpoints (instead of 1000).


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.1 NOE/SIP Dual stack for IP TouchDual stack has been implemented in IP Touch EE to provide a low-cost survivability solution for very small branch offices (without local Media Gateway). Therefore, this solution ensures 100% of availability of our devices for an effective cost (no additional HW) by avoiding to duplicate the whole voice infrastructure (Key System or Media Gateway). Survivability mode is offered by the phone (using its functional mode) and a local SIP Proxy / Gateway (embedded or not in the Branch office router). In nominal mode, IP Touch is handled by the Com Server via the Alcatel-Lucent protocol. When the IP network between both IP Touch and Com Server is out of service (or Com Server unreachable), the IP Touch switches on the SIP Stack.

1.2.2 Telephony service level enhancement for 3rd party SIP endpointsThe 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)

1.2.3 SIP & strategic partners1.2.3.1 SIP endpointsAs far as telephony services are concerned, SIP has still to mature. However, IP-PBX vendors are under pressure from the market to test and recommend a number of SIP endpoints that are interoperable with their IP-PBX range. Alcatel has decided to partner with Thomson, Teledex (hospitality leadership) to certify a first batch of interoperable low end SIP hard-phones, and to give a first level of support to customers when these products are installed. Same approach has to be adopted for a SIP wifi low-cost set, a PTI SIP Wifi set (Ascom) and dual GSM-Wifi sets. It is important to remember that these sets are not part of the official IP Touch Range, nor are they provided as OEM sets. Sourcing of sets is done directly through the vendors / Application Partners. Consequently, Alcatel-Lucents technical support is limited to the issues regarding SIPPage 5 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

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.

1.2.4 SIP Device ManagementThe Device Management Software module provides a Graphical User Interface for devices firmware and device parameters configuration.

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

All Rights Reserved Alcatel-Lucent 2006, #####


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.

1.2.5 SIP Trunks optimization1.2.5.1 Feature descriptionFrom Release R9.0, the maximum number of simultaneous communications is SIP trunk group type dependant : - in a MINI_SIP trunk group : 64 simultaneous communications (4 trunks equipment per access) ; - in an usual SIP trunk group : 992 simultaneous communications (16 accesses per SIP trunk with 62 trunks per access). Benefits : Improve the scalability and the manageability of OmniPCX Enterprise.

1.2.6 SIP Proxy enhancement when Com Server switchoverPreviously, in case of switchover from CS main to standby, all SIP communications were lost (signalling and media). This SIP Proxy enhancement allows to keep SIP communications active in case of switchover to standby Com Server. The service is available with IP role addressing and spatial redundancy of Communication Servers. This feature is available for all SIP communications, either with SIP endpoints or SIP trunks. Benefits : Avoid to loose all SIP communications (with SIP endpoints and SIP trunks) in case of switchover. Constraints/ impacts with spatial redundancy: With spatial redundancy, where both CS are in different IP sub-networks, SIP communications may be lost depending on behaviour of the connected SIP Proxy: SIP proxy should accept outgoing calls (from OXE) from both IP addresses (main and standby) and send incoming calls ( to OXE) on the active server but should not cancel established sessions in case of switchover. SIP endpoints have to be able to address both IP addresses of the primary and secondary Com Servers.Page 7 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

1.2.7 DNS SRV (client) on OXEOXE was supporting DNS A mechanism, which allows to resolve a name into an IP@, for OXE to reach a remote SIP domain or an outbond proxy, to avoid configuring an IP @in OXE data base DNS SRV is now supported which allows to resolve 2 or more SIP proxies when resolving a domain name and choose the right one according to priority or weight parameters. The name of each SIP proxy is then resolved using DNS A. It allows also to failover to another proxy in the list in case of no answer from selected DNS SRV resolves names for the next hop (the outbound proxy or, if not configured, the SIP remote domain). So the DNS server (and its backup DNS server) is the enterprise one. OXE will not access to public (managed by carrier) DNS server. There is a also a caching mechanism to avoid making a DNS query for each SIP dialog/transaction DNS SRV can be used for public SIP trunking but also private SIP trunking, for instance if SIP trunking is used between several OXEs. Benefits: - Simplifies configuration : IP @/port of SIP server can be changed or new SIP server can be added without changing configuration in IPPBX. - Availability: manages distribution of calls on several SIP servers or SBCs failover. Previously on OXE, ARS was used to failover to a second proxy. Limits: DNS NAPTR is not supported (RFC 3403 - Dynamic Delegation Discovery System (DDDS) Part Three: The Domain Name System (DNS) Database). DNS NAPTR allows for instance to discover the type of protocol of a server (TCP, UDP, TLS). DNS SRV relies third parties servers to establish calls. This may result in lack of service or delays for establishing calls if main and secondary DNS servers are not reachable from OXE server. Load-balancing is not supported through DNS SRV. Standards: RFC 2782: A DNS RR (Resource Record) for specifying the location of services (DNS SRV) RFC 3263: Locating SIP Servers (except NAPTR)

1.2.8 Session timer using update methodSession timer is defined by RFC 4028. OXE was supporting in previous releases session timer using re-invite method. In R9, OXE supports also update method . Support of update method (instead of re-invite) is configurable


1.3 Session Boarder ControllerComverse Neogate Session Border Controller has been introduced in Alcatel-Lucent catalogue further to a reseller agreement. For more information, refer to Comverse/ Alcatel-Lucent NeoGate product description. In today's IP Telephony deployments , VoIP is used inside the private IP network of an enterprise. To communicate with the external world , TDM interfaces are used. VoIP will have to cross the IP borders of the enterprise, to bridge VoIP islands and because TDM will get less and less prevalent. SIP trunking, Remote SIP worker , Hosted OXE are among the services that require that VoIP crosses the IP border of the enterprise. From a data point of view, Firewalls are used today to control the data going to or coming from external networks. Nevertheless, managing VoIP traversal poses a number of challenges that are solved by SBC functions. These challenges are solved at the applicative level : the SBC is active (session aware Bach to Back User Agent, can change the session parameters) on the SIP session between the enterprise and the external world. SBC functions allow to solve following issues Connectivity Interoperability QoS Security

Compa ny

DMZ

Un- trusted a rea s

Com Server Security Border Element

Mobility Server

Internet / IPVPN Home or hotspot WLAN


1.3.1 ConnectivitySupports 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 InteroperabilityVoIP 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.

1.3.4 Quality of service: SLA enforcement and control.In addition, a SBC controls access of media packets to the network to provide differentiated services and QoS for different media streams : It provides Call Admission Control.. Call admission control can be used to guarantee and police Service Level Agreements, and to ensure that subscribers keep their call setup rates within limits that the backbone can handle. It can manage a Quality of Service, reserving network resources to handle calls being set up, and ensuring there is always enough bandwidth to handle emergency services calls. It can prevent unauthorized media from gaining access to the network, and performs per-call traffic conditioning and policing to ensure that the resources consumed by any particular callPage 10 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

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

1.3.5 Use cases in OXE environmentSession Border Controllers can be deployed in any of the following network scenarios: Public SIP Trunking Tele-workers Hosted PBX services

1.3.5.1 SIP trunking :TDM (T2, T0, analog) is the prevalent way to connect enterprises to carriers. This is changing, as native SIP offers are emerging in the carrier space, with the emergence of NGN and IMS networks. OXE connects to NGN/IMS networks through its SIP public trunk directly. In some cases, an Enterprise SBC is required between OXE and the NGN/IMS network. NeoGate solves SIP trunking connectivity issue by providing NAT traversal between the companys LAN/WAN and the operators network, as well as security, QoS management, bandwidth management, routing functions and SIP communication protocol interoperability.

1.3.5.2 Remote worker/mobile worker/remote office:Employees are more and more working from outside the enterprise geographical borders. They want to have the same services as if they were sitting at their desk. For the enterprise itself, cost must be contained and using the Internet as a connection between the employee and the enterprise is very cost effective. NeoGate solves remote SIP device connectivity through the Internet issue by providing Hosted NAT traversal for SIP protocol, as well as strong security, QoS, bandwidth management, routing functions and SIP communication protocol interoperability.

1.3.5.3 Hosted OmniPCX Enterprise ALU Business Partners and Large Enterprises aim at being the service provider for a number of enterprises or affiliates. The requirement is to be able to provide IP communications between the enterprises and the public network through Enterprise Service Provider systems (hosted OXE), without requiring any change in the IP infrastructure at customer site (no IP routing between enterprises ; overlap IP addressing plans). Neogate solves the issue of allowing communications between different IP networks byPage 11 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

providing NAT traversal, for Alcatel-Lucent proprietary protocols, as well as security, QoS, bandwidth management, routing functions

1.4 Security 1.4.1 GD signalling encryptionIntroduction In order to provide secure the communications for small remote branch offices, at a better cost the Alcatel-Lucent OmniPCX Enterprise R9.0 will provide a MGSec service in the GD board . This MGSec service is not aimed at replacing the hard MSM but is a complement to address a part of the market that is not addressable with hardware security module : the MGSec service is used to protect the IP signalling link (IP Link) between the OXE (through the SSM) and the IPMG with authentication and integrity to protect the availability of IPMG against MIM attacks. Additionally, the IP link is also be encrypted to protect against sniffing. The MGSec will not provide encryption of voice through SRTPOXE will consider an IPMG with soft SSM has unencrypted in order not to have SRTP between an IP phone and IPMG MGsec will be available on Common hardware only, and for small capacity only. Not on crystal hardware. MGsec can only be used on a secured system ( with SSM modules) The Firewalling capabilities of hard SSM are not supported on MGSec (blocking or opening IP addresses and ports). The MGSec has the same initialization process has the hard MSM, for instance will be able to be deactivated according to the security line in the LANPBX.cfg file. The MGSec service will use SHA-1 as an integrity method with SSM (Hard MSM may also use AES XCBC). On a site equipped with MGSec, IP Touch phones failover to PCS (without hard MSM) will deactivate security: no encryption of signalling between IP Touch and PCS. Limits Max number of analogical equipments (fax, phone) = 50 20 VoIP channels 300 BHCC (beware on CC agents)

1.4.2 Secured telnet access of Gateway BoardTo improve the Media Gateway hardening, it is possible to configure the telnet service on GDPage 12 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

board by: Closing telnet access and remove telnet client to GD Configuration on demand from the Com Server

1.4.3 802.1X TLS1.4.3.1 Feature descriptionThe latest version R9.0 of the OmniPCX Enterprise includes an enhancement to the IEEE 802.1X authentication capabilities by adding X.509 v3 digital certificate support. IEEE 802.1X provides a standardized authentication methodology for all 802-type networks, including Local Area Networks (LANs) and Wireless Local Area Networks (WLANs), providing a significant benefit for users, enterprise network managers, and service providers. Users can focus on a single authentication interface, which would allow them to roam among network access services re-authenticating as required. The OmniPCX Enteprise was the first VoIP product on the market (in 2006) to provide support for 802.1X authentication, providing support for the IP Touch series (EAP-MD5 and EAP-TLS) and allowing a better integration of the VoIP solution inside a secure LAN. The newly supported digital certificate capability provides an additional security layer and enables the OmniPCX solution to play into a corporates overall plans around common authentication management."

1.5 IP Foundation enhancements 1.5.1 IP ABC Trunk GroupBefore the Alcatel-Lucent OmniPCX Enterprise R9.0, different ABC sub-networks could only be interconnected by using: classical TDM links at physical level, and ABC-F trunk groups at application level, IP links with a SIP level of services

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, )

1.5.2 Calling Line Identity per IP domain.For OXE users making a public outgoing call, OXE will send in general the user CLI. In case of emergency call, the network has to identify the geolocation of the calling party. This is done in general by identifying the trunk group where the call is originated. ARS per entity or per IP domain on OXE allows to select the right trunk. But more and more, public trunks are centralized in multi-site IP telephony networks. The network can no more use the trunk group to identify calling party. CLI can be used by the network to identify the location. An emergency server must be installed by the carrier that maps enterprise CLI to locations and to emergency centres that serve these locations. User CLI does not take into account user and device mobility between several locations, and even for fixed phones requires to manage all the user CLI per entity is already available. It allows to send a number associated to an entity, which represents a location. But as entity is linked to a user and not a device, CLI per entity can not be used for mobile devices that are roaming between several locations. CLI per IP domain allows this in R9 Following diagram shows an example of a 2 sites network using a centralized trunk group. Different CLI are sent when dialling 112 number, depending on location of caller.


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


A new parameter is included in IP domain data: calling number CLI per IP domain is not applicable to internal calls .

1.5.3 Fax T38 for internal callsOXE supports 2 types of fax over IP protocols Fax relay for local and ABC calls (internal calls) T38 for calls on IP trunks (SIP or H323) (external 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.

1.5.4 VoIP tickets in real time & Health-CheckDue to IP convergence, the OmniPCX Enterprise is more and more often integrated in IT / data environment. Therefore, the OmniPCX Enterprise has to be able to give some information to Alcatel-Lucent monitoring tools (VitalSuite) or third party monitoring tools (HPoV, Micromuse, Tivoli Netview, Concord, BMC Visualis, BMC Patrol, Spectrum, EMC2 Smarts, CA Unicenter, NetIQ, Service Pilot, Thomas, InfoVista, ). These tools are mandatory for Large Enterprises (own needs), Carriers, Service Providers and integrators to perform SLM, global performance monitoring, capacity planning and troubleshooting. Applicative health-check :Page 16 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

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.

1.6 Multi-Time Zone per Com ServerAlcatel-Lucent OmniPCX Enterprise R9.0 will provide Multi Time Zone (MTZ) featuring, responding to centralization of more or less large configuration requests . Hour information is updated by ISDN or NTP and changes automatically with Daylight Saving Times. It is displayed on mobile (MIPT, DECT) or fixed digital sets (8 and 9Series) (whether IP or TDM), IP Desktop Softphone, Class (S0) sets and attendant sets (4059). Therefore, the notion of time zone (# 85) has to be associated to IP domains notion of the Communication Server. Thus, the Communication Server will be able to : display the local date & time on the sets with multi-country format (D/M/Y or M/D/Y) update time of wake-up & appointment reminder (except wakeup setup by attendant) update time of non answered calls take into account the time update by Isdn and private link generate local hour in the accounting ticket (4760 impact): OXE calculates in the accounting ticket the offset between the time of the CS and the local time of the trunk used for the communication to allow the 4760 to calculate the right billing. This offset is in an additional field in the CDR (only fill in for external calls). update voice mail deposit time (external voice mail only)Page 17 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

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.

1.7 Miscellaneous 1.7.1 Attendant display enhancementFeature : called number display when the attendant makes an outgoing call. Use case description: An Attendant makes an external outgoing call. The called number is displayed on the attendant screen during ringing state. When the called user picks up the phone, the called number on the display of the attendant is replaced by the trunk group name. For example, the attendant prepares a number of other calls on request . So, all the outgoing calls are put on hold (via individual hold keys) by the attendant and due to the wrong display, the attendant is no longer able to retrieve/identify the called number.Page 18 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

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.

1.7.2 Attendant Application 4059The Alcatel-Lucent A4059 IP Attendant Console is a state-of-the-art attendant application that offers advanced telephony services on desktop PC. From OmniPCX Enterprise R9, this application is also a Windows Vista-based application.

1.7.3 IP Desktop SoftphoneNew skin for Phone Emulation Plug-in It has been designed for MOC MSFT GUI compatibility. Thanks to this skin, the user can have access, on the same desktop, to MSFT applications (IM, collaboration) and OmniPCX Enterprsie Voice over IP services. This kind of configuration requires some specific software components. For additional information, refer to OCS Microsoft integration documentation. Security IP Desktop Softphone is compatible with IP Touch Security solution to protect the IP signaling link between the OXE (through the SSM) and the Softphone with authentication and integrity. Additionally, the IP link and voice flows (SRTP) will also be encrypted to protect against sniffing. OS compatibility From OmniPCX Enterprise R9, this application is a Windows Vista-based application. Restriction: IP Touch Security solution cannot be deployed on Vista OS. Therefore, communications with this Softphone will not be encrypted.

1.7.4 Free Desktop enhancementInfrastructure In release 3.0 and upper, the Free Desktop Server application can be installed on the same physical server as UC XML Framework or OmniTouch Unified Communication server. Thanks to this cohabitation, Free Desktop application of OmniTouch Framework mechanism, providing High Availability services. Limit: this all-in-one server solution is available only with XML API Framework or OTUC serverPage 19 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

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 codeFor 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.

1.7.6 Valenciano language supportAdd a new language Valenciano in OXE. Valanciano language concerns the management strings(mgr), system strings, voice guide translation and Attendant 4059 strings.

1.7.7 Number of calls on DPNSS & DASS2 linkThe limit of calls for DNPSS+DASS2 access is linked to the number of declared DPNSS & DASS2 boards (same configuration as ISDN trunks). Previously, the number of DPNSS+DASS2 calls was set to 250.Page 20 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

1.7.8 Increasing the amount of domain of managementLarge companies with several network managers, multi-company, or organizations with security/confidentiality policy use configuration by domain. This feature provides specific access rights on a domain to each manager. On each domain, a given manager can have for each object, instance, or attribute: No access Read only Read/Modify Read/Modify/Create/Delete

Up to 128 (instead of 32) domains can be created within a sub-network.

1.7.9 Networking compatibilityIn a networking configuration, the release 9.0 of Alcatel OmniPCX Enterprise must be fully compatible with following systems releases : Alcatel OmniPCX Enterprise R7.1 Alcatel OmniPCX Enterprise R8.0.1 To facilitate release migration of Communication Servers within an ABC sub-network, several releases (from R6.1.1) have to be temporary compatible inside this sub-network.


2 Genesys Entreprise Telephony Server (GETS)2.1 GETS for Microsoft Office CommunicatorThe GETS (Genesys Enterprise Telephony Software) platform provides telephony services, such as call transfer, click to call, forwarding, caller ID, do not disturb, missed call notification, telephony presence and many more to all Microsoft Office Communicator and Microsoft Office users. This solution, based on the proven and market-leading Genesys CTI platform, integrates the complete and reliable Alcatel-Lucent OmniPCX Enterprise enterprise communication features within the Microsoft Office Communicator desktop. GETS is high scalable and compatible with OXE and OXO, as well as with 8 other vendors PBXs. GETS is configurable and orderable through ACTIS and the voice catalogue. For OXE connectivity, bundles including GETS and CSTA licenses are available.

M icro so ftor

MOC OCSM 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

T h ird -p a rty PBXs


3 Mobility Solutions3.1 Remote extension: activation / de-activationThe 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.

3.2 WLAN: MIPT compatibility with Passive Com ServerFrom Release 9.0, MIPT is compatible with Passive Com Server feature. Thanks to a backup IP address, the mobile Phone is able to exchange the telephony signalling with the Passive Com Server when the main and secondary Com Servers are no longer reachable. IP address is downloaded during initialisation step of the phone. Restriction: local DHCP is mandatory to allocate the IP addresses of the set. With Release 9.0.1, the IP addresses will be stored in the phone set. So, local DHCP server will not be longer necessary.Page 23 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

4 Infrastructure / Hardware evolution & obsolescence4.1 Hardware evolution / cost reduction & obsolescence managementSince 2006 Alcatel-Lucent is rationalizing and simplifying OmniPCX Enterprise Offer. Alcatel-Lucent constantly works on evolution of hardware items based on features obsolescence, new technology anticipation, cost issues and Electrical Manufacturer Suppliers ability to support Alcatel-Lucent OmniPCX Enterprise materials and low components volume. Within the OmniPCX Enterprise 2008 offer, due to be released in November 2008, the hardware phase out highlight are: OmniPCX Enterprise Crystal CPU boards (CPU6 & CPU7 board) - End of Life Analog tie line access board (ACEM board) - End of Life Crystal Remote Media Gateway connection through leased T2 link (RT2-1 board) - End of Life For smooth transition, there is no hardware dismantling in any releases upgrade. Alcatel-Lucent advices Business Partner to evaluate and order the products listed hereafter before fourth quarter 2008.

ItemCPU6 board OBCA2 card CPU7 board

EoL2008 2008 2008

SubstituteCrystal 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


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:

End of Life date & End of Shipment. Alternative solution

4.2 Introducing the PowerDsine 7024GThe PowerDsine 7024G completes the Power-over-Ethernet Midspan range to offer High-Power and Gigabit support in a single unit up to 24 ports. A PoE Midspan (PoE injector) resides between the Ethernet switch and the data terminals, delivering data, along with power, from switch to powered devices. The Gigabit interface makes the PD-7024G/AC the perfect solution for the recent IP Touch Extended Edition range. Values & Benefits: High Power over 2-pairs only - 32W per port. Perfect fit for most 802.11n Access Points, WiMAX CPEs, Video Phones Access control units, Point-of-Sale terminals and more 10/10/1000BaseT Support (Gig) A cost-effective solution to upgrade existing infrastructures to PoE Safe & reliable power over existing Ethernet infrastructure Safe solution that protects network infrastructure investments - buy your power once, don't buy again when replacing the switch. 802.3af Compliant with higher power

5 Launching strategy5.1 Country availabilityAlcatel-Lucent OmniPCX Enterprise R9.0 will be available worldwide. Possible restriction on component offer availability due to local approval issues are mentioned inPage 25 OmniPCX Enterprise Communications Server R9.0 Release note 8AL020043xxxDRASA ed 0 All Rights Reserved Alcatel-Lucent 2008

the country list

5.2 PlanningStep 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


www.alcatel-lucent.com


omniPCX R9 MOCS

Documents

Transcript of omniPCX R9 MOCS