Skip to content

Set Up Sangoma Connect

Sangoma Connect is a softphone app (iOS/Android/Desktop) that pairs with UnifiedBX for voice calls, SMS, voicemail, presence, and chat. Provisioning is mostly automatic — generate an activation link, user clicks it, app configures itself.

Before You Start

  • The Sangoma Connect module is installed (commercial — license check at System Admin → Activation).
  • The user has a User Management entry with a default extension (see Configure User Management).
  • The user's email is set in their User Management record.
  • UnifiedBX has a public FQDN with a valid SSL cert (Connect requires HTTPS).
  • SMTP relay is working (for sending the activation email).

Steps

  1. Go to User Attributes → Sangoma Connect.
  2. The page lists User Management users; pick the one to provision.
  3. Click + Add User to Sangoma Connect (or the activation button).
  4. Configure (per user):
    • Default Device — usually the user's primary extension.
    • Mobile Device — Yes if they'll use the mobile app.
    • Desktop Device — Yes if they'll use desktop.
    • Permissions — what features (chat, video, SMS) the user gets.
  5. Click Send Welcome Email — Connect sends an activation email with a one-time link.
  6. User clicks the link on their device(s); the app installs (if needed) and auto-configures.

After Activation

The user's Sangoma Connect app:

  • Registers as a SIP endpoint on their default extension.
  • Receives push notifications for incoming calls.
  • Can chat with other Sangoma Connect users on the same UnifiedBX.
  • Sees voicemail notifications.

Verify

asterisk -rx "pjsip show endpoint 1001"

A new contact should appear (Connect mobile or desktop). Place a test call.

Common Issues

  • Activation link doesn't arrive. Email failing — check System Admin → Sysadmin → Email Setup, send a test email, fix SMTP first.
  • App won't activate. UnifiedBX FQDN unreachable from the user's device, or SSL cert is self-signed (Connect requires trusted cert). Use Let's Encrypt.
  • Call rings on phone but Connect doesn't ring. Push notifications need outbound HTTPS to Sangoma's notification servers. Check firewall.
  • Battery drain on iOS. Background SIP registration is expensive; Connect uses pushkit by default — confirm push is configured.
  • License expired. Connect users get warning banners. Renew at Sangoma portal.
  • User has multiple extensions. Only one is "default" for Connect; secondary needs separate provisioning.