Download as pdf or txt
Download as pdf or txt
You are on page 1of 19

Open Interoperability Test Report

Huawei

TEST RESULT:
DATE TESTED:
PRODUCT/VERSION:
IVT Contact Name
/Email:

TEKVIZION PVS, INC. CONFIDENTIAL

PASS
September 14, 2012
eSpace U1980 / V100R001

Microsoft Unified Communications Open


Interoperability Test Report

Copyright 2012 by tekVizion PVS, Inc.


All Rights Reserved.
Confidential Information
The information contained in this document is confidential and proprietary to tekVizion PVS, Inc. Its
purpose is to communicate the overall strategy of an Interoperability Test Plan used by tekVizion Labs.
This document is the property of, and is proprietary to tekVizion. It is not to be disclosed in whole or in
part without the express written authorization of tekVizion, shall not be duplicated or used, in whole or in
part, for any purpose other than to evaluate the proposed scope of testing under contemplation.
TEKVIZION, TEKVIZION PVS, AND TEKVIZION LABS ARE TRADEMARKS OF TEKVIZION PVS, INC. FAST
FORWARD IS A SERVICE MARK OF TEKVIZION.

DOC UM E NT RE V IS IO N HI ST OR Y
Version

Reason for Change

Date

Created/Updated by

1.0

Initial Draft

01/10/2008

Abelardo G.

1.1

Updated based on OCS Lync 2010 release

11/03/2010

Gerry Pearson

1.2

Huawei test results

09/14/2012

Satheesh Kumar

TEKVIZION PVS, INC. CONFIDENTIAL

Microsoft Unified Communications Open


Interoperability Test Report

Table of Contents
1

EXECUTIVE SUMMARY ..................................................................................................... 4

INTRODUCTION ................................................................................................................. 9

2.1

Document Scope ...........................................................................................................................................9

2.2

tekVizion Labs ................................................................................................................................................9

TESTING PROCESS AND CRITERIA .............................................................................. 11

3.1

Test Approach ............................................................................................................................................. 11

3.2

Entry Criteria ............................................................................................................................................... 11

3.3

Acronyms .................................................................................................................................................... 11

UC-OIT TEST CONFIGURATION ..................................................................................... 12

4.1

Test Network Setup .................................................................................................................................... 13

4.2

Device Under Test ...................................................................................................................................... 14

4.3

3 Party Components ................................................................................................................................ 14

4.4

Administration and Debugging Tools ...................................................................................................... 14

4.5

Test Equipment and Number Assignment ............................................................................................... 14

5
5.1

rd

INTEROPERABILITY TEST RESULTS ............................................................................ 15


Rules of Engagement for Testing ............................................................................................................. 15

REFERENCES .................................................................................................................. 19

TEKVIZION PVS, INC. CONFIDENTIAL

Microsoft Unified Communications Open


Interoperability Test Report

1 Executive Summary
The following summarizes tekVizions findings:
Test Case Failures
None
Features Not Supported

The PBX does not support REFER.

185693: Device supports hairpin elimination for consultative transfer with REFER

185695: Device supports hairpin elimination for blind transfer with REFER

187009: Device generates INVITE with Replaces and Refer-by headers when it receives a REFER
request

193401: Device does not drop the call when a blind transfer initiated by Lync End Point to PSTN
End Point2 fails

Test Cases that are Not Applicable

None

Test Cases that were Not Executed

As
per
approval
from
Microsoft
(approval
received
from
Ken
Johnson.Ken@microsoft.com), only sanity testing was conducted on eSpace U1910.

Huawei has indicated that eSpace U1910/U1980 runs the same software as IP PBX eSpace U1930
which was tested earlier. Therefore the following test cases were not executed as they were not
part of the pre-approved suite of sanity test cases:

176523: Device disconnects a forked call if PSTN End Point hangs up while phones are ringing

208490: Device disconnects a forked call if PSTN End Point hangs up while phones are ringing
when media bypass is ON

208546: Device disconnects a forked secure call if PBX Phone hangs up while phones are ringing

