search

cxueqin / idoubs

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

H.264 issue interacting with linphone #51

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
a) Before posting your issue you MUST answer to the questions otherwise it
will be rejected (invalid status) by us
b) Please check the issue tacker to avoid duplication
c) Please provide network capture (wireshark) or Android log (DDMS output)
if you want quick response

What steps will reproduce the problem?
1. only enable h264 video codec (either profile 1, 2, or 3)
2. make video call to linphone client
3. linphone client does not show video correctly

What is the expected output? What do you see instead?
linphone client does not show video correctly but iDoubs can show linphone's 
video correctly. If using h.263, both way video look good. 

What version of the product or source code revision are you using? On what
operating system?
Latest doubango/idoubs 2.x version on iPad 2.

Please provide any additional information below.
we also tried to use Imsdroid (same doubango code) to call linphone and did not 
find the problem. Imsdroid to iDoubs also works well. By using Wireshark RTP 
Stream Analysis tool, noticed that there are a lot of sequence number errors in 
the direction from iDoubs to linphone. They arrived not at the same sequence as 
sequence number order. We also tested between imsdroid and idoubs. It does not 
have such problem.

Original issue reported on code.google.com by xiangch...@gmail.com on 14 Jul 2011 at 6:04

Attachments:

GoogleCodeExporter commented 9 years ago 
Sorry. I just saw issue 49 which is same as this one. The new finding is the 
sequence numbers are not in order. Also compared trace for iDoubs to Boghe 
video call and there are also a lot of out-of-sequence packets but it seems 
Boghe somehow can handle it.

Original comment by xiangch...@gmail.com on 14 Jul 2011 at 7:43

GoogleCodeExporter commented 9 years ago 
Issue 49 has been merged into this issue.

Original comment by boss...@yahoo.fr on 15 Jul 2011 at 3:47

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 15 Jul 2011 at 3:47

GoogleCodeExporter commented 9 years ago

Original comment by boss...@yahoo.fr on 6 Aug 2013 at 7:22