Additional notes, we also have 10 Polycom SoundPoint IP 331 which are now also in the 10.0.7.XXX range and have no problem connecting with FreePBX.
The real problem is that when a phone restarts from factory default, it will not auto discover the Digium Phones configuration server, nor will it connect to it if we input the info manually.
I’ve tried everything and at this point I don’t know what to do.
So all the digium phones started acting up one after the other so I had to delete all the DHCP reservations and all is back to normal.
Now this is not a DHCP reservation issue, simply because we also have POLYCOM IP331 phones for which I did the exact same thing (get their mac address and make a DCHP reservation) and they kept working until their initial lease expired, then got their new IP in the 10.0.7.XXX range and didn’t even stop working in between.
So I think I can safely assess that this is a problem with DPMA.
Once the phones get DHCP reservation, they do not see the configuration server.
Or sometimes, after hitting refresh several times, they will see it, but connecting to the server will time out.
So I think I can safely assess that this is a problem with DPMA.
Really?
Is that because you saw MESSAGE packets received by Asterisk?
Were response packets not going out?
Were response packets going out to the wrong address?
If you didn’t see MESSAGE packets received by Asterisk, did you see the phone sending them to what would have been the proper address?
Now I’ve tried a LOT of different things and the error was nor in my network, nor in DPMA
The problem came from fail2ban on the FreePBX server.
It appears that if you change the IP of a server that’s already registered with DPMA, when the lease expires and it’s getting it’s new IP, the new IP will get banned.
I know this is an old thread but I had the same problem with Astra and Vertical phones. The issue was the TFTP server was not set to the PBX box in pfSense. Adding that in to the pfSense DHCP server setting and applying the changes seemed to fix things. It is weird it only happened to some of the phones and only some of the times since the pfSense has been in place for over 3 years like this.