-
-
Notifications
You must be signed in to change notification settings - Fork 32
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
Rendezvous mode works only with outgoing connection #18
Comments
Hi, Do you have something on your logcat? Any hint about the issue? As a temporary workaround, according to SRT documentation (https://github.com/Haivision/srt/blob/master/docs/API/API-functions.md#srt_rendezvous), rendezVous is It might be time to add an AndroidTest on rendezVous() to check what it's happening. Regards, |
socket.setSockFlag(SockOpt.RENDEZVOUS, true); logcat after 30 seconds of calling rendezVous i tried using "0.0.0.0", "localhost", "192.168.1.244" as the localhost value, no result
I do not understand this phrase, rendezVous blocks the thread on 30 sec. |
What operations do you perform on the peer device? I am not familiar with rendezVous API but the peer device should also call
I think it means that:
is the equivalent of:
|
I use android apps Larix Player, Haivision Play, Haivision Play Pro on another device as peers socket.bind("0.0.0.0", 5000) |
In the link Larix Player - Larix Brodcaster if an incorrect ip address is specified in one of the apps, the connection is not established, a similar situation srtdroid - srtdroid. |
Hi, I am not sure I fully understand the issue. It seems to me that you are describing the server/listener mode instead of the rendezvous mode. |
Socket socket = new Socket();
socket.setSockFlag(SockOpt.TRANSTYPE, Transtype.LIVE);
socket.setSockFlag(SockOpt.PAYLOADSIZE, 1316);
socket.rendezVous("0.0.0.0", remotehost, 5000);
if I set remotehost a non existent ip, connection is not established
Caller and Listener modes work fine.
I use android apps Larix Player, Haivision Play, Haivision Play Pro
Thank you.
The text was updated successfully, but these errors were encountered: