V20 upgrade - issue with one user extension

[hlfb]

Hi all,

I upgraded to v20 last nigt, all appeared to be well, however one user this morning was not working, and although signing in with her credentials ok, did not appear in the extension list as signed in, or to any of the queues. I did notice another extension number was though, so I set this one up with hr details and added it to the queues and that is working, although to the user its still showing like she is signed in with her actual extension.

I guess a restart of the system might be the next step, but thought I would ask if anyone had seen this before or could advise?

Also, I have noticed the M365 integration option is there and looks like it is connected, but the SSO button is not on the login when the user goes to sign in, why is this? I have reactivated the integration, I would like all users to be paired with SSO and their M365 ID.

Thanks

 

[Alphabetic]

Are they using web client / softphone? they need to make sure they enable all permissions.

https://www.3cx.com/community/threa...showing-as-not-registered.124599/#post-586860

As for 365 SSO - You need to to go to admin > users and press 365 at the top and enable "Sync..." and SSO.

 

[hlfb]

so I have noticed this extension has linked itself to the back door phone - i have named it Jade 2 (exten 104) but Jade is 107 and when we sign in as 107 it logs in as 104

 

[Alphabetic]

Is this when you sign in with 365? Make sure your email addresses are unique per extension.

 

[hlfb]

Ive given all extensions unique email addresses, but 104 has lost its details for some reason and is linked to extension 107 - this is a web client user typically.

I will update the permissions, but maybe reboot SBC afterwards?

 

[Alphabetic]

Could be that 104 and 107 are syncing back to 365?

try turning off the sync, restart the PBX and turn it back on.

 

[hlfb]

M365 sync is turned off, I can only reconfigure the integration. I think a PBX reboot is needed, I will try at lunchtime and see how it goes

 

[hlfb]

the permissions solved logging in as 107 - still 104 has lost all its details for some reason, will reboot and see what happens today