fanyapeng / doubango

Automatically exported from code.google.com/p/doubango
0 stars 1 forks source link

Doubango Clients may not respond properly to NACK requests #407

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. Making a Call using a SIPML5 endpoint and a doubango endpoint, in this case 
IMSDroid.

What is the expected output? What do you see instead?
Expected: Video/Audio communications with minimal frame dropping, artifacting, 
and freezing. Endpoints should correct the artifacting, frame dropping, and 
freezing by themselves. 

Actual: Video/Audio communications with frequent frame dropping, artifacting, 
and freezing. Endpoints appear to not be dealing with these items properly. 
SIPML5 client experiences remote video freezing, and spams NACK requests to the 
doubango client (IMSdroid) forcing download on the doubango client to 3-5 Mb/s. 
Freezing is corrected after a period of 30-50 seconds, but quickly returns. 

I should also note that it appears to get worse as the duration of the call 
goes on. 

What version of the product are you using? On what operating system?
Up to date SIPML5 client embedded in a chromium client. 
IMSDroid-2.548.870 on a Nexus 7 running android 4.4.2. 
IMSDroid is configured with: 
CIF resolution
Zero Video Artifacts Enabled
VP8,PCMA,PCMU codecs

Using WebRTC2SIP with mediacoder disabled for the SIPML5 endpoint. 
Using just SIP for Doubango endpoints.

Please provide any additional information below.
Using two SIPML5 clients, the Audio/Video communication is flawless. I have 
also tested this with the desktop windows build of Boghe, and the issue still 
persisted. So I can assume that it is most likely a Doubango problem.

Attached is a listing with snippets of the WebRTC2SIP logs.

Has anyone seen this before, or can someone provide insight?

Appreciate the help!

Original issue reported on code.google.com by da...@students.pti.edu on 24 Oct 2014 at 2:54

Attachments: