zert report c4b xphone osbiz v2 - unifypartnerdialog.unify.com/portal/.../1960_zert_report... · in...

Copyright © Unify GmbH & Co. KG, 2013

Hofmannstr. 63, D-81379 Munich, Germany

All rights reserved.

Unify, OpenScape, OpenStage and HiPath are registered

trademarks of Unify GmbH & Co. KG. All other company, brand,

product and service names are trademarks or registered

trademarks of their respective holders.

Unify Ready Technology connectivity certification

The connectivity of

XPhone Connect V5

developed by C4B Com For Business AG has been certified at the CSTA and SIP Interface of OpenScape Business V2 in accordance with the test report dated October 27, 2015.

C4B Com For Business AG is now entitled to label the above mentioned

product with the Unify Ready emblem.

The test was conducted conforming to DIN EN ISO 9001. This certificate is only valid in conjunction with the full test report and the notes contained

therein. Please consider that the test report only covers the functionality of the interface. The certificate and test report are not good for a

statement of end-to-end functionality.

Munich, October 30th 2015

Luzia Stephan

Director Technology Partner Program

Technology Partner Program

Certification Test Report

C4B Com for Business

XPhone Connect With

Unify

OpenScape Business V2

Authors: Michel Lambrecht

Version: 1.0

Status: Released

Date: 27 Oktober 2015

Copyright © Unify GmbH & Co. KG 2015 All Rights Reserved.

This document contains confidential information that is proprietary to Unify GmbH & Co. KG. No part of its contents may be used, copied, disclosed, or conveyed to any party in any manner whatsoever without prior consent.

Issued by: Unify Inc., Huizingen, Belgium

Certification Test Report Page 2 (of 31) C4B Com for Business / XPhone Connect OpenScape Business V2

1 HISTORY OF CHANGE................................................................................................. 1-4

2 OVERVIEW .................................................................................................................... 2-5

2.1 Test Object ....................................... .................................................................................... 2-5

2.1.1 Basic Equipment ......................................................................................................................... 2-5

2.1.2 XPhone Server ............................................................................................................................ 2-5

2.1.3 XPhone Connect Client ............................................................................................................... 2-6

2.1.4 XPhone Connect Web ................................................................................................................. 2-6

2.2 Test Strategy ..................................... ................................................................................... 2-7

2.2.1 Test Intensity ............................................................................................................................... 2-7

2.2.2 Measuring / Test Instruments ...................................................................................................... 2-7

2.3 Realization Data .................................. ................................................................................. 2-7

2.4 Test Result Summary ............................... ........................................................................... 2-8

2.4.1 Problems ..................................................................................................................................... 2-8

2.4.2 Restrictions ................................................................................................................................. 2-8

2.4.3 Remarks ...................................................................................................................................... 2-8

3 CONFIGURATION ....................................................................................................... 3-10

3.1 OpenScape Business ................................ ........................................................................ 3-10

3.2 XPhone Applications ............................... .......................................................................... 3-14

3.2.1 Configuration Guidelines ........................................................................................................... 3-14

3.2.2 Configuration Advices ................................................................................................................ 3-14

3.3 Configuration Block Diagram ....................... ..................................................................... 3-18

4 TEST RESULTS IN DETAIL ............................ ............................................................ 4-21

4.1 Test with Call Processing ......................... ......................................................................... 4-21

4.1.1 Startup, Configuration and Administration XPhone Server ......................................................... 4-21

4.2 Restart Behavior / Recovery ....................... ...................................................................... 4-21

4.2.1 Recovery from XPhone Client Restart........................................................................................ 4-21

4.2.2 OSBiz restart ............................................................................................................................. 4-21

4.2.3 Device Restart ........................................................................................................................... 4-21

4.2.4 Loss of Input Data for XPhone Server / Client ............................................................................ 4-22

4.3 Functionality ..................................... .................................................................................. 4-22

4.3.1 XPhone Connect Client Telephony Functions ............................................................................ 4-22

