SMS to APRS

[John Spoonhower]

I have a fill-in APRX digipeater that is working well. Additionally, I am attempting to enable transmission of packets that originate from APRS-IS to RF. Specifically I want to enable use of SMS Gateway for a few individual users. With the aprx.conf configuration below I can successfully get packets sent from APRS RF to SMS, but I cannot do the reverse. That is, messages that originate from SMS through SMSGTE do not get RF transmitted. I see these SMS---> APRS packets as received in the APRX logfile but they do not get transmitted over RF. The aprx.conf looks like this when I am trying this for my own portable NX2I-7:

mycall  NX2I-11

myloc lat 2852.69N lon 08200.62W

<aprsis>
   passcode XXXX
   server   noam.aprs2.net
   filter "m/150"    # My-Range filter: positions within 150 km from my location
</aprsis>

<logging>
   pidfile /var/run/aprx.pid
   rflog /var/log/aprx/aprx-rf.log
   aprxlog /var/log/aprx/aprx.log
</logging>

<interface>
   ax25-device   $mycall
   tx-ok true
</interface>

<beacon>
beaconmode both
cycle-size  30m
beacon via WIDE2-1 \
symbol "I#" \
$myloc \
comment "Igate/Fill-in Digi in The Villages, Fl"   
</beacon>

<digipeater>
  transmitter     $mycall
    <source>
      source         $mycall
      relay-type    digipeated # default mode is "digipeated"
      viscous-delay  0     # no viscous delay for RF->RF digipeating
    </source>
    <source>                # APRSIS source adds a TX-IGATE behaviour
      source        APRSIS
      relay-type    third-party  # Must define this for APRSIS source!
      via-path    WIDE2-1
      msg-path    WIDE2-1
      filter     b/NX2I-7                              #Gate internet station to RF within 50km
      viscous-delay  5    # Recommendation: 5 seconds delay to give
    </source>
</digipeater>

What am I missing?

thanks and 73, John, NX2I

[LAPADU-HARGUES Matthieu (GMAIL)]

Hi,

I think you should have a look to the "b/" filter. It look too restrictive.

I will look more when I will have time :)

73 de F4ACU

Matthieu 

--
You received this message because you are subscribed to the Google Groups "Aprx software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aprx-softwar...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/aprx-software/3167780f-a043-4f59-b4d9-578ff78cb05e%40googlegroups.com.

[Eric]

Not sure if I don't know what I'm doing...but here goes anyway.

My understanding is that the b filter matches the source addresses.

Is the b filter checking the source address,finding SMSGTE and rejecting it?

Eric

[LAPADU-HARGUES Matthieu (GMAIL)]

Hi,

I agree with Eric.

Looking the APRS filter guide up (http://www.aprs-is.net/downloads/javaprssrvr/FilterUsersGuide.pdf), we can confirm "b" filter is to restrict packets from exact call NX2I-7.

Is it really the callsign from SMSGTE source ? I have a doubt because of -7 SSID standardly used for handheld radio.

Maybe should you try first without any filter ?

After a comparison with my own Tx-Rx digipeater's configuration file, I found nothing else.

73 de F4ACU

Matthieu

--
You received this message because you are subscribed to the Google Groups "Aprx software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aprx-softwar...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/aprx-software/29bab13e-82c7-760d-80f9-dfd896de8724%40gmail.com.

[Eric]

Unless I've missed a way for aprx or aprs-is to directly do what you
want, I'm going to suggest what could possibly be a very much grossly
over complicated process. It's late (1:30am) and I don't have any
coffee, so forgive me if this is wrong.





From what I can tell, the aprs-is will send sms originated messages for
a ham callsign-ssid to any igate that has recently reported that it has
received that callsign-ssid via RF.

So.....
What happens if you let the aprs-is send the all the sms originated
messages that would normally be sent to your igate and then use a regex
filter within aprx to filter out what you don't want to be gated to RF?

Unfortunately aprx appears to use regular expressions only as a reject
filter. Building a regular expression to match a set of strings is
easy. In this case you need to build a regular expression that matches
everything except an exact set of strings to create what would be a
double negative......and "match everything except a specific set of
strings" can get a bit messy.



If the regular expression stuff in aprx is complete enough, replacing
the line

filter b/NX2I-7

with

regex-filter destination ^(?!FRIEND1-|FRIEND2-|FRIEND3-|FRIEND4-).*$

*MIGHT* possibly work. Note there is a dot between ) and *$ and there
are no spaces between the ^ and the $ characters.

I don't think this expression is perfect as I believe it would allow any
destination with FRIEND1- or FRIEND2-, in it (such as FRIEND1-494 or
FRIEND3-ABCDEF) to be gated to RF. Fixing this would require a lot more
coffee. :-)

The strings that aprs-is would allow to be presented to your filter are
probably constrained enough so that this excess matching would not be a
big problem.

