- Joined
- Jan 18, 2011
- Messages
- 159
- Reaction score
- 45
Hi, a small fun question, I just want to make sure I am not missing something. I have a client who has an ISP service to their office which is not static IP, it is dynamic public IP. In reality the IP changes infrequently, but ISP reserves right to change it whenever they wish.
Right now I've got 3cx running on an openstack instance in Montreal (Cloud hosting provider) and it works great. I've added a 'whitelist' so that the current office IP address is not going to blacklist. Unless the IP changes. And then... I need to re-do this.
The office has a DynDNS FQDN that is always correct (firewall does DynDNS updates so they are ~always current, despite being infrequent). So it basically behaves like a static / unchanging FQDN. Just the IP changes a few times maybe per year.
The reason I ask. One of the users in the office today, pounded on login to their extension for voice mail access and had their pass wrong, and triggered blacklisting of the office IP address, which I believe means that temporarily the phone system was effectively busted for everyone in the office, because one user decided to re-re-retry the failed pass login. Bit frustrating.
I'm OK for short term with the new added whitelist based on present IP numerical address. But in a perfect world if the whitelist config supported an FQDN instead of a numerical IP it would be really really nice.
Figured I would ask in case anyone knows of a workaround for this, or if this is one that I may need to request could get put into the ideas/forum request thread. (ie, not by me, I am not sufficiently awesome in forums yet to do that
Thanks,
Tim
Right now I've got 3cx running on an openstack instance in Montreal (Cloud hosting provider) and it works great. I've added a 'whitelist' so that the current office IP address is not going to blacklist. Unless the IP changes. And then... I need to re-do this.
The office has a DynDNS FQDN that is always correct (firewall does DynDNS updates so they are ~always current, despite being infrequent). So it basically behaves like a static / unchanging FQDN. Just the IP changes a few times maybe per year.
The reason I ask. One of the users in the office today, pounded on login to their extension for voice mail access and had their pass wrong, and triggered blacklisting of the office IP address, which I believe means that temporarily the phone system was effectively busted for everyone in the office, because one user decided to re-re-retry the failed pass login. Bit frustrating.
I'm OK for short term with the new added whitelist based on present IP numerical address. But in a perfect world if the whitelist config supported an FQDN instead of a numerical IP it would be really really nice.
Figured I would ask in case anyone knows of a workaround for this, or if this is one that I may need to request could get put into the ideas/forum request thread. (ie, not by me, I am not sufficiently awesome in forums yet to do that
Thanks,
Tim