Hello Lorenzo,
One curious observation. The mountpoint sends audio and video, the audio is actually received instantly and is the video track what is being "muted". Is that possible?
Thanks for the early response :)
PD: I tryed your suggestion and it didn't solve the issue.
For creating the streming mounpoint I'm using this message structure:
var stream1 = { "request": "create", "type": "rtp", "id":parseInt(room), "audio": true, "video": true, "pin": pin, "audioport": audioport1 , "audiopt": 111, "audiortpmap": "opus/48000/2", "videoport": videoport, "videopt": 100, "videortpmap": "VP8/90000", "videortcpport":4004};
And for the rtp_forward:
var requestmsg = { "request": "rtp_forward", "publisher_id" : parseInt(myid), "room": parseInt(room), "audio_port": audioport1, "audiopt": 111, "video_port": videoport, "videopt": 100, "host":"", "local_rtcp_port":4004, "remote_rtcp_port":4005};
I wrote it based on the documentation and the API doesn't complain... Still I'm not sure it's correct because for the rtp_forward I cannot distinguish between audio and video rtcp ports (I only included the videortcpport in the streaming mountpoint because is the problematic track)