ANVEO VOIP not working after upgrade router from AC66 to AC3100
Taoman:
Whether using UDP or TCP as your transport protocol the proxy server port must be 5010.
http://www.anveo.com/faq.asp?code=sip_obi110
Webslinger:
Quote from: Taoman on July 17, 2017, 09:12:24 am
Whether using UDP or TCP as your transport protocol the proxy server port must be 5010.
http://www.anveo.com/faq.asp?code=sip_obi110
Thanks, that other dslr screenshot was confusing me.
simsin:
Quote from: Webslinger on July 17, 2017, 08:52:08 am
Quote from: Taoman on July 17, 2017, 08:15:56 am
My suggestion is to carefully follow Webslinger's directions exactly as written.
This may be completely unrelated, but I was just looking at this error again:
"Register Failed: No Response From Server (server=67.212.84.21:5010; retrying)"
Okay, so that's the Canadian Anveo SIP server.
Isn't 5010 for TCP? And isn't TCP only a premium subscription option with Anveo?
I'm wondering if UDP for Proxyservertransport and 5060 for Proxyserverport shouldn't be used instead?
You folks would know better than I do because I'm not on a special paid plan with Anveo.
http://www.anveo.com/service.asp
Look under SIP TCP.
I don't know if simsin is on a paid plan.
Presumably if the only thing that changed is the router, then what I'm asking here doesn't matter.
Webslinger!! You gave me advice when i was deciding on switching from POTS on RFD!
Thanks for taking the time to help.
I'll try to add as much details as possible about my setup.
I have Bell FTTH setup.
The Bell ONT is connected directly into my ASUS router (using VLAN tagging) so I eliminated the modem.
So my setup is BELL ONT ---> ROUTER ---> ATA
I have the "CANADA UNLIMITED" plan from anveo:
http://www.anveo.com/anveoforobitalk.asp
I'm going to try all the steps you gave me tonight and report back.
Webslinger:
Quote from: simsin on July 17, 2017, 11:29:18 am
Webslinger!! You gave me advice when i was deciding on switching from POTS on RFD!
There's all kinds of Webslingers out there. ;)
Quote
Thanks for taking the time to help.
No problem
Quote
I have Bell FTTH setup.
The Bell ONT is connected directly into my ASUS router (using VLAN tagging) so I eliminated the modem.
So, you're doing this: http://blog.ngpixel.com/post/104449747538/how-to-bypass-bell-fibe-hub-and-use-your-own-router ?
That might be part of the problem. I haven't done any troubleshooting using the setup you're describing. I do know there were some related issues at one time with using VLAN with NAT Acceleration enabled. I don't know if those issues still exist (one of them was traditional QoS didn't work properly with NAT Acceleration enabled).
If you still experience issues after following the steps I listed in my first reply in this thread, for troubleshooting purposes,
a) try disabling NAT Acceleration. It's found under Advanced Settings-->LAN-Switch Control-->NAT Acceleration
(set to disable). Then click "Apply". Reboot router (wait for Wi-Fi SSiDs to start broadcasting)-->Reboot ATA.
Check Anveo registration status in the ATA. If Anveo shows as being registered, test calls. If everything works, you found the source of the problem: NAT Acceleration is enabled with VLAN.
b) Re-enable NAT Acceleration. Re-attach your modem (put it back in/use it), and do PPoE login with your router. Disable all the VLAN stuff in the router (return those to defaults). Don't use the modem to do PPoE login (also disable Wi-Fi in it). Click "Apply". Reboot router-->Reboot ATA. Ensure that Anveo is registered in the ATA. Test calls.
simsin:
Quote from: Webslinger on July 17, 2017, 11:50:45 am
So, you're doing this: http://blog.ngpixel.com/post/104449747538/how-to-bypass-bell-fibe-hub-and-use-your-own-router ?
Yes - basically i use router to setup a PPPOE and tell it to use VLAN35. This way I avoid using the Bell modem completely.
But the weird thing is... I have this exact same setup on the AC66 and that setup doesnt cause any issues with ANVEO.
Navigation
[0] Message Index
[#] Next page
[*] Previous page