ENTP0400P13TEUS

Alcatel-Lucent OmniPCX Enterprise
R9.1 Newness
All Rights Reserved © 2009, Alcatel-Lucent 1
OBJECTIVE
To describe the Release 9.1 new features
Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Ref. ENTP0400P13TEUS Issue 03
NGP: New Generation Platform
Overview
The aim of the New Generation Platform(1) is to cover the hardware and
software obsolescence and to provide
A converged solution for both Common and Crystal hardware platforms
New IP Gateway functionalities, capacities and performances
30 onboard compressors, permanent binaries authentication
The NGP project introduces the following boards

Motherboards
INT-IP3(2)
Replaces the current INTIP Crystal hardware board
GD3/GA3(2)
Replace the current GD/GA Common hardware boards
PowerMex(3)
Replaces the current Mex (components obsolescence)
Daughter boards
ARMADA: common to both platform types, replaces MADA1, MADA3, GIP4 and GIP4A
Actis 14.2 (minimum) is required to order NGP boards(4)
1) NGP is available as of R9.1 TR+1b (i1.605.14 available on BPWS since 26 feb 2010)
2) INT-IP3 and GD3/GA3 boards are only available from R9.1
3) This board mainly covers hardware obsolescence. It can only be connected to a GD3
Remark:
The NGP boards handle Linux Kernel 2.6
4) An order realized with Actis 14.1.1 will offer GD2/GA2/MEX and INTIP2

NGP: New Generation Platform
CS-2
CS-2 board has the following characteristics:

Intel 80579 Processor (600 MHz)
1 x DDR2 memory module (Total size: up to 2GB)
FLASH Boot
USB 2.0 (not usable in this stage)
1 x RS232 interface(1)
2 x 10/100/1000 BT Ethernet LAN interfaces
Enhanced SATA Disk 2.5
4 x 10/100BT Ethernet interfaces with SLANX4 daughter card
PCS mode
For XL configuration, instead of Appliance Sever use, the CS-2 can be used
CPU CS-2: dual Ethernet(2)

2 modes: load balancing or backup
1) V24 port can be used for Remote reset signal coming from a RMA Box
2) If the second Ethernet port is not used, it must not be connected to the network

SIP enhancement in R9.1
SEPLOS Keep alive mechanism
The purpose of this feature is to create a supervision of the device in order

to know if its state is in/out of service
History Info (RFC 4244)
When a set forwarded (on a SIP voicemail or an external number via SIP
Trunking) is called, this feature allows to add an History-Info header in the
INVITE message for the SIP External gateways/Voice mails (allowing to
notify the initial called party)
SEPLOS Call Server Information display
A SIP MESSAGE can be sent to the SEPLOS device in order to inform the user
about the CS settings
Forwarding activation, DND, Hunting group belonging
Compatible devices: Thomson ST2022/ST2030 and 4008/18 EE in SIP mode

(Cont)
SEPLOS Reason header (RFC 3326)

When an equipment is not reachable, the OXE provides the reason via a new
field called Reason Header in the SIP answer message
Examples: Busy, Out of service
SIP: PRACK with SDP

Allows the media negotiation in a PRACK message
SIP: Call Admission Control for FAX calls

With this feature the IP domains can be configured in order to work in
tandem and to allow the management of the number of FAX calls
SEPLOS: SIP/CSTA divert service

The purpose of the feature SEPLOS SIP/CSTA - Divert Service is to provide
the Divert service over CSTA for SEPLOS

(Cont)
Mapping between ABC F/ISDN causes and SIP responses
It is now possible to manage(1) the codes sent by the CS in case of problem in

case of ABCF/ISDN SIP exchanges
SIP: Contact Header User part
As of release 9.1 the user part is sent in the FROM and in the Contact
fields
SIP: Method update for early media (RFC 3311)
The UPDATE method allows to provide updated session information before to

receive a final response to the initial INVITE request
1) In the previous releases, this message mapping was hard coded

