3CX client does not log out under any circumstance

[namth2]

A predecessor tell me that 3CX client on her iPhone Xr has been able to make and receive calls on behalf of the current holder. The information is easily verified right after that notification. I have tried generating new passwords for the reported extention without any luck. Then a 3CX partner asked me to delete and re-create the extension to clear PBX cache. It was also useless.

Is there any way that I (any my company, of course) stop leaving people from continuously make use of the PBX?

 

[JohnS_3CX]

If you completely delete the extension and recreate it, then any phones that had that extension should no longer be able to use it.

What version is your PBX currently?

 

[namth2]

My delete and re-create procedure is:

1. Log in to 3CX admin console
2. Navigate to Extensions page
3. Select the extension (381)
4. Export the extension configuration to a csv file to lately import
5. With the selection, click Delete (X button on the right of the selection row)
6. Find 381 again to make sure that it does not exist any longer
7. Import the configuration file saved previously to re-create the extension again.

A red icon displayed next to teh re-created extension which indicated that it was not provisioned by any device (does my assumption correct?). Then I informed the lady to check if she was able to make/receive any call on behalf of the destined user. My surprise was that her phone was successfully provisioned and still able to make a call to my phone number. The destined user has not had his phone provisioned until now.

My PBX version is 16.0.5.619.

Thank you!

 

[JohnS_3CX]

So you mean you were re-importing the extension then rather than creating it from scratch?

Please create a fresh extension and confirm that the previous user can no longer make calls.

And if you want an extension template so the settings aren't lost, use the "copy extension" button whenever you want to create a fresh user which allows you to copy the following

 

[namth2]

So you mean you were re-importing the extension then rather than creating it from scratch?

Please create a fresh extension and confirm that the previous user can no longer make calls.

And if you want an extension template so the settings aren't lost, use the "copy extension" button whenever you want to create a fresh user which allows you to copy the following
View attachment 17447

I assume that by deleting an extension from the extensions management page it will no longer exist from that moment. Manually create a new extension and adjust/modify some options should be definitely equivalent to importing a pre-set configuration file. Let's say that if I modify the exported csv file by replacing the extension with another number or even adding more lines in case that I want to add more extensions in batch mode, the importing function will do exactly the same as if the/these extensions are iteratively manually added?

 

[JohnS_3CX]

> I assume that by deleting an extension from the extensions management page it will no longer exist from that moment.

This part is correct - however if you exported it and reimported it, a mobile app will re-register and continue to work as before (because the passwords still match). There are a few other things that are not "visible to the naked eye" like unique internal IDs generated for each extension, and unique provisioning URLs for each extension (for the apps - not deskphones!) and this is why deletion is important to ensure that these become invalid as soon as an employee leaves. The CSV does not include/control those.

>Let's say that if I modify the exported csv file by replacing the extension with another number or even >adding more lines in case that I want to add more extensions in batch mode, the importing function will >do exactly the same as if the/these extensions are iteratively manually added?

If it changed significantly, yes. But it's easy to make errors this way. If you inspect the exported CSV you will see that it contains a number of various fields that if left the same, an already provisioned client will continue to work. But adding batch extensions is not the same concept as deleting and re-creating extensions of employees who left (two separate subjects not to be conflated). Adding batch is more useful if you will import a number of deskphone MACs, for everything else we recommend you use the copy extension function in the interest of auto-generating secure passwords for the original case we discussed.

If you still choose to bulk import (when it makes sense to do so) make sure you have deleted the old extensions first, and most importantly also use the "Regenerate" button to get new secure passwords as soon as you re-import.

Note: If you restore a backup that contains old extensions now deleted, you will ofcourse revert to a previous state - so keep that in mind too and create fresh backups whenever you make changes.

 

[namth2]

Thank god! Following your clear and detailed explanation and instructions, I have successfully deregistered the unwanted client. I wonder in case that such extension has been registered by an IP Phone located in a department and a softphone installed on an employee's personal mobile phone, what is the best way to deal with a HR change?

 

[JohnS_3CX]

You delete the extension, and reset their deskphone.

Then create a new extension, assign the deskphone automatically via your Phones tab (for easy PnP provisioning) and the new employee receives their welcome email with the fresh details and QR codes.

It should take you a couple of minutes once the deskphone has been reset, and the next employ has a ready to use extension and phone.

Optionally: Leave the brand new extension with no name and email if the new person has not arrived, but provision the phone so it's ready for use. You have the option to "Disable Extension" so nobody can use the deskphone. When the new person arrives, edit the extension accordingly, enable it, and send a reprovision command to the registered deskphone to receive the new name and surname.