After last weeks security issue we changed the admin port on our deployments to a custom port and only trusted IPs can access it. However, Sangoma mobile apps can no longer register. I tried changing the mobile app registration address to the FQDN:custom port, restarted sangoma talk and sangomartapi, ran the cloudconnect agent action update and re-ran the domain action. Tried with firewall down. No effect.
I reviewed the port documentation (https://sangomakb.atlassian.net/wiki/spaces/PP/pages/14057601/PBX+Platforms+-+Ports+used+on+your+PBX) and it indicates the ports used for mobile are the same as physical SIP phones. However, changing the admin GUI port definitely breaks Sangoma Talk mobile registration.
How are you guys securing your admin port while keeping Sangoma Talk Mobile functional?