-
Notifications
You must be signed in to change notification settings - Fork 350
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Writing a custom xmpp client: Endpoint ID does not match channel bundle ID #531
Comments
Thanks for the well-written report, clearly you've done your research :) In general this sort of thing should be posted over at community.jitsi.org, though, until we confirm there's an actual issue. Can you include logs from the bridge with
Added in Is your client doing max-bundle? (all RTP + RTCP sent and received over a single port?) This is required. If it is, perhaps it's not advertising its transport bundles correctly (it should be a single channel-bundle). Also, I don't see any session-initiate or session-accept in there your client logs? |
I think it's not an issue with jiicofo, it's me doing something wrong, I just can't figure out what exactly. I'm pretty new to jitsi (I've been playing with it just for the last week or less), so there may be some obvious mistakes from my side. If you want I'll move this issue to the
Yes, thank for that, here's the JVB log: and jicofo (FINE) And I see the reason for the error (there's no
Do you mean rtcp-mux and bundle? I use gstreamer and they have rtp funnel which adds bundle capabilities, also I have rtpmux element, but these should be used after session-initiate in XMPP, right? I should advertise my channel-bundle after session-initiate in session-accept jingle, is that right? Or I should send something else to |
@bbaldino I've posted it on community forum: https://community.jitsi.org/t/writing-a-custom-xmpp-client-endpoint-id-does-not-match-channel-bundle-id/57699?u=timadevelop |
So, as @bbaldino said on the community forum, the problem is that my xmpp client library did not send disco features for mux & bundle standards because it actually does not support them. Thank you, I'm closing this issue. |
Hey guys,
I'm trying to write a custom xmpp client for Jitsi meet in C++.
I'm using the latest
docker-jitsi-meet
repo in order to run a local jitsi instance. Web client works fine, there are no problems.But in my custom terminal client I'm getting this error:
(
Endpoint ID does not match channel bundle ID
)Here's how I see the process:
<bind> and <session>
stanzas and sends<conference>
stanza to jicofo.But here's what I get :(
<ping> and <presence>
stanzas.Endpoint ID does not match channel bundle ID
when jicofo tries to allocate channel for my client.and in jicofoc logs there's
Jicofo 2020-05-17 18:11:31.037 WARNING: [30] org.jitsi.jicofo.JitsiMeetConferenceImpl.log() No jingle session yet for room@muc.meet.jitsi/urxvt
No jingle session yet for room@muc.meet.jitsi/urxvt
Here are my logs my client and jicofo:
QXmppClientLog.log
jicofo.log
Could you help me with this issue? I'm not sure where am I wrong... Jicofo creates a conference, joins the room, my client appears in the room and even can send messages to others, can leave and rejoin the muc, but the call is not working because I don't get
session-initiate
jingle from jicofo. And there are also no error stanzas from jicofo.I've read almost everything on https://community.jitsi.org/ and haven't found anything about this error, but I've found this code:
jicofo/src/main/java/org/jitsi/jicofo/AbstractChannelAllocator.java
Line 301 in b3821f5
Also, I've read all these source files below and found out that Jicofo sets Bundle ID equal to Endpoint ID which is my nickname, is that right?
Thank you,
Vlad.
jicofo/src/main/java/org/jitsi/jicofo/ParticipantChannelAllocator.java
Line 85 in b3821f5
jicofo/src/main/java/org/jitsi/jicofo/Participant.java
Line 38 in b3821f5
jicofo/src/main/java/org/jitsi/jicofo/ParticipantChannelAllocator.java
Line 142 in b3821f5
jicofo/src/main/java/org/jitsi/jicofo/Participant.java
Line 322 in 87e97a8
jicofo/src/main/java/org/jitsi/jicofo/ParticipantChannelAllocator.java
Line 94 in 87e97a8
jicofo/src/main/java/org/jitsi/jicofo/ParticipantChannelAllocator.java
Line 118 in 87e97a8
jicofo/src/main/java/org/jitsi/impl/protocol/xmpp/colibri/ColibriConferenceImpl.java
Line 222 in 87e97a8
jicofo/src/main/java/org/jitsi/jicofo/ParticipantChannelAllocator.java
Line 146 in 87e97a8
jicofo/src/main/java/org/jitsi/jicofo/Participant.java
Line 56 in 87e97a8
-
jicofo/src/main/java/org/jitsi/impl/protocol/xmpp/ChatMemberImpl.java
Line 148 in 87e97a8
The text was updated successfully, but these errors were encountered: