Alcatel-Lucent Application Partner Program
Inter-Working Report
Partner: Microsoft / AudioCodes
Application type: Unified Messaging
Application name: Exchange 2013
Alcatel-Lucent Platform: OmniPCX Enterprise™
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 member’s product and the Alcatel-Lucent Communication
Platform. The inter-working report is valid until the AAPP member’s 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 MEMBER’S 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 3 - page 1/65
Certification overview
Date of the certification
July 2014
Alcatel-Lucent’s representative
Claire Dechristé
Florian Residori
Serge Leclercq
AAPP member representative
Alcatel-Lucent Communication
Platform
Alcatel-Lucent Communication
Platform Release
OmniPCX Enterprise
R11.0 (k1.400.25.f)
AAPP member application version
Mediant Software ESBC
6.80A.018.05
Application Category
Gateway
Voice Mail
Author(s):
Reviewer(s):
Claire Dechristé, Florian Residori
Denis Lienhart
Historic
Edition 1: Creation of the document - April 2014
Edition 2: Update on OXE software licences - July 2014
Edition 3: Minor syntax corrections - August 2014
Test results
Passed
Refused
Postponed
Passed with restrictions
Refer to the section 6 for a summary of the test results.
IWR validity extension
Extended to all Audiocodes Mediant SBC range
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 2/65
AAPP Member Contact Information
Contact name:
Title:
Serge Leclercq
Field Application Engineer
Address 1:
Address 2:
City:
State:
Zip:
Country:
104 Avenue Albert 1er – Les Passerelles
Web address:
E-mail:
http://www.AudioCodes.com
serge.leclercq@audioCodes.com
Rueil-Malmaison
France
92500
France
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 3/65
TABLE OF CONTENTS
1
2
3
Introduction ............................................................................................................................................. 5
Validity of the InterWorking Report ........................................................................................................ 6
Limits of the Technical support .............................................................................................................. 7
3.1
CASE OF ADDITIONAL THIRD PARTY APPLICATIONS ........................................................................................ 7
4 Application information ........................................................................................................................... 8
5 Tests environment ................................................................................................................................ 10
5.1
GENERAL ARCHITECTURE ............................................................................................................................. 10
5.2
HARDWARE CONFIGURATION ....................................................................................................................... 11
5.3
SOFTWARE CONFIGURATION ......................................................................................................................... 11
6 Summary of test results ....................................................................................................................... 12
6.1
SUMMARY OF THE MAIN FEATURES TESTED .................................................................................................. 12
6.2
SUMMARY OF PROBLEMS .............................................................................................................................. 13
6.3
SUMMARY OF LIMITATIONS .......................................................................................................................... 13
6.4
NOTES, REMARKS ......................................................................................................................................... 13
7 Test Result Template ........................................................................................................................... 14
8 Test Results ......................................................................................................................................... 15
8.1
CONNECTIVITY AND SET-UP .......................................................................................................................... 15
8.2
LOCAL ACCESS TO VOICE MAIL ................................................................................................................... 16
8.3
OUTLOOK VOICE ACCESS ............................................................................................................................. 17
8.4
OVERFLOW/FORWARD TO VOICE MAIL ........................................................................................................ 18
8.5
FAX CALLS ................................................................................................................................................... 23
8.6
PLAY ON PHONE FEATURE ............................................................................................................................ 24
8.7
UM AUTO ATTENDANTS .............................................................................................................................. 25
8.8
DUPLICATION AND ROBUSTNESS .................................................................................................................. 27
8.8.1
Access to Voice Mail when CPU switches over ................................................................................... 27
8.8.2
Access to Voice Mail after Exchange server is rebooted ..................................................................... 29
8.8.3
Access to Voice Mail when LAN is down between OXE and Exchange server .................................... 30
9 Appendix A : Microsoft Exchange 2013 UM configuration ................................................................... 31
10
Appendix B: Alcatel-Lucent Communication Platform: OXE configuration requirements ................ 41
10.1 OXE SOFTWARE LICENCES ........................................................................................................................... 41
10.2 SIP TRUNK ................................................................................................................................................... 42
10.2.1
Global SIP trunk parameters ............................................................................................................... 42
10.2.2
Virtual Access for SIP .......................................................................................................................... 43
10.3 SIP EXTERNAL GATEWAY ............................................................................................................................ 44
11
Appendix C: AudioCodes Mediant E-SBC configuration requirements ............................................ 48
12
Appendix D: AAPP member’s escalation process ............................................................................ 59
13
Appendix E: AAPP program ............................................................................................................. 60
13.1 ALCATEL-LUCENT APPLICATION PARTNER PROGRAM (AAPP).................................................................... 60
13.2 ALCATEL-LUCENT.COM ................................................................................................................................ 61
14
Appendix F: AAPP Escalation process ............................................................................................ 62
14.1 INTRODUCTION ............................................................................................................................................. 62
14.2 ESCALATION IN CASE OF A VALID INTER-WORKING REPORT ........................................................................ 63
14.3 ESCALATION IN ALL OTHER CASES ................................................................................................................ 64
14.4 TECHNICAL SUPPORT ACCESS ....................................................................................................................... 65
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 4/65
1 Introduction
This document is the result of the certification tests performed between the AAPP member’s application
and Alcatel-Lucent’s platform.
It certifies proper inter-working with the AAPP member’s 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.alcatellucent.com) in the Application Partner Interworking Reports corner (restricted to Business
Partners)
-
the Application Partner portal (https://applicationpartner.alcatel-lucent.com) with free access.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 5/65
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 didn’t 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.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 6/65
3 Limits of the 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 member’s 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”).
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 7/65
4 Application information
Application commercial name:
Microsoft Exchange 2013
Audiocodes Application version:
Mediant Software E-SBC 6.80A.018.05
Interface type:
SIP for voice mail (transport protocol is UDP between OXE and
E-SBC, TCP between E-SBC and Exchange 2013)
Brief application description:
The Unified Messaging server role in Exchange 2013 lets users access voice mail, e-mail, fax messages,
and calendar information that is located in their Exchange 2013 mailbox from an e-mail client such as
Microsoft Outlook or Outlook Web Access, from a mobile device that has Microsoft Exchange ActiveSync
enabled, such as a Windows Mobile® powered smartphone or a personal digital assistant (PDA), or from
a telephone.
The Unified Messaging features that has been tested with the OmniPCX Enterprise:
Call Answering Call answering includes answering an incoming call on behalf of a user, playing
their personal greeting, recording a message, and submitting it for delivery to their inbox as an email message.
Subscriber Access The subscriber access feature enables dial-in access for company users.
Company users or subscribers who are dialing into the Unified Messaging system can access
their mailbox using Outlook Voice Access. Subscribers who use Outlook Voice Access can
access the Unified Messaging system by using the telephone keypad or voice inputs. By using a
telephone, a subscriber or user can:
 Access voice mail over a telephone.
 Listen, forward, or reply to e-mail messages over a telephone.
 Listen to calendar information over a telephone.
 Access or dial contacts stored in the global address list or a personal contact list over a
telephone.
 Accept or cancel meeting requests over a telephone.
 Set a voice mail Out-of-Office message.
 Set user security preferences and personal options.
Auto Attendant An auto attendant is a set of voice prompts that gives external users access to
the Exchange 2013 Unified Messaging system. An auto attendant lets the user use either the
telephone keypad or speech inputs to navigate the menu structure, place a call to a user, or
locate a user and then place a call to that user. An auto attendant gives the administrator the
ability to:
 Create a customizable set of menus for external users.
 Define informational greetings, business hours greetings, and non-business hours
greetings.
 Define holiday schedules.
 Describe how to search the organization's directory.
 Describe how to connect to a user's extension so external callers can call a user by
specifying their extension.
 Describe how to search the organization's directory so external callers can search the
organization's directory and call a specific user.
 Enable external users to call the operator.
Fax Receiving Fax receiving is the process of submitting a fax message for delivery to the
Inbox. The fax receiving feature lets users receive fax messages in their Inbox.
Note: Customers who require a fax solution that works with Exchange 2013 will have to deploy a
fax partner solution. Fax partner solutions are available from several fax partners. The fax partner
solutions are designed to be tightly integrated with Exchange 2013 and enable UM-enabled users
to receive incoming fax messages.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 8/65
Figure 1 Global architecture
Microsoft Exchange 2013
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 9/65
5 Tests environment
5.1 General architecture
The tests are performed on the Alcatel-Lucent Etesting platform in the following environment:
Alcatel-Lucent Communication Platform:
 name: etesting4.etesting.lab
 IP addresses: CPU A: 10.1.12.1 CPU B: 10.10.10.5
 External voice mail numbers : 14991 (vm), 14992 (AA)
AudioCodes Mediant E-SBC Gateway:
 name: otsbc

