OXE R11-1 Overview ed5 1 Central Pre-Sales · • OV 8770 2.6 is available from April 2015. " OmniVista 4760 is no more supported for OXE R11.1 • existing 4760 (upgrade or migration)

1 OXE_R11-1_Overview_ed5 Central Pre-Sales

COPYRIGHT © 2015 ALE International. ALL RIGHTS RESERVED.

v



OMNIPCX ENTERPRISE R11.1 OVERVIEW

With speaker notes Narasimha Murthy Central Presales



PREAMBLE

The objective of this pre-sales presentation is to describe the news features and solutions brought by the release 11.1 of the OmniPCX Enterprise including MD1 (January 2015) and MD2 (May 2015) maintenance deliveries.



AGENDA

1.  General information

2.  OXE MS enhancements

3.  Call Handling (including Rapid Call Shift and NFC Extended Mobility)

4.  Redundant Ethernet for Gateway boards

5.  SIP trunking evolution

6.  Obsolescence management

7.  IPv6

8.  4645 enhancements

9.  8001 « business » and 8088 « Hospitality » SIP Desk Phones

10. IP Touch Security with OTMS



AGENDA







7.  IPv6






GENERAL INFORMATION

OXE R11.1 is part of OpenTouch Suite for MLE November 2014 Offer

q  Availability: 3rd of November 2014

q  OXE R11.1 is a minor release

q  OXE R11.1 is not integrated in OTBE R2.0.x (it is OXE R11.0.1)

q  OXE R11.1 is compatible with OTMS R2.0.x and R2.1

q  OXE R11.1 will be integrated in OTBE R2.1

q  OXE R11.1 can be managed with

§  OmniVista 8770 >= 2.5. •  OV 8770 2.6 is available from April 2015.

§  OmniVista 4760 is no more supported for OXE R11.1 •  existing 4760 (upgrade or migration) must be migrated to 8770

q  ACTIS tool versions: 19.2.x (Nov ’14) and 19.3.x (April ’15)

•  MD1 January ’15 •  MD2 May ’15 •  MD3 August ’15

OT Suite for MLE •  OXE R11.1 •  OTMS R2.0.2 •  OTMC R2.0.2 •  OV 8770 R2.5 •  …

OmniVista 4760



GENERAL INFORMATION RELEASES IN ABC SUB-NETWORK

q  OXE R11.1 can interwork with R10.0, R10.1, R10.1.1, R11.0, R11.0.1 and can be front-end node for OTMS R2.0.x and R2.1 §  The Cross Compatibility and Technical Support Installation Procedures available on the ALE Business

Portal provide detailed information about specific constraints when upgrading OXE versions in an ABC network (direct RTP, progressive migrations, old VoIP boards replacement…)

OXE R10.0 OXE R9.1

OXE R10.1.1

OXE R10.1

ABC sub-network OTMS R2.0.x / R2.1

OXE R11.0.1

For OTBE/OTMS the “front-end” OXE CS has to be deployed with a compatible version Compatibility table:

« front-end » OXE CS version OTMS version

For multi-OT in OXE network see rules in Speaker Notes

OXE R11.0



GENERAL INFORMATION

q  Product Limit enhancements

§  Up to 5000 DECT handsets on IP DECT infrastructure instead of 1500

•  5000 is a global limit for IP DECT and/or TDM DECT infrastructure(s)

§  Up to 5000 mailboxes on 4645 VM for hospitality (OXE R11.1 MD1)

§  Up to 2000 Hunting Groups (instead of 500) (OXE R11.1 MD1)

§  OTCC SE R10.2 new limits

•  Number of routing pilots is increased from 200 to 600 •  Number of Pilot Routing Directions is increased from 20 to 30 •  Number of Queues is increased from 200 to 600 •  Number of Queue distribution directions is increased from 30 to 50 •  Number of processing groups is increased from 150 to 450 •  Number of Calendar per pilot is increased from 6 to 10 •  The number of Expected Waiting Time (announcements) is increased from 200 to 600



GENERAL INFORMATION

q  Virtualization news

§ Extended virtualization platform ecosystem •  Support of Vmware ESXi / vSphere v5.5 •  Red Hat KVM ® (OXE R11.1 MD1)

-  OpenSource support for OXE-V (CS), A4645-V and OXE MS

§ A4645-V is taken into account in Actis 19.2.x

§ PCS-V is taken into account in Actis 19.3.x



AGENDA



3.  Call Handling (including Rapid Call Shift and NFC Extended Mobility) 4.  Redundant Ethernet for Gateway boards



7.  IPv6



10.  IP Touch Security with OTMS



OXE MS ENHANCEMENTS q  Evolution with R11.0.1 (reminder) §  VoIP/QoS ticket support §  Multi-instance (up to 4 OXE MS per physical core) §  120 simultaneous Voice Guides per OXE MS (instead of 16 in R11.0) § Download dynamic Voice Guide

•  Up to one hour per OXE MS

§ H323 trunks for ABC networking (up to 30 network trunks)

q  Evolution with R11.1 § G722 codec support for conferencing (3-party and N party) (see Speaker Notes)

•  4028/38/68 EE, 8028/38/68 sets and SIP trunks can be connected with G722 to a conference managed by the OXE MS •  An OXE MS conference can have participants connected with G729, G711 and G722

§  N party conference support •  To complete 3 party and casual conferences (6 party) already existing in R11.0.1 •  Meet-me and mastered conferences (14 and 29) •  Up to 29 participants per conference / Up to 90 participants per OXE MS

§ H323 trunks for ABC networking product limit •  Up to 60 network trunks (instead of 30)

from patch K1.520.29

(June 2014)



AGENDA







7.  IPv6






ROBERT

CALL HANDLING RAPID CALL SHIFT (CALL CONTINUITY) § To move an active communication (in the conversation state) from one set to

the other in a TwinSet (e.g. a Desk Phone associated with a DECT or GSM (REX) handset) § From the set which is in the idle state, the user dials a new prefix (Twinset Get Call) to move the call (instead of using enquiry + transfer features)

§ The remote party does not experience any change during the move, neither on audio (only a small noise or blank may occur) nor on display

§ The communication duration is restarted on the set that picks up the call. § A new accounting ticket is created.

BOB

OXE twinset

2 Robert dials the TGC prefix (or press a key containing this prefix)

1 conversation

3 conversation (internal or external)

2

3

1

Rapid Call Shift example. The reverse case (desk set to mobile set) is also possible.



CALL HANDLING RAPID CALL SHIFT (CONT’D) § Set from which the prefix is dialed must be in idle state or in ringing state § On the twinset’s set which was initially in the conversation state “Call is picked up” is

displayed when move is OK (except if REX) before inviting this one to go on hook (tone) § Once moved, the call can be moved again to the other twinset set § This feature can be enabled/disabled in Phone Features CoS (default value is Yes)

§ Twinset configuration •  Main set can be any 40x8, 40x9, 80x8, 80x9 series, IPDSP, 8082 OT Connection and SIP integrated

(Seplos) including OT Connection PC. •  Secondary set can be any 40x8, 40x9, 80x8, 80x9 series, IPDSP, 8082 OT Connection, SIP integrated

(Seplos) including OT Connection PC, DECT 300/400/500, 8232/42, VoWLAN OT81x8, Remote Extension •  There is no restriction on set feature configuration (e.g. boss/secretary) •  The 2 twinset sets must be on the same node (twinset restriction)



CALL HANDLING RAPID CALL SHIFT (CONT’D) § Call pick-up from a Remote Extension

•  A REX can either -  dial a DID number translated by the OXE in the “Twinset Get Call” prefix

-  in this case, the automatic authentication on ISDN CLI must be managed in the system, as for DISA -  or dial first the DID number corresponding to the DISA prefix (with or without authentication),

then dial the “Twinset Get Call” prefix •  After having picked-up the call, the REX gets the DISA functionalities for REX

-  Reminder: DISA functionalities accessible for REX via suffixes sent in DTMF are: -  Enquiry, Broker, 3-Party Conference, Transfer, Programmable Keys activation (up to 10)

§  Restrictions •  The remote party cannot be an Attendant or a Voice Mail (the feature is “unavailable”) •  DECT in OXE roaming (from one node to an other node) cannot access the feature



ROBERT

CALL HANDLING NFC EXTENDED OXE MOBILITY § Rapid Call Shift triggered by approaching the 2 devices

•  without pressing a key or dialing the TGC prefix

•  Performed thanks to the NFC technology (Near Field Communication) •  Authorized sets and clients (exhaustive list)

-  Android cellular phone (>= 4.2) equipped with an NFC interface, using either the IPDSP or the native telephone application in REX mode, and the dedicated ALE user application

-  40x8, 40x9, 80x8, 80x9 series, 8082 OT Connection desk set equipped with an ALE NFC tag

BOB

OXE twinset

2

Robert approaches his Smartphone of his Desk

Phone

1 conversation

3 conversation (internal or external)

NFC Extented OXE Mobility example. The reverse case (desk set to mobile set) also works.



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § Immediate Forward to a “self service” desk phone triggered by approaching

the 2 devices •  to forward calls to any extension equipped with a NFC tag (typically to a “self

service” desk phone installed in a transit office or meeting room) by approaching the Android Smartphone to the destination phone

•  to cancel call forwarding to any extension equipped with a NFC tag (typically to a “self service” desk phone installed in a transit office or meeting room) by approaching the Android Smartphone -  of the destination phone -  or of its Twinset’s primary desk phone or from the Smartphone application

•  Twinset configuration is not mandatory for forward functions

BOB

Bob approaches his Smartphone of his Desk Phone to program or to cancel Call Forwarding

to a “self service” phone



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § NFC Extended OXE Mobility application

•  Google Play ALE application •  developed for Google Android environment (R 4.2 to R5.1) •  It allows the user to:

-  Shift a call in a twinset (from his mobile to his desk set or from his desk set to his mobile) -  Forward (Immediat) calls to any other set on the network equipped with a NFC tag -  Cancel a forward established on another set equipped with a NFC tag

•  « Forward only » mode is possible (e.g. for users who do not use twinset) •  This application is compatible with

-  An Android Smartphone declared as an OXE Remote Extension (REX) and using its native telephone application

-  An ALE IP Desktop SoftPhone (IPDSP) on Android Smartphone

•  This application is not compatible with any OTC client including the OTC client for Connection user (OTC Ct for Smartphone) on an Android Smartphone



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § Call flows

•  The application reads the content of the NFC tag -  Extension number of the desk set on which the tag is stuck -  Role main addresses of its main and stand-by call server(s) -  Port number of the CSTA server

•  The application select the operation to be done through CSTA -  This connection is done through IP network, using Wi-Fi network (or

mobile data through VPN*). -  This CSTA connection is needed to monitor the desk phone and the

mobile device itself. -  Through this monitoring the application is able to select the correct

operation requested by the user (call shift or forward operations):

•  The selected operation is sent via CSTA or dialing

Android Smartphone with NFC interface and the NFC Extended

OXE Mobility application

NFC tag

1

1

2

3

Wi-Fi (or VPN*)

CSTA

2

REX or IPDSP

Twinset Desk

Phone

CSTA server

OXE CS

(*): CSTA connection via VPN is not convenient and therefore not recommended. Data GSM access via Reverse Proxy is technically possible but not validated.

3PSTN or

SIP Carrier

GSM network

3

Mobile set \ Desk set busy idle

busy

idle

Desk phone equipped with a programmed

NFC tag



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § Android Smartphone Graphical User Interface

Call Shift to an Android Smartphone declared as a REX: DISA number dialing

Call Shift to an Android Smartphone declared as a REX in Call Back mode

Android notification of the desktop set forward

application GUI for desktop set forward

cancellation



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § Android Smartphone Graphical User Interface (cont’d)

Message to confirm Desktop set forward programming

Message to confirm Desktop set forward cancellation



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § Mobile application configuration

Automatically launched when starting manually the application

In R11.2 it will be possible to hide these sensitive information. They will be transmitted “hidden” in a picture. See Speaker Notes for more details.

The OXE number (REX or IPDSP)

-  REX -  REX Extension in Call Back mode -  or IPDSP

The OXE number of the desk set

Default value: 3000 ms

Deactivated if the selected mobile mode is not « REX »

Specific screens are opened for parameters input

To record information on the tag of his/her primary set



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § “Call Forward Only“ mode

•  The application can be deployed on site to offer only the Forwarding Call and Forwarding Call Cancellation, without the Rapid Call Shift feature. -  In this case the application configuration is simplified

-  useless fields are greyed

•  The application configured in “full feature“ mode also works in “Call Forward Only“ mode if -  The « Local number of softphone / remote extension » is not configured -  the mobile phone is declared as an IPDSP, but the IPDSP is not running on the mobile



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § Deployment - Record NFC tag of desktop phone

•  To simplify deployment on site, this application offers the ability to record NFC tag information of the primary set of the user twinset from the NFC Extended Mobility application

•  Once parameters have been set, the Record NFC tag of desktop phone option becomes available

If the user clicks on this option

a new screen appears, asking to approach the mobile to an empty tag.

When the NFC tag is recorded the user is notified.



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § Deployment – “ALE NFC Extended OXE Mobility Administration” app.

•  This application is called ”ALE NFC Extended OXE Mobility Adm” in Google play •  This application complements the ”NFC Extended OXE Mobility” application •  This application allows the site administrator to record NFC tags for any set on the network •  Two functions are offered

-  Write a NFC tag with the required format -  Check a NFC tag format and content



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § Deployment – “ALE NFC Extended OXE Mobility Administration” app. (cont’d)

•  Write NFC tag operations



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § Deployment - ALE NFC Extended OXE Mobility Administration (cont’d)

•  Managing node profile



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § Deployment - ALE NFC Extended OXE Mobility Administration (cont’d)

•  Reading NFC tag content



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § How To Quote •  In Actis

-  CSTA licenses (assumptions: 2 licenses per shift during 1 second, one shift per user per hour, loss rate: 0.1 %) -  For 1 to 400 users with NFC Extended Mobility: 2 CSTA licenses

-  For 500 to 800 users: 4 CSTA licenses





-  Remote Extension licenses (if it is the chosen option and not already existing) or

-  IP Desktop Softphone licenses (if it is the chosen option and not already existing)

•  In eBuy -  NFC tags by bunch of 100. Cannot be ordered in Actis.

3BA27856AA NFC TAG STICKERS (x100)



CALL HANDLING NFC EXTENDED OXE MOBILITY (CONT’D) § Availability

•  April 2015 MLE Offer

§ Links to get the applications on Google play •  https://play.google.com/store/apps/details?id=com.alu.OXE.NFCExtendedMobility&hl=fr •  https://play.google.com/store/apps/details?id=com.alu.OXE.NFCExtendedMobilityAdmin&hl=fr

§ Related documents •  OXE R11.1 System Documentation

-  NFC Extended OXE Mobility -  ALE NFC Extended OXE Mobility Administration



CALL HANDLING

q  PER 2626: build the right CLI (calling number) including the right first digits corresponding to the used outgoing trunk group in case of external call forwarding and when the caller is on another node than the forwarded set §  It was working in stand-alone. OK in ABC network from OXE R11.1

q  PER 2668: display simultaneously calling/called number and trunk group name on phone set incoming and outgoing calls in ringing and conversation state

§  For 4038/39/68, 8038/39/68 and 8082 OT Connection §  Behavior before R11.1: see Speaker Notes §  new system option “Display trunk group name” (to be able to keep the existing behavior) § New behavior: if the name is not received and no name is associated to the external number

(programmable key or abbreviated number) and if there is no Secret Identity (for incoming calls), the number and the trunk group name can be displayed on the set



CALL HANDLING

q  PER 2700: auto-deletion of call logs § This feature allows deleting the record of call log, non-answered call and mini-messages

automatically after a particular period of time. § This feature is due to the new German privacy law (law for Data Protection and Freedom of

Information) which forbids storage of telephone numbers for more than 90 days. This feature considers only the time stamped data. It means redial list which is not time stamped could be stored for more than 90 days.

§ This feature applies to 4028, 4029, 4038, 4039, 4068, 8028, 8039, 8068, 8082 OT Connection, IPDSP and DECT AGAP devices (300/400, 8232 and 8242).

§  Before this feature: •  information of call log, non-answered calls and mini messages are stored till it reaches the maximum

number of records mentioned in system parameters. If reaches the maximum number of records is reached, the oldest records with latest records are overwritten.

•  The user can delete the record manually by using the “delete” Soft Key.

§ Limitation: •  Multi time zone feature is not considered



CALL HANDLING q  PER 2735: restricted direct call to attendant § Customer request:

•  To forbid direct call to attendant because too many people only call for information while the attendant should be called for call transfer.

§ Solution with OXE R11.1: •  New flag in Phone Features CoS: “No direct call to attendant”; default = No. •  The concerned prefixes are:

-  Attendant call -  Individual attendant call -  Attendant group call

§ Restriction •  Every set types except SIP devices (= SIP registered) so not available for OT Conversation users

q  Native Call Log with CPU7-2 (OXE R11.1 MD1)

§ 20 call logs max per user

q  Miscellaneous PERs: see Speaker notes



CALL HANDLING

q  Contact Center

§ PER 2633 (OXE R11.1 MD1) •  call rotation when agent not answering during an enquiry call to a pilot

-  to serve a pilot called in enquiry mode with supervised transfer enabled (see Speaker Notes).

§ PER 397 (OXE R11.1 MD1)

•  Number of agent presentation messages no more limited to 1000 (see Speaker Notes)

§ PER 2632 (OXE R11.1 MD2) •  Display improvement on agent screen

-  Many information about calling, pilot, entity... Are displayed on the agent screen set, especially for the x8&x9 sets. These information are displayed on the first line, so some strings are truncated.

-  The customer requests to have non truncated calling number on the first

line, and to keep the entire calling number on the second line (for 4038/4039/4068 /8038/8039/8068 sets)



AGENDA







7.  IPv6






REDUNDANT ETHERNET FOR GATEWAY BOARDS

q  Two network interfaces providing hot-standby service (active-backup)

q  Available on INTIP-3, IOIP3, GD-3 and GA-3

§ Two network interfaces (eth0 and eth1) per board § Linux kernel includes a bonding driver which provides a method for aggregating multiple network interfaces into a single logical "bonded" interface.

§ Only one network interface (called slave) in the bond is active. The other network interface becomes active if and only if the active slave fails.

§ Compatibility status with IP Touch Security •  Redundant Ethernet on gateway boards is compatible with SoftMSM •  Redundant Ethernet on gateway boards with MSM-RM is not supported



REDUNDANT ETHERNET FOR GATEWAY BOARDS

q  Design rules §  For complete Ethernet redundancy each interface must be connected to a different switch unit. §  These units must comply with the Fast Spanning Tree protocol and be configured to allow a fast IP

frames forwarding when the port interface is up. §  Caution: LANX/S-LANX boards cannot be used in this context.

ST = Spanning Tree FST = Fast Spanning Tree (see Speaker Notes)

LAN ST ST

FST FST



AGENDA







7.  IPv6






SIP TRUNKING ENHANCEMENTS q  PER 2762 & PER 2763: Name display on ringing (for better interworking with Cisco)

§  Update the display on ringing with the PAI (P-Asserted Identity) received in the “180 Ringing” for an outgoing call on a private (ABC-F) SIP Trunk Group

§  Update the remote set display on ringing by sending a PAI in the “180 Ringing” for an incoming call on a private (ABC-F) SIP Trunk Group

q  SIP & CS-1 Passive Com Server

§  SIP deployment is not compatible with CS-1 (from R9.1) used as Com Server §  The CS-1 can used as Passive Com Server if less than 500 calls/hour (values to be confirmed)

q  SIP conformity with RFCs

§  491 Request Pending support: Used to manage the “mutual hold” issue §  Support of the SIP User to User header field : to transport the CSTA “correlator data” and “Global Call

id” between OTCS and OXE in private SIP trunking (in accordance to IETF “draft-ietf-cuss-sip-uui-isdn”)

q  PER 2858: SIP & serviceability (OXE R11.1 MD1)

§  simplification of PCS management in case of local SIP carrier connectivity •  To simplify ARS routes and SIP external gateways management in case of local SIP carrier connectivity



AGENDA







7.  IPv6






OBSOLESCENCE MANAGEMENT q  New Appliance Server IBM x3250 M5 for the OXE CS

§  to replace the IBM x3250 M4

§ Dual power supply option for M5 •  orderable in Actis (Additional Hardware) when the x3250 M4 stock will be depleted

(see Speaker Notes). Commercial reference: 3BA27598AA.

§ Compatibility from OXE R11.0.1 patch >= k1.520.32



OBSOLESCENCE MANAGEMENT q  IBM x3250 M5 BoM



OBSOLESCENCE MANAGEMENT q  Hardware obsolescence (cont’d)

§ Are phased-out and suppressed from MLE Offer November ‘14 catalogue: •  DDI4 board (ref. 3EH73036AB) Common Hardware Public analogue trunks with DDI for US market •  T1-CAS (ref. 3EH73007AE) digital access board

-  T1-CCS board remains available in the offer

•  GSCLI daughter board of the APA board (ref 3BA23196AAJA in US catalogue) -  used for the Ground Start protocol (BellCore)

•  Voice record box for 1UA set (ref. 3BD19160AF) •  8UA record interface board (ref. 3BD19218AH) •  VPU6 board

-  New A4635J Voice Mail orders no longer available from November 2014 -  Alternative solutions: 4635J migration to

-  OTMC for business solutions or -  4645 for hospitality solutions with their associated commercial programs

4635J




§ Phased-out and suppressed from MLE Offer November ‘14 catalogue: •  TNLO11 (ref. 3BA23088AB) board for one optical fiber link

-  No more used for RT2 inter-ACT links over E1 (RT2 link is phased-out) -  Still used for E1 private links (ABC-F/QSIG/DPNSS) over optical fiber, associated with NPRAE -  Alternative: TNLO21 (ref.3BA23079AB ) board for 2 optical links is kept.




§ Phased-out and suppressed from MLE Offer November ‘14 catalogue: •  Extension Battery rack 48V (ref. 3EH76187AA)

Currently : ALE offers a 500 W charger rack solution, to backup 48VDC supplied Common Hardware, cabinets. The charger rack can power up to 3 MR1–48V / MR3–48V cabinets and includes rectifier and backup batteries. According to the requested autonomy, there can be up to 8 batteries placed in the charger rack and up to 8 batteries can be add in an optional battery rack. Issue : Due to EOL announcement of the optional battery rack, ALE will no more being able to provide autonomy solution with more than 8 batteries.




§ Phased-out of Extension Battery rack 48V (cont’d)

Consequence : The cells in orange, in the autonomy table hereby, can then no more be configured. (The cells in red were already out of range).



OBSOLESCENCE MANAGEMENT Phased-out of Extension Battery rack 48V (cont’d)

Workaround solution with UPS (Ininterruptible Power Supply) and EBM (Extension Battery Module) ref. 3EH76210AA: (POWER BACK-UP 100W/1H30) and (3EH76211AA: BATTERY PACK + 100W/4H):

Advantages : Drawbacks : - Scalable with required autonomies - Cost increase for long backup of heavy configuration - Up to 8 hours can be guaranteed through UPS extensions - UPS and EBM are available in ALE catalogs and Actis (Additional Hardware) -

The back-up time is expanded by an additional UPS placed on mains side upstream of the charger rack.



OBSOLESCENCE MANAGEMENT Phased-out and of Extension Battery rack 48V (cont’d)

Workaround solution with UPS and EBM (Extension Battery Module):

This table will be provided in Actis

19.2.x. Help.



AGENDA







7.  IPv6






q  IPv6 first step of implementation with OXE R11.1 MD1

§ v4/v6 dual stack support for signaling and media flows between Com Server and: •  Common Hardware Media Gateway with GD-3, GA-3

•  8028/38/68 Premium desk phones (January 2015 –firmware R200)

§ OST64 software component for signaling

§ RTP Proxy for media flows, embedded in GD-3/GA-3

§  For a complete description please consult the presentation « CPSC021-IPv6_Solution_OXE_R11_1_MD1_ed3.pptx » available on the ALE Business Portal -> Pre-Sales Corner.

IPv6



§ OST64: new Software component to perform IPv4 & IPv6 translation for CS and PCS •  always virtualized •  on a dedicated AS or a dedicated VM (see next slide)

OXE CS

IPv4@/IPv6@

DHCP & DNS IPv4/IPv6

IPLINK

IPv6 IPv6@

OST64 NOE

v4 v6

Dual Stack Network IPv4 & IPv6

Desk phones (dual-Stack) 8028/8038/8068 (January 2015) IPv6@

Use case with Dual Stack IPv4/v6 LAN and IPv6 LAN

IPv6 Network

NOE

IPLINK

IPv4@

NOE

Common Hardware IP Media Gateway

RTP

PSTN

The image cannot be displayed. Your computer

The image cannot be displayed. Your computer may not

IPv6



q  OST64 characteristics

§ one instance of OST64 per CS or PCS (one to one) § CS duplication is possible (with 2 OST64, one per CS) § Each PCS must have a dedicated OST64 if translation to be done for the IPv6 devices in its

rescued domain •  no need of OST64 in case the domain has only pure IPv4 or mixed mode devices

§ software application running in a RedHat Linux machine § recommended to be virtualized along with OXE CS

IPv4@/IPv6@

OXE CS 1

Linux

Vmware ESX 5.1 or 5.5 VM

8770 MCS

Win

VM

OST64 1

RH Linux

VM

OXE CS n

Linux

VM

OST64 n

VM …… RH

Linux

OST64

OR

IPv6



IPv6 Network


IP LINK

IPv6

IP Touch (NOE 2G) with minimum

firmware version

IPv4@

IPv4@/IPv6@

RTP Proxy : Software component allowing media protocol translation between IPv4 & IPv6 environments

RTP

RTP

v4 v6


IPv4@/IPv6@

IPLINK

OXE CS

q  v4/v6 RTP Proxy for RTP flows

§ To interconnect a pure v4 device with a pure v6 device § Embedded in the Common Hardware Media Gateway (GD-3/GA-3)

PSTN

Common Hardware IP Media Gateway

IPv6@

NOE

OST64

IPv6

RTP Proxy use case with CH Media Gateway



RTP Proxy use case with 8028/38/68 Premium deskphone

IPv6 Network


NOE

IPv6

IPv4@

NOE IPv4@/IPv6@

RTP Proxy : Software component allowing media protocol translation between IPv4 & IPv6 environments

RTP

RTP

v4 v6


IPv6@

hardphones (dual-Stack) 8028/8038/8068

(Q1 ’15)

IPv4@/IPv6@ NOE OXE CS

IP Touch (NOE 2G) with minimum

firmware version

IPv6



q  Available Q1’15 with Premium desk phones

§ OXE R11.1 MD1 and Premium desk phones (NOE-3G) R200 TR

q  Quotation

§ Quotation is not accessible yet for Business Partners/Customers § Via Central Pre-Sales (PCS process) § No additional cost for IPv6 on OXE except:

•  An Appliance server per OST64 if OXE CS not virtualized •  One Red Hat license per OST64 virtualization regardless of the fact that the CS is virtualized or not.

q  Limited to Proof of Concepts in this step

§ Crystal hardware, OXE MS, ABC/IP, SIP trunking, OV 8770, IP DECT, IP Touch Security, applications…. remains in IPv4

q  Under PCS process (Premium Customer Support) from GA

§  See “IPv6 PCS form OXE R11.1 MD1 ed1” available on the ALE Business Portal

q  Virtualized OST64 installation performed with ALEDS (version 3.1.1.2 minimum)

IPv6



AGENDA







7.  IPv6






4645 VM ENHANCEMENTS (OXE R11.1 MD1) q  5000 mail boxes (instead of 3000) and 30 ports for Hospitality configurations

