Video Tutorials

Check why your SIP account will not register

M20 · Mobile · 1 minute 20 seconds

Steps

Open Menu > Settings > Accounts and select the account.
Check Enabled and Registration status.
When you are not on a call, disable the account before editing its details.
Compare the username and domain with the details supplied by your provider. Update the password only when needed.
In Advanced SIP settings > SIP identity, check any required authentication username or SIP proxy.
In Registration, check the transport against your provider instructions.
After correcting the settings, save, enable the account and check its status again.
If it still fails, collect and share a SIP log.

This example shows an actual registration failure and leaves the test account disabled for investigation. It does not demonstrate a successful connection or establish the cause of the failure. Passwords are not displayed.

Transcript

If your SIP account won’t connect, start by checking what SessionTalk says about its status.

Open the menu, then Settings and Accounts. Select the account you want to check. Our test account is disabled at the moment.

Switch on Enabled to try connecting. This account shows Registration failed.

Save and reopen the account to check the status. That message tells us the connection didn’t work, but it doesn’t tell us why.

When you’re not on a call, disable the account to edit it. Compare the username and domain with your provider’s details. Only enter a new password if it needs changing.

Under Advanced SIP settings, open SIP identity. Check whether your provider needs a separate authentication username or a SIP proxy.

Then open Registration and check the transport. Our example uses UDP, but use whatever your provider has specified.

We’ll leave this test account disabled while its details are checked. After making corrections, save and enable your account, then try again. If it still fails, the logging tutorial shows you how to collect a SIP log for support.

Back to the mobile tutorial series.