WEB RTC stream no video

[Jan de la Peña]

it works on the same network but apparently on a different one it wont render the stream. i also have setup my TURN server and it is working fine, set to relay when i tested it on Trickle ICE

is it because of tcp? that webRTC doesnt support? my ISP blocks mostly udp but allows tcp.

setting my ice url to ?transport=tcp, coturn logs nothing on verbose mode.

im on react-native btw.

this is my turn (coturn) server log, when only the default turn url is used:

3: handle_udp_packet: New UDP endpoint: local addr <my_server_address>:5349, remote addr 1<ip_address_1>:61058
3: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
3: handle_udp_packet: New UDP endpoint: local addr <my_server_address>:5349, remote addr 1<ip_address_1>:61059
3: session 000000000000000002: realm <north.gov> user <>: incoming packet BINDING processed, success
3: handle_udp_packet: New UDP endpoint: local addr <my_server_address>:5349, remote addr 1<ip_address_1>:61060
3: session 001000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
3: handle_udp_packet: New UDP endpoint: local addr <my_server_address>:5349, remote addr 1<ip_address_1>:61062
3: session 001000000000000002: realm <north.gov> user <>: incoming packet BINDING processed, success
3: handle_udp_packet: New UDP endpoint: local addr <my_server_address>:5349, remote addr 1<ip_address_1>:61064
3: session 000000000000000003: realm <north.gov> user <>: incoming packet BINDING processed, success
3: handle_udp_packet: New UDP endpoint: local addr <my_server_address>:5349, remote addr 1<ip_address_1>:61063
3: session 001000000000000003: realm <north.gov> user <>: incoming packet BINDING processed, success
3: handle_udp_packet: New UDP endpoint: local addr <my_server_address>:5349, remote addr 1<ip_address_1>:61065
3: session 000000000000000004: realm <north.gov> user <>: incoming packet BINDING processed, success
3: handle_udp_packet: New UDP endpoint: local addr <my_server_address>:5349, remote addr 1<ip_address_1>:61066
3: session 001000000000000004: realm <north.gov> user <>: incoming packet BINDING processed, success
3: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
3: session 001000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
3: session 001000000000000002: realm <north.gov> user <>: incoming packet BINDING processed, success
3: session 000000000000000003: realm <north.gov> user <>: incoming packet BINDING processed, success
3: session 001000000000000003: realm <north.gov> user <>: incoming packet BINDING processed, success
3: session 000000000000000004: realm <north.gov> user <>: incoming packet BINDING processed, success
3: session 001000000000000004: realm <north.gov> user <>: incoming packet BINDING processed, success
4: handle_udp_packet: New UDP endpoint: local addr <my_server_address>:5349, remote addr <ip_address_2>:59641
4: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
4: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
4: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
13: session 000000000000000002: realm <north.gov> user <>: incoming packet BINDING processed, success
13: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
13: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
14: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
14: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
23: session 000000000000000002: realm <north.gov> user <>: incoming packet BINDING processed, success
23: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
23: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
24: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
24: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
33: session 000000000000000002: realm <north.gov> user <>: incoming packet BINDING processed, success
33: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
33: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
34: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
34: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
35: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
43: session 000000000000000002: realm <north.gov> user <>: incoming packet BINDING processed, success
43: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
43: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
45: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
45: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
53: session 000000000000000002: realm <north.gov> user <>: incoming packet BINDING processed, success
53: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
54: session 000000000000000001: realm <north.gov> user <>: incoming packet BINDING processed, success
55: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
55: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
55: session 001000000000000005: realm <north.gov> user <>: incoming packet BINDING processed, success
63: session 000000000000000001: closed (2nd stage), user <> realm <north.gov> origin <>, local <my_server_address>:5349, remote 1<ip_address_1>:61058, reason: allocation watchdog determined stale session state
63: session 000000000000000002: closed (2nd stage), user <> realm <north.gov> origin <>, local <my_server_address>:5349, remote 1<ip_address_1>:61059, reason: allocation watchdog determined stale session state
63: session 001000000000000001: closed (2nd stage), user <> realm <north.gov> origin <>, local <my_server_address>:5349, remote 1<ip_address_1>:61060, reason: allocation watchdog determined stale session state
63: session 001000000000000002: closed (2nd stage), user <> realm <north.gov> origin <>, local <my_server_address>:5349, remote 1<ip_address_1>:61062, reason: allocation watchdog determined stale session state
63: session 001000000000000003: closed (2nd stage), user <> realm <north.gov> origin <>, local <my_server_address>:5349, remote 1<ip_address_1>:61063, reason: allocation watchdog determined stale session state
63: session 000000000000000003: closed (2nd stage), user <> realm <north.gov> origin <>, local <my_server_address>:5349, remote 1<ip_address_1>:61064, reason: allocation watchdog determined stale session state
63: session 000000000000000004: closed (2nd stage), user <> realm <north.gov> origin <>, local <my_server_address>:5349, remote 1<ip_address_1>:61065, reason: allocation watchdog determined stale session state
63: session 001000000000000004: closed (2nd stage), user <> realm <north.gov> origin <>, local <my_server_address>:5349, remote 1<ip_address_1>:61066, reason: allocation watchdog determined stale session state

[Jan de la Peña]

in my app it never reach connected and completed on ice connection ch

[Jan de la Peña]

turns out the syntax for the username is not the same from the coturn wiki to the library... hence the user <> is blank. it is working now