(Cont)
SIP - tool: Active calls display
The sipdump tool has been enhanced
SIP backup with PCS
The SIP sets (SEPLOS & Device) and the external gateways can be activated
on an active PCS
Only equipments supporting Primary and Backup SIP server can benefit from this feature
SIP Stand-Alone with 4008/18 extensions
Possibility to use the SIP protocol in native mode instead of NOE

(proprietary) for 4008/18 Extended Edition extensions
The SIP mode activation can be realized via the local MMI or globally via the
lanpbx.cfg(1) (as of patch i1.605.14e)
DHCP server + SIP Device Manager 1.2 allow the automatic setup of the
sets
1) Restriction in ABC-F network: all nodes have to use R9.1 version at minimum

OmniTouch 4135 IP
The OmniTouch 4135 IP is a conference phone based on SIP providing wideband sound (200-7000 Hz)
Features: Audio
5-way conferences
Call recording on SD card up to 2 GB
G711, G729ab
DTMF: In-band / SIP INFO, DTMF RFC 2833
Features: Directory
Phone book: 1,000 entries per profile
Export/import of directory and configuration
Call list
User profile: 4 profiles (password protected)
LDAP Directory access
Features: Infrastructure
DHCP, static IP, SIP SEPLOS
One SIP account
Redundancy : Spatial, PCS, via external SIP proxy
802.1p and VLAN tagging, 802.1x
NTP and SNTP
Power over Ethernet IEEE 802.3af
Transformer: 100240 V AC/13.5 V DC
Expansion microphone port and aux port
Software upgrade: TFTP / HTTP/HTTPS
Integrated web server
Web-based remote configuration & diagnostics log files and SIP traces
The OmniTouch 4135 IP is declared as a SIP device

Configuration can be done using web (login: admin / password: 1234)
Two accounts can be created for a SIP PBX or SIP Public Provider

DECT
Communications Encryption
As of the patch i1.605.15 (TR+2), it is possible to encrypt the DECT

communications via IBS-NG(1) on Crystal hardware
In the previous releases, theIBS domains could only support identity and
Authentication modes
From now, the encryption is also availabale
3 available security levels (modes)
Identity (default mode):
The system accepts emission/reception of DECT communications from DECT terminals only
verifying their IPUI-N/IPUI-0
1) IBS-NG: Intelligent Base Station New Generation

DECT
Communications Encryption (Cont)
Authentication (based on Identity mode):
An authentication key (AC(1) key) has to be given to the system and terminals
Thanks to a specific algorithm, each device is going to derivate a new (called UAK(2)) key from the AC
one
At each signaling exchange (registration, call request, localization, un-registration), the

system and terminals authenticate the requesting device
The OXE generates a random key and codes it with the UAK key, this new key is called:
DCK(3),
Then it provides the random key to the terminal
The terminal calculates itself the DCK from the received random key et sends it to the OXE
The OXE checks the coherency of the keys if they correspond, the terminal is
authenticated
Encryption (based on Authentication mode):
The DCK key is also used to encrypt the communication
This key is calculated at the beginning of each communication
1) AC: Authentication Code
2) UAK: User Authentication Key
3) DCK: Derived Cipher Key

CSTA/RSI optimization
Creation of a new type of RSI
The specificity of this RSI is to send Route-End only when call is answered
In case of ringing overflow on RSI, Reroute Request will be sent instead of a new
Route Request
Increase of the reroute requests
Up to release 9.0 the maximum number of reroute request is 3
As of Release 9.1 a maximum of 1000 RE-ROUTE-REQUEST is possible
This maximum number of RE-ROUTE-REQUEST is manageable via a new parameter

in RSI object (the default value of this new parameter is 3)
Configuration
/Applications/CCD/RSI
Max Number of Reroute Request : 3 (up to 1000)
The maximum number of RSI Reroute Request is displayed in the rsi tool

