search

just50415 / android-rcs-ims-stack

Automatically exported from code.google.com/p/android-rcs-ims-stack
0 stars 0 forks source link

a=recvonly causes the TCP connection problem #43

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1.some offline display/delivery reports are waiting for client
2.the client goes online
3.the client does not get display/delivery reports

What is the expected output? What do you see instead?

The client should get display/delivery reports. 
According to our analysis, it is SBC that rejects 'TCP SYN' which is used for 
TCP connection establishment. 
Then we contact with the SBC guys. They explain us that the client uses 
a=recvonly in SDP for session negotiations, and this a=recvonly cannot be used 
for TCP connection, because TCP connection is both directions connection, not 
receive only.

Do you agree their explanation?

What version of the product are you using? On what operating system?

Please provide any additional information below.
We tested it in a real IMS/RCSe environment.

Original issue reported on code.google.com by lin.ha...@gmail.com on 30 Dec 2011 at 9:07

GoogleCodeExporter commented 8 years ago 
above the TCP connection is used for MSRP which is used for delivering offline 
delivery/display reports

Original comment by lin.ha...@gmail.com on 30 Dec 2011 at 9:09

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
it is definitely SBC problem. please close this issue.

Original comment by lin.ha...@gmail.com on 3 Feb 2012 at 8:26

GoogleCodeExporter commented 8 years ago 
Ok thks

Original comment by jmauffret@gmail.com on 10 Feb 2012 at 6:06