This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/op25-dev@lists.osmocom.org/.
Ryan Schilder rjschilder at gmail.comok i'll give it a shot. just for giggles i tried the op25_audio_tx.py that
I have on a local repeater. I was able to make it into the repeater!
I'll check the file you mentioned above right now.
Thanks!
-Ryan
On Sat, Dec 28, 2013 at 9:40 AM, <ikj1234i at yahoo.com> wrote:
>
>
> Hi Ryan
>
> This is an interesting update - sounds like some progress, anyway!
>
> As to the encryption, older versions of the TX code did not properly set
> the crypto algo ID, and if you're
> using one of these that would explain why. The way to tell is to look in
> repeater_vocoder.cc to see if you
> have the following (see below). If this code is not there that would
> explain what's happening. If it is there then I think the next step would
> be to run some type of trace so we can confirm what the settings are by
> looking at the actual air data, there would be no doubt as to whether or
> not the bits are being set OK...
>
> 73
>
> Max
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> /* bits to be preset to 1 for all transmitted frames */
> static const bool ldu1_preset[] = {
> ...
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/op25-dev/attachments/20131228/2d8c26fa/attachment.htm>