search

LX3JL / xlxd

HAM radio multiprotocol dstar reflector server
GNU General Public License v3.0
163 stars 111 forks source link

Attempt to extract callsign from 10 char YSF frames. When YSF header… #199

Closed nostar closed 1 year ago

nostar commented 2 years ago

Attempt to extract callsign from 10 char YSF frames. When YSF headers are missed (late entries), extract callsign from one of the VD2 frames. If no DMR ID can be found after all of these attempts, use an optional default DMR ID, defined in main.h. Also append a main.h defined module char on RPTR1 when no char exists in REF mode. This is the case for OpenSpot 1 users that can not assign a module char to their RPTR1 when in REF mode. DPlus reflectors allow RPTR1 callsings with no module char, but stock xlxd does not.

K2IE commented 2 years ago

The ability to set a default ID to something other than 0 is useful. I was using this prior to the IMRS release. It would be great if this could be refactored into the current codebase.

K2IE commented 2 years ago

Could this be the fix to the following issue that I reported on the BBS?

https://xlxbbs.epf.lu/viewtopic.php?f=7&t=590

It seems like xlxd 2.5.0 does something to break compatibility with HBlink.
The audio is always passed, but if the transmission originates from YSF
HBlink never logs the start of the stream nor the bridged call. This worked
properly in the prior xlxd version.

If I transmit from D* or DMR via xlxd, everything goes over to HBlink as before
and the logging looks good on the HBlink side.

If I transmit from YSF via xlxd, the audio is passed but HBlink never logs the
start of the stream. It does the log the end of the stream.

I wonder if there is some data normally present in the DMR stream that is not
inserted if the call originates from YSF.

Any other xlxd/HBlink users seeing this?