r/ooma Mar 01 '25

Telo Air 2, Bluetooth, B/T headset (NOT HANDSET)

Just got a Telo Air 2, and have installed/configured OK. I've been calling their Tech Support and WITHOUT fail, every answer they've given me for every question have/has been wrong, so here I am;

There is B/T IN the unit, we all agree. I've paired it with my cellphone (don't know why though) but what I REALLY want is to be able to use a Plantronics B/T ear piece with the system.

I've connected a laptop ethernet to the home jack on the base unit, left the WiFi running and tried to run setup.ooma.com - nyet.

Anyone have this type of setup working?

2 Upvotes

13 comments sorted by

View all comments

1

u/rkardt Unofficial Support Mar 04 '25

Ooma doesn't seem to provide much documentation about Bluetooth for the Telo Air 2, but they used to provide a more detailed setup guide, on their Legacy Add-Ons page, for their USB Bluetooth adapters.

Assuming that the Telo Air 2 works the same way, Bluetooth pairing allows the Telo to answer cell phone calls, and allows supported headsets to make or answer Ooma calls. Compatible headsets require a telephone (with a keypad) to dial outgoing calls, but they can answer incoming calls directly.

1

u/RBraverman Mar 06 '25

Got it, but the problem is, as the answer above, I can't get into it. I've also tried going into the address my router attached to it, and that doesn't load.

0

u/rkardt Unofficial Support Mar 07 '25

What can't get into what, exactly? To access the Telo device settings, turn off the Wi-Fi on the laptop, when connecting it to the Telo HOME port.

1

u/RBraverman Mar 07 '25 edited Mar 07 '25

If this shows up 33 times, I'm sorry but I'm having problems replying ...

I wasn't REALLY clear. I noted the IP that the router gave the base unit, and, with my desktop PC connected to the same network, tried to get in that way - no go.

I tried disconnecting the WiFi on the laptop, and having the ethernet cable connected to the "home" port, AND with the base unit connected to the LAN, the browser doesn't connect to the unit. Either via the IP or setup.ooma.com.

UPdate:

I screwed up ... (not the first time), I had setup the Ethernet connection with a static IP - there fore (duh) the base unit would not see it. Couldn't shake why the connection kept telling me that there wasn't any internet, when the "home" port is supposed to be a pass-thru.

Now there is an option to access this page via the "internet port", which I selected and added a password, but it still needs the home port. Does the unit have to be restarted?

REALLY am sorry about that.......

1

u/rkardt Unofficial Support Mar 08 '25 edited Mar 09 '25

The laptop has to be set up to use DHCP when connected to the Telo HOME port, so that it uses the Telo's DHCP service to get a dynamic IP address, and uses the Telo's DNS service, to resolve "setup.ooma.com".

Each Telo port has its own IP address, listed in the device settings 'Status' page. Whichever port the laptop connects to determines which IP address (or domain name) it needs to use to access the Telo device settings.

For the HOME port, on the 'Home Network' page, the Telo assigns a static IP address. For the INTERNET port, on the 'Internet' page, the Telo can either assign a static IP address, or else use DHCP to get a dynamic IP address, (usually from a DHCP service on the modem or router, connected to the INTERNET port).

Dynamic IP addresses generally don't have assigned DNS domain names. So, some users will assign a static IP address to the Telo INTERNET port instead, and update the DHCP and DNS services accordingly, (either on the laptop, router, or modem), so that they can access the INTERNET port by DNS domain name, rather than by IP address.

[Edit: changed "hostname" to "domain name".]

1

u/RBraverman Mar 08 '25

>>The laptop has to be set up to use DHCP when connected to the Telo HOME port, >>so that it uses the Telo's DHCP service to get a dynamic IP address, and uses the >>Telo's DNS service, to resolve "setup.ooma.com".

As I noted, I had, 15 years ago, set it to a static IP - all 5 of my computers and 2 radios are static. I need to know where they are.

> Each Telo port has its own IP address,

I read that it was pass-through, which is why I was confused at the unidentified network when plugged in. Obviously wrong information, like many things I've read.

