祝早日找回

前辈

抽一个试试

是否支持远程

沉下去

支持远程？

这是我在服务器端和本地跑的
turnutils_uclient -v -u "cccc" -w "bbbb" aaaa.com
0: : IPv4. Connected from: 192.168.2.147:45624
0: : IPv4. Connected from: 192.168.2.147:45624
0: : IPv4. Connected to: a.b.c.d:xxxx
0: : IPv4. Connected to: a.b.c.d:xxxx
0: : allocate sent
0: : allocate sent
0: : allocate response received:
0: : allocate response received:
0: : allocate sent
0: : allocate sent
0: : allocate response received:
0: : allocate response received:
0: : success
0: : success
0: : IPv4. Received relay addr: a.b.c.d:49742
0: : IPv4. Received relay addr: a.b.c.d:49742
0: : clnet_allocate: rtv=2768477507450501170
0: : clnet_allocate: rtv=2768477507450501170
0: : refresh sent
0: : refresh sent
2: : refresh response received:
2: : refresh response received:
2: : success
2: : success
2: : IPv4. Connected from: 192.168.2.147:38182
2: : IPv4. Connected from: 192.168.2.147:38182
2: : IPv4. Connected to: a.b.c.d:xxxx
2: : IPv4. Connected to: a.b.c.d:xxxx
2: : IPv4. Connected from: 192.168.2.147:52290
2: : IPv4. Connected from: 192.168.2.147:52290
2: : IPv4. Connected to: a.b.c.d:xxxx
2: : IPv4. Connected to: a.b.c.d:xxxx
2: : allocate sent
2: : allocate sent
2: : allocate response received:
2: : allocate response received:
2: : allocate sent
2: : allocate sent
3: : allocate response received:
3: : allocate response received:
3: : success
3: : success
3: : IPv4. Received relay addr: a.b.c.d:49743
3: : IPv4. Received relay addr: a.b.c.d:49743
3: : clnet_allocate: rtv=0
3: : clnet_allocate: rtv=0
3: : refresh sent
3: : refresh sent
3: : refresh response received:
3: : refresh response received:
3: : success
3: : success
3: : allocate sent
3: : allocate sent
3: : allocate response received:
3: : allocate response received:
3: : allocate sent
3: : allocate sent
3: : allocate response received:
3: : allocate response received:
3: : success
3: : success
3: : IPv4. Received relay addr: a.b.c.d:63538
3: : IPv4. Received relay addr: a.b.c.d:63538
3: : clnet_allocate: rtv=2941159566689094446
3: : clnet_allocate: rtv=2941159566689094446
3: : refresh sent
3: : refresh sent
3: : refresh response received:
3: : refresh response received:
3: : success
3: : success
3: : channel bind sent
3: : channel bind sent
5: : cb response received:
5: : cb response received:
5: : channel bind: error 403 (Forbidden IP)
5: : channel bind: error 403 (Forbidden IP)

@andyskaura 只是给客户端渲染出了问题

我的是 SFU 服务端能截获到流 而且就算转发的时候我服务端收到的转发流是正常的

o=- 4335692748102869869 2 IN IP4 127.0.0.1
s=-
t=0 0
a=extmap-allow-mixed
a=msid-semantic: WMS
a=group:BUNDLE 0 1
m=audio 9 UDP/TLS/RTP/SAVPF 96
c=IN IP4 0.0.0.0
a=rtpmap:96 opus/48000/2
a=fmtp:96 minptime=10;useinbandfec=1
a=rtcp:9 IN IP4 0.0.0.0
a=extmap:2 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:1 urn:ietf:params:rtp-hdrext:sdes:mid
a=setup:active
a=mid:0
a=recvonly
a=ice-ufrag:K/wc
a=ice-pwd:MjiqCWR2y85px+rHu7Q+Cv7c
a=fingerprint:sha-256 04:6B:27:35:A2:D3:DE:EE:9A:FD:40:F3:86:84:44:39:93:20:E5:F3:39:26:F1:38:AD:27:66:D6:63:8E:C7:C8
a=ice-options:trickle
a=rtcp-mux
m=video 9 UDP/TLS/RTP/SAVPF 99
c=IN IP4 0.0.0.0
a=rtpmap:99 H264/90000
a=fmtp:99 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f
a=rtcp:9 IN IP4 0.0.0.0
a=extmap:4 http://www.webrtc.org/experiments/rtp-hdrext/abs-send-time
a=extmap:3 urn:ietf:params:rtp-hdrext:sdes:mid
a=setup:active
a=mid:1
a=recvonly
a=ice-ufrag:K/wc
a=ice-pwd:MjiqCWR2y85px+rHu7Q+Cv7c
a=fingerprint:sha-256 04:6B:27:35:A2:D3:DE:EE:9A:FD:40:F3:86:84:44:39:93:20:E5:F3:39:26:F1:38:AD:27:66:D6:63:8E:C7:C8
a=ice-options:trickle
a=rtcp-mux
这是第一次建立的协商的 sdp 信息

@andyskaura 你们什么场景 摄像头监控集群?

@andyskaura 我明天顺着这个思路排查

@andyskaura 我用我本机 ping 的无丢包 响应在 90ms

@andyskaura 您厂里的监控都是打洞?如何监控的

还是 tcp

@andyskaura 客户端就没正常过只要和人互联之后接收的视频流就有延迟和丢包

@andyskaura 我手机直连 wifi 上网 也会由于路由器策略丢包？但是我强制用 tcp 连 turn 中继服务 情况并无改善呢

@andyskaura 服务器带宽没打满

@andyskaura 这种观测手段不太靠谱把