1
00:00:00,142 --> 00:00:03,360
If your SIP account won’t connect, start by checking

2
00:00:03,408 --> 00:00:06,240
what SessionTalk says about its status.

3
00:00:06,821 --> 00:00:10,885
Open the menu, then Settings and Accounts. Select the

4
00:00:10,935 --> 00:00:13,685
account you want to check. Our test account is

5
00:00:13,756 --> 00:00:15,205
disabled at the moment.

6
00:00:15,430 --> 00:00:19,956
Switch on Enabled to try connecting. This account shows

7
00:00:20,030 --> 00:00:21,636
Registration failed.

8
00:00:22,695 --> 00:00:26,359
Save and reopen the account to check the status.

9
00:00:26,487 --> 00:00:30,279
That message tells us the connection didn’t work, but

10
00:00:30,306 --> 00:00:31,839
it doesn’t tell us why.

11
00:00:32,025 --> 00:00:35,161
When you’re not on a call, disable the account

12
00:00:35,241 --> 00:00:38,761
to edit it. Compare the username and domain with

13
00:00:38,793 --> 00:00:42,841
your provider’s details. Only enter a new password if

14
00:00:42,894 --> 00:00:44,081
it needs changing.

15
00:00:44,287 --> 00:00:49,674
Under Advanced SIP settings, open SIP identity. Check whether

16
00:00:49,706 --> 00:00:53,434
your provider needs a separate authentication username or a

17
00:00:53,514 --> 00:00:54,554
SIP proxy.

18
00:00:55,097 --> 00:00:59,609
Then open Registration and check the transport. Our example

19
00:00:59,705 --> 00:01:03,849
uses UDP, but use whatever your provider has specified.

20
00:01:04,134 --> 00:01:07,387
We’ll leave this test account disabled while its details

21
00:01:07,426 --> 00:01:11,387
are checked. After making corrections, save and enable your

22
00:01:11,456 --> 00:01:15,306
account, then try again. If it still fails, the

23
00:01:15,346 --> 00:01:18,107
logging tutorial shows you how to collect a SIP

24
00:01:18,206 --> 00:01:19,466
log for support.