TBE036 - IPV6 Solution ed06b.pptx

COPYRIGHT © 2022 ALE International. ALL RIGHTS RESERVED.
TBE036 - IPv6 Solution OXE Purple R100 – Ed06b
Pre-Sales
Pre-Sales presentation
TBE036 - IPv6 Solution OXE Purple R100
Edition 06b: March 2022

Pre-Sales
2
History
Edition 01: Creation
Edition 01b : IPv6 scenario updates and RTP Proxy rule add-on
Edition 02: Update to match IPv6 PCS document requirements
Edition 03: Update for OXE 12.2 MD1 and new deskphones
Edition 04: Minor update and alignment with H2/2019 offer
Edition 05: Update for OXE 12.4 and minor updates
Edition 06: Update for OXE Purple R100
Disclaimer
This documentation is provided for reference purposes only and does not fully describe the capabilities of each Product and related features. Therefore, ALE International declines any liability
for inaccuracies contained herein. For an exhaustive view on features list and product limits for the current product release please see the required Feature List/Product Limits document
available through the ALE eBusiness Portal web site.
In the interest of continued product development, ALE International reserves the right to make improvements or other changes to this document and the products it describes at any time
without prior notice.
Copyright
Copyright © ALE International 2022. Distribution of substantively modified versions of this document is prohibited without the explicit permission of the copyright holder.
Distribution of the work or derivative of the work in any standard (paper) book form for commercial purposes is prohibited unless prior permission is obtained from the copyright holder.
The Alcatel-Lucent name and logo are trademarks of Nokia used under license by ALE.

Pre-Sales
3
General
Objectives
The goal of this presentation is to describe how to design and deploy the OmniPCX Enterprise
Purple R100 in an IPv6 networks.
This document describes the supported IPv6 scenarios, and the components necessary to support
these scenarios.

Pre-Sales
Agenda
1. IPv6 Architecture
2. Supported scenarios
3. RTP Proxy
4. DHCP and TFTP Servers
5. OST64 Deployment
6. How to quote
7. Reference documents

Pre-Sales
5
IPv6 architecture
Definitions
There are 3 types of devices:
• Pure IPv4 devices: Pure IPv4 devices can be configured only with IPv4 addressing.
• Pure IPv6 devices: Pure IPv6 devices can be configured only with IPv6 addressing.
• Dual stack devices: Dual stack devices can be configured as a pure IPv4 device, a pure IPv6 device or a
mixed mode device which have both an IPv4 and an IPv6 address.
An IP network can be divided into 3 subnetworks:
• A pure IPv6 subnetwork is only supporting IPv6 addressing devices. Pure IPv6 and dual stack devices
can be placed in this network.
• A pure IPv4 subnetwork is only supporting IPv4 addressing devices. Pure IPv4 and dual stack devices
can be placed in this network.
• A mixed subnetwork: supporting all type of devices. Pure IPv4, pure IPv6 and dual stack devices can
be placed in this network.

Pre-Sales
6
IPv6 architecture
Deskphones
 The following IP Premium desk phones running on NOE protocol are dual stack devices:
– They support both IPv4 or IPv6 addressing.
– They can be placed in an IPv4, an IPv6 or a mixed IPv4/IPv6 subnetwork.
When running in IPv6, there is no DHCP survivability, and the embedded VPN client is not available
(*) Hybrid ALE-20h and ALE-30h in IP mode
 All other ALE IP desk phones running on NOE protocol or on SIP protocol are pure IPv4 devices:
– They support IPv4 addressing.
– They can be placed in an IPv4 or a mixed IPv4/IPv6 subnetwork.
8008/8008G 8078s
8068s
8058s
8028s
8018
ALE-500
ALE-400
ALE-300
ALE-20
8088
ALE-20h(*) ALE-30h(*)

Pre-Sales
7
IPv6 architecture
Media Gateway
 Both common hardware with GD3/GA3 and GD4/GA4 and crystal Media Gateway with