4.3.2 XPhone Connect Client Functions ............................................................................................. 4-24

4.3.3 Hotkey Functions ....................................................................................................................... 4-24

4.3.4 Journal Functions ...................................................................................................................... 4-24

4.3.5 MULAP functions ....................................................................................................................... 4-25

4.3.6 UM Functions ............................................................................................................................ 4-25

4.3.7 Anydevice ................................................................................................................................. 4-26


4.3.8 Conference ............................................................................................................................... 4-29

4.4 Remarks ........................................... ................................................................................... 4-29

5 CONFIGURATION DATA ................................ ............................................................ 5-30

5.1 OSBiz ............................................. ..................................................................................... 5-30

5.2 Devices ........................................... .................................................................................... 5-30

5.3 XPhone Connect .................................... ............................................................................ 5-30

6 CONFIRMATION ......................................................................................................... 6-31


1 History of Change

Version Date Changes Author

0.1 September 17, 2015

Initial Creation

Derived from Certification report OpenScape Business V2, Unify GmbH & Co. KG

Michel Lambrecht Unify Belgium E-mail : [email protected] Phone : +32 2 406 7325 Alexander Haugg C4B Com For Business AG E-Mail: [email protected] phone: +49 89 840798-170


update Michel Lambrecht Unify Belgium Alexander Haugg C4B Com For Business AG


update Michel Lambrecht Unify Belgium

0.4 Oktober 23, 2015

Update after review by Alexander Haugg

of C4B

Michel Lambrecht

Unify Belgium

1.0 Oktober 27, 2015

Release document after final review done by Alexander Haugg of C4B

Michel Lambrecht

Unify Belgium


2 Overview

2.1 Test Object

2.1.1 Basic Equipment

Test system: Openscape Business (OSBiz)

Software Versions:

Embedded: OSBiz X5: osbiz_v2_R0.2.1089

Server:

Test Equipment: Embedded: OSBiz X5 with OCAB

Server:

2.1.2 XPhone Server

Cert ification: Test of interface functionality between the OSBiz and the Com For Business XPhone Server. Also failure cases and features are considered.

Test Equipment: Hardware PC or Virtual machine with Windows 2012 R2 Server.

Software Release: Version XPhone Connect V5.0.5.3

HW / FW Release: NA

Manufacturer: C4B AG Gabriele-Münter-Straße 3-5 D - 82110 Germering

Description:

Documentation: See user manual (shipped with systems). Additional info concerning the C4B products is put in attachment or can be found on http://www.c4b.de .

Test Network:

Test Configuration: See picture section 3.2.


2.1.3 XPhone Connect Client

Certification: Test of the CTI functionality and the features of XPhone Connect Client.

Test Equipment: Desktop PCs with Windows 7 64 bit.

Software Releases: XPhone Connect Client V5.0.5.3

HW / FW Release: NA

Manufacturer: C4B AG Gabriele-Münter-Straße 3-5 D - 82110 Germering

Description: XPhone Connect Client is a client application to monitor and handle the phone lines of one or more users. It uses the XPhone Server application to connect to the OSBiz.

These client applications are installed on a desktop PC.

Test Network:

Test Configuration: See picture section 3.2.

2.1.4 XPhone Connect Web

XPhone Connect Web was not tested, since it was not yet released at the time of the certification.


2.2 Test Strategy

The main goal is to test:

• the interfaces between the OSBiz and the C4B products • the system failure/recovery behavior • the main functionality

The interface between the XPhone server and the OSBiz is CSTA based for CTI/Call control and SIP based for Fax, voicemail, AnyDevice and Conference.

2.2.1 Test Intensity

Scopes of the tests are to execute / to verify the solution performs within the limits of the system requirements, targeting the end product. To accomplish this, feature and solution based test cases are created, inspected, and executed under a real system environment (mirroring as close as possible real customer's environment).

Note: The testing of the product with regard to compliance to requirements for Product Safety, EMV, Network Access Interfaces and Radiation Protection were not performed. Unify GmbH therefore assumes no responsibility for the compliance to these requirements.

2.2.2 Measuring / Test Instruments

Tracing and monitoring available on all IP phones, servers, gateways and laptops. No special hardware required.

2.3 Realization Data

Test Preparation: 16 September 2015

Test Duration: 2 days

Test Location:

Guido Gezellestraat 121 B-1654 Huizingen Belgium

Test Personnel:

Michel Lambrecht Professional Services Unify Belgium E-mail : [email protected] Phone : +32 2 406 7325 Alexander Haugg C4B Com For Business AG E-Mail: [email protected] phone: +49 89 840798-170


2.4 Test Result Summary

C4B XPhone Connect has been successfully tested with OSBiz.

2.4.1 Problems

2.4.2 Restrictions

2.4.2.1 Mulap

Monitoring of MULAP-members is supported within the CSTA-limitations of the OSBiz system.

- It is not possible to dial on other devices than the MULAP master device.

- “Do not Disturb” is not possible for MULAP.

- Mulap can not be a member of a group.

2.4.2.2 Camp on at an busy mulap member not signall ed via CSTA

When a mulap member is busy with a call, and a second call is offered, then (when enabled by OSBiz config) the second call will be offered on the already busy mulap member (“camp on” called).

On functional level, this functions fine, but the second call that camps on, is not signalled via CSTA. Due to this, the second call cannot be answered via CSTA.

When the phones are not part of a mulap group, then the second call is correctly signalled via CSTA.

2.4.2.3 Call reject for a connected transferred cal l

“Call reject” for a connected transferred call is not possible.

2.4.2.4 Xphone Connect Web

XPhone Connect Web was not tested, since it was not yet released at the time of the certification.

2.4.3 Remarks

2.4.3.1 Fax SIP RE-INVITE remark

FAX : Both fax via G.711 as also fax via T.38 was OK.

There is only one small remark: when OSBiz has G.711 fax + T.38 enabled, and the XCAPI has only G.711 fax enabled, then the OSBiz will send a SIP RE-INVITE with T.38. Since XCAPI does not have the T.38 enabled, XCAPI needs to react with a “SIP 488 Not Acceptable here” or something similar.

However, the XCAPI reacts with a SIP 200 OK with G.711 voice codecs at the time they receive a SIP RE-INVITE with T.38. This is not an RFC conform answer. Only a small remark, since normally T.38 is enabled or disabled on both sides.

See wireshark packet 10 where a SIP RE-INVITE with media line “image” is offered.


In Wireshark packet 11 the XCAPI answers with a SIP 200 OK with an SDP media line “audio”.

This reply is not RFC conform.

See Wireshark attached :

C4B_wireshark_01_T38_Error_filtered.cap

2.4.3.2 Display text for MWI via CSTA

When MWI is sent via CSTA from C4B to OpenScape Business: For the display message always the „Info-Text 9“ is shown as text.

You can find these text messages at OSBiz Assistant -> Expert Mode -> Telephony Server -> Basic Settings -> Texts

It is however not normal when an MWI is sent to a phone that the “Info-Text 9” is shown on the phone display when you press the envelope key that blinks after an MWI is received.

Furthermore, when you try to call back on the phone via the MWI message on the phone, then the OSBiz Attendant as sender is called, and not the voicemailserver.

2.4.3.3 Callback button to callback to VM after MWI message

When you try to call back on the phone via the MWI message on the phone (envelope key), then the OSBiz Attendant (or intercept) as sender is called, and not the voicemailserver.

2.4.3.4 CLIP during Playback of a new voice message

Test case “Playback of a new voice message at the phone and initiating a call to the caller”:

CLIP is correct when C4B config is done. For the correct CLIP, C4B config needs to configure the VM access number at XPhone connect server -> UM -> Voicemail -> general -> advanced settings -> Name VMPClip : Value e.g. 405 (in our case)


3 Configuration

3.1 OpenScape Business

Configure CSTA link at

Expert Mode -> middleware

Enter here an CSTA user id and a CSTA user password.

Same on C4B side.

Status can be seen at Middleware –W CSTA Service Provider -> CSTA service provider (CSP) statistics :


TDM user 390

TDM user 391

HFA user 392

SIP user 393


For the native SIP Trunk, don’t forget to “add native SIP server Trunk user”, otherwise the OSBiz does not answer on the SIP OPTION messages, and the SIP trunk will not get active.

When more than one SIP trunk to C4B is needed, you need to use a unique SIP port number for each native SIP trunk


Settings native SIP trunk1 :

Settings native SIP Trunk 2 to XCAPI :


3.2 XPhone Applications

3.2.1 Configuration Guidelines

C4B XPhone was configured by C4B personnel for the certification test due to system settings of the switch in the certification lab.

The XPhone server application runs on a Windows 2008R2 or more recent server platform (64 bit only).

The XPhone client applications run on Windows Operating Systems ranging from Windows Windows 7 or more recent (32 or 64 bit).

3.2.2 Configuration Advices

3.2.2.1 CSTA Link

CSTA Username/password must be configured on both systems identically.


3.2.2.2 MULAP: XPhone server line configuration

In XPhone server line configuration, the MULAP group number must be configured as a line device (not the devices as in previous versions).

3.2.2.3 XCAPI Link

The Configuration of OSBiz/Booster server is described in the document “XP_CTI_OpenscapeBusiness_DE.pdf ” and “XP_UM_OpenscapeBusiness_DE.pdf” which can be found on XPhone Server / Client DVD.

3.2.2.4 QOS settings

The SIP and RTP packets sent by C4B do not have any DSCP QOS marking (Differentiated Services Code Point).

See also

https://en.wikipedia.org/wiki/Differentiated_services

Due to this, the SIP and RTP packets will never get priority on the LAN (to keep the round trip delay low), and they are also vulnerable to packet drop.

To get priority on the LAN, you better TAG the SIP and RTP packets with the appropriate DSCP value.

This can be done easily.

On your C4B Windows server (e.g. Windows 2012 server or so), go to the start menu, and select “Run”

Then execute “Gpedit.msc” (Full name : Group Policy Editor Microsoft Management Console)

Go to Computer configuration -> Windows settings -> Policy Based QOS

Add new policy “QOS_SIP”

Executable : xxx.exe (exe name of Voip application)

Protocol : UDP (or UDP/TCP)

Dest port : 5060:5069

Value : 26 (= AF31 = Assured forwarding 31)

Add new policy “QOS_RTP”


Protocol : UDP (RTP is always UDP)

Src port : 30000:31000

Value : 46 (EF = Expedited Forwarding)


Add new policy “QOS_T38”


Protocol : UDP

Src port : xxx:yyy

Value : 46 (= EF = Expedited Forwarding)

After this, make a wireshark trace of a basic call.

Select a SIP packet, and look at “Internet Protocol Version 4” -> “Differentiated Services Field”

Look if the DSCP value is AF31 both for the SIP packet sent by C4B.

Now have a look at an RTP packet, and check if the DSCP value of the RTP packets sent by C4B are marked with Expedited Forwarding.

Important remark: the customer must configure the DSCP QOS on the LAN switches so that SIP and RTP/T.38 packets get priority on the LAN. Also when DSCP QOS queues are not correct configurated on the LAN switches, then the LAN switch will send DSCP value zero when he forwards any tagged packet, so DSCP gets lost in this case, which is not good.


3.2.2.5 XCAPI Config

Activation Softfax-Feature in XCAPI. An additional setting in the OSBiz may be required. No setting in the C4B software is required.


But we have to activate the ECT simulation to enable call transfers by XCAPI which is needed for the “Representative” feature for example.

3.3 Configuration Block Diagram

General System Architecture:


CSTA architecture for “CTI test scenario a”: Single OSBiz system

Openscape Business X

Master OCAB

XPhone Connect

Server XPhone Connect Clients

IP Phone

PSTN

SIP/ISDN

Digital Phone

SIP

CSTA

OSBiz Xx

OCAB

XPhone server

CSTA


IP architecture for “UM, AnyDevice or Conference test scenario”:

PSTN

OSBiz

XPhone server w/XCAPI

SIP


4 Test Results in detail

4.1 Test with Call Processing

This test part checks the correct connection of the OSBiz system to the C4B XPhone Connect computing system. For that different call scenarios are executed.

4.1.1 Startup, Configuration and Administration XPh one Server

No Test Procedure Expected Result Result 1. Power-on and Startup Startup is successful.

Configuration is successful and in case there already was a stored configuration it still exists

OK

2. Specify client capabilities System capabilities and settings are done for the specific test environment

OK

3. Team Configuration OSBiz parties can be configured into XPhone Connect Client

OK

4.2 Restart Behavior / Recovery

4.2.1 Recovery from XPhone Client Restart

No Test Procedure Expected Result Result 4. Restart on C4B XPhone Connect

Client Client C4B XPhone Client comes back to work in case it is included in auto start procedures. The actual configuration still exists.

OK

4.2.2 OSBiz restart

No Test Procedure Expected Result Result 5. Soft Restart of OSBiz system(s) Client shows inoperability. After restart the

client comes back to work without manual interferences.

OK

6. Power off of OSBiz system(s) Client shows inoperability. After restart the client comes back to work without manual interferences.

OK

4.2.3 Device Restart

No Test Procedure Expected Result Result


7. Pull and push SLMO card with the configured digital subscriber 100 and 101.

Subscriber 100/101 shows inoperability. After reload of the card, the subscriber comes back into service without manual interferences.

OSBiz S not possible

8. Pull and push line of digital subscriber.

Subscriber 100 shows inoperability. After reconnection, the subscriber comes back to work without manual interferences.

OSBiz S not possible

9. Pull LAN Cable from IP Phone No unregister message is sent for half an hour, the XPhone client application will not respond

OK

4.2.4 Loss of Input Data for XPhone Server / Client

No Test Procedure Expected Result Result 10. Disconnect LAN cable of XPhone

Client and put it back again The client displays the broken connection. After re-establishing the link the client comes up again.

OK

11. Disconnect LAN cable of XPhone Server and put it back again

The client continues to work but shows inoperability. After re-establishing the link the client continues work.

OK

12. Disconnect LAN signalling cable between LAN switches and OSBiz and put it back again

The client continues to work but shows inoperability. After re-establishing the link the client continues work.

OK

4.3 Functionality

Test results will be documented for “CTI scenario b” single Station and MULAP (see architecture diagram).

4.3.1 XPhone Connect Client Telephony Functions

No Test Procedure Expected Result Result Phone/Mulap

13. XPhone Connect Client initiates an internal call.

Call is set up OK/ OK

14. XPhone Connect Client initiates an external call.

Call is set up OK/ OK

15. XPhone Connect Client initiates a consultation internal/external

Consultation status is reached OK/ OK

16. XPhone Connect Client transfers the call Call is transferred OK/ OK

17. XPhone Connect Client chooses to toggle Toggling between the two calls OK/ OK

18. XPhone Connect Client chooses to initiate a conference (internal and external)

Conference is established OK/ OK



19. XPhone Connect Client chooses to initiate a conference (internal)


20. XPhone Connect Client creates a conference with external parties (using PSTN trunk)


21. XPhone Connect Client chooses to release the call

Call is released OK/ OK

22. XPhone Connect Client accepts an incoming call.

Call is accepted, XPhone Connect Client is in conversation status

OK/ OK

23. XPhone Connect Client is busy, another call camps on. The user chooses to accept this call

Call is accepted, original party is put on hold. XPhone Connect Client is in conversation status

OK/ NOK Test fails

when user is a MULAP member

24. XPhone Connect Client redirects an incoming internal call to any valid number (team member or not team member)

Call is redirected, there it starts ringing

OK/ OK

25. XPhone Connect Client redirects an incoming external call to any valid number (team member or not team member)

Call is redirected, there it starts ringing

OK/ OK

26. XPhone Connect Client calls a hunting group. A member of the hunting group takes the call.

User is connected to client. Hint: see 2.4.2 Restrictions

OK/ NA

27. XPhone Connect Client is member of a hunting group. It gets a call over the hunting group and takes the call.

Client is connected to the caller of the hunting group. Hint: see 2.4.2 Restrictions

OK/ NA

28. XPhone Connect Client gets an incoming call. User decides to reject.

Call is cleared. Hint: see 2.4.2 Restrictions

OK/ OK

29. A User has call forwarding enabled to XPhone user. XPhone Connect Client correctly displays the forwarded call.

XPhone Connect Client detects the forwarded call

OK/ OK

30. XPhone Connect Client with server based features enabled) sets call forwarding options for the device.

