I was just noticing that James said that if you don't see the "DSL/Cable IP Address" Your Ooma device isn't in the DMZ.horsecore wrote:thunderbird wrote:horsecore:
8. The IP address listed (In you Ooma device “Status” page under modem) should change from 192.168.x.x to your DSL/Cable IP Address. If it stayed at 192.168.x.x, go back to step 3. It might take a few times for your (Ooma device) router to pickup the correct IP.
9. Once your Ooma device) router has the external IP, everything is configured correctly.
Even if your (Ooma device) router has the 192.168.x.x the router still appears to be in DMZ however, most obscure-protocols (GRE,IPv6) still will not work. The router must have the external IP as its IP address for everything to work correctly.
Thanks,
James Hartig
What thread is Ooma referring to? - audio delay fix (?)
-
- Posts:6388
- Joined:Mon Nov 08, 2010 4:41 pm
Re: What thread is Ooma referring to? - audio delay fix (?)
Your post inspired me to test my delay again:horsecore wrote:When I call the 909-390-0003 test number and say 'hello,' I don't hear the return 'hello' until I've completed saying hello and even some time beyond that (I don't have a mic to measure the total delay).
In crude visual terms:
Start: Hello
Return:......Hello
When I call the 925-259-0082 test number and say hello, my return hello starts between the 'llo' portion of me saying hello...if that makes sense.
Again, in crude visual terms:
Start: Hello
Return:...Hello
909-390-0003 measures 700 ms and 925-259-0082 measures 240 ms.
I'm in southern CA with a 22 ms ping to www3.ooma.com.
In my previous post above I found that consecutive calls to 909-390-0003 yielded random delay measurements reduced almost in half. This seems to point to the possibility that some telco gateways at Ooma are better than others and for some reason Thunderbird always gets the better telco gateways.
I believe 700 ms less 240 ms is the telco gateway delay I'm seeing - because '0082 is internal at Ooma and does not go out onto the telco network like '0003 does. Ooma could randomly assign gateways or specifically assign them depending on the Ooma customer originating the call.
Bill
-
- Posts:6388
- Joined:Mon Nov 08, 2010 4:41 pm
Re: What thread is Ooma referring to? - audio delay fix (?)
Bill D:
If it were me, I would put the information that you just posted in an E-mail to Ooma Support.
I would politely point out that when testing within the Ooma phone system, the delay is much shorter that when testing to a phone number outside of the Ooma system.
909-390-0003 measures 700 ms and 925-259-0082 measures 240 ms
I would insist that this has to be a carrier routing problem.
I would politely E-mail Ooma everyday, even if Ooma Support doesn't respond, until someone corrects your problem.
If it were me, I would put the information that you just posted in an E-mail to Ooma Support.
I would politely point out that when testing within the Ooma phone system, the delay is much shorter that when testing to a phone number outside of the Ooma system.
909-390-0003 measures 700 ms and 925-259-0082 measures 240 ms
I would insist that this has to be a carrier routing problem.
I would politely E-mail Ooma everyday, even if Ooma Support doesn't respond, until someone corrects your problem.
Re: What thread is Ooma referring to? - audio delay fix (?)
Good advice. I'll try emailing them and see what they say. I also tried it with nothing on my network except my Hub and DSL modem, so I ruled out my LAN as the culprit.thunderbird wrote:909-390-0003 measures 700 ms and 925-259-0082 measures 240 ms
I would insist that this has to be a carrier routing problem.
I would politely E-mail Ooma everyday, even if Ooma Support doesn't respond, until someone corrects your problem.
Since you measure 180 ms on '0003, I'm curious what you measure on '0082. It should be less than 180 ms by the added gateway delay.
Bill
-
- Posts:6388
- Joined:Mon Nov 08, 2010 4:41 pm
Re: What thread is Ooma referring to? - audio delay fix (?)
Today:
I measure about 170 using 925-259-0082
I measure about 195 using 909-390-0003
I measure about 170 using 925-259-0082
I measure about 195 using 909-390-0003
Re: What thread is Ooma referring to? - audio delay fix (?)
Wow. 25 ms added by the gateway compared to my 460 ms added.thunderbird wrote:Today:
I measure about 170 using 925-259-0082
I measure about 195 using 909-390-0003
The difference in the internal loopback is also interesting 240 ms vs. 170 ms.
Bill
-
- Posts:6388
- Joined:Mon Nov 08, 2010 4:41 pm
Re: What thread is Ooma referring to? - audio delay fix (?)
I wonder where the 240 ms vs. 170 ms = 70 ms internal difference comes from?Bill D wrote:Wow. 25 ms added by the gateway compared to my 460 ms added.thunderbird wrote:Today:
I measure about 170 using 925-259-0082
I measure about 195 using 909-390-0003
The difference in the internal loopback is also interesting 240 ms vs. 170 ms.
Bill
Maybe your Internet provider, or your home's equipment, or even the Ooma home device?
When you are in California or Flordia, do you use the same modem, router, and ooma devices in both places?I'm experiencing the same delay trouble in Florida & California with 3 Hubs. My only difference is 25 ms ping in CA and 75 ms ping in FL.
Bill
Re: What thread is Ooma referring to? - audio delay fix (?)
I can't image how my Ooma Hub, home LAN or anything in my house would know even know the difference between those measurement calls.thunderbird wrote:I wonder where the 240 ms vs. 170 ms = 70 ms internal difference comes from?
Maybe your Internet provider, or your home's equipment, or even the Ooma home device?
The difference clearly occurs at the Ooma datacenter, unless I'm missing something.
I have one Hub here in California and two Hubs at my other house in Florida, all with similar delay issues. All were around 400 ms in Dec 2010 and then jumped to 700-800. I do not not have Premiere service on any of my Hubs. Do you have Premier service?
Bill
Re: What thread is Ooma referring to? - audio delay fix (?)
Thunderbird,
Sorry, I miss-read your question - so ignore my last response.
You asked about the 240 ms vs. 170 ms = 70 ms internal difference.
That's a good question. My ping to www3.ooma.com is 22 ms. What's yours?
Sorry, I miss-read your question - so ignore my last response.
You asked about the 240 ms vs. 170 ms = 70 ms internal difference.
That's a good question. My ping to www3.ooma.com is 22 ms. What's yours?
-
- Posts:6388
- Joined:Mon Nov 08, 2010 4:41 pm
Re: What thread is Ooma referring to? - audio delay fix (?)
4 packet Ping with 32 bites of data for www3.ooma.com = 163ms, 159ms, 169ms, 159ms.
Bill: you sure has a strange set of circumstances. It's hard to determine the common denominator for large delays in two locations, one on the west coast and one on the east coast.
Do you have the same brand and same model number modems and routers in each location?
What are the brand and model numbers of your modems and routers for each location.
You certainly wouldn't think that three Ooma devices would all be defective?
You wouldn't think that routing issues would be the problem for both locations?
Bill: you sure has a strange set of circumstances. It's hard to determine the common denominator for large delays in two locations, one on the west coast and one on the east coast.
Do you have the same brand and same model number modems and routers in each location?
What are the brand and model numbers of your modems and routers for each location.
You certainly wouldn't think that three Ooma devices would all be defective?
You wouldn't think that routing issues would be the problem for both locations?