I got a very strange behaver on DMO Gateway Call. Has this ever been testet in real.
The DMO gateway implementation only goes as far as to detect that it is a gateway.
This was to at least indicate the presence of it and to stop crashing when it saw it.
Most likely any call activity (call control) may not be correctly processed.
I was only given a small IQ sample of a DMO gateway beacon which looks like a CAP+ in rest mode.
There was not any call activity to be able to test further.
It is connected to a Gateway and gSSI says: 0 and never change.
Then when trafic is recevied. The GSSI and ISSI show some odd behaver.
GSSI stays with all call 16777215 and ISSI is show c for clear but has lots of wrong numbers.
My Radio show correct numbers. But SDR# has change ISSI to some other numbers.
The signal is not perfect. But I do not think that this is the problem. When signal is 100% it still shows wrong.
And some times the MCC and MNC change to 1023 and 16383 but the GSSI is only show all call 16777215.
I do not understand this and what is the gSSI small letter g under GATE ?
Has this gSSI somthing to to do with what the Gateway Radio has selected as TMO Talkgroup ?.
PS: Not using TTT with this and is Unselected. The Auto is enabled. Have also try to select Stronger Burst Detection and Audio Bandpass.
IQ sample I have also returns GATE: 0
The '16777215' may be a gateway address (DMO-MS to Gateway) like 16777184 is for E.184 phone gateway.
"GATE:" is the gateway address.
"gSSI:" is the Gateway SSI, but this may not be the correct usage.
More info can be seen in
EN 300-396-05 v1.3.1 - 14.1.2 DPRES-SYNC PDU (page 220)
- see element 'Usage restriction type (URT)'.
- see conditional element 'Addressing for URT' which depends on value of the above element.
I have not spent much time reading into the DMO gateway, so what I understand of it is limited.
Latest version (v1.7.1.0) can be found here: Release post