<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="#0563C1" vlink="#954F72"> <div class="WordSection1"> Hi, with webrtcbin it appears that if one attempts to create-answer immediately after set-remote-description, that the promise is often not called back with the answer.<o:p></o:p> <o:p> </o:p> From looking at the logs I can see the webrtcbin create_answer_task run and it even appears to reply to the promise. However, I never see the promise return to my code.<o:p></o:p> It also appears that the create_answer_task starts while gstreamer is creating a bunch of elements in response to set-remote-description. My inference is that gstreamer needs to process the offer and set up those elements before it can correctly create an answer. Is this the case?<o:p></o:p> <o:p> </o:p> I am able to get the answer created if my code waits a bit (e.g. 200ms) between the set-remote-description and the create-answer. The answer is returned and sent back to the client, ice negotiation happens, media flows, etc.<o:p></o:p> <o:p> </o:p> I’m using gstreamer 1.16.0 on OSX. I’m also using the java bindings via gst1-java-core 1.1.0.<o:p></o:p> <o:p> </o:p> The java bindings interrupt the promise passed into the set-remote-description call (signal emission) indicating that a callback isn’t needed. I tried replacing this logic and passing in an actual (non-interrupted) promise to set-remote-description to get notified when it is complete, and then do create-answer. However, that didn’t seem to work – the answer still wasn’t returned. Perhaps the completion promise is called back before gstreamer has actually fully processed the offer.<o:p></o:p> <o:p> </o:p> My code that encountered these problems is running in a unit test that creates one pipeline for the client (sending) side of a webrtc session and another pipeine for the peer (receiver) side of a webrtc session. Both pipelines are running in the same process on the same machine. I cranked up logging to *:4,*webrtc*:7 and saw no errors, nor any informative warnings. I can share a log file of the failure if you’d like.<o:p></o:p> <o:p> </o:p> Question: How can I know after set-remote-description when I can call (emit) create-answer?<o:p></o:p> <o:p> </o:p> This problem also seems to afflict on-negotiation-needed and create-offer, but not as clearly as with set-remote-description and create-answer.<o:p></o:p> <o:p> </o:p> Thanks,<o:p></o:p> <o:p> </o:p> Stuart<o:p></o:p> <o:p> </o:p> <o:p> </o:p> <o:p> </o:p> </div> </body> </html>