Author Topic: Private Call Bug Report  (Read 25 times)

0 Members and 0 Guests are viewing this topic.

Offline N3DG

  • Newbie
  • *
  • Posts: 1
  • Referrals: 0
Private Call Bug Report
« on: November 29, 2022, 08:36:21 pm »
I don't know if there's a github for the TGIF servers or not, but I found a minor bug in the encoding of private messages returning from the service (parrot for example).

This is an example of a DMR Header on a parrot call I made today.

00000011 00000000 00000000 00000000 00100111 00000110 00110000 10101001 01000000

Breaking this down for the DMR Header standard:
0 - Protect Flag
0 - Reserved
000011 - Full Link Control Opcode (0x000011 for Private Call)
000000 - Feature Set ID
000000 - Service Options
00000000 00100111 00000110 - Target Address (9990)
00110000 10101001 01000000 - Source Address (3189056 [yes that's my real one, idc, it's publicly accessible already])

The Response header is:
00000001 00000000 00000000 00110000 10101001 01000000 00000000 00100111 00000110

0 - Protect Flag
0 - Reserved
000001 - Full Link Control Opcode (0x000011 for Private Call)
000000 - Feature Set ID
000000 - Service Options
00110000 10101001 01000000 - Target Address (3189056)
00000000 00100111 00000110 - Source Address (9990)

As you can see the FLCO in the response is 0x000001 instead of the proper 0x000011, which isn't a BIG deal for MMDVM, but it is throwing this error:
'DMR Slot 2, DMRD header doesn't match the DMR RF header: 9990->3189056 9990->3189056'

Share on Facebook Share on Twitter


 

Related Topics

  Subject / Started by Replies Last post
1 Replies
125 Views
Last post February 04, 2019, 12:53:47 am
by ke5cdk
2 Replies
200 Views
Last post January 27, 2020, 01:08:41 pm
by G0AMO Mike
0 Replies
1296 Views
Last post April 20, 2020, 10:40:54 am
by k7cet
1 Replies
201 Views
Last post July 03, 2020, 06:32:45 am
by KY4WIN
1 Replies
216 Views
Last post January 15, 2022, 07:25:19 pm
by n9mfk