#920 NAT Issue - Internal IP

[Anonymous]

Originally created by: maerte...@gmail.com

What steps will reproduce the problem?
1.
2.
3.

What is the expected output? What do you see instead?
Sipdroid works fine, the internal IP is correctly reported to the server. Using exactly the same settings in csip the public internet address is reported to the server and not the local ip

What version of the product are you using? On what operating system?
Android 2.2 latest public build

Please provide any additional information below.
None of the ICE/Stun options make a difference. Port number on UDP is correct. The same settings in sipdroid correctly transmit the local IP. Same Wifi network

[Anonymous]

Originally posted by: r3gis...@gmail.com

In this kind of case STUN *MUST* be disabled.

Then the sip client will try to do it's best to announce the IP as seen by the server. Even without STUN and ICE pjsip (the sip stack on which CSipSimple is based), can rewrite contact IP with public IP. This is a feature of the pjsip stack.
By default this feature is enabled cause in most case it helps a lot.

However you can disable it. To do so :
* Convert you account into an expert account (see the wiki page about ExpertSettingMode).
* Disable the option "Allow contact rewrite".

To ensure that the pjsip stack will flush your public IP, go in csipsimple settings and press back (it will restart the stack ;) ).

That's it.
In the future, pjsip 2.0 will provide a way to split for each account STUN settings. Cause for now the problem is that the sip stack only consider one public IP.
See issue 345.

Status: WrongConfig

[Anonymous]

Originally posted by: maerte...@gmail.com

Brillant! That's fixed it...
Top App. Stick a donate button up and I would be more than happy to pay for the app!

[Anonymous]

Originally posted by: r3gis...@gmail.com

:), there is a donate link in wiki (https://code.google.com/p/csipsimple/wiki/Donate?wl=en).

But your feedback is as valuable as money :). It helps to improve the app and that's my only goal (I do this app just for my pleasure with no commercial goals ;) ).

Now it make one supplementary vote for the upcoming stun per account feature of pjsip2.0 so I'll try to integrate that as soon as possible.

[Anonymous]

Originally posted by: maerte...@gmail.com

Spoke too soon
Okay new one for you...
It works great with 1 account IP is the local one on the server.
However. add another account with exactly the same settings and it goes back to reporting the public ip.
Remove the additional account and refresh - Back to local ip again!

[Anonymous]

Originally posted by: maerte...@gmail.com

sorry just re-read your comment, so I guess we can't do anything about this until pjsip2.0?

[Anonymous]

Originally posted by: r3gis...@gmail.com

Yes indeed, it's due to the fact the pjsip stack consider only one public IP. So it shares the known public IP to all accounts ... unfortunately.
For now, there is no real reliable solution for that. Some workaround that could work depending your configuration is to "Force contact" by putting a fixed IP SIP contact there. But the problem is that it requires a fixed IP addressing plan :S.

So for now, if you have one external SIP provider and one internal (on your lan) SIP provider, no real way to solve this problem by a clean way.