domain: etesting.lab
 IP address: 10.1.2.37
Microsoft Exchange 2013:
 name: Exchange2013
 domain: etesting.lab
 IP address: 10.1.2.9
Figure 2 Tests environment
The Mediant E-SBC is used as a SIP/SIP gateway between the OmniPCX Enterprise and the Microsoft
Exchange 2013. It is needed to adapt OXE SIP implementation to Exchange SIP specificities and vice
versa. It is declared on the OmniPCX Enterprise as an external Gateway (see section 11 Appendix C:
AudioCodes Mediant E-SBC configuration requirements).
An external voice mail is declared on OXE (here 14991) using the external gateway representing the
Mediant E-SBC (see section 10 Appendix B: Alcatel-Lucent ).
On the Microsoft Exchange 2013, the Mediant E-SBC is seen as a VoIP gateway (see section 9 Appendix
A : Microsoft Exchange 2013 UM configuration)
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 10/65
5.2 Hardware configuration



Alcatel-Lucent Communication Platform: OmniPCX Enterprise in spatial redundancy
Server hosting Audiocodes Mediant E-SBC: VMWare ESXi 5.1 running on HP Proliant
DL380
Server hosting Windows server: HP VMWare ESXi 5.1 running on Proliant DL380
5.3 Software configuration




Alcatel-Lucent Communication Platform: OmniPCX Enterprise R11.0 k1 400.25.f
AudioCodes Plateform : Mediant Software E-SBC version 6.80A.018.05
Server application: Windows Server 2008 R2 Standard edition
Application platform: Microsoft Exchange 2013 version 15.0 Build 516.32
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 11/65
6 Summary of test results
6.1 Summary of the main features tested
Note: only the features, which interact with the ALU solution, are mentioned here.
Feature
N/A
OK
OK
But
NOK
Voice mail access
Voice mail access by dialing VM number
Voice mail access by using Message key
Voice mail access by using VM access prefix
Outlook voice access
Voice mail management
Email management
Calendar management
Personal contacts
Personal options
Forward to voice mail
Forward on no reply to VM
Forward on busy to VM
Voice mail access prefix
Message deposit suffix
Message deposit suffix
MWI
Message led management
Fax calls
Leave a FAX into a mailbox
Play On Phone
In Outlook client, play VM message on a local phone
Auto attendant
Auto Attendant access by dialing AA number Erreur !
Source du renvoi introuvable.
Auto attendant Speech recognition / DTMF mode
Transfer from Auto Attendant
OXE switchover
Voice Mail/Auto Attendant Service continuity during
switchover
Voice Mail consultation/suppression after a switchover
MWI indication after a switchover
Recovery
Access to Voice Mail after Exchange server is
rebooted
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 12/65
6.2 Summary of problems
OXE problems:
o Before OXE version k1.400.33: there is no service continuity during a CPU switchover, all existing
calls involving Exchange 2013 are disconnected. SR1-158492571/crqms00127928
o
For OXE release k1.400.33, if a CPU switchover occurs during a call from iptouch to Exchange
2013, iptouch screen remains blocked after releasing the communication, SR 1159316901/crqms00130868. Cf section 8.8.1 Access to Voice Mail when CPU switches over
Audiocodes problems:
o None
Exchange problems:
o None
6.3 Summary of limitations
OXE limitations:
o
There is an issue in OXE R11 k1.400.30.f (and k1.400.33), transfer from Auto Attendant will fail if
SIP authentication is set to Digest (crqms 00131490)
Fix should be in next OXE release.
Audiocodes limitations:
o DNS requests are not issued by Audiocodes Mediant for every messages when TTL value is set
to 0. This can lead to communication troubles during the time of the CPU switchover. As a
workaround, it is advised to set the parameter Proxy IP List Refresh Time to 10s on SBC to
refresh dns cache every 10s.
Exchange limitations:
o Only TCP can be used between Audiocodes Mediant and Exchange server. UDP is configured as
transport protocol between OXE and Audiocodes Mediant (refer to section 5.1, figure 2 for more
detail about SIP flows)
o
Exchange 2013 does not natively provide complete fax support, that’s why tests involving fax are
not done
6.4 Notes, remarks
Following tests have been performed using virtualized version of Audiocodes Software ESBC (VE).
o
There is no registration of Exchange voice mail on OXE
o
RTP direct is used between Exchange and OXE users (no media anchoring on SBC).
o
On Exchange side, G729 cannot be used, only G711
o
SIP Message manipulations have to be set up on E-SBC in order to make MWI and transfer from
Auto Attendant work
o
This IWR does not cover OXE users in an Opentouch environment (also named connection
users)
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 13/65
7 Test Result Template
The results are presented as indicated in the example below:
Test
Case
Id
1
2
3
4
…
Test Case
N/A
OK
NOK
Comment
Test case 1
 Action
 Expected result
