search

Wael-Fathallah / imsdroid

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

Wrong IP address in the SDP connection info when using NATT #298

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
What steps will reproduce the problem?
1. Connect an android phone on a NATted network (i.e. phone IP 
address=192.168.1.x, public IP address=79.212.42.xx)
2.Configure imsdroid by enabling NATT with a working STUN server address.
3.From imsdroid start an audio call towards a remote party (es. remote party 
IP=109.32.43.xx).

What is the expected output? What do you see instead?
Once the call is established I expect to hear the voice coming from the remote 
party. I can't hear anything instead.

What version of the product are you using? 
Last version available oh the Android Market (2.0.431)

On what operating system?
Android Froyo 2.2 on LG P500

Please provide any additional information below.
The issue seems to be caused by wrong SDP sent by the NATted client in the 
INVITE message. With the NATT enabled the client should provide the public IP 
address retrieved from the STUN server in the connection information, like the 
following:

c=IN IP4 79.212.42.xx
m=audio ...

The client provides its local address instead even if the NATT is enabled:

c=IN IP4 192.168.1.xx
m=audio ...

By doing this the remote party will try to send the audio packets to the local 
address(192.168.1.xx) instead of the public address of the NATted client 
(79.212.42.xx).

I also tried the same thing using Boghe and iDoubts and they both act well in 
this scenario, providing the correct address in the sdp body. Only imsdroid 
seems to be affected by this issue.

Original issue reported on code.google.com by massimo....@gmail.com on 27 Oct 2011 at 6:55

GoogleCodeExporter commented 9 years ago 
Please provide network trace with both SIP and STUN2 packets. Please note that 
we use STUN2 not STUN1 and many public server don't support this version.

Original comment by boss...@yahoo.fr on 21 Nov 2011 at 6:20

GoogleCodeExporter commented 9 years ago 
I also met this problem, the attachment is sip and stun packets.

Original comment by liuyueji...@gmail.com on 30 Nov 2011 at 1:33

Attachments:

GoogleCodeExporter commented 9 years ago 
Fixed by IMSDroid 2.0.481

Original comment by boss...@yahoo.fr on 28 Feb 2012 at 12:03