$99.92 - Ooma Telo Home Phone Service VoIP Phone and Device

nettalk was a disaster. I lost my number I loved and service was disrupted a ton. ooma is far better. zero issues. had it for a year now. costs 3.95 a month.

Still happy with them, 3 years so far.

The same as this one?
http://www.staples.ca/en/Ooma-Telo-Cana ... CA_1_20001
Actually Staples has the BT adapter bundle together at
http://www.staples.ca/en/Ooma-Telo-Air- ... CA_1_20001

5 years later im still happy with them

Might be an internet speed issue or phone you are using. Have you tried a different handset?

feejai wrote: ↑I have been with Ooma as well for almost three years now. I am happy with the service except that there is a bit of a delay when talking on the phone (takes some getting used to). Has anyone else had this issue and/or have a fix?

feejai wrote: ↑ I have been with Ooma as well for almost three years now. I am happy with the service except that there is a bit of a delay when talking on the phone (takes some getting used to). Has anyone else had this issue and/or have a fix?

You're not the only one (and I would consider your experience to be unacceptable):
http://www.ooma.com/forums/viewtopic.ph ... 5&p=139211
costco-ca-voip-ooma-telo-home-phone-110 ... #p24754741
ooma-ooma-telo-wireless-adapter-ymmv-99 ... #p26314311
costco-ca-voip-ooma-telo-home-phone-110 ... #p24754193
etc.

People in Ontario or further east might want to try the east coast server.
Request the East Coast Server here: http://www.ooma.com/forums/viewtopic.php?f=4&t=20813
Also, visit http://support.ooma.com/home/configurin ... of-service and http://support.ooma.com/home/learning-m ... ervice-qos.

There's too many people who seem to believe that everyone should, universally, have the exact same experience using the exact same SIP service. They don't. Server location, where you're located, and your ISP's routing tables matter.

People should be testing their pings and jitter (you want little to no variation between pings) to the specific VoIP providers' SIP servers they plan on using before purchasing anything.

My pings to

a) voip.freephoneline.ca average 11 ms.
b) voip2.freephoneline.ca average 12 ms
c) voip4.freephoneline.ca average 27 ms

I also see low latency to voip.ms closest sip servers to me as well.
http://wiki.voip.ms/article/Choosing_Server


My pings to VoIP sip servers (FPL, Anveo, voip.ms and to ping.callcentric.com), are well below 50.

Anything over 200ms is unacceptable. You'll begin to encounter crosstalk, even if an untrained ear doesn't notice. So, if you're getting really high pings and jitter, I would avoid the service you're testing.

What you don't want to see is 40, 45, 50, 35, 500, 40, 30, 45, 700. That's bad jitter.
You want relatively consistent pings without a lot of variation. When using winmtr, look at the very last hop or line.


