In-browser webrtc_websys can open stream, but can not accept stream from dialed peer (identify times out in golang basic host)

Summary

While trying to implement(https://github.com/lat-murmeldjur/weeb-3) an in-browser wasm client (to ethswarm bee network), the following behaviour was encountered.
Dial to go-libp2p over webrtc-direct succeeds.
Can open custom handshake stream which succeeds.
After the handshake the other side tries to open a stream, which fails with identify failed: context timed out.
My in-browser node has identify behaviour, also tried manually accepting off-band identify streams, also tried triggering identify push manually from browser, however, the result is in each case the golang side failing with this line while trying to open a new stream.
Any help appreciated

Expected behavior

After .accept(P_PROTOCOL) and polling incoming streams, dialed node should be able to open stream towards browser node on the already existing connection.

Actual behavior

After .accept(P_PROTOCOL) and polling incoming streams, dialed (golang libp2p server) node times out with identify failed.

Relevant log output

No response

Possible Solution

Using websocket instead of webrtc with upgrade(V1), yamux and noise solved the issue. Is there a similar way to add a multiplexer to webrtc_websys transport?

Version

Latest git commit

Would you like to work on fixing this bug ?

Yes

Start by reproducing the browser-to-Go flow around webrtc_websys, then inspect go-libp2p's p2p/host/basic/basic_host.go at line 723 where stream opening times out. Compare the working websocket upgrade(V1), yamux, and noise path with the WebRTC transport. Done means the Go peer can open a stream toward the browser after the existing connection and identify exchange.