Troubleshooting Cloud PBX
Fix 2FA sign-in, Click2Call, CRM integration, and microphone volume issues in Cloud PBX.
Find the issue you see in the table below, then open its article for the full fix. Most Cloud PBX issues come from IP access rules, Click2Call setup, or browser settings, so start with the quick checks.
Check these first
Run these checks before you open an article. They solve many sign-in and integration issues.
- Make sure the IP addresses you use are allowed in your PBX's Access Control Lists (ACL): the Web ACL for signing in, and the Click2Call ACL for requests from your Customer Relationship Management (CRM) system. See PBX IP ACL Settings.
- Make sure you set up Click2Call as described in Getting Started With Click2Call. If you recently moved to a new CRM, see How Can I Set Up Click2Call After Switching to a New CRM?.
- Use an up-to-date Chrome browser, and allow it to access your microphone.
Cloud PBX issues
Each article covers one symptom and its fix.
| Issue | What you see | Common causes |
|---|---|---|
| 2FA Login Issues | The 2FA code email does not arrive, or you cannot use Google Authenticator | Code email in spam or moved by a filter, email delays, an incorrect email address, lost access to the authenticator app |
| I Cannot See Click2Call in My CRM | Click2Call does not appear in your CRM | Click2Call setup not completed, the CRM's IP address missing from the Click2Call ACL |
| Integration Challenges With CRM Systems | Errors appear when you connect Cloud PBX to your CRM | API key or endpoint errors, mismatched data fields, missing permissions in either system |
| Microphone Volume Automatically Decreases: WebRTC Issue | Your microphone level drops to 60–80 on its own during browser calls | Chrome automatic volume adjustment, Windows auto-volume features, media key shortcuts, headset controls |
Still need help?
If you work through a VPN, see How Can VPN Affect VoIP Calls?. If none of the articles solve the issue, contact CommPeak Support.
Updated 10 days ago
Did this page help you?