I’ve been trying to get my Grandstream HT802V2 working with my Xfinity Rogers WiFi router for the last 3 days without success. I’ve followed every thread I can find and tried all the suggestions. I had no trouble with an Ooma VoIP device and the Rogers router that I’ve been using for several years. The Grandstream was recommended to me by voip.ms. FXS 1 port is registered; SIP port changes don’t seem to make a difference. No calls come in, and everything going out is a busy signal, including the echo test 4443. Rogers tells me that they know people are successfully using the Grandstream ATA with their routers, but they can’t help me with any setup. If anyone has the Rogers Xfinity WiFi router working with the Grandstream HT802V2 please let me know what the magic is. Grandstream tech support suggested I update the firmware on the ATA, which I did, with no different results. Thanks for any help in advance.
In recent HT802V2 firmware, the default setting for SYSTEM SETTINGS > SECURITY SETTINGS > CLIENT CERTIFICATE > SIP TLS > ENABLE/DISABLE WEAK CIPHER SUITES was changed from the first option (the least strict) to the last option (the most strict). Moving it back to the first option solved a similar problem for me.
If SIP/ALG is the culprit (either in your router or on the Rogers network), then switching your VOIP.MS subaccount to ENCRYPTED and enabling TLS in the HT802V2 might fix things.
Here’s the list that I use for basic setup of an HT802V2 at VOIP.MS:
=======================================
Before starting, on the VOIP.MS website, set the subaccount to Yes for ENCRYPTED SIP TRAFFIC.
A. SYSTEM SETTINGS > SECURITY SETTINGS > CLIENT CERTIF. > SIP TLS:
••• ENABLE/DISABLE WEAK CIPHER SUITES: Enable Weak TLS Cipher Suites
Of the 14 options, any of the first 11 will work. (This change is necessary because in about 2025, Grandstream changed the default to Disable All Of The Above Weak TLS Ciphers Suites, which blocks TLS for VOIP.MS.)
••• At the bottom of the page, click SAVE AND APPLY.
Make the remaining settings for each FXS port.
B. PORT SETTINGS > FXS PORT > GENERAL SETTINGS:
••• PRIMARY SIP SERVER: gothamcity.voip.ms [for example]
••• OUTBOUND PROXY: [same as entered above for PRIMARY SIP SERVER]
••• SIP USER ID: [subaccount name]
••• SIP AUTHENTICATE ID: [subaccount name] Ù
••• SIP AUTHENTICATION PASSWORD: [subaccount password]
••• NAT TRAVERSAL: Keep-Alive
••• At the bottom of the page, click SAVE AND APPLY.
C. PORT SETTINGS > FXS PORT > SIP SETTINGS:
••• SIP TRANSPORT: TLS
••• REGISTER EXPIRATION: 2
••• ENABLE SIP OPTIONS/NOTIFY KEEP ALIVE: OPTIONS
••• SIP OPTIONS/NOTIFY KEEP ALIVE INTERVAL: 20
••• At the bottom of the page, click SAVE AND APPLY.
D. PORT SETTINGS > FXS PORT > CODEC SETTINGS:
••• VOCODER SETTINGS (IN LISTED ORDER): set all to PCMU
••• SRTP MODE: Enabled and forced
••• SRTP KEY LENGTH: AES 128&256 bit
••• At the bottom of the page, click SAVE AND APPLY.
E. PORT SETTINGS > FXS PORT > CALL SETTINGS:
••• DIAL PLAN: { 1[2-9]xx[2-9]xxxxxx }
••• At the bottom of the page, click SAVE AND APPLY.
F. PORT SETTINGS > FXS PORT > ADVANCED SETTINGS:
••• VALIDATE INCOMING SIP MESSAGE: check the box
••• CHECK SIP USER ID FOR INCOMING INVITE: check the box
••• ALLOW INCOMING SIP MESSAGES FROM SIP PROXY ONLY: check the box
••• At the bottom of the page, click SAVE AND APPLY.
G. After making changes, reboot the Grandstream.
Thank you for taking the time to post that information. I’ve changed the items according to your post. Most of what you show, I did have, but there were a couple of items different. I still get the busy signal on echo test and outbound calls, but I am going to stay with these settings and not continue to make multiple changes based on every suggestion I come across. If, for some reason, I have a setting incorrect, the config.txt and the cinfig.xml configuration files should help me identify it. I’ve exported the data from these files and will review them.
I forgot to say that prior to trying my recommended list of settings (above), the device should be set to factory defaults. My list assumes that to be the case. Otherwise, some lingering setting on an item that’s not on my list could be obstructing calls.
That’s good to know. I’ll try this again with your recommendation.