INTIP3A/INTIP3B are dual stack devices:
 OXE Media server is only IPv4.
 Former GA/GD and INTIPA/INTIPB are pure IPv4 devices:
– They support IPv4 addressing.
GD3
INTIP3A/B
GD3/GA3 INTIP3A/3B
GD4
GD4/GA4

Pre-Sales
8
IPv6 architecture
Other elements 1/2
 4059EE
– The ABC-A Communication handler (4059 module used for signaling purpose) can use IPv6
addresses. It supports both IPv4 or IPv6 addressing and can be placed in an IPv4, an IPv6 or
a mixed IPv4/IPv6 subnetwork.
– When 4059 EE is associated to a dual stack Premium deskphone, the 4059 EE is full dual
stack for voice and signaling, if the 4059 EE is associated to another deskphone, voice is
only IPv4.
4059EE
 PC Port Connection : On a mixed IPv4/IPv6 network,
an IPv6 PC can be connected:
– To the PC port of an IP Touch (IPv4 only)
– To the PC port of a dual stack IP Premium Deskphone
(IPv4 and IPv6)
IPv4/IPv6 mixed
IPv4@ IPv6@
IP Touch
PC Port
IPv6@ IPv6@
Dual stack IP Premium
PC Port
IPv4@ IPv6@
Dual stack IP Premium
PC Port
IPv4@/IPv6@ IPv6@
Dual Stack IP Premium
PC Port

Pre-Sales
9
IPv6 architecture
Other elements 2/2
 OXE call server is pure IPv4
– It support IPv4 addressing.
– It can be placed in an IPv4 or a mixed IPv4/IPv6 subnetwork.
Support of IPv6 requires that OXE call servers (main, standby) and PCS are virtualized.
 IP Premium SSM and MSM security modules are dual stack as of OXE release 12.0
As of October 2020, the IP Premium Security solution is phased out. It will be supported
according to the ALE release policy.

Pre-Sales
10
IPv6 architecture
OST64
OXE Call server is pure IPv4. It can operate in IPv6 via the OST64 server.
OST64 - OXE Signaling Translator for interfacing IPv6 & IPv4 NOE signaling
– A virtualized software component co-localized with other VMs (e.g. OXE-V) acting as a proxy, that
translates the IPv4 signaling messages from CS, to IPv6 signaling messages towards IPv6 devices and
vice versa.
– Supports only NOE & IP Link protocols (SIP & H323 are not translated)
– There is one OST64 instance per OXE Call server or PCS
– OST64 is a dual stack device and must be installed in a mixed IPv4/IPv6 network.
Pure IPv6
IPv4/IPv6 mixed
Call server
OST64
IPv4 IPv6 IPv6 deskphone
NOE/IPv4 NOE/IPv6

Pre-Sales
11
IPv6 architecture
RTP Proxy
– RTP Proxy is an application running on GD3/GA3, GD4/GA4 or INTIP3A/INTIP3B, that converts IPv4
media streams from pure IPv4 devices to IPv6 media streams towards pure IPv6 devices and vice versa
– Some compression resources on boards are reserved by the RTP Proxy application.
Pure IPv6
IPv4/IPv6 mixed
IPv6 deskphone
RTP/IPv6
RTP Proxy
IPv4 IPv6
RTP/IPv4
– RTP Proxy is a dual stack component and must be installed in a mixed IPv4/IPv6 network.

Pre-Sales
12
IPv6 architecture
Signaling & media communication
 Rules for signaling
– IPv4/IPv6 signaling translation is done by OST64
 Rules for media
– IPv4/IPv6 Media translation is done by RTP Proxy
– Between 2 dual stacks devices: the behavior depends on the configuration (IPv4 or IPv6) - (OXE parameter
« Prefered IPv6 for Media » )
Call to
User B
Pure IPv4 Pure IPv6 Dual Stack
User A
Pure IPv4 IPv4 RTP Proxy IPv4
Pure IPv6 RTP Proxy IPv6 IPv6
Dual stack IPv4 IPv6
Based on « Prefered IPv6 for
Media« System Option
Signaling to
Peer component
Pure IPv4 Pure IPv6 Dual Stack
Call server (pure IPv4) IPv4 IPv6 via OST64 IPv4

