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

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

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

Checks SpagoBI and statistics using sample reports

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

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

Verify that desktop assistant MSI installer is build and works

Checks that the signed desktop assistant on the mirror is downloadable, signed, can be installed, and launch

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.

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.

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

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

Calls between external user and webrtc on MDS 

Test new XiVO UC installation on Deneb or newer XiVO

We want to test group managmement through API.

We want to be able to create, read, update and delete groups using the API.

Test the basic conference feature :

• without PIN
• with user PIN

Checks that boss filter works

See https://documentation.xivo.solutions/en/latest/ipbx_configuration/boss_secretary_filter.html for configuration

This is mainly to test thath dxtorc is working.

Test monitoring on Webi > Services > Monitoring page

Test results of "xivo-service restart all"

• Services are stopped without delays and errors
• Services are started without delays and errors

Start and stop sequence when shutting down or booting is not handled by xivo-service. So it is different.

Note: Services should start even if monit is not running, but some of them fail because db is not running

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

Be able to duplicate existing IVR flowchart

Checks that the action buttons works as expected

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

Checks that mass import works

Download switchboard stats reports using webi in pdf

Check if agent pause status is correctly reported

Test the Queue Waiting Call counter

The goal of this test is to verify the feature 3008 (https://projects.xivo.solutions/issues/3008).

Verify that an agent can go from Wrapup state to Ready and Pause state

Testing if bug #4448 was fixed.

Install new Xivo CC with these dialog answers :

• Configure XiVO PBX
• Do not restart XiVO PBX

On any queue call, there is a single row in xc_queue_call.

Checks that UA user can use the boss secretary filter as expected
See https://documentation.xivo.solutions/en/latest/ipbx_configuration/boss_secretary_filter.html for configuration

Checks that UA users can use group calls

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

The purpose of this test is to verify that we have the sip call id for different scenario.

We want to make sure a web service user can be authenticated with the right credentials which allows to create a JWT token.

We want to make sure a web service user can be authenticated with the right credentials which allows to create a JWT token.

The goal of this test is to verify that we can have nested path to retrieve nested conf values

Verify that configmgt send the firebase token if configured on XIVO

Test the tel: and callto: protocol for at least windows (built-in) and linux (manual procedure)

• test.html : test.html
• test.html

This test needs to be launched on two platforms (Windows and Linux), it checks :

- When you click on close button of the desktop assistant it does'nt close the app if configured in settings. 

- It launches at startup of the OS if defined

- Test notification icons in Tray notification bar

Check the desktop assistant global short key

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

Checks that a warning is displayed when refreshing the desktop apps during an ongoing call. 

This test checks that the desktop app can be resized correctly

When clicking on the button, jitsi video can be extended

Test that resize is working smoothly when resizing desktop assistant

Check that the contextual menu works on electron

Verify that we can use the autologin by token with the -t parameter in electron

The purpose of this test is to verify that Asterisk on XiVO Main and all XiVO Media servers is reloaded.

There are two ways how the asterisk reload commands are sent when using webi:

Webi > confd API > rabbitmq > all mds

• line
• voicemail

Webi > rabbitmq > all mds

• user
• agent
• queue

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.

You are able to start and stop jitsi video conference

Test few scenarios for personal meeting room (PMR) invitation link.

1) login to UC Assistant with U1 and let anonymous user join first, then join with U1.

2) login to UC Assistant with U1, join the PMR1 and then join with anonymous user.

You can't access two meeting rooms at the same time (either the same or one another)

Test that you can invite another user in a conference you were invited in

   have a waiting message when we call user connected on his mobile app

Checks that user with mobile can use the boss secretary filter as expected
See https://documentation.xivo.solutions/en/latest/ipbx_configuration/boss_secretary_filter.html for configuration

Checks if *8 works for users with mobile app

Checks that users with mobile app can use group calls

User can see mobile - web switch and change their preferred device to receive incoming calls

Test that we can set / update a token for mobile push notification for mobile application users.

This test check if you have correctly an information notification in the UC Assistant application when you connect for the first time after having paired the mobile application with your account.

Assistant can be dissociated from the mobile app 

 non webrtc user should not be able to see the ringing device menu

If the call managment modal is opened, and I register or unregister from the mobile app, I want the switch to act accordingly without having to close the modal first

Test that we display a modal when mobile application is not compatible with line config

Test hat we don't allow mobile user to connect if no Firebase key for push notification is configured

   have a waiting message when we call user connected on his mobile app

Tests that the ring direction works as expected with the webapp and the mobileapp

The purpose of this test is to test these variables :

The purpose is to test the global variable in XIVO_MAPP_WAIT_WITH_MUSIC=True (no double quotes !) in /etc/xivo/asterisk/xivo_globals.conf

Then do a 'dialplan reload' in asterisk console ('asterisk -r' on xivo)

Basically if set to true you should have a music while we try to reach a mobile app user

 Check that iOS push token is correctly registered when the user logins to the application 

 Check that android push token is correctly registered when the user logins to the application 

Test if mobileApp wakes up when we call mobileApp user on his "locked"  mobile