Tests that multiple PJSIP contacts may ring at the same time and don't overlap each others

Mobile application attached to a webrtc user U1 on main

Mobile application attached to a webrtc user U2 on mds

User U3

Launch mobile application and connect user U1

User is connecetd to mobile APP

Open UC assistant and connect same user U1

User is connected to UC assistant

Make a call from user U3 to U1

U1 mobile app is ringing

U1 UC is ringing

Answer the call from Mobile 

UC of U1 should stop ringing and call should disapear from call line

Hangup call, make a call from U1 UC to U3

UC of U1 shows a call line

No call displayed in mobile APP

Hangup call, make a call from U1 mobile App to U3

UC of U1 shows no call

Call is displayed in Mobile App

Make an attended transfer from UC assistant

calls are only displayed in UC assistant

Hangups calls and make an attended transfer from mobile App

calls are only displayed on mobile App

Disconnect U1 from mobile APP and UC assistant

user is logged off

Launch mobile App and connect User U2 (mds user)

User U2 is connected to mobile App

Open UC assistant and connect same user U2

User U2 is connected to UC assistant

Make a call from U3 to U1

U2 mobile app and U2 UC assistant is ringing

Answer the call from mobile

Call is answered

Hangup call and make a call from mobile to U3 and answer it

U3 and U1 are in conversation

Recording saves call records and Configuration manages users that can access it

Configuration: Login as "avencall" with password "superpass" using https://XIVO_IP/configmgt URL

You should be logged in and see list of users

Configuration: Type a letter into search field on the right side

Drop-down list of XiVO users appears

Configuration: Through fingerboard open configuration

Login as "avencall" with password "superpass"

You should be logged in and see list of users

Configuration: Type a letter into search field on the right side

Drop-down list of XiVO users appears

Configuration: Select a user that has XivoCC login and password defined
(in Xivo configuration > IPBX settings > Users > XiVO Client section)

Add him (with "+" button)

Select Superviseur profile, assign him to a queue and confirm

The user appears in the list of users

Recording: Try login as user that has login and password defined in Xivo configuration, but he is not in CC Configuration

User is recognized, but can't login

Message "Aucun droit d'accès n'existe pour vous" appears

Call a queue, answer, talk to the microphone

Recording: Login as the newly added user

You are logged in

Recording: Open the first tab - Liste des enregistrements

You should see list of call records

Recording: Check the most recent call records (on top)

Last record should be recent

Records should have different length

If the topmost record has zero length, refresh the page

Recording: Download a recent record

Wav file is downloaded

Recording: Open the file in default media player

Test record is being played
(although calls from loadtester may not contain any sound)

Configuration: Refresh the page to see if you are still logged in. Login if not

Delete the newly added user

The user disappears from the list of users

Agen can login, change styate, see available agents on its queue

Agents A1 and A2, both assigned to Q1, not logged in to the agent interface 

Agent A1  put the username and password and click to the button "Se connecter"

Agent A1 is logged in the Agent interface. A1 state is Ready (green icon).

Agent A1 is logged.

Agent A1 sees his queue and calls in queue. A1 state is Ready (green icon).

In CCManager agent view check value of statistic "Tot. Pause"
Agent A1 change his state Ready into Pause.

A1 state is Paused (red icon).

Agent A1 change his state Pause back into Ready.

A1 state is Ready (green icon).

In CCManager verify that statistic "Tot. Pause" was incremented.

Agent A2 is logged

A2 device must be available (on mds0 = main)

In Activities tab move cursor on queue Q1 on Status column and verify that number of Avail. agents increased

Logout A2

In Activities tab move cursor on queue Q1 on Status column and verify that number of Avail. agents decreased

Checks the Kibana panels

Xivo and XivoCC installed, at least one agent in a queue and some calls passed

Open Kibana in a browser

Kibana welcome page is shown

To import some data in Kibana, follow this documentation: https://documentation.xivo.solutions/en/latest/administrator/xivocc/configuration/reporting.html#import-default-configuration-and-demo-dashboards
(path : application configuration -> reporting) 

You should see some calls in following widgets:

TOUTES FAS

APPELS RÉPONDUS PAR FA

Checks SpagoBI and statistics using sample reports

Xivo and XivoCC installed, at least one agent in a queue, some calls passed

Sample reports installed following the procedure described in the documentattion:

https://documentation.xivo.solutions/projects/xivo-nextlts/en/latest/installation/xivocc/installation/installation.html#spagobi

Open the SpagoBI and log in using biadmin/biadmin

You should be logged in

Open the Documents development item from the sidebar  (directory icon, the name is shown in a tooltip), then go to system directoty and open the data status report by clicking on it

