PhoneSuite - TPI for sterisk cceptance Test pproved (asic CTI), with restrictions
Legal Information / Imprint The information contained in this document reflects the state of knowledge at the time the document was created. Errors and subsequent alterations are reserved. estos GmbH rejects any liability for damage caused by the direct or indirect use of this document. ll brand and product names quoted are trademarks or property of their respective owners. Our current General Terms and Conditions can be found on our website at http://www.estos.com/about-us/imprint.html Copyright estos GmbH. ll rights reserved. estos GmbH Petersbrunner Str. 3a 82319 Starnberg Germany info@estos.de www.estos.de PhoneSuite - TPI for sterisk cceptance Test Page 2 of 27
Table of contents Document Status and Information... 4 1.1. General... 4 1.2. Change History... 4 Preface... 5 2.1. Who should read this Manual... 5 2.2. What is not covered... 5 2.3. Word Usage... 5 Introduction... 6 3.1. ackground Information... 6 3.2. Test Procedure... 6 Exceptions... 7 Specialities... 7 ECST for SIP-Phones... 7 3.3. Example... 7 Software cceptance... 9 4.1. PhoneSuite - TPI for sterisk... 9 Result of cceptance... 9 Reasons of pproval... 9 References... 23 4.2. ProCall Enterprise Remote Office... 24 Result of cceptance... 24 Reasons of pproval... 24 References... 25 4.3. ProCall nalytics... 26 Result of cceptance... 26 Reasons of pproval... 26 References... 27 PhoneSuite - TPI for sterisk cceptance Test Page 3 of 27
Document Status and Information 1.1. General Current Status of the document is summarized here: Project initiative : Kerio Operation, Technologie Partnerschaft (rainworks) Document type : Original author : Thomas Pecher-Wagner Current status : draft Phone : 08151 368 561 61 Email : tp@estos.de 1.2. Change History History of the document is outlined here. Version Date uthor Changes 1.0 18.03.2016 Thomas Pecher-Wagner initial 1.1 25.03.2016 Thomas Pecher-Wagner/ Matthias ecker Final tests PhoneSuite - TPI for sterisk cceptance Test Page 4 of 27
Preface 2.1. Who should read this Manual The intended audience of this documentation is for technical skilled personnel interested in the functional and non-functional specifications of the tested TPI-driver as well as its interoperability with other estos software components. The document describes what telephony related functional and non-functional features are supported by the tested TPI-driver. s the TPI-driver is rarely used as a standalone component, but rather used in combination with certain applications (e.g. Call Center, CTI etc.) it is also in scope of this manual to document the grade of interoperability between the tested component and ProCall Enterprise and its OEM variants. 2.2. What is not covered It is not possible to cover every aspect of the software presented here in this short document. We exclude topics that depend on special-purpose hardware, other software and special features of the respective communication system. It is not likely and not intended that the tested software supports all features mentioned in this document. So this document only states test cases performed successfully or errors. While features not supported by the tested communication system will be counted as neutral (with not influence on the approval). 2.3. Word Usage In this document the usage of must, shall and have to are used in the meaning of mandatory without any exception. Should has the meaning of mandatory but exceptions are possible if desired with an adequate explanatory statement. May and can are used in the meaning of optional. N means not okay because test ended with error or failed and one or more reasons must be commented. means okay because test succeeded or ended with success and additional comment is optional. N/R means not required but a reason must be commented (e.g. Test needed but customer agreed not to perform due to resource lack ). means not applicable e.g. test cannot be done (nothing of that kind implemented in SW or specified in a requirement). PhoneSuite - TPI for sterisk cceptance Test Page 5 of 27
Introduction 3.1. ackground Information There are differences between the actions initiated via TPI or directly at the phone. Contrary to the phone, actions initiated via TPI already provide rich information to the interface (especially conferences). So actions initiated using the phone can lead to different behavior on the TPI interface or in ProCall. 3.2. Test Procedure Prerequisites for the test environment: Connection to outside line t least three (3) connected phones s test application for ECST or any third party TSP estos ephone.exe shall be used. Each test case has to be executed with internal and external participants and should be verified using the phone. The result has to be set in RESULT column using the results set forth above, any observations and errors shall be reported using the COMMENTS column. efore reporting errors the tester should determine whether the error originates from the TSP or PX system. The mention of party 1, 2 or similar in the PRTY column always refers to different line states as stated in the screenshot below. PhoneSuite - TPI for sterisk cceptance Test Page 6 of 27
Exceptions n exception are hidden TPI functions, e.g. different types of call forwarding. Tests, which are not doable due to hidden TPI features, have to be marked accordingly as stated above. Specialities Mostly conferences are displayed differently between the TSP and the phone. The conference itself is only displayed for the starter, not for the participants, they only see a connection to the starter. ECST for SIP-Phones ECST for SIP Phones controls the phones directly, without using a central entity. So there is no connection between calls in different scenarios where multiple phones are involved. Group call scenarios will fail, as calls do not get the same HOSTCLLID. Redirecting of calls will eventually lead to wrong CLLED and REDIRECTING information. 3.3. Example CallState: Dialtone -> Dialing -> Ringback Direction: Outbound 1.1.1 Make Call: calls CallState: Offering PhoneSuite - TPI for sterisk cceptance Test Page 7 of 27
The test is executed in ephone.exe and leads to the positive result below. The next step is to verify the test scenario involving an external participant using ephone.exe. In this case party has to become external participant. Then both test should be executed using the phone. PhoneSuite - TPI for sterisk cceptance Test Page 8 of 27
Software cceptance 4.1. PhoneSuite - TPI for sterisk Result of cceptance Test type : Test of functional and non-functional requirements Install Package : PhoneSuite (TPI for sterisk) 1.1.098 Test object : PhoneSuite (TPI for sterisk) 1.1.098 and Kerio Operator Combination Test environment : Kerio Operator V300, 2.4.5 build 5285, snom820, snom821, Panasonic KX-UT670 Main focus : CTI functionality and interoperability with ProCall Enterprise Overall status : pproval successful with restrictions (asic CTI Function is given) Reasons of pproval Inspection Records Test case Test description Expected result no. Party Call states 1.1 asic test scenarios CallState: Dialtone -> Dialing -> Ringback Direction: Outbound Make Call: 1.1.1 calls CallState: Offering Result Comments Snom 820 to snom 821 PhoneSuite - TPI for sterisk cceptance Test Page 9 of 27
Direction: Outbound 1.1.2 Incoming Call: nswer calls, answers the call Connected: Connected: 1.1.3 Incoming Call: reject calls, rejects No Call No Call CallState: Ringback Direction: Outbound Connected: 1.1.4 Incoming Call: Redirect calls, redirects to C C Redirecting: CallState: Offering CallType: Redirect N Not possible Connected: Redirecting: PhoneSuite - TPI for sterisk cceptance Test Page 10 of 27
Direction: Outbound 1.1.5 Redirected Call: nswer calls, redirects to C, C answers the call C Redirecting: CallType: Redirect N Not possible Connected: Redirecting: 1.1.6 Outbound Call: Hang Up calls, hangs up before connecting. Hang up is possible and working No call anymore 1.1.7 Connected Call: Hang up is connected to, hangs up, Hang up is possible and working 1 CallState: On Hold (no 2) 1.1.8 Connected Call: Hold is connected to, holds the call 2 or CallState: On Hold Pending Transfer CallState: Dial tone 1.1.9 Held call: Unhold holds, Unhold, Connected PhoneSuite - TPI for sterisk cceptance Test Page 11 of 27
No call Call Type: Transfer 1.1.10 Connected Call: blind transfer (single step transfer) connected to, transfers the call to C, C answers C CallState: Offering > Connected Call Type: Transfer wrong ConnectID No usable Redirecting Information Connected: / -> 1 CallState: On Hold Pending Transfer 2 Called: C Connected call: consultation 1.1.11 transfer is connected to, starts a consultation transfer with, C answers (oder On Hold) Connected: C Called: C Connected: PhoneSuite - TPI for sterisk cceptance Test Page 12 of 27
Feature: Merge 1.1.12 Connected call: consultation transfer, merge Like 1.1.11, merges the call between and C C Called: C Connected: 1.1.13 DTMF connected with, starts dial digits Hears DTMF 1.2 Conference PhoneSuite - TPI for sterisk cceptance Test Page 13 of 27
1 CallDirection: Conference 2 CallState: Conferenced Connected: 3 CallState: Conferenced 1.2.1 Conference starts conference with and C Called: C N No conference Support via TPI Via Phone, TPI shows wrong info Connected: C Called: C Connected: 1.2.2 Conference: Participant hangs up conferenced with and C, hangs up C No conference Connected: N No conference Support via TPI 1.2.3 Conference: Starter hangs up conferenced with and C, hangs up,, C Depends on PX settings. Normally and C are connected or the conference is hung up N No conference Support via TPI No conference Conference: Remove Party 1.2.4 conferenced with and C, No call removes C Connected: 1.3 dvanced test scenarios N No conference Support via TPI PhoneSuite - TPI for sterisk cceptance Test Page 14 of 27
1.3.1 1.3.2 1.3.3 1.3.4 Connected and incoming call: busy is connected to, C calls, busy Connected and incoming call: Call waiting is connected to, C calls, call waiting Connected and incoming call: Call waiting and answer is connected to, C calls, call waiting, answers Connected and incoming call: Call waiting and reject is connected to, C calls, call waiting, rejects C 1 Direction: Outbound Connected: (2) 1 CallState: Offering C CallState: usy 1 Direction: Outbound Connected: 2 CallState: Offering (CallType: CampedOn) C CallState: Dial tone -> Dialing -> Ringback Direction: Outbound 1 on Hold 2 Connected to C N C Connected to Connected to N Wrong party is disconnected 1 Not possible with all ECST PhoneSuite - TPI for sterisk cceptance Test Page 15 of 27
Connected to 1.3.3 Connected and incoming call: Call waiting and redirect is connected to, C calls, call waiting, redirects C to D C D Caller: C Connected: D N Maybe misconfiguration at pbx side 1.3.4 Connected call and one on hold: Swap hold is connected to, consultation transfer to C, C answers, 1 2 Holds C Connected to No swap hold available swap hold between and C 1.3.5 Complete Call: Callback is connected to, C calls and busy, C completes call: callback, hangs up C Callback Complete Call: Callback and nswer 1.3.6 is connected to, C calls and busy, C completes call: callback, hangs up, C answers callback C Outbound call to Inbound call from C 1.3.7 Complete Call: Callback, Reject is connected to, C calls and busy, C completes call: callback, hangs up, C rejects callback C No callback PhoneSuite - TPI for sterisk cceptance Test Page 16 of 27
1.3.8 Pickup: direct Call Incoming call on, picks the call CallType: Pickup N CallState: Offering HostCallID: like Caller: C 1.3.9 Call on Group (circular/parallel): incoming C calls group. Call rings on, Called: Group Redirecting: Group CallState: Offering HostCallID: like Wrong CallID and no Redirecting ID (no ProCall nalytics Support) Called: Group Redirecting: Group HostCallID: like 1.2.9 1.3.10 Call on Group: answer C calls group. Call rings on,. answers the call Caller: C Called: Group Wrong CallID and no Redirecting ID (no ProCall nalytics Support) Redirecting: Group D CallType: Pickup 1.3.11 Pickup: Call on Group C calls group. Call rings on,. D picks call from HostCallID: like 1.2.9 Caller: C Called: Group N/R Redirecting: Group or PhoneSuite - TPI for sterisk cceptance Test Page 17 of 27
D CallType: Redirect Redirect: Call on Group C calls group. Call rings on,., 1.3.12 Caller: C redirects to D, Called: Group D answers the call Redirecting: Group or Drop to Extension C calls, Caller: C 1.3.13 Call is dropped to, answers the call Drop to Group C calls, Caller: C 1.3.14 Call is dropped to Group ( is member), answers the call Redirecting: Group or 1.4 Forwarding test scenarios N N Wrong CallID CallerID only after a call is connnected, no Redirecting Information 1.4.1 Call Forwarding: Unconditional Call Forwarding: Unconditional Forwarding is set N Not possible in Phone.exe Possible in ProCall, but no effect Caller: C 1.4.2 Call Forwarding: Unconditional C calls C Caller: C N Not possible in Phone.exe PhoneSuite - TPI for sterisk cceptance Test Page 18 of 27
1.4.3 1.4.4 1.4.5 Call Forwarding: Internal (Unconditional) Call Forwarding: Internal (Unconditional) Call Forwarding: Internal (Unconditional) C calls Call Forwarding: External (Unconditional) Call Forwarding: External (Unconditional) Forwarding is set Caller: C C Caller: C Forwarding is set 1.4.6 Call Forwarding: External (Unconditional) External contact calls Caller: external contact 1.4.7 Call Forwarding: usy Call Forwarding: usy Forwarding is set 1.4.8 1.4.9 Call Forwarding: usy C calls busy Call Forwarding: (internal) usy Call Forwarding: (internal) usy Caller: C C Caller: C Forwarding is set N PhoneSuite - TPI for sterisk cceptance Test Page 19 of 27
1.4.10 1.4.11 Call Forwarding: (internal) usy C calls busy Call Forwarding: (external) usy Call Forwarding: (external) usy Caller: C C Caller: C Forwarding is set 1.4.12 Call Forwarding: (external) usy External contact calls busy Caller: external contact 1.4.13 Call Forwarding: No nswer Call Forwarding: No nswer Forwarding is set 1.4.14 1.4.15 Call Forwarding: No nswer C calls, doesn t answer Call Forwarding: No nswer (internal) Call Forwarding: No nswer (Internal) Caller: C C Caller: C Forwarding is set PhoneSuite - TPI for sterisk cceptance Test Page 20 of 27
1.4.16 1.4.17 1.4.18 1.4.19 1.4.20 Call Forwarding: No nswer (internal) C calls, doesn t answer Call Forwarding: No nswer (external) Call Forwarding: No nswer (external) Call Forwarding: No nswer (external) External contact calls, doesn t answer Call Forwarding: Unconditional / do not disturb do not disturb Call Forwarding: Unconditional / do not disturb C calls Caller: C C Caller: C Forwarding is set Caller: external contact DND is set N C DND tone N 1.4.21 Forwarding: Remove removes forwarding Forwarding is removed N/R 1.4.22 DND: remove removes DND DND is removed N/R Can be set in ProCall, but has no effect 1.5 Special test scenarios (not controllable via ProCall) PhoneSuite - TPI for sterisk cceptance Test Page 21 of 27
1.5.1 Complete Call: Intrude connected to, C calls and it is busy, C intrudes C No change No change Conferenced with, Complete Call: Intrude, Hang up 1.5.2 connected to, C calls and it is busy, C intrudes, C hangs up Complete Call: Intrude, one hangs up 1.5.3 connected to, C calls and it is busy, C intrudes, or hangs up ctive participation connected to, C calls and 1.5.4 it is busy, C participate actively on No change No change C No call,, No call C Conferenced with C and No change C Conferenced with and 1.6 Non-functional test scenarios 1.6. 1 PX restart Line is not in service (SVC) and gets into service after the restart N Seems always to be green (in Service) 1.6.2 Device restart Line is not in service (SVC) and gets into service after the restart N Seems always to be green (in Service) 1.6.3 Connection PX Server is disconnected Line is not in service (SVC) N Seems always to be green (in Service) PhoneSuite - TPI for sterisk cceptance Test Page 22 of 27
1.6.4 Connection PX Server is reestablished Line is in service (SVC) 1.6.5 Snapshot Device In the set time interval the Snapshot can be seen in the log N/R 1.6.6 Read out lines Line is read out ll lines can be read out via PhoneSuite TSP References PhoneSuite - TPI for sterisk cceptance Test Page 23 of 27
4.2. ProCall Enterprise Remote Office Result of cceptance Test type : Test of functional requirements Install Package : Test object : Test environment : Main focus : Overall status : pproval failed Reasons of pproval Test case no. 2 2.1.0 2.2.0 Test description Call Forwarding: Unconditional Call Forwarding: Unconditional to external contact Make Call: calls external contact in hands-free mode Inspection Records Expected result Party Call states Result Comments Forwarding is set N No forwarding The call is set up in hands-free mode of the device Just with snom devices PhoneSuite - TPI for sterisk cceptance Test Page 24 of 27
2.3.0 Consultation Transfer 2 like 2.2.0, consultation transfer to 2nd external participant 1 2 On Hold CallState: Ringback Feature: Merge N 2.4.0 lind Transfer like 2.2.0, call is transferred blind References lind transfer is possible and will be executed Only root number is displayed, without ddi. 2 Please necessarily note FIVE-2190 regarding Ringback PhoneSuite - TPI for sterisk cceptance Test Page 25 of 27
4.3. ProCall nalytics Result of cceptance Test type : Test of functional requirements Install Package : Test object : Test environment : Main focus : Overall status : pproval successful with restrictions Reasons of pproval Inspection Records Test case no. Test description Party Expected result Call states Result Comments 3 CallState: Offering HostCallID: like Caller: C 3.1.0 Call on Group (circular/parallel): incoming C calls group. Call rings on, Called: Group Redirecting: Group CallState: Offering HostCallID: like Called: Group Redirecting: Group PhoneSuite - TPI for sterisk cceptance Test Page 26 of 27
HostCallID: like 3.1.0 3.2.0 Call on Group: nswer C calls group. Call rings on,. answers the call Caller: C Called: Group Redirecting: Group References PhoneSuite - TPI for sterisk cceptance Test Page 27 of 27