NGINX-PLUS-1.5.3 OpenTouchR1.3 IWR Ed02

Alcatel-Lucent Application Partner Program
Inter-Working Report
Partner: NGINX
Application type: Reverse Proxy
Application name: NGINX Plus 1.5.3
Alcatel-Lucent Platform: OpenTouch
The product and release listed have been tested with the Alcatel-Lucent Communication Platform and the release specified
hereinafter. The tests concern only the inter-working between the AAPP members product and the Alcatel-Lucent
Communication Platform. The inter-working report is valid until the AAPP members product issues a new major release of
such product (incorporating new features or functionality), or until Alcatel-Lucent issues a new major release of such
Alcatel-Lucent product (incorporating new features or functionalities), whichever first occurs.
ALCATEL-LUCENT MAKES NO REPRESENTATIONS, WARRANTIES OR CONDITIONS WITH RESPECT TO THE APPLICATION
PARTNER PRODUCT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, ALCATEL-LUCENT HEREBY EXPRESSLY
DISCLAIMS ANY AND ALL REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY NATURE WHATSOEVER AS TO THE
AAPP MEMBERS PRODUCT INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON
INFRINGEMENT OR FITNESS FOR A PARTICULAR PURPOSE AND ALCATEL-LUCENT FURTHER SHALL HAVE NO LIABILITY
TO AAPP MEMBER OR ANY OTHER PARTY ARISING FROM OR RELATED IN ANY MANNER TO THIS CERTIFICATE.
Alcatel-Lucent Application Partner Program Inter-working report

Copyright 2014 Alcatel-Lucent, All rights reserved
- Edition 2 - page 1/40
Certification overview
Date of certification
April 2014
Alcatel-Lucents representative
Florian Residori
Claire Dechrist
AAPP member representative

Alcatel-Lucent Communication
Platform
Alcatel-Lucent Communication
Platform Release
AAPP member application version
Application Category
Author(s):
Reviewer(s):
OpenTouch BE/MS
OT 1.3 (1.3.000.042)
NGINX plus 1.5.3
Gateway
Collaboration & UC
Security
Florian Residori, Claire Dechrist

Lienhart Denis, Himmi Rachid, Frank Gadot
Revision History
Edition 1: creation of the document November 2013
Edition 2: Minor writing correction April 2014
Test results
Passed
Refused
Postponed
Passed with restrictions
Refer to the section 4 for a summary of the test results.
IWR validity extension

None

AAPP Member Contact Information

Contact name:
Andrew Alexeev
Title:
Business Development
Address:
Zip Code:
State:
City:
600 Montgomery Street

43rd floor
94111
CA
San Fransisco
Country:
USA
Phone:
Fax:
Mobile Phone:
Web site:
Email address:
http://nginx.com
Andrew@nginx.com

TABLE OF CONTENTS
1 INTRODUCTION ........................................................................................................................................ 6
1.1 GLOSSARY .................................................................................................................................................. 7
2 VALIDITY OF THE INTERWORKING REPORT ................................................................................. 8
3 LIMITS OF TECHNICAL SUPPORT ....................................................................................................... 9
3.1 CASE OF ADDITIONAL THIRD PARTY APPLICATIONS ...................................................................................... 9
4 SUMMARY OF TEST RESULTS ............................................................................................................. 10
4.1 SUMMARY OF THE MAIN FEATURES TESTED................................................................................................. 10
4.2 SUMMARY OF PROBLEMS ........................................................................................................................... 11
4.3 SUMMARY OF LIMITATIONS........................................................................................................................ 11
4.4 NOTES, REMARKS ..................................................................................................................................... 11
5 APPLICATION INFORMATION ........................................................................................................... 12
6 TEST ENVIRONMENT ............................................................................................................................. 14
6.1 TESTS PERFORMED ................................................................................................................................... 14
6.2 GENERAL ARCHITECTURE .......................................................................................................................... 14
6.3 HARDWARE CONFIGURATION................................................................................................................... 15
6.4 SOFTWARE CONFIGURATION...................................................................................................................... 15
6.4.1 Alcatel-Lucent Communication Platform OT ............................................................................. 15
6.4.2 Partner Application ....................................................................................................................... 15
7 TEST RESULT TEMPLATE ...................................................................................................................... 16
8 TEST RESULTS ......................................................................................................................................... 17
8.1 CLIENT INITIALIZATION AND AUTHENTICATION .......................................................................................... 17
8.2 OUTGOING CALLS ..................................................................................................................................... 18
8.3 INCOMING CALLS ...................................................................................................................................... 19
8.4 FEATURES DURING CONVERSATION ............................................................................................................ 20
8.5 WEB SERVICES ......................................................................................................................................... 22
8.6 MYTEAMWORK SERVICES (ONLY FOR MYIC PC) ......................................................................................... 23
8.7 VIDEO ...................................................................................................................................................... 24
9 APPENDIX A : AAPP MEMBERS APPLICATION DESCRIPTION .............................................. 26
10 APPENDIX B: CONFIGURATION REQUIREMENTS OF THE AAPP MEMBERS
APPLICATION .............................................................................................................................................. 27
10.1 NGINX CERTIFICATE FOR SSL ................................................................................................................. 27
10.2 UPDATE CONFIGURATION FILES ............................................................................................................... 27
10.3 FIREWALL CONFIGURATION ..................................................................................................................... 29
11 APPENDIX C: ALCATEL-LUCENT COMMUNICATION PLATFORM: CONFIGURATION
REQUIREMENTS .......................................................................................................................................... 30
11.1 OT REVERSE PROXY CONFIGURATION ...................................................................................................... 30
11.2 OT SBC CONFIGURATION ....................................................................................................................... 31
11.3 MYIC PC SIP CLIENT CONFIGURATION ................................................................................................... 32
12 APPENDIX D: AAPP MEMBERS ESCALATION PROCESS ........................................................ 34
13 APPENDIX E: AAPP PROGRAM .......................................................................................................... 35
13.1 ALCATEL-LUCENT APPLICATION PARTNER PROGRAM (AAPP) ............................................................. 35
13.2 ALCATEL-LUCENT.COM ......................................................................................................................... 36
14 APPENDIX F: AAPP ESCALATION PROCESS .................................................................................. 37