CSTA/RSI and PCS
Before R9.1 a CSTA client is able to connect on a inactive PCS
From R9.1 a CSTA client connection is
Accepted if the PCS is in active mode
Rejected if the PCS state is inactive
When the PCS is inactive the connection is treated like with a stand-by CPU

Security enhancement (JTIC)
From the release I1 the user account password management in OXE takes JITC
conformance as a minimum level of security
JITC(1) conformance requires the following:

Min length: 8 characters
Min lower case letter: 1
Min upper case letter: 1
Min digits: 2
Min special character: 1
From the release I1 only SSLV3 and TLSv1 are allowed
The SSL support for LOW encryption ciphers is disabled in order to increase
the security level because messages encrypted with low encryption ciphers
are easy to decrypt
The key length must be equal or larger than 128 bits
1) JTIC: Joint Interoperability Testing Center

Log files improvement
maohist logs size is increased from 1000 to 9999 records
With the previous releases, the DHS3 process logs during RUNTEL are stored in
DHS3-init logs
Logs are kept for the for three last RUNTEL startup
At each restart of the OXE the oldest is lost and overwritten by the new one
The log files are stored in /tmpd folder
From release R9.1 the last 10 RUNTELs DHS3-init logs will be stored

(Next)
With the previous releases, a backtrace is generated when the execution of a

program in the telephone application is not performed correctly
There are two real-time processes, btracer and blackbox, used to export
the information linked with the Monitel telephone application process
Logs are kept for the three last reboots

At each restart of the OXE the oldest is lost and overwritten by the new one
Currently btracer and blackbox store logs in /tmpd directory
From release R9.1 the last 10 reboots btracer and blackbox logs will be
stored

(Next)
The tool excvisu is used to read the exceptions stored by btracer

Currently it can read only up to 3
Using excvisu 3
From release R9.1 it will be possible to read the 10 btracer logs
Using excvisu 10
The tool readbbox is used to read the logs stored by blackbox

Currently it can read only upto 3
Using readbbox 3
From release R9.1 it will be possible to read the 10 blackbox logs
Using readbbox 10
The infocollect tool is used to collect all the logs from the site in case of any
problem
Currently it copies only 3 logs of DHS3-init logs
From release 9.1 the latest 10 logs from main and standby will be copied by
infocollect tool(1)
1) infocollect use process

login as root, then
cd /usr/sbin
./sfx-infocollect.sh
infocollect
Transfer file /tmpd/infocollectyyyy-mm-ddThhZ.tbz to the PC

Download tool from BPWS and install it on PC to open the file

New basic features
Timer for overflow on associated set or no reply

This timer can now be configured via the Phone Features Class of Service
Example of need: a tandem is created between an OXE user and a GSM. In order to
let the public network to route the call to the GSM before overflow the associated
set (voice mail for example), this timer can be increased
New Moxa box Nport 5410
Supervision Enhancement
A new option allows to cancel the direct call by supervision key
Automatic display of Perso (main) page on NOE sets

This feature implementation allows the first page of perso page in Alcatel-
lucent 8&9 series sets to be displayed after certain time out

New basic features
(Cont)
4059 internal call parking

An attendant (4059 IP) is able to park the established calls coming from local
node as well as Network node, on another set
Increase in number of attendants and attendant groups
Implementation of Arabic and Hebrew strings on IP Touch sets
MLA & Conferences

Possible to initiate the 6-party conferences even though one of the MLA
keys is the master of the conference
MLA & Call notification

In case of incoming call on a MLA key, the display is the same as a
supervision key

Multi Countries
Forward on External
Multi Countries / Forward on External
Enhancement of the external call forwarding in case of CAC=0
Default IP Domain
Calling Id:
Central
01273380000
Office USA
CLI:02088529000
IP Domain 1
IP Domain 2
FORWARDED
CLI: 01273380000
Private to public overflow
France
CAC=0 CAC=0
GD 2
UK
CLI: 01392 875100 GD 1
Unavailable route
The aim of this feature is to respond to a specific case: a CS owns two GDs but CAC of links between GDs and CS is set to 0, meaning
than no call can be done from GD #1 to GD #2 directly.
Instead, private to public overflow feature is used.
Before R9.1 in a such situation, if a set of GD #2 is immediately forwarded on an external number using a GD #2 trunk group, call from
GD #1 to this set actually fails, because call forward is managed directly from caller set (on GD #1) and private to public overflow does
not allow to seize distant trunk group (on GD #2).
In R9.1, the call forwarding works fine.
Multi-Country feature can affect external call forward. If forwarded sets are not located in the same country then the call terminates,
calling number presented on outgoing trunk group must take care of this specific case. To provide a relevant calling number two
possibilities are offered:
Building an International calling number from caller number using parameters of the country of forwarded set.
Ignore the configuration and provide forwarded sets number.
Due to high complexity of first solution, in case of multi-county external forward, number of forwarded sets will be provided as calling
number. This feature works only with R2 and ISDN TGs.

LLDP-MED
Generalities
The IP Touch x8 Series extensions handle the LLDP-MED protocol
LLDP-MED: Link Layer Discovery Protocol - Media Endpoint Discovery
LLDP operates on data link layer. It is used to exchange some devices

information (identity, capabilities) between the connected devices and the
network switch. This mechanism is based on IEEE 802.1AB and ANSI TIA 1057
standards
With LLDP-MED protocol, the IP Touch x8 Series terminals can automatically:
Acquire VLAN ID(1)
Renegotiate power consumption with more accurate figure instead of only

POE class information
Send inventory information of terminal to the adjacent LAN switch
1) The terminal sends to the switch some information via a LLDP/LLDP_MED message. It then starts a one second timer. If the set
does not receive anything from the switch, it considers that the adjacent LAN Switch does not support VLAN Assignment, and the
terminal continues its initialization with a normal startup

MIPT enhancement
MIPT on PCS: survivability step 2 (from i1605.14e)
MIPT set in Branch Office has to be able to reach a PCS in case of WAN
failure
Step1 (OXE R9.0): solution requiring a mandatory local DHCP server
Step2 (OXE R9.1): solution with IP addresses in flash memory of the MIPT
PRS on MIPT
PRS Openness only to offer notification information

Examples: Meeting request application, nurse call (alarm from a patient)

MIPT enhancement
(Cont)
Hands-free activation on MIPT
The feature allows the Loudspeaker Announcement on MIPT 310/610
Alarm on MIPT (UPMC)
MobiCall application (from NewVoice company) sends an alarm to a MIPT set,

the calling name has 16 characters on one line
With new implementation: MIPT display will be having name on two lines
(30 characters in UTF-8) instead of one
MobiCall (MC) is an alarm system which is connected to OXE through an ABC-F TDM trunk group (T1 or T2). When an alarm occurs MC
calls an MIPT set (a nurse or other people). In the SET-UP message MC fills the calling name with the 16 first characters of the alarm
text. For example "Patient. When the MIPT answers MC sends 16 further characters as name in FACILITY message.
For example "Room No12345".
With new implementation MIPT display will be having name on 2 lines (30 characters) instead of one.
MC will send 30 characters in UTF8 name. When ringing, instead of 3 lines with Name, number and "Calling", display would be Name on
two lines (15 characters on each line) and "Calling" on 3rd line. When MIPT answers call, display would be Name on two lines and
"Conversation" + timer" on 3rd line.
A new trunk group data will be added in given below path.
Trunk Group -> Special Services + Alarm Call.
+ Nothing
+ Urgent Broadcasting
+ Timed Call Release.
Default value for the parameter Special Services is Nothing.
The condition to modify display on MIPT for an Alarm Call will be MIPT Set + trunk group data. When MIPT answers the call, it directly
goes to DTMF mode. When MIPT dials the digits in DTMF mode, display of digits on MIPT screen can be managed through parameter
given in below path.
System -> Other System Parameter + No. Digits displayed on the Sets (1 to 16).