185250: Device load balances inbound calls among Mediation Servers in the cluster

185722: Device fails over incoming call to Mediation Server2 when Mediation Server1 sends 503
response

187060: PBX Phone establishes a call with Lync End Point when Mediation Server1 goes down

187488: Multiple inbound calls from PSTN End Points to multiple Lync End Points through the
Device

176476: Mediation Server initiated session modification using a "RE-INVITE" message without any
SDP

TEKVIZION PVS, INC. CONFIDENTIAL

Johnson

Microsoft Unified Communications Open


Interoperability Test Report

176541: Device disconnects a call that is on hold when PBX Phone hangs up

176588: Device sends RTCP packets while playing music on hold

176967: Lync End Point plays music when it holds call from PBX Phone to Lync End Point

185246: Attendant Console resumes call to PBX Phone after playing music on hold

187012: Mediation Server initiated session details modification of an existing voice session

186993: PBX Phone set to call forward on busy to Lync End Point

176467: PBX Phone calls Lync End Point that has call forwarded to another PBX Phone

208522: PSTN End Point1 calls Lync End Point that has call forwarded to PSTN End Point2 when
media bypass is ON

208560: PSTN End Point1 makes a secure call to Lync End Point that has call forwarded to PSTN
End Point2

185314: Lync End Point1 parks call from PSTN End Point which is later retrieved by Lync End Point2

185691: PBX Phone calls Lync End Point that has call forwarding set to another PBX Phone

186988: PBX Phone set to call forward all (CFA) to Lync End Point

176596: Device is able to disconnect a call that is forked to Lync End Points set to 'Do not disturb'

185305: PBX Phone1 calls Lync End Point which is set to simul-ring to another IVR number on a
PSTN endpoint

176431: Device handles 488 Not Acceptable from Mediation Server operating in RTP only mode

176536: Device does not change the SSRC of an established SRTP session

176600: Device does not change the SSRC of an established inbound SRTP session

176617: Device sends Crypto attributes in SDP for call from PBX Phone to Lync End Point

184904: Device with RTP only setting rejects call from Lync End Point that requires SRTP

185355: Mediation Server that requires SRTP rejects call from Device that supports RTP only

185356: Device that supports SRTP only rejects call from Lync End Point that supports RTP Only

185357: Lync End Point calls PBX Phone with TLS ON and SRTP Optional on Mediation Server and
Device

185360: Device sends its own FQDN in contact header for TLS call from Lync End Point to PBX
Phone

TEKVIZION PVS, INC. CONFIDENTIAL

Microsoft Unified Communications Open


Interoperability Test Report

185361: PSTN End Point calls Lync End Point with security enabled and Lync End Point later hangs
up

185362: Lync End Point calls PBX Phone with security enabled and PSTN End Point later hangs up

185702: PSTN End Point places secure call from Lync End Point on hold and then resumes

185708: PBX Phone places secure call to Lync End Point on hold and then resumes

185237: Lync End Point1 calls Lync End Point2 and later escalates it to conference by inviting
PBX Phone

185298: PSTN End Point establishes the call with CAA

187072: Lync End Point1 calls Lync End Point2 and escalates it to conference by inviting PSTN
End Point

176343: Device disconnects a call that is on hold when Lync End Point hangs up

176383: PSTN End Point rejects call from Lync End Point

176398: PSTN End Point calls Lync End Point and hangs up while Lync End Point is ringing

176413: PSTN End Point displays caller ID of Lync End Point for an outbound call

208588: PSTN End Point displays caller ID of Lync End Point for an outbound call when media by
pass is ON

176419: PSTN End Point disconnects call made to Lync End Point

176426: PSTN End Point makes a call with G.711 A-law codec to Lync End Point

176439: PSTN End Point makes a call with G.711 U-law codec to Lync End Point

176448: PSTN End Point calls Lync End Point when Caller ID set to 'Anonymous' on Device

176529: Device does not change the SSRC of an established RTP session

208508: Device does not change the SSRC of an established RTP session when media bypass is
ON

176545: Device sends RTCP sender and receiver reports

208501: Device sends RTCP sender and receiver reports when media bypass is ON

208550: Device sends RTCP sender and receiver reports for a secure call

176567: Lync End Point response to PSTN End Point is delayed due to network delay

176574: Device handles multiple RTP streams for a call to Lync End Point

TEKVIZION PVS, INC. CONFIDENTIAL

Microsoft Unified Communications Open


Interoperability Test Report

176579: Device does not change SSRC of an established inbound RTP session
176610: Device processes phone-context in Request and To URI from Lync End Point

176641: Device negotiates Comfort Noise in a call from Lync End Point to PSTN End Point

176645: Device rejects call from Lync End Point to PSTN End Point when the associated PRI line is
down

176883: Device sends Comfort Noise packets to Lync End Point when call is muted

207720: Device sends Comfort Noise packets to Lync End Point when secure call is muted

208486: Device sends Comfort Noise packets to Lync End Point when call is muted when media
bypass is ON

176960: Lync End Point makes call to PSTN End Point with G.711 A-law and G.711 U-law codecs

208466: Lync End Point makes a call to PSTN End Point with G.711 A-law and/or G.711 U-law
codecs when media bypass ON

176971: Lync End Point makes an outbound call and hangs up before connect

176973: Lync End Point makes a call with G.711 A-law codec to PSTN End Point

176981: Device times out after 3 min of no response from Lync End Point following 100 trying

184490: Lync End Point calls PSTN End Point with an alias name in the 'FROM' header

184493: PBX Phone1 calls Lync End Point which is set to simul-ring to PSTN End Point2 and Lync
End Point answers

184494: PBX Phone1 calls Lync End Point which is set to simul-ring to PSTN End Point2 and PSTN
End Point2 answers

184569: Device establishes call to Lync End Point with configured value of p-time

185685: Device sends DTMF payload type in the range of 96-127

186625: PSTN End Point disconnects a call established with Lync End Point

187006: Device sends single m attribute in initial offer for call from PBX Phone to Lync End Point

176499: Device processes call from Lync End Point with E.164 number in From URI

176592: Device handles call from Lync End Point to a user that does not exist in the domain

TEKVIZION PVS, INC. CONFIDENTIAL

Microsoft Unified Communications Open


Interoperability Test Report

Observations

The PBX, as designed plays its own MOH to the PBX endpoints when the MOH is disabled on the
Lync.

TEKVIZION PVS, INC. CONFIDENTIAL

Microsoft Unified Communications Open


Interoperability Test Report

