Subject: Re: [44net] AMPRNET katency in VOIP connections ? From: "'Gustavo Ponza'" g.ponza@tin.it Date: 05/30/2016 07:12 PM
To: 44net@hamradio.ucsd.edu
On 05/30/2016 05:55 PM, Rob Janssen wrote:
(Please trim inclusions from previous messages) _______________________________________________
I don't know how they do the job... but as all of you can see, also iPAD/iPhone can do it by using my small ampr.org facility :)
73, gus
Which repeater is this log from? It is on an AMPRnet address?
It is from IR0AAB (ER-IR0AAB). It is on (or better, it should be on) 44.134.32.240/44.208.58.1
Ok but it registers on Echolink using IP address 79.47.199.234 So there is some NAT between its 44-address and internet!
This is no problem as long as the repeater always routes its traffic via that NAT, but in practice those operators often route 44-net traffic directly and then it does not work.
I have tried to connect it from my 44-address and indeed it fails! I connect to the node on address 79.47.199.234 as directed by the Echolink server, and I get replies from 44.134.32.240:
Spurious audio packet received from 44.134.32.240
So I cannot connect that repeater from AMPRnet.
Rob
I don't know how they do the job... but as all of you can see, also iPAD/iPhone can do it by using my small ampr.org facility :)
73, gus
Which repeater is this log from? It is on an AMPRnet address?
It is from IR0AAB (ER-IR0AAB). It is on (or better, it should be on) 44.134.32.240/44.208.58.1
Ok but it registers on Echolink using IP address 79.47.199.234 So there is some NAT between its 44-address and internet!
This is no problem as long as the repeater always routes its traffic via that NAT, but in practice those operators often route 44-net traffic directly and then it does not work.
I have tried to connect it from my 44-address and indeed it fails! I connect to the node on address 79.47.199.234 as directed by the Echolink server, and I get replies from 44.134.32.240:
Spurious audio packet received from 44.134.32.240
So I cannot connect that repeater from AMPRnet.
Rob
The fact is that, actually the repeater is networked to the EchoLink server and this can be obtained ONLY by using the commercial IP number, i.e. IP address 79.47.199.234.
Analyzing the log released from here:
Mon May 30 21:15:09 2016: Incoming EchoLink connection from PE1CHL (Rob) at 44.137.41.97 Mon May 30 21:15:09 2016: Switching to SPEEX audio codec for EchoLink Qso. Mon May 30 21:15:09 2016: SimplexLogic: Activating module EchoLink... Mon May 30 21:15:09 2016: PE1CHL: Accepting connection. EchoLink ID is 945451... Mon May 30 21:15:09 2016: PE1CHL: EchoLink QSO state changed to CONNECTED Mon May 30 21:15:09 2016: Tx1: Turning the transmitter ON Mon May 30 21:15:12 2016: PE1CHL: EchoLink QSO state changed to BYE_RECEIVED Mon May 30 21:15:12 2016: PE1CHL: EchoLink QSO state changed to DISCONNECTED Mon May 30 21:15:12 2016: SimplexLogic: Deactivating module EchoLink...
the incoming IP results 44.137.41.97; so I understand that the internet server act as the real gateway in a similar way as our ampr.org gateways. It function very OK!
73, gus
-
'Gustavo Ponza' -
Rob Janssen