Ihor

Another small documentation fix https://github.com/zelloptt/opus-to-pcm/pull/2

> Is [80e753f52562eb454910.worker.js](https://github.com/zelloptt/zello-channel-api/pull/184/files#diff-5d69eefe41f40f06ba17bfbc9fd72ac15579dfeed62941db1be031e4a6ec4f31) a desired file we actually want to commit? It seems to me like these files are maybe incidental from our build process, and that we don't actually...

> > It's requested as blob before sending and before receiving audio data. > > What's the significance behind the name of this? I'm not sure. The filename is generated...

Back-merged master Merged the [auth token version support](https://github.com/zelloptt/zello-wss/pull/120) Rebuilt SDK

Back-merged master, changed according to the latest minor comments; rebuilt SDK

> minor. are you still waiting on anything to merge? I remember the comment [here](https://github.com/zelloptt/zello-channel-api/pull/193) > Maybe add a brief description about possible `tokenVersion` values? Or it's supposed not to...

It looks like the way of constructing the ogg pages is not correct. You have to calculate and fill the **page_segments** and **segment_table** fields (see [Ogg page format](https://datatracker.ietf.org/doc/html/rfc3533#section-6)) More information...

Here is a simple example: https://github.com/zelloptt/zello-channel-api/commit/4ed91cc4e0355576d78e17a639e5515eef9df382

Hi @HotEmu, Are you using Zello Consumer or Zello Work? So far, I noticed a property `listen_only` In your logon packet, so you should get an error `listen only connection`...

We have found the root cause and fixed it. A `refresh_token` is sent in response to the successful `logon` command.