14.1 INTRODUCTION ...................................................................................................................................... 37
14.2 ESCALATION IN CASE OF A VALID INTER-WORKING REPORT ................................................................. 38
14.3 ESCALATION IN ALL OTHER CASES ......................................................................................................... 39
14.4 TECHNICAL SUPPORT ACCESS ................................................................................................................ 40

1 Introduction
This document is the result of the certification tests performed between the AAPP members
application and Alcatel-Lucents platform.
It certifies proper inter-working with the AAPP members application.
Information contained in this document is believed to be accurate and reliable at the time of printing.
However, due to ongoing product improvements and revisions, Alcatel-Lucent cannot guarantee
accuracy of printed material after the date of certification nor can it accept responsibility for errors or
omissions.
Updates to this document can be viewed on:
-
the Technical Support page of the Enterprise Business Portal

(https://businessportal.alcatel-lucent.com) in the Application Partner Interworking Reports
corner (restricted to Business Partners)
the Application Partner portal (https://applicationpartner.alcatel-lucent.com) with free

access.

1.1 Glossary
API
Application Programming Interface
AAA
Authentication, Authorization and Accounting
CA
Certificate Authority. It is part of a PKI. It issues and verifies digital certificates.
DMS
Device Management Server
CSR
Certificate Signing Request. This is file generated by a server to get signed by a
CA which will deliver a signed certificate.
DN
Distinguished Name
DNS
Domain Name System. Server that translates FQDN into IP addresses.
EVS
Event server
FQDN
Fully Qualified Domain Name. A domain name that specifies its exact location in
the tree hierarchy of the Domain Name System (DNS). It specifies all domain levels,
including the top-level domain, relative to the root domain. Ex: myhost.mydomain.com
IM
Instant Messaging
MyIC
My Instant Communicator
LDAP
Lightweight Directory Access Protocol. This is a directory that can be used as an
authentication server.
OTES
Opentouch Edge Server
PLMN
Public Land Mobile Network
PKI
Public Key Infrastructure. It provides digital certificates that can identify an
individual or an organization and directory services that can store and, when necessary,
revoke the certificates.
RADIUS Remote Authentication Dial In User Service. This is an Authentication Server.
RP
Reverse Proxy
SBC
Session Border Controller
SSL TLS
Transport Layer Security (formerly Secure Socket Layer). It allows
client/server applications to communicate across a network in a way designed to prevent
eavesdropping, tampering, and message forgery. TLS provides endpoint authentication and
communications confidentiality over the Internet using cryptography.

2 Validity of the InterWorking Report

This InterWorking report specifies the products and releases which have been certified.
This inter-working report is valid unless specified until the AAPP member issues a new major
release of such product (incorporating new features or functionalities), or until Alcatel-Lucent
issues a new major release of such Alcatel-Lucent product (incorporating new features or
functionalities), whichever first occurs.
A new release is identified as following:
a Major Release is any x. enumerated release. Example Product 1.0 is a major product
release.
a Minor Release is any x.y enumerated release. Example Product 1.1 is a minor product
release
The validity of the InterWorking report can be extended to upper major releases, if for example the
interface didnt evolve, or to other products of the same family range. Please refer to the IWR
validity extension chapter at the beginning of the report.
Note: The InterWorking report becomes automatically obsolete when the mentioned product
releases are end of life.

3 Limits of Technical support

Technical support will be provided only in case of a valid InterWorking Report (see chapter 2
Validity of the InterWorking Report) and in the scope of the features which have been certified.
That scope is defined by the InterWorking report via the tests cases which have been performed,
the conditions and the perimeter of the testing as well as the observed limitations. All this being
documented in the IWR. The certification does not verify the functional achievement of the AAPP
members application as well as it does not cover load capacity checks, race conditions and
generally speaking any real customer's site conditions.
Any possible issue will require first to be addressed and analyzed by the AAPP member before being
escalated to Alcatel-Lucent.
For any request outside the scope of this IWR, Alcatel-Lucent offers the On Demand Diagnostic
service where assistance will be provided against payment.
For more details, please refer to Appendix F AAPP Escalation Process.
3.1 Case of additional Third party applications

In case at a customer site an additional third party application NOT provided by Alcatel-Lucent is
included in the solution between the certified Alcatel-Lucent and AAPP member products such as a
Session Border Controller or a firewall for example, Alcatel-Lucent will consider that situation as to
that where no IWR exists. Alcatel-Lucent will handle this situation accordingly (for more details,
please refer to Appendix F AAPP Escalation Process).

4 Summary of test results

4.1 Summary of the main features tested
Note: only the features, which interact with the ALU solution, are mentioned here.
Both clients MyIC PC SIP and MyIC Mobile Android have been tested.
Feature
N/A
OK
OK
But
NOK
Application initialization and authentication

Start and stop phase
Authentication on RP using LDAP
Outgoing calls
Local call
External call
2nd outgoing call
Incoming calls
Local call
External call
2nd incoming call
Features during conversation
Hold / Resume
Back and forth
Push/Get call (Transfer to another users device)
Transfer
Web Services
Event notification
Directory search
Routing profile modification
My teamwork services
IM
Whiteboard
Video Calls
Video call MyIC PC SIP/MyIC Phone
Video call MyIC PC SIP/ MyIC PC SIP

4.2 Summary of problems

OT problems:
o None
NGINX problems:
o None
4.3 Summary of limitations

OT limitations:
o Callers picture is not displayed on remote worker side
NGINX limitations:
o External LDAP authentication is not available on Nginx solution.
4.4 Notes, remarks

It is possible to do the tests using encryption of signaling (SIP-TLS) and audio (SRTP). Using
encrypted or unencrypted signaling and media has no impact on reverse proxy.
Client authentication by certificate is not available on MyIC PC and MyIC Mobile Android.

5 Application information
Application commercial name:
NGINX
Application version:
Nginx plus 1.5.3 (nginx-plus-1.5.3-1.ngx.el6.x86_64.rpm)
Interface type:
through configuration files
Interface version (if relevant):

Brief application description:
NGINX is a lightweight, high performance web server/reverse proxy. It runs on UNIX, GNU/Linux,
BSD variants, Mac OS X, Solaris, and Microsoft Windows.
Nginx is available in three versions, for technology professionals through to businesses and
enterprises. For more information: http://nginx.com/products/
NGINX Plus product is built on the open source NGINX product and includes advanced features to
support mission critical production environments. In contrast to legacy hardware-based networking
appliances, NGINX Plus originates from the world of application software and provides an
innovative new set of features to bridge users and applications.
NGINX Plus frees applications from the heavy lifting of HTTP by managing all of the complexities of
application request routing, application security, content delivery and acceleration without incurring
unnecessary costs in time or capital.
Advanced Features of NGINX Plus Include:
Application Health Checking

Commercial-Grade Activity Monitoring
Advanced Load Balancing
Dynamic On-The-Fly Reconfiguration
Extended Logging Capabilities
High Availability Setup
Adaptive Media Streaming
Services Available With NGINX Plus Include:
Configuration and Tuning

Performance Optimization
Technical Account Management

Figure 1 Global Principle
The following diagram describes a typical redirection policy implemented on the Nginx RP for the
Alcatel-Lucent solution.
Figure 2 Redirection policy

6 Test environment
6.1 Tests performed
This document describes the tests of homeworker scenario using NGINX plus configured as a
reverse proxy and MyIC PC/MyIC Mobile Android applications for OT users (also called
conversation users) in the context of OT solution release 1.3.000.42.
MyIC clients use an internet connection on the WAN. Remote user is connected to the enterprise
network through the RP in HTTPS and to a SBC in SIP without media encryption.
OT users have several devices: at least a MyIC PC SIP or MyIC Mobile Android and a MyICPhone
desktop phone (8082).
The way to configure OT server, MyIC PC SIP, Android clients and NGINX RP is described in the
Appendix. In these tests, Nginx is running in a linux vm.
6.2 General Architecture
Figure 3 Test architecture

MyIC clients send web requests to OT server through NGINX Reverse Proxy which forwards the
requests to the OT server located in the trusted zone.
Users can be authenticated by the RP using OT authentication web service.

NGINX Plus Reverse Proxy Deployment:

Public fqdn: https://opentouch5.aapp-etesting.com
Public IP address: 83.206.62.69
Internal fqdn: rpnginx.etesting.lab
Internal IP address: 10.1.2.37
Operating system: Linux CentOS 6.4
Alcatel-Lucent Communication Platform:
IP address: 10.1.2.85
fqdn: ice2.etesting.lab
DNS: 10.1.2.15
6.3 Hardware configuration

NGINX plus
HP Proliant DL380p Gen8
Alcatel-Lucent OT:
HP Proliant DL120 G6
6.4 Software configuration

6.4.1 Alcatel-Lucent Communication Platform OT
o
o
o
OTBE version 1.3.000.042

MyIC PC SIP client version 5.2.009.002
MyIC Mobile Android client version 4.3.2
6.4.2 Partner Application

Nginx plus 1.5.3 (nginx-plus-1.5.3-1.ngx.el6.x86_64.rpm)

7 Test Result Template

The results are presented as indicated in the example below:
Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Test case 1
Action
Expected result
Test case 2
Action
Expected result
Test case 3
Action
Expected result
Test case 4
Action
Expected result
The application waits

for PBX timer or
phone set hangs up
Relevant only if the
CTI interface is a
direct CSTA link
No indication, no error
message
Test Case Id: a feature testing may comprise multiple steps depending on its complexity. Each
step has to be completed successfully in order to conform to the test.
Test Case: describes the test case with the detail of the main steps to be executed the and the
expected result
N/A: when checked, means the test case is not applicable in the scope of the application
OK: when checked, means the test case performs as expected
NOK: when checked, means the test case has failed. In that case, describe in the field Comment
the reason for the failure and the reference number of the issue either on Alcatel-Lucent side or on
Application Partner side
Comment: to be filled in with any relevant comment. Mandatory in case a test has failed especially
the reference number of the issue.

8 Test Results
In all following sections, the SIP client under test is an external user; It has been declared on the
public side of the RP. For this remote user, MyIC PC SIP/Android has been configured to connect
to OT via Nginx reverse proxy.
8.1 Client initialization and authentication

These tests cover MyIC PC SIP clients initialization and authentication.
On NGINX proxy, authentication, if activated, will send a request to OT authentication WS.
Test
Case
Id
1
Test Case
N/A
Check OT login/password verification

Go through MyIC application menus and verify thaht
the application is responding correctly.
NOK
Comment
Application initialization
MyIC PC SIP basic connection to the OT
through reverse proxy
OK
Authentication
certificate must
disabled on the
(not supported
MyIC
PC
Android)
MyIC basic connection to the OT through

reverse proxy using LDAP
Check credentials validation
User logout/login
User logout/login without exiting the
application.
Logout from MyIC client (without exiting the

application)
Check that user is disconnected
Log again MyIC user
Check that user reconnects correctly
3
A
Application exit
Stop MyIC client.
MyIC user is unregistered.

via
be
RP
on
and
8.2 Outgoing calls
Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Internal outgoing call

Call from remote User A (MyIC PC/Android) to
User B
A
Check that the call is established
2
External outgoing call

External call from remote User A (MyIC
PC/Android) to user B
Check that the call is correctly established
Second outgoing call

User B
User C
Check that the 2nd call is correctly established

8.3 Incoming calls
Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Internal incoming call

Internal call from User B to User A (MyIC PC
SIP/Android)
Check that the call is correctly presented and

established
External incoming call
External call from User B to User A (MyIC PC
SIP/Android)
Check that the call is correctly presented and is

correctly established
Second incoming call
Call from User B to User A (MyIC PC
SIP/Android)
Call from User C to User A (MyIC PC
SIP/Android)
Check that the 2nd call is correctly presented and is
correctly established

8.4 Features during conversation

Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Hold/Resume
Call from User A (MyIC PC SIP/Android) to
User B and establish the call.
Put User B on hold.
Verify the music on hold is played

Verify you can resume the call by clicking on it
again.
Back and forth

User B. Establish the call.
User C
Establish the call.
User B must be put on hold.

Check that you can retrieve User B.
User C must be on hold.
Check that you can retrieve User C.
User B must be on hold.
Transfer to another users device
(Push call/Get call)
Internal call from User B to User A (MyIC PC
SIP/Android), establish the communication,
then MyIC user transfers the call to another of
his device (MyIC Phone deskphone for
example)
Check that the call is correctly presented to MyIC

Phone and can be correctly established
From MyIC PC SIP/Android, get the current
call again.
Check that the call is correctly presented to MyIC
PC/Android and can be correctly established

Test
Case
Id
4
Test Case
N/A
OK
NOK
Comment
Transfer to another user

User B. Establish the call.
User C
Establish the call.
Transfer User C to user B
User picture
Call from User B to User A (MyIC PC

SIP/Android)
Callers picture is not

presented on remote
side
Check that the callers picture is correctly presented

8.5 Web services
Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Event notifications
Missed call event
From another user or station, call MyIC PC

SIP/Android user but do not answer.
Check that the event logs show a missed call.
Check that it is propagated to other users devices.
Voice mail event
User B (MyIC Phone) calls User A (MyIC PC
SIP/Android) and leaves a message.
User A can see a voice message in his events logs.

User A can listen to the voice message, and delete
it.
The voice mail event must disappear.
Directory Search (dial by name)

User A (MyIC PC/Android) calls an OT user
using dial by name
Verify that dial by name feature is working.

Check that the call can be established
Routing profile modification
On User A (MyIC PC/Android), change the

routing profile of the remote user
Check that that the routing modification is working.

8.6 Myteamwork services (only for MyIC PC)

Application sharing and file transfer will not be tested here as they do not use HTTP protocol.
Test
Case
Id
Test Case
IM
Check IM is possible between remote worker

and an internal user
Whiteboard
Check whiteboard session is possible

between remote worker and an internal user

N/A
OK
NOK
Comment
8.7 Video
Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Incoming call to a remote MyIC PC

Audio call from internal User A (MyIC PC SIP)
to remote User B (MyIC PC SIP), add video.
A
Check that the call in audio and video is correctly
presented and established
Video call from internal User A (MyIC PC SIP)
to remote User B (MyIC PC SIP).
B

Audio call from internal User A (MyIC Phone)
to remote User B (MyIC PC SIP), add video.
C
Video call from internal User A (MyIC Phone)
to remote User B (MyIC PC SIP).
D

Audio call from internal User A (OTC Ipad) to
remote User B (MyIC PC SIP), add video.
Video call from internal User A (OTC Ipad) to
remote User B (MyIC PC SIP).
Escalate an audio call

to a video call is not
available in OTC Ipad

2
Outgoing call from a remote MyIC PC

Audio call from remote User A (MyIC PC SIP)
to internal User B (MyIC PC SIP), add video.

Video call from remote User A (MyIC PC SIP)
to internal User B (MyIC PC SIP).
to internal User B (MyIC Phone), add video.
C
Test
Case
Id
Test Case
N/A
OK
NOK
Comment

to internal User B (MyIC Phone).
to internal User B (OTC Ipad), add video.
to internal User B (OTC Ipad).


9 Appendix A : AAPP members Application

description
Protocols and performance
HTTP/1.1, HTTPS, SPDY, WebSocket
IMAP, POP3, SMTP with an external HTTP based authentication
IPv4 and IPv6
1 million concurrent connections
10,000+ virtual servers multi-tenancy
Connection multiplexing pools for low latency communications
Request Routing
HTTP, FastCGI, SCGI, uwsgi, memcached
Exact, prefix, regex-based URL/URI path switching
Reverse proxy and load balancer with round-robin,least-connected, ip-hash
Session persistence
Application backend health monitoring
SSL Termination
TLSv1.1/TLSv1.2/SSL/SNI/PFS/PCI-DSS
OCSP Stapling
Security
Bandwidth, connection and request policing
Protocol isolation and request filtering
Header manipulation
Edge Cache and Origin Server
Content offload and caching
On-the-fly content compression and optimization
HTTP video streaming with MP4/FLV/HDS/HLS
Configuration and Management
Live reconfiguration of server pools to change
upstream settings on the fly
Activity monitoring
Geo-IP configuration
Logging to syslog
High Availability
Active-Standby (NGINX AMI on EC2 only)
Live binary upgrades to eliminate downtime
Graceful restart with non-stop request processing
Supported Operating Systems and Architectures
Ubuntu, Debian, CentOS, Amazon Linux, Red Hat,
SuSE, Solaris, SmartOS, *BSD
x86_64, i386, ARM

10 Appendix B: Configuration requirements of the

AAPP members application
After having installed nginx on your server (download the rpm, then yum install nginx on CentOS),
following steps are needed before starting the tests:
10.1 Nginx certificate for SSL

For this IWR, the Root CA of etesting lab PKI has been used to sign OT and RP certificates.
The location for NGINX certificate and its private key is configurable in the config file:
ssl_certificate
/etc/nginx/cert/cert.pem;
ssl_certificate_key /etc/nginx/key/cert.key;
10.2 Update configuration files

Configuration files are located in /etc/nginx/ and /etc/nginx/conf.d/
You can see below the configuration files used for the tests:
nginx is configured as reverse proxy, using hostname opentouch5.aapp-etesting.com
it listens to ports 443 and 8016
chunk mode must be enabled (should be by default)
proxy buffering has been disabled
To start/stop NGINX process:
/etc/init.d/nginx start/stop/restart
nginx.conf
user nginx;
worker_processes auto;
error_log /var/log/nginx/error.log warn;
pid
/var/run/nginx.pid;
events {
worker_connections 1024;
}
http {
include
/etc/nginx/mime.types;
default_type application/octet-stream;
log_format main '$remote_addr - $remote_user [$time_local] "$request" '
'$status $body_bytes_sent "$http_referer" '
'"$http_user_agent" "$http_x_forwarded_for"';
access_log /var/log/nginx/access.log main;
sendfile
on;
#tcp_nopush on;

keepalive_timeout 65;
#gzip on;
}
include /etc/nginx/conf.d/*.conf;
Default.conf
server {
listen
80 default_server;
server_name localhost;
#charset koi8-r;
#access_log /var/log/nginx/log/host.access.log main;
location / {
return 444;
root /usr/share/nginx/html;
index index.html index.htm;
}
#error_page 404
/404.html;
# redirect server error pages to the static page /50x.html

#
error_page 500 502 503 504 /50x.html;
location = /50x.html {
root /usr/share/nginx/html;
}
}
opentouch5.aapp-etesting.conf file :
server {
listen
443;
server_name opentouch5.aapp-etesting.com;
# SSL configuration
ssl
on;
ssl_certificate
ssl_session_timeout 5m;
ssl_protocols SSLv3 TLSv1;
ssl_ciphers HIGH:!aNULL:!MD5;
ssl_prefer_server_ciphers on;
# Client authentiication via Certificate
# ssl_client_certificate /etc/nginx/cert/etesting.pem;
# ssl_verify_client on;
location / {
proxy_pass https://10.1.2.85;
# /!\ Warning do not use this method !!
#proxy_redirect
https://ice2.etesting.lab/ /;
proxy_set_header Host $host;

proxy_buffering off;
chunked_transfer_encoding on;
client_body_timeout 3600;
proxy_read_timeout 900;
client_max_body_size 200M;

server {
listen
8016;
server_name opentouch5.aapp-etesting.com;
# SSL configuration
ssl
on;
ssl_certificate
ssl_session_timeout 5m;
ssl_protocols SSLv3 TLSv1;
ssl_ciphers HIGH:!aNULL:!MD5;
ssl_prefer_server_ciphers on;
# Client authentiication via Certificate
# ssl_client_certificate /etc/nginx/cert/etesting.pem;
# ssl_verify_client on;
location / {
proxy_pass https://10.1.2.85:8016;
# /!\ Warning do not use this method !!
#proxy_redirect
https://ice2.etesting.lab/ /;
proxy_set_header Host $host;

proxy_buffering off;
chunked_transfer_encoding on;
client_body_timeout 3600;
proxy_read_timeout 900;
10.3 Firewall configuration

On the server where the RP is running, configure the firewall to accept packets on port 443 and
8016:
iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 443 -j ACCEPT
iptables -I INPUT -p tcp -m state --state NEW -m tcp --dport 8016 -j ACCEPT

11 Appendix C: Alcatel-Lucent Communication

Platform: configuration requirements
11.1 OT reverse proxy configuration
Declare the reverse proxy and the mapping between public and private URLs of servers.
Select System services > Topology > Reverse proxy
OT is listening on 2 ports:
- 443 for web services
- 8016 for event management
API: enter the public FQDN of the OpenTouch server
EVS: enter the public FQDN of the OpenTouch server followed by the 8016 port
Number
ACS:
If there is no OTES (OpenTouch Edge Server), enter the public FQDN of the OpenTouch
server
If there is an OTES, enter the Cluster Name/FQDN
DMS (Device Management): enter the public FQDN of the OpenTouch server

11.2 OT SBC configuration

A SBC is needed for SIP signaling and audio management.
SBC declaration on user side (MyIC PC SIP device) :

11.3 MyIC PC SIP client configuration

During the installation process, modify Reverse proxy entry with public URL of your reverse proxy.

Create a new profile remote_worker:

12 Appendix D: AAPP members escalation

process
In order to get support from NGINX, customer will need to subscribe to either NGINX Plus
Standard or NGINX Plus Premium version. The difference in the versions is described at
http://nginx.com/products/
Subscribed customers can open service requests through the NGINX Customer Portal at
http://cs.nginx.com/

13 Appendix E: AAPP program

13.1 Alcatel-Lucent Application Partner Program (AAPP)
The Application Partner Program is designed to support companies that develop communication
applications for the enterprise market, based on Alcatel-Lucent's product family.
The program provides tools and support for developing, verifying and promoting compliant thirdparty applications that complement Alcatel-Lucent's product family. Alcatel-Lucent facilitates market
access for compliant applications.
The Alcatel-Lucent Application Partner Program (AAPP) has two main objectives:
Provide
easy
interfacing
for
Alcatel-Lucent
communication
products:
Alcatel-Lucent's communication products for the enterprise market include infrastructure
elements, platforms and software suites. To ensure easy integration, the AAPP provides a
full array of standards-based application programming interfaces and fully-documented
proprietary interfaces. Together, these enable third-party applications to benefit fully from
the potential of Alcatel-Lucent products.
Test and verify a comprehensive range of third-party applications:

to ensure proper inter-working, Alcatel-Lucent tests and verifies selected third-party
applications that complement its portfolio. Successful candidates, which are labelled
Alcatel-Lucent Compliant Application, come from every area of voice and data
communications.
The Alcatel-Lucent Application Partner Program covers a wide array of third-party

applications/products designed for voice-centric and data-centric networks in the enterprise market,
including terminals, communication applications, mobility, management, security, etc.

Web site
The Application Partner Portal is a website dedicated to the AAPP program and where the
InterWorking Reports can be consulted. Its access is free at
http://applicationpartner.alcatel-lucent.com
13.2 Alcatel-Lucent.com
You can access the Alcatel-Lucent website at this URL: http://www.Alcatel-Lucent.com/

14 Appendix F: AAPP Escalation process

14.1 Introduction
The purpose of this appendix is to define the escalation process to be applied by the Alcatel-Lucent
Business Partners when facing a problem with the solution certified in this document.
The principle is that Alcatel-Lucent Technical Support will be subject to the existence of a valid
InterWorking Report within the limits defined in the chapter Limits of the Technical support.
In case technical support is granted, Alcatel-Lucent and the Application Partner, are engaged as
following:
(*) The Application Partner Business Partner can be a Third-Party company or the Alcatel-Lucent
Business Partner itself

14.2 Escalation in case of a valid Inter-Working Report

The InterWorking Report describes the test cases which have been performed, the conditions of the
testing and the observed limitations.
This defines the scope of what has been certified.
If the issue is in the scope of the IWR, both parties, Alcatel-Lucent and the Application Partner, are
engaged:
Case 1: the responsibility can be established 100% on Alcatel-Lucent side.
In that case, the problem must be escalated by the ALU Business Partner to the Alcatel-Lucent
Support Center using the standard process: open a ticket (eService Request eSR)
Case 2: the responsibility can be established 100% on Application Partner side.
In that case, the problem must be escalated directly to the Application Partner by opening a
ticket through the Partner Hotline. In general, the process to be applied for the Application
Partner is described in the IWR.
Case 3: the responsibility can not be established.
In that case the following process applies:
The Application Partner shall be contacted first by the Business Partner (responsible for
the application, see figure in previous page) for an analysis of the problem.
The Alcatel-Lucent Business Partner will escalate the problem to the Alcatel-Lucent
Support Center only if the Application Partner has demonstrated with traces a problem
on the Alcatel-Lucent side or if the Application Partner (not the Business Partner) needs
the involvement of Alcatel-Lucent.
In that case, the Alcatel-Lucent Business Partner must provide the reference of the Case
Number on the Application Partner side. The Application Partner must provide to AlcatelLucent the results of its investigations, traces, etc, related to this Case Number.
Alcatel-Lucent reserves the right to close the case opened on his side if the investigations
made on the Application Partner side are insufficient or do no exist.
Note: Known problems or remarks mentioned in the IWR will not be taken into account.
For any issue reported by a Business Partner outside the scope of the IWR, Alcatel-Lucent
offers the On Demand Diagnostic service where Alcatel-Lucent will provide 8 hours
assistance against payment.
IMPORTANT NOTE 1: The possibility to configure the Alcatel-Lucent PBX with ACTIS quotation tool
in order to interwork with an external application is not the guarantee of the availability and the
support of the solution. The reference remains the existence of a valid InterWorking Report.
Please check the availability of the Inter-Working Report on the AAPP (URL:
https://private.applicationpartner.alcatel-lucent.com) or Enterprise Business Portal (Url: Enterprise
Business Portal) web sites.
IMPORTANT NOTE 2: Involvement of the Alcatel-Lucent Business Partner is mandatory, the access
to the Alcatel-Lucent platform (remote access, login/password) being the Business Partner
responsibility.

14.3 Escalation in all other cases

These cases can cover following situations:
1. An InterWorking Report exist but is not valid (see Chap Erreur ! Source du renvoi
introuvable. Validity of an Interworking Report)
2. The 3rd party company is referenced as AAPP participant but there is no official InterWorking
Report (no IWR published on the Enterprise Business Portal for Business Partners or on the
Alcatel-Lucent Application Partner web site) ,
3. The 3rd party company is NOT referenced as AAPP participant
In all these cases, Alcatel-Lucent offers the On Demand Diagnostic service where AlcatelLucent will provide 8 hours assistance against payment.

14.4 Technical Support access

The Alcatel-Lucent Support Center is open 24 hours a day; 7 days a week:
e-Support from the Application Partner Web site (if registered Alcatel-Lucent Application Partner):
http://applicationpartner.alcatel-lucent.com
e-Support from the Alcatel-Lucent Business Partners Web site (if registered Alcatel-Lucent Business
Partners): https://businessportal.alcatel-lucent.com click under Let us help you the eService Request
link
e-mail: Ebg_Global_Supportcenter@alcatel-lucent.com
Fax number: +33(0)3 69 20 85 85
Telephone numbers:
Alcatel-Lucent Business Partners Support Center for countries:
Country
Supported language
Toll free number
France
Belgium
French
Luxembourg
Germany
Austria
German
Switzerland
United Kingdom
Italy
Australia
Denmark
Ireland
Netherlands
+800-00200100
South Africa
Norway
English
Poland
Sweden
Czech Republic
Estonia
Finland
Greece
Slovakia
Portugal
Spain
Spanish
For other countries:

English answer:
French answer:
German answer:
Spanish answer:
+ 1 650 385 2193

+ 1 650 385 2196
+ 1 650 385 2197
+ 1 650 385 2198
END OF DOCUMENT


NGINX-PLUS-1.5.3 OpenTouchR1.3 IWR Ed02

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NGINX-PLUS-1.5.3 OpenTouchR1.3 IWR Ed02

Uploaded by

Copyright:

Available Formats

Alcatel-Lucent Application Partner Program

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 1/40

AAPP member representative

Florian Residori, Claire Dechrist

Passed with restrictions

Refer to the section 4 for a summary of the test results.

IWR validity extension

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 2/40

AAPP Member Contact Information

600 Montgomery Street

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 3/40

- Edition 2 - page 4/40

14 APPENDIX F: AAPP ESCALATION PROCESS .................................................................................. 37

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 5/40

the Technical Support page of the Enterprise Business Portal

the Application Partner portal (https://applicationpartner.alcatel-lucent.com) with free

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 6/40

Application Programming Interface

Authentication, Authorization and Accounting

Certificate Authority. It is part of a PKI. It issues and verifies digital certificates.

Device Management Server

Domain Name System. Server that translates FQDN into IP addresses.

Opentouch Edge Server

Public Land Mobile Network

RADIUS Remote Authentication Dial In User Service. This is an Authentication Server.

Session Border Controller

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 7/40

2 Validity of the InterWorking Report

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 8/40

3 Limits of Technical support

3.1 Case of additional Third party applications

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 9/40

4 Summary of test results

Application initialization and authentication

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 10/40

4.2 Summary of problems

4.3 Summary of limitations

4.4 Notes, remarks

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 11/40

Nginx plus 1.5.3 (nginx-plus-1.5.3-1.ngx.el6.x86_64.rpm)

through configuration files

Interface version (if relevant):

Application Health Checking

Services Available With NGINX Plus Include:

Configuration and Tuning

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 12/40

Figure 1 Global Principle

Figure 2 Redirection policy

Alcatel-Lucent Application Partner Program Inter-working report

- Edition 2 - page 13/40

6.2 General Architecture

Figure 3 Test architecture