IP Enhancement
Attendant on 4068 set
Because 4035/4037 sets are in phase out status, there is no more hard-phone
for attendants
A solution based on 4068 (Fast Ethernet/Extended Edition) allows to use this set
as an attendant
The 4059 TDM solution is in phase out

The 4059 solution is only available on IP for a new site

IP Enhancement
IP Touch Security - Solution historical
The IP Touch Security Solution offered the possibility to secure the signaling
and voice over IP in Stand-Alone configuration at its first launching
A SSM(1) is required to secure the CS CPU

And a MSM(2) is required to secure a MG (Crystal or Common hardware)
The IP Touch handles themselves the security feature
A second step of development allowed to secure IP ABCF Network links

(Signaling first, then Signaling + Voice)
Then, this Thalès solution has been chosen to respond to some customers who
wanted a strong and reliable signaling link against DOS(3) attacks for remote IP
Media Gateways (Common hardware). The Thalès VPN Client is embedded on
the GD(4) and only encrypts the signaling
This GD is then called MGSec
The release 9.1 introduces the possibility to secure a MG without Thalès boxes
(NGP Crystal & Common hardware) for Signaling & Voice. The Thalès VPN Client
is embedded on both platforms boards
1) SSM: Server Security Module. In case of Call Server duplication, A SSM can be used per CPU
2) MSM: Media Security Module. According to the box generation [MSM or MSM-RM (Rack Mounted)] and the topology, a MSM can
protect a GD (or GD + GA) or an INTIPA/B (or two INTPA/B)
3) Deny Of Service
4) This solution does not require a MSM to protect the GD

IP Enhancement
IP Touch Security - NGP Security
A NGP board always controls the authenticity of the binary even if the security
mode is Bypass(1)
The binaries are signed with the Alcatel-Lucent private key. The boards use the
Alcatel-Lucent public key stored in their flash to authenticate the files. This
authentication control ensures that the binary has been produced by Alcatel-Lucent
The integrity control uses the SHA-1 HMAC method(2) for NGP boards
The new NGP hardware capabilities offer the possibility to handle the security
functionalities without any MSM(3). The security level of this solution is the
following one:
Signaling encryption: AES-CBC(4)

Voice encryption: SRTP(5) and SRTCP
Terminology
SoftMSM: NGP Media Gateway(6) running the embedded Thalès VPN client and
the Thalès SRTP library
1) In the previous release the GD authenticated its binary only if the security feature was activated (Security=Protect in the
lanpbx.cfg file). The crystal INTIP board did not support this authentication
2) The MD5 method is still used for classical Common hardware (GD-GD2)
3) A SSM is still required to protect the Call Server. The MSM are not used to protect the NGP Media Gateways
Remark:
A MSM remains mandatory to protect a PCS in order to secure the communications handled by the PCS
4) Advanced Encryption Standard (AES) cipher Algorithm - in Cipher Block Chaining (CBC) Mode
The packet authentication uses the HMAC-SHA-1 method
5) The voice encryption is realized with the AES-CM cipher [Advanced Encryption Standard (AES) cipher Algorithm - in Counter Mode
(CM)]
6) It includes both types of platforms: Common and Crystal hardware

IP enhancement
e-CS Duplication - Database consistency
Problem with previous releases features like « Free Seating »and Contact center
frequently modify the database(1)
If the Stand-by CPU is unreachable (loss of the IPLINK for maintenance reasons, IP
network failure), the consistency of the database is no more ensured
Differences between the 2 databases raise many incidents and may give issues at
the next CPU switchovers
A manual mastercopy must be done
R9.1 Solution (automatic update):
The main CPU stores the mao commands when stand-by is no more
available(2). This data is transmitted to the stand-by CPU as soon as the
inter-CPU IPLINK is back to normal in order to avoid a mastercopy
1) Each time a user is logging on or off, the database is modified
2) The second CPU has at least once to be connected and initialized as stand-by CPU to activate the feature

IP enhancement
e-CS Duplication - Database consistency (Cont)
Only CS-2, Appliance Server and Blade server are compatible with this feature(1)
The CPU main IPLINK is in charge of the MAO commands storage
Number of stored MAO commands

255 maximum from R9.1 Technical Release
The previous limit is removed from i1.605.14e
All MAO commands are stored in CPU RAM instead of a buffer
If the Stand-by CPU is still unavailable, the main CPU IPLINK ends the storage
of the MAO commands after a timer (max 2 hours) a MASTERCOPY will be
required !
Configuration
/IP/Duplication parameters
Updates storage time limit: 120(2)
If the Stand-by CPU is available before the main IPLINK deletes stored MAO
commands, the main IPLINK forwards the MAO commands to the Stand-by
IPLINK in order to update the Stand-by CPUs database
1) This feature is not available on Crystal and CS-1 CPUs
2) Value in minutes. If this timer is equal to 0, there is not any MAO command storage
Telephonic features handled

Logon/logoff CCD agent
Modification of sets data (secret code, language..)
Modification of digital sets data
In and Out of service
Modification of users name
Interphony
Modification of Directory keys
Modification of keys
Modification of cordless sets parameters
Modification of DATA parameters
Automatic sets recognition
RISO
HOTEL
Flat Base Console
Attendant
Attendant groups
CDT routing
Entity
Features not handled

Management by attendant
Management by X25

IP enhancement
MAO commands are forwarded before the telephonic updates

(IN SERVICE, OUT OF SERVICE, IN COMMUNICATION)
During this update, the main database can be modified
Thus, the Free-Seating is allowed
Then, the main IPLINK stops storing MAO commands
Information about the storage of MAO commands is saved in the log file of the
main IPLINK (/var/log/iplink.log)

IP enhancement
The file iplink.log provides some information about the storage of MAO messages
On main CPU
(1)xa000000> more iplink.log
(29/09/09 09:29:41) DUPLI: local CPU connected to the reference media gateway
(29/09/09 11:05:49) DlLink: Save MAO msg because Sdby CPU is not available
(29/09/09 11:40:22) DUPLI: local CPU connected to the reference media gateway
(29/09/09 11:47:23) DUPLI: MAO is ON on the remote CPU
(29/09/09 11:47:23) DlLink: Ready to send 2 MAO msg saved when standby CPU was not available
(29/09/09 11:47:23) DUPLI: Database updated on the remote CPU
(29/09/09 11:52:35) DUPLI: MAO is ON on the remote CPU
On stand by CPU
(29/09/09 11:40:38) MAIN: iplink killed by signal 15
(29/09/09 11:47:37) DUPLI: MAO is ON on the local CPU
(29/09/09 11:47:37) DUPLI: expecting 2 MAO msg
(29/09/09 11:47:38) DUPLI: Database updated on the local CPU
(29/09/09 11:47:44) SOCKET: socket is closed
(29/09/09 11:47:44) SOCKET: socket is suspended
(29/09/09 11:47:44) MAIN: iplink killed by signal 15
(29/09/09 11:52:35) DUPLI: MAO is ON on the local CPU
The maohist command allow also to check if the mao information are taken into
account by the CPU updated
Save MAO msg because Sdby CPU is not available occurs on main CPU only. The IP link between both CPU is broken. The database
on main CPU has been modified and the first MAO message has been stored by main IPLINK waiting for standby CPU comes back.
MAO is ON on the remote CPU occurs on main CPU only. Main IPLINK received the MAO_IS_ON message from standby IPLINK. That
means that standby CPU is ready to process MAO messages stored by main CPU.
MAO is ON on the local CPU occurs on standby CPU only. Standby IPLINK received the MAO_IS_ON_ACK message from main IPLINK.
That means that main CPU knows that standby CPU is ready to process MAO messages. So, main IPLINK starts sending stored MAO
messages.
Stop saving MAO msg after X minutes occurs on main CPU only. Main IPLINK stopped storing MAO messages after X minutes
whereas standby CPU was not available. Stored MAO messages are deleted. Standby CPU MUST be updated using the master copy
command.

IP enhancement
New incidents 439 and 440
29/09/09 12:41:05 000001M|019/01/-/---|=0:0440=IP_LINK Incident: The

standby CPU requests a mastercopy
It happens on main CPU when main IPLINK deletes stored MAO messages. It
may happen when the time limit for storage is reached, or in a double
main case when both of the CPUs have stored MAO commands
When this incident is raised, the OXE system administrator MUST proceed to
a mastercopy on standby CPU
29/09/09 12:49:02 000001M|019/01/-/---|=0:0439=IP_LINK Incident: The local

CPU requests a mastercopy
When both CPUs are main after a network failure, they decide which one
must reset. If the CPU that resets, has stored MAO messages, this incident is
raised
So, a mastercopy is requested

IP enhancement
ABC-F IP Trunk group
Status on previous release
On an ABC-F IP trunk group all the calls were released in case of Call Server
switchover
R9.1 Improvement
Ongoing communications are maintained
In set-up phase:
Communications are released except the incoming external communications which
are routed to the relevant Entity (e.g. an attendant)
Note:
As in Release 9.0, the IP ABC-F communications can not be encrypted

IP enhancement
Telnet on IP boards
From R9.0, the Telnet service has been disabled by default on boards but can
be activated. Here follows the activation methods available from R9.1
Crystal hardware boards
For INT-IP/INT-IP2 boards

Via V24, activate the Telnet server (configuration menu)
For INT-IP3 boards

Via V24 or from the CS with the command cpl_online
In the mgconfig, activate the Telnet server (always opened, or opened with a timer)
Common hardware boards
GD/GA and GD-2/GA-2

The Telnet server has to be activated via the ippstat tool (on the CS)(1)
GD-2/GA-2 et GD-3/GA-3
Via V24 or from the CS with the commande cpl_online
In the mgconfig, activate the Telnet server (always opened, or opened with a timer)
1) In this case a mandatory signaling link has to be operational
Remark:
The telnet_al command has to be used for all the boards in order to initialize properly the Telnet session

Applications
OmniVista 4760 & SIP DM
OmniVista 4760 R5.1.1
Software download optimization
OmniVista 4760 Scheduler enhancement

Possibility to schedule the software download of a large set of CS and PCS during a time
range (for example during the night)
Status of the PCS software download

Intermediate status of the OXE CS / PCS remote download is provided
OXE improvement:
The master CPU provides to the OmniVista 4760 the remote loading status for each CS/PCS CPU, and
not anymore a global status at the end of loading of all CPUs
SIP DMS (Device Management Server) R1.2
New terminals taken in account:

IP Touch 4008 & 4018 working in SIP nominal mode
My IC SIP SoftPhone

ABC-F Networking
Network compatibilities
Minimum required release: R8.0
The cohabitation with release R5.1 < to < 7.x is only allowed during migration
process
Refer to the Installation procedure for version to check restrictions

Direct RTP
H323 inter-node protocol
Fax T38 inter Media Gateways
Audit Broadcast
Hardware restrictions

No possible cohabitation with Ux releases


ENTP0400P13TEUS

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

ENTP0400P13TEUS

Încărcat de

Drepturi de autor:

Formate disponibile

Alcatel-Lucent OmniPCX Enterprise

All Rights Reserved © 2009, Alcatel-Lucent 1

To describe the Release 9.1 new features

Alcatel-Lucent OmniPCX Enterprise  R9.1 Newness

The NGP project introduces the following boards

Actis 14.2 (minimum) is required to order NGP boards(4)

