Open marrold opened 3 years ago
It's a testament to how rare DMRA frames are that this has only just come up now. This has been in the code base for a little while, and I would imagine there are lots of people using this.
Most Talker Alias info is embedded inside of DMRD frames, so I'll have to go back and look at MMDVMHost to see how these frames are structured.
I've spent some time in the last week helping Jonathan with researching a few issues having to do with talker alias. I've also read over the ETSI spec regarding those particular data blocks. I'll have something to offer here in the weeks to come, perhaps before the end of March.
It's a testament to how rare DMRA frames are that this has only just come up now. This has been in the code base for a little while, and I would imagine there are lots of people using this.
Most Talker Alias info is embedded inside of DMRD frames, so I'll have to go back and look at MMDVMHost to see how these frames are structured.
Also, this isn't correct. DMRD really only contains the actual data from the DMR packet itself. link control and call setup info (where talker alias lives) is handled entirely using DMRA frames on Homebrew.
I do wish there was a written definition for the protocol that wasn't way out of date.
Hi,
I am using hblink in a bridged configuration and have noticed DMRA frames cause an exception in the logs:
Looking at the code, _rf_src is indeed referenced before assignment. A quick fix would be to just
pass
DMRA frames but it would be nice to extract the info I guess.Thanks Matthew 2E0SIP