Closed xhaakon closed 8 years ago
@hojthojt This doesn't look right:
a=rtpmap:96 X-DATA/90000
it should read:
a=rtpmap:127 X-DATA/90000
Most Lync endpoints aren't so picky about RTP payload type numbers, but conference server is one of them.
This issue is caused by an incomplete update of your installation, namely libfarstream-0.2-5-sipe
doesn't match installed pidgin-sipe
. To fix this, please update to libfarstream-0.2-5-sipe 0.2.8+sipe+collab-1+201605241617~ubuntu14.04.1
or newer.
I'll update the dependencies of pidgin-sipe
package so that next time it pulls in also the correct Farstream version.
@hojthojt Turns out on 14.04 it won't work even after Farstream update because some files are installed in different locations there. So hold on, I'll have to fix that too...
@hojthojt @gy-lehel Depending on your Ubuntu version, please update to one of the following pidgin-sipe
packages and re-test:
pidgin-sipe - 1.21.0+sipe-0+201605260901~ubuntu16.04.1
pidgin-sipe - 1.21.0+sipe-0+201605260901~ubuntu15.10.1
pidgin-sipe - 1.21.0+sipe-0+201605260901~ubuntu14.04.1
Installing the package should also update libfarstream-0.2-5
to the required version automatically.
@xhaakon Thank you very much for the quick fix. I have updated (I'm on 14.04.1).
@hojthojt Please let me know it it's fixed so that I can close this issue.
@xhaakon I do not have a "test case" that could reproduce this error every time. But I have successfully tested on one meeting so far and it worked. For my point of view you can close this one. If it happens to me again, I'll let you now ;) . Again, thank you for your quick response.
@hojthojt This issue is 100% reproducible with meetings of multiple users ("chats" in Pidgin), so one working is enough to be sure it has been fixed. Thanks and closing.
I've got this today for the first time, and it repeatedly failed until I eventually restarted pidgin, which recovered it for me.
I recall seeing something similar, or even identical. It behaves as if an old connection wasn't terminated or cleaned up correctly. A restart did the trick in my case also.
Initiating SDP message from the user's Sipe client:
488 Not Acceptable Here
reply:Installed packages: