Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement more verbose call_progress labels #92

Open
griffonboi opened this issue Jan 24, 2024 · 1 comment
Open

Implement more verbose call_progress labels #92

griffonboi opened this issue Jan 24, 2024 · 1 comment

Comments

@griffonboi
Copy link

Add some helpful information about voice call status. The 7th SU octet contains information about the beam and what is happening in general with the voice call.

Example call_progress SU labels to add:
0x30 0x78 0x0E 0xAB 0x82 0xD0 [0xE1] 0x00 0x04 0x00
0xE1 - Call_status -2db EIRP adjustment
(first four bits denote beam adjustment power)
(0 - none, 1,2,3 - +1,+2,+3 db respectively & D,E,F - -3,-2,-1 db respectively)

0x30 0x78 0x0C 0xAC 0x50 0xD0 [0x02] 0x00 0x00 0x00
0x02 - Call_connect

0x03 - Call_test

0x04 - Call_report (can also add class & cause values from pg 264-265 of the AMSS doc)

0x30 0x71 0xBE 0x34 0x50 0xD2 [0x05] 0x10 0x03 0x00
0x05 - Call_release

Could also add info from the 6th octet. First four bits mean:
D - General, E - Urgent, F - Distress

Last four bits mean app. id and can show which party initiated the call.
0-7 - Aircraft calling ground
8-F - Ground calling aircraft

Full example label when decoding the voice SUs could then be something like this:
0x30 0x7C 0x6B 0xC3 0x50 0xDB 0xE1 0x05 0x38 0x00 AES = 7C6BC3 GES = 50
General Call_status from ground -2db EIRP adjustment

@CasualArclamp
Copy link

This would be a great addition

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants