FreePBX won't connect to softphone

FreePBX
1

FreePBX 13.0.190.19
CentOS

I have a hosted PBX with Vitelity and have configured routes and trunks. The dashboard shows that 2 trunks are online and occasionally that there are active calls. The calls are forwarded to my cell since the PBX isn’t working. I have downloaded X-Lite and Yate Client to test the phones but neither one will connect to the PBX. Yate just continuously says, “connecting” and nothing happens. If I try to make a call it just hangs up immediately. I have white listed my office and home IP addresses and experience the same issue, in my mind ruling out a network config issue?

I am somewhat at a loss here and need some help or guidance. I am new to FreePBX but had previously setup an incrediblePBX on a cloud at cost server, unfortunately the server proved to be too unreliable. I hope I have given enough information; if I have not, please let me know what you need and i’ll get it for you.

2

A few more details would help. What kind of extension did you setup? (sip? pjsip? …) how did you configure the soft phones. What ports are they connecting on? Any output on the asterisk console

asterisk -rvvvvvvvvv

? Have you verified network connectivity between the server and the machine you are running the soft phone on?

3

It is a SIP extension. The softphones are configured to connect to the Static IP of the PBX with the extension number in the username field and the secret from FreePBX as the password. They are connecting on 5060.

Provider: none
Protocol: sip
Username: Extension Number from PBX
Password: Secret from PBX
Server: Static IP Address

I’m sorry I don’t know how to check the asterisk console… I don’t know what command to put in the Asterisk CLI, please advise…

I am connecting to the server for config from the computer I am running the soft phone which should verify connectivity.

Thanks for your help. - Harrison

4

By sip, you are saying chan_sip? If so, you are on the wrong port. I believe freepbx sets chan_sips port to 5160. pjsip is on 5060.

5

I do mean CHAN_SIP. I used port 5060 because on the FreePBX Extension Menu it says “This device uses CHAN_SIP technology listening on Port 5060 (UDP)”

I changed it to 5160 but it still won’t connect. No change in behavior. There are advanced settings in the soft phone of:

Domain: Blank
Outbound Proxy: Blank
Registration Interval: Blank
Authentication Username: Blank
Transport: UDP

6

How about connectivity being verified? Can you ping from the machine with the soft phone and get a response from the server? Is there anything showing a connection attempt in /var/log/asterisk/full?

What are the IPs for the server and your phone? Are they the same network? Is the freepbx firewall on or off?

7

The IP of the server is 207.166.132.131
The IP of the soft phone is 68.99.77.228
They are not on the same network. The freepbx firewall is enabled.

Here is what the log files say:
[2017-03-03 08:05:52] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:52] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:52] VERBOSE[1350] asterisk.c: – Remote UNIX connection
[2017-03-03 08:05:52] VERBOSE[15301] asterisk.c: – Remote UNIX connection disconnected
[2017-03-03 08:05:52] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:52] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:52] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:52] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:53] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:53] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:53] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:53] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:53] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:53] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:53] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:53] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:53] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:53] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:53] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:54] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:54] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:54] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:54] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:54] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:54] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:54] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:54] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:54] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:55] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:55] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:55] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:55] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:55] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:55] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:55] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:55] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:55] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:56] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:56] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:56] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:56] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:56] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:56] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:56] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:56] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:56] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:56] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password
[2017-03-03 08:05:56] NOTICE[1375] chan_sip.c: Registration from ‘“100” sip:[email protected]’ failed for ‘51.15.137.109:5766’ - Wrong password

I don’t understand what the 51.15.137.109:5766 IP is???

8

Also, I am able to access the server via SSH with Putty from my computer (the computer that the soft phone is installed on)

9

Looks like connectivity is not the problem. Also looks like using 5160 and chan_sip is OK. This tells me that the login for extension 100 (the username you entered into your soft phone) is not matching. On the softphone, you need username 100 and whatever the password is. If you did not cut and paste, entering all the digits it gives you by default is error prone (I’m dyslexic, so in my case, entering all of those is almost impossible :slight_smile: )

10

Hi!

Someone from France trying to abuse your server… :worried:

51.15.137.109 is the IP, 5766 is the port it is coming from on their side…

Is this a static IP address?

Are there any plans to have other IP addresses access your PBX?

Good luck and have a nice day!

Nick

11

Hi!

That IP is currently listed here:

http://www.networksystemssolutions.eu/voipblocklist.php

for trying to hack into other VoIP systems… :scream:

Good luck and have a nice day!

Nick

12

Good point. I did not look closely at the IP, just the fact that there was a connection and that ssh was working. So there is no evidence that you soft phone is even trying.

13

Hi!

I wonder if his ISP might be blocking it…

Have a nice day!

Nick

14

It is a static IP. That’s why I am so confused. The soft phone says “connecting” but I can’t verify that it is making contact with the server. I have tried with multiple soft phones from multiple (whitelisted) IP addresses.

If I can connect to the server with SSH, wouldn’t that mean that the ISP isn’t blocking it? Or could it be port specific? Like Port 22 or whatever for SSH is open but 5060/5061/5160 are blocked by the ISP? I wanted to try everything before I call them, it’s usually a nightmare to get support. Thanks for all the input, everyone.

I guess I should do something about the French Invasion…

15

Hi!

Since your IP is static if it is the only IP which should be communicating with that PBX block everything else…

No need to leave a port open to the world if it’s not needed…

Good luck and have a nice day!

Nick

16

I’d say your first effort should be to lock down your PBX. The brute force attacks, however lame, will fill your logs in no time.

You might also try the extension number for the Authentication Username.