Ooma is selling a proprietary device and a single service (Ooma's).
Their SIP servers are located in California. They also a SIP server location on the U.S. East Coast now, but I haven't
looked into where that location on the East Coast is. I'm not positive
whether they will offer something more local for Canadian customers in the future.
http://www.monitis.com/traceroute/
208.83.244.94 is one Ooma SIP server that seems to be on the west coast of the U.S.
Regardless, Ooma is a U.S. company, based in California.

Some popular voip services include
freephoneline.ca (servers are in Ontario, I think, possibly around Waterloo, but I'm not positive), voip.ms (wide range of server locations: http://wiki.voip.ms/article/Choosing_Server), anveo.com (Montreal), www.thespout.ca (Vancouver and Seattle), and callcentric.com (New York).




1.Use winmtr http://winmtr.net/download-winmtr/. Ping about 100 times.

If you're on a Macintosh, maybe this helps: https://www.reddit.com/r/TagPro/comment ... tr_on_mac/

When using WinMTR, look at your average ping and then maximum ping. Although WINMTR doesn't provide a jitter value, you can get an idea of what yours is by subtracting maximum ping from your average.
Jitter is the difference between each successive ping.
The bigger the difference, the bigger the problem.

Same with ping, which represents lag or delay. The lower your ping and jitter, the better.

Generally speaking it's best to have a decent router for VoIP with strong QoS features.
Stick your ISP's modem/router combo in bridge mode, use your own router, and properly enable QoS in your router for your ATA.



2. For Freephoneline.ca (Ontario based, possibly around Milton or Waterloo), test to voip.freephoneline.ca (let winmtr ping about 100 times), voip2.freephoneline.ca, and voip4.freephoneline.ca. You can copy text to clipboard and paste your results (do not post your own IP public address though) and post them for others to examine if you want.

You do not want high pings and lots of jitter (you do not want a lot of variation between each ping). If you get horrible results, you should probably avoid FPL.

You should also test to make sure FPL works for you before paying anything: https://www.fongo.com/app/desktop/. You will need a microphone and speakers (or preferably a headset).

3. For voip.ms, test to the closest server to you:
http://wiki.voip.ms/article/Choosing_Server

This company has a lot of servers in a lot of different locations.

4. For Anveo (Montreal POP), test to sip.ca.anveo.com

POP= Point of Presence
That's essentially an access point or physical location where two or more types of communication or network devices make a connection.

5. For The Spout (Vancouver), test to ca.sipfrom.thespout.ca
Spout Communications also has servers in Seattle.

Spout Communications can obtain phone numbers for a lot of rural areas in Canada.

6. For Callcentric (New York), test to ping.callcentric.com

7. For Ooma (California), test to myxprov.ooma.com
If I find the east coast server address (or if someone PMs it to me), I'll post it.

By the way, with WinMTR, you should also test to 74.125.39.7 (California) if you plan on trying to use Google Voice.
Obtaining a Google Voice number requires that you have a U.S. IP address and a U.S. phone number first (and I will generally be avoiding questions on how to go about obtaining a GV number).


Pinging and testing to the SIP servers you're thinking of using (and to Google Voice) should always be the first steps before jumping into a voip service.
Do this between 8 p.m. and 11 p.m. to see if local congestion is a factor (this often is your ISP's fault). Sundays are the best days to test (because that's when most people in your area will be home). 8 p.m. - 11 p.m. is prime time.

If you get horrible results (really high pings and jitter), do not sign up for the service. You will not be happy.
This goes for all VoIP services. Test to their servers first.

This is one reason why I suggest testing first . . .

Ping is a measurement of data packet transmission, and ping does affect delay or lag. All gamers know, almost inherently, that lag affects them negatively. A PC gamer will pound his or her keyboard in hope that a character will respond on his or her monitor, quickly, but when there's a delay or lag, reality doesn't meet expectation. A gamer can see this problem visually. Over VoIP, anything over 200-210 ms, you will typically start to encounter crosstalk due to increased delay, even if the untrained ear doesn't notice. All VoIP services are subject to the same scientific principles including the fact that speed of transmission affects delay, and Ooma is not some magical service that is somehow exempt from issues arising from high pings and jitter. I have helped a few people with Ooma. When pings (and especially) jitter are high, it's a pretty horrible experience, just as it would be with any other VoIP service. When pings and jitter are fine, so is Ooma, at least for local calls.

Paul's not having jitter issues, but he is experiencing delay:



Start at the 48 minute 20s mark.

https://tinkertry.com/why-i-gave-up-on- ... ne-service

Paul wrote:
"I figured it was time for one last email to Ooma. Can they give me a way to connect my phone calls from a server a lot closer to Connecticut than San Jose, California? It got me a response the next day that gave me a bit of a chuckle


Dear PAUL,

Thank you for contacting Ooma Customer Care. Good day! We are sorry that this isn`t going to work for you. As mentioned before, we only have one server which is in west coast as of yet and we do not have control over with this latency.

If you decide to port your nos. out of Ooma, we will need to keep your account active while the other provider is in the process of porting your nos. out. Please let us know once that is completed so we can remove your nos. from our database.

In case you want to stay with us, we can refund half of the amt. you paid for the Annual Premier.

Please write me back if you have further questions and I will respond to you as quickly as possible.

Thank you for choosing Ooma!

Sincerely,

Ooma Customer Care Specialist
Chat Support is now available 24/7
To reach a live chat agent, please visit us at www.ooma.com/support"

Ooma now has an East Coast server. So Paul may want to test with Ooma again. Back when he was using Ooma, the only server location was in California. However, Ooma may be using the cheapest routing options available after its venture capital ran dry (according to some people), which may make some call quality in some cases less than ideal: http://www.dslreports.com/forum/r30911315-

So go ahead and test.

Anyone using any communication service (or even when playing online games or using other online services) should understand that the longer the path to the server being used, the greater the potential exists for a problem to occur somewhere along that path. This is one reason why voip.ms is so desirable to some people; it has SIP servers situated in numerous locations (not just in California).


Another factor to keep in mind, is that during prime time (between 8 p.m. and 11 p.m.) cable internet nodes may be oversubscribed and face congestion issues (and congestion can also exist with DSL). So I suggest testing services between 8 p.m. and 11 p.m., particularly on Sundays, when everyone in your area will be home.

Running http://vac.visualware.com/index.html at 8p.m. (especially on Sunday) might be a better test than a speedtest. Look at California (for Ooma users) and San Jose. Or pick the server that's closest to your VoIP provider's server. A MOS score below 4.0 is bad news. It means call quality will not be good.

@Webslinger thanks for a detailed reply, could you please let me know how can I test VOIPMUCH service (ping) as I am having a lot static and jitter with them and planing to switch to some other provider..............Thanks again for all you help

w11x22 wrote: ↑ @Webslinger thanks for a detailed reply, could you please let me know how can I test VOIPMUCH service (ping)

I've never used them. If you have an ATA that you can log into, find the server you're using. If you can't, you can try to monitor traffic on your LAN (router/firewall logs) for outgoing connections to a specific IP address whenever you make calls (or use something like Wireshark to monitor outgoing traffic). Otherwise, you'd have to contact them and ask for either the server address or IP address of the SIP media server you're using.


I'm copying and pasting a lot of stuff of this thread: newegg-obihai-obi200-ata-49-99-1-50-ehf ... #p27516045. I suggest reading through the first two pages. Actually, you may find the preamble (the first 4 pages) of this PDF guide useful: http://forum.fongo.com/viewtopic.php?f= ... 805#p73839.

as I am having a lot static

1. First thing I would do is try a different phone.

2. Try moving your ATA away from other devices to see if that helps.

3. Try a different power supply

4. If the static only occurs on very specific calls, it could be the fault (of the very likely) of a cheap carrier (to lower costs) being used by VOIPMUCH.

and jitter

I'm getting choppy audio, what should I do?

Generally speaking it's best to have a decent router for VoIP with strong QoS features.
Stick your ISP's modem in bridge mode, use your own router, and properly enable QoS for your ATA.
Refer to your router's manual.

I'm not a big fan of this site, but for a general QoS description, visit http://www.voipmechanic.com/qos-for-voip.htm (avoid anything it says about G729 codec).

I'm suggesting Toronto below, because FPL's SIP servers are in Ontario. When you test, pick the location that is closest to your VoIP service provider's server location.

sfrancis wrote: ↑Have been using freephoneline with obihai 202 behind Asus RT N66U router. Often time people complain that my voice very choppy on their end, yet I seem to hear them fine. Is there setting that I should tweak on ATA set up or on router? Thanks very much

That's usually related to upload jitter/packet loss.

1) The typical reaction would be to try enabling QoS properly in your router for your ATA. Refer to your router's manual. If your router was issued by your ISP, contact your ISP.

Probably in the traffic manager area, use a drop down box to select "User Defined Rules". Then create a rule giving traffic highest priority to your ATA's MAC address.

2) Another possibility is you're dealing with congestion during prime time (8p.m. to midnight, especially on Sundays). That's an ISP issue (possibly oversold its service in your area).

Try running Running http://vac.visualware.com/index.html at 8p.m. (especially on Sunday).

Pick the test location that's closest to where your VoIP server is situated.
A MOS score below 4.0 is bad news. It means call quality will not be good.
The advanced (+) tab provides interesting info.

You should also try the winmtr test I mention over here around 8 p.m. to FPL's servers:
newegg-obihai-obi200-ata-49-99-1-50-ehf ... #p27515963

Anything over 200ms is unacceptable.

What you don't want to see is 40, 45, 50, 35, 500, 40, 30, 45, 700. That's bad jitter.
You want relatively consistent pings without a lot of variation.

One reason why jitter can occur is due to other devices on your LAN (local area network) using bandwidth. That’s why properly enabling QoS in your router for your ATA is always a good idea. Refer to point 4 in the Preamble.

Bad jitter can produce broken up audio or choppiness during phone calls. Severe jitter can cause calls to drop. Ping affects delay.

If the problem only occurs during prime time (as opposed to weekday mornings), then I would probably start thinking your ISP is to blame.

Navon01 wrote: ↑The Internet is 100down/10up.

Down doesn't matter. What people hear from you is upload.

No other devices are being used at time of bad voice quality.

A lot of people say that without realizing other devices and/or programs may actually be using bandwidth in the background. It's really not a good idea, in general, to be using a router that doesn't have a good QoS feature for VoIP.

But if what you wrote is really true, then you may be dealing the possibility of congestion during prime time (8p.m. to midnight, especially on Sundays). That's an ISP issue (possibly oversold its service in your area).

Try running http://vac.visualware.com/index.html at 8p.m. (or between 8 p.m. and 11 p.m.)

Select a test server location that's located close to the SIP server you're using.
A MOS score below 4.0 is bad news. It means call quality will not be good.


You should also try the winmtr test (or if you're on a mac, maybe this helps: https://www.reddit.com/r/TagPro/comment ... tr_on_mac/) I mention over here around 8 p.m. to FPL's servers:
newegg-obihai-obi200-ata-49-99-1-50-ehf ... #p27515963

If the problem only occurs during prime time (as opposed to weekday mornings), then I would probably start thinking your ISP is to blame.

Ooma users, is the toll free numbers blocked, I have magic jack and the toll free numbers are blocked. Especially when I want to connect to my work local conf call number (416/647), magicjack blocks the call. Need to know if it is the same with OOma

Thanks,

raghuprasad wrote: ↑ Ooma users, is the toll free numbers blocked, I have magic jack and the toll free numbers are blocked. Especially when I want to connect to my work local conf call number (416/647), magicjack blocks the call. Need to know if it is the same with OOma

Thanks,

They are not blocked. But you never know depending on the number

on sale at BB now for $99 with the wireless adapter

https://www-ssl.bestbuy.ca/en-ca/produc ... 9510.aspx?

Magicjack is cheaper.

Had ooma for 2 years and starting to experience problems. Can not make out going calls for almost 2 months. Tried to call/email their support department, every single time they told me to try again. I have a feeling they dont even know or want to investigate. Took a lot of emails/calls to get the issue escalate to a higher level.

+1 for ooma, had for over a year now and no issues. Just cancelled my premier service since we didnt really need it (although I'll miss the blacklist...) paying just 4.50 per month after tax now. Be warned however, most home security DOES NOT work with ooma, you will need to buy an internet based package which is usually +$10 more then landline security (at least from my provider)

In for 1, my current nettalk service expires in December but it might take months before my number gets ported over. For Ooma users who have already ported their number given my current service expires in early December when should I request the # porting from Ooma? Early September to be safe?

I am using voip service from talkit.ca for the past 6 years. No issues. It used to be $59/year..now $79/year

have this since MAY 2017. had issues with the connection for 1 month but after that everything works fine

Have had freephoneline for 2 years. Couldn't be happier with the service. The only thing that swayed me away from Ooma was that you had to pay $35 to specify how your caller ID looked to outgoing numbers. FYI.