ALE Application Partner Program Inter-Working Report

Transcription

1 ALE Application Partner Program Inter-Working Report Partner: Vidyo Application type: video conferencing systems Application name: VidyoWorks Platform Alcatel-Lucent Enterprise Platform: OmniPCX Enterprise The product and release listed have been tested with the Alcatel-Lucent Enterprise Communication Platform and the release specified hereinafter. The tests concern only the inter-working between the AAPP member s product and the Alcatel-Lucent Enterprise Communication Platform. The inter-working report is valid until the AAPP member s product issues a new major release of such product (incorporating new features or functionality), or until ALE International issues a new major release of such Alcatel-Lucent Enterprise product (incorporating new features or functionalities), whichever first occurs. ALE INTERNATIONAL MAKES NO REPRESENTATIONS, WARRANTIES OR CONDITIONS WITH RESPECT TO THE APPLICATION PARTNER PRODUCT. WITHOUT LIMITING THE GENERALITY OF THE FOREGOING, ALE INTERNATIONAL HEREBY EXPRESSLY DISCLAIMS ANY AND ALL REPRESENTATIONS, WARRANTIES OR CONDITIONS OF ANY NATURE WHATSOEVER AS TO THE AAPP MEMBER S PRODUCT INCLUDING WITHOUT LIMITATION THE IMPLIED WARRANTIES OF MERCHANTABILITY, NON INFRINGEMENT OR FITNESS FOR A PARTICULAR PURPOSE AND ALE INTERNATIONAL FURTHER SHALL HAVE NO LIABILITY TO AAPP MEMBER OR ANY OTHER PARTY ARISING FROM OR RELATED IN ANY MANNER TO THIS CERTIFICATE.

2 Certification overview Date of the certification July-August 2016 ALE International representative AAPP member representative Alcatel-Lucent Enterprise Communication Platform Alcatel-Lucent Enterprise Communication Platform release AAPP member application release Application Category Benoit Trinité Tzachi Levy OmniPCX Enterprise R11.2 (l e) Vidyo Manager TAG_VC3_3_6_025 Vidyo Router TAG_VC3_3_6_025 Vidyo Gateway 3.2.0(264) Vidyo Desktop (017) Conferencing (audio & video) Collaboration & UC Author(s): Reviewer(s): Benoit Trinité Rachid Himmi Revision History Edition 1: creation of the document August 2016 results Passed Refused Postponed Passed with restrictions Refer to the section 6 for a summary of the test results. IWR validity extension None

3 AAPP Member Contact Information Contact name: Title: Address: Tzachi Levy VP Technology Sales Rakefet 77 Matan Zip Code: City: Matan Country: Israel Phone: Fax: NA Mobile Phone: Web site: address:

4 TABLE OF CONTENTS 1 INTRODUCTION VALIDITY OF THE INTERWORKING REPORT LIMITS OF THE TECHNICAL SUPPORT CASE OF ADDITIONAL THIRD PARTY APPLICATIONS APPLICATION INFORMATION TEST ENVIRONMENT HARDWARE CONFIGURATION SOFTWARE CONFIGURATION SUMMARY OF TEST RESULTS SUMMARY OF MAIN FUNCTIONS SUPPORTED SUMMARY OF PROBLEMS SUMMARY OF LIMITATIONS NOTES, REMARKS TEST RESULT TEMPLATE TEST RESULTS THIRD PARTY VIDEO SYSTEM PROTOCOLS CONFIGURATION SIP REGISTRATION (OPTIONAL) GLOBAL REGISTRATION OTHER SIP REGISTRATIONS (OPTIONAL) SIP TRUNK (OPTIONAL) CAPABILITIES Basic incoming Call Basic Outgoing Call Video Escalation SIP REFER Support SIP Replaces Support DTMF Session Timer LD/SD/HD Video Quality level PCC MakeCall Automatic answer H.264 specificities observed CALL FROM OXE EXT. TO 3RD PARTY VIDEO SYSTEM Place an Audio call to Third party video System Place an Audio/Video call to the Third party video System Dial By Name Call-Log, Redial List CALL FROM 3RD PARTY VIDEO SYSTEM TO OXE EXT Receive an Audio call Receive an Audio/Video call Dial by Name Call-Log, Redial List MID CALL SERVICES Escalate an Audio call to Audio/Video Third party video System Holds/Retrieves communication Endpoint Holds/Retrieves the communication DTMF Call transfer from OXE extension: Blind transfer Call transfer from OXE extension: Attended transfer Call transfer from Third party video System: transfer (blind)... 41

5 8.8.8 Call transfer from Third party video System: transfer (Other) OXE CONFERENCE party conference from IP Touch party conference from Mastered Conference Meet-me conference OT SCHEDULED CONFERENCE Video Dial-in Audio Dial-in then escalation Audio Dial-out from OTC Web then escalation Add Participant on the fly from OTC PC Dropped from the conference by OTC PC TUI Menu Mix of H.264 Level, OT Conference configured to support HD THIRD PARTY VIDEO SYSTEM CONFERENCE Audio Dial-in, then Video escalation Audio/Video Dial-out from Third party Video System Dropped from the conference by Third Party Video System TUI Menu Blast Call CONTENT SHARING REMOTE CALL CONTROL OXE ADVANCED TELEPHONY SERVICES ANONYMOUS CALL ABANDONED CALL, CALL ROUTING ERROR TONES IPV CAC SECURITY OXE H.A INFORMATION FOR END USERS ROBUSTNESS & AGEING NETWORK IMPAIRMENT & AUDIO/VIDEO QUALITY APPENDIX A : AAPP MEMBER S APPLICATION DESCRIPTION APPENDIX B: CONFIGURATION REQUIREMENTS OF THE AAPP MEMBER S APPLICATION TENANT EXTENSION PREFIX VIDYO GATEWAY ROUTING CALL FROM VIDYO SOLUTION TO OXE CALL SERVER EXTENSIONS VIDYO CALL TYPE APPENDIX C: ALCATEL-LUCENT ENTERPRISE COMMUNICATION PLATFORM: CONFIGURATION REQUIREMENTS APPENDIX D: AAPP MEMBER S ESCALATION PROCESS APPENDIX E: AAPP PROGRAM ALCATEL-LUCENT APPLICATION PARTNER PROGRAM (AAPP) ENTERPRISE.ALCATEL-LUCENT.COM APPENDIX F: AAPP ESCALATION PROCESS INTRODUCTION ESCALATION IN CASE OF A VALID INTER-WORKING REPORT ESCALATION IN ALL OTHER CASES TECHNICAL SUPPORT ACCESS... 64