Test case 2
 Action
 Expected result
The application waits
for PBX timer or
phone set hangs up
Test case 3
 Action
 Expected result
Relevant only if the
CTI interface is a
direct CSTA link
Test case 4
 Action
 Expected result
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 AAPP
member side
Comment: to be filled in with any relevant comment. Mandatory in case a test has failed especially the
reference number of the issue.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 14/65
8 Test Results
In next sections, users A, B, C are OXE users configured with Exchange voice mail access.
Test devices are iptouch 40x8 phones, but could be replaced by analog 40x9 series, SIP or DECT
phones.
8.1 Connectivity and set-up
These tests shall verify that Mediant E-SBC, Exchange server and OXE are properly connected and can
communicate together.
Test
Case
Id
Test Case
1
Exchange Voice Access
A
From User A set, call the Exchange Pilot number
(voice mail number)
N/A
OK
NOK
Comment
Check that the call is correctly established
2
Exchange automatic attendant
From User A set, call the Exchange automatic
attendant number
A
Check that the call is correctly established
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 15/65
8.2 Local Access to Voice Mail
Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Message key
A
Check User A has access to his mailbox by pressing
the message key on his business phone and
selecting Voice Mail key
2
Voice Mail Access Prefix
A
Check ‘Voice Mail Access’ prefix gives access to
Exchange voice mail system from User A set and
gives correct prompts.
3
Voice Mail access from another set on same
location/PBX node
A
Check User A has access to his Voice Mail by
dialing Exchange Pilot Number from another set
having no Exchange voice mail access
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
If the caller number is
the same as the
mailbox number,
Exchange recognizes
the user, and only
asks for the code PIN
Prefix 43 is used on
etesting4
The user Identification
is done using voice
recognition and/or
DTMF
Edition 3 - page 16/65
8.3 Outlook Voice Access
Unified Messaging servers also process and route incoming calls that are received by Outlook Voice
Access users. When a UM-enabled user dials a subscriber access number that is set on a UM dial plan to
access their Exchange 2013 mailbox, they are presented with a welcome message and a series of
telephone user interface voice prompts. The voice menu system that is presented to the user is called
Outlook Voice Access. These voice prompts help the user to navigate and interact with the Unified
Messaging system by using touchtone or speech inputs.
With Exchange 2013 Unified Messaging, UM-enabled users can access their e-mail, contacts, and
calendaring information using a standard analog, digital, or mobile telephone. When UM-enabled users
use Outlook Voice Access, they can perform the following tasks using speech recognition or DTMF:






