Product Acceptance: net.Desktop 2.26

This section provides a list of functional test which can be executed in order to verify the installation of the net.Desktop X100, X300 and X500. Define the test objectives, and select the tests or part of the tests relevant in your usage context. The tests in the list below are to be executed in the order provided here.

Starting point

  • net.Desktop 2.26
  • Sop with a PSTN connection
  • Three users (identified as UserA, UserB, UserC) with their own extension, deskphone and net.Desktop WCEx permission on SOP A
    • Possible permission combinaison to consider are:
      • WCE1 permission v1.2
      • WCE3 permission v1.3
      • WCE5 permission v1.8
    • All three have to belong to the same (pickup) group
    • All of them needs to have filled the mobile number and email address with real values
  • One user (identitied as UserD) must be configured on another SOP in the cluster, SOP B.
  • Three PCs with webcams (for the video tests)

Installation tests (X100, X300, X500)

1.1 Install net.Desktop using the msi installation procedure (from http://<sopip>/netDesktop/netDesktop.msi) with the default installation procedure
  • context: Microsoft Windows OS only
  1. Check you get the Desktop shortcut and the ESCAUX folder on the Start Menu
  2. Check that it can be launched from both places

1.2 Install net.Desktop using msiexec
  • context: Microsoft Windows OS only
  • prerequesite: net.Desktop is already installed and cmd.exe is launched with admistrator rights
  1. Uninstall net.Desktop with : msiexec /x path_to_msi /quiet /norestart
  2. Install net.Desktop with : msiexec /i path_to_msi /quiet /norestart
  3. Check you get the Desktop shortcut and the ESCAUX folder on the Start Menu
  4. Check that it can be launched from both places

1.3 Install net.Desktop using the jnlp file
  • prerequisite: check the versino of the java runtime environment
  1. Check you get the Desktop shortcut and the ESCAUX folder on the Start Menu
  2. Check that it can be launched from both places

1.4 Install net.Desktop on Microsoft Windows OS, MAC OS X, Linux
  • Check that it can be launched

1.5 Roaming user data profile
  • context: Microsoft Windows OS only
  1. Check that the net.Desktop user foler size complies with roaming application data size policy of the company, if necessary

1.6 Upgrade resistant
  • Install a previous version of netdesktop on your pc. Next Try to upgrade to the newer version you are testing and check if the major function still work ( like ALT+Q)
In the past we had trouble that installing a newer version broke down some key feature. This is because the newer version was not able to read the current preferences file. Most of the clients upgrade there netdesktop and want aspect all feature still work and the newer version is compatible with the current preferences file

Login – Logout tests (X100, X300, X350, X500)

2.1. Non-existing username
  1. On PC A. Type any username but the UserA's username, and the correct UserA's password
  2. Check you are asked to type the correct credentials

2.2. Correct username and a faulty password
  1. On PC A. Type UserA's username and a wrong password
  2. Check you are asked to type the correct credentials

2.3. Password omission
  1. On PC A. Type UserA's username. Omit UserA's password
  2. Check you get the notification question mark

2.4. Add a space and a character to the username
  1. On PC A. Type UserA's username plus a space and a character, e.g. "userA@escaux.com a". Type the correct UserA's password
  2. Check you are asked to type the correct credentials

2.5. Add a space and a character to the password
  1. On PC A. Type UserA's username. Type UserA's password plus a space and a character, e.g. "passwordA a"
  2. Check you are asked to type the correct credentials

2.6. Fill up the content of the user name field (with a huge payload)
  1. On PC A. For instance, type UserA's username plenty of times in sequence so that you increase the payload, making the content of the username field really huge. Type the correct UserA's password
  2. Check you are asked to type the correct credentials

2.7. Fill up the content of the password field (with a huge payload)
  1. On PC A. Type UserA's username. For instance, type UserA's password plenty of times in sequence so that you increase the payload, making the content of the password field really huge)
  2. Check you are asked to type the correct credentials

2.8. Standard login
  1. On PC A. Type UserA's username. Type UserA's password
  2. Check the login succeeded: the application runs, the net.Desktop main windows is displayed

2.9. Logout
  1. On PC A. Exit net.Desktop
  2. Check that no java process from net.Desktop is still running (using taskmanager under Windows, and 'ps -ef' cmommand line under Linux or MAC)

2.10. Auto login
  1. On PC A. Type UserA's username and password. Select 'Auto Login' checkbox. Click on 'Login' button. Exit net.Desktop
  2. On PC A. Launch net.Desktop again and check that the login screen is bypassed
  3. Open settings, general, verify that "Auto login" is checked as expected. Uncheck it, exit net.Desktop and launch it again
  4. Check that you get the login screen where you still need to click login

2.11. Double login
  1. On PC A. Do a standard Login of UserA
  2. On PC B. Do a standard Login of UserA
  3. Check PC A gets notified he has been logged out. Click the 'OK' button

2.12. Double login on the same PC
  1. On PC A. Start net.Desktop, do a login of UserA. Don't log out. Do a login of UserA again on another net.Desktop instance
  2. Check you get notified the application is running and refusing to login again

2.13. Password forgotten
  1. On PC A. Type UserA's username and a wrong password
  2. When you are asked to type the correct credentials. Click on 'Reset password' button
  3. On PC A. Type UserA's username and the password you got via email
  4. Check the login succeeded. And the Application runs and the main window is displayed

2.14. Erased user
  1. On the SMP. Erase UserA, and click on 'apply changes' button
  2. On PC A. Type UserA's username. Type UserA's password
  3. Check UserA cannot login and you are asked to type the correct credentials
  4. Create UserA again

2.15. Authentication using the 'Trusted client' mode
  1. In the module details choose value WinLogon for "Authentication Type" then install the module
  2. Create/configure a username on the SOP that is the same with the workstation login username. Password does not matter, it will not be taken into account.
  3. Start net.Desktop, it will show progress authenticating with the workstation login username and will not ask for password
  4. net.Desktop should start normally
  5. Try the login with a windows domain "domain.com", a user in the SMP "user@domain.com" and a windows user "user"

2.16. Login in cluster mode with local user
  1. On PC A. Open netDesktop. Check with the following command that netDesktop is connected to SOP A
    • netstat -tanpu | grep java on linux
    • netstat -a -b on windows
  2. Type UserA username. Type UserA password
  3. Check that UserA is logged in. Check that netDesktop is connected to SOP A

2.17. Login in cluster mode with remote user
  1. On PC A. Open netDesktop. Check with the following command that netDesktop is connected to SOP A
    • netstat -tanpu | grep java on linux
    • netstat -a -b on windows
  2. Type UserD username. Type UserD password
  3. Check that UserD is logged in. Check that netDesktop is connected to SOP B

2.18. Login in cluster mode with local user again
  1. Be sure to do test 2.17 just before executing this one
  2. Open netDesktop. Check with the following command that netDesktop is connected to SOP B
    • netstat -tanpu | grep java on linux
    • netstat -a -b
  3. On PC A. Type UserA username. Type UserA password
  4. Check that UserA is logged in. Check that netDesktop is connected to SOP A

2.19. Login in cluster mode with a user that has changed SOP
  1. On PC A. Type UserD username. Type UserD password
  2. Check that UserD is logged in. Check that netDesktop is connected to SOP B
  3. Logout
  4. Go to the SMP and change UserD netDesktop resource from SOP B to SOP A
  5. On PC A. Type UserD username. Type UserD password
  6. Check that UserD is logged in. Check that netDesktop is connected to SOP A

2.20 Login with a LDAP user.
  1. Install LDAP Sync module and configure it so that you have LDAP users.
  2. Login using an LDAP user.

Chat (X350 and X500 only)

Prerequisite: Login each UserX on its net.Desktop instance

3.1. Send a chat
  1. On net.Desktop A. Open a chat session with UserB
  2. On net.Desktop A. Type a message and press enter
  3. On net.Desktop B. Check that it gets a notification popup, that the taskbutton is flashing and that the message is displayed

3.2. Receive a chat
  1. On net.Desktop B. Send a message back to UserA and check that the user receives it
  2. On net.Desktop A. Check it gets the message

3.3. Reopen the chat session
  1. On net.Desktop A. Close the Unified Communication Window (UCW) of UserB
  2. On net.Desktop B. Send a message to UserA
  3. Check that the taskbutton is flashing and it shows the previous as well as the new message

3.4. Send an URL link
  1. On net.Desktop A. Send a message with a large existing URL (more than 25 characters) in order to get a message with a chopped link
  2. On net.Desktop B. Check when you click on it the web browser opens it

3.5. Escalate to Video (X500 only)
  1. On net.Desktop A. Switch to Video view and start a video session
  2. On net.Desktop B. Accept it
  3. On net.Desktop A. Check you get both, your own video and the remote one

3.6 Escalate to Video (X350 and X500)
  1. Set up 2 net.Desktop, one X350 and one X500.
  2. On net.Desktop X500 try to escalate to a video session with net.Desktop X350 net.Desktop.
  3. On net.Desktop X500 you should see a message, explaining that the other party cannot send video.

3.7 Check that you cannot start video on X350 (X350 only)
  1. Check that the video icon is greyed out on X350 UCW.

SMS (X500 only)

Prerequisite: UserA needs to register his mobile number

4.1. Send an SMS to your colleague fails
  1. On net.Desktop B. Send a sms to UserC
  2. Check to get a warning notifying that UserC has no mobile phone

4.2. Send an SMS to your colleague succeeds
  1. On net.Desktop B. Send a sms to UserA
  2. Check callerID, and the message content on the mobile phone

4.3. Send a huge SMS
  1. On net.Desktop B. Send a huge (200 characters) sms to UserA
  2. Check that the message content is complete and chopped in two sms

4.4. Receive an SMS
  1. The mobile phone replies to the SMS
  2. On net.Desktop B. Check the message appears in UserA's Unified Communication Window (UCW), text messaging view

4.5. Send an SMS to an Outlook contact
  1. Create an Outlook contact with a real mobile number
  2. On net.Desktop A. Synchronise Outlook contacts. Send an sms to the previous added Outlook contact
  3. Check callerID, and message content on the mobile phone

4.6. On an undeliverable chat send it as an SMS
  1. On net.Desktop A. Exit
  2. On net.Desktop B. Send a chat to UserA
  3. On net.Desktop B. Click on 'SMS' button when you get the warning about 'Undeliverable chat message'
  4. Check callerID, and message content on the mobile phone

Email tests (X300, X350, X500 only)

5.1. Send
  1. On net.Desktop A. Click on the UserB's email icon
  2. Compose an e-mail and send it
  3. Check UserB has received it

5.2. On an undeliverable chat send it as an email
  1. On net.Desktop A. Exit
  2. On net.Desktop B. Send a chat to UserA
  3. On net.Desktop B. Click on 'e-mail' button when you get the warning about 'Undeliverable chat message'
  4. Check UserB has received it and that the content is the same as the undeliverable chat

Presence tests (X300, X350, X500 only)

Test setup:
  • net.Desktop1 connected on SOP1, with extension1 and phone1 for primary phone
  • net.Desktop2 connected on SOP1, with extension2 and phone2 for primary phone
  • extension3 with phone3 for primary phone

Test setup for cluster tests:
  • a cluster with two SOPs: SOP1 and SOP2
  • net.Desktop1 connected on SOP1, with extension1 and phone1 for primary phone
  • net.Desktop2 connected on SOP2, with extension2 and phone2 for primary phone

Phone status

6.1. Phone's status Ring notification
  1. Call extension3 from net.Desktop1
  2. Let phone3 ring. Check that phone's status for extension1 is busy in net.Desktop2

6.2. Phone's status Ringing notification
  1. From phone3 call extension1
  2. Let phone1 ring
  3. Check that phone's status for extension1 is busy in net.Desktop2

6.3. Phone's status Conversation notification
  1. From phone3 call extension1
  2. Answer call on phone1
  3. Check that phone's status for extension1 is busy in net.Desktop2

6.4. Phone's status Answer notification
  1. From net.Desktop1 call voicemail box (8500)
  2. Check that phone's status for extension1 is busy in net.Desktop2

6.5. Phone's status synchronization
  1. Check in net.Desktop2 that extension1 is Idle
  2. Stop net.Desktop2. From net.Desktop1 call extension3
  3. Answer the call
  4. Start net.Desktop2
  5. Check that existion1 is busy in net.Desktop2.

6.6. Phone registration notification
  1. From SMP>Advanced>System Status>Phone Status restart phone1
  2. Check in net.Desktop2 that phone for extension1 get greyed out and then back again once the phone is restarted

6.7. Phone registration synchronization
  1. Check in net.Desktop2 that phone for extension1 is not greyed out
  2. Shutdown phone1. Check in SMP>Advanced>System Status>Phone Status that phone1 is not registered
  3. If needed wait for phone1 to get unregistered. Start net.Desktop2
  4. Check in net.Desktop2 that phone for extension1 is greyed out

6.8. Cluster test - Phone's status clustering
  1. From net.Desktop1 call the voicemail box (8500). Check that the phone state for extension1 is busy

6.9. Cluster test - Phone's status synchronization
  1. Check that the phone's status for extension1 is idle in net.Desktop2. Stop net.Desktop2. From net.Desktop1 call the voicemail box (8500). Start net.Desktop2
  2. Check that phone' status from extension1 is busy in net.Desktop2
6.10. Cluster test - Phone registration clustering
  1. From SMP>Advanced>System Status>Phone Status, reboot phone1
  2. Check in net.Desktop2 that the phone icon for extension1 get grey when the phone goes down and is then re-enabled when the is up again

6.11. Cluster test - Phone registration synchronization
  1. Check in net.Desktop2 that the phone is not greyed out for extension1. Stop net.Desktop2. Shutdown phone2
  2. Check in SMP>Advanced>System Status>Phone Status that phone1 is unregistred. If not wait until it is (reguistration timeout). Start net.Desktop2
  3. Check in net.Desktop2 the phone is greyed out for extension1

Extension status

6.12. Extension's status notification
  1. Change status in net.Desktop1 for extension1
  2. Check in net.Desktop2 that extension's status for extesion1 has been changed

6.13. Extension's status synchronization
  1. Check status of extension1 in net.Desktop2
  2. Stop net.Desktop2. Change extension's status for extension1
  3. Start net.Desktop2
  4. Check the extension's status for extension1 in net.Desktop2

6.14. Cluster test - Extension's status clustering
  1. Change the extension's status on net.Desktop1
  2. Check that the status for the extension of net.Desktop1 has changed in net.Desktop2

6.15. Cluster test - Extension's status synchronization
  1. Check the extension's status for extension1 in net.Desktop2. Stop net.Desktop2. Change extension'status of extension1. Start net.Desktop2
  2. Check extension's status for extension1

net.Desktop status

6.16. net.Desktop registration notification
  1. Check in net.Desktop2 that keyboard activity is not greyed out for extension1
  2. Stop net.Desktop1
  3. Check in net.Desktop2 that keyboard activity is greyed out for extension1

6.17. net.Desktop registration synchronization
  1. Check in net.Desktop2 that keyboard activity is not greyed out for extension1
  2. Stop net.Desktop2
  3. Stop net.Desktop1
  4. Start net.Desktop2
  5. Check in net.Desktop2 that keyboard activity is greyed out for extension1

6.18. net.Desktop keyboard activity
  1. Check in net.Desktop2 that keyboard activity is 'extended away'
  2. Type some keys on the PC running net.Desktop1
  3. Check that it the 'extended away' and 'away' are removed
  4. Check that after a while it goes in 'away' and then in 'extended away' according to related timers

7. Video tests (X500 only)

NOTE As of this moment, Zoiper and net.Desktop's on Vista both fight for the same port. You need to exit zoiper when relaunching net.Desktop. It is recommended to disconnect zoiper until the final video tests.

Test setup: Video during a chat 'Ask'. Video during a phone call 'Accept always'

7.1. H264 codec
  1. In the net.Desktop resource of UserA and B, set preferred codec to H264 . Apply changes on the smp
  2. Logout and back in both UserA and UserB's net.Desktop
  3. In net.Desktop A. Get the UCW of UserB on Video view. Click the webcam
  4. Check that UserB gets a video chat request with a popup to accept the chat. Click yes and check that video communication is established
  5. click stop video (red button)

7.2. 512 kbps bandwidth (H264 codec)
  1. Open settings and change preferred video bandwidth from 128 to 512. Retry the video chat
  2. Check that video communication is established
  3. Click stop video (red button)

7.3. Theora vs H263+ codec (128 bandwidth)
  1. In the net.Desktop resource of UserB, set preferred codec to H264 (Discovery testing: h263+). Apply changes on the smp
  2. Logout and back UserB's net.Desktop
  3. In net.Desktop A. Get the UCW of UserB on Video view. Click the webcam
  4. In net.Desktop B. Accept the video chat request
  5. Check that video communication is established though both parties selected a different video codec as preferred
  6. Click stop video (red button)

7.4. H263+ codec (128 bandwidth)
  1. In the net.Desktop resource of UserA, set preferred codec to H264(Discovery testing: h263+). Apply changes on the smp
  2. Logout and back UserA
  3. In net.Desktop A. Get the UCW of UserB on Video view. Click the webcam
  4. Check that video communication is established
  5. Check that the quality is at least as good as before
  6. Click stop video (red button)

7.5. 512 kbps bandwidth (H263+ codec)
  1. Open settings and change preferred video bandwidth from 128 to 512. Retry the video chat
  2. Check that video communication is established

7.6. Videophone
  1. On net.Desktop A. Establish a call with UserB. Add Video to the conversation
  2. Check both sides are able to see both remote and local video image on the Video view and audio as working well

7.7. Stop Videophone
  1. On net.Desktop A. Stop the video
  2. The video at both sides should stop

7.8. Hangup Videophone
  1. On net.Desktop A. Add video to the current call. Hangup the phone call
  2. The video at both sides should stop, even if the 'Close net.Desktop contact' option is set to 'manually'

7.9. Videochat
  1. On net.Desktop A. Establish a chat with UserB. Add Video to the conversation
  2. Check that video still works fine and chatting as well

7.10. Swap from Video to Chat
  1. On net.Desktop A. Switch to chat view
  2. On net.Desktop A. Check you get the remote video on top of the UCW and that you can continue chatting, both receiving and sending messages

7.11. Stop Videochat
  1. On net.Desktop A. Switch to Video view and stop video (click on the 'Stop video' icon)
  2. On both net.Desktop. Check video has stopped

7.12. Close Videochat
  1. On net.Desktop B. Send a message to UserA
  2. On net.Desktop A. Escalate to Video (open a video session)
  3. On net.Desktop B. Switch to chat view and send a chat. Close the UserB's UCW
  4. On net.Desktop A. Check video has stopped

7.13. Undock control
  1. Check undock action works

7.14. Dock control
  1. Check dock action works

7.15. Mirror control
  1. Check mirror action works

7.16. Picture in picture control
  1. Check flip action works

7.17. Fullscreen control
  1. Check fullscreen action works

7.18. Snap control
  1. Check a snap-shot photo is saved in your user directory

7.19. Camera disconnected
  1. On net.Desktop A. Disconnect webcam. Try to establish a video communication with UserB
  2. Check that a warning should be displayed explaining that your webcam is not connected
  3. On net.Desktop A. Connect webcam

7.20. Other party does not have webcam
  1. On net.Desktop B. Disconnect webcam
  2. On net.Desktop A. Try to establish a video communication with UserB
  3. Check that a warning should be displayed explaining that the other party does not have video
  4. On net.Desktop B. Connect webcam

7.21. QoS
  1. Using tethereal, check that the QoS settings are effectively translated in the correct DSCP marking of the audio traffic

7.22. Max bandwidth enforcement
  1. Check that the settings as defined in the inter-site Media Links is effectively enforced in the net.Desktop video settings

7.23. at Startup
  1. Verify that the webcam light is turned off (no video grabbing) at startup (and after closing video)

FAX (X500 only)

Prerequisiste:
  • Fax server module installed on SOP1
  • net.Desktop1 connected on SOP1, with extension1 and phone1 for primary phone
  • pdf writer in order to print documents as pdf file

