|
|
| Author |
Message |
| 7 new of 122 responses total. |
dtk
|
|
response 116 of 122:
| 
Jan 13 01:19 UTC 2013 |
We do not bounce off a LEO bird; they move too much. Instead, we bounce
off of a geostationary bird. We set expectations about latency, and
people adapt pretty quickly to the latency, as long as it is
consistent. Jitter is your big killer, not delay. Oh, and SAA on Cisco
gear, or SmokePing on UNIX (or Linux) is absolutely your friend,
followed closely by any NetFlow analyzer you can cope with.
|
ball
|
|
response 117 of 122:
|
Jan 13 01:58 UTC 2013 |
I'll ask the packet pushers what SmokePing is.
|
dtk
|
|
response 118 of 122:
|
Jan 13 13:44 UTC 2013 |
http://oss.oetiker.ch/smokeping/
|
cross
|
|
response 119 of 122:
|
Jan 20 02:02 UTC 2013 |
resp:115 Latency is almost always an issue for satcom. Pushing on Ka or X
band to geo-sync/geo-stationary is going to be slow because, well, the speed
of light isn't just a good idea, it's the law. :-)
I've never had great luck with LEO for anything. Maybe DAMA voice, but I
don't recall what birds those were bitting.
|
dtk
|
|
response 120 of 122:
|
Jan 25 22:06 UTC 2013 |
Here here. GEOS is great for resilience, and as long as you can tolerate
delay, you can go anywhere in its shadow. That said, it takes people a
while to get used to the delays involved in a voice call, but as long as
the delay is pretty consistent (i.e. low jitter), people adapt.
Oh, and for the fans following along at home, remember that the speed of
light in the atmosphere is a lot slower than the speed of light in a
vacuum.
I never tried using a LEO-provider; having to track a bird that is in
motion relative to your frame of reference either requires the dish to
be in constant motion, or accept drop-offs frequently. Neither seems
like much fun, and not worth the small improvement in round-trip-time.
-DTK
|
cross
|
|
response 121 of 122:
|
Feb 9 18:18 UTC 2013 |
Indeed. It's a pain in the butt.
|
tod
|
|
response 122 of 122:
|
Jan 27 15:08 UTC 2017 |
re #114
Back in the stone ages, we used analog phones through a multiplexer over
VHF. VOIP is a very specific protocol overhead for packet node sites.
I haven't looked at Network44 in years, though.
|