Mikhail Kiurshin

> I can't get a response from megamk, so I wrote a patch for this. I'm sorry, my ruby knowledge is not enough to dive into how your system tests...

There's no support for that right now, we'll add this as a feature request for the future versions

hello @DigitalMike I wasn't able to reproduce the issue reported. I connected as a `user` to a `channel` using Sdk. Granted admin permissions to a `user`, then reconnected again using...

@JasonF2 incoming voice data contains of opus encoded packets with 9 byte headers. Once you strip off the header to detect message id and packet id, you can then decode...

@Allanksr thank you report > on most channels I try to implement, Can you please give us channel names? Thank you

Hello @OnkelTem You're not initializing a session in your example. You need to initialize sdk, then create and connect a session and then you will be able to send messages....

> As for custom encoder, I actually got my idea from the docs: https://zelloptt.github.io/zello-channel-api/js/Session.html#startVoiceMessage Thanks for pointing on that, yes, `startVoiceMessage` options are merged with session options so both ways...

you can create a new session to connect to the other channel

Errors are duplicated probably because session is trying to reconnect. Sdk does not support password protected channels, zelect and zelect+ channels and `Allow anonymous listeners` channel option has to be...

> wondering if you had thoughts on the above ? this is documentation error. It should mention as @agatx says that maximum is `60` Also, encoder used by JS SDK...