6 1 Introduction This document is the result of the certification tests performed between the AAPP member s application and Alcatel-Lucent Enterprise s platform. It certifies proper inter-working with the AAPP member s application. Information contained in this document is believed to be accurate and reliable at the time of printing. However, due to ongoing product improvements and revisions, ALE International cannot guarantee accuracy of printed material after the date of certification nor can it accept responsibility for errors or omissions. Updates to this document can be viewed on: - the Technical Support page of the Enterprise Business Portal ( in the Application Partner Interworking Reports corner (restricted to Business Partners) - the Application Partner portal ( with free access.

7 2 Validity of the InterWorking Report This InterWorking report specifies the products and releases which have been certified. This inter-working report is valid unless specified until the AAPP member issues a new major release of such product (incorporating new features or functionalities), or until ALE International issues a new major release of such Alcatel-Lucent Enterprise product (incorporating new features or functionalities), whichever first occurs. A new release is identified as following: a Major Release is any x. enumerated release. Example Product 1.0 is a major product release. a Minor Release is any x.y enumerated release. Example Product 1.1 is a minor product release The validity of the InterWorking report can be extended to upper major releases, if for example the interface didn t evolve, or to other products of the same family range. Please refer to the IWR validity extension chapter at the beginning of the report. Note: The InterWorking report becomes automatically obsolete when the mentioned product releases are end of life.

8 3 Limits of the Technical support For certified AAPP applications, Technical support will be provided within the scope of the features which have been certified in the InterWorking report. The scope is defined by the InterWorking report via the tests cases which have been performed, the conditions and the perimeter of the testing and identified limitations. All those details are documented in the IWR. The Business Partner must verify an InterWorking Report (see above Validity of the InterWorking Report) is valid and that the deployment follows all recommendations and prerequisites described in the InterWorking Report. The certification does not verify the functional achievement of the AAPP member s application as well as it does not cover load capacity checks, race conditions and generally speaking any real customer's site conditions. Any possible issue will require first to be addressed and analyzed by the AAPP member before being escalated to ALE International. Access to technical support by the Business Partner requires a valid ALE maintenance contract For details on all cases (3 rd party application certified or not, request outside the scope of this IWR, etc.), please refer to Appendix F AAPP Escalation Process. 3.1 of additional Third party applications In case at a customer site an additional third party application NOT provided by ALE International is included in the solution between the certified Alcatel-Lucent Enterprise and AAPP member products such as a Session Border Controller or a firewall for example, ALE International will consider that situation as to that where no IWR exists. ALE International will handle this situation accordingly (for more details, please refer to Appendix F AAPP Escalation Process ).

9 4 Application information Application commercial name: Video Conferencing Systems Application version: 3.4 Interface type: SIP Brief application description: Vidyo delivers video conferencing solutions to improve the way people communicate and collaborate in all walks of life like practical and engaging solutions to enterprises, healthh care providers, educational institutions, government agencies, financial services firms, and technology companies in every corner of the world. The applications and real-world benefits of VidyoConferencingTM are boundless.

10 5 environment Figure 1 environment OTC PC OXE Voice Ext. OXE Meeting Room Ext. PSTN Extension MyIC Phone 8088 Data Center OTMS OXE Node1 OXE Node2 Vidyo System (Manager, Router, Gateway Third Party Video Clients Vidyo Desktop

11 5.1 Hardware configuration Third Party o ESXi running - Vidyo Manager - Vidyo Router - Vidyo Gateway o Vidyo Desktop OmniPCX Entreprise: o OXE Call Server o IP Touch digital sets o 8088 ISDN Interface 5.2 Software configuration OmniPCX Enterprise Release 11.2 (l e) MyIC Phone 8088 Release R Partner Application Vidyo : Release : o Vidyo Manager TAG_VC3_3_6_025 o Vidyo Router TAG_VC3_3_6_025 o Vidyo Gateway 3.2.0(264) o Vidyo Dekstop (017)

12 6 Summary of test results 6.1 Summary of main functions supported Simple call from OXE to Vidyo system (P2P or Conference Call Mode) Simple call from Vidyo system to OXE Video between 8088 (Registered as SIP Device on OXE) and Vidyo system (P2P or Conference Call Mode, direct A/V call or Video escalation) Content sharing initiated from Vidyo side is seen on 8088 OXE H.A. supported Hold/Retrieve initiated on OXE side 6.2 Summary of problems Call transfer initiated one OXE side and any other complex telephony feature initiated on OXE side Call forward and overflow performed on OXE side. 6.3 Summary of limitations Audio : Only G.711 No DTMF from Vidyo to OXE No SIP authentication interop, SIP Ext Gateway IP based control is used on OXE side. No way for Vidyo to join an OTMS conference (because of DTMF) Rare robustness issue 6.4 Notes, remarks Vidyo does not support properly SIP REFER mechanism in OXE environment.

13 7 Result Template The results are presented as indicated in the example below: 1 case 1 Action Expected result N/A OK NOK Comment case 2 Action Expected result case 3 Action Expected result case 4 Action Expected result The application waits for PBX timer or phone set hangs up Relevant only if the CTI interface is a direct CSTA link No indication, no error message : a feature testing may comprise multiple steps depending on its complexity. Each step has to be completed successfully in order to conform to the test. : describes the test case with the detail of the main steps to be executed the and the expected result N/A: when checked, means the test case is not applicable in the scope of the application OK: when checked, means the test case performs as expected NOK: when checked, means the test case has failed. In that case, describe in the field Comment the reason for the failure and the reference number of the issue either on ALE International side or on AAPP member side Comment: to be filled in with any relevant comment. Mandatory in case a test has failed especially the reference number of the issue.

14 8 Results 8.1 Third party Video System Protocols configuration Purpose of this set of test is to check for availability of minimum set of parameters that are needed to properly interface the Third party video System Vidyo to an OXE server. N/A OK NOK Comment 1.1 Enable SIP stack w/o registration SIP global registration and SIP Digest authentication parameters. Other SIP registrations (per room,endpoints, ) and SIP Digest authentication parameters. NA NA 1.4 SIP Authentication for incoming call NA 1.5 Support for UDP/TCP.Only TCP is tested 1.6 Configuration for Codecs No G Configuration for DTMF (RFC2833/4733, Patload Type) No way to configure DTMF PT

15 8.2 SIP Registration (optional) Global Registration Purpose of this set of test is to check SIP Registration of the Third party video System to the OXE server. N/A OK NOK Comment First SIP Rergistration, SIP ExtGw is switched IN- Service (DNS A Record) Contact header from received Vidyo (IP/Domain Name) NA NA 2.3 Expires header received from Vidyo NA 2.4 Registration refresh NA 2.5 Un-registration, SIP ExtGw switched ouf of service NA 2.6 Registration authentication NA 2.7 Other specific REGISTER content Details on REGISTER message:

16 8.3 Other SIP Registrations (optional) Purpose of this set of test is to check Other SIP Registrations of the Third party video System to an OXE server (Per room, endpoints, ). N/A OK NOK Comment 3.1 First SIP Rergistration, Registrar is updated (DNS A Record) NA 3.2 Contact header from received Vidyo(IP/Domain Name) NA 3.3 Expires header received from Vidyo NA 3.4 Registration refresh NA 3.5 Un-registration, Registrar is updated NA 3.6 Registration authentication NA 3.7 Other specific REGISTER content Details on REGISTER message:

17 8.4 SIP Trunk (optional) Purpose of this set of test is to check SIP Trunk between OXE Server and Third party video System. N/A OK NOK Comment 4.1 OPTION msg responsed, IP address 4.2 OPTION msg responded, DNS A Record 4.3 OPTION msg responded, DNS SRV Record Not ed 4.4 Failover, OPTION msg responsed, DNS A Record Not ed 4.5 Failover, OPTION msg responsed, DNS SRV Record Not ed

18 8.5 Capabilities Purpose of set of this set of test is to identify SIP Profile to be used with the Third Party Video System Basic incoming Call For this set of tests, we use 8088 endpoint equipment as the remote party N/A OK NOK Comment An Audio/Video call is established from Third party video System Vidyo. To OXE 8088 SIP Device Headers (From, Contact, Allow, Supported, Accepted, Session-Expires, Via) sent by Vidyo SDP Offer content (codecs, feature s options) sent by Vidyo Contact with IP address G.711, G.722, H.264 Level 3.1, PM0, PLI, FIR, TMMBR. No generic Nack Call remains established after 1 minute List of identified Audio and Video capabilities (Audio codec and details, video codec and details, profiles, level, constraints, packet mode, RTPC Feedback, ) : INVITE sip: @ SIP/2.0 Via: SIP/2.0/TCP :5060;rport;branch=z9hG4bK From: " Radiologist" <sip:770002@ :5060>;tag= To: <sip: @ > Call-ID: CSeq: 20 INVITE Contact: <sip:770002@ :51276;transport=tcp> Content-Type: application/sdp Allow: INVITE,BYE,CANCEL,ACK,INFO,UPDATE Max-Forwards: 70 User-Agent: VidyoGateway Content-Length: 452 v=0 o=vidyogateway IN IP s=c=in IP b=as:1600 t=0 0 m=audio RTP/AVP a=rtpmap:9 G722/8000 a=rtpmap:0 PCMU/8000 a=rtpmap:8 PCMA/8000 a=sendrecv a=rtpmap:110 telephone-event/8000 m=video RTP/AVP 99 a=rtpmap:99 H264/90000 a=fmtp:99 profile-level-id=42801f;packetization-mode=0 a=sendrecv a=content:main a=rtcp-fb:* ccm fir a=rtcp-fb:* nack pli a=rtcp-fb:* ccm tmmbr

19 8.5.2 Basic Outgoing Call For this set of tests, we use a 8088 equipment as the remote party (standalone device) and Vidyo Conference Call Type N/A OK NOK Comment An Audio/Video call is established from 8088 endpoint (registered as a SIP Device on OXE Node 1) to Third party video System Vidyo. INVITE successfully parsed by the Third party video System. G.722 not offered by OXE in this case. G.729 added to SDP Optionnal : Third party video System Vidyo performs a SIP digest authentication. Authentication provided by OXE is accepted. NA Ringing state : 180 Ringing provided, content (SDP or no SDP, 100rel) Call answered : 200 OK provided, Headers content (From, contact, Allow, Supported, Accepted, Session- Expires) SDP Answer content (codecs, feature s options) 180 Ringing provided, even in Conference Call Type. No COLP Only G.711 is available Call remains established after 1 minute INVITE sent by OXE : INVITE sip:770002@ ;transport=tcp;user=phone SIP/2.0 Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, INFO Supported: replaces,timer,path,100rel User-Agent: OmniPCX Enterprise R11.2 l e Session-Expires: 1800;refresher=uac Min-SE: 900 P-Asserted-entity: "Wayne John" <sip: @ ;user=phone> Content-Type: application/sdp To: <sip:770002@ ;user=phone> From: "Wayne John" <sip: @ ;user=phone>;tag=55f5db04eea377a b1cf8647f Contact: <sip: @ ;transport=tcp> Call-ID: 72dc7ff5ffe456ccb6110e515760aba7@ CSeq: INVITE Via: SIP/2.0/TCP ;branch=z9hG4bKe51a516489a516b2ade86d316c5035a2 Max-Forwards: 70 Content-Length: 291 v=0 o=oxe IN IP s=c=in IP t=0 0 m=audio 6000 RTP/AVP a=sendrecv a=rtpmap:8 PCMA/8000 a=ptime:20 a=maxptime:30 a=rtpmap:18 G729/8000

20 a=fmtp:18 annexb=no a=ptime:20 a=maxptime:40 a=rtpmap:101 telephone-event/ Ringing received from third party video system : SIP/ Ringing Via: SIP/2.0/TCP ;branch=z9hG4bKe51a516489a516b2ade86d316c5035a2 From: "Wayne John" <sip: @ ;user=phone>;tag=55f5db04eea377a b1cf8647f To: <sip:770002@ ;user=phone>;tag= Call-ID: 72dc7ff5ffe456ccb6110e515760aba7@ CSeq: INVITE Contact: <sip:770002@ :5060;transport=tcp> User-Agent: VidyoGateway Content-Length: 0 200OK received from third party video system: SIP/ OK Via: SIP/2.0/TCP ;branch=z9hG4bKe51a516489a516b2ade86d316c5035a2 From: "Wayne John" <sip: @ ;user=phone>;tag=55f5db04eea377a b1cf8647f To: <sip:770002@ ;user=phone>;tag= Call-ID: 72dc7ff5ffe456ccb6110e515760aba7@ CSeq: INVITE Contact: <sip:770002@ :5060;transport=tcp> Content-Type: application/sdp User-Agent: VidyoGateway Content-Length: 203 v=0 o=vidyogateway IN IP s=c=in IP b=as:1600 t=0 0 m=audio RTP/AVP a=rtpmap:8 PCMA/8000 a=sendrecv a=rtpmap:101 telephone-event/8000

21 8.5.3 Video Escalation For this set of tests, we use a 8088 SIP Device endpoint equipment as the remote party. N/A OK NOK Comment An Audio call established from 8088 SIP Device on Node 1 to Third party video System Vidyo escalates to Video. reinvite successfully parsed by the Third party video System Vidyo Video MCU rejects escalation (no more ports, incompatible offer), rejection is done through SDP by setting video port to 0. For the test, Vidyo gateway configured to support only H.263. OKBut Video part is just missing in SDP answer, which is not legal Viceo MCU accept the video escalation Escalation answered : 200 OK provided, Headers content (From, contact, Allow, Supported, Accepted) SDP Answer content (codecs, feature s options) Vidyo answered on H.264 PM1 payload type offer Video is established reinvite sent by 8088 to Vidyo : INVITE sip:770002@ :5060;transport=tcp SIP/2.0 Allow: INVITE, ACK, CANCEL, BYE, PRACK, NOTIFY, REFER, SUBSCRIBE, OPTIONS, UPDATE, INFO Contact: <sip: @ ;transport=tcp> Supported: replaces,timer,path,100rel User-Agent: OmniPCX Enterprise R11.2 l e Session-Expires: 1800;refresher=uac Min-SE: 900 Content-Type: application/sdp To: <sip:770002@ ;user=phone>;tag= From: <sip: @ ;user=phone>;tag=55f5db04eea377a b1cf86 47f Call-ID: 72dc7ff5ffe456ccb6110e515760aba7@ CSeq: INVITE Via: SIP/2.0/TCP ;branch=z9hG4bKb6c64c2f0b5c4da8b0db be13e Max-Forwards: 70 Content-Length: 669 v=0 o=oxe IN IP s=abs c=in IP t=0 0 a=sendrecv m=audio 6000 RTP/AVP c=in IP a=sendrecv a=rtpmap:8 PCMA/8000 a=ptime:20

22 a=maxptime:30 a=rtpmap:101 telephone-event/8000 m=video 7000 RTP/AVP a=rtpmap:99 H264/90000 a=rtpmap:100 H264/90000 a=rtcp-fb:99 nack a=rtcp-fb:99 nack pli a=rtcp-fb:99 nack sli a=rtcp-fb:100 nack a=rtcp-fb:100 nack pli a=rtcp-fb:100 nack sli a=fmtp:99 profile-level-id=42801f;max-fs=1300;level-asymmetryallowed=0;packetization-mode=1 a=fmtp:100 profile-level-id=42801f;max-fs=1300;level-asymmetryallowed=0;packetization-mode=0 a=sendrecv Answer returned by Vidyo : SIP/ OK Via: SIP/2.0/TCP ;branch=z9hG4bKb6c64c2f0b5c4da8b0db be13e From: <sip: @ ;user=phone>;tag=55f5db04eea377a b1cf86 47f To: <sip:770002@ ;user=phone>;tag= Call-ID: 72dc7ff5ffe456ccb6110e515760aba7@ CSeq: INVITE Contact: <sip:770002@ :5060;transport=tcp> Content-Type: application/sdp User-Agent: VidyoGateway Content-Length: 382 v=0 o=vidyogateway IN IP s=c=in IP b=as:1600 t=0 0 m=audio RTP/AVP a=rtpmap:8 PCMA/8000 a=sendrecv a=rtpmap:101 telephone-event/8000 m=video RTP/AVP 99 a=rtpmap:99 H264/90000 a=fmtp:99 profile-level-id=42801f; packetization-mode=1 a=sendrecv a=content:main a=rtcp-fb:* nack pli a=rtcp-fb:* nack sli

23 8.5.4 SIP REFER Support For this set of tests, we use a IP Touch endpoint equipment as the remote party N/A OK NOK Comment Place an Audio call from IP Touch 1 (from OXE node 1) to Third party video Video MCU Vidyo Capture 200OK sent by Third party video System Vidyo when answering a simple call and check for REFER in Allow header An second Audio call is placed from IP Touch 1 to IP Touch 2. While IP Touch 2 is ringing, IP Touch 2 transfer the call. A REFER is sent to Third party video MVU Vidyo, REFER is successfully parssed and accepted by Third party video System Vidyo. The full URI (including parameters) provided in Refer- To header is re-used by Third party video System Vidyo to forge the Requested URI in subsequent outgoing INVITE The SDP of the new INVITE is built based on media previously established. Third party video System Vidyo generated implicit Notify releative to the Refer request Previous dialog is released at the earliest, after subsequent 180 Ringing is processe (NOTIFY Ringing) No Allow Header Call Released REFER not acknowledge by Vidyo New Call is established successfully. Call is released Kepp the call established for 1 mn New Call is released successfully. NA Conclusion: Vidyo does not support properly SIP REFER mechanism in OXE environment.

24 8.5.5 SIP Replaces Support For this set of tests, we use IP Touch endpoints N/A OK NOK Comment Place an Audio call from IP Touch 1 (from OXE node 1) to IP Touch 2 (on OXE node 1) An second Audio call is placed from IP Touch 1 to Third party video Video system Vidyo. Video system Vidyo answers the call. Capture 200OK responded by Third party video System Vidyo when and check for replaces in Supported header, IP Touch 1 transfer the call. A INVITE with Replaces header is sent to Third party video System Vidyo, OXE send INVITE with Replaces header to Third party video System Vidyo No Supported header New Call is established successfully Previous SIP leg is released Released by OXE Call remaines established for 1mn OXE Self Refered SIP Leg is supported by Vidyo Not ed Conclusion: Vidyo supports properly SIP Replaces mechanism in OXE environment.

25 8.5.6 DTMF DTMF Payloadtype can be configured on Vidyo N/A OK NOK Comment An Audio or Audio/Video call is established from OXE to Third party video System Vidyo DTMF are generated by OXE. No way to configure DTMF PT Check for PayloadType used in RTP, Perform the test with symetric DTMF payloadtype negotiation. Check for PayloadType used in RTP, Perform the test with assymetric DTMF payloadtype negotiation. An Audio call is established from Third party video System Vidyo to OXE. DTMF are generated by Third party video System Vidyo Check for PayloadType used in RTP, Perform the test with symetric DTMF payloadtype negotiation. Check for PayloadType used in RTP, Perform the test with assymetric DTMF payloadtype negotiation. NA DTMF are in band. NA NA

26 8.5.7 Session Timer For this set of tests, we use a 8088 endpoint equipment as the remote party (standalone device) N/A OK NOK Comment An Audio or Audio/Video call is established from 8088 endpoint (from OXE node 1) to Third party video System Vidyo Check for Session Timer relative headers content Wait expiration of SIP Session timers and check for session refresh. An Audio or Audio/Video call is established from IP Touch endpoint (from OXE node 1) to Third party video System Vidyo Check for Session Timer relative headers content Wait expiration of SIP Session timers and check for session refresh. No session timer related parameters in response from Vidyo OXE did the refresh No session timer related parameters in response from Vidyo OXE did the refresh An Audio or Audio/Video call is established from Third party video System Vidyo to a Check for Session Timer relative headers content Wait expiration of SIP Session timers and check for session refresh. An Audio or Audio/Video call is established from Third party video System Vidyo to an IP Touch (OXE Node 1) Check for Session Timer relative headers content Wait expiration of SIP Session timers and check for session refresh. No session timer related parameters in response from Vidyo. OXE Take control of session timer OXE did the refresh No session timer related parameters in response from Vidyo. OXE Take control of session timer OXE did the refresh

27 8.5.8 LD/SD/HD Video Quality level N/A OK NOK Comment Audio/Video call established between Third party video System Vidyo (Full HD) and 8088 (H.264 High Profile) Call remains is this state after waiting 60 minutes Vidyo offers level 4.0 in SDP. Vidyo advertised Level 4.0 in SPS Audio/Video call established between Third party video System Vidyo (Full HD) and 8088 (H.264 Medium Profile) Vidyo offers level 4.0 in SDP. Vidyo advertised Level 4.0 in SPS Call remains is this state after waiting 60 minutes Audio/Video call established between Third party video System Vidyo (Full HD) and 8088 (H.264 Low Profile) Vidyo offers level 4.0 in SDP. Vidyo advertised Level 1.3 in SPS Call remains is this state after waiting 60 minutes Audio/Video call established between Third party video System Vidyo (HD) and 8088 (H.264 High Profile) Vidyo offers level 3.1 in SDP. Vidyo advertised Level 4.0 in SPS Call remains is this state after waiting 60 minutes Audio/Video call established between Third party video System Vidyo (HD) and 8088 (H.264 Medium Profile) Vidyo offers level 3.1 in SDP. Vidyo advertised Level 4.0 in SPS Call remains is this state after waiting 60 minutes Audio/Video call established between Third party video System Vidyo (HD) and 8088 (H.264 Low Profile) Vidyo offers level 4.0 in SDP. Vidyo advertised Level 1.3 in SPS Call remains is this state after waiting 60 minutes Audio/Video call established between Third party video System Vidyo (Below HD) and 8088 (H.264 High Profile) Vidyo offers level 3.0 in SDP. Vidyo advertised Level 4.0 in SPS Call remains is this state after waiting 60 minutes Audio/Video call established between Third party video System Vidyo (Below HD) and 8088 (H.264 Medium Profile) Vidyo offers level 3.0 in SDP. Vidyo advertised Level 4.0 in SPS Call remains is this state after waiting 60 minutes Audio/Video call established between Third party video System Vidyo (Below HD) and 8088 (H.264 Low Profile)

28 Call remains is this state after waiting 60 minutes

29 PCC MakeCall N/A OK NOK Comment Not ed Not ed Automatic answer N/A OK NOK Comment NA NA H.264 specificities observed An Audio/Video call is established from 8088 video endpoint to Third pârty Video MCU Vidyo. A network capture is performed and analysed to establish the list of capability. List of capabilities related to Video observed for Vidyo : N/A OK NOK Comment Multiples Reference Frame supported Not ed Multiples Reference Frame used Not ed Packetiezation mode (PM0, PM1, STAP-A) Advertised Profile/Level in SPS in conformance to SDP negotiation Configuration option to limit Video bandwifth PM0 only offered, but PM1 supported in answer 4.0 for level > 1.3 OK, at Vidyo Gateway level RTCP FB NACK PLI negotiation RTCP FB NACK SLI negotiation RTCP FB generic NACK negotiation

30 RTCP FB FIR negotiation SDP parameter for Bandwidth Control No constraints, but tmmbr supported INFO based Video Fast Update (respond) INFO based Video Fast Update (request) INFO based Bit Rate modification (respond) INFO based Bit Rate modification (request) Example of SIP INFO based Video Fast Update request from Vidyo <?xml version="1.0" encoding="utf-8"?> <media_control> <vc_primitive> <to_encoder> <picture_fast_update> </picture_fast_update> </to_encoder> </vc_primitive> </media_control>

31 8.6 Call from OXE ext. to 3rd party Video system Place an Audio call to Third party video System The established call must be maintained at least 1 minute. Calling Number/Name is checked on third party Video System side. Connected Party Number/Name is checked on OXE side. N/A OK NOK Comment Place an Audio call (G.722) from IP Touch (OXE Node 1) to Third party video System Vidyo Not available at OXE level Place an Audio call (G.711) from IP Touch (OXE Node 1) to Third party video System Vidyo Place an Audio call (G.729) from IP Touch (OXE Node 1) to Third party video System Vidyo Place an Audio call (G.711) from TDM Set (OXE Node 1) to Third party video System Vidyo Place an Audio call (G.722) from 8088 (OXE Node 1) to Third party video System Vidyo Place an Audio call (G.711) from PSTN Extension (OXE Node 1) to Third party video System Vidyo Place an Audio call (G.711) from 8088 (OXE Node 2) to Third party video System Vidyo Place an Audio call (G.711) from IP Touch (OXE Node 2) to Third party video System Vidyo Place an Audio call (G.729) from IP Touch (OXE Node 2) to Third party video System Vidyo Place an Audio call (G.729) from TDM Set (OXE Node 1) to Third party video System Vidyo Call is Cancelled on OXE side before the call is answered by Third party video System Vidyo Call is Rejeccted on Third party video System side Vidyo Check for Reason Header Call is Deflected on Third party video System side Vidyo Check for Diversion and History-Info Headers Check Calling Name/Number on Third party video System Vidyo Vidyo does not support G.729 Not available at OXE level. Not ed Not ed Not ed Not ed Only applicable in P2P call type. Only applicable in P2P call type. Call is diverted to an IVR on Vidyo side. NA P2P mode or Conference mode : only Display Name is displayed on Vidyo clients (with either a name or a number if no name, or Anonymous).

32 8.6.2 Place an Audio/Video call to the Third party video System NA Video profile on Third Party Video Systel is set to default. The established call must be maintained at least 1 minute. N/A OK NOK Comment Dial By Name N/A OK NOK Comment Place an Audio/Veo call from 8088 (OXE Node 1) to Third party video System Vidyo, by searching Name (LDAP Integration). Place an Audio call from IP Touch (OXE Node 1) to Third party video System Vidyo by searching Name (LDAP Integration). Not ed Not ed Details on LDAP Integration: No specific LDAP integration, just populate a common LDAP with Vidyo users details. Vidyo allows performing user authentication on the LDAP server Call-Log, Redial List N/A OK NOK Comment After a call has been placed from 8088 (OXE Node 1) to Third party video System Vidyo, Call-Log/Redial List is checkedd on 8088 side. After a call has been placed from IP Touch (OXE Node 1) to Third party video System Vidyo, Call-Log/Redial List is checkedd on IP Touch side.

33 8.7 Call from 3rd party Video system to OXE Ext Receive an Audio call N/A OK NOK Comment Receive an Audio call (G.722) from Third party video System Vidyo to IP Touch (OXE Node 1) Receive an Audio call (G.711) from Third party video System Vidyo to IP Touch (OXE Node 1) Receive an Audio call (G.729) from Third party video System Vidyo to IP Touch (OXE Node 1) Receive an Audio call (G.711) from Third party video System Vidyo to TDM (OXE Node 1) G.722 Not supported by OXE G.729 Not supported by Vidyo Receive an Audio call (G.711) from Third party video System Vidyo to 8088 (OXE Node 1) Receive an Audio call (G.722) from Third party video System Vidyo to 8088 (OXE Node 1) Receive an Audio call (G.722) from Third party video System Vidyo to PSTN (OXE Node 1) Receive an Audio call (G.711) from Third party video System Vidyo to 8088 (OXE Node 2) Receive an Audio call (G.711) from Third party video endpoint Vidyo to IP Touch (OXE Node 2) Receive an Audio call (G.729) from Third party video endpoint Vidyo to IP Touch (OXE Node 2) Receive an Audio call (G.729) from Third party video endpoint Vidyo to TDM Set (OXE Node 1) Receive an Audio call from Third party video System Vidyo to IP Touch (OXE Node 1) : Call is cancelled Receive an Audio call from Third party video System Vidyo to IP Touch (OXE Node 1) : Call is rejected (DND) Receive an Audio call from Third party video System Vidyo to IP Touch (OXE Node 1) : Call is deflected to another OXE extension Receive an Audio call from Third party video System Vidyo to IP Touch (OXE Node 1) : Call is forwarded to another OXE extension (immediate, no response, busy) Receive an Audio call from Third party video System Vidyo to IP Touch (OXE Node 1) : Call is forwarded to Voic (immediate, no response, busy) Receive an Audio call from Third party video System Vidyo to IP Touch (OXE Node 1) : Call is forwarded to PSTN destination (immediate, no response, busy) Receive an Audio call (G.722) from Third party video System Vidyo to OTC PC (OTMS/OXE Node 1 / SEPLOS Mode) Receive an Audio call (G.711) from Third party video System Vidyo to OTC PC (OTMS/OXE Node 1 / SEPLOS Mode) G.722 Not supported by OXE G.722 Not supported by OXE Not ed Not ed G.729 Not supported by Vidyo G.729 Not supported by Vidyo Call continue to ring for few seconds on OXE side. Call is silently abandoned. 302 not supported by Vidyo 302 not supported by Vidyo 302 not supported by Vidyo

34 Receive an Audio call (G.729) from Third party video System Vidyo to OTC PC (OTMS/OXE Node 1 / SEPLOS Mode) Receive an Audio call (G.722) from Third party video System Vidyo to OTC PC (OTMS/OXE Node 1 / Z/SIP Mode) Receive an Audio call (G.711) from Third party video System Vidyo to OTC PC (OTMS/OXE Node 1 / Z/SIP Mode) Receive an Audio call (G.729) from Third party video System Vidyo to OTC PC (OTMS/OXE Node 1 / Z/SIP Mode) Check Calling Name/Number on OXE extensions : 8088 Check Calling Name/Number on OXE extensions : IP Touch G.722 Not supported by OXE G.729 Not supported by Vidyo Calling name : OK Calling Number : OK Calling name : OK Calling Number : OK Receive an Audio/Video call The established call must be maintained at least 1 minute. N/A OK NOK Comment Receive an Audio/Veo call from Third party video System Vidyo to 8088 (OXE Node 1) (8088 set in H.264 High Profile) Receive an Audio/Veo call from Third party video System Vidyo to 8088 (OXE Node 2) (H.264 High Profile) Receive an Audio/Video call from Third party video System Vidyo to 8088 (OXE Node 1) (8088 set in H.264 Medium Profile) Receive an Audio/Video call from Third party video System Vidyo to 8088 (OXE Node 1) (8088 set in H.264 Low Profile) Receive an Audio/Veo call from Third party video System Vidyo to IP Touch (OXE Node 1) Receive an Audio/Veo call from Third party video System Vidyo to OTC PC (OTMS/OXE Node 1 / SEPLOS Mode) Receive an Audio/Veo call from Third party video System Vidyo to OTC PC (OTMS/OXE Node 1 / Z/SIP Mode) Not ed Dial by Name N/A OK NOK Comment Place an Audio/Veo to 8088 (OXE Node 1) to Third party video System Vidyo, by searching Name (Phonebook Integration). Details on LDAP Integration: No way to have LDAP integration here, for all OXE extension that need to be reached, a Legacy endpoint must be configured in Vidyo. This Legacy endpoint is then searchable in Vidyo call by name featre.

35 8.7.4 Call-Log, Redial List N/A OK NOK Comment After a call has been placed Third party video System Vidyo to 8088 (OXE Node 1), Call-Log/Redial List is checkedd on Third party video System Vidyo. After a call has been placed Third party video System Vidyo to PSTN Destination, Call-Log/Redial List is checkedd on Third party video System Vidyo. After a call has been placed Third party video System Vidyo to IP Touch OXE Node 1, Call-Log/Redial List is checkedd on IP Touch. After a call has been placed Third party video System Vidyo to 8088 OXE Node 1, Call-Log/Redial List is checkedd on NA NA NOK, trailing #, checking OXE configuration

36 8.8 Mid call services Escalate an Audio call to Audio/Video The established call must be maintained at least 1 minute after escalation takes place N/A OK NOK Comment Place an Audio call between 8088 (OXE Node 1) and Third party video System Vidyo then escalate to Video on 8088 side (8088 set in H.264 High Profile) Place an Audio call between 8088 (OXE Node 2) and Third party video System Vidyo then escalate to Video on 8088 side (H.264 High Profile) Place an Audio call between 8088 (OXE Node 1) and Third party video System Vidyo then escalate to Video on Third party video System side (8088 set in H.264 High Profile) Place an Audio call between 8088 (OXE Node 2) and Third party video System Vidyo then escalate to Video on Third party video System side (H.264 High Profile) From Vidyo, you always place A/V call, but you can place an A/V call with video disabled, then reenable it later Not ed Even if you receive an initial Audio call, Call on vidyo side will be A/V ready. Not ed Third party video System Holds/Retrieves communication N/A OK NOK Comment Audio/Video call is established between Third party video System Vidyo and 8088 (Oxe Node 1), Third party video System Vidyo puts communication on hold, 8088 is in hold state; System music is heared on 8088, Call remains is this state after waiting 1 minute Third party video System Vidyo retrieves the communication, audio and video are resumed Call remains is this state after waiting 1 minute Audio/Video call is established between Third party video System Vidyo and 8088 (Oxe Node 2), Third party video System Vidyo puts communication on hold, 8088 is in hold state; System music is heared on 8088, Call remains is this state after waiting 1 minute Third party video System Vidyo retrieves the communication, audio and video are resumed Call remains is this state after waiting 1 minute Audio only call is established between Third party video System Vidyo and IP Touch (Oxe Node 1), Third party video System Vidyo puts communication on hold, IP Touch is in hold state; System music is heared on IP Touch,

37 Call remains is this state after waiting 1 minute Third party video System Vidyo retrieves the communication, audio only media is resumed Call remains is this state after waiting 1 minute Audio only call is established between Third party video System Vidyo and OTC PC (OTMS/Oxe Node 1/SEPLOS Mode), Third party video System Vidyo puts communication on hold, OTC PC is in hold state; System music is heared on OTC PC, Call remains is this state after waiting 1 minute Third party video System Vidyo retrieves the communication, audio only media is resumed Call remains is this state after waiting 1 minute Audio only call is established between Third party video System Vidyo and OTC PC (OTMS/Oxe Node 1/Z/SIP Mode), Third party video System Vidyo puts communication on hold, OTC PC is in hold state; System music is heared on OTC PC, Call remains is this state after waiting 1 minute Third party video System Vidyo retrieves the communication, audio only media is resumed Call remains is this state after waiting 1 minute Endpoint Holds/Retrieves the communication N/A OK NOK Comment Audio/Video call is established between Third party video System Vidyo and 8088 (OXE Node 1), 8088 puts communication on hold, System music is heared by Third party video System Vidyo, Call remains is this state after waiting 1 minute No indication neither music on Vidyo side MyIC Phone 8088 retrieves the communication, Audio/Video is resumed Call remains is this state after waiting 1 minute Audio/Video call established between OTCV user A/Third party video System Vidyo and 8088 (OXE Node 2), 8088 puts communication on hold, System music is heared by Third party video System Vidyo, Not ed Call remains is this state after waiting 1 minute Not ed MyIC Phone 8088 retrieves the communication, Audio/Video media are resumed. Not ed

38 7.3.8 Call remains is this state after waiting 1 minute Not ed Audio only call established between OTCV user A/Third party video System Vidyo and IP Touch (OXE Node 1), IP Touch puts communication on hold, System music is heared by Third party video System Vidyo, No indication neither music on Vidyo side Call remains is this state after waiting 1 minute MyIC Phone IP Touch retrieves the communication, Audio only media is resumed Call remains is this state after waiting 1 minute Audio only call established between OTCV user A/Third party video System Vidyo and OTC PC (OTMS/Oxe Node 1/SEPLOS Mode), OTC PC puts communication on hold, System music is heared by Third party video System Vidyo, Call remains is this state after waiting 1 minute OTC PC retrieves the communication, Audio only media is resumed Call remains is this state after waiting 1 minute Audio only call established between OTCV user A/Third party video System Vidyo and OTC PC (OTMS/Oxe Node 1/Z/SIP Mode), OTC PC puts communication on hold, System music is heared by Third party video System Vidyo, No indication neither music on Vidyo side Call remains is this state after waiting 1 minute OTC PC retrieves the communication, Audio only media is resumed Call remains is this state after waiting 1 minute

39 8.8.4 DTMF N/A OK NOK Comment An Audio or Audio/Video call is established from IP Touch to Third party video System Vidyo DTMF are sent from IP Touch to Third party video System Vidyo DTMF are regognized by Third party video System Vidyo.. An Audio or Audio/Video call is established from OTC PC (OTMS/OXE Node 1/SEPLOS Mode) to Third party video System Vidyo DTMF are sent from OTC PC to Third party video System Vidyo. DTMF are regognized by Third party video System Vidyo.. An Audio or Audio/Video call is established from OTC PC (OTMS/OXE Node 1/Z/SIP Mode) to Third party video System Vidyo DTMF are sent from OTC PC to Third party video System Vidyo. DTMF are regognized by Third party video System Vidyo.. An Audio or Audio/Video call is established from 8088 (OXE Node 1) to Third party video System Vidyo DTMF are sent from 8088 to Third party video System Vidyo. DTMF are regognized by Third party video System Vidyo.. An Audio or Audio/Video call is established from 8088 (OXE Node 2) to Third party video System Vidyo DTMF are sent from 8088 to Third party video System Vidyo. DTMF are regognized by Third party video System Vidyo.. An Audio or Audio/Video call is established from PSTN origine to Third party video System Vidyo done with Vidyo IVR done with Vidyo IVR done with Vidyo IVR Not ed Not ed Not ed DTMF are sent from PSTN side to Third party video System Vidyo. DTMF are regognized by Third party video System Vidyo.. An Audio or Audio/Video call is established from Third party video System Vidyo to 8088 forwarded to Voic DTMF are sent from Third party video System Vidyo to Voic application DTMF are regognized by Voic application. done with Vidyo IVR Forward to VM does not work. Vidyo is sending DTMF in band

40 8.8.5 Call transfer from OXE extension: Blind transfer The established call must be maintained at least 1 minute. N/A OK NOK Comment Place an Audio/Video call between Third party video System Vidyo and a 8088 (OXE Node 1) performs a blind transfer to a second 8088 (OXE Node 1). Second 8088 answers the call. Place an Audio/Video call between Third party video System Vidyo and a 8088 (OXE Node 1) performs a blind transfer to second 8088 (OXE Node 2). Second 8088 answers the call. Place an Audio/Video call between Third party video System Vidyo and a 8088 (OXE Node 2) performs a blind transfer to a second 8088 (OXE Node 1). Second 8088 answers the call. Place an Audio/Video call between Third party video System Vidyo and an OTC PC (OTMS/OXE Node 1/SEPLOS Mode). OTC PC performs a blind transfer to a 8088 (OXE Node 1) answers the call. Place an Audio/Video call between Third party video System Vidyo and an OTC PC (OTMS/OXE Node 1/Z/SIP Mode). OTC PC performs a blind transfer to a 8088 (OXE Node 1) answers the call. For one of the test above, Call remains established after waiting 1 minute REFER not supported by Vidyo Not ed REFER not supported by Vidyo REFER not supported by Vidyo REFER not supported by Vidyo Call transfer from OXE extension: Attended transfer N/A OK NOK Comment Place an Audio/Video call between Third party video System Vidyo and a 8088 (OXE Node 1) performs an attended transfer to a second 8088 (OXE Node 1). Second 8088 answers the call. Place an Audio/Video call between Third party video System Vidyo and a 8088 (OXE Node 1) performs an attended transfer to second 8088 (OXE Node 2). Second 8088 answers the call. Place an Audio/Video call between Third party video System Vidyo and a 8088 (OXE Node 2) performs an attended transfer to a second 8088 (OXE Node 1). Second 8088 answers the call. Place an Audio/Video call between Third party video System Vidyo and an OTC PC (OTMS/OXE Node 1/SEPLOS Mode). OTC PC performs an attended transfer to a 8088 (OXE Node 1) answers the call. Place an Audio/Video call between Third party video System Vidyo and an OTC PC (OTMS/OXE Node 1/Z/SIP Mode). OTC PC performs an attended transfer to a 8088 (OXE Node 1) answers the call. For one of the test above, Call remains established after waiting 1 minute REFER not supported by Vidyo Not ed REFER not supported by Vidyo REFER not supported by Vidyo REFER not supported by Vidyo

41 8.8.7 Call transfer from Third party video System: transfer (blind) N/A OK NOK Comment Place an Audio/Video call between Third party video System Vidyo and a 8088 (OXE Node 1). Third party video System performs a blind transfer to a second 8088 (OXE Node 1). Second 8088 answers the call. Place an Audio/Video call between Third party video System Vidyo and a 8088 (OXE Node 1). Third party video System performs a blind transfer to second 8088 (OXE Node 2). Second 8088 answers the call. Place an Audio/Video call between Third party video System Vidyo and a 8088 (OXE Node 2). Third party video System performs a blind transfer to a second 8088 (OXE Node 1). Second 8088 answers the call. Place an Audio/Video call between Third party video System Vidyo and an OTC PC (OTMS/OXE Node 1/SEPLOS Mode). Third party video System performs a blind transfer to a 8088 (OXE Node 1) answers the call. Place an Audio/Video call between Third party video System Vidyo and an OTC PC (OTMS/OXE Node 1/Z/SIP Mode). Third party video System performs a blind transfer to 8088 (OXE Node 1) answers the call. For one of the test above, Call remains established after waiting 1 minute Call transfer from Third party video System: transfer (Other) N/A OK NOK Comment Accordingly to Third party video System capabilities.

42 8.9 OXE Conference party conference from IP Touch N/A OK NOK Comment Place an Audio call between IP Touch (OXE Node 1) and Third party video System Vidyo then manage a three party conference on IP Touch side Conference remains established after waiting 1 minute The third participant leaves the conference, P2P call between IP Touch and Third party video System Vidyo is re-established. Place an Audio call between OTC PC (OTMS/OXE Node 1/SEPLOS Mode) and Third party video System Vidyo then manage a three party conference on OTC PC side Conference remains established after waiting 1 minute Place an Audio call between OTC PC (OTMS/OXE Node 1/Z/SIP Mode) and Third party video System Vidyo then manage a three party conference on OTC PC side Conference remains established after waiting 1 minute party conference from 8088 N/A OK NOK Comment Not ed Mastered Conference N/A OK NOK Comment TBD Not ed Meet-me conference N/A OK NOK Comment TBD Not ed

43 8.10 OT Scheduled Conference Video Dial-in N/A OK NOK Comment No one is currently connected to the conference. Place an Audio/Video call from Third party video System Vidyo to the conferencing application (dial-in to the btridge). In a first step, Video is rejected by the system. Provides the PIN code through DTMF function of the Third party video System. Video is resumed automatically. Once all announcement are finished, stop the waiting music if any. Video from Third party video endpoint is loopbacked through the conferencing system. Several 8088 (OXE Node 1) joins the Audio/Video conference Video is displayed on Third party video endpoint Third party video System Vidyo according to the SFU algorithm When Third party video System Vidyo is the active talker, video from Third party video endpoint is seen by other participants according to the SFU algorithm. DTMF from Vidyo are not recognized (Vidyo send DTMF in band) Call remains established after waiting 1 minute Audio Dial-in then escalation N/A OK NOK Comment Several 8088 are connected to the conference (Audio/Video). Place an Audio call from Third party video System Vidyo to the conferencing application (dial-in to the btridge). Provides the PIN code through DTMF function of the Third party video system. Once all announcement are finished, audio from the other participant can be heard. DTMF from Vidyo are not recognized (Vidyo send DTMF in band) Third party video system escalates to video Video is displayed on Third party video endpoint Third party video System Vidyo according to the SFU algorithm When Third party video System Vidyo is the active talker, video from Third party video endpoint is seen by other participants according to the SFU algorithm Call remains established after waiting 1 minute

44 Audio Dial-out from OTC Web then escalation N/A OK NOK Comment Several 8088 are connected to the conference (Audio/Video). User joins the conference through the URL (OTC Web) and ask to system to call-back the Third party video System Vidyo System place an Audio call from conferencing application to the Third party video system. Answer the call on the Third party video System Vidyo². Once all announcement are finished, audio from the other participant can be heared Third party Third party video System Vidyo escalates to video. Video is displayed on Third party video endpoint Third party video System Vidyo according to the SFU algorithm When Third party video System Vidyo is the active talker, video from Third party video endpoint is seen by other participants according to the SFU algorithm. DTMF from Vidyo are not recognized (Vidyo send DTMF in band) Call remains established after waiting 1 minute Add Participant on the fly from OTC PC N/A OK NOK Comment Several 8088 and an OTC PC joins a scheduled conference On the OTC PC, User adds Third party video System Vidyo Third party video System Vidyo is ringing Call is answered on Third party video System Vidyo, The audio call is established with the conference brtidge, and conference prompt is delivered to the end user. End user performs video escalation on the Third party video System Vidyo. Video is displayed on Third party video endpoint Third party video System Vidyo according to the SFU algorithm When Third party video System Vidyo is the active talker, video from Third party video endpoint is seen by other participants according to the SFU algorithm Call remains established after waiting 1 minute

45 Dropped from the conference by OTC PC N/A OK NOK Comment An OTC PC is connected to the conference. Third party video System Vidyo is connected to the conference (Audio/Video). OTC PC drops Third party video System from the scheduled conference. Third party video System Vidyo is disconnected from the conference and call is released TUI Menu N/A OK NOK Comment Third party video System Vidyo is connected to the conference (Audio/Video). Third party video System dial the ##1 DTMF code to access the TUI menu Various TUI menu optios workd (list of participants, ) DTMF from Vidyo are not recognized (Vidyo send DTMF in band) Mix of H.264 Level, OT Conference configured to support HD N/A OK NOK Comment Several 8088 are connected to the conference with various levels (Low, Medium, High). Place an Audio/Video call from Third party video System Vidyo to the conferencing application (dial-in to the btridge). In a first step, Video is rejected by the system. Provides the PIN code through DTMF function of the Third party video System. Video is resumed automatically. Once all announcement are finished, stop the waiting music if any. Video from Third party video endpoint is loopbacked through the conferencing system. Several 8088 (OXE Node 1) joins the Audio/Video conference Video is displayed on Third party video endpoint Third party video System Vidyo according to the SFU algorithm When Third party video System Vidyo is the active talker, video from Third party video endpoint is seen by other participants according to the SFU algorithm Call remains established after waiting 1 minute

46 8.11 Third party Video System Conference Audio Dial-in, then Video escalation N/A OK NOK Comment No one is currently connected to the conference. Place an Audio call from 8088 (OXE Node 1) to the Third party video System Vidyo conferencing application (dial-in to the btridge). Provides the PIN code through DTMF Once all announcement are finished, 8088 is able escalate to escalate to Video and able to see itself (loopback) or a video prompt. Place an Audio call from a second 8088 (OXE Node 2) to the Third party video System Vidyo conferencing application (dial-in to the btridge). Provides the PIN code through DTMF Once all announcement are finished, second 8088 is able to escalate to Video and see a layout including first 8088 or a video prompt. Several others 8088 (OXE Node 1/2) and Third party video System Endpoints Vidyo(if applicable) joins the Audio/Video conference Video is displayed on first 8088 according to the third party video system dynamic layout algorithm When first 8088 is the active talker, video from first 8088 is seen by other participants according to the third party video system dynamic layout algorithm. Video is displayed on second 8088 according to the third party video system dynamic layout algorithm When second 8088 is the active talker, video from first 8088 is seen by other participants according to the third party video system dynamic layout algorithm. Note, conference will not start until a Vidyo owner is connected or you need to change tenant level parameter! Call remains established after waiting 1 minute Place an Audio call from 8088 (OXE Node 1) to the Third party video System Vidyo conferencing application (dial-in to the btridge). Try to escalate to Video as eraly as possible (before providing any code through DTMF, ). Provides the PIN code through DTMF Once all announcement are finished, 8088 is able escalate to see itself (loopback) or a video prompt Audio/Video Dial-out from Third party Video System N/A OK NOK Comment Several 8088 and Third party video System Vidyo endpoints (if applicable) are connected to the conference (Audio/Video). User joins the conference through conference URL (or any other means to be called back provided by Third party video System Vidyo) System place an Audio call from conferencing application to the 8088 (OXE Node 1). Answer the call on Once all announcement are finished, audio/video from the other participant can be heared/seen Call remains established after waiting 1 minute

47 Several 8088 and and Third party video System Vidyo endpoints (if applicable) are connected to the conference (Audio/Video). User joins the conference through conference URL (or any other means to be called back provided by Third party video System Vidyo) System place an Audio call from conferencing application to the 8088 (OXE Node 2). Answer the call on Once all announcement are finished, audio/video from the other participant can be heared/seen Call remains established after waiting 1 minute Dropped from the conference by Third Party Video System N/A OK NOK Comment 8088 is connected to the conference (Audio/Video). Third party video System Vidyo drops Third party video System from the scheduled conference is disconnected from the conference and call is released TUI Menu N/A OK NOK Comment TBD Blast Call N/A OK NOK Comment TBD

48 8.12 Content Sharing This is to identify behaviour of the system when content sharing capability (if any) is used N/A OK NOK Comment Several 8088 are connected to the conference (Audio/Video). Several Third party video System Vidyo are also connected to the conference. One of the Third party video System Vidyo starts to share desktop or application On 8088, video layout is replaced by the latest content shared. Multiple content sharing can be done in Vidyo world, but legacy endpoints will only see the latest one (at activation time) Call remains established after waiting 1 minute Sharing is stopped, 8088 display video layout 8.13 Remote Call Control N/A OK NOK Comment Not ed OXE Advanced Telephony Services N/A OK NOK Comment Not ed

49 8.15 Anonymous Call N/A OK NOK Comment Place an anonymous call from PSTN extension to Third party video System Vidyo Place an anonymous call from Third party video System Vidyo to PSTN extension 8.16 Abandoned Call, Call Routing Error N/A OK NOK Comment Place a call from Third party video System Vidyo to a wrong number Place a call from Third party video System Vidyo to 8088 (OXE Node 1), Call is abandonned in ringing state Place a call from 8088 (OXE Node 1) to Third party video System Vidyo, Call is abandonned in ringing state Place a call from Third party video System Vidyo to 8088 (OXE Node 1), 8088 is BUSY (no Voic opveflow) Place a call from Third party video System Vidyo to IP Touch (OXE Node 1), 8088 is BUSY (Voic opveflow) Place a call from 8088 (OXE Node 1) to Third party video System Vidyo, Third party video System Vidyo is busy Place a call from Third party video System Vidyo to IP Touch (OXE Node 1), 8088 is ringing forever Either IVR or call is rejected But 8088 still rings for few seconds Call rejected (603 decline) Timeout on Vidyo side and message popup to user 8.17 Tones N/A OK NOK Comment Not ed

50 8.18 IPv6 N/A OK NOK Comment Not ed CAC N/A OK NOK Comment Not ed Security N/A OK NOK Comment Not ed OXE H.A. OXE Node 1 is running in geo-redundancy mode. Depending on Third party video System capability, either : - OXE Node name based SIP domain is used to configure relation between Third party video System and OXE Node 1, - Role based OXE virtual IP are used to configure relation between Third party video System and OXE Node 1, N/A OK NOK Comment OXE Node 1 machine A is role Main. OXE Node 1 machine B is role StdBy Place a call from 8088 OXE Node 1 to Third party video System Vidyo Place a call from Third party video System Vidyo to 8088 OXE Node 1 Change OXE Node 1 machine B role to Main Place a call from 8088 OXE Node 1 to Third party video System Vidyo Place a call from Third party video System Vidyo to 8088 OXE Node 1

51 Check the downtime between Third party video System Vidyo and OXE Check if Internal DNS resolver is well used by Third party video System Vidyo (TTL to zero) Reboot OXE Node 1 machine A (Role main given to machine A by priority). Check downtime between Third party video System Vidyo and OXE Few seconds 8.22 Information for End Users This is mainly to identify any existing capability to display a end user would need to use the solution. This is for example a phone number. N/A OK NOK Comment Vidyo users s phone number and conference room number can be easely communicated to OXE users Phone number displayed in various place can be directly used by OXE users 8.23 Robustness & Ageing N/A OK NOK Comment Join a Vidyo room from 8088 (audio call + video escalation) and check that video is well established each time Make a long communication between 8088 and Vidyo conference room Some time, there are black screen on hours

52 8.24 Network impairment & Audio/Video quality Video call is established. Several Network impairments profiles are evaluated. Video Quality level selected is Medium Level. Profile A : One way latency : ms, Jitter : 0-50ms, packet lost : % Profile B : One way latency : ms, Jitter : 0-150ms, packet lost : 0 2% Profile C1 : One way latency : ms, Jitter : 0-500ms, packet lost : 0 4% Profile C2 : One way latency : ms, Jitter : 0-500ms, packet lost : 0 10% N/A OK NOK Comment An Audio/Video call is established between 8088 (OXE Node 1) and a Third party video System. Network impairement Profile A is used. Check that re-syn/retransmission based on RTCP-FB messages is effective in both direction. An Audio/Video call is established between 8088 (OXE Node 1) and a Third party video System. Network impairement Profile B is used An Audio/Video call is established between 8088 (OXE Node 1) and a Third party video System. Network impairement Profile C1 is used Not ed Not ed Not ed Not ed

53 9 Appendix A : AAPP member s Application description Refer to VidyoConferencing admin guide. The System in Brief The VidyoConferencing system allows users to connect to and have conversations with other system users using the best of online video technology. Each end user has a portal (web page) that can be viewed in Internet Explorer, Firefox, Chrome and its own window. This VidyoPortal allows system users to search and find other users, place calls, and gather in virtual online meeting rooms. Users have the VidyoDesktopTM program on their Windows, Macintosh, or Linux computers that enable them to participate in VidyoConferences with just one other participant (known as a point-topoint or direct call) or with multiple participants. VidyoDesktop can display up to eight other participants, and users can also choose to view their own images using a PIP (picture-in-picture). This feature is called Self-View. VidyoDesktop also enables users to share any window currently displayed on their screens (an Excel spreadsheet or a Keynote slide, for example). We call this application sharing. While there are different programs for each platform, each installation of an endpoint program consumes one license. Therefore, a user who needs VidyoDesktop on a desktop and VidyoMobile on an iphone would consume two licenses. However, you don t have to predetermine how many of each kind of license you re going to need in advance. There s only one kind of license and it can be used for any device. In other words, our endpoint licensing is deviceagnostic. The optional VidyoGateway server allows interoperability with Legacy conferencing systems that use multi-point control units (MCUs). VidyoGateway also allows people to call into a conference from an ordinary landline or cell phone (that doesn t have VidyoMobile installed) for voice-only participation

54 10 Appendix B: Configuration requirements of the AAPP member s application 10.1 Tenant Extension Prefix First, you need to configure an extension prefix such as all Vidyo numbers (users, room) have this common leading prefix. This prefix must match the prefix configured on OXE side (Routing Number Prefix). To configure the prefix, you need to access to the Super Admin, and change prefix at Tenant level (Field Extension Prefix) 10.2 Vidyo Gateway To allow SIP communication between Vidyo Gateway and OXE Call Server, you must configure the SIP Interface on Vidyo Gateway side. To configure SIP Interface on Vidyo Gateway side, you have to access the VidyoGateway Admin and perform the following configuration step : - Click on General Tab, then click on SIP sub-tab. Enable TCP Protol As Proxy Address, fill either OXE IP address or OXE SIP Domain (nodename) Select inbound & outbound Let Username and Password empty (no authentication) - Click on Services Tab Edit DEFAULT (Direction=FROMLEGACY) o Check that H264 is part of selected Video codec, o Check that G.711 is part of selected Audio codec, o Set resolution up to HD, accordingly to your configuration o Change bandwidth, if required, to match bandwidth defined at 8088 level. o Change Call Type accordingly to your need, see nex chapter. Edit DEFAULT (Direction=TOLEGACY) o Check that outbound protocol is SIP o Check that H264 is part of selected Video codec, o Check that G.711 is part of selected Audio codec, o Set resolution up to HD, accordingly to your configuration - Do not forget to click on Apply Changes blue button Routing Call from Vidyo solution to OXE Call Server extensions If you need Vidyo user to be able to call OXE Extensions, you will have to define each extension in Vidyo as a Legacy device. To create a Legacy device, you have to access the VidyoPortal admin and perform the following configuration steps : Select Users Tab Select Add Legacy Device o Legacy Device Name : Put the name you want (this filed will be searchable from Vidyo clients) o Extension: Put the OXE extension here.

55 10.4 Vidyo Call Type In Vidyo solution, there are intrinsically two ways to call a user (Call type): Conference Call P2P Call Indeed, each Vidyo user has a personal room. Conference call means to call the personal room of a user. In such case, caller is immediately connected to the room. Vidyo user may be already connected or may connect later. For P2P call, when caller call the vidyo user, this last one is alerted, and communication will take place only if Vidyo user accept the call. If you need both call type (conference and P2P) for call from OXE Call Server to Vidyo solution, you will have to : add a new service with an additional prefix. Be careful, this is an additional prefix. For example, if your Vidyo tenant prefix is 77, and you have configured a new service with prefix 8 for P2P call, OXE users will have to dial 877xxx to join user in a P2P call type, and directly 77xxx to join user in a Conference call type. Add a new Network Routing Table

56 11 Appendix C: Alcatel-Lucent Enterprise Communication Platform: configuration requirements Homogenous Private Dialling Plan ABC-F IP Link SIP Connexion OXE N2 Numbering plan 21xxxx OXE N1 Numbering Plan : 22xxxx Third party Video System Numbering Plan : 3xxxx In this configuration, Third Party Video System is seen as a node of the OXE Network. From dial plan perspective, this node is then known to host numbers starting by a unique prefix (Routing Number Prefix). This configuration is suitable for interconnecting OXE to Third Party Video System when this last one is able to expose through the SIP Trunk a homogeneous dialling plan. The SIP Trunk can be configured with either a fixed or dynamic (Registered) contact address. On OXE Node 1, Create a Routing Number Prefix Translator/Prefix Plan/Create Number : <Prefix used to join the Third Party Video System> (3 in the example above). Prefix meaning : Routing No. Network number : <An arbitrary network number associated to the third party Video System> Node Number / ABC-F Trunk Group : <ABCF SIP Trunk identify of SIP Trunk resources to be used>. If you don t have existing Trunk available for that purpose, you need to create a new one. Number of digits : <Total Number of digits to collect before trying to connect to the third party video system> (numbering plan size used on Video MCU), for example : 5, for for up to 9999 different rooms/automated attendant) Create a SIP External Gateway SIP/SIP Ext Gateway/Create SIP External Gateway ID : Select a free index Gateway Name : <a friendly name for this gateway> (for example Video MCU <location>/<model>) SIP remote domain : <IP address or FQDN of Vidyo Gateway> SIP Port number : <Port number of SIP interface of Vidyo Gateway> Transport Type : <Transport Protocol to use for SIP interface to Vidyo Gateway >(TCP) Supervision Timer : <Choose a value> (60 for example) Trunk Group Number : <ABCF SIP Trunk identify of SIP Trunk resources to be used.> DNS Type : DNS A SIP DNS1 IP address: <IP address of a DNS able to resolve Vidyo FQDN> (if FQDN is used).

57 SIP DNS2 IP address: <IP address of a backup DNS able to resolve Vidyo FQDN> (if FQDN is used). authentication method : SIP None Payload type for DTMF : 101 Gateway Type : Standard Type Proxy entification on IP address : True Video Support Profile : Un Restricted Network Routing Table Translator/Network Routing Table/Review/Modify (select a free table) Protocol Type : ABC_F Numbering Plan Descriptor : <a free NPD> Associated Ext SIP gateway : <the SIP external gateway to is used to join the Vidyo Gateway> (created above). To fix calling number displayed on OXE side (incoming call from Vidyo to OXE extension like IP Touch), you need also to create a External Callback Translation Rule as follow: Ext. Callback Translation Rule Translator/External Numbering Plan/Ext. Callback Translation Table/Descend Hierarchy/Create External Callback Table : 0 (accordingly to your trunk configuration) Basic Number : B< Prefix used to join the Third Party Video System > (B3 in the example above) No. Digits To Be Removed : 1 Digits To Addd : let empty For a better user experience, if DTMF is required to interact with Video MCU, you can enable option DTMF end-to-end signal at SIP trunk level. Such a way, one the call is established between OXE device and the Video MCU, OXE device switch in DTMF transparency mode automatically.

58 12 Appendix D: AAPP member s escalation process Refer to Vidyo Support handbook..

59 13 Appendix E: AAPP program 13.1 Alcatel-Lucent Application Partner Program (AAPP) The Application Partner Program is designed to support companies that develop communication applications for the enterprise market, based on Alcatel-Lucent Enterprise's product family. The program provides tools and support for developing, verifying and promoting compliant thirdparty applications that complement Alcatel-Lucent Enterprise's product family. ALE International facilitates market access for compliant applications. The Alcatel-Lucent Application Partner Program (AAPP) has two main objectives: Provide easy interfacing for Alcatel-Lucent Enterprise communication products: Alcatel-Lucent Enterprise's communication products for the enterprise market include infrastructure elements, platforms and software suites. To ensure easy integration, the AAPP provides a full array of standards-based application programming interfaces and fully-documented proprietary interfaces. Together, these enable third-party applications to benefit fully from the potential of Alcatel-Lucent Enterprise products. and verify a comprehensive range of third-party applications: to ensure proper inter-working, ALE International tests and verifies selected third-party applications that complement its portfolio. Successful candidates, which are labelled Alcatel-Lucent Enterprise Compliant Application, come from every area of voice and data communications. The Alcatel-Lucent Application Partner Program covers a wide array of third-party applications/products designed for voice-centric and data-centric networks in the enterprise market, including terminals, communication applications, mobility, management, security, etc.

60 Web site The Application Partner Portal is a website dedicated to the AAPP program and where the InterWorking Reports can be consulted. Its access is free at Enterprise.Alcatel-Lucent.com You can access the Alcatel-Lucent Enterprise website at this URL:

61 14 Appendix F: AAPP Escalation process 14.1 Introduction The purpose of this appendix is to define the escalation process to be applied by the ALE International Business Partners when facing a problem with the solution certified in this document. The principle is that ALE International 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, ALE International and the Application Partner, are engaged as following: (*) The Application Partner Business Partner can be a Third-Party company or the ALE International Business Partner itself