illuspas / illuspas/Node-Media-Server
Reconect when connection lost publishing to RTMP
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6.2k
- Forks
- 1.5k
- Avg merge
- 7m
- Merged PRs (30d)
- 1
Description
I have a problem when connection lost and try to reconnect, or trying to connect to same path to rtmp, first should reject the session, because OBS try to get response and froze
node_rtmp_session.js
// this.reject(); // pull request
Logger.log(`[rtmp publish] Already has a stream. id=${this.id} streamPath=${this.publishStreamPath} streamId=${this.publishStreamId}`);
after reject() should close RTMP connection and reconnect with new session or resume session with the same path, but i can't, anyone can solve this? please , thanks!
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in node_rtmp_session.js at the existing reject() comment and the "Already has a stream" log path. Trace how duplicate publishing and lost connections are handled for the same RTMP path. Done means the old session is rejected and closed so OBS does not freeze, and a new or resumed session can connect successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js
- Domain
- audio-video-rtc
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100