I’m troubleshooting an issue where my Grandstream ATA reports as registered on my end, but the VoIP.ms portal shows the subaccount as not registered. I started out using the HT502 settings from the wiki.
I’m trying to understand the underlying cause. What conditions would make an ATA believe it’s registered while VoIP.ms shows no registration?
Any insight from others who’ve run into this would be appreciated.
I had previously had a similar issue when I was not using the same server to register and the one my DID POP was set to.
Do both incoming and outgoing calls get through even if you don’t see the green “Registered” in the portal or do you also have call routing issues?
I have the exact same setup running at another location. Same router model, same Grandstream ATA, same firmware, same settings, just on a different VoIP.ms sub-account, and that one stays registered with no issues. Both locations even use the same ISP, which is why this behavior is so confusing.
One thing I tried on the problem setup was enabling a STUN server, and that actually seems to keep both sides registered. I was told STUN is usually not recommended, especially when using TLS, and several people have said it should not work or should not be needed. But I tested it anyway, and it completely stopped the registration drops.
I was just wondering if there is a proper way to fix this without STUN, or if anyone else has run into the same situation and found a better solution. I am mainly trying to understand why the setup works perfectly at one location but not the other when everything is basically identical.