ms-diagnostics: 24000 "Error parsing SDP" when attempting to view conference presentation
Closed this issue · 11 comments
Invitation SDP:
v=0
o=- 0 0 IN IP4 192.168.1.157
s=session
c=IN IP4 192.168.1.157
b=CT:99980
t=0 0
m=applicationsharing 50006 TCP/RTP/AVP 127
a=candidate:1 1 TCP-ACT 2020212991 192.168.1.157 50006 typ host
a=candidate:1 2 TCP-ACT 2020212991 192.168.1.157 50006 typ host
a=candidate:2 1 TCP-PASS 2019819775 192.168.1.157 50006 typ host
a=candidate:2 2 TCP-PASS 2019819775 192.168.1.157 50006 typ host
a=candidate:3 1 TCP-PASS 1768161535 1.2.3.4 50006 typ srflx raddr 192.168.1.157 rport 50006
a=candidate:3 1 TCP-PASS 1768161535 1.2.3.4 50006 typ srflx raddr 192.168.1.157 rport 50006
a=candidate:3 2 TCP-PASS 1768161535 1.2.3.4 50006 typ srflx raddr 192.168.1.157 rport 50006
a=candidate:3 2 TCP-PASS 1768161535 1.2.3.4 50006 typ srflx raddr 192.168.1.157 rport 50006
a=candidate:4 1 TCP-ACT 1684668671 5.6.7.129 0 typ srflx raddr 192.168.1.157 rport 0
a=candidate:4 2 TCP-ACT 1684668671 5.6.7.129 0 typ srflx raddr 192.168.1.157 rport 0
a=candidate:5 1 TCP-ACT 174719231 5.6.7.148 57727 typ relay raddr 192.168.1.157 rport 50006
a=candidate:5 2 TCP-ACT 174719231 5.6.7.148 57727 typ relay raddr 192.168.1.157 rport 50006
a=candidate:6 1 TCP-PASS 174326015 5.6.7.148 57727 typ relay raddr 192.168.1.157 rport 50006
a=candidate:6 2 TCP-PASS 174326015 5.6.7.148 57727 typ relay raddr 192.168.1.157 rport 50006
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:XKpC5JNbfGfhfVL7zXqw+cQStxCXPnk00gzVHCIp|2^31
a=rtpmap:127 X-DATA/90000
a=rtcp:50006
a=connection:new
a=setup:active
a=x-applicationsharing-session-id:1
a=x-applicationsharing-role:viewer
a=x-applicationsharing-media-type:rdp
a=ice-ufrag:WnVP
a=ice-pwd:gIX/5bs8Se3Ms4Wg3ouany
ms-diagnostics: 24000;Component="RTCC/5.0.0.0_applicationsharing";Reason="Error parsing SDP";Source="server.company.com"
The duplicate TCP-PASS candidates with foundation 3 shouldn't be there:
a=candidate:3 1 TCP-PASS 1768161535 1.2.3.4 50006 typ srflx raddr 192.168.1.157 rport 50006
a=candidate:3 1 TCP-PASS 1768161535 1.2.3.4 50006 typ srflx raddr 192.168.1.157 rport 50006
a=candidate:3 2 TCP-PASS 1768161535 1.2.3.4 50006 typ srflx raddr 192.168.1.157 rport 50006
a=candidate:3 2 TCP-PASS 1768161535 1.2.3.4 50006 typ srflx raddr 192.168.1.157 rport 50006
The IP denoted by 1.2.3.4
is the pubic IP address of user's internet connection.
Second time:
v=0
o=- 0 0 IN IP4 192.168.1.157
s=session
c=IN IP4 192.168.1.157
b=CT:99980
t=0 0
m=applicationsharing 50005 TCP/RTP/AVP 127
a=candidate:1 1 TCP-ACT 2020212991 192.168.1.157 50005 typ host
a=candidate:1 2 TCP-ACT 2020212991 192.168.1.157 50005 typ host
a=candidate:2 1 TCP-PASS 2019819775 192.168.1.157 50005 typ host
a=candidate:2 2 TCP-PASS 2019819775 192.168.1.157 50005 typ host
a=candidate:3 1 TCP-PASS 1768161535 1.2.3.4 50005 typ srflx raddr 192.168.1.157 rport 50005
a=candidate:3 1 TCP-PASS 1768161535 1.2.3.4 50005 typ srflx raddr 192.168.1.157 rport 50005
a=candidate:3 2 TCP-PASS 1768161535 1.2.3.4 50005 typ srflx raddr 192.168.1.157 rport 50005
a=candidate:3 2 TCP-PASS 1768161535 1.2.3.4 50005 typ srflx raddr 192.168.1.157 rport 50005
a=candidate:4 1 TCP-ACT 1684668671 5.6.7.129 0 typ srflx raddr 192.168.1.157 rport 0
a=candidate:4 2 TCP-ACT 1684668671 5.6.7.129 0 typ srflx raddr 192.168.1.157 rport 0
a=candidate:5 1 TCP-ACT 174719231 5.6.7.145 63616 typ relay raddr 192.168.1.157 rport 50005
a=candidate:5 2 TCP-ACT 174719231 5.6.7.145 63616 typ relay raddr 192.168.1.157 rport 50005
a=candidate:6 1 TCP-PASS 174326015 5.6.7.145 63616 typ relay raddr 192.168.1.157 rport 50005
a=candidate:6 2 TCP-PASS 174326015 5.6.7.145 63616 typ relay raddr 192.168.1.157 rport 50005
a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:4ygK2y5DswLC5/aARYUvxnLhIs0slxBF9kcBXZWK|2^31
a=rtpmap:127 X-DATA/90000
a=rtcp:50005
a=connection:new
a=setup:active
a=x-applicationsharing-session-id:1
a=x-applicationsharing-role:viewer
a=x-applicationsharing-media-type:rdp
a=ice-ufrag:hIUI
a=ice-pwd:aZqSSerZiGhmHgOb8gPLeu
Note the candidate duplication happens also when a different relay is used.
Unfortunately, libnice debug logging is insufficient. We should dump connection check list after the gathering is finished too.
(Pidgin:7397): libnice-DEBUG: Agent 0x5560f3996de0 : Candidate gathering FINISHED, stopping discovery timer.
(Pidgin:7397): libnice-DEBUG: Agent 0x5560f3996de0: gathered TCP-ACT local candidate : [192.168.1.157]:0 for s1/c1. U/P '(null)'/'(null)'
(Pidgin:7397): libnice-DEBUG: Agent 0x5560f3996de0: gathered TCP-PASS local candidate : [192.168.1.157]:50005 for s1/c1. U/P '(null)'/'(null)'
(Pidgin:7397): libnice-DEBUG: Agent 0x5560f3996de0: gathered TCP-PASS local candidate : [1.2.3.4]:50005 for s1/c1. U/P '(null)'/'(null)'
(Pidgin:7397): libnice-DEBUG: Agent 0x5560f3996de0: gathered TCP-ACT local candidate : [5.6.7.129]:0 for s1/c1. U/P '(null)'/'(null)'
(Pidgin:7397): libnice-DEBUG: Agent 0x5560f3996de0: gathered TCP-PASS local candidate : [5.6.7.129]:50005 for s1/c1. U/P '(null)'/'(null)'
(Pidgin:7397): libnice-DEBUG: Agent 0x5560f3996de0: gathered TCP-ACT local candidate : [5.6.7.145]:63616 for s1/c1. U/P '(null)'/'(null)'
(Pidgin:7397): libnice-DEBUG: Agent 0x5560f3996de0: gathered TCP-PASS local candidate : [5.6.7.145]:63616 for s1/c1. U/P '(null)'/'(null)'
(Pidgin:7397): libnice-DEBUG: Agent 0x5560f3996de0: gathered TCP-ACT local candidate : [192.168.1.157]:0 for s1/c2. U/P '(null)'/'(null)'
(Pidgin:7397): libnice-DEBUG: Agent 0x5560f3996de0: gathered TCP-PASS local candidate : [192.168.1.157]:50001 for s1/c2. U/P '(null)'/'(null)'
I get the same error when I try to accept a shared screen... but today I get one more line in the error message:
Error occurred
Unable to establish a call
488 Not Acceptable HerePrevious hop federated peer did not report diagnostic information
@overisberg error 488 is very generic and can mean a lot of things. If possible, please provide your Pidgin logs.
Hi, I have had this problem a few times now and I have the feeling that it has something to do with when I move my computer between different network connections (wired, wifi, different wifi access points). But this is just a "hunch". Restarting Pidgin is not enough since today I restarted Pidgin in debug mode and still got the error. I have the pidgin.log from:
GST_DEBUG=3 G_MESSAGES_DEBUG=all NICE_DEBUG=all,libnice-nice-verbose pidgin --debug |& tee ~/pidgin.log
Mail me if you want it.
I attached the package versions I was running.
versions.txt
@hojthojt If you don't want to post the log publicly, please send it to the mail in my profile.
I get the same error when I try to accept a shared screen... but today I get one more line in the error message
@overisberg Your problem is likely the same as in #83, which was affecting everybody with 14.04. Please update pidgin-sipe
if you haven't yet.
@xnandersson This needs a check for reproducibility with recent libnice package.
Not reproduced with recent libnice within 14 days. Considered as fixed.