Pre-Sales
13
IPv6 Compatibility Rules
OST64 & RTP Proxy make the Communication Server compliant with IPv6.
The following table indicates in which mode each element can operate.
IPv4 IPv6 Dual stack Comment
Communication server Yes
OST64 Yes
RTP Proxy Yes
IPMG (GD3/GA3/GD4/GA4) Yes Yes Yes
Crystal MG (INTIP3A/3B) Yes Yes Yes
4059EE Yes Yes Yes
IP Desktop Premium
8008, 8018, 8028s, 8058s, 8068s, 8078s
ALE-20, ALE-20h, ALE-30h, ALE-300,
ALE-400, ALE-500
Yes Yes Yes
IP Premium SSM/MSM – Phase Out Yes Yes Yes From binary 4.0.14

Pre-Sales
14
Compatibility in a mixed IPv4-IPv6 network
The following components can be deployed in a mixed IPv4-IPv6 network or a pure IPv4 network.
Element Comment
IOIP3 board Only IPv4
OXE Media Server Only IPv4
Voice mail 4645 Only IPv4
8770
Only in IPv4. OXE IPv6 VoIP ticket
treatment available
OTMC/OTMS Only IPv4
WebRTC Gateway Only IPv4
Element Comment
CCD
CCS application is IPv4 only.
CCD Agent sets can be in IPv4 or IPv6
SIP Endpoint Only IPv4
SIP Trunking Only IPv4
IPDect, IP-xBS
& VoWLAN
Only in IPv4. OXE IPv6 VoIP ticket
treatment available
IP Desktop Softphone Only IPv4
Deskphone other than
dual stack IP Phone
Only IPv4
All other not mentioned ALE applications work in IPv4 mode. Applications performing RTP flows use the RTP
Proxy to transform RTP on IPv4 to RTP on IPv6.

Pre-Sales
15
Feature not compatible in an IPv6 environment
The following features are incompatible in an IPv6 deployment even in a mixed IPv4-IPv6 network
 SCEP (Simple Certificate Enrollment Protocol)
 Voice recorder IPv4 & IPv6 (IP DR link & TDM DR link) and OmniPCX Record
 Legacy e-Reflex IP phone set 4035.
 OXE Native encryption

Pre-Sales
17
PSTN
Scenario 1
Mixed Mode Network (IPv4/IPv6) using IPv4 addresses
IPv4/IPv6 mixed
Call server
RTP/IPv4
GD4 IPMG
IPv4@
IPv4@
IPv4@
RTP/IPv4
RTP/IPv4
NOE/IPv4
NOE/IPv4
IP Premium Deskphones
(Dual-Stack)
IP Link/IPv4
IP Premium Deskphones and Media Gateways operate in pure IPv4
• Direct RTP in IPv4 between IP Premium Deskphones and Media Gateways
4645
(Dual-Stack)

Pre-Sales
18
PSTN
Scenario 2
Mixed Mode Network (IPv4/IPv6) using IPv4 and IPv6 addresses
IPv4/IPv6 mixed
Call server
RTP/IPv6
GD4 IPMG
IPv4@ , IPv6@
IPv4@, IPv6@
RTP/IPv6
RTP/IPv4
NOE/IPv4
NOE/IPv4
(Dual-Stack)
IP Link/IPv4
IP Premium Deskphones and Media Gateways operate in dual stack IPv4/IPv6
• Direct RTP in IPv6 between IP Premium Deskphones and Media Gateways (“Prefer IPv6 for Media“ in OXE system )
• Signaling is IPv4
4645
RTP Proxy
IPv4 IPv6
(Dual-Stack)
RTP/IPv6
IPv4@, IPv6@
RTP/IPv6

Pre-Sales
19
Scenario 3
Mixed Mode (IPv4/IPv6) to a Pure IPv6 Network (without Media Gateway)
IP Premium Deskphone operates in pure IPv6, IP Touch operates in pure IPv4
• Direct RTP between (IPv6) Premium Deskphone and (IPv4) IP Touch: RTP translation IPv4/IPv6 by RTP Proxy
• Direct RTP between both IP Premium Deskphones
The IPMG is dedicated to RTP Proxy function so there is no OXE services for IP Premium Deskphone/IP Touch
IPv4/IPv6 mixed
Call server
IPv6@
IPv6@
OST64
IPv4 IPv6
RTP Proxy
IPv4 IPv6
RTP/IPv6
RTP/IPv6
NOE/IPv6
NOE/IPv4
RTP/IPv4
IPv4@
IP Touch
NOE/IPv4
IPv6 network
(Dual-Stack)
(Dual-Stack)

Pre-Sales
20
Scenario 4
Mixed Mode (IPv4/IPv6) to a Pure IPv6 Network – 4059EE
• The ABC-A Communication handler (4059 module used for signaling purpose) can use IPv6 addresses and communicates
with the call server via the OST64
IPv4/IPv6 mixed
Call server
IPv6@
OST64
IPv4 IPv6
RTP Proxy
IPv4 IPv6
NOE/IPv6
NOE/IPv4
RTP/IPv4
IPv4@
IP Touch
NOE/IPv4
IPv6 network
4059EE IPv6@
ABCA/IPv6
RTP/IPv6
ABCA/IPv4
(Dual-Stack)

Pre-Sales
21
PSTN
Scenario 5
ABC Subnetwork and ABC Supranetwork
The IPv4/IPv6 RTP flow negotiation works in ABC subnetwork and ABC supranetwork
The ABC signaling (ABC/H323 for ABC links, ABC-F for ABC-F trunk groups) remains in IPv4
IPv4/IPv6 mixed
IPv6@
Call server
Node 1 OST64
IPv4 IPv6
Call server
Node 2
OST64
IPv4 IPv6
INTIP3A/B
INTIP3A/B
INTIP3A/B
IPv6 network
NOE/IPv6
IP Link/IPv6
RTP/IPv6
ABC/IPv4
H323/IPv4
IP Link/IPv4
NOE/IPv4
IP Link/IPv4
IP Link/IPv4
RTP on ABC depends on the
« Prefer IPv6 for Media« System
Option
(Dual-Stack)

Pre-Sales
22
Scenario 6
OTMS in a Mixed Mode (IPv4/IPv6)
IPv4/IPv6 mixed
Call server
IPv6@
IPv6@
OST64
IPv4 IPv6
RTP Proxy
IPv4 IPv6
RTP/IPv6
RTP/IPv6
NOE/IPv6
NOE/IPv4
RTP/IPv4
IPv4@
IP Touch
NOE/IPv4
IPv6 network
OTMS
IPv4
https/IPv4
Connection User
An IP deskphone operating in pure IPv6 can be associated to an Opentouch CT user
(Dual-Stack)
(Dual-Stack)

Pre-Sales
23
Scenario 7
OTMS in a Mixed Mode (IPv4/IPv6) – Softphone IPv4
IPv4/IPv6 mixed
Call server
IPv6@
OST64
IPv4 IPv6
RTP Proxy
IPv4 IPv6
RTP/IPv6
NOE/IPv6
NOE/IPv4
RTP/IPv4
IPv6 network
OTMS
IPv4
https/IPv4
Connection User
Softphone mode
OTC PC Softphone operates in pure IPv4, IP Premium Deskphone operates in pure IPv6 .
SIP/IPv4
Softphone
(Dual-Stack)

Pre-Sales
24
In case of failure of the OST64, a switchover occurs to the standby OXE Call server.
Scenario 8
Redundancy : Lost of OST64
Main Call Server
Standby Call Server
IPv4/IPv6 mixed
IPv6 network
NOE/IPv6
NOE/IPv4
OST64
IPv4 IPv6
OST64
IPv4 IPv6