Listen to new and saved e-mail and voice mail messages.
Forward, reply, save, and delete e-mail and voice mail messages.
Interact with their calendar.
Locate a person in the global address list or personal contacts.
Send a voice message to a person.
Change their PIN, spoken name, or greetings.
Note: Most features have been tested using DTMF, but some tests have been done using speech
recognition.
Test
Case
Id
Test Case
1
Outlook Voice Access features
A
Check User A is recognized by Exchange and has to
enter his voice mail password
N/A
OK
NOK
Comment
User A leaves a voice message to User B
B
Check the voice message is sent to User B
C
Check User A can listen to a voice message
D
Check User A can delete a voice message
E
Check User A can listen to an email
F
Check User A can delete an email
G
Check User A has access to his calendar
H
Check User A can change his PIN, spoken name
and greetings
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 17/65
8.4 Overflow/Forward to Voice Mail
Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Forward to Voice Mail
Local/Network/External incoming call to User A.
User A is forwarded to Voice Mail
A
Check that the call is forwarded to Voice Mail after
the timeout
External call done
using T2 loopback
Leave a message
Check that User A can listen to the message and
delete it
Local/Network/External incoming call to User A.
User A is forwarded to Voice Mail
B
Check that the call is forwarded to Voice Mail after
the timeout
Hang up without leaving a message
Check that User A has a missed call notification in
his outlook mailbox
1
Forward to Voice Mail on no answer
Local incoming call to User A.
User A is forwarded to Voice Mail on no answer
A
Check that the call is forwarded to Voice Mail after
the timeout
Leave a message
Check that User A can listen to the message and
delete it
2
Forward to Voice Mail on busy
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 18/65
Test
Case
Id
Test Case
N/A
OK
NOK
Comment
Local incoming call to User A
User A is forwarded to Voice Mail on busy
User B calls User A, while User A is already in
conversation
A
Check that the call is forwarded to Voice Mail
Leave a message
Check that User A can listen to the message and
delete it
3
Voice Mail forwarding rule
User A calls User B which is forwarded to User C
Phone facility category parameter “Voice Mail
Forwarding” is set to ring final set mail
A
Check that the call is forwarded to user’s C Voice
Mail
Leave a message
Check that User C can listen to the message and
delete it
User A calls User B which is forwarded to User C
Phone facility category parameter Voice Mail
Forwarding is set to “ring called set mail”
B
Check that the call is forwarded to user’s B Voice
Mail
Leave a message
Check that User B can listen to the message and
delete it
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 19/65
8.4.1.1 Force Message Deposit
Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Message deposit suffix
User A calls User B which does not answer.
User A uses message deposit suffix or icon key
to send a voice message to User B
Check that Voice Mail of User B can be reached
A
Suffix 8 on etesting4
Leave a message
Check that User B can listen to the message and
delete it
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 20/65
8.4.1.2 Message Waiting Indication
For MWI to work correctly between OXE and Exchange server it is necessary to add message
manipulation rules on E-SBC (see 11 Appendix C: AudioCodes Mediant E-SBC configuration
requirements)
Test
Case
Id
1
A
Test Case
N/A
OK
NOK
Comment
MWI led management
User B calls User A and leaves a voice message
in User A Voice Mail
Check message LED is switched ON and flashing
User A delete the voice message from B
B
Check message LED is switched OFF
C
User B calls User A and leaves a voice message
in User A Voice Mail. User A listens to the voice
message from B, but doesn’t delete it.
The led is switched off
Check message LED follows LED policy
User B calls User A and leaves a voice message
in User A Voice Mail
User C calls User A and leaves another voice
message in User A Voice Mail
D
Check message LED follows LED policy when one
message is consulted and other new messages are
not consulted by user A
When all messages
have been consulted,
the led is switched off
Check number of new messages is correctly
updated
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 21/65
8.4.1.3 OXE attendant
This test was done using 4035 attendant set
Test
Case
Id
1
Test Case
OK
NOK
Comment
OXE attendant
Check OXE attendant can leave a voice message
to User A on no answer
A
Check that User A can listen to the message and
delete it
B
N/A
Attendant needs to
press “Voice
message” dynamic
key to leave a
message
Check OXE attendant can transfer a call
(internal/external/network) to User A Voice Mail
without ringing called set.
Check that User A can listen to the message and
delete it
C
Check attendant is reached when caller presses ‘0’
from mailbox greeting or auto attendant ( for
transfer).
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
OXE attendant prefix
must be configured on
Exchange Auto
Attendant
Edition 3 - page 22/65
8.5 Fax Calls
Test
Case
Id
1
A
Test Case
N/A
OK
NOK
Comment
fax
Send a FAX from an internal FAX to User A
forwarded on the Exchange Voice access
Verify that the fax is in the user’s mailbox
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 23/65
8.6 Play on Phone Feature
Exchange 2013 Unified Messaging Play on Phone feature lets a UM-enabled user listen to a voice
message by using a telephone instead of playing it over their computer speakers or headphones.
Test
Case
Id
Test Case
1
Play on Phone
A
Using Outlook desktop client, play a message to the
business phone of the user
B
Using Outlook desktop client, play a message to
another phone
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
N/A
OK
NOK
Comment
Playing the message
to any other OXE user
is OK
Edition 3 - page 24/65
8.7 UM Auto Attendants
To enable a UM auto attendant to answer incoming calls, you must first enable and configure an UM auto
attendant for the current dial plan. A UM auto attendant is a set of voice prompts that callers hear instead
of a human operator when they place a call to an organization that has Exchange 2013 Unified
Messaging. An UM auto attendant helps callers navigate the organization's menu system by using dual
tone multi-frequency (DTMF) (also known as touchtone) inputs or voice-activated inputs that use Speech
Recognition so that they can locate a user or caller in an organization and then place a call or leave a
message to that user.
User A is UM enabled. User B can be any OXE user.
Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Call transfer from Exchange Auto Attendant
Call transfer from User A to User B
A
User A calls Auto Attendant and asks for User B
Check that Auto Attendant can transfer the call to
User B
Test done using
speech recognition
and DTMF mode
See Note (1)
Call transfer from User A to User B when User B
is busy and automatic callback
User A calls Auto Attendant and asks for User B
B
Check that Auto Attendant can transfer the call to
User B
Test done with User B
being UM and not
UM enabled
Check that the busy menu of OXE is reached
Ask for Automatic call back and verify the callback
works correctly
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 25/65
Test
Case
Id
Test Case
N/A
OK
NOK
Comment
Call transfer from User A to User B when User B
is busy, User A leaves a voice message
User A calls Auto Attendant and asks for User B
C
Check that Auto Attendant can transfer the call to
User B
Check that the busy menu of OXE is reached
Test done with User B
being UM and not
UM enabled
Leave a voice message to User B
Check that User B can listen to the message and
delete it
Call transfer from User A to User B when User B
is forwarded to VM/Another set
User A calls Auto Attendant and asks for User B
D
Check that Auto Attendant can transfer the call to
User B
Test done with User B
being UM and not
UM enabled
Check that call is forwarded correctly
Call transfer from User A to User B , User B does
not answer, User A leaves a voice message
User A calls Auto Attendant and asks for User B
E
Check that Auto Attendant can transfer the call to
User B which does not answer
Leave a voice message to User B
Check that User B can listen to the message and
delete it
Note (1): To be able to use DTMF, parameter “Auto Attendant is speech enabled” needs to be deactivated
in Exchange 2013
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 26/65
8.8 Duplication and Robustness
Following tests check how the application reacts during a CPU switch-over, Exchange server reboot and
network link failure.
8.8.1 Access to Voice Mail when CPU switches over
In this IWR, OXE is configured in spatial redundancy. DNS delegation method is used to resolve OXE
hostname.
This requires that, at least during the switchover , a dns request is issued by Audiocodes Mediant for
every messages. This is not the case today on E-SBC, but as a workaround, it is advised to set the
parameter Proxy IP List Refresh Time to 10s to refresh dns table every 10s.
For OXE release k1.400.33, if a CPU switchover occurs during a call from iptouch to Exchange 2013,
iptouch remains blocked for a while after releasing the communication. The user needs to press the
message key, then release key to return to normal state.
Note on older k1 versions: Before OXE version k1.400.33, there is no service continuity during a CPU
switchover, all existing calls involving Exchange 2013 are disconnected. SR1-158492571/crqms00127928
Test
Case
Id
1
Test Case
Verify the service continuity during a CPU
switchover
User B is leaving a voice message to User A
B
Verify the service continuity during a CPU
switchover
User A is calling MS Exchange Auto attendant
C
2
OK
NOK
Comment
Voice Mail Service continuity
User A is consulting his voice mail
A
N/A
Verify the service continuity during a CPU
switchover
OK for service
continuity, but iptouch
screen remains
blocked for a while
after releasing the
communication,
crqms00130868
OK for service
continuity, but iptouch
screen remains
blocked for a while
after releasing the
communication,
crqms00130868
OK for service
continuity, but iptouch
screen remains
blocked for a while
after releasing the
communication,
crqms00130868
Voice Mail consultation/suppression after a
switchover
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 27/65
Test
Case
Id
Test Case
N/A
OK
NOK
Comment
Check that User A has access to saved/new
messages after a CPU switchover
A
Check that User A can listen to the messages and
delete them
3
Auto attendant access after a switchover
A
Check Auto Attendant access after a switchover
B
Check Auto Attendant can transfer a call after a
switchover
4
MWI after a switchover
User B is leaving a voice message to User A during
a CPU switchover
A
Check Message Waiting Indication is activated
correctly
User A has new voice message.
B
Check that the Message Waiting Indication is still
active after a CPU switchover
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 28/65
8.8.2 Access to Voice Mail after Exchange server is rebooted
Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Voice Mail Service availability after a reboot
Reboot Exchange server
A
Check that voice mail access and auto attendant are
reachable again after some time
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 29/65
8.8.3 Access to Voice Mail when LAN is down between OXE and Exchange server
Test
Case
Id
1
Test Case
N/A
OK
NOK
Comment
Voice Mail Service availability after a network
incident
Check access to Voice Mail when LAN connection is
down
A
A system message must be played saying that the
Voice Mail is currently unavailable
B
Check access to Voice Mail when LAN connection is
back
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 30/65
9 Appendix A : Microsoft Exchange 2013 UM
configuration
Exchange 2013 has been installed on a Windows 2008 R2 server.
Exchange 2013 server can be configured using ECP web interface.:
https://<exchange_server_fqdn>/ecp
Go to Unified Messaging

