<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Bob,</p>
<p>Getting gateway permission is easy, just an email requesting it.
Got a reply the next day saying approved.<br>
</p>
<p>I believe this is the JSON POST that is needed. (but i could be
wrong, I havent gone through all of them, but it matches what's on
BPQ's page)<br>
</p>
<p><a class="moz-txt-link-freetext" href="https://api.winlink.org/json/metadata?op=ChannelAdd">https://api.winlink.org/json/metadata?op=ChannelAdd</a></p>
<p>Reading through the winlink google group they don't provide api
keys to any 'Joe Blogs' .... only software developers.... and I'm
far from that.</p>
<p>Yes a simple curl with the correct JSON would work.</p>
<p><br>
</p>
<p>Andrew<br>
</p>
<div class="moz-cite-prefix">On 1/12/25 16:19, Boudewijn (Bob) Tenty
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:7a6faa65-26c2-43c8-a806-edcd188df6df@tenty.ca">I have
the feeling that it is a json script what is send (embedded in the
usual http exchange format) as that is used in rmsgw to list the
call, ports, password, etc.,
<br>
also the software release and version are exchanged. The server
and port what they use to exchange this information is:
api.winlink.org, port 80.
<br>
<br>
Above is the correct server / port to exchange this as G8BPQ's
examples lists two different host names and ports at the
WL2KREPORT line of bpq32.cfg at different pages,
<br>
<br>
one is an old one what was in use before as it seems, as I can't
connect to it. Hopefully this information exchange will be
embedded in jnos eventually as it is not only that
<br>
<br>
you are not at the list at the Winlink website, but they may block
your access after a while if you are not registered as a Gateway.
I did set up a lot of these servers and it did happen
<br>
<br>
to me a couple of months ago and that was the first time that they
did block me. Winlink is becoming more strict with this if they
feel you are Gateway in my opinion.
<br>
<br>
73,
<br>
<br>
Boudewijn (Bob) VE3TOK
<br>
<br>
<br>
<br>
<br>
<br>
<br>
On 1/12/25 10:19, Andrew - K1YMI wrote:
<br>
<blockquote type="cite">
<br>
Hay Maiko,
<br>
<br>
So in order to stay listed as an available RMS gateway you
need to report home (every 30 mins possibly). If you don't send
the updates you never appear on the list that you get on Winlink
express, PAT etc that shows you the nearest gateway to your
location.
<br>
<br>
Click on "RMS List" and then select "packet" here -
<a class="moz-txt-link-freetext" href="https://www.winlink.org/RMSChannels">https://www.winlink.org/RMSChannels</a> and you'll see the list I am
talking about.
<br>
<br>
G8BPQ has a nice primer here -
<a class="moz-txt-link-freetext" href="https://www.cantab.net/users/john.wiseman/Documents/WL2KReporting.html">https://www.cantab.net/users/john.wiseman/Documents/WL2KReporting.html</a>
<br>
<br>
There's an example here with this project <a class="moz-txt-link-rfc2396E" href="https://github.com/nwdigitalradio/rmsgw"><
https://github.com/nwdigitalradio/rmsgw ></a> that has some
scripts that run every 30 mins to update winlink.org. (rmsgw_aci
& 'updatesysop.py)
<br>
<br>
But basically there's a blob of data sent to api.winlink.org
every x mins that includes "Callsign, Locator, Hours, Freq,
Mode, Power, Ant Height, Ant Gain, Ant Direction"
<br>
<br>
If you are not changing modes and frequencies... this sounds
like a simple script run by an AT command or even just a
cronjob. But I am probably over simplifying things.
<br>
<br>
<br>
Andrew
<br>
<br>
<br>
On 1/12/25 08:48, <a class="moz-txt-link-abbreviated" href="mailto:maiko@pcsinternet.ca">maiko@pcsinternet.ca</a> wrote:
<br>
<blockquote type="cite">Hey Andrew,
<br>
<br>
<blockquote type="cite">How do you set the gateway frequency
advertised to winlink?
<br>
</blockquote>
<br>
What do you mean ? Can you be more specific please.
<br>
<br>
Maiko
<br>
<br>
_______________________________________________
<br>
nos-bbs mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org">http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org</a>
<br>
</blockquote>
<br>
_______________________________________________
<br>
nos-bbs mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:nos-bbs@lists.tapr.org">nos-bbs@lists.tapr.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org">http://lists.tapr.org/mailman/listinfo/nos-bbs_lists.tapr.org</a>
<br>
</blockquote>
<br>
</blockquote>
</body>
</html>