v20 problems

[IgorGorjanc]

We are a system integrator, who deploys IoT devices with VoIP capability. We usually deploy also 3CX as PBX. However, version 20 requires users to set their password via email. This is a dealbreaker for us, as it is not realistic to expect a technician, to set up (a fake) email account for every extension, check email and set password in the provided form. Why can't you simply set an extension number and password like in v18? Why would a VoIP devices (doorbells, SOS phones etc...) need to have their own email address? This creates a ton of completely unnecessary complications (and costs) and is a complete dealbreaker for us (and probably many other system integrators).
What is your proposed solution for this?

 

[JohnS_3CX]

There are no actual users then, just devices.

Why would a VoIP devices (doorbells, SOS phones etc...) need to have their own email address?

They don't. Just make extensions and assign devices. Extension creation does not require an email.

And if you want credentials for custom SIP devices, just get them from here:

 

[SteveITS]

set up (a fake) email account

If you ever do need to set up multiple email accounts, Microsoft and Google both support Plus Addressing ([email protected]).

Ensure "send email notification on missed call" is unchecked when creating the user/extension, and its voicemail is disabled or set to not send a notification.