If you have a backup of the PBX, you can open the XML file within it and check who the system owner is and which email address is linked to them.Thanks. Historically we've always logged into this PBX using the System Owner extension number and password rather than an email address.
Unfortunately, we've now lost access and don't know which email address is assigned to the System Owner extension. I suspected it might be the same as the subscription contact, but password reset emails are not received for that address.
As I no longer have access to the PBX, I'm unable to verify which email address is actually configured for the System Owner extension.
Is there an alternative recovery method for a partner who owns the licence, or another way to identify the System Owner email?
When you integrate with a system using M365, the email server can switch to using the M365 account you use for integration (the M365 global admin account). The choice is presented to you during integration, and you can use the M365 mail option to send mail from 3cx.Thanks everyone.
I've done some more investigation and found something that may be relevant.
We recently configured scheduled backups for several customer PBXs to our SharePoint. On every PBX where this was done, the Email Server setting changed from the built-in 3CX service to Microsoft 365. This wasn't an intentional change on our part. The only configuration change made was enabling the SharePoint backup destination.
The Email Server was automatically populated with the same Microsoft 365 Global Administrator account that had been used to authorise the SharePoint backup. That account was not licensed for Exchange Online.
Reverting those PBXs back to the built-in 3CX SMTP service immediately restored normal email notifications on the affected systems.
Interestingly, it didn't affect every instance in the same way. Some PBXs continued sending notifications despite being configured for Microsoft 365, including this instance, which is still successfully sending missed call notifications even though we're currently unable to access the Management Console. Other PBXs, however, stopped sending notifications altogether.
Has anyone from 3CX seen this behaviour before, or is configuring SharePoint backups expected to switch the Email Server from 3CX to Microsoft 365?
Founded in 2005, when VoIP was an emerging technology, 3CX has gone on to establish itself as a global leader in business communications.