Professional Documents
Culture Documents
Audiocodes-M1K Lync2013 OmniPCXEnterpriseR10.0&R11.0 IWR Ed05
Audiocodes-M1K Lync2013 OmniPCXEnterpriseR10.0&R11.0 IWR Ed05
Inter-Working Report
Partner: AudioCodes
Application type: Session Border Controller
Application name:
Mediant 1000 SBC /Microsoft Lync 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 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.
Historic
Test results
Passed Refused Postponed
Phone: +336 42 18 15 60
1 Introduction .................................................................................................. 6
1.1 GLOSSARY ................................................................................................... 6
2 Validity of the InterWorking Report ..................................................................... 7
3 Limits of the Technical support .......................................................................... 8
3.1 CASE OF ADDITIONAL THIRD PARTY APPLICATIONS ........................................................... 8
4 Application information.................................................................................... 9
5 Tests environment ........................................................................................ 10
5.1 GENERAL ARCHITECTURE ...................................................................................10
5.2 SOFTWARE CONFIGURATION ................................................................................11
6 Summary of test results ................................................................................. 13
6.1 SUMMARY OF MAIN FUNCTIONS SUPPORTED .................................................................13
6.2 SUMMARY OF PROBLEMS ....................................................................................13
6.2.1 OXE ........................................................................................................................................... 13
6.2.2 Audicodes/Lync ...................................................................................................................... 13
6.3 SUMMARY OF LIMITATIONS ..................................................................................13
6.3.1 OXE ........................................................................................................................................... 13
6.3.2 AudioCodes/Lync .................................................................................................................... 13
6.4 NOTES, REMARKS...........................................................................................14
7 Test Scenarios ............................................................................................. 15
7.1 TEST PROCEDURE ..........................................................................................15
7.2 RESULT TEMPLATE..........................................................................................15
8 Testing ....................................................................................................... 16
8.1 BASICS OUTGOING CALLS: OXE TO LYNC...................................................................16
8.1.1 Calls from an OXE user set to a Lync user ......................................................................... 16
8.2 INCOMING CALLS: LYNC => OXE ...........................................................................18
8.2.1 Reception of calls .................................................................................................................. 18
8.3 FEATURES DURING CONVERSATION ..........................................................................20
8.3.1 Hold, Consultation call and broker call ............................................................................. 20
8.3.2 Transfer call ........................................................................................................................... 22
8.3.3 Conference .............................................................................................................................. 24
8.4 VOICE MAIL ................................................................................................25
8.4.1 Test Objectives....................................................................................................................... 25
8.4.2 Test Results ............................................................................................................................. 25
8.5 ATTENDANT ................................................................................................26
8.5.1 Test Objectives....................................................................................................................... 26
8.5.2 Test Results ............................................................................................................................. 26
8.6 DEFENSE / RECOVERY ......................................................................................27
8.6.1 Test Objectives....................................................................................................................... 27
8.6.2 Test Results ............................................................................................................................. 27
9 Appendix A : AudioCodes Mediant 1000 MSBG Configuration ................................... 28
9.1 GETTING STARTED .........................................................................................28
9.2 CONFIGURATION PROCEDURE...............................................................................29
9.2.1 Configure IP Address ............................................................................................................. 29
9.2.2 Enable the SBC Application .................................................................................................. 29
9.2.3 Add a SIP Interface ................................................................................................................ 29
9.2.4 Add IP groups .......................................................................................................................... 30
9.2.5 Configure IP Profiles ............................................................................................................. 33
9.2.6 Configure the Proxy Set table ............................................................................................. 36
9.2.7 Configure Routing .................................................................................................................. 38
9.2.8 Configure Reasons for Alternative Routing ....................................................................... 38
9.2.9 Sip Header Manipulations ..................................................................................................... 39
9.2.10 Reset the Gateway................................................................................................................. 41
10 Appendix B: Alcatel-Lucent Communication Platform: configuration requirements .... 42
11 Appendix C: Partner escalation process ........................................................... 49
12 Appendix D: AAPP program .......................................................................... 50
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:
1.1 Glossary
Acronym Meaning
OXE OmniPCX Enterprise
Transferee The party being transferred to the transfer target
Transferor The party initiating the transfer
Transfer target The new party being introduced into a call with the transferee
Blind or semi-attended transfer The transferor having a session in hold state with the transferee and
initiating the transfer by a consultation call to the target performs the
transfer while the target is in ringing state
Attended transfer or transfer on The transferor waits to be in conversation state with the target before
conversation completing the transfer
CLIP Calling Line Identification Presentation
CNIP Calling Name Identification Presentation
CLIR Calling Line Identification Restriction
CNIR Calling Name Identification Restriction
COLP Connected Line Identification Presentation
CONP Connected Name Identification Presentation
COLR Connected Line Identification Restriction
CONR Connected Name Identification Restriction
CRC Customer Relationship Centre
PG SIP GW XXX Peripheral Gateway
ICM SIP GW XXX Intelligent Call Manager
CCM SIP GW XXX Call Manager
CVP Customer voice Portal
BC ALU Business Contact
CTI Computer Telephony Integration
PSTN(analogique card on the OXE) Public Switched Telephone Network
SBC Session Border Controller
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.
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.
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.
Application type: SIP SBC Mediant 1000 MSBG Customer Relationship Center includes SIP SBC
Mediant 1000 MSBG
Office
Basic outgoing call
Basic incoming call
Hold/Retrieve
Consultation call
Transfer
Conference/Cancel
Voice Mail
Microsoft
Lync 2013
server
OXE
Lync
Phones
users
AudioCodes Mediant 1000 : 1
Microsoft Microsoft
Domain Mediation
Controller server Alcatel-Lucent
OmniPCX Enterprise
The Microsoft Lync 2013 Server and Mediation Server connect to the Sip SBC Mediant 1000 MSBG
which is connected to the OmniPCX Enterprise via a private SIP Trunk.
6.2.1 OXE
None
6.2.2 Audicodes/Lync
None
6.3.1 OXE
None
6.3.2 AudioCodes/Lync
Call from an OXE set to a Lync client: Lync doesnt update the calling name.
Call from an OXE set to a Lync client: The trunk name is displayed on the OXE set instead
of the Lync client name
Transfers from Lync: Lync doesnt update transferee information after a transfer
(unattended or attended transfer).
Semi attended or attended transfers from OXE: OXE sends the user information to
AudioCodes gateway (in REFER or REINVITE messages). However Lync display is not
updated. Transfer is OK.
After an OXE CPU swichover to a standby CPU, an existing call cannot evolve (stet
changed to on hold, transferred)
After an OXE CPU swichover to a standby CPU resolved by spatial redundancy mechanism,
a call cannot be established with the new main call server before the next DNS request.
These DNS request are configured to be sent every 10 seconds on the Median 1000
(parameter PROXYIPLISTREFRESHTIME=10).
Microsoft Lync user does not call a number with a character: *, #,$
AudioCodes gateway Mediant 1000 supports 150 simultaneous sessions per CPU or 60
simultaneous sessions in case of audio transcoding (for example law change : G711a-
>G711, codec change : G729->G711).
Step: a test may comprise multiple steps depending on its complexity. Each step has to be
completed successfully in order to conform to the test. Step 0 when present represents the initial
state for all the following steps.
Action: describes which action to realize in order to set-up the conditions of the test.
Result: describes the result of the test from an external point of view. If it is positive, it
describes which application's trigger was checked. If it is negative, it describes as precisely as
possible the problem.
Comment: this column has to be filled in when a problem occurs during the test. It must contain
a high level evaluation of the localization of the responsibility: Alcatel or the Partner.
it is not intended during this test session to debug and fix problems.
5 . action 5
No indication, no
NOK
error message
The calls are generated to several numbers corresponding to users on the Lync platform.
Called party can be in different states: free, busy, Out of service, do not disturb.
Points to be checked: tones, voice during the conversation, display (on caller and called party),
hang-up phase.
Note: dialling will be based on direct dialling number but also using programming numbers on the
phone.
During conversation, waiting and consultation call are provided and must be checked.
In addition, a second call must be generated in order to check that right tones are generated on
Lync user.
During the consultation call step, the transfer service can be requested and must be tested.
Several transfer services exist: blind transfer, supervised transfer and busy transfer.
Audio, tones and display must be checked.
Tests are performed using all possible combinations of legacy (IPPHONE) and Lync sets.
During the consultation call step, the transfer service can be requested and must be tested.
Several transfer services exist: Unattended Transfer, Semi-Attended Transfer and Attended
Transfer.
Audio, tones and display must be checked.
In the below tables, OXE means a proprietary OXE (Z/UA/IP) set. The calls can be local/network
calls.
Check the transfer for two configuration possibilities on Lync (with or without REFER). For blind
transfer check that the transferred call can be taken back from the transferee in case of no
answer or wrong number dialed.
During the consultation call step, the conference is provided and must be tested.
Programmed conference and 3 steps conferences have to be checked by analyzing the audio and
display on each user.
Option 1: Voice mail is Exchange 2010 for all users: Not tested (Should be OK from
Option 2: Each system is served by its own Voice Mail: OK
Temporary Data Network Link down with Existing calls are stopped.
1 the PBX and Mediant 1000 MSBG OK Establishing new call is possible
when the link is reestablished.
Spatial redundancy IP Method : CPU An existing call cannot evolve
2 switchover with SIP communication OK,but (stet changed to on hold,
transferred)
Spatial redundancy DNS method A call cannot be established after
(delegation on a third party DNS server) : the switchover with the new main
CPU switchover without SIP communication call server before the next DNS
request. These DNS request are
3 OK,but
configured to be sent every 10
seconds on the Median 1000
(parameter
PROXYIPLISTREFRESHTIME).
Spatial redundancy DNS method : CPU A second call cannot be
switchover with SIP communication established after the switchover
with the new main call server
before the next DNS request.
4 OK,but
These DNS request are configured
to be sent every 10 seconds on
the Median 1000 (parameter
PROXYIPLISTREFRESHTIME).
Switchover to Passive Call Server (PCS). (IP
link to main/stdby OXE call servers down)
5 N/A
For more information, see the Mediant 1000 MSBG Users manual.
RFC 2833 Behavior Extend (in case the OXE does not send RFC
2833 in SDP)
This table resume parameters that are mandatory to interconnect with Lync 2013:
Parameter Setting
SBC Remote Refer Behavior Handle Locally (mandatory because Lync
Server 2013 does not support receive Refer)
To configure Proxyset 2 :
2. Open the Proxy Set Table page (Configuration tab > VoIP menu > Control
Network> ProxySet Table).
1. Open the 'Proxy & Registration' page (Configuration tab > VoIP menu > SIP
Definitions > Proxy & Registration).
2.
Figure 9-11: Proxy & Registration
7. Open the 'IP to Trunk Group Routing' page (Configuration tab > VoIP menu >
Sip Definitions > Msg Policy & Manipulation > Messages Manipulation).
Figure 9-13: Messages Manipulations for OXE
Parameter Setting
Action Subject header.from.url.host
Action Type Modify
Action Value 172.17.165.3 : AudioCodes SBC IP address
Parameter Setting
Action Subject header.p-asserted-identity.url.host
Action Type Modify
Action Value header.from.url.host
Node1 Configuration:
Field Value
Private SIP Trunk Group which will be used for outgoing and incoming (or not) calls
Trunk group Trunk Groups
(2)
Trunk Group ID 37
Trunk Group Type T2
Trunk Group name SIPTRK
Remote Network 15
Node number 1
Q931 signal variant ABC-F (private sip trunk)
T2 Specification SIP
Overlap dialing No
Virtual accesses Trunk Groups/Trunk Group/Virtual access for SIP
Trunk Group Id 37
Number of SIP Access 2 (ie 2*62 accesses)
SIP management for incoming calls (from remote SIP domain)
SIP External Gateway configuration used to reach Operator SIP GW
SIP Ext Gateway SIP/SIP Ext Gateway
SIP External Gateway Id 1
SIP Remote domain 172.17.165.3
SIP Port Number 5060
SIP Transport Type TCP
Trunk group number 37
Supervision timer 10 (used for AudioCodes gateway redundancy)
RFC 3325 supported by the distant True
Management for outgoing calls via SIP Trunk Group
ARS routing used to rout outgoing calls to external SIP GW through Public SIP TG
Dialing command table (DCT) Translator/Automatic Route Selection/Dialing Command Table
(4)
Table Id 1
Carrier Reference 0
Command I
Associated Ext SIP gateway 1
Dialing command table (DCT) Translator/Automatic Route Selection/Dialing Command Table
(4)
Table Id 2
Carrier Reference 0
Command I
Associated Ext SIP gateway 2
ARS route list Translator/Automatic Route Selection/ARS Route list
(5)
ARS Route list 4
To get the display name of Lync user on OXE user when the OXE user calls the Lync user or when
Lync user calls the OXE user, You must make the configuration bellow:
1. System -> Other System Parameter ->Descend Hierarchy -> External signaling Parameter -
> review Modify -> calling name presentation -> put it in True.
Node2 Configuration:
Field Value
To make a Call to ARS via T2 Loopback, You must make the configuration bellow, to allow OXE to
make a transit calls. In this case: we are getting call from:
One trunk (T2) and routed to another trunk (SIP).
The Alcatel-Lucent Application Partner Program (AAPP) has two main objectives:
12.2 Alcatel-Lucent.com
You can access the Alcatel-Lucent website at this URL: http://www.Alcatel-Lucent.com/
13.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
If the issue is in the scope of the IWR, both parties, Alcatel-Lucent and the Application Partner,
are engaged:
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 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 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.
1. An InterWorking Report exist but is not valid (see Chap 2 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) ,
In all these cases, Alcatel-Lucent offers the On Demand Diagnostic service where Alcatel-Lucent will
provide 8 hours assistance against payment.