Hi, i am using licode for building a broadcasting service, the basic
concepts is that in a room, there would be two role type: presenter and
viewer
presenter could publish stream while viewer only subscribed them
i modify the basic_example to let user choose their role manually
and i met a problem.
Problem:
1, i found that 3 clients in my local network works well if the licode
hosting is also in the local network
2, if i host licode in a public vps, and invite my friend for testing the
service, he as a presenter has a camara, could send stream to me (as the
viewer)
but the video play on myside only insists for seconds, and then it
shows black screen.
3, i am now on my office(behind another router), and i could subscribe
his stream and play that for long times
My guess:
i knew webrtc’s p2p communication need to do udp hole punching, and from
the effects of above step 2, it successed. but some nat
seems would disable the punching if his inner client dont send data through
that port, in my case, as a viewer role, my browser wont sent
data throught that port except the begining connecting steps, that
explained why myside could receive the stream at the begining and after a
while, it stop, just because it wont sent data back after connected, so the
router would disable that port
the above is all my guess, i dont know if it’s the true, if that, i
think maybe you guys need consider send heartbeat packages between peers
for consist the connection
BTW, can anyone tell me how many events there? i cant find any documents
about that