All Rights Reserved © 2009, Alcatel-Lucent 2

2) INT-IP3 and GD3/GA3 boards are only available from R9.1

Alcatel-Lucent OmniPCX Enterprise  R9.1 Newness

CS-2 board has the following characteristics:

CPU CS-2: dual Ethernet(2)

All Rights Reserved © 2009, Alcatel-Lucent 3

Alcatel-Lucent OmniPCX Enterprise  R9.1 Newness

SEPLOS Keep alive mechanism

The purpose of this feature is to create a supervision of the device in order

History Info (RFC 4244)

SEPLOS Call Server Information display

All Rights Reserved © 2009, Alcatel-Lucent 4

Alcatel-Lucent OmniPCX Enterprise  R9.1 Newness

SEPLOS Reason header (RFC 3326)

SIP: PRACK with SDP

SIP: Call Admission Control for FAX calls

SEPLOS: SIP/CSTA divert service

All Rights Reserved © 2009, Alcatel-Lucent 5

Alcatel-Lucent OmniPCX Enterprise  R9.1 Newness

Mapping between ABC F/ISDN causes and SIP responses

It is now possible to manage(1) the codes sent by the CS in case of problem in

SIP: Contact Header  User part

SIP: Method update for early media (RFC 3311)

The UPDATE method allows to provide updated session information before to

All Rights Reserved © 2009, Alcatel-Lucent 6

1) In the previous releases, this message mapping was hard coded

Alcatel-Lucent OmniPCX Enterprise  R9.1 Newness

SIP - tool: Active calls display

The sipdump tool has been enhanced

SIP backup with PCS

SIP Stand-Alone with 4008/18 extensions

Possibility to use the SIP protocol in native mode instead of NOE

All Rights Reserved © 2009, Alcatel-Lucent 7

Alcatel-Lucent OmniPCX Enterprise  R9.1 Newness

All Rights Reserved © 2009, Alcatel-Lucent 8

The OmniTouch 4135 IP is declared as a SIP device

Alcatel-Lucent OmniPCX Enterprise  R9.1 Newness

As of the patch i1.605.15 (TR+2), it is possible to encrypt the DECT

From now, the encryption is also availabale

3 available security levels (modes)

Identity (default mode):

All Rights Reserved © 2009, Alcatel-Lucent 9

1) IBS-NG: Intelligent Base Station  New Generation

Alcatel-Lucent OmniPCX Enterprise  R9.1 Newness

Authentication (based on Identity mode):

At each signaling exchange (registration, call request, localization, un-registration), the

Encryption (based on Authentication mode):

The DCK key is also used to encrypt the communication

This key is calculated at the beginning of each communication

All Rights Reserved © 2009, Alcatel-Lucent 10

1) AC: Authentication Code

2) UAK: User Authentication Key

3) DCK: Derived Cipher Key

Alcatel-Lucent OmniPCX Enterprise  R9.1 Newness

Creation of a new type of RSI

Increase of the reroute requests

Up to release 9.0 the maximum number of reroute request is 3

As of Release 9.1 a maximum of 1000 RE-ROUTE-REQUEST is possible

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Actis 14.2 (minimum) is required to order NGP boards(4)

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

SEPLOS: SIP/CSTA divert service

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

SIP: Contact Header User part

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

The sipdump tool has been enhanced

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

As of the patch i1.605.15 (TR+2), it is possible to encrypt the DECT

1) IBS-NG: Intelligent Base Station New Generation

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Increase of the reroute requests

As of Release 9.1 a maximum of 1000 RE-ROUTE-REQUEST is possible

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

maohist logs size is increased from 1000 to 9999 records

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

With the previous releases, a backtrace is generated when the execution of a

Currently btracer and blackbox store logs in /tmpd directory

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

The tool excvisu is used to read the exceptions stored by btracer

1) infocollect use process

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness

Alcatel-Lucent OmniPCX Enterprise R9.1 Newness