Create and configure an UM Dial Plan: exchange2013_etesting4_DialPlan
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 31/65
o
o
Extension length: Must match the extension length set in OXE
Dial plan type: Telephone extension
o
o
VoIP security mode: Unsecured
Country/Region code: your country code without 00 (33 for France)
In outlook voice access section, add the directory number of OXE external Voice Mail, also called
Exchange Voice Access: 14991
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 32/65

Create an UM IP Gateway
Enter the ip address or the FQDN of the Mediant E-SBC and select previously created dialplan
Enable message waiting indication and outgoing calls
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 33/65

DialPlan Default Policy
Exchange automatically creates an “exchange2013_etesting4_DialPlan_Default Policy” which will be
applied to the newly created Dial Plan. This default policy can be modified depending on the
requirements.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 34/65

Create an Auto attendant
Use the OXE directory number of the external voicemail created for the Auto Attendant, 14992
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 35/65
If you want to use voice recognition, select “Auto attendant is speech enabled”.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 36/65
OXE attendant prefix can be configured, here. Before a transfer, the Auto Attendant proposes to user to
be transferred to the OXE attendant.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 37/65

Create 2 Hunt Groups: one for Outlook Voice Access and one for the Auto Attendant
VoIP gateway: Last created UM IP gateway (OTSBC)
Pilot identifiers: OXE voice mail (14991) and Auto Attendant numbers (14992)
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 38/65

Create mailboxes and give them the UM right
Navigate to Recipients.
Add users from AD and enable Unified messaging on their mailboxes.
Set the mailbox number to OXE user’s directory number (for example OXE user 14016)
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 39/65
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 40/65
10 Appendix B: Alcatel-Lucent Communication
Platform: OXE configuration requirements
The following mgr screens show the basic configuration of the OmniPCX Enterprise (OXE) to allow SIP
communication between OXE and Mediant E-SBC.
On the OXE, it is necessary to create:
-
A SIP trunk ABC-F
-
An external SIP gateway for AudioCodes Mediant E-SBC
-
2 external voice mails for Exchange 2013 voice mail access and Auto Attendant access
For more details on SIP features configuration, refer to standard OXE technical documentation chapter
“SIP configuration procedure”.
10.1 OXE software licences
Software locks given by ACTIS are the following (value x is depending on the client configuration):
OmniPCX software: SIP services
1
3BA09557AA
SIP GATEWAY
Lock 185
x
3BA09559AA
SIP NETWORK
Lock 188
OmniPCX software: Networking services
x
3BA09183JA
ABC-F IP TRUNK GROUP ACCESS
Lock 342
SIP VM W/O OTUC UP TO 50 EXT
Lock 337
OmniMessage: VPS interfaces
1
3BA09137JA
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 41/65
10.2 SIP Trunk
10.2.1 Global SIP trunk parameters
Access path: mgr/Trunk Groups
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 42/65
10.2.2 Virtual Access for SIP
Access path: mgr/Trunk Groups/Trunk Group/Virtual Access for SIP
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 43/65
10.3 SIP External Gateway
Access path: mgr/SIP/SIP Ext Gateway /
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 44/65
Sip remote domain: Mediant E-SBC fqdn
SIP Port Number: 5060
Transport type: UDP
DNS1: ip address of DNS server
Outgoing realm/username/password: Username/password used by the external gateway for outgoing
SIP messages.
SBC can authenticate SIP messages coming from OXE. In this case, outgoing username/password must
be set as on SBC, in Etesting4_for_exchange IP Group. Realm must be left empty (see 11 Appendix C:
AudioCodes Mediant E-SBC configuration requirements)
Incoming Username/Password: Username/password used by the external gateway for incoming
message authentication. Must be set as on SBC, account table (see 11 Appendix C: AudioCodes Mediant
E-SBC configuration requirements)
Minimal Authentication Method: SIP Digest
Note 1:
There is an issue in OXE R11 k1.400.30.f (and k1.400.33), transfer from Auto Attendant will fail if SIP
authentication is set to Digest (crqms 00131490)
Note 2:
For modified SIP ext gateway parameters to be applied, the external gateway must be restarted. To do
this, run the command “dhs3_init –R SIPMOTOR”.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 45/65
mgr : Application > External Voice Mail
External voice Mail for Exchange Voice Access
URL UserName : Directory number of external Voice Mail, has to be defined as the Voice access number
on Exchange 2013 (here 14991)
URL Domain : hostname of Mediant E-SBC
External Gateway Number: OTSBC external gateway number (here 0)
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 46/65
External voice mail for Auto Attendant:
URL UserName : Directory number of external Voice Mail, has to be defined as the Auto Attendant
number on Exchange 2013 (here 14992)
URL Domain : hostname of Mediant E-SBC
External Gateway Number: OTSBC external gateway number (here 0)
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 47/65
11 Appendix C: AudioCodes Mediant E-SBC
configuration requirements

