英文:
Why mutliple transport ICE candidate allocated even when sdp using `a=group:BUNDLE 0 1` in chrome?
问题
Chrome版本：113.0.5672.129。
提供的SDP：
v=0
a=group:BUNDLE 0 1
...
m=video
a=mid:0
...
m=application
a=mid:1
但我发现本地收集的ICE候选项被分成两组，一组用于mid-0，另一组用于mid-1：
sdpMid: 0, sdpMLineIndex: 0, candidate: candidate:2558938800 1 udp 2122260223 192.168.2.200 54078 typ host generation 0 ufrag DncU network-id 1
sdpMid: 1, sdpMLineIndex: 1, candidate: candidate:2558938800 1 udp 2122260223 192.168.2.200 54079 typ host generation 0 ufrag DncU network-id 1
sdpMid: 0, sdpMLineIndex: 0, candidate: candidate:1250609983 1 udp 1686052607 115.89.7.51 60609 typ srflx raddr 192.168.2.200 rport 54078 generation 0 ufrag DncU network-id 1
sdpMid: 1, sdpMLineIndex: 1, candidate: candidate:1250609983 1 udp 1686052607 115.89.7.51 43434 typ srflx raddr 192.168.2.200 rport 54079 generation 0 ufrag DncU network-id 1
这是Chrome的一个bug吗？
英文:
Chrome version: 113.0.5672.129。
Offer sdp:
v=0
a=group:BUNDLE 0 1
...
m=video
a=mid:0
...
m=application
a=mid:1
But I found the ice candidates collected locally are splitted into two groups, one for mid-0, the other for mid-1:
sdpMid: 0, sdpMLineIndex: 0, candidate: candidate:2558938800 1 udp 2122260223 192.168.2.200 54078 typ host generation 0 ufrag DncU network-id 1
sdpMid: 1, sdpMLineIndex: 1, candidate: candidate:2558938800 1 udp 2122260223 192.168.2.200 54079 typ host generation 0 ufrag DncU network-id 1
sdpMid: 0, sdpMLineIndex: 0, candidate: candidate:1250609983 1 udp 1686052607 115.89.7.51 60609 typ srflx raddr 192.168.2.200 rport 54078 generation 0 ufrag DncU network-id 1
sdpMid: 1, sdpMLineIndex: 1, candidate: candidate:1250609983 1 udp 1686052607 115.89.7.51 43434 typ srflx raddr 192.168.2.200 rport 54079 generation 0 ufrag DncU network-id 1
It this a bug for chrome?
答案1
得分: 0
除非您将 bundlePolicy 设置为 max-bundle，否则这是规范所要求的行为。
英文:
Unless you set the bundlePolicy to max-bundle that is the behavior required by the specification.
通过集体智慧和协作来改善编程学习和解决问题的方式。致力于成为全球开发者共同参与的知识库，让每个人都能够通过互相帮助和分享经验来进步。
评论