Just a further tip from my side: the RemoteRig RRC allows ToS tagging.
It is entered in the advanced settings under "IP Type-of-Service (dec)".
The manual refers to RFC791 that use this in QoS networks and support
this function. Entries must be made in decimal.
Unfortunately, I have found no "home" routers so far (at least here in
DL) that support QoS tags. However, this will for sure help those that
do have routers supporting QoS.
73,
Mitch DJ0QN
Mitch Wolfson
DJØQN / K7DX
Neubiberger Str. 21, 85640 Putzbrunn
Skype: mitchwo - Home:+49 89 32152700 - Mobile:+49 172 8374436
Echolink: 3001 - IRLP: 5378
On 18.07.2014 11:22, David Woolley wrote:
It is standard to use UDP (RTP) over VoIP for the reasons given by
Iain. Over a corporate network, VoIP traffic should have a QoS
tagging on the IP packets which causes routers to prioritise it. VoIP
over the internet has always been done for cost, not quality reasons,
as the whole concept behind IP networks is at conflict with constant
rate traffic; the telephone industry devised ATM as a packet network
for that application (although they are now moving to IP, because
voice is no longer the dominant bandwidth user - but I am sure they
will prioritise their voice traffic).
RTP has a marker bit which indicates a safe place to dump a latency
buffer's contents. Conceivably setting this during tuning would be a
good idea. If the remote operation protocol doesn't user RTP, someone
has been re-inventing the wheel.
As someone mentioned WiFi. It is generally accepted, in the VoIP
world, that WiFi and VoIP don't mix because WiFi introduces additional
latency. I believe it also does link level retransmission which,
means latency can be particularly bad if you don't have ideal conditions.
______________________________________________________________
Elecraft mailing list
Home: http://mailman.qth.net/mailman/listinfo/elecraft
Help: http://mailman.qth.net/mmfaq.htm
Post: mailto:[email protected]
This list hosted by: http://www.qsl.net
Please help support this email list: http://www.qsl.net/donate.html
Message delivered to [email protected]
