Jain sip how to connect to WiFi in Android
I am developing a softphone using jain sip which should exit except for the following problem: I am using restcomm-android-sdk on android-jain-sip-ri-1.2.233.jar and the problem let's say two clients are client A and client B,
-
If Client A and Client B are using 3G / 4G then everything is working fine as they both can call each other and can call each other correctly here.
-
If client A is using 3G / 4G network and clent B is in open WiFi, then both can call each other, but only client A can hear the voice of client B, client B cannot hear anything.
I think it is something about routing and nat, here is my android manifest
<uses-permission android:name="android.permission.USE_SIP" />
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<uses-permission android:name="android.permission.RECORD_AUDIO" />
<uses-permission android:name="android.permission.MODIFY_AUDIO_SETTINGS" />
<uses-permission android:name="android.permission.READ_CONTACTS" />
<uses-permission android:name="android.permission.READ_CALL_LOG" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.WAKE_LOCK" />
<uses-feature android:name="android.hardware.telephony" android:required="true"/>
<uses-feature android:name="android.hardware.sip.voip" android:required="true" />
<uses-feature android:name="android.hardware.wifi" android:required="true" />
<uses-feature android:name="android.hardware.microphone" android:required="true" />
Can anyone help with this issue?
source to share
NAT might be too restrictive on the public Wi-Fi you are using. Have you tried using non-public Wi-Fi? What SIP server are you using? Are you using RestComm as a server?
To make sure network capture is necessary aka tracehark trace (client side - you can try https://play.google.com/store/apps/details?id=lv.n3o.shark&hl=fr and server side too)
If so (NAT is too restrictive, STUN AND TURN will need to be implemented on the Android client planned in the roadmap). Another option, if you are using RestComm, is to create a conferencing app and both clients call the conferencing app to see if that helps.
Have you tried with both clients on different public Wi-Fi networks?
source to share