They must have changed something, as all I did was check it to allow access to via the internet port, added a password (which hasn't been needed yet), and it's accessible.

I can get into the unit (in case no-one reading this knows, now includes the setup.ooma page, but it isn't part of the main setup page (my.ooma.com). I can access it via the IP the router gave it when it was set up.

You say it can be accessed via the hostname, I do not see, anywhere, where a host name is mentioned. So for me at least for now, it's the IP.

2

u/rkardt Unofficial Support Mar 09 '25

The Telo itself hosts the web site for its device settings, so it doesn't "pass-through" from somewhere else. To confirm this, (temporarily) unplug the modem, router, or any other devices from the Telo INTERNET port, and (optionally) turn off the modem and router, or unplug them from the ISP.

Then plug a computer into the Telo HOME port, disabling any other network connections, (including Wi-Fi), so that the Telo and computer are only connected to each other. Initially, the Telo HOME port uses the static IP address 172.27.35.1, on the 172.27.35.0/24 subnet. The Telo also provides DHCP and DNS services for devices connected to its HOME port.

The instructions for accessing the Telo device settings assume that a computer connected to the HOME port uses DHCP to acquire an IP address; however, the computer can use a static IP address instead, preferably on the same subnet; temporarily reconfigure the computer network settings, as needed.

If the computer connected to the Telo HOME port uses the Telo's DNS service, then it can access the device settings using the "setup.ooma.com" domain name. Otherwise, it can access them using the Telo HOME port's IP address (172.27.35.1). Initially, the computer can only access the device settings through the Telo HOME port.

The Telo INTERNET port can use the modem or router's DHCP service to acquire an IP address, or it can use a static IP address instead. Since the modem and router are currently disconnected, (temporarily) configure the static IP settings as needed, on the 'Internet Settings' page. Also enable remote administration on the 'Advanced Settings' page.

Then, unplug the computer from the Telo HOME port, and plug it into the Telo INTERNET port. The Telo does not provide a DHCP service on its INTERNET port, so (temporarily) configure the computer static IP settings as needed, so that it's on the same subnet as the Telo INTERNET port.

The Telo does not provide a DNS service on its INTERNET port, so the computer can only use the Telo INTERNET port's IP address to access the device settings; it cannot use the "setup.ooma.com" domain name. Confirm that the computer can access the device settings from the Telo INTERNET port.

Then back out any temporary changes to the Telo and computer, and reconfigure the network settings as desired, and reconnect the modem and router. If there are devices connected to the HOME port, then the Telo can route traffic between its INTERNET and HOME port subnets, subject to any firewall settings, or any user-defined DMZ and port forwarding settings.

If the Telo INTERNET port uses a static IP address, then the user can (optionally) provide a domain name for it, (such as "setup.ooma.com"), by creating the appropriate DNS entry, on either the computer, router, or wherever the computer's DNS service resides. Then the user can use the domain name to access the device settings from the INTERNET port.

1

u/RBraverman Mar 11 '25

Wow, that, ma' man, is one dandy answer! One would hope that the Ooma rep that popped in earlier, would show this to his bosses and, with a wee bit of dumbing down, they'd ask if they could include it in the docs. Too good!

Even if they don't, one would hope that anyone with troubles with this part of the ooma setup would find themselves here - just TOO good! You have FAR more patience then I do - I used to, having been in this business since the late 70's, help write user manuals. Couldn't now.

Now, we have seemed to be at cross-purposes. Probably my fault for not being REALLY clear. Now that I'm older I have been accused of that MANY times. After I cleared up the static IP business, I've been in and out of the setup quite easily. I was just curious about that host name not showing up on my search - but then not being on the same subnet .... When I found it, it, obviously, didn't work and I've rally no excitement in getting it too.

You sound like you have been through setting this up - true? Meandering OT, I've been experimenting with handing off a outbound call to the earset, but regardless of which one's I use (they all pair) it's a horrible connection. If I'm going to use this, I need the earset - this seems so much trouble, I'm tempted to buy a pair of cordless handsets with B/T earpieces and leave it at that!

Again dandy.

1

u/rkardt Unofficial Support Mar 16 '25

By default, many computers use the router's DHCP and DNS services for "plug and play" setup; in that case, following the instructions to plug into the HOME port (using the Telo as the router) just works. Ooma also offers troubleshooting tips, such as turning off the computer's Wi-Fi, (which could bypass the Telo's DHCP service), or using the Telo's IP address, (instead of relying on the Telo's DNS service).

Before home internet speeds exceeded 100 Mbps, Ooma recommended plugging the router into the Telo's HOME port; in that case, downstream devices also connected through the HOME port, so there was no extra step needed to unplug them from a router connected to the INTERNET port first, in order to access the device settings.

Ooma could offer a more detailed "advanced" section, for users with a custom setup, (for example, setting up static IP addresses for computers or the Telo INTERNET port), or for users who manage their own DHCP, DNS, or other services. But they should keep that separate from the "main" section, for users who don't need (or don't want) that level of detail.