When the - character is included in the string, but the SSID is left
off, the filter would allow a message to any SSID attached to your
friend's callsign to be gated to RF. So, perhaps the bug might actually
be a feature. :-)




Hopefully there is an easier way to do this and I've just missed it.

Eric

[John Spoonhower]

Thank you to all that replied. This is just a quick update. I have tested the suggestion to eliminate the line " filter     b/NX2I-7 " from the aprx configuration file. This seemed to have no effect. To clarify, the RF packets are still digipeated as usual. Packets sent from RF to SMSGTE are both digipeated over RF and APRS-IS; the APRS-IS packets are received at SMSGTE and ack back to my Igate. I see these APRS-IS packets as received in the log. These are still not transmitted to RF, back to the originating station NX2I-7. I can experiment later with the idea of adding a REGEX filter.

73, John, NX2I

[John Spoonhower]

Let's simplify the problem (I think). Shown below is the digipeater section of my aprx.conf file. It does NOT cause any APRS-IS (internet) packets to get transmitted. How do I get transmission over RF of APRS-IS packets to happen?

73, NX2I

<digipeater>
  transmitter      $mycall
  <source>
    source         $mycall
    relay-type     digipeated

    viscous-delay  0

  </source>
  <source>                # APRSIS source adds a TX-IGATE behaviour
    source        APRSIS
    relay-type    third-party  # Must define this for APRSIS source!
    via-path    WIDE2-1
    msg-path    WIDE2-1

    viscous-delay  5
  </source>
</digipeater>

[VZW engr]

Is another station transmitting the packet within the 5 second viscous delay? 

A minute worth of rf log file either side of reception of an aprsis packet might show something.

[John Spoonhower]

I don't think so. To simplify further I set the viscous-delay to 0 for both sections of the digipeater section of aprx.conf.

Here is some log file output:

2019-12-02 15:59:28.150 NX2I-11   R N2MJP-9>RW5V4W,NI4CE-11*,WIDE1*,WC4PEM-14*,K4OZS-10*,WIDE2*:`n<}qp`>/"4'}
2019-12-02 15:59:34.744 NX2I-11   R WC4PEM-14>APMI06,K4OZS-10*,WIDE2-1:@021600z2815.27N/08139.28W_326/010g013t061r000p007P007h65b10155
2019-12-02 15:59:34.744 NX2I-11   T WC4PEM-14>APMI06,K4OZS-10*,NX2I-11*,WIDE2*:@021600z2815.27N/08139.28W_326/010g013t061r000p007P007h65b10155
2019-12-02 15:59:37.556 NX2I-11   R WE5MAG-14>RX4P8W,N4FLA-3*,WIDE2-1:`mO]q]A>/`"4*}146.520MHz_%
2019-12-02 15:59:37.557 NX2I-11   T WE5MAG-14>RX4P8W,N4FLA-3*,NX2I-11*,WIDE2*:`mO]q]A>/`"4*}146.520MHz_%<0x0d>
2019-12-02 16:00:12.613 NX2I-11   d *KG4YZY-1>APRS,TCPIP,KG4YZY-10*:@021600z2815.52N/08241.27W_302/010g016t060r000p008P007b10177h59.WD 31
2019-12-02 16:00:17.872 APRSIS    R W4HEM-14>APN391,WIDE2-2,qAR,WC4PEM-10:!2717.73N/08122.05W_/LAKE PLACID, FL WX STATION
2019-12-02 16:00:23.610 APRSIS    R WC4PEM-13>APN391,WIDE2-2,qAR,WC4PEM-10:!2747.25NS08119.66W_PHG74616/W3,FLn Indian Lake Estates, Florida
2019-12-02 16:00:25.912 NX2I-11   R WC4PEM-13>APN391,WC4PEM-14*,K4OZS-10*,WIDE2*:!2747.25NS08119.66W_PHG74616/W3,FLn Indian Lake Estates, Florida
2019-12-02 16:00:34.092 NX2I-11   R WC4PEM-12>APN391,WC4PEM-14*,K4OZS-10*,WIDE2*:!2745.40NS08134.12W_PHG73676/W3,FLn Frostproof, Florida
2019-12-02 16:00:34.996 APRSIS    R WC4PEM-7>APN391,WC4PEM-11*,WIDE2-1,qAR,WC4PEM-10:!2754.60NS08159.53W_PHG73266/W3,FLn Mulberry, Florida
2019-12-02 16:00:35.861 APRSIS    R WC4PEM-15>BEACON,qAR,KQ4KX:;146.985_D*111111z2800.58N/08135.97Wr146.985MHz C127 - R40m
2019-12-02 16:00:36.407 APRSIS    R WC4PEM-15>APN391,WIDE2-2,qAR,KQ4KX:!2800.58NS08135.97W_PHG74616/W3,FLn Dundee, Florida
2019-12-02 16:00:38.127 NX2I-11   R WC4PEM-15>APN391,WC4PEM-14*,K4OZS-10*,WIDE2*:!2800.58NS08135.97W_PHG74616/W3,FLn Dundee, Florida
^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A^[[A2019-12-02 16:00:40.159 NX2I-11   R WE5MAG-14>RX4P4R,N4FLA-3*,WIDE2-1:`mO/nSj>/`"4/}146.520MHz_%
2019-12-02 16:00:40.171 NX2I-11   T WE5MAG-14>RX4P4R,N4FLA-3*,NX2I-11*,WIDE2*:`mO/nSj>/`"4/}146.520MHz_%<0x0d>
2019-12-02 16:00:43.522 NX2I-11   R WC4PEM-8>APN391,WC4PEM-14*,K4OZS-10*,WIDE2*:!2809.81NS08200.83W_PHG73266/W3,FLn Kathleen, Florida
2019-12-02 16:00:53.684 NX2I-11   R K4OZS-10>BEACON:;146.610- *111111z2910.68N/08209.54WrT123 R30m Net 7:30M Mg3rdTu
2019-12-02 16:00:59.965 APRSIS    R WC4PEM-10>APMI06,TCPIP*,qAC,FIFTH:{{I021601zU=16.5V,T=86.9F
2019-12-02 16:01:08.938 NX2I-11   R K4OZS-11>APRSWX,K4OZS-10*,WIDE1*,WIDE2-1:$ULTW00B000A8022252A327AA000E85E500010204014F03CA0000004A
2019-12-02 16:01:08.938 NX2I-11   T K4OZS-11>APRSWX,K4OZS-10*,WIDE1*,NX2I-11*,WIDE2*:$ULTW00B000A8022252A327AA000E85E500010204014F03CA0000004A<0x0d>

[LAPADU-HARGUES Matthieu (GMAIL)]

Hi ! 

Really strange !

Can you try to send a message from TCPIP APRS app (NX2I-10) to your radio NX2I-7 to check if a simple message is transmitted from APRS-IS to RF ?

73 de F4ACU

Matthieu 

--
You received this message because you are subscribed to the Google Groups "Aprx software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aprx-softwar...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/aprx-software/9b82c9ba-5f6f-4032-ba59-f129ad06dd55%40googlegroups.com.

[John Spoonhower]

Sometime tomorrow I hope to be able to devote some additional time to testing. I am setting up a different  APRS station, different from my original tests. I  was using APRSDroid on a smartphone interfaced with mobilinkd to a handheld radio. I am not confident about the smartphone radio combination, even though on the SMS Gateway website there is mention of it's having been tested. More later,

NX2I

To unsubscribe from this group and stop receiving emails from it, send an email to aprx-s...@googlegroups.com.

[Jason Buchanan]

Did NX2I-11 receive a packet from NX2I-7 before you sent a message from NX2I-10 to NX2I-7?

APRX won't blindly TX a packet to a radio that it hasn't directly received a packet from within the last hour, or since aprx was started.  If you restart aprx to pick up a config change, send a packet from NX2I-7 (beacon, status, etc.) to populate NX2I-11's cache of recent stations so that it will send messages from TCPIP/APRSIS (NX2I-10) to the radio.

Doing this also populates the route to get messages sent to your aprx from the upstream APRSIS feed. 

If other TX gateways "hear" your radio they will send messages to your radio and you'll discover that your aprx station will hear those packets that your HT/mobile can't.  You may have to set viscous delay for aprsis to 0 to get around that.  For testing, reduce your HT/mobile's power output to lowest level, etc.

To unsubscribe from this group and stop receiving emails from it, send an email to aprx-softwar...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/aprx-software/5793de31-8aaf-462e-ae73-efdd5e32f70f%40googlegroups.com.

[John Spoonhower]

After a few days of testing I have come to the conclusion that the problem I have experienced is NOT an APRX problem, but rather  a problem of the messaging client. I build a second client aprs station (NX2I-4) using the same handheld and a combination of direwolf and YAAC. This system works well with SMSGTE thru APRX. I am not sure what the issue is with the original client station (NX2I-7); it used the same handheld radio but the TNC was a combination of smart phone/aprsdroid/mobilinkd that did not work for me. The SMSGTE website indicated that this tnc software was tested with the system, but I have not had good luck. Anyway, this appears to be an aprsdroid or mobilinkd problem, so I'll stop wasting time and bandwidth here. Thanks for the suggestions offered in this group.

73, NX2I

[LAPADU-HARGUES Matthieu (GMAIL)]

Hi John,

No, it is not a waste of time beaucause thinking about other's issues is a great opportunity to oneself understand.

Hope you will find in Aprsdroid or Mobilinkd areas :)

73 de F4ACU

Matthieu

--

You received this message because you are subscribed to the Google Groups "Aprx software" group.
To unsubscribe from this group and stop receiving emails from it, send an email to aprx-softwar...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/aprx-software/de5b1ead-c769-4a40-9d00-541caa16c521%40googlegroups.com.