After upgrading to FreePBX17 we are having some major issues with hotdesking. We are using the Sangoma P330 phones. All phones are listed under the emergency hot desking.
This is how it looks after logging out but there is an issue on the phone
I’m not sure if it eventually corrects itself - I am going to leave it now to see… What I have done is added and removed the extension in EPM 2 dozen times and changed between templates and finally it worked - but it may have just been a time issue.
If we don’t logout and factory reset the phone - it gets the config right away without any issue. The issue only happens when hotdesking.
Is this a known issue when upgrading to FreePBX 17 - anything I can check to resolve this.
It looks like two different things are happening. The issue with logging out is still an issue so if anyone can offer any assistance on this that would be great. This was not an issue on our FreePBX16 - it has only become an issue after upgrading to FreePBX17.
The issue with it getting stuck at the fetching config and looping has been found - it was the intrusion detection part blocking the endpoints. I’m not sure why as this never happened on our FreePBX16 build, and all the networks are listed under trusted. I’ve also manually added them in the CLI under the fail2ban config.
After disabling the that part of the config and setting the endpoint manager extension mapping back to “server” it logs back in right away. I do still have to use “fwconsole epm remove” to remove the mapping left after the fail logout.
For now we will not have our users use the hotdesking feature but hopefully if this has happened to us other users have experience on how to resolve it! If anyone has any information as to why our endpoints now get blocked by the fail2ban so I can reenable it that would also be great. If not - we are only allowing our trunk provider to send SIP messages through our firewall so not a major concern.
Thank for your being willing to take a look at this. I suspect it is something during the upgrade process that has broken rather than being an issue on a fresh install. Looking forward to getting it resolved either way!
I’ve went to create a support ticket but am seeing the message “Your new sangoma.com user registration has been flagged for review. Please allow 1 business day while we validate and activate your account.” I saw this many years ago as well so I’m not sure it was ever reviewed.. I’ve contacted the support link provided on that page in hopes it can be addressed to allow me to create a ticket. Once resolved I’ll DM you the support ticket number as requested.
Anyway we can look at this without making a support ticket? I’m hoping they’ll end up resolving it tomorrow but support keeps following up with me but seems unable to resolve the issue so far with our account.
As it impacts our Sangoma hardware phones I’m hoping someone can jump on and resolve this
@kgupta forgive me I am not sure how to DM you on here… I was able to access my support account at support.sangoma.com so I have made a ticket using that platform. help.sangoma.com is throwing the error for my account and that support team is looking into why.
The ticket I created is #1227340
Aside from this issue the system has been working but we would like to be able to hotdesk again.
