New router - now Obi calls don't connect

[mychaelp]

Hello everyone,

I bought a new Archer c5400 router finally. Works amazing! However, now my Obi100 will make calls but will not actually connect them once someone picks up the line, or someone calls me and I pick up. Ugh. I hear phones ring, but if picked up, nothing.

I thought I could simply just plug in the Obi100 to the new router and all work.

Is there something else I need to do? Vestalink is my first provider and they  tell me to reset the Obi completely and do a new setup. I'd rather not since I heard I may have to pay Obitalk to do that now? I also don't know if that would fix the issue. Maybe port forwarding?
I also have a callcentric number set up in the port 2 FYI.

Any suggestions or tips are appreciated, I love my Obi, but would like it to work with my new router.
For now I've gone back to my old Cisco router and it works again.

thanks

[Mango]

OBiTALK doesn't cost anything, as long as you do any necessary firmware updates by yourself.  If you require a firmware update, follow the manual update instructions here: http://www.obitalk.com/forum/index.php?topic=11256.msg73954#msg73954

Suggestions:

1) Disable your new router's SIP ALG if possible.  Also, navigate to your OBi's Voice Services >> SP1 Service and change X_UserAgentPort to a random number between 20000 and 65535, for example, 33884.  Reboot and retest.  If you configured your device with OBiTALK, you will need to use OBi Expert Configuration to make the change.

2) If 1) did not work, try to forward your RTP ports.  I'm assuming Vestalink is configured with ITSP Profile A, and the RTP LocalPortMin and LocalPortMax are the default of 16600 and 16798.  Use your router to forward UDP (not TCP) ports 16600-16798 to your OBi100's static IP address.  (Replace with the port numbers you use if not the ones I listed.)  Retest.  If this does not solve the problem, remove your port forwarding, as it should only be used when things won't work any other way.

3) If neither 1) nor 2) work, I would be interested to know if the symptoms change if you change ITSP Profile A >> SIP >> X_DiscoverPublicAddress.  (I.e. turn on if off, turn off if on.)  Reboot and retest.

Let us know how things go.

[mychaelp]

OBiTALK doesn't cost anything, as long as you do any necessary firmware updates by yourself.  If you require a firmware update, follow the manual update instructions here: http://www.obitalk.com/forum/index.php?topic=11256.msg73954#msg73954

Suggestions:

1) Disable your new router's SIP ALG if possible.  Also, navigate to your OBi's Voice Services >> SP1 Service and change X_UserAgentPort to a random number between 20000 and 65535, for example, 33884.  Reboot and retest.  If you configured your device with OBiTALK, you will need to use OBi Expert Configuration to make the change.

2) If 1) did not work, try to forward your RTP ports.  I'm assuming Vestalink is configured with ITSP Profile A, and the RTP LocalPortMin and LocalPortMax are the default of 16600 and 16798.  Use your router to forward UDP (not TCP) ports 16600-16798 to your OBi100's static IP address.  (Replace with the port numbers you use if not the ones I listed.)  Retest.  If this does not solve the problem, remove your port forwarding, as it should only be used when things won't work any other way.

3) If neither 1) nor 2) work, I would be interested to know if the symptoms change if you change ITSP Profile A >> SIP >> X_DiscoverPublicAddress.  (I.e. turn on if off, turn off if on.)  Reboot and retest.

Let us know how things go.

hello, and thank you for your input. I will do this, this evening if I get home before too late, otherwise later this week when I do. I'm not extremely technically skilled with these things, but usually can follow along as I see the various menus. It was interesting that I can make and receive calls (they ring), but when they pick up, there are issues. And thank you for clarifying that Obitalk doesn't cost anything. I don't think updating the firmware should be needed if it worked just a day ago.

[drgeoff]

From my perusal of the manual, there does not appear to be a way to turn off SIP ALG via the GUI.  Try the method at http://www.tp-link.com/en/faq-343.html

[mychaelp]

From my perusal of the manual, there does not appear to be a way to turn off SIP ALG via the GUI.  Try the method at http://www.tp-link.com/en/faq-343.html

thanks, it notes at the lower portion of the page that the change would be temporary and those features would be turned back on after a restart. Will check it out anyway, along with the port items. I have seen elsewhere online, and here in these forums where some problems (somewhat different than mine however) were resolved with the port changes. thanks again

[mychaelp]

From my perusal of the manual, there does not appear to be a way to turn off SIP ALG via the GUI.  Try the method at http://www.tp-link.com/en/faq-343.html

Editing my last post. After going through over and over again until almost throwing this thing away, I found a buried menu that had the ALG setting you wrote about. Now it appears to be working. The ports settings are very confusing, and I tried over and over many different settings with no luck. Crossing my fingers this keeps working, it's a really fast router, but the old one worked with everything out of the box.
Will review on Amazon with a 1-star rating since it should just work. The average person would have given up already.
Thank you for your help, your advice about the ALG was the only one I found of that type, everyone else, even Vestalink and Obihai through the support ticket said to do the ports, that did nothing at all for me. I even tried a DMZ setting for the Obi's local IP address with no luck.
have a good weekend

[drgeoff]

https://www.obitalk.com/info/faq/sip-alg

and

http://www.obihai.com/support/troubleshooting/sg/inc . Then click the " I am using a SIP service..." and see Step 2.

Evidently someone at Obihai knows (or knew) about the SIP ALG issue.

[mychaelp]

https://www.obitalk.com/info/faq/sip-alg

and

http://www.obihai.com/support/troubleshooting/sg/inc . Then click the " I am using a SIP service..." and see Step 2.

Evidently someone at Obihai knows (or knew) about the SIP ALG issue.

Thank you for the info. I'm liking this new router quite a bit. VoiP works flawlessly so far even while using the media server and streaming a movie with it, along with various phones in the house connected as well.
Your help is greatly appreciated. I've bookmarked for future use as I know things will happen.