We have decided to phase out the Mixed Reality Forums over the next few months in favor of other ways to connect with us.
The first way we want to connect with you is our mixed reality developer program, which you can sign up for at https://aka.ms/IWantMR.
The plan between now and the beginning of May is to clean up old, unanswered questions that are no longer relevant. The forums will remain open and usable.
On May 1st we will be locking the forums to new posts and replies. They will remain available for another three months for the purposes of searching them, and then they will be closed altogether on August 1st.
So, where does that leave our awesome community to ask questions? Well, there are a few places we want to engage with you. For technical questions, please use Stack Overflow, and tag your questions using either hololens or windows-mixed-reality. If you want to join in discussions, please do so in the HoloDevelopers Slack, which you can join by going to https://aka.ms/holodevelopers. And always feel free to hit us up on Twitter @MxdRealityDev.
[UWP]WebRTC issue - Hololens unable to send video offer
we developed a fully working webRTC UWP environment starting from this project (https://github.com/webrtc-uwp/PeerCC/tree/Mosa/20180320-peercc-unity).
We developed a Desktop app and a HoloLens app to communicate with each other. Everything was good until we moved to a custom server (Xirsys in this case).
We then modified the Signalling script to adapt it to the new server which uses the MessageWebSocket instead of the StreamSocket that we used before with the peerccconnection_server.exe included in the sample demo.
The current scenario is:
-Desktop connects to the server and waits for peers.
-Hololens connects to the server and is added to the available peers' list.
-Desktop can now call the Hololens and start communicating.
Hololens should send both audio and video, while Desktop only sends audio.
The actual problem now is the hololens is not able to send the video offer, so the app freezes and crashes. Audio is still working fine (just a few secs before the crash).
If we try communicating between two Desktop clients everything works like a charm.
It would be appreciated some help to solve the problem.