Jitsi-meet: sending endpoint text message Error: Channel support is disabled

[cfry]

This Issue tracker is only for reporting bugs and tracking code related issues.

I am attempting to send a message via Jitsi

Description

`var domain = 'beta.meet.jit.si' //'meet.jit.si'
var options = {
roomName: 'fry_room',
width: 490,
height: 470,
parentNode: jitsi_id // document.querySelector('#meet')
}
var api = new JitsiMeetExternalAPI(domain, options)
function text_listener(data){
console.log("got text data: " + JSON.stringify(data))
}
api.addEventListener('endpointTextMessageReceived', text_listener);
api.executeCommand('sendEndpointTextMessage', api._myUserID, 'programmatic text');

Current behavior

Text does not show up in the local or remote gui but rather errors with:
Logger.js:154 2020-04-11T17:53:23.026Z [modules/API/API.js] : Failed sending endpoint text message Error: Channel support is disabled!
at t.value (VM1479 lib-jitsi-meet.min.js:1)
at oe.sendEndpointMessage (VM1479 lib-jitsi-meet.min.js:10)
at Object.sendEndpointMessage (VM1480 app.bundle.min.js:126)
at Object.send-endpoint-text-message (VM1480 app.bundle.min.js:126)
at b.on (VM1480 app.bundle.min.js:126)
at n.size.n.forEach.e (VM1480 app.bundle.min.js:29)
at Set.forEach ()
at p.emit (VM1480 app.bundle.min.js:29)
at p._onMessageReceived (VM1480 app.bundle.min.js:29)
at postis.listen.e (VM1480 app.bundle.min.js:29)
at u (VM1480 app.bundle.min.js:152)

Expected Behavior

Seeing the text in the GUI on both the sender and the reciever.
Seeing my text_listener function called.

Possible Solution

See description, but I don't really care if that's the approach.
Any way I can send a text message via Jitsi from one
jitsi client to another, both "broadcase" to all participants,
and to target it to one participant would be great.

Steps to reproduce

See description

Environment details

Mac OS, code in description evaled in Electron V4

[dlbdvd96]

I have the same issue.

[jminor]

I had the same "Channel support is disabled" problem, so I experimented with the openBridgeChannel options to see if that would help. Every once in a while a message goes through, but 99% do not.

configOverwrite: { openBridgeChannel: 'datachannel' }

From another thread, I found a suggestion to try connecting via the domain beta.meet.jit.si instead. That did the trick, and now sendEndpointTextMessage is working great.

const domain = 'beta.meet.jit.si';
const options = { ... };
const api = new JitsiMeetExternalAPI(domain, options);

Also, @cfry, two things to note: 1) Your sample code is sending an endpoint message to yourself - you might want to try sending to a different participantId. 2) These endpoint text messages are not the same as the chat text messages that you see in the UI. I don't see any exposed API for chat messages.

[cfry]

thanks Joshua, this sounds like "the missing manual"!

On Sun, May 3, 2020 at 12:51 AM Joshua Minor [e-mail]
wrote:

I had the same "Channel support is disabled" problem, so I experimented
with the openBridgeChannel options to see if that would help. Every once in
a while a message goes through, but 99% do not.

configOverwrite: { openBridgeChannel: 'datachannel' }

From another thread, I found a suggestion to try connecting via the domain
beta.meet.jit.si instead. That did the trick, and now
sendEndpointTextMessage is working great.

const domain = 'beta.meet.jit.si';
const options = { ... };
const api = new JitsiMeetExternalAPI(domain, options);

Also, @cfry https://github.com/cfry, two things to note: 1) Your sample
code is sending an endpoint message to yourself - you might want to try
sending to a different participantId. 2) These endpoint text messages are
not the same as the chat text messages that you see in the UI. I don't see
any exposed API for chat messages.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jitsi/jitsi-meet/issues/5975#issuecomment-623053789,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJBG7NCFZJG3UMMPZ32W7DRPTZ3XANCNFSM4MHMAGQQ
.

[horymury]

hi @cfry ,

Is this still an issue for you? Just tested on both beta.meet.jit.si and meet.jit.si and it seems to work fine now.

[wuttke]

Doesn't work for me - same exception.
I tried configOverwrite: { openBridgeChannel: 'datachannel' } (also tried passing 'true') and beta.meet.jit.si.

EDIT: works for me! - silly mistake ;)

[globalexport]

Doesn't work for me - same exception.
I tried configOverwrite: { openBridgeChannel: 'datachannel' } (also tried passing 'true') and beta.meet.jit.si.

EDIT: works for me! - silly mistake ;)

Hi @wuttke! What was your mistake? Having the same problem right now.