Tetra decoding

[bilbolodz]

i've added a minor tweak to the install_telive.sh script to allow installation under raspbian 8

It's also working with Ubuntu 16.04 but you have to change "ubuntu 15" to "ubuntu 16"

 

[sq5bpf]

It's also working with Ubuntu 16.04 but you have to change "ubuntu 15" to "ubuntu 16"

thanks, added it to the install script.

so far there is support for debian 8, raspbian 8, mint 17.2 and 17.3 (not sure about 17.1), ubuntu 14, 15 and 16

 

[bilbolodz]

Actually I've noticed strange behavior on Debian decoding with "remote RTL stick" (rtl_tcp) is NOT working (signal lost/signal found on telive, out of buffer space on rtl side). The same setup on Ubuntu 16.04 is working fine.

 

[sq5bpf]

Actually I've noticed strange behavior on Debian decoding with "remote RTL stick" (rtl_tcp) is NOT working (signal lost/signal found on telive, out of buffer space on rtl side). The same setup on Ubuntu 16.04 is working fine.

you probably need to tweak some buffer sizes.

also try to see if this isn't a network issue, especially if wifi is involved.

 

[bilbolodz]

you probably need to tweak some buffer sizes.
also try to see if this isn't a network issue, especially if wifi is involved.

It's only "distro depended", the same hardware and network setup, only difference Ubuntu 16.04 vs Debian

 

[sq5bpf]

It's only "distro depended", the same hardware and network setup, only difference Ubuntu 16.04 vs Debian

the issues are either with gnuradio (different version, so maybe different buffer sizes etc) or with the network stack. for example there might be a different wifi driver causing more packet drops, and these will cause tcp retransmissions etc (use a sniffer to check).

 

[bilbolodz]

the issues are either with gnuradio (different version, so maybe different buffer sizes etc) or with the network stack. for example there might be a different wifi driver causing more packet drops, and these will cause tcp retransmissions etc (use a sniffer to check).

I agree that's probably gnuradio issue. For sure not WiFi (using LAN connection) ;-)

 

[sq5bpf]

I agree that's probably gnuradio issue. For sure not WiFi (using LAN connection) ;-)

you can try to use gnuradio 3.7.9 packages from debian jessie backports, maybe that will be better

btw are you using udp or named pipes between gnuradio and receiver1* ?

 

[bilbolodz]

I've replaced my old Debian setup with Ubuntu but I will try to look for a backup (I should have one). I'm using UDP.

 

[M6UEX]

I've read all 69 pages of this thread, thank you goes to sq5bpf for all of your hard work!!

Currently been using the bootable version of Telive, and have found a few private Tetra networks I otherwise wouldn't of known existed. I've installed Ubuntu 15.10 on my laptop, but with no Linux experience I kinda failed pretty early on in the install of Telive.. Will call on a few guys from my local club to help!

I can confirm that number displayed below the user(s) ISSI in the usage identifier when on a clear network is the GSSI. I think I remember reading earlier in the thread people weren't sure which was the group ID.

 

[sq5bpf]

I can confirm that number displayed below the user(s) ISSI in the usage identifier when on a clear network is the GSSI. I think I remember reading earlier in the thread people weren't sure which was the group ID.

that really depends on the order in which the signalling info arrives, and also only 3 SSIs are remembered, so if there is a group call, and more than 2 ISSIs use it, then one ssi has to be forgotten and the list gets "shifted"

btw was this on tetra equipment which you own (or control)? if so, then you can try different scenarios (group calls, individual etc). i'd also be interested in the results

 

[tripadvisor]

Hello, just wondering if it is possible to get ISSI and GSSI info from encrypted network, I don't need voice traffic, only groups. Thanks.

 

[M6UEX]

Good to know, thank you.

It's on a network I have occasional access to, unfortunately the private (individual) call function has been disabled. I'm happy to try a few things when I'm next at the site though.

 

[racingfan360]

that really depends on the order in which the signalling info arrives, and also only 3 SSIs are remembered, so if there is a group call, and more than 2 ISSIs use it, then one ssi has to be forgotten and the list gets "shifted"

btw was this on tetra equipment which you own (or control)? if so, then you can try different scenarios (group calls, individual etc). i'd also be interested in the results

I rarely get to monitor TETRA networks in the clear: on one major network I monitored last year, I know there were several Groups and Users operating. But the filenames of the recordings made by Telive didn't appear to make much sense. Is this expected behavior, or should I have expected one of the SSI names in the .ogg filename to have been the correct GSSI, or will SSI1, 2 and 3 in the filename likely to be be a mix of ISSI and GSSI?

 

[passie101]

Is it possible to add the 3 played id's ( (G)ISSI ) that are showed in the telive screen under the PLAYED message to the logfile ?
So is is easier to filter them out, for external use.

 

[bilbolodz]

Maybe it could be a good idea to implement external xrpc server driving e.x. codding program and make Telive to report current (G)ISSI to it. I've thought about implementing online (private) streaming from telive and icecast/ices2 (with dynamic stream description) but my "favorite tetra network in my city" turned encryption on so there is no need for it anymore :-(

 

[sq5bpf]

Is this expected behavior, or should I have expected one of the SSI names in the .ogg filename to have been the correct GSSI, or will SSI1, 2 and 3 in the filename likely to be be a mix of ISSI and GSSI?

they will be a mix of issi and gssi. if there are only 2 radios talking in this group, then often there is an order (usually it's: calling issi _ gssi _ responding issi), but that depends on a lot of things (and is invalid for a lot of networks).

you can still find out the gssis, just listen to a few days worth of recordings, while looking at the file names.

btw i've planned to distinguish between issis and gssis in the next major version (whenever it comes)

 

[sq5bpf]

Maybe it could be a good idea to implement external xrpc server driving e.x. codding program and make Telive to report current (G)ISSI to it. I've thought about implementing online (private) streaming from telive and icecast/ices2 (with dynamic stream description) but my "favorite tetra network in my city" turned encryption on so there is no need for it anymore :-(

i've planned to do this somewhere in this major version, for reasons unrelated to streaming.

 

[sq5bpf]

Is it possible to add the 3 played id's ( (G)ISSI ) that are showed in the telive screen under the PLAYED message to the logfile ?
So is is easier to filter them out, for external use.

yes, i can add this to the next version (if i don't forget)

 

[passie101]

Thank you !