You should get a rapport called Etat de la base des statistiques

in this rapport you have to check that dates for Dernier queuelog, Dernier cel, Call data and Call on queue correspond to the last call passed on the xivo and for the other tables the time should be at more half an hour before "now", means if you generated the report at 10.10, the time should be 9.30 or 9.45

Validate that the call history is generated and available through xuc interfaces

Xivo and XivoCC installed, some calls passed by user U1

Login to the xivo assistant as user U1

You should be logged in

Open the call history

You should see calls passed by user U1 with numbers translated to names for xivo users.

Verify that desktop assistant is available to be downbloaded from web interface and at least runs on Windows

• Open /etc/docker/compose/custom.env
• Change XUC_HOST to use address reachable from the windows machine
• Apply: xivocc-dcomp up -d

Go to https://<xivocc>/install/win64

Check that download starts 

On windows , right click on the installer .exe file  and check in properties that file is signed as Avencall

Application is marked as signed

Install it 

If the version >= Jabbah, check that the gif during installation is the xivo by wisper logo

The application is installed, starts

You can connect a user

User is connected

Dial *55

Call is OK

Verify that desktop assistant MSI installer is build and works

Go to http://jenkins.xivo.solutions:8080/job/desktop-assistant-msi-builder/ and download the MSI package of this release

Package is available

On windows with no desktop assistant, install the downloaded MSI package

Installation is successfull

Start the desktop assistant and logon

Application is started and user is connected

Test an outgoing WebRTC call using the latest Stable and Beta release of Chrome under Linux.

Please, write down in the comment box the exact versions of Chrome tested.

Webrtc users U1 U2 and U3
Install required Chrome from:

• Stable version for Linux
• Beta version for Linux
   

Install latest stable version of chrome, listed in the prerequisites

Login OK, registered in the navigator developer console.

Type an extension number in the search box and press Enter

You hear a ringback tone

Callee answers

You can talk with the callee

Callee hangs up

No more active calls in the Calls view

Test webrtc conferences : 
U2 calls U1 
U1 answers 
U3 calls U1 
U1 answers 
U1 merges the calls 

All three users are in a webrtc conference and can talk to each other

Repeat step 2-6 with latest Beta version of Chrome

For versions higher than Five.14 and Polaris.09 check that you have no warning about rtcpMuxPolicy in the developer console.

Connect U1 on chrome, U2 on chrome beta, U3 on electron
Call a conference with or without pin 

The users can call the conference and hear each other

Test an outgoing WebRTC call using the latest Stable and Beta release of Chrome under Windows.

Please, write down in the comment box the exact versions of Chrome tested.

webrtc users U1, U2 and U3 
Install required Chrome from:

• Stable version for Windows (64bits)
• Beta version for Windows (64bits)

XUC_HOST in the custom.env file must use network interface accessible from Windows

Install latest stable version of chrome, listed in the prerequisites

Login OK, registered in the navigator developer console.

Type an extension number in the search box and press Enter

You hear a ringback tone

Callee answers

You can talk with the callee

Callee hangs up

No more active calls in the Calls view

Test webrtc conferences : 
U2 calls U1 
U1 answers 
U3 calls U1 
U1 answers 
U1 merges the calls 

All three users are in a webrtc conference and can talk to each other

Repeat step 2-6 with latest Beta version of Chrome

Connect U1 on chrome, U2 on chrome beta, U3 on electron
Call a conference with or without pin 

The users can call the conference and hear each other

Test an outgoing WebRTC call using the latest Beta release of Chrome on the oldest currently supported LTS (at the time of writing -2020/12- this is Aldebaran).

Please, write down in the comment box the exact versions of Chrome tested.

The goal is to check that Chrome didn't deprecate any WebRTC and/or SSL/TLS that won't be compatible with an older version/configuration of asterisk (the goal is to not reproduce the #3676 bug)

For Aldebaran please follow procedure in ticket https://projects.xivo.solutions/issues/3676#Fix

Have XiVO/XiVOCC with oldest currently mainained LTS

Install required Chrome from:

• Beta version for Windows

Start your XiVO and XiVOCC for oldest currently maintained LTS

- till 2021/03 this is Aldebaran

- then till 2021/10 this will be Boréalis

Install latest stable version of chrome, listed in the prerequisites

Login OK, registered in the navigator developer console.

Type an extension number in the search box and press Enter

You hear a ringback tone

Callee answers

You can talk with the callee

Callee hangs up

No more active calls in the Calls view

any user

search for an user, unfold the userline and click click on his phone number

a toast should appear to tell you that the phone number is now copied to the clipboard

paste it somewhere to verify

click on his email

a toast should appear to tell you that the email is now copied to the clipboard

paste it somewhere to verify

search for a meetingroom and click on the sharing link button

a toast appears to tell you that the sharing link was copied to your clipboard
paste it somewhere to verify

re-do for UCAssistant or CCAgent (the one you've not done yet)

This test aims to verify that a webrtc user on mds1 can call and receive internal calls from a phone user on MDS0.  

MDS1 installed

WebRTC user W1 on MDS1

Phone user U1 on MDS0

Both connected on UCAssistant

U1 calls W1 from MDS0

W1 can pick up the call and speak to U1

W1 calls U1 from MDS1

U1 can pick up the call and speak to W1

From the webi, edit U1's line to MDS1  

Both W1 and U1 are on MDS1

U1 calls W1

W1 can pick up the call and users speak to each other 

W1 calls U1 

U1 can pick up the call and users speak to each other 

Calls between external user and webrtc on MDS 

An external user E1

A WebRTC user W1 on MDS1 

W1 connected to the XiVO assistant

W1 calls E1 

E1 receives the call and users can speak to each other

E1 calls W1 

W1 receives the call and users can speak to each other

Be able to join ivr using number from extern

This requires IVR Editor up and running

See 

 - doc is on the way as of 2021.15.05

Have 1 ivr created

Incoming call:

Did: 0123123007 or any matching prefix for your maquette
Context: incalls (from-extern)
Destination: IVR
Redirect to: IVR I1

Dial your DID from the prod user P1 using xivo-net eg. 2123007

Call is answered by the IVR

This requires IVR Editor up and running

See 

 - doc is on the way as of 2021.15.05

Have 1 IVR scenario created with a menu forwarding to a queue

Have an agent in that queue ready to answer calls

Incoming call:

Did: 0123123007 or any matching prefix for your maquette
Context: incalls (from-extern)
Destination: IVR
Redirect to: IVR MyScenario

Dial the correct DID from the prod to reach your IVR scenario

You should arrive in the menu

When the audio is played, press the corresponding button to go to the queue

You should then arrive in the queue waiting list and the agent should ring

Be able to duplicate existing IVR flowchart

This requires IVR Editor up and running

See 

 - doc is on the way as of 2021.15.05

Have 1 ivr created

In webi go to IVR index page Services -> IPBX -> IVR

You can see IVR flowcharts index with  at least 1 IVR listed (according preconditions)

Invoke flowchart duplication for by clicking star icon in the most right column

IVR duplication form opens

Insert unique name for the new IVR flowchart to the form and submit it

IVR flowcharts index apears and contains a the new flowchart with the name insrted to the form

Compare the original and the new flowchart

Both flowchart are same. They have same nodes (type, name, parameters) on same position on the screen and flowchart contains same connection between nodes.

Checks that the action buttons works as expected

One or more flowcharts already created

Go into Service > IPBX > Call management and open "IVR"

The list of already created flowcharts should appear

Try to rename one or more of them by clicking the pen icon

You can rename them

Try to open the configuration page by clicking on the cog icon

You can reconfigure them

Try to delete one or more of them

It should prompt you asking if you're sure to delete the flowchart
If pressing OK, it should delete it
If pressing Cancel, it should not delete it

This test checks that you can correctly add, edit and delete voiceprompts (the audio files available to be played in the ivr)

A web interface
A couple of short wav files

Go in services > ipbx > call management > ivr voice prompts

it should open the ivr voice prompts page

click on the orange button "load"

it should open the form to create a new voice prompt

fill in a description and a file and click upload

it should blame you for not filling in a name

fill the name then re-click upload

it should save your voiceprompt and go back to the list

click the pen icon in the bar of your newly created voiceprompt

it should open an edition form without the possibility to upload an audio file

change the name and the description and save

it should save and go back to the list (it should also prevent you from saving without a name)

click on the upload button (with a small disk and an arrow on the right of the edit button)

it should open an edition form with the possibility to upload a new audio file

update the audio file with a new one then save

it should allow you to change it and then go back to the list

click the play button

it should play the newly updated audio file

click on the trash icon

it should delete the voiceprompt

Checks that mass import works

Go in services > IPBX > call management > IVR voice prompts

the voice prompts page should be displayed

click mass upload

it should open a form with a select files button

select multiple files and validate

it should display them in a line
you can remove some of them if you want
you can rename some of them if you want

click upload

it should upload them and if all of them are validated, redirect you to the list of files

retry to upload, with a duplicate name

it should prevent you from uploading the duplicate

This test ensure the xuc connection to AMI is retry and is behaving well with multiples mds unreachable.

Have a XiVO and XiVO CC or XiVO UC working.

Have one configured mds mds1.

In webi : Configuration -> Media Servers, add 5 unreachable mds. (e.g. name: mds2, display name : media server 2, ip:  10.11.12.13) etc.

You have 6 mds in the webi : main, mds1 and 5 unreachable.

Check if xuc is connected to mds ami : execute following commands on mds1 machine.

`asterisk -rx "manager show connected"`

The result should contain xuc

Restart xuc (the goal here is just to synchronize AMI retry connection to help you to count the retry intervals)

open xuc logs `/var/log/xivocc/xuc/xuc.log` on xivocc machine

Open also configmgt logs `/var/log/xivo/xivo-confimgt/xivo-confimgt.log` on xivo machine

You should see xuc retry ami connection for each 5 mds each 2 minutes.

You also see the 5 requests in configmgt logs

Delete an unreachable mds from webi

You only see 5 retry for following requests

Open the AMI on mds1 : `asterisk -r` on mds1 machine

Then edit mds1 in webi (you don't need to change a value, just save the form)

You should see xuc instantly log out and log in from the cli

```

[Jun 27 09:45:39]   == Manager 'xuc' logged off from 10.181.31.3
[Jun 27 09:45:39]   == Manager 'xuc' logged on from 10.181.31.3

```

Create a new unreachable mds from the webi

You see an additionnal retry every 2 minutes (it may be not synchronised with the others)

Test for the new button in the desktop assistant which is used to switch inbetween UC Assistant, switchboard and CC Agent easily

Desktop assistant opened and not logged in

click the wrench icon (settings) in the top right corner

it should open the settings tab 

check if UC Assistant is selected by default

click on CC Agent and save the settings

it should reload the desktop assistant with the CC Agent inside

open the settings and select UC Assistant, then save

it should reload the desktop assistant with the UC Assistant inside

open the settings and select switchboard, then save

it should reload the desktop assistant with the switchboard inside

This test checks that the desktop app can be resized correctly

a desktop app installed and a webrtc connected on it

start the desktop app

it should be the same size as you left it

resize it as you wish

it should allow you to do whatever you want with it but there is still a minimal size that you cannot bypass

Test that resize is working smoothly when resizing desktop assistant

U1 logs in the assistant
U1 click on toggle maximize button

Window goes to maximized state

U1 reclick on toggle maximize 

Window goes back to inital state

U1 joins a meeting room
U1 clicks on maximize 

Window goes to maximized state

U1 reclick on toggle maximize 

Windows doesn't go to initial state but keep more width to see that a video is ongoing

Try to doucble click on title bar

Behaviour should be the same

To be tested on uc, cc and from XiVO >= Jabbah, also switchboard

When in an XDS installation I should see the correct status of every user of installation.

Note that currently (Callisto.02) the initial state is incorrect but becomes eventually correct.

XDS with 

- MDS0 with U01

- MDS1 with U11 and U12

- MDS2 with U21

After system is started up have log in UC Assistant with

U01

U11

and U21

For U01, U11 and U21 select as favorite

U01, U11, U12, U21

Check the state (at this time the state may be incorrect. this is normal as of Callisto.02)

U01 calls U11

State must be correct on all UC Assistant

- U01 (dialing)

- U11 (ringing)

U11 answers

State must be correct on all UC Assistant

- U01 (on call)

- U11 (on call)

U11 hangup

State must be correct on all UC Assistant

- U01 (idle)

- U11 (idle)

U12 calls U21

State must be correct on all UC Assistant

- U12 (dialing)

- U21 (ringing)

U12 hangup

State must be correct on all UC Assistant

- U12 (idle)

- U21 (idle)

Related to bug #2282

Test we can recover successfully from an AMI disconnection

Initiate a call from web-assistant and destination answers

A call is displayed in web-assistant

• Block xuc ip from the xivo server (assuming 192.168.56.1 is xuc IP address)
  `iptables -A INPUT -s 192.168.56.1 -p tcp --dport 5038  -j REJECT --reject-with tcp-reset`
• Try to make another call from web-assistant to trigger the Ami failure from the xuc point of view

The web-assistant should be still available but no call is displayed in the user interface

Hangup call manually on the phone

• Unblock xuc IP:
  `iptables -D INPUT -s 192.168.56.1 -p tcp --dport 5038  -j REJECT --reject-with tcp-reset`
• Wait a minute while the xuc reconnect to the ami
• Emit another call

A call should be displayed in the web-assistant