I’m running FreePBX and a Grandstream HT802. It registers to FreePBX fine and have had no issues.

I’ve gone through the process of moving my desk phones to a different VLAN (20, from VLAN 1), which has a different IP subnet. So now the phones have a different IP and they successfully connect to FreePBX, which has a separate interface on that VLAN. So far, so good.

The problem is when I moved the HT802 to the new VLAN and IP. I won’t connect to FreePBX. The Asterisk log shows nothing (as in, no attempts or registration errors), and Fail2Ban has no blacklisted IPs. I even whitelisted the IP for the Grandstream ATA to no avail.

Here’s a brief of how the network configuration looks:

VLAN 1

FreePBX IP: 192.168.1.10

HT802 IP: 192.168.1.3

Status: Successfully registers

​

VLAN 20

FreePBX IP: 10.10.20.10

HT802 IP: 10.10.20.3

Status: ATA says “NOT REGISTERED”. FreePBX doesn’t log any failed attempts, that I could find.

​

The steps I performed on the ATA is to update the IP for the FreePBX server, click apply, then click update, then reboot. Just as I click REBOOT, I change the VLAN assignment on my Cisco managed switch to VLAN 20. It boots up to its new IP, but never registers.

I’ve tried setting the ATA to use DHCP, I’ve also set it to use Static IP… no change.

I change the IP for the FreePBX server to register to, to point back to the 192 address on VLAN 1, click apply, then update, then reboot. Immediately put it back on VLAN 1, and then it registers.

I’ve also done a FWCONSOLE RESTART on FreePBX each time I’ve moved the ATA to a different VLAN, to no avail. It simply won’t register.

I really don’t understand why the Grandstream device won’t register. Oh, and it’s also running the latest firmware (I did upgrade the firmware, but didn’t change anything).

Anyone ever come across this before?

  • panjadotme@alien.topBEnglish
    1·
    11 months ago

    Agree with other person. This sounds like firewall issue. You need to allow traffic between VLANs.

  • Sarith2312@alien.topBEnglish
    1·
    11 months ago

    You should be able to pull syslogs off the HT802 and see what it’s trying to connect to on boot. If it ends up not being a network or firewall issue then you can always put a ticket in with logs to Grandstreams support. They respond pretty quick usually once every 24 hours and seem to be active during European daytime hours

  • 1BadDawg@alien.topOPBEnglish
    1·
    11 months ago

    SOLVED!

    Thanks to u/Classic-Walk-1171, who replied to my post in r/freepbx, the issue was DNS.

    The DHCP server was assigning it to a remote DNS, but the firewall is set to block all outbound traffic. Setting the DNS to point to the gateway fixed the issue. Don’t know why, but apparently it’s what the Grandstream device needed.

    To answer other’s comments about the firewall, the ATA and phones are communicating to a FreePBX server all on the same VLAN. No firewall rules are needed. And yes, I could ping it (forgot to mention that earlier).

    Anyway, even when it’s not DNS… it’s always DNS. :-)