phoenix
phoenixPhoenix - Your AI Assistant
Inactive session will be ended in 24 hours
End Session

Seeking Webrtc professional

  • Posted:
  • Proposals: 21
  • Remote
  • #4490284
  • Open for Proposals
David O.Shahvez J.Parveen A.Muhammad I.Vignesh L. + 16 others have already sent a proposal.
  • 0

Description

Experience Level: Entry
Estimated project duration: Not sure
Greetings.
I have built a live streaming platform using mediamtx, node server (and others).
Having trouble with the webrtc features.
Would need someone to diagnose and help resolve/develop the issues we are having.
The site is live and about 75% completed.
I chose the starting fee at $25 per hour, willing to negotiate a fixed fee or whatever works.
I estimate that the current issues may take anywhere from 4-12 hours (more or less).
May lead to further work down the line.
Kindly message me to get started.
Project base is located in Australia. working from VPS until the program is fully developed.
Have an awesome day!

New Proposal

Login to your account and send a proposal now to get this project.

Log in

Clarification Board Ask a Question

  • Moon Technolabs Pvt. Ltd.

    Hi Ven,

    We are award-winning professionals, we can confidently help you with this bug fixing. Let me know when we can connect.?

  • Sudhanshu K.

    Hi, thanks for the details, WebRTC issues with MediaMTX can get tricky depending on signaling, NAT, ICE/STUN/TURN setup and browser handling.

    To diagnose quickly, could you clarify a few things:

    1. What exact issue are you seeing - no video/audio, connection failures, latency, or intermittent stream drops?
    2. Are you currently using a TURN server (like coturn) or only STUN?
    3. Is MediaMTX configured for WebRTC over WHIP/WHEP or custom signaling via Node.js?
    4. Are the issues happening on all browsers/devices or specific ones (Chrome/Safari/mobile)?
    5. Do you have logs from MediaMTX + Node server when the failure happens?

    Once I have this, I can quickly pinpoint whether it’s signaling, ICE negotiation, or server/network config and suggest fixes or jump into hands-on debugging.

  • Moon Technolabs Pvt. Ltd.

    Hi Ven,

    Are you utilizing TURN and STUN servers for NAT traversal? If so, which servers are you using, and have you experienced any connectivity issues?

    Are you using any specific tools or libraries for testing the WebRTC functionality?

    What specific WebRTC issues are you encountering? Are there any error messages in the browser console or server logs that you can share?

    Ven G.Wed 7:08am

    we are using mediamtx to point to stun or turn servers. They are external and 'free' ones at the moment. We plan on creating our own stun or turn server at some point. Main issue we are having is echo.
    the other issues - need to be discussed and shown to the programmer.Thank you for the question.

  • Eight Veer Ltd

    Hi Ven, could you confirm whether the immediate need is one active WebRTC failure resolved first, or a broader completion push around the remaining 25%?

    Ven G.Wed 4:35am

    it is for both. I have immediate issues. and looking for long term assistance,

    Eight Veer LtdWed 6:51am

    Hi Ven,
    That makes sense. The cleanest route is to deal with the immediate WebRTC issues first, then scope any remaining build work separately once the current fault path is clear.