8.1. Fax sending (X500 only)
  1. In net.Desktop1>Settings>Fax, check the directory to be monitored by net.Desktop for outging faxes
  2. Open your favorite office suite and open any document
  3. Print the document with the pdf-writter and save the document in the directory monitored by net.Desktop
  4. A popup appear requesting the phone number where to send the fax. Once sent, it will be moved in Media>Fax>Sent

8.2. Fax viewing
  1. In Media>Fax>Sent, click on 'view' icon
  2. Check that the document get open with the default pdf viewer of the PC

8.3. Fax deletion
  1. In Media>Fax>Sent, click on 'delete' icon
  2. Check that you can delete the document
  3. Check if the fax is removed on the file system

8.4. Fax sending with a specific fax server (X500 only)
  1. Configure the WCE5 resource using the IP, not the extension. And fill credentials accordingly
  2. Do the test 8.1

8.5 Check for notifications.
  1. Configure your net.Desktop resource with a local fax extension that is prepared to send email notifications.
  2. Send a fax.
  3. Check that you receive a notification in the mailbox configured in the local fax extention.

Recording (X500 only)

Test setup:
  • net.Desktop1 connected on SOP1, with extension1 and phone1 for primary phone, with permission for call recording (see permission and WCE5 resource)
  • extension2 with phone2 for primary phone

9.1. Call recording
  1. From net.Desktop1 call extension2
  2. Answer the call
  3. In the communication window of net.Desktop1 click on the record icon
  4. Hang up the call
  5. After 1 minute, check in net.Desktop1 in Media>Recorded Calls>Inbox that you can find the recorded call

9.2. Recorded call listening
  1. In net.Desktop1, Media>Recorded call>Inbox, click on 'Listen' icon
  2. Check that you can hear the recorded call

9.3. Old recorded call
  1. In net.Desktop1, Media>Recorded call>Inbox, click on 'Move to Old' icon
  2. Check that recorded call can be moved from Media>Recorded call>Inbox to Media>Recorded Call>Old

9.4. Recorded call deletion
  1. Check that recorded call can be deleted in Media>Recorded call>Inbox and Media>Recorded Call>Old

Voice mail (X300, X350, X500 only)

Test setup:
  • net.Desktop1 connected on SOP1, with extension1 and phone1 for primary phone, with permission for call recording
  • extension2 with phone2 for primary phone
  • callflow sending to voicemail in case of no answer

10.1. Voice message reception
  1. From phone2 call extension1
  2. Wait for call to drop in voicemail
  3. Leave a message in the mailbox
  4. Check in Media>Voicemail>Inbox that voice message can be found

10.2. Voice message listening
  1. In net.Desktop1, Media>Voicemail>Inbox, click on 'Listen' icon
  2. Check that you can listen to the voice message

10.3. Old voice message
  1. In net.Desktop1, Media>Voicemail>Inbox, click on 'Move to Old' icon
  2. Check that file has been effectively moved

10.4. Voice message deletion
  1. Check that voice message can be delete in Media>Voicemail>Inbox and Media>Voicemail>Old

10.5. voicemail synchronization
  1. Stop net.Desktop1
  2. From phone2 call extension1
  3. Wait for call to drop in voicemail
  4. Leave a message
  5. Start net.Desktop1
  6. Check voicemail in Media>Voicemail>Inbox

Call tests (X300, X500 only)

Test setup:
  • Be sure each user has Office as status

Inbound call

Call ringing

  1. On net.Desktop A. Using the desk phone, call UserB's extension
  2. Check that on both sides net.Desktop show a UCW
  3. Hangup

Stop ringing by the caller side

  1. On net.Desktop A. Using the desk phone, call UserB's extension
  2. On net.Desktop A. Click on the 'Hangup' button in the UserB's UCW
  3. Check that both phones stop ringing and that the 'Hangup' button on top is no longer enabled

Stop ringing by the called side

  1. On net.Desktop A. Using the desk phone, call UserB's extension
  2. On net.Desktop B. Click on the 'Hangup' button in the UserA's UCW
  3. Check that both phones stop ringing and that the 'Hangup' button on top is no longer enabled

Outbound call

Establish a call via the desk phone

  1. On net.Desktop A. Using the desk phone, call UserB's extension
  2. On net.Desktop B. Pickup the phone
  3. Check that on both sides net.Desktop show a UCW and that a call is established
  4. Hangup

Establish a call via the UCW

  1. On net.Desktop A. Get the UserB's UCW. Click on the 'Call' button
  2. Check that phone A is receiving a call from asterisk, accept it
  3. Check that phone B rings. Pickup the phone
  4. Check that the call is established and that 'Hangup', 'Record' and 'Consult' buttons (UCW) are enabled
  5. Hangup

Establish a call via the Unified Directory

  1. On net.Desktop A. Click on phone icon of UserB in the directory
  2. Check that phone A is receiving a call from asterisk, accept it
  3. Check that phone B rings. Pickup the phone
  4. Check that the call is established and that 'Hangup', 'Record' and 'Consult' buttons (UCW) are enabled
  5. Hangup

Establish a call via the Free Number option (net.Desktop)

  1. On net.Desktop A. Type the extension of UserB in the 'number field' at the bottom of net.Desktop. Click on the 'Dial button'
  2. Check that the UserB's UCW pops up, showing the 'Details' view
  3. Check that phone A is receiving a call from asterisk, accept it
  4. Check that phone B rings. Pickup the phone
  5. Check that the call is established and that 'Hangup', 'Record' and 'Consult' buttons (UCW) are enabled
  6. Hangup

Establish a call via Quick Number

  1. On net.Desktop A. Type the extension of UserB in the notepad of other application. Select it and launch Quick Number (alt-q by default). Make a call
  2. Check that the UserB's UCW pops up, showing the 'Details' view
  3. Check that phone A is receiving a call from asterisk, accept it
  4. Check that phone B rings. Pickup the phone
  5. Check that the call is established and that 'Hangup', 'Record' and 'Consult' buttons (UCW) are enabled
  6. Hangup

Call Pickup

