Callsign lookup fails when the callsign contains a "/" character
ctjacobs opened this issue · 1 comments
ctjacobs commented
Callsigns that contain "/" characters are not handled properly when performing callsign lookups. Callsigns may need to be stripped of any suffix (e.g. "/M") and/or prefix before performing a callsign lookup.
This bug was reported by Paride Legovini.