Skip to content
This repository has been archived by the owner on Oct 23, 2024. It is now read-only.

Cannot subscribe the 2nd room mix stream #214

Closed
zhouhuirun2015 opened this issue Aug 13, 2019 · 7 comments · May be fixed by qwu16/owt-server#9
Closed

Cannot subscribe the 2nd room mix stream #214

zhouhuirun2015 opened this issue Aug 13, 2019 · 7 comments · May be fixed by qwu16/owt-server#9

Comments

@zhouhuirun2015
Copy link

zhouhuirun2015 commented Aug 13, 2019 •
edited
Loading

Join room a, subscribe room a's stream, public own local stream, mix a stream, all functions well.
Join room b, subscribe room b's mix stream, success, but no stream rendered.

The webrtc_agent report:

2019-08-13 14:32:35.661 - DEBUG: Connections - Add connection: 966844107217069000 internal [email protected]_5
2019-08-13 14:32:35,664 - DEBUG: owt.RawTransport - Accept ok, local TCP listening port: 20771
2019-08-13 14:32:35,667 - WARN: owt.RawTransport - TCP transport listen in port range bind error: Address already in use
2019-08-13 14:32:35.671 - DEBUG: WebrtcNode - publish, connectionId: 705758938687604000 connectionType: internal options: { controller: '[email protected]_5',
publisher: '5d4020208584087a71fc7656-common',
audio: false,
video: { codec: 'vp8' },
ip: '192.168.1.179',
port: 0 }
@zhouhuirun2015 zhouhuirun2015 changed the title Cannot subscribe the 2nd room stream Cannot subscribe the 2nd room mix stream Aug 13, 2019
@starwarfan
Copy link
Collaborator

Hi, it seems that your internal port range is too small.
Change the port range under [internal] section in webrtc_agent/agent.toml and have a try.

@zhouhuirun2015
Copy link
Author

zhouhuirun2015 commented Aug 13, 2019 •
edited
Loading

This doesn't work,
The webrtc_agent port range is from 20000 ~ 30000 or 10000 ~ 60000

All tested, not worked.

Not every time the stream not rendered.

@starwarfan
Copy link
Collaborator

starwarfan commented Aug 14, 2019 •
edited
Loading

the "maxport" should be larger than "minport", for both [internal] and [webrtc] sections.

@zhouhuirun2015
Copy link
Author

min port and max port in [internal] and [webrtc] sections:
10000 and 60000

@zhouhuirun2015
Copy link
Author

zhouhuirun2015 commented Aug 14, 2019 •
edited
Loading

I wrote a script file to test the server tcp port range open, it's ok.
Not the server's port problem.

tcpSocketRangeTest.txt

@zhouhuirun2015
Copy link
Author

version from commit https://github.com/open-webrtc-toolkit/owt-server/commit/c5438556d91eca891e3d9296dbd4739573a8cc67 fix this bug.

@kurapatijayaram
Copy link

I specified min: 1025 and max: 65535, still facing this problem.

@juncha4x juncha4x mentioned this issue Oct 27, 2022
Closed
@qwu16 qwu16 mentioned this issue Dec 14, 2022
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@kurapatijayaram @starwarfan @zhouhuirun2015