[Freeswitch-dev] Video of the WebRTC client gets locked up

[Yan Brenman]

Hello,

I have been running 1.4.beta (WebRTC enabled) branch of the FreeSWTICH 
with SIPml5 clients and I am constantly getting
client video freeze in about a minute after call is established and 
video shows up. Here is the relevant part of the log from the console:

2014-03-12 15:24:00.923640 [NOTICE] switch_core_media.c:2577 Choose 
video Candidate cid: 1 proto: udp type: host addr:99.8.141.165:64234 
<http://137.79.217.63:64234/>
2014-03-12 15:24:00.923640 [NOTICE] switch_core_media.c:2577 Choose 
video Candidate cid: 2 proto: udp type: host addr:99.8.141.165:64234 
<http://137.79.217.63:64234/>
2014-03-12 15:24:00.923640 [NOTICE] switch_core_media.c:2582 Save video 
Candidate cid: 1 proto: udp type: host addr:192.168.239.1:64235 
<http://192.168.239.1:64235/>
2014-03-12 15:24:00.923640 [NOTICE] switch_core_media.c:2582 Save video 
Candidate cid: 2 proto: udp type: host addr:192.168.239.1:64235 
<http://192.168.239.1:64235/>
2014-03-12 15:24:00.923640 [NOTICE] switch_core_media.c:2706 setting 
remote video ice addr to99.8.141.165:64234 
<http://137.79.217.63:64234/>based on candidate
2014-03-12 15:24:00.923640 [NOTICE] switch_core_media.c:2726 setting 
remote rtcp video addr to99.8.141.165:64234 
<http://137.79.217.63:64234/>based on candidate
2014-03-12 15:24:00.923640 [INFO] switch_core_media.c:2745 RE-Activating 
video ICE
2014-03-12 15:24:00.923640 [NOTICE] switch_rtp.c:3775 Activating RTP 
video ICE: +Pz0ELVd4tEZygTU:ZGabdph1JK6l9boM99.8.141.165:64234 
<http://137.79.217.63:64234/>
2014-03-12 15:24:00.923640 [INFO] switch_core_media.c:2794 Activating 
video RTCP PORT 64234
2014-03-12 15:24:00.923640 [INFO] switch_core_media.c:2802 Skipping 
video RTCP ICE (Same as RTP)
2014-03-12 15:24:00.923640 [INFO] switch_core_media.c:4703 RE-SETTING 
video DTLS
2014-03-12 15:24:00.923640 [INFO] switch_rtp.c:2878 Activate RTP/RTCP 
video DTLS server
2014-03-12 15:24:00.962458 [NOTICE] switch_rtp.c:1132 Auto Changing 
stun/rtp/dtls port from99.8.141.165:64234 
<http://137.79.217.63:64234/>to192.168.239.1:64235 
<http://192.168.239.1:64235/>
2014-03-12 15:24:01.003229 [NOTICE] switch_rtp.c:1132 Auto Changing 
stun/rtp/dtls port from99.8.141.165:64234 
<http://137.79.217.63:64234/>to192.168.239.1:64235 
<http://192.168.239.1:64235/>
2014-03-12 15:24:01.982369 [WARNING] switch_rtp.c:857 
sofia/internal/1003 at 192.168.239.150 <mailto:1003 at 192.168.239.150>got 
stun binding response 487 Role Conflict
2014-03-12 15:24:01.982369 [WARNING] switch_rtp.c:868 Changing role to 
CONTROLLED
2014-03-12 15:24:01.982369 [WARNING] switch_rtp.c:857 
sofia/internal/1003 at 192.168.239.150 <mailto:1003 at 192.168.239.150>got 
stun binding response 487 Role Conflict
2014-03-12 15:24:01.982369 [WARNING] switch_rtp.c:868 Changing role to 
CONTROLLED

Just one more thing wanted to mention is that my clients are running on 
the same subnet as the FreeSWITCH and the FreeSWITCH is running
inside of the Linux CentOS VM. Could the root of the problem be the fact 
that FreeSWICH is running in the VM and ICE tries to use the port
on the VM interface (192.168.239.1 <http://192.168.239.1:64235/>)?

I would greatly appreciate any piece of advise on the subject.

Thanks
Yan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.freeswitch.org/pipermail/freeswitch-dev/attachments/20140313/19807ead/attachment-0001.html