§ Configurable in Actis 19.2.1 •  By default the number of mailboxes is based on the number of users (steps of 500) •  It can be limited to 1000 mail boxes if desired

q  1000 mail boxes and 16 ports max for Business configurations, as with R11.0.1

q  Up to 600 hours of storage depending on the HD (same rules as with R11.0.1)



AGENDA







7.  IPv6






8001 DESKPHONE

q  Country dependent availability § Not launched worldwide

•  To be checked carefully

q  Main physical characteristics

§  B&W backlit display 128x64 pixels 5-lines §  Dual 10/100M Base Ethernet ports §  2 headset ports RJ9 & 3.5mm §  USB port (DC 5V-1A output) §  High audio quality via HD handsets, HD speaker §  Navigation & Soft keys, Lines/Voicemail/

Headset keys with LED §  2 level adjustable foot § wall-mountable §  Color: grey §  See Speaker notes and product datasheet for more details

MID RANGE VALUE AT LOW END COST

q  Level of service § OXE SIP integrated user

•  Make call •  LDAP Directory Access •  Incoming call, including display info •  Call Hold/Enquiry/Broker •  Call deflect •  Call reject •  Call Transfer •  Call Forward (Local) •  DND •  3Party conference •  CLIR •  Redial •  DTMF •  MWI •  SIP survivability/ HA •  CSTA Monitoring (3PCC not supported)

§  Local Contacts §  8770 R2.6 Device Management

q  not sellable as hospitality room set



8088 HOSPITALITY q  Evolution of the 8082 Hospitality by using the

8088 Smart DeskPhone

q  Same level of service as 8082 Hospitality

§  Native Hospitality features §  Smart Guest Application Suite (SGA)

q  Availability: July 2015

8088 Smart Desk Phone characteristics

(refer to product datasheet for more details):

•  Width/Depth/Height: 252 mm ( 9.92 in.)/167 mm ( 6.57 in.)/204 mm ( 8.03in.)

•  Weight: 1486 gr (3.27 lbs) including handset

•  Color: Black

•  Adjustable foot stand ranging from 25° to 60°

•  Ingress protection (IP): 22

•  CPU: Freescale dual-core (i.MX6 Dual Lite)

•  RAM: 1GByte

•  FLASH: 2GBytes

•  Display: 7” touch screen WVGA (16:9) format /

Ambient Light Sensor

•  Camera: inhibited with a specific fixed mask for hospitality room sets

•  x2 Gigabit Ethernet ports (support of 802.3AF)

•  HDMI 1.4 connector (for external screen display)

•  Bluetooth 2.1 connectivity (BT handset and compatible headset) •  USB 1.1/2.0 connector (compatible headset)

•  Jack connector 3.5 mm and 4 pins stereo (compatible headset)



AGENDA







7.  IPv6






IP TOUCH SECURITY WITH OTMS

q  As of release 2.1 the OpenTouch Multimedia Service (OTMS) is compatible with IP Touch Security feature for the application services that can be provided to Connection users configured on the OTMS and can be secured with a MSM-RM module in front of the server

q  The application services available on the OTMS that support encryption with the IP Touch Security feature for Connection users only are:

- Messaging service (Voice mail and Automated Attendant)

-  Conferencing service

q  See detailed description in the “OTBE-OTMS R2.1 Overview” Pre-Sales Presentation



REFERENCE DOCUMENTS

q  OXE R11.1 Product limits and OXE R11.1 Feature List

q  MLE Cross Compatibility November 2014 and MLE Release Policy November 2014

q  OXE R11.1 Release Notes and OXE R11.1 Installation Procedures

q  OXE R11.1 System Documentation



Linkedin.com – Group: Alcatel-Lucent Enterprise

Twitter.com/ALUEnterprise

Facebook.com/ALUEnterprise

Youtube.com/user/enterpriseALU

Slideshare.net/tagged/Enterprise

Storify.com/ALUEnterprise

Follow us on:



enterprise.alcatel-lucent.com

Documents

OXE R11-1 Overview ed5 1 Central Pre-Sales · • OV 8770 2.6 is available from April 2015. " OmniVista 4760 is no more supported for OXE R11.1 • existing 4760 (upgrade or migration)