SOLVED Odd incoming situation

[DavidBer]

Let's start with the simple part





First off, thanks for recommending RentPBX! I had hosted my PIAF locally and after the wife constantly complained about the fans in the box I started looking for a hosted solution. One day, about 45 days ago, I was getting weird results. Nothing changed hardware wise (router, piaf, etc.) All of a sudden some calls were coming inbound, and some calls were going straight to voice mail. It was not consistent. A inbound caller from a number could sometimes get through, sometimes not.

After talking to Vitelity, thinking something changed on their end, I felt this was the time to get of my local solution and host it. I have 2 Grandstream IP phones and a Linksys 3102 that connects to a Vtech handset. So I moved over to RentPBX and ***SHAMELESS PLUG*** the cost there is $1.40 per month more than my cost for electricity on the PBX per month! I wanted to see if the problem lied within PIAF. The problem did not. The problem is still somewhere else.

Here is the bullet point issues:

• All outbound calls work fine. This is the same for the 3102 and the Grandstreams.
• All inbound calls are flaky. This is the same for the 3102 and the Grandstreams. Sometimes it will come in, sometimes it will not.
• All DIDS are Vitelity.
• The flaky calls go straight to voicemail, as if it can not reach the device.

At this point, honestly, it does not seem to be a PIAF issue. I am wondering if my ISP (cox) is doing something port wise. Has anyone else seem this scenario and how did you resolve it?

Thanks.

dave

 

[DavidBer]

I may have "possibly" solved this.

One of the grandstreams is only used for testing. It is set to a did that is not used for anything but testing connectivity. Out of boredom, I went to reports->asterisk info in FreePbx. Somehow, someway, all the extensions were showing unreachable. Well, now that makes sense why the extensions could not be reached However, where it gets more interesting is the testing Grandstream did not have a matching authentication password. I set the password correctly, and then all of the extensions were reachable. I am not sure if this is the fix or if I will see the issue again. However, it is very odd that one extension not registering will take down all the extensions.

 

[rentpbx]

It could be the work of Fail2ban. You should check /var/log/asterisk/full. Try to find whether there are any credential error comes from a phone behind your IP.

If that is the case and you have fixed the offending phone, you may have resolved your issue. As long as you do not have rouge phones in the future, you do not have to have fail2ban kicked in.