Ok, it shouldn't be too hard to update OP25 to support TSBK opcodes $30 and
$38, but $14 is still a mystery... Please see the attached spreadsheet for
a list of opcodes that we currently know about. If you have any info on any
of the manufacturer specific opcodes, please feel free to let us know.

0x30 is a Harris Dynamic regrouping command:-

[image: image.png]

0x38 is a standard authentication response:-

[image: image.png]

I'll see how we can go about getting these added in. I'm not sure what the
best approach would be to reduce noise in the logs however - any ideas Max?

Credit for the attached spreadsheet goes to Ellie Dugger (thnx Ellie!)

Cheers,
Matt


On Sat, 21 Jan 2023 at 12:41, Kevin Utzy <krutz...@gmail.com> wrote:

> Matt,
>
>
>
> Yes it is as a matter of fact it is.
>
>
>
> Kevin
>
>
>
> *From:* Matt Ames <matt.ames...@gmail.com>
> *Sent:* Friday, January 20, 2023 20:24
> *To:* krutz...@gmail.com
> *Cc:* op25-dev@lists.osmocom.org
> *Subject:* Re: [op25-dev] Unsupported TSBK opcodes
>
>
>
> Hi Kevin,
>
>
>
> Is this by chance a Harris system that you are monitoring?
>
> Cheers,
> Matt
>
>
>
>
>
> On Thu, 19 Jan 2023 at 10:36, <krutz...@gmail.com> wrote:
>
> Minor request.
>
> It multi_rx.py it is difficult to find other issues because of messages
> regarding unsupported TSBK opcodes.  It isn't hurting but just filling the
> log.  Not sure how best to report these (increase the log level?).
>
> Examples in my case are as below:
> received unsupported TSBK opcode 30 (b00000040000000033200000)
> received unsupported TSBK opcode 38 (b800080c2e000c2e00010000)
> received unsupported TSBK opcode 14 (9400000165ffff3125d70000)
>
> I understand the need to know about these but it isn't helpful to have the
> log filling up with these.
>
> Kevin
>
>

Attachment: TSBK_Reference_2021-05-08_1.xlsx
Description: MS-Excel 2007 spreadsheet

Reply via email to