--- In [email protected], "Y.Kawabe" <tiarad...@...> wrote: > > We found out gBest and Easy Wayh to reply from U.S. and EU, when you > received "CQ" Call from Japan via D-Star Gateway. > Just push "One-Touch Reply" button of your transceiver and capture the call > sign > Ex. > 2820 push [R>CS] > 91AD push [RX-CS] > However, this is an effective method only to the answer of the station in the > U.S. and EU to Japan. Please try once. > 73 de JF1TEU
This is a more detailed explanation of what Nate posted in a few lines. We don't know what they are doing in J-land to get their DV streams pointed at our gateways since we know nothing about their gateway system, but Pierre Thibaudeau explains how NU5D's RF observations and my database observations fit together with G2 on this end. I have been grabbing snapshots of the sync_mng table every five minutes. Here's an example of what's happening: target_cs | last_mod_time | mod_date | reg_date | pc_hostname | arearp_cs | zonerp_cs | user_cs | regist_rp_cs | pc_ipaddr | del_flg JF1CXH | 2009-01-31 14:17:32 | 2009-04-09 22:27:29.602372 | 2009-04-09 22:27:29.602372 | jf1cxh | WB4HRO A | WB4HRO | JF1CXH | WB4HRO | 10.220.193.144 | f JF1CXH | 2009-01-31 14:17:32 | 2009-04-09 22:27:29.602372 | 2009-04-09 22:27:29.602372 | jf1cxh | JP1YJX A | JP1YJX | JF1CXH | WB4HRO | 10.220.193.144 | f JF1CXH | 2009-01-31 14:17:32 | 2009-04-09 22:27:29.602372 | 2009-04-09 22:27:29.602372 | jf1cxh | JP1YJX A | JP1YJX | JF1CXH | WB4HRO | 10.220.193.144 | f JF1CXH | 2009-01-31 14:17:32 | 2009-04-09 22:27:29.602372 | 2009-04-09 22:27:29.602372 | jf1cxh | JP1YJX A | JP1YJX | JF1CXH | WB4HRO | 10.220.193.144 | f JF1CXH | 2009-01-31 14:17:32 | 2009-04-09 22:27:29.602372 | 2009-04-09 22:27:29.602372 | jf1cxh | JP1YJX A | JP1YJX | JF1CXH | WB4HRO | 10.220.193.144 | f JF1CXH | 2009-01-31 14:17:32 | 2009-04-09 23:07:51.048988 | 2009-04-09 23:07:51.048988 | jf1cxh | WB4HRO A | WB4HRO | JF1CXH | WB4HRO | 10.220.193.144 | f Follow reg_date (date time) and arearp_cs. Remember USROOT refreshes this table once or twice an hour. In the five minutes between the first and second observations JF1CXH sent a DV stream to our gateway which immediately updated the sync_mng table based on the callsigns in his header - this is a feature of G2 - an immediate update to the gateway receiving a DV stream so that gateway will know how to route a reply back. In the five minutes between the last two observations USROOT refreshed the table and put JF1CXH back to the WB4HRO A module because that's where USROOT has him at. Here's Pierre's detailed explanation: "When they call your repeater, your gateway's database gets updated on the spot. But unlike when you hit the PTT on your repeater, USROOT's database is not updated. Eventually, USROOT pushes back to all gateways (including your own) a fresh copy of the database in which JF1CXH is still known to be on WB4HRO A (the default for having registered on WB4HRO) because JP1YJX did not update to USROOT. Your gateway will update USROOT only for callsign heard locally, not for anything coming from another gateway (it is assumed that the other gateway will have done it already). On the other hand, your gateway knows me on VE2RIO A. If I relocate to Quebec City and call you from there, your gateway will immediately get my new location, say VE2RMF C. But at the same time VE2RMF will inform USROOT of my now current location which will eventually be pushed to all gateways that are synchronizing there. From that point on all gateways will know I'm there, until I relocate again." Thus, when a J-lander calls one of our G2 gateways, our gateway will know how to callsign (aka one-touch) route back to the J-lander until USROOT "updates" our database. In the example above, this was between 20 and 25 minutes. 73 -- John (and Pierre and Steve)