Pre-Sales
25
Switchover between Main and Standby INTIP3B requires an IPv4/IPv6 translation through OST64.
Scenario 9
Redundancy : INTIPB3 switch over
Main Call Server
IPv4/IPv6 mixed
IPv6 network
IP Link/IPv6
OST64
IPv4 IPv6
Standby
INTIP3B
Main
INTIP3B
IP Link/IPv4

Pre-Sales
26
PSTN
Scenario 10
Encryption
IP Premium Deskphone operates in pure IPv6
• IP Premium SSM must secure both the OXE Com Server and its dedicated OST64
IPv4/IPv6 mixed
Call server
IPv6@
OST64
IPv4 IPv6
IPv6 network
GD4
IPMG IPv6@
NOE/IPv4
IP Premium MSM
IP Premium SSM
IPSEC/IPv6
NOE/IPv6
SRTP/IPv6
RTP/IPv6
IPSEC/IPv6
(Dual-Stack)
As of October 2020, the IP Premium Security solution is phased out. Please consult the ALE release policy.

Pre-Sales
27
Scenario 11
Encryption
• IP Premium SSM must secure both the OXE Com Server and its dedicated OST64
IPv4/IPv6 mixed
Call server
IPv6@
OST64
IPv4 IPv6
IPv6 network
NOE/IPv4
IP Premium SSM
IPSEC/IPv6
RTP Proxy
IPv4 IPv6
IPv4@
IP Touch
NOE/IPv6
NOE/IPv4
IPSEC/IPv4
SRTP/IPv6
SRTP/IPv4
(Dual-Stack)

Pre-Sales
28
PSTN
Scenario 11
Encryption – migration IPv4 to IPv6
IP Premium Deskphone operates in pure IPv6. The Media Gateway is installed in IPv4 network
• RTP Proxy should not be configured behind IP Premium xSM module
• Old encryption boxes MSM-RM will be operating in IPv4 mode only with the new IP Premium SSM module
IPv4/IPv6 mixed
Call server
IPv6@
(Dual-Stack)
OST64
IPv4 IPv6
IPv6 network
NOE/IPv4
IP Premium SSM
IPSEC/IPv6
RTP Proxy
IPv4 IPv6
IPv4@
NOE/IPv6
NOE/IPv4
SRTP/IPv6
SRTP/IPv4
Crystal MG
MSM - RM
RTP/IPv4
IPSEC/IPv4

Pre-Sales
29
PSTN
Scenario 12
Mixed Mode (IPv4/IPv6) to a Pure IPv6 Network on a remote site
The Media Gateway is installed in IPv6 Network operates in pure IPv6 on a remote site
• Signaling and IP Link translation is done by OST64
• PCS secures the remote site.
IPv4/IPv6 mixed
Call server
IPv4@
IP Touch
4645
RTP/IPv4
PCS
GD4
IPMG
OST64
IPv4 IPv6
IPv4/IPv6 mixed
OST64
IPv4 IPv6
IPv6 network
WAN
IPv4/IPv6
mixed
NOE/IPv6
IP Link/IPv6 RTP/IPv6
RTP Proxy
IPv4 IPv6
IPv6@
(Dual-Stack)
RTP/IPv6
RTP/IPv4
RTP/IPv4
IP Link/IPv4
NOE/IPv4
IPv6@

Pre-Sales
30
PSTN
Scenario 12 bis
IPv6 Network on a remote site, loss of the call server
The Media Gateway is installed in IPv6 Network operates in pure IPv6 on a remote site
• PCS starts
• IMPG, IP Premium connect on PCS through the OST64
IPv4/IPv6 mixed
Call server
IPv4@
IP Touch
4645
RTP/IPv4
PCS
GD4
IPMG
OST64
IPv4 IPv6
IPv4/IPv6 mixed
OST64
IPv4 IPv6
IPv6 network
WAN
IPv4/IPv6
mixed
NOE/IPv6
RTP/IPv6
IPv6@
(Dual-Stack)
IP Link/IPv4
NOE/IPv4
IP Link/IPv4
NOE/IPv4
IPv6@

Pre-Sales
32
RTP Proxy
Compression resources
RTP proxy converts IPv4 media streams from pure IPv4 devices to IPv6 media streams towards
pure IPv6 devices and vice versa.
It uses compression resources of the IP Media Gateway. One RTP Proxy feature requires 2
compressions resources. The IP Media Gateway can be configured to dedicate all of its
compression resources, or only a part of them to work as RTP Proxy.
Example: a GD3/4 with an ARMADA daughter board has 60 compression resources.
Numbers of RTP Proxy
required
Numbers of compression
resources needed by the
RTP Proxies
Remaining number of
compression resources on
the IP Media Gateway
0 0 60 No RTP Proxy. IPMG provides only standard
compression resources
11 22 38 IPMG provides RTP Proxy and standard
30 60 0 IPMG is fully dedicated to RTP Proxy feature

Pre-Sales
33
The following table gives the maximum number of RTP Proxy for a given configuration (board and
daughter board).
RTP Proxy
Compression resources per board
board
Daughter
board
Max available
Max number of RTP Proxy
GA3/GA4 None 30 15
GA3/GA4 ARMADA 60 30
GD3/GD4 None 30 15
GD3/GD4 ARMADA 60 30
INTIP3B None 30 15
INTIP3B ARMADA 60 30
INTIP3A None 30 15
INTIP3A ARMADA 60 30
INTIP3A ARMADA x 2 90 45
INTIP3A ARMADA x 3 120 60
Note: The maximum
number of compression
resources depends on the
ARMADA daughter board
configuration

Pre-Sales
34
RTP Proxy Sizing
General principles
Sizing of RTP Proxy depends on the customer topology. It depends on the RTP flows between the
IPv6 and the IPv4 area.
The following recommendations must be followed-up:
 It is recommended to migrate existing Media Gateway to the dual stack IPv4/IPv6 version:
GA3/GD3 or GA4/GD4, INTIP3A/INTIP3B
 If there are IPv4 and IPv6 devices that can do external calls, the PSTN access must be on Media
Gateway running in a mixed IPv6/IPv4 mode.
 The design must minimize the mix of IPv4 and IPv6 devices.
It is strongly recommended that you contact the central presales team to check the RTP proxy
configuration.

Pre-Sales
35
Number of IPv6 devices 100
Number of IPv4 devices called by an IPv6 device 100
Number of RTP Proxy 30
Hypothesis
Number of calls per hours 5
Internal traffic 100%
Internal call duration in seconds 120
Percentage of call fail due to a lack of RTP proxy 0.10%
RTP Proxy Sizing
Example 1 – Case with GD2
PSTN
IPv4/IPv6 mixed
Call server
IPv6@
RTP Proxy
IPv4 IPv6
RTP/IPv4
IPv4@
IP Touch
IPv6 network
GD2
IPMG
IPv4@
Topology with:
 100 IP Touch in the IPv4/v6 mixed area
 100 IP Premium Deskphone with IPv6 addresses
RTP/IPv6
RTP/IPv4
This configuration require a dedicated media gateway with
a GD3/GA3 used as a RTP Proxy
RTP Proxy is used to convert media in case of:
 Call from pure IPv6 devices to pure IPv4 devices
 Call from pure IPv6 devices to PSTN
(Dual-Stack)

Pre-Sales
36
Hypothesis
RTP Proxy Sizing
Example 2 – Replace GD2 by GD3
PSTN
IPv4/IPv6 mixed
Call server
IPv6@
RTP/IPv6
IPv4@
IP Touch IPv6 network
GD3
IPMG
Topology with:
RTP/IPv4
RTP Proxy
IPv4 IPv6
The media gateway running in dual stack can host the RTP
Proxy applications (depending on the number of RTP proxy
needed)
(Dual-Stack)

