Skip to content
This repository has been archived by the owner on Mar 11, 2024. It is now read-only.

Not a valid Callsign #16

Open
vetsin opened this issue May 6, 2017 · 0 comments
Open

Not a valid Callsign #16

vetsin opened this issue May 6, 2017 · 0 comments

Comments

@vetsin
Copy link

vetsin commented May 6, 2017

New to APRS and trying to decipher the format, but the following is throwing exceptions (picked up via r/33/-97/200 t/p:

     def test_weird_frame(self):
         frame = 'DL0II>APRS,TCPIP*,qAC,T2MAZURY:=5115.19N/00658.49E&www.r09.de APRS iGate'
         aprs_frame = aprs.Frame(frame)

With the trace:

======================================================================
ERROR: test_weird_frame (tests.test_aprsframe.FrameTestCase)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/vetsin/Projects/aprs/tests/test_aprsframe.py", line 103, in test_weird_frame
    aprs_frame = aprs.Frame(frame)
  File "/home/vetsin/Projects/aprs/aprs/classes.py", line 87, in __init__
    self.parse()
  File "/home/vetsin/Projects/aprs/aprs/classes.py", line 120, in parse
    self.parse_text()
  File "/home/vetsin/Projects/aprs/aprs/classes.py", line 142, in parse_text
    self.path.append(Callsign(path))
  File "/home/vetsin/Projects/aprs/aprs/classes.py", line 258, in __init__
    self.parse(callsign)
  File "/home/vetsin/Projects/aprs/aprs/classes.py", line 293, in parse
    self.callsign.encode('hex'))
BadCallsignError: ('Could not extract callsign from %s', '54324d415a555259')

----------------------------------------------------------------------

Far as I understand the protocol thus far station DL0II received a verified qAC from an 'invalid' callsign. Are we okay with not validating >= 3x2, 3x3 callsigns?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant