My Obi202 has for the most part been working well for years in front of my Asus TM-AC1900 router. However, I just got faster internet speed and don't want my Obi throttling my connection down to 30meg, so I tried doing the following, and nothing has worked (all of the following options keep giving me problems either receiving or placing calls using my providers: GV, CallCentric and VoipMS):
1) Put it in bridge mode and kept it in front of the router. Connected my modem to the Obi's Internet port and the downstream router to the Obi's LAN port.
2) Put if in bridge mode and put it after my router. Connected the router to my Obi's Internet port.
3) Put it back in router mode and moved it after my router. Connected the router to my Obi's Internet port.
Is there anything else I can do to get one of these options to work? Since it was working well in front of the router when the Obi was in router mode, if I try that option again, are there any other settings I should change?
Thanks much for any advice you may have.
The OBi200 is relatively slow. For most people it no longer makes sense to have all one's WAN or LAN traffic going through it.
Connect the WAN port of your router to your new modem. Connect the WAN port of your 202 to a LAN port of the router. Connect all other devices to the router. If you had set a static IP address on the 202 you probably need to change it to match the router's subnet or change to DHCP.
If you need to log in to the 202's web GUI do any one of the following:
1. Operate the 202 in bridge mode.
2. Operate the 202 in router mode but temporarily connect a PC to its LAN port when required.
3. Operate the 202 in router mode and enable web GUI access from its WAN port.
More details for option 3 (my preferred method).
https://www.obitalk.com/info/faq/OBi202-sec/Howto-Access-Web-from-WAN
Configure your router to assign a specific ip via dhcp. This ensures the obi device will always be at the same ip address.
https://www.asus.com/support/FAQ/1000906/
Also, depending how adventurous you feel, there are ways of converting the tm-ac1900 to the regular rt-ac68u. Proceed at your own risk. http://www.bayareatechpros.com/ac1900-to-ac68u/ . Note, I've done several of these already (at $48 on amazon it's hard to pass up) and they all work as expected. When doing the CFE patch, select all at the bottom right corner to enable additional DFS channels (for 5ghz).
Thanks for the tips everyone. Yes, my router is T Mobile's version of a regular Asus modem and I believe it's preconfigured for T Mobile's wifi calling or something (I just bought it because it was a good deal ... I don't use Tmobile). Could that be interfering with my Obi? If so, maybe I should reset it to the regular Asus version of the modem, as you suggest. Good to know you've successfully done it.
Regarding option 3: Operate the 202 in router mode and enable web GUI access from its WAN port.
Are you saying I should connect it after my router using the Obi's LAN connection? Or do I still use the WAN port to connect it downstream from my router?
Connect modem to asus router's wan port. Connect obi's wan port to one of the asus lan ports.
Obi's wan<>lan is garbage. It might of been useful a decade ago, but today's speeds exceed what it's wan<>lan is capable of. Do not use the obi's lan port. Put a piece of tape over it and forget it even exists.
Execute the sequence in the obi tutorial link if you wish to configure the obi via its web interface. You'll still need to use the portal to provision a google voice profile, so access to the obi's local ui is not likely needed. However is useful if for nothing else to observe status screens.
Quote from: GPz1100 on May 02, 2018, 05:29:18 PM...access to the obi's local ui is not likely needed. However is useful if for nothing else to observe status screens.
Especially Call History which cannot be seen via the portal.
Quote from: GPz1100 on May 02, 2018, 05:02:55 PM
More details for option 3 (my preferred method).
https://www.obitalk.com/info/faq/OBi202-sec/Howto-Access-Web-from-WAN
Configure your router to assign a specific ip via dhcp. This ensures the obi device will always be at the same ip address.
https://www.asus.com/support/FAQ/1000906/
Also, depending how adventurous you feel, there are ways of converting the tm-ac1900 to the regular rt-ac68u. Proceed at your own risk. http://www.bayareatechpros.com/ac1900-to-ac68u/ . Note, I've done several of these already (at $48 on amazon it's hard to pass up) and they all work as expected. When doing the CFE patch, select all at the bottom right corner to enable additional DFS channels (for 5ghz).
Ok, I have it set up for option 3 (the Obi is acting as a router, connected downstream from my Asus router through the Obi's internet port, and as you recommended I assigned an IP address via DHCP (thanks for the link on how to do that) to the Obi.
I rebooted everything and tested and am still having problems making and receiving calls with the Obi202. For instance, when I dial out on my VoipMS acct., I hear nothing although it rings on the other end. Also outgoing calls on Google Voice works but incoming calls do not ring.
(Haven't changed the TM-AC1900 router yet so it acts like a regular ASUS rt-ac68u, but I'm wondering if that will make a difference in how my Obi202 performs?)
Quote from: Studly on May 03, 2018, 08:29:27 AM
(Haven't changed the TM-AC1900 router yet so it acts like a regular ASUS rt-ac68u, but I'm wondering if that will make a difference in how my Obi202 performs?)
What is your setting for the following?
Advanced Settings-->WAN-->SIP Passthrough
You also mentioned Callcentric. Are your incoming GV calls being forwarded to Callcentric? If so, are you registering successfully to Callcentric? If the above is true, are you seeing incoming GV calls in your Callcentric call records/history?
Quote from: Studly on May 03, 2018, 08:29:27 AM
I rebooted everything and tested and am still having problems making and receiving calls with the Obi202. For instance, when I dial out on my VoipMS acct., I hear nothing although it rings on the other end. Also outgoing calls on Google Voice works but incoming calls do not ring.
This indicates a media problem. The signaling part has set up the call, but the audio (media) is getting blocked somewhere. Note, this applies to sip services. Google voice uses a different mechanism to set up the call. Review Taoman's suggestion above.
For inbound calls to work correctly, correct setting must be used in the google voice account, depending if you want the calls to come through google chat, callcentric, or voipms. Show us a screen shot of your google voice forwarding page from the legacy site (https://www.google.com/voice/b/0/redirection/voice , then gear icon top right, settings). Blank out any personal information.
Assuming gv is properly forwarding the call then the obi must be configured which phone port to pass the call to.
Quote(Haven't changed the TM-AC1900 router yet so it acts like a regular ASUS rt-ac68u, but I'm wondering if that will make a difference in how my Obi202 performs?)
I doubt this will make any difference. I think the tmo model just has some preconfigured qos settings for when mobile devices use tmobile's wifi calling. If you want to rule the router out entirely, connect the obi directly to your modem and retest.
The OP has had his OBi202 working fine with GV before making changes to his local equipment. That should not require him to check that his GV forwarding settings are OK.
Quote from: Taoman on May 03, 2018, 09:07:50 AM
Quote from: Studly on May 03, 2018, 08:29:27 AM
(Haven't changed the TM-AC1900 router yet so it acts like a regular ASUS rt-ac68u, but I'm wondering if that will make a difference in how my Obi202 performs?)
What is your setting for the following?
Advanced Settings-->WAN-->SIP Passthrough
You also mentioned Callcentric. Are your incoming GV calls being forwarded to Callcentric? If so, are you registering successfully to Callcentric? If the above is true, are you seeing incoming GV calls in your Callcentric call records/history?
My router's SIP Passthrough is set to "enable."
Yes, I have GV incoming calls forwarded to Callcentric so I get caller ID on incoming calls. The forwarded GV calls are registering in Callcentric, and when I call the Callcentric number directly, that rings and works.
Quote from: GPz1100 on May 03, 2018, 11:14:14 AM
Quote from: Studly on May 03, 2018, 08:29:27 AM
I rebooted everything and tested and am still having problems making and receiving calls with the Obi202. For instance, when I dial out on my VoipMS acct., I hear nothing although it rings on the other end. Also outgoing calls on Google Voice works but incoming calls do not ring.
This indicates a media problem. The signaling part has set up the call, but the audio (media) is getting blocked somewhere. Note, this applies to sip services. Google voice uses a different mechanism to set up the call. Review Taoman's suggestion above.
For inbound calls to work correctly, correct setting must be used in the google voice account, depending if you want the calls to come through google chat, callcentric, or voipms. Show us a screen shot of your google voice forwarding page from the legacy site (https://www.google.com/voice/b/0/redirection/voice , then gear icon top right, settings). Blank out any personal information.
Assuming gv is properly forwarding the call then the obi must be configured which phone port to pass the call to.
Quote(Haven't changed the TM-AC1900 router yet so it acts like a regular ASUS rt-ac68u, but I'm wondering if that will make a difference in how my Obi202 performs?)
I doubt this will make any difference. I think the tmo model just has some preconfigured qos settings for when mobile devices use tmobile's wifi calling. If you want to rule the router out entirely, connect the obi directly to your modem and retest.
Thanks for the help, but GV's incoming calls (forwarded to Callcentric) have been working fine for years when my Obi was in front of the router in router mode and still works fine there (but I don't want it limiting my internet connection). It's only when I move the Obi downstream from the router in either mode that I have call problems. Or if I set it to bridge mode and keep it in front of the router, then I have problems too.
Good idea on testing it straight from the modem, but since the Obi works fine in router mode between my Asus router and the modem, I think the problem has something to do with the router settings or the Obi settings that need changing if placed behind the router.
Thanks for everyone's good questions and suggestions!
Quote from: Studly on May 03, 2018, 11:45:30 AM
My router's SIP Passthrough is set to "enable."
Well it should be working and since calls directly to your Callcentric number work my theory is shot.
Do
incoming calls to your Voip.ms number work?
I've converted several TM-AC1900s to AC68Us using Merlin firmware. They suggest setting SIP Passthrough to "Enabled + NAT helper." You can try making that change and restarting everything but I'm not at all confident that will make any difference.
Quote from: Studly on May 03, 2018, 11:45:30 AM
Yes, I have GV incoming calls forwarded to Callcentric so I get caller ID on incoming calls. The forwarded GV calls are registering in Callcentric, and when I call the Callcentric number directly, that rings and works.
Well color me confused. Calls directly to your Callcentric number work?!? And you can see your GV calls being successfully forwarded to your CC account by looking at your Callcentric call records? But incoming GV calls don't ring your OBi connected phone? Is that all correct? If so, that's a mind bender for me.
Anyone else have any ideas here? After OP's last post I'm at a loss.
^^Maybe the tmobile firmware is indeed doing something funky to the sip traffic. The conversion process isn't difficult, but is tedious, especially the first time.
Quote from: Taoman on May 03, 2018, 12:07:33 PM
Quote from: Studly on May 03, 2018, 11:45:30 AM
My router's SIP Passthrough is set to "enable."
Well it should be working and since calls directly to your Callcentric number work my theory is shot.
Do incoming calls to your Voip.ms number work?
I've converted several TM-AC1900s to AC68Us using Merlin firmware. They suggest setting SIP Passthrough to "Enabled + NAT helper." You can try making that change and restarting everything but I'm not at all confident that will make any difference.
Quote from: Studly on May 03, 2018, 11:45:30 AM
Yes, I have GV incoming calls forwarded to Callcentric so I get caller ID on incoming calls. The forwarded GV calls are registering in Callcentric, and when I call the Callcentric number directly, that rings and works.
Well color me confused. Calls directly to your Callcentric number work?!? And you can see your GV calls being successfully forwarded to your CC account by looking at your Callcentric call records? But incoming GV calls don't ring your OBi connected phone? Is that all correct? If so, that's a mind bender for me.
Anyone else have any ideas here? After OP's last post I'm at a loss.
Yes, incoming calls work to Voip.ms. However outgoing calls from VOIP.ms do not work right. It doesn't ring on the callers end when I make a call from it, but it may ring on the receiver's end.
On your last question, yes, that is all correct.
Regarding your sip/nat passthrough sugguestion:
On my sip passthrough screen on my router it only allows me to choose enable or disable. But the name of the page where I have an option to do that is called: "WAN - NAT Passthrough" and then it says:
"Enable NAT Passthrough to allow a Virtual Private Network (VPN) connection to pass through the router to the network clients." Then when I go down to the option for SIP Passthrough, I can either disable or enable it.
Quote from: GPz1100 on May 03, 2018, 12:16:47 PM
^^Maybe the tmobile firmware is indeed doing something funky to the sip traffic. The conversion process isn't difficult, but is tedious, especially the first time.
Is there a way I can just change the Obi to bridge mode and keep it before the router and get it to work? Not sure if I was doing everything correctly when I set it up before. If I do that, are there any other changes I need to make on the Obi other than doing the phone commands to set it to bridge mode? And then what would be the proper way to connect it upstream to the modem and downstream to the router?
Quote from: GPz1100 on May 03, 2018, 12:16:47 PM
^^Maybe the tmobile firmware is indeed doing something funky to the sip traffic. The conversion process isn't difficult, but is tedious, especially the first time.
Possible but unlikely especially considering calls directly to CC number (and Voip.ms) work ok.
I've bought all my TM-AC1900s thru SlickDeals. I've read dozens of reports from folks who never bothered to change firmware and stayed with the T-Mobile firmware and had zero problems with SIP.
Quote from: Studly on May 03, 2018, 12:26:09 PM
Quote from: GPz1100 on May 03, 2018, 12:16:47 PM
^^Maybe the tmobile firmware is indeed doing something funky to the sip traffic. The conversion process isn't difficult, but is tedious, especially the first time.
Is there a way I can just change the Obi to bridge mode and keep it before the router and get it to work? Not sure if I was doing everything correctly when I set it up before. If I do that, are there any other changes I need to make on the Obi other than doing the phone commands to set it to bridge mode? And then what would be the proper way to connect it upstream to the modem and downstream to the router?
In bridge mode the two ethernet ports on an OBi202 behave identically.
There are different things you can try to troubleshoot this but putting your OBi in front of your router in bridge mode isn't one I would recommend unless there is no alternative.
Why your incoming GV calls don't ring is a poser. I would try this:
Go to Voice Services for your Callcentric configuration and disable it. Your OBi should restart.
Go here and enable Google Chat and save your settings.
https://www.google.com/voice/b/0/redirection/voice/#phones (https://www.google.com/voice/b/0/redirection/voice/#phones)
Now make a call to your GV number. Does your OBi connected phone ring?
Quote from: Taoman on May 03, 2018, 12:58:32 PM
There are different things you can try to troubleshoot this but putting your OBi in front of your router in bridge mode isn't one I would recommend unless there is no alternative.
Why your incoming GV calls don't ring is a poser. I would try this:
Go to Voice Services for your Callcentric configuration and disable it. Your OBi should restart.
Go here and enable Google Chat and save your settings.
https://www.google.com/voice/b/0/redirection/voice/#phones (https://www.google.com/voice/b/0/redirection/voice/#phones)
Now make a call to your GV number. Does your OBi connected phone ring?
Actually, before I tried your suggestion above, I did this and got my GV number to ring through on an incoming call: On the phone line with Google Voice incoming through CallCentric, I did more test phone calls and unplugged and replugged in my Panasonic cordless phone base unit that is connected through the Obi to that line, and now it rings through when someone calls our GV number.
So now the main problem seems to be calling out. Whether using Voip.MS (which sometimes works and sometimes doesn't) or GV (doesn't work at all ... you dial and then don't hear anything), the outgoing calls are the problem.
Quote from: Studly on May 03, 2018, 08:29:27 AM
Also outgoing calls on Google Voice works but incoming calls do not ring.
So the above statement you made in your third post is not true?
Does the echo test work? Dial **9 222 222 222. Does it answer and can you hear your own voice coming back to you?
Quote from: Taoman on May 03, 2018, 01:09:53 PM
Quote from: Studly on May 03, 2018, 08:29:27 AM
Also outgoing calls on Google Voice works but incoming calls do not ring.
So the above statement you made in your third post is not true?
Yes, it is no longer true. I've found while testing this since moving the Obi behind the router, things don't work consistently over time. Also, I was testing both lines from the same phone (i.e., pressing **2 to call out on the other line), and I realized I probably shouldn't be doing that since it complicates things.
Quote from: drgeoff on May 03, 2018, 01:20:54 PM
Does the echo test work? Dial **9 222 222 222. Does it answer and can you hear your own voice coming back to you?
Yes, the echo test works on both outgoing lines (GV and Voip.ms).
Quote from: Studly on May 03, 2018, 01:30:51 PM
Quote from: drgeoff on May 03, 2018, 01:20:54 PM
Does the echo test work? Dial **9 222 222 222. Does it answer and can you hear your own voice coming back to you?
Yes, the echo test works on both outgoing lines (GV and Voip.ms).
That is nonsense. When you dial **9 222 222 222 the echo test does not use either GV or Voip.ms.
Quote from: drgeoff on May 03, 2018, 01:36:20 PM
Quote from: Studly on May 03, 2018, 01:30:51 PM
Quote from: drgeoff on May 03, 2018, 01:20:54 PM
Does the echo test work? Dial **9 222 222 222. Does it answer and can you hear your own voice coming back to you?
Yes, the echo test works on both outgoing lines (GV and Voip.ms).
That is nonsense. When you dial **9 222 222 222 the echo test does not use either GV or Voip.ms.
Ok, but when I dialed out on each phone connected to each line in the Obi, the echo test worked.
Quote from: Studly on May 03, 2018, 01:38:13 PM
Quote from: drgeoff on May 03, 2018, 01:36:20 PM
Quote from: Studly on May 03, 2018, 01:30:51 PM
Quote from: drgeoff on May 03, 2018, 01:20:54 PM
Does the echo test work? Dial **9 222 222 222. Does it answer and can you hear your own voice coming back to you?
Yes, the echo test works on both outgoing lines (GV and Voip.ms).
That is nonsense. When you dial **9 222 222 222 the echo test does not use either GV or Voip.ms.
Ok, but when I dialed out on each phone connected to each line in the Obi, the echo test worked.
You don't understand how OBis work. A phone port is not rigidly assigned to a Voice Service. Either phone port can make a call on any of the Voice Services. No matter which phone port you use, when you dial **9 followed by 9 digits the call goes to an Obihai server, not via any of your other Voice Services.
Anyway, that the echo test worked means there is no need for further investigation on that tack.
Quote from: drgeoff on May 03, 2018, 01:20:54 PM
You don't understand how OBis work. A phone port is not rigidly assigned to a Voice Service. Either phone port can make a call on any of the Voice Services. No matter which phone port you use, when you dial **9 followed by 9 digits the call goes to an Obihai server, not via any of your other Voice Services.
Anyway, that the echo test worked means there is no need for further investigation on that tack.
Gotcha. Sorry, I stated it wrong.
To provide an update and confuse matters more, after more test calls, recent outgoing calls from both lines started working again just now. But I'm sure that won't be the case long term. Before I posted on this forum, I thought I had it working correctly for a full day, but then suddenly either certain calls wouldn't ring in when people called or dialing out didn't work.
Update for today: I'm having problems with incoming calls again to GV, which are then forwarded to CallCentric. So it seems both outgoing and incoming calls may work for a while and then one or the other doesn't work again for a while. It's really sporadic.
Since nothing else has worked, I'd like to try putting the Obi in front of the router again, in bridge mode, but wanted to double check the correct settings and connections. Not sure I did it correctly when I tried it previously.
Quote from: drgeoff on May 03, 2018, 12:53:21 PM
In bridge mode the two ethernet ports on an OBi202 behave identically.
So if both ports on the Obi work the same in bridge mode, should it work for me to connect either port to my modem and the other port to the downstream router? Other than doing the phone keypad commands to put my Obi in bridge mode, are there any other settings I need to change to make the Obi work properly in bridge mode?
Quote from: Studly on May 04, 2018, 06:56:56 AM
So if both ports on the Obi work the same in bridge mode, should it work for me to connect either port to my modem and the other port to the downstream router? Other than doing the phone keypad commands to put my Obi in bridge mode, are there any other settings I need to change to make the Obi work properly in bridge mode?
No you cannot do that.
In bridge mode the OBi202 is a 3 port ethernet switch. Two ports are the ethernet jacks and the third one is the internal connection to 202's VoiP stuff.
You can only connect one ethernet address to most modems. You use a router, not a switch, to use more than one. That is basic IP networking, not a limitation of the OBi202.
Thanks again for educating me on the Obi. :)
Are there any newer models of the Obi that don't limit you in router mode to 30k? If so, which do you recommend?
Quote from: Studly on May 04, 2018, 09:06:27 AM
Thanks again for educating me on the Obi. :)
Are there any newer models of the Obi that don't limit you in router mode to 30k? If so, which do you recommend?
You DO NOT NEED router mode. The OBi100, 110 and 200 do not have a router mode and thousands of people have been using them successfully for years. Use the T-Mobile/Asus router to do the routing and forget that the 202 has router mode.
The option 3 right back at the early stages of this thread should work.
Quote from: drgeoff on May 04, 2018, 09:02:00 AM
annot do that.
In bridge mode the OBi202 is a 3 port ethernet switch. Two ports are the ethernet jacks and the third one is the internal connection to 202's VoiP stuff.
You can only connect one ethernet address to most modems. You use a router, not a switch, to use more than one. That is basic IP networking, not a limitation of the OBi202.
Do you have some special version of the 202 with 3 ethernet ports?
(https://images10.newegg.com/ProductImageCompressAll1280/33-617-003-12.jpg)
@GPz1100
Either your reading or comprehension is below par.
Indeed.....
Quote
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: unm: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:00:4d:52:56:4c brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb qlen 1000
link/ether 9c:ad:ef:xx:yy:zz brd ff:ff:ff:ff:ff:ff
inet 10.10.3.103/24 brd 10.10.3.255 scope global eth1
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 9c:ad:ef:x2:y2:z2 brd ff:ff:ff:ff:ff:ff
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/ether 9c:ad:ef:x2:y2:z2 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.1/24 brd 192.168.10.255 scope global br0
Taking a page out of Steve's book eh?
Output from ssh'ing into the obi202. There's no 3 ports. Two interface and a bridge.. I've yet to hear a bridge called a switch.... Albeit a bridge consists of interfaces, virtual or real.
Quote from: GPz1100 on May 04, 2018, 01:26:54 PM
Indeed.....
Quote
# ip addr show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
2: unm: <BROADCAST,MULTICAST> mtu 1500 qdisc noop qlen 1000
link/ether 00:00:4d:52:56:4c brd ff:ff:ff:ff:ff:ff
3: eth1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc htb qlen 1000
link/ether 9c:ad:ef:xx:yy:zz brd ff:ff:ff:ff:ff:ff
inet 10.10.3.103/24 brd 10.10.3.255 scope global eth1
4: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 9c:ad:ef:x2:y2:z2 brd ff:ff:ff:ff:ff:ff
5: br0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue
link/ether 9c:ad:ef:x2:y2:z2 brd ff:ff:ff:ff:ff:ff
inet 192.168.10.1/24 brd 192.168.10.255 scope global br0
Taking a page out of Steve's book eh?
Output from ssh'ing into the obi202. There's no 3 ports. Two interface and a bridge.. I've yet to hear a bridge called a switch.... Albeit a bridge consists of interfaces, virtual or real.
What I wrote was perfectly clear. If you still want to argue, go to the Admin Guide and search for "IP Routing and LAN Switching Features (OBi202 and OBi302 Only)". Read the two line paragraph.
Just an update to my ongoing problem getting my phone lines to work once consistently once I moved my Obi202 after my router.
Well, good news, I think I have the problem solved! Thought I'd try a new ethernet cable to connect the Obi and router to, and for good measure, I also used a different LAN port on the router. Now everything has worked great for about 3 days. Thanks for everyone's help and assistance on that and assuring me it should work with the Obi behind the router.
However, I do have a new minor problem now. When I'm on a call, it knocks out my internet connection on my PC that is also connected via ethernet to the router. (It doesn't impact other devices that are connected via wifi.) As a reminder, I have the Asus TM-AC1900 router, with stock firmware. The only change I made to the router settings was to set it so the Obi has an assigned IP address, as suggested earlier in this thread. Any suggestions on what other router settings I can tweak to fix this new problem?
Check that the static IP address you gave the OBi was not already assigned elsewhere.
Quote from: drgeoff on May 07, 2018, 09:53:00 AM
Check that the static IP address you gave the OBi was not already assigned elsewhere.
Ok, the call problems have come back on by Obi202. GV is working fine but now I have sporadic problems calling out on Voip.ms. Since I'm a novice when it comes to router (and Obi) settings, I did some more research, watched a Youtube video on how to assign static IP addresses and double check them. I found out that when I did it previously, I did it wrong. In fact, my LAN connected PC did have the same IP as the Obi. So maybe that is what has been causing problems. Also, my MAC address is coming up the same for the Obi and my PC. So only one will show up in my network connections on my Asus router control panel. So I manually typed in the Mac address of my Obi device and assigned a new IP address to it, then after saving and rebooting everything, my router doesn't find my Obi.
Is there some setting on the Obi or on a router where it clones the Mac address? I seem to remember a few years back posting some questions in this forum about a problem I was having and someone recommended doing something with the Mac address settings. Where would I find these settings on the Obi? Or could it be a setting on my Asus TM-AC1900 router?
Another update. I found where the Mac Clone setting is on my Obi202: Router Configuration -> WAN Settings -> MACAddressClone :
Nothing was entered in that blank and there was a check mark under Obitalk Settings. However when I unchecked that Obitalk Settings box, as if I wanted to enter something, then it showed the Mac address of my PC in that blank, as I entered it a few years ago when I was trying to fix another problem using help from this forum (see http://www.dslreports.com/forum/r29239119- if you're interested in that old thread). I've completely deleted that Mac address and resaved and rechecked Obitalk Settings for MacAddressClone and now the address doesn't come back when I uncheck both boxes.
Anyway, now I have to reboot and retest. Will report back on if that fixes the problem.
Ok, still no go. Both my PC and my Obi are still sharing the same mac address and only one will show up at a time on my router "clients" list. This thread is getting long, and the problem has morphed into a new one, so I'm going to start a new thread regarding not being able to turn off the Mac address clone.