-
-
Notifications
You must be signed in to change notification settings - Fork 235
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
Abort the relay,I need a demo. #629
Comments
You can try to do it yourself |
@upeartaker Thanks for the answer, i'd like to help if you can PR a example :) |
Of course, I will propose a PR to you sometime @adwpc |
@upeartaker yes, i done it, but it not work. when a publisher join session, I call Peer.Publisher().Relay(...),then, send the data to other sfu by RPC, other sfu get the data and call session.AddRelayPeer(peerID string, signalData []byte) ([]byte, error). |
Emmm, I think it is possible that your two SFU service exposed UDP port is single port, change to random port try. I have also encountered this problem, in ORTC mode, the relay operation uses a single port, there are some weird problems. The code I implemented under the signal service looks something like this
invoke is grpc client |
@upeartaker en, it still not work.
other sfu err log:
|
[2021-12-20 11:12:32.477] [ERROR] [relay.go:286] => Error starting relay error="connecting canceled by caller" If that doesn't solve your problem, I suggest you use a packet capture tool to analyze your STUN server mappings |
@upeartaker all peers and sfu nodes use same LAN. |
I encountered the same error while playing with SFUa SFUb ( and after digging into the detailed response (content of |
ION-SFU integration
ION-SFU offers some convenience methods for relaying peers in a very simple way.
To relay a peer just call Peer.Publisher().Relay(...) then signal the data to the remote SFU and ingest the data using:
session.AddRelayPeer(peerID string, signalData []byte) ([]byte, error)
set the []byte response from the method as the response of the signaling. And is ready, everytime a peer joins to the new SFU will negotiate the relayed stream.
When will I call Peer.Publisher().Relay(...) ?
When will I call session.AddRelayPeer(peerID string, signalData []byte) ([]byte, error) ?
The text was updated successfully, but these errors were encountered: