Open Dr-Django opened 4 days ago
Hey @Dr-Django
First off, I'm surprised this project is actually in use! Thank you!
Second, I built this quite a while back (4yrs ago) and I haven't touched it since. A lot may have changed since esp. on how KMS actually operates. I've even forgotten a lot of the concepts.
I unfortunately can't help with your problem.
I'll however keep this issue open, in case someone else stumbles on it and can help.
My bad.
@kelvingakuo
Hey! I can understand. No problem
I have been facing this issue for two days. I'll be going to attach a diagram at the end for better understanding of my communication structure.
The problem is that whenever I get ice candidates after exchanging SDP offers, I can add ice-candidates using methods like:
add_ice_candidate()
&gather_ice_candidates
.Besides,
add_event_listener
is not working.One more question here is that:
Suppose we have added ice candidates and gathered them by calling methods. Should we send an acknowledgement message from my websocket custom handler that ice candidates were added, or should I return an ice candidate object?
If ice-candidates would be sent from KMS to the client. Then how could we process the generation of ice-candidates with or without call back functions ?