2 Introduction
Microsoft@ Unified Communications Open Interoperability Testing is performed between Microsoft@
Lync Server 2010 and Huawei U1900 [eSpace U1980]. This document is a record of the test results,
observations, and the overall testing experience with the device under test (DUT. The configuration of
the device under test is also documented where required to make the systems interoperable.

2.1

Document Scope

This document provides the test report and approach used by tekVizion Labs to perform Microsoft@
Lync Open Interoperability testing for the documented products and their versions. This document does
not provide the test cases, the success criteria, processes and execution steps of testing that was
performed. Refer to the Microsoft@ connect.microsoft.com site for the Microsoft@ documentation and
test plan details.

2.2

tekVizion Labs

tekVizion LabsTM is an independent testing and Verification facility offered by tekVizion PVS, Inc.
(tekVizion). tekVizion Labs offers several types of testing services including:

Remote Testing provides secure, remote access to certain products in tekVizion Labs for preVerification and ad hoc testing

Verification Testing Verification of interoperability performed on-site at tekVizion Labs


between two products or in a multi-vendor configuration (solution Verification)

Product Assessment independent assessment and verification of product functionality,


interface usability, assessment of differentiating features as well as suggestions for added
functionality, stress and performance testing, etc.

tekVizion is a systems integrator specifically dedicated to the telecommunications industry. Our core
services include consulting/solution design, interoperability/Verification testing, integration, custom
software development and solution support services. Our services helps service providers achieve a
smooth transition to packet-voice networks, speeding delivery of integrated services. While we have
expertise covering a wide range of technologies, we have extensive experience surrounding our
FastForward>> practice areas which include: IN Evolution, Packet Voice, Service Delivery, and
Integrated Services.
The tekVizion team brings together experience from the leading service providers and vendors in
telecom. Our unique expertise includes legacy switching services and platforms, and unparalleled
product knowledge, interoperability and integration experience on a vast array of VoIP and other nextgeneration products. We rely on this combined experience to do what we do best: help our clients
advance the rollout of services that excite customers and result in new revenues for the bottom line.
tekVizion leverages this real-world, multi-vendor integration and test experience and proven processes
to offer services to vendors, network operators, enhanced service providers, large enterprises and other

TEKVIZION PVS, INC. CONFIDENTIAL

Microsoft Unified Communications Open


Interoperability Test Report

professional services firms. tekVizions headquarters, along with a state-of-the-art test lab and Executive
Briefing Center, is located in the Telecom Corridor in Richardson, Texas.
(For more information on tekVizion and its practice areas, please visit tekVizion Labs web site at
www.tekVizionlabs.com.)

TEKVIZION PVS, INC. CONFIDENTIAL

10

Microsoft Unified Communications Open


Interoperability Test Report

3 Testing Process and Criteria


3.1

Test Approach

End-to-End testing methodology is used for Microsoft@ Unified Open Interoperability Verification testing.
The testing approach is to test the functional interoperability between the products under test
simulating a real-world setup. The testing focused on all interaction between the Mediation server of
Lync 2010 and the partner device or network referred to as Device Under Test (DUT). No validation for
Exchange Unified Messaging is verified. Microsoft@ provided their Open Interoperability test tool (lyncIT)
to simulate the OCS and its clients to perform the automated tests and the remaining manual tests are
executed using a real deployment of Lync 2010. The PSTN network was simulated in the tekVizion lab
and for certain test cases, Tektronixs Spectra2 was used to simulate the PSTN network. The version of the
tool and the other test equipment used is documented in the next few sections.

3.2

Entry Criteria

Before Microsoft@ Lync 2010 Open Interoperability testing can begin, the partner has to download the
test plan from the connect.microsoft.com site, execute the test cases in their lab and submit the results
to tekVizion. TekVizion and Microsoft verify the submitted results for any exempt scenarios. Once the test
results have been reviewed, partner can work with the tekVizion engineers to setup the partner
equipment or network for testing. Partner engineer has the opportunity to verify the configuration of the
DUT in the test network. Once interoperability testing has been initiated, the products under test are
considered frozen for interoperability testing purposes. No software/firmware load will change during
the testing period.

3.3

Acronyms

The key terms (acronyms) used in this test strategy are listed below.
BVT
B3R
B2BUA
DUT
GW
LC
OCS
SIP
SDP
ICE
QoS
PBX
SBC
SP
UA
UAC
UAS

Basic Verification Test


Beta 3 Refresh
Back to Back User Agent
Device Under Test
Gateway
Live Communications
Office Communications Server
Session Initiation Protocol
Session Description Protocol
Interactive Connectivity Establishment
Quality of Service
Private Branch Exchange
Session Border Controller
Service Provider
User Agent
User Agent Client
User Agent Server

TEKVIZION PVS, INC. CONFIDENTIAL

11

Microsoft Unified Communications Open


Interoperability Test Report

UC-OIP
OITT
UC
VoIP

Unified Communications Open Interoperability Program


Open Interoperability Test Tool
Unified Communications
Voice over Internet Protocol

4 UC-OIT Test Configuration


For this test, the IP-PBX was provisioned with two FXS analog phones. The Lync cluster consisted of a
Standard Edition front end with collocated mediation server, plus one standalone mediation server.
Three Lync endpoints were used during the test. The PBX configurations were modified during testing to
match the requirements of each test case.

TEKVIZION PVS, INC. CONFIDENTIAL

12

Microsoft Unified Communications Open


Interoperability Test Report

4.1

Test Network Setup

PSTN Phone #1
PSTN phone #2

PSTN

E1 PRI

+5010
Huawei eSpace
U1980 (DUT)

FXS

+5016

FXS

SIP

Lync 2010 Mediation Server Cluster


182.72.70.140 (pool #1)
182.72.70.141 (pool #2)

182.72.70.140

LyncIT

+8657120985630
+8657120985631
+8657120985630
+8657120985631
Figure 1 Microsoft@ Lync Open Interoperability Test network.

TEKVIZION PVS, INC. CONFIDENTIAL

13

Microsoft Unified Communications Open


Interoperability Test Report

4.2

Device Under Test

Devices Under Test

Version

Huawei U1900

V100R001

Microsoft Lync 2010

4.0.7577.4103

Microsoft Lync Interoperability Tool (LyncIT V2)

4.0.7577.344

4.3

3rd Party Components

None.

4.4

Administration and Debugging Tools

Administration and Debugging Tools

Version

WireShark

1.28 (SVN Rev 32676)

4.5

Test Equipment and Number Assignment

Test
Equipment

Description

Number
Assigned

Analog phone

PBX extension

+5010

Analog phone

PBX extension

+5016

OCS subscriber

Extension (Lync client)

+8657120985630

OCS subscriber

Extension (Lync client)

+8657120985631

TEKVIZION PVS, INC. CONFIDENTIAL

14

Microsoft Unified Communications Open Interoperability Test Report

5 Interoperability Test Results


5.1

Rules of Engagement for Testing


The test steps and the expected results are defined in the test plan and not in this report. If any changes or deviations are needed they have
to be documented in the report.
If any test case is not applicable then it should be marked as N/A and an explanation should be provided for marking it N/A
In the comments section the file reference where the logs are captured should be documented
The test result should be marked as Pass, Fail, N/A, N/S for Not Applicable and Not Supported only
All test cases should have a result defined.
If a test case has a N/A or a N/S, the reason for this result should be documented
If a test case if marked Fail, change the color to Red for easy reading

Test Case ID
Required
Load Balancing and Failover
176507
Y

Automated
Y

208531

184897

187063

187066

176461

176571

Hold-Resume
176456

TEKVIZION PVS, INC. CONFIDENTIAL

Description

P/F

Device responds to OPTIONS as keep-alive to


Mediation Server
Device responds to OPTIONS as keep-alive to
Mediation Server when media bypass is ON
Device sends periodic OPTIONS message as a keepalive to Mediation Server
Device resumes sending calls to Mediation Server
when it starts receiving OPTIONS response from that
Mediation Server
PSTN End Point establishes a call with Lync End Point
when Mediation Server1 goes down

Lync End Point resumes call to PBX Phone after


playing music on hold for 15 min
PBX Phone puts Lync End Point on hold and resumes
after 15 minutes
Device sends RTCP packets when Lync End Point has
placed call on hold

Comments

P
P
P
P

P
P

15

Microsoft Unified Communications Open Interoperability Test Report

Test Case ID
208538

Required
Y

Automated
Y

176969

Transfer
187500

187504

184900

185308

185309

185693

185695

185696

185697

187009

193401

Extended Features
184902

TEKVIZION PVS, INC. CONFIDENTIAL

Description
Lync End Point plays music when it holds call from
PSTN End Point to Lync End Point when media
bypass is ON
Lync End Point places a call from PBX Phone on hold
and resumes after 15 min

P/F

Device initiates a blind transfer from Lync End Point1


to Lync End Point2
Device initiates a consultative transfer from Lync
End Point1 to Lync End Point2
PBX Phone calls Lync End Point1 and Lync End Point1
initiates a blind transfer of the call to Lync End
Point2
Device does not drop the call when a blind transfer
initiated by Lync End Point to PBX Phone2 fails
Device does not drop the call when a consultative
transfer initiated by Lync End Point to PBX Phone2
fails
Device supports hairpin elimination for consultative
transfer with REFER
Device supports hairpin elimination for blind
transfer with REFER
PBX Phone1 calls Lync End Point1 and Lync End
Point1 initiates a blind transfer of the call to PBX
Phone2
PBX Phone1 calls Lync End Point1 and Lync End
Point1 initiates a consultative transfer of the call to
PBX Phone2
Device generates INVITE with Replaces and Refer-by
headers when it receives a REFER request
Device does not drop the call when a blind transfer
initiated by Lync End Point to PSTN End Point2 fails

PBX Phone calls Lync End Point that later parks the
call but does not retrieve it

Comments

P
P

P
P
P
P
N/S

REFER Not Supported

N/S

REFER Not Supported

P
P
N/S

REFER Not Supported

N/S

REFER Not Supported

16

Microsoft Unified Communications Open Interoperability Test Report

Test Case ID
185315

Required
N

Automated
N

Early Media
176550

176587

176601

176956

207709

208477

176977

208592

TLS / SRTP
184905

185701

Conference
172875

185235

Basic Voice Calls


176388

176406

TEKVIZION PVS, INC. CONFIDENTIAL

Description
Lync End Point1 parks call to PBX Phone which is
later retrieved by Lync End Point2

P/F

Comments

Device sends PRACK for reliable early media for call


from PBX Phone to Lync End Point
Device sends PRACK for reliable early media for call
from PSTN End Point to Lync End Point
Lync End Point calls an IVR number and walks
through the IVR menu after Connect from Device
Lync End Point calls an IVR number and walks
through the IVR menu before Connect from Device
Lync End Point makes a secure call to an IVR number
and walks through the IVR menu before Connect
from Device
Lync End Point calls an IVR number and walks
through the IVR menu before Connect from Device
when media bypass ON
Lync End Point hears early media for a call to PSTN
End Point
Lync End Point hears early media for a call to PSTN
End Point when media bypass is ON

Lync End Point calls PBX Phone when "TLS=ON" and


"SRTP=Required"
Lync End Point places secure call to PSTN End Point
on hold and then resumes after 12 minutes

PBX Phone calls Lync End Point1 and escalates to


conference by inviting Lync End Point2
Lync End Point calls PSTN End Point1 and escalates it
to a conference by inviting PSTN End Point2

Lync End Point sends INVITE with E.164 number and


extension in Request and To URI
PSTN End Point disconnects a call established with
Lync End Point

P
P
P
P
P
P
P

P
17

Microsoft Unified Communications Open Interoperability Test Report

Test Case ID
176481

Required
Y

Automated
Y

176583

178605

208443

184571

Error Codes
176487

208562

176493

TEKVIZION PVS, INC. CONFIDENTIAL

Description
PSTN End Point makes an inbound call with both
G.711 A-law and G.711 U-law codecs
Device correctly handles non-E.164 number in
outbound Request URI
Lync End Point makes an outbound call of duration >
32 sec to PSTN End Point
Lync End Point makes an outbound call of duration >
32 sec to PSTN End Point when media bypass ON
PBX Phone calls Lync End Point when media bypass
is ENABLED
Device processes a 603 (Declined) response from
Lync End Point
Device processes a 603 (Declined) response from
Lync End Point when media bypass is ON
Device processes busy response from a busy PSTN
End Point

P/F

Comments

P
P
P
P
P
P
P
P

18

Microsoft Unified Communications Open Interoperability Test Report

References

The test strategy and the test cases for the interoperability testing are not attempting to check the complete conformance of these references, but
are used a guide in designing the test cases.

Microsoft Enhanced Gateway Test Plan; Microsoft; http://connect.microsoft.com

Telephony Partner Product Interoperability Specification Enhanced Gateway specification for Connection to Lync Server 2010, Mediation
Server; Microsoft; http://connect.microsoft.com

Microsoft Lync Server 2010, Partner Gateway Audio Quality Specification; Microsoft; http://connect.microsoft.com

TEKVIZION PVS, INC. CONFIDENTIAL

19

You might also like