Media Real Table: Create a media realm for internal traffic

SBC Application must be enabled
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 48/65

SRD and SIP interfaces:
A SIP interfaces on port 5060 is linked to a SRD with media anchoring disabled
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 49/65

IP profile: One profile must be set up for RTP (security is not used in this IWR).
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 50/65

2 proxies are defined: one for Exchange 2013, one for etesting4
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 51/65

Configure IP Group Tables for both Exchange and OXE servers
Inbound outbound manipulation rules are defined later
Outbound Message manipulation set: 14, it will be set up later.
SIP digest authentication on incoming OXE SIP messages:
It is possible to authenticate SIP INVITE messages coming from OXE by configuring IP Group
Etesting4_for_Exch2013 using following parameters:
Authentication mode: SBC as Server
Authentication method list: INVITE
Username: The same as OXE SIP ext gw “outgoing username”
Password: The same as OXE SIP ext gw “outgoing password”
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 52/65
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 53/65

Account table:
Used if SIP digest authentication is activated on OXE SIP external gateway.
For the SBC to answer directly to 407 Proxy Authenticate SIP message, a new account must be added in
SIP Definitions> Account Table
Username: The same as incoming username on OXE external gateway (Etesting4)
Password: The same as incoming password on OXE external gateway
Application type: SBC
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 54/65

Configure IP to IP routing table
Route the calls from Exchange to OXE by routing the calls from “Source IP Group” 11 to “Destination IP
Group” 12
Route the calls from OXE to Exchange by routing the calls from “Source IP Group” 12 to “Destination IP
Group” 11
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 55/65

SIP message manipulations
4 rules have been added in SIP definitions>Msg Policy and Manipulation> Message Manipulations
for MWI and transfer from Auto Attendant features.
Message type: ALL
Condition: None
Action Subject: header.from.url.host
Action type: Modify
Action value: ‘otsbc.etesting.lab’ E-SBC fqdn
Message type: NOTIFY
Condition: None
Action Subject: header.from.url.user
Action type: Modify
Action value: ‘14991’ Exchange Voice mail number
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 56/65
Message type: NOTIFY
Condition: None
Action Subject: header.contact.url.user
Action type: Modify
Action value: ‘14991’ Exchange Voice mail number
Message type: REFER
Condition: None
Action Subject: header.refer-to.url.host
Action type: Modify
Action value: ‘etesting4.etesting.lab’ OXE fqdn
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 57/65

ProxyIPListRefreshTime
Parameter Description:Time interval between refresh of proxies list (seconds). For example SRV query
will be done every ProxyIPListRefreshTime seconds
To be set to 10
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 58/65
12 Appendix D: AAPP member’s escalation process
In case you would need technical assistance, please contact the reseller/distributor where you purchased
your AudioCodes products. They have been trained on the products to give you 1st and 2nd levels of
support. They are in plus in direct relation with 3rd level AudioCodes support in case an escalation would
be needed.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 59/65
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 third-party
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.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 60/65
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/
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 61/65
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
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 62/65
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 AlcatelLucent 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 Alcatel-Lucent 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 not 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.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 63/65
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 Alcatel-Lucent will
provide 8 hours assistance against payment.
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 64/65
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
Poland
English
Sweden
Czech Republic
Estonia
Finland
Greece
Slovakia
Portugal
Spain
For other countries:
English answer:
French answer:
German answer:
Spanish answer:
Spanish
+ 1 650 385 2193
+ 1 650 385 2196
+ 1 650 385 2197
+ 1 650 385 2198
END OF DOCUMENT
Alcatel-Lucent Application Partner Program – Inter-working report
Copyright © 2014 Alcatel-Lucent, All rights reserved
Edition 3 - page 65/65