A cool feature we had on our wish list for a long time will be in our next version 60 build: Login with your Google account.
Google has done a lot to make the login convenient and secure, providing two-factor authentication and email notifications as part of Google G Suite service. There is nothing the end user needs to do to make this work.
The email address in the user account must match the email account in the Google account; if a user has multiple email addresses, one match will be sufficient. It makes no difference if it’s a free Gmail account or a paid Google business account.
The domain for this feature must be set up on the Google side: for this you have to log in to the Google API site and create credentials for the domain. It isn’t possible to use wildcard domain names, so every domain name that can be used for the login must be listed; if you are using a secure connection you should only enter the https address; if you are using multiple domain names, they must be listed separately. There is a wizard at https://developers.google.com/identity/sign-in/web/sign-in you can use to set this up:
After picking a name for your login, you need complete some minimal configuration. The PBX uses "Web browser" as configuration; the URL must match the URL that you use for logging in:
The final screen shows you the Client ID you need to copy into the PBX web interface. A typical client ID has the form xxxxxxxxxxxx-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx.apps.googleusercontent.com.
Copy the Client ID into the domain settings, "Google sign in client ID." Hit the save button.
The next time someone visits the login page, there will be a small login field under the login submit button to trigger the login process; right now this service is only available for user accounts.
System and domain administrators still need to use their username and password credentials as before. Fortunately, most browsers today support storing those credentials, so repeated logins shouldn’t be too inconvenient.
This will be generally available for 60.2 builds. We have already included it in some 60.1 test builds.
Cove Central teams up with QuestBlue and Vodia to revolutionize communication solutions for MSPs nationwide. This elite turnkey partnership simplifies FCC compliance, integrates global cloud capabilities, and redefines industry standards. With Cove Central's TAPP, MSPs gain white-glove support and 24x7 service, setting a new standard in unified communications.
Remote work, fueled by cloud computing, is changing how we connect beyond traditional offices. Telephones remain vital, demanding solutions beyond basic call forwarding. Emulating extensions, with call control functions, becomes essential for effective remote communication. Options like home IP phones and softphones blur the line between office and remote work. The emphasis is on replicating a seamless phone experience in the era of flexible work arrangements.
Addressing a challenge with LDAP, VoIP phones lack the ability to write new contacts to the address book. For users of snom phones, a solution involves utilizing the snom button mode, specifically the "keyevent" mode with the F_ADR_BOOK parameter. This configuration enables users to add phone numbers directly from the phone keyboard, bypassing the need for PBX login and web interface use. This versatile approach can also be applied to other functions and is similarly available for Grandstream, HTek, and Yealink phones.