Call forwarding notification is visible on the phone.

OK/ OK

31. XPhone Connect Client with server based features enabled) sets do not disturb option for the device.

Do not disturb notification is visible on the phone. Hint: see 2.4.2 Restrictions

OK/ NA


4.3.2 XPhone Connect Client Functions

The XPhone connect Client provides additional functionality. These tests are performed with external lines.


32. XPhone Connect Client (monitoring multiple phones) picks incoming call from team member.

Call is picked, status is shown correctly. OK/ OK

33. XPhone Connect Client (monitoring multiple phones) diverts a call to team member.

Call is diverted to team member. OK/ OK

34. XPhone Connect Client (monitoring multiple phones) sees CF from team member

CF arrow is visible on that team member. OK/ OK

35. Incoming calls to team members. Number of incoming ringing call is visible by red blinking bars on the toolbar.

OK/ OK

36. A Speed Dial button is created on the toolbar directing to external number. You can divert the call with the Speed Dial Button

OK/ OK

37. A consultation is setup using the toolbar.

Consultation succeeds OK/ OK

38. XPhone Connect Client tries to execute a directed Call Pickup.

OK/ OK

4.3.3 Hotkey Functions

For hot key functionality the key combination ‘ALT’ – F12 is used.


39. XPhone Connect Client dials external number out of a Word document

The call is set up. OK/ OK

40. XPhone Connect Client accepts incoming internal call with ALT+F12

The call is accepted OK/ OK

41. XPhone Connect Client chooses a text string out of a Word document that matches to one or more Names of the phone book. ( Only with “Last Name” )

All matches of the phone book are presented.

OK/ OK

4.3.4 Journal Functions

For journal functions the test cases should show that the basic activities are recognized and are shown and can be used for further activities.


42. XPhone Connect Client logs incoming and outgoing calls, external as well as internal. The call log is

The log shows the call data correctly OK/ OK


divided in Pending, Completed and Missed Calls

4.3.5 MULAP functions


43. Perform test steps 13 to 44 on a MULAP group.

Same results as with normal devices.

Call control functions (dial, accept) on idle MULAP lines will always address the MULAP master device.

Call control functions on active MULAP lines (i.e. drop) will address the active device.

Behaviour is determined by OSBiz MULAP/CSTA specification.

OK

4.3.6 UM Functions

XPhone UM Server will be connected by SIP (native)-Trunking with OSBiz over XCAPI (product of TE-Systems).


44. User calls voice portal of XPhone UM Server and wants to get access to his voice mailbox.

The user gets access to his voice mailbox.

OK

45. User activates Call Forwarding to the voice portal and gets an incoming call (internal and external).

Info: The feature “secret number” can be activated.

The caller will be transferred to the voice mailbox and can leave a message.

OK

46. A new voicemail message was left. XPhone Client signals a new voicemail message.

OK

47. A new voicemail message was left. Will be signalled at the phone by (MWI).

OK

48. Playback of a voice message. The voice message can be played back on XPhone Client and phone.

OK

49. Playback of a new voice message at the phone and initiating a call to the caller.

CLIP is correct.

For the correct CLIP, C4B config needs to

The user will be connected to the caller.

OK



configure the VM access number at XPhone connect server -> UM -> Voicemail -> genereal -> advanced settings -> Name VMPClip : Value e.g. 405 (in our case)

50. User has activated the feature Representative in his voice mailbox. (internal and external) During the announcement, the caller can be transferred to the representative by dialling the digit 1.

Caller will be transferred to the representative.

OK

51. Sending a Fax by XPhone Client (to internal and external)

OK

52. Receiving a Fax by XPhone Client (from internal and external)

OK

53. Transferring a Fax by XPhone Client

OK

4.3.7 Anydevice

Remark : At external calls, the provider often has no "clip no screening". In some testcases, the provider overrules the CLIP with the head number in case a calling party number is used which is not part of the DID range. This is however due to the provider settings.


54. Basic phone. Outbound Call. Internal – internal.

OK

55. Basic phone. Outbound Call "AssistedDial".

Internal – internal.

OK

56. Basic phone. Inbound Call.


OK

57. Basic phone. Answer Call (possible via "AnyDevice" only!) .


OK

58. Basic phone. Hold Call.


OK



59. Basic phone. Drop Call.


OK

60. Basic phone. Reject Call.


OK

61. Basic phone. Calling Number include the provider prefix outbound.


OK

62. Basic phone. Calling Number include the provider prefix inbound.


OK

63. Basic phone. Outbound Call.

External – External.

OK

64. Basic phone. Outbound Call "AssistedDial".


OK

65. Basic phone. Inbound Call.


OK

66. Basic phone. Answer Call (possible via "AnyDevice" only!).


OK

67. Basic phone. Hold Call.


OK

68. Basic phone. Drop Call.


OK

69. Basic phone. Reject Call.


OK

70. Basic phone. Calling Number include the provider prefix outbound.


OK



71. Basic phone. Calling Number include the provider prefix inbound.


OK

72. Consultation: Consultation initiated by connected call.


OK

73. Consultation: consulttion initiated by hold call.


OK

74. Consultation: Swap hold.


OK

75. Consultation: Disconnect connected call.

Internal – internal

OK

76. Consultation: Hold partner hang up.


OK

77. Consultation: Consulted partner reject the call.


OK

78. Transfer: Transfer Consultation OK

79. Transfer: Blind Transfer OK

80. Transfer: Redirect / Deflect OK

81. Specials: Consultation -> Conference NOK conf setup failed. Internal C4B analysis needed.


4.3.8 Conference


82. Call into the Conference.

Automatic Authentification.

From external.

OK



From internal.

OK



Via Anydevice.

OK


Automatic via PIN.

From external.

OK


Automatic via PIN.

From internal.

OK


Automatic via PIN..

Via Anydevice.

OK

4.4 Remarks

Meanings of Abbreviations:

OK Test case successful

NOK Test case NOT successful

NA Test case not applicable

NP Test case not processed

NS Situation not supplied

N *X Error / restriction with description

* X Remark to Functionality


5 Configuration Data

5.1 OSBiz

The Master Node OSBiz X5 with OCAB

5.2 Devices

Used Devices are TDM/ HFA.

5.3 XPhone Connect

Conduct a normal installation of the XPhone Server / XPhone Clients.


6 Confirmation

Testing personnel confirms that the all test cases were performed and that the results were as described in this document. The testing personnel confirm test duration from 16 September, 2015 – 17 September.

Alexander Haugg Michel Lambrecht C4B Com For Business AG Unify

zert report c4b xphone osbiz v2 - unifypartnerdialog.unify.com/portal/.../1960_zert_report... · in...

Documents