Pickup via net.Desktop

  1. On net.Desktop A. Activate 'Group pickup' on your group. (SMP: On each user's extension set the pickup group equal to '1'. On net.Desktop check 'Show Notification' on preferences, rigth click on 'My Group' node and enable 'Group Pickup' )
  2. On net.Desktop B. Call UserC's extension
  3. On net.Desktop A. When get a notification click on the pickup pop-up. Pickup your phone
  4. Check that Phone C stops ringing. Check the call is established
  5. Check that UCW of net.Desktop A shows caller number of caller and contact information if now in the directory and the display name as provided by the callflow (new in net.Desktop 2.25)
  6. Hangup

Pickup via Desktop phone

  1. UserB and UserC are in the same pickup group
  2. UserA calls UserB
  3. UserC dials the pickup extension (*8)
  4. The UCW of net.Desktop C shows the dialled number *8 (known limitation of asterisk 1.2)

Pickup call coming from a queue (via net.Desktop)

  1. UserB and UserC are in the same pickup group
  2. UserC is added as member of a Queue, with Member Ringing Time > net.Desktop resource Pickup timeout
  3. UserA calls UserC's Queue
  4. When net.Desktop B shows a notification popup, click on the pickup button
  5. Check that Phone C stops ringing. Check the call is established
  6. Hangup

Call transfer

Test setup:
  • Add consultation callflow 234* which includes the 'via' in the display name
  • Enable re-invite on Desk Phone (new in asterisk 1.2 v 2.32.6)

Attended Transfer to a mobile phone

  1. On net.Desktop B. Establish a phone call with UserC
  2. On net.Desktop C. Press the 'Consult Call' button on UserB's UCW
  3. On net.Desktop C. In the mini directory type the mobile phone number. Click on the phone icon
  4. Check UserB get music on hold
  5. Pick up mobile phone
  6. On net.Desktop C. Click on 'Transfer' button
  7. Check the call between A and B is established
  8. The UCW of net.Desktop B and shows the dialled number (limitation with asterisk 1.2)
  9. Hangup

Attended Transfer to an external number

  1. On net.Desktop B. Establish a phone call with UserC
  2. On net.Desktop C. Press the 'Consult Call' button on UserB's UCW
  3. On net.Desktop C. In the mini directory type the external number. Click on the phone icon
  4. Check UserB get music on hold
  5. Pick up the phone behind the external number
  6. On net.Desktop C. Click on 'Transfer' button
  7. Check the call between the external number and B is established
  8. The UCW of net.Desktop B and shows the dialled number (limitation with asterisk 1.2)
  9. Hangup

Attended Transfer of an internal call to a desk phone

  1. On net.Desktop B. Establish a phone call with UserC
  2. On net.Desktop C. Press the 'Consult Call' button on UserB's UCW
  3. On net.Desktop C. In the mini directory search for UserA. Click on UserA's desk phone icon
  4. Check UserB get music on hold
  5. The UCW of net.Desktop A shows the caller number and contact information of UserB and the Display name " via " (new in net.Desktop 2.25)
  6. Pick up UserA's phone
  7. On net.Desktop C. Click on 'Transfer' button
  8. Check the call between A and B is established
  9. The UCW of net.Desktop B shows the dialled number (limitation of asterisk 1.2)
  10. The UCW of net.Desktop A shows the caller number and contact information of UserB and the Display name " via " (no update on connect, limitation of asterik 1.2)
  11. Hangup

Attended Transfer of an external call to a desk phone

  1. From a public phone Establish a phone call with UserC
  2. On net.Desktop C. Press the 'Consult Call' button on UserB's UCW
  3. On net.Desktop C. In the mini directory search for UserA. Click on UserA's desk phone icon
  4. Check UserB get music on hold
  5. The UCW of net.Desktop A shows the caller number and contact information of UserB and the Display name " via " (new in net.Desktop 2.25)
  6. Pick up UserA's phone
  7. On net.Desktop C. Click on 'Transfer' button
  8. Check the call between A and B is established
  9. The UCW of net.Desktop B shows the dialled number (limitation of asterisk 1.2)
  10. The UCW of net.Desktop A shows the caller number and contact information of UserB and the Display name " via " (no update on connect, limitation of asterik 1.2)
  11. Hangup

Early Attended Transfer of an internal call to a desk phone

  1. On net.Desktop B. Establish a phone call with UserC
  2. On net.Desktop C. Press the 'Consult Call' button on UserB's UCW
  3. On net.Desktop C. In the mini directory search for UserA. Click on UserA's desk phone icon
  4. Check UserB get music on hold
  5. The UCW of net.Desktop A shows the caller number and contact information of UserB and the Display name " via " (new in net.Desktop 2.25)
  6. On net.Desktop C. Click on 'Transfer' button before the consultee answers the call
  7. Pick up UserA's phone
  8. Check the call between A and B is established
  9. The UCW of net.Desktop B shows the dialled number (limitation of asterisk 1.2)
  10. The UCW of net.Desktop A shows the caller number and contact information of UserB and the Display name " via " (no update on connect, limitation of asterik 1.2)
  11. Hangup

Attended Transfer to an internal number of the call initiated by transferrer from the net.Desktop

  1. On net.Desktop C. Establish a phone call with UserB
  2. On net.Desktop C. Press the 'Consult Call' button on UserB's UCW
  3. On net.Desktop C. In the mini directory search for UserA. Click on UserA's desk phone icon
  4. Check UserB get music on hold
  5. The UCW of net.Desktop A shows the caller number and contact information of UserB and the Display name " via " (new in net.Desktop 2.25)
  6. Pick up UserA's phone
  7. On net.Desktop C. Click on 'Transfer' button
  8. Check the call between A and B is established
  9. The UCW of net.Desktop B shows the dialled number (limitation of asterisk 1.2)
  10. The UCW of net.Desktop A shows the caller number and contact information of UserB and the Display name " via " (no update on connect, limitation of asterik 1.2)
  11. Hangup

Attended Transfer to an internal number of a call initiated by transferrer from the phone

  1. From phone of UserC. Establish a phone call with UserB
  2. On net.Desktop C. Press the 'Consult Call' button on UserB's UCW
  3. On net.Desktop C. In the mini directory search for UserA. Click on UserA's desk phone icon
  4. Check UserB get music on hold
  5. The UCW of net.Desktop A shows the caller number and contact information of UserB and the Display name " via " (new in net.Desktop 2.25)
  6. Pick up UserA's phone
  7. On net.Desktop C. Click on 'Transfer' button
  8. Check the call between A and B is established
  9. The UCW of net.Desktop B shows the dialled number (limitation of asterisk 1.2)
  10. The UCW of net.Desktop A shows the caller number and contact information of UserB and the Display name " via " (no update on connect, limitation of asterik 1.2)
  11. Hangup

Call rejected by the consultee

  1. On net.Desktop B. Establish a phone call with UserC
  2. On net.Desktop C. Press the 'Consult Call' button on UserB's UCW
  3. On net.Desktop C. In the mini directory search for UserA. Click on UserA's desk phone icon
  4. Check UserB get music on hold
  5. On net.Desktop C. Click on 'Hangup' button
  6. Check UserA's desk phone stops ringing
  7. Check the call between B and C continue
  8. Hangup

Call cancelled by the transferrer

  1. From phone of UserC. Establish a phone call with UserB
  2. On net.Desktop C. Press the 'Consult Call' button on UserB's UCW
  3. On net.Desktop C. In the mini directory search for UserA. Click on UserA's desk phone icon
  4. Check UserB get music on hold
  5. The UCW of net.Desktop A shows the caller number and contact information of UserB and the Display name " via " (new in net.Desktop 2.
  6. On net.Desktop C. Click on 'Hang-Up' button
  7. Check that A's phone stop ringing
  8. Check that the communication is still established between C and B
  9. Hangup

Call transfer in cascade

  1. UserA calls user userB
  2. On net.Desktop B transfer to C
  3. The UCW of net.Desktop C shows the caller number and contact information of UserB and the Display name " via <caller name of
UserB>" (new in net.Desktop 2.25)
  1. On net.Desktop C transfer to D
  2. The UCW of net.Desktop D shows the caller number and contact information of UserC and the Display name " via <caller name of
UserB> via <caller name of UserC>" (new in net.Desktop 2.25)

Attended Transfer to a queue

  1. UserA has now a callflow that uses the Queue Action with the queue configured to play a music-on-hold
  2. On net.Desktop B. Establish a phone call with UserC
  3. On net.Desktop C. Press the 'Consult Call' button on UserB's UCW
  4. On net.Desktop C. In the mini directory search for UserA. Click on UserA's desk phone icon
  5. Check UserB get music on hold
  6. On net.Desktop C. Click on 'Transfer' button
  7. Check that B is in the queue.
  8. Hangup

Attended Transfer to a Conference Room

  1. UserA has now a callflow that makes the caller join a conference room
  2. On net.Desktop B. Establish a phone call with UserC
  3. On net.Desktop C. Press the 'Consult Call' button on UserB's UCW
  4. On net.Desktop C. In the mini directory search for UserA. Click on UserA's desk phone icon
  5. Check UserB get music on hold
  6. On net.Desktop C. Click on 'Transfer' button
  7. Check that B is in the conference room.
  8. Hangup

Call forward via a callflow

Redirect all calls to a colleague

  1. On net.Desktop UserB. Change your Intentional Status into 'Forward'. In Profile Parameters, set to UserC's extension the 'Number to forward to'
  2. On net.Desktop A. Call UserB's extension
  3. Check the Phone C is ringing. Pick up the phone and check the call is established
  4. Hangup
  5. On net.Desktop UserB. Change your Intentional Status into 'Office'

Redirect all calls to your mobile phone

  1. On net.Desktop UserA. Change your Intentional Status into 'Forward'. In Profile Parameters, set your mobile phone number as the 'Number to forward to'
  2. On net.Desktop B. Call UserA's extension
  3. Check your mobile is ringing. Pick up the phone and check the call is established
  4. Hangup

Advanced UCW interactions

Add chat

  1. On net.Desktop A. Establish a call with UserB
  2. On net.Desktop A. Switch to the Chat view and type a message
  3. On net.Desktop B. Check that the call continues and gets the message
  4. On net.Desktop B. Reply the message
  5. On net.Desktop A. Check that the call continues and gets the message
  6. Hangup

Close the UCW do not stop an established call

  1. On net.Desktop A. Establish a phone call with UserB
  2. On net.Desktop A. Close the UserB's UCW
  3. Check that the call continues

Web tests (X300, X350, X500 only)

Test setup

12.1. Static trigger
  1. On net.desktop A. Check that you see the static link in the 'Web branch' and triggers the external browser which shows the ESCAUX webpage

12.2. Dynamic trigger
  1. Using phone A call UserB
  2. Check that UserB triggers the external browser which shows the url http://www.google.com/search?q=xxx where xxx is the extension of UserA

12.3. Add link
  1. On net.Desktop B. Add a link by right-clicking on the 'Web branch'
  2. On net.Desktop B. Check that you see this link in the 'Web branch'

12.4. Remove Link
  1. On net.Desktop B. Remove an added link by right-clicking on the 'Web branch', 'Clear Custom'
  2. On net.Desktop B. Check that it has been removed from the 'Web branch'

Data sources tests (X300, X350, X500 only)

Test setup
  • At least UserA needs to have Outlook

13.1. Synchronise
  1. Click on the synchronize icon
  2. Check that the data sync window appears

13.2. Import Outlook contacts
  1. Check all of them have been added in the Unified Directory

13.3. Import ESCAUX UCS contacts
  1. Check all of them have been added in the Unified Directory

Buddy List tests (X300, X350, X500 only)

14.1. Create
  1. Right click on Contacts branch and select 'Add Buddy List'
  2. Check that it has been added

14.2. Edit
  1. Right click on the buddy list and choose 'Edit', rename it
  2. Check that it has been renamed

14.3. Drag contacts
  1. Drag contacts from the Unified Directory into the new buddy list
  2. Check that they are there

14.4. Add contacts
  1. Rigth click the contact you want to add, select the name of the buddy list
  2. Check the contact is there

14.5. Remove a contact
  1. Rigth click the contact you want to remove, select the name of the buddy list
  2. Check the contact has been removed

14.6. Remove
  1. Right click on the buddy list and choose 'Remove'
  2. Check the budddy list has been removed

Search tests (X300, X350, X500 only)

15.1. Search on part of a phone number
  1. On net.Desktop A. Type part (2 digits) of the UserB's phone number
  2. Check that in the Unified Directory UserB is displayed

15.2. Search on part of a name
  1. On net.Desktop A. Type part (2 characters) of the UserB's name
  2. Check that in the Unified Directory UserB is displayed

15.3. Save
  1. Save a specific directory search, clicking on 'Save Query...'. Rename it
  2. Check that it has been added in the Contacts branch

15.4. Edit
  1. Right click on the saved query list and choose 'Edit'
  2. Check that it has been changed

15.5. Set as default
  1. Right click on the saved query list and choose 'Set as default'
  2. Check that it has been set as default when click on the Contacts tab

15.6. Remove
  1. Right click on the saved query list and choose 'Remove', change query
  2. Check that it has been removed

Call History tests (X300, X350, X500 only)

Test Setup:
  • net.Desktop1 connected on SOP1, with extension1 and phone1 for primary phone, with mobile1 for mobile phone
  • extension2 with phone2 for primary phone
  • InternalDocs.Gateway with PSTN
  • Mobile2: a mobile phone whose number is not known in net.Desktop (enter the number in the search field of net.Desktop1)

16.1. Unanswered incoming call history
  1. From phone2 call extension1
  2. Hang up the call
  3. Check that the call appear in net.Desktop1>Call History>Missed and in net.Desktop1>Call History

16.2. Unanswered outgoing call history
  1. From phone1 call extension2
  2. Hang up the call. Check that the call appear in net.Desktop1>Call History>Called and in net.Desktop1>Call History with the right disposition (icon on the right)

16.3. Answered outgoing call history
  1. From phone1 call extension2
  2. Answer the call
  3. Check that the call appear in net.Desktop1>Call History>Called and in net.Desktop1>Call History with the right disposition (icon on the right)

16.4. Answered incoming call history
  1. From phone2 call extension1
  2. Answer the call
  3. Check that the call appear in net.Desktop1>Call History>Received and in net.Desktop1>Call History with the right disposition (icon on the right)

16.5. Call history synchronization
  1. Stop net.Desktop1. From phone2 call extension1
  2. Hang up the call
  3. Start net.Desktop1 and launch the manual synchronization if it's not already done
  4. Check that the call appear in net.Desktop1>Call History>Missed and in net.Desktop1>Call History with the right disposition (icon on the right)

16.6. Outgoing call to external number
  1. From phone1 call mobile2
  2. Hang up the call
  3. Check that the call appear in net.Desktop1>Call History>Missed and in net.Desktop1>Call History with the right disposition (icon on the right) and with the right called number.

16.7. Incoming call from non hidden external number
  1. Check that mobile2 called number is not hidden
  2. From mobile2 call extension1
  3. Hangup the call
  4. Check that the call appear in net.Desktop1>Call History>Missed and in net.Desktop1>Call History with the right disposition (icon on the right) and with the right caller number

16.8. Incoming call from hidden number
  1. Check that mobile2's called number is hidden
  2. From mobile2 call extension1
  3. Hangup the call
  4. Check that the call appear in net.Desktop1>Call History>Missed and in net.Desktop1>Call History with the right disposition (icon on the right) and with the unknown caller number

Keyboard shortcuts tests (X300, X350, X500 only)

17.1. Contact Lookup
  1. Verify alt-F6 pops up net.Desktop

17.2. Change Contact Lookup shortcut
  1. Verify the change you did has been taken into account

17.3. Quick Number
  1. Verify alt-Q pops up the Quick Number window

17.4. Change Quick Number shortcut
  1. Verify the change you did has been taken into account

Quick Number tests (X100, X300, X350, X500)

18.1. Filter characters
  1. On net.Desktop A. Type the extension of UserB in the notepad of other application add once at a time some characteres (/.\ ()-) between the number. Select it and launch Quick Number. Make a call
  2. Check that the character is well filtered and the call can be established

Intentional Status & Custom Message tests

19.1. Intentional Status button's icon (X100, X300, X350, X500)
  1. On net.Desktop A. Check the icon corresponds to the current Intentional Status

19.2. Change Intentional Status (X100, X300, X350, X500)
  1. On net.Desktop A. Change Intentional Status in the Intentional Status parameters window (clicking the Status button)
  2. Check the icon corresponds to the changed Intentional Status

19.3. Set a Custom Message (X300, X350, X500 only)
  1. On net.Desktop A. Enter the message in the 'Custom Message' field and press enter
  2. On net.Desktop B. Check that in the Unified Directory, UserA's extension will show the Intentional Status and the Custom Message

Notification tests (X300, X350, X500 only)

NOTE Check 'Show notification'.

20.1. When a colleague is available for chat
  1. On net.Desktop B. Logout
  2. On net.Desktop A. Rigth click on UserB, and request to be 'Notify when available for chat'
  3. On net.Desktop B. Login
  4. On net.Desktop A. Check you get a notification

20.2. When a colleague is available on phone
  1. On net.Desktop B. Establish a call con UserC
  2. On net.Desktop A. Rigth click on UserB, and request to be 'Notify when available on phone'
  3. On net.Desktop B. Hangup
  4. On net.Desktop A. Check you get a notification

20.3. When lost connectivity with SOP
  1. On net.Desktop A. Unplug the network cable (disable wireless network discovery too)
  2. On net.Desktop A. Check you get a red notification

20.4. When get connectivity back with SOP
  1. On net.Desktop A. Plug the network cable
  2. On net.Desktop A. Check you get a green notification

System tray icon tests (X100, X300, X350, X500)

Note For X300, X350 and X500, the system tray icon is available under Windows only.

21.1. Present
  1. Check that the system tray icon is present

21.2. Status icon
  1. Check the system tray icon corresponds to the current itentional status

21.3. Change the intentional status
  1. Right click on the system tray icon. Change the intentional status
  2. Check the tray icon corresponds to the changed intentional status

21.4. Pop up net.Desktop (X300, X350, X500 only)
  1. Check that double clicking the system tray icon raises net.Desktop

21.5. Open 'net.Desktop' window (X300, X350, X500 only)
  1. Right click on the system tray icon. Click on 'net.Desktop'
  2. Check that net.Desktop is displayed

21.6. Open 'About' window
  1. Right click on the system tray icon. Open 'About...' and check contents

21.7. Open 'Preferences' window (X300, X350, X500 only)
  1. Right click on the system tray icon. Open 'Preferences...'. Check that it opens

21.8. Expand 'Preferences' menu (X100 only)
  1. Right click on the system tray icon. Select 'Preferences...'. Check that it expands

21.9. Open 'QuickNumber' window (X300, X350, X500 only)
  1. Right click on the system tray icon. Click on 'Quick Number'. Check that the window is shown

21.10. Open 'Dial' window (X100 only)
  1. Right click on the system tray icon. Click on 'Dial'. Check that the window is shown

21.11. Manage the display of the intentional status list (X100 only)
  1. In the resource parameters configuration for the X100, enable/disable the display of the intentional status, do an 'apply changes'. Verify the change you did shows/hides the intentional status list in the net.Desktop system tray

Clustering tests (X100, X300, X350, X500)

net.Desktop supports for the clustering consists in the following:
  • cluster wide visibility of the presence information (phone state, registration state, extension's status, keyboad presence is not supported)
  • intra-cluster instant messaging
  • intra-cluster video session
  • Active-Active is not supported by the current net.Desktop

22.1. Chat clustering
  1. Check that net.Desktop1 can chat with net.Desktop2

22.2. Disconnect LAN from PC running net.Desktop2
  1. Connect the PC via the Wifi, so that net.Desktop2 has to use another IP
  2. Check that net.desktop1 can send an instant message to net.Desktop2

22.3. Video clustering
  1. From net.Desktop1 call extension2
  2. Check the net.Desktop1 can initiate a video session with net.Desktop2

22.4. Change IP
  1. Disconnect LAN from PC running net.Desktop2
  2. Connect the PC via the Wifi, so that net.Desktop2 has to use another IP
  3. Check that net.desktop1 can still initiate a video session with net.desktop2

Language tests (X100, X300, X350, X500)

23.1. French
  1. In the preferences window/menu, change in general the language to French. Restart net.Desktop
  2. Check that everything is in French

23.2. Dutch
  1. In the preferences window/menu, change in general the language to Dutch. Restart net.Desktop
  2. Check that everything is in Dutch

23.3. English
  1. In the preferences window/menu, change in general the language to English. Restart net.Desktop
  2. Check that everything is in English

Memory tests (X100, X300, X350, X500)

24.1. Consumption
  1. At the time of this writing 29/10/09, net.Desktop consumes around 68Mb of memory. Check using windows Task manager or top command that the memory consumption hasn 't increased dramatically

24.2. Minor longevity test
  1. Leave net.Desktop running overnight, check that memory consumption is still at the level you noted above

Categories tests (X100, X300, X350, X500)

25.1 HTML Help
  1. Add some html content in the « Documentation field » of the profile used by netDesktop
  2. Open the extension settings and check that the help is shown correctly
  3. Check the box in the bottom of the help
  4. Open the extension settings again and check that the help is not shown

25.2 All parameters in main tab
  1. Install a new netDesktop instance (>=X300)
  2. Open the extention settings page
  3. Check that there is only one tab called main that contains all the parameters of the profile

25.3 Category creation
  1. Click on the profile name and add a new « Profile parameter form » with « (CATEGORY) » as Profile parameter.
  2. Apply changes, restart netDesktop and check that the tab does not appear in the extension settings page
  3. Select the newly created category and add a few parameters in it
  4. Apply changes, restart netDesktop and check that the tab appears in the extension settings page.

25.4 Parameters values in menu (X100 only)
  1. Install a new X100 instance (the user cannot click on « Apply » in the extension settings page)
  2. Open the menu with a right click on the icon
  3. Check that the parameters' values are shown

25.5 All parameters in dedicated tab
  1. Create at least one category for the used profile
  2. Add all the parameters in this new category
  3. Apply changes and restart netDesktop
  4. Check that only the newly created category is still present as a tab

Connectivity tests

26.1 No connectivity at startup
  1. Start netDesktop without connectivity to the SOP
  2. Try to login and check that you get an error message
  3. Activate the connectivity to the SOP
  4. Try to login and check that the login works at the first try

26.2 Connectivity after standby
  1. Start netDesktop and log in on a computer capable of standby
  2. Put the computer in standby for 2 minutes
  3. Wake the computer up and check that netDesktop gets the connectivity to the SOP back automatically
  4. Put the computer in standby for at least 6 hours
  5. Wake the computer up and check that netDesktop gets the connectivity to the SOP back automatically

26.3 Connectivity loss
  1. Start netDesktop with a working network connection
  2. Login and check that you can receive chat and calls
  3. Disconnect the network and check that netDesktop shows the red icon in the bottom right
  4. Reconnect the network and check that netDesktop does not show the red icon and is working

Additional specific tests

The following tests list are useful, when you need to retest a new version of a component used by netDesktop

Known Issues and Product Acceptance Results : net.Desktop

Note : for clarity, only the problems are reported in the results. All the passed tests are ignored in this section.

For efficiency reasons, the tests done on each release are only the most important or probably affected by the changes in the release.

net.Desktop 2.26.0

Known Issues

  • Right and left click behaviors are inversed on OSX M4980
  • net.Desktop does not detect duplicate contacts in Exchange public folders M5087
  • Recorded calls cannot be played in net.Destkop on some computers M5684
  • Search with multiple keywords (separated by spaces) does not always give the expected results M5685
  • The call history will only show the received call and not the placed call after a transfer M5688
  • User get a notification (red !) after a voicemail has been moved from inbox to old M5719
  • Some options are greyed out and cannot be edited even if the rights were given to the user M5727
  • Close net.Desktop contact after inactivity of X seconds does not always work M5728
  • External incoming call are not matched to internal directory mobile number starting with "+32" - a solution is to adapt the contact list with "+32" M5753
  • The folder "My Group" contains only the contacts of one identity when multiple identities are used M5795
  • Group pickup on buddy list only works for contacts already in My Group - not for the one added by the end user M5804
  • The net.Desktop that receives the video chat invitation only displays the distant video feed and not the local one M5807
  • An error pop up might appear at the end of a video chat M5811
  • The login window is not big enough in french and german M5794
  • After an hibernation or a reconnection to the SOP, the net.Desktop might fail to resynchronize with the SOP. Some communication window might then need to be closed and then reopen in order to chat. Alternatively a restart of the net.Desktop can be done. M5814
  • When checking the capability of the remote user, we do not check the permissions defined in the X500. We only check if the remote user is a X500 or not. M5815
  • On some computers, net.Desktop GUI will start to have problems when left running for more than 2 days. M5856

net.Desktop 2.26.1

Known Issues

  • Right and left click behaviors are inversed on OSX M4980
  • net.Desktop does not detect duplicate contacts in Exchange public folders M5087
  • Recorded calls cannot be played in net.Destkop on some computers M5684
  • Search with multiple keywords (separated by spaces) does not always give the expected results M5685
  • The call history will only show the received call and not the placed call after a transfer M5688
  • User get a notification (red !) after a voicemail has been moved from inbox to old M5719
  • Some options are greyed out and cannot be edited even if the rights were given to the user M5727
  • Close net.Desktop contact after inactivity of X seconds does not always work M5728
  • External incoming call are not matched to internal directory mobile number starting with "+32" - a solution is to adapt the contact list with "+32" M5753
  • The folder "My Group" contains only the contacts of one identity when multiple identities are used M5795
  • Group pickup on buddy list only works for contacts already in My Group - not for the one added by the end user M5804
  • The login window is not big enough in french and german M5794
  • After an hibernation or a reconnection to the SOP, the net.Desktop might fail to resynchronize with the SOP. Some communication window might then need to be closed and then reopen in order to chat. Alternatively a restart of the net.Desktop can be done. M5814
  • When checking the capability of the remote user, we do not check the permissions defined in the X500. We only check if the remote user is a X500 or not. M5815
  • On some computers, net.Desktop GUI will start to have problems when left running for more than 2 days. M5856

net.Desktop 2.26.2

Known Issues

  • Right and left click behaviors are inversed on OSX M4980
  • net.Desktop does not detect duplicate contacts in Exchange public folders M5087
  • Search with multiple keywords (separated by spaces) does not always give the expected results M5685
  • The call history will only show the received call and not the placed call after a transfer M5688
  • User get a notification (red !) after a voicemail has been moved from inbox to old M5719
  • Some options are greyed out and cannot be edited even if the rights were given to the user M5727
  • Close net.Desktop contact after inactivity of X seconds does not always work M5728
  • The folder "My Group" contains only the contacts of one identity when multiple identities are used M5795
  • Group pickup on buddy list only works for contacts already in My Group - not for the one added by the end user M5804
  • The login window is not big enough in french and german M5794
  • When checking the capability of the remote user, we do not check the permissions defined in the X500. We only check if the remote user is a X500 or not. M5815
  • On some computers, net.Desktop GUI will start to have problems when left running for more than 2 days. M5856
  • Outlook contacts disappear if the Outlook authorisation is cancelled. M6116
  • If you close a video chat using the red camera icon, a pop up appears and say : "Invalid contact information. Resync your contact list might resolve the issue. Please contact your administrator otherwise". M5811

Copyright © Escaux SA