Pre-Sales
37
Hypothesis
RTP Proxy Sizing
Example 3 – Replace IP Touch deskphones by IP Premium deskphones
PSTN
IPv4/IPv6 mixed
Call server
IPv6@
RTP/IPv6
IPv4@
IP Touch IPv6 network
GD4
IPMG
IPv6@/IPv4@
Topology with:
Replace 80 IP Touch by 80 IP Premium
RTP/IPv4
PSTN calls from IPv6 pure device don’t need translation
RTP Proxy
IPv4 IPv6 IP Premium Deskphones
(Dual-Stack)

Pre-Sales
38
RTP Proxy Sizing
Example 4 – Access to voice mail
IPv4/IPv6 mixed
Call server
IPv6@
RTP Proxy
IPv4 IPv6
RTP/IPv4
IPv6 network
Topology with:
 Voice mail on the 4645.
 Hypothesis :
– 1 call to voice mail every 3 hours
– Call duration is 2 minutes
RTP/IPv6
4645
Hypothesis
Number of calls per hours 0.33
 Call from pure IPv6 devices to voice mail
(Dual-Stack)

Pre-Sales
40
DHCP and TFTP servers
IPv6 compatible IP deskphones support both statefull (DHCPv6) and stateless (SLAAC) auto-
configuration
 DHCP server
–In IPv4, the DHCP server can be either external, or embedded in the call server.
–In IPv6, the DHCP server must be external (Call server don’t support IPv6)
 TFTP server
–IPv4 operation : IPv4 TFTP Server is provided by OXE Call server
• OXE Call server is IPv4 TFTP server for IPv4 devices (IP Touch, IPMG GD2)
• OXE Call server is IPv4 TFTP server for OST64
–IPv6 operation : IPv6 TFTP Server is provided by OST64
• OST64 is IPv6 TFTP server for IPv6 devices and IPv6 IPMG (GD3, GA3, GD4, GA4)

Pre-Sales
42
OST64 – OXE Signaling Translator is natively virtualized.
– OST64 is be proposed on an OXE-V only.
– OST64 is a dongle-less and license-less component
Deployment
OST64
Hypervisor
Virtualized environment
VM#1
Custom Linux
OXE CS
Dongle
FLEXLM
Centos
VM#2 VM#3
OST64
Custom
Linux


Please refer to: TBE031 – OpenTouch Suite for MLE in virtualized environment (Partner, ALE) and
TBE043 - OpenTouch Suite for MLE virtualization design guide (Partner, ALE)

Pre-Sales
44
How to quote
ACTIS
Configure IPv6 and OST 64
Check IPv6 and configure the number of OST64:
There is one OST64 instance per OXE Call server
or PCS. (multiply by 2 in case of OST redundancy)
ACTIS configures one SUSE Linux license per OST64. Price of this support is fully integrated in the SPS as of Actis 23.1
Additional IPMG(s) for RTP Proxy function depends on RTP traffics between IPv6 zone & IPv4 zone

Pre-Sales
46
Reference Documents
 TG0090 Installation and troubleshoot of the OXE in IPV6 network (Partner, ALE)
 TBE031 – OT Suite for MLE in virtualized environment (Partner, ALE)
 TBE043 - OT Suite for MLE - Virtualization Design Guide (Partner, ALE)

Pre-Sales
linkedin.com/company/alcatellucententerprise
twitter.com/ALUEnterprise
facebook.com/ALUEnterprise
youtube.com/user/enterpriseALU
enterprise.alcatel-lucent.com
47

TBE036 - IPV6 Solution ed06b.pptx

Recommended

Recommended

More Related Content

Similar to TBE036 - IPV6 Solution ed06b.pptx

Similar to TBE036 - IPV6 Solution ed06b.pptx (20)

Recently uploaded

Recently uploaded (20)

TBE036 - IPV6 Solution ed06b.pptx