jain sip如何在android中连接WiFi

Question

I am developing a softphone using jain sip which is about to complete except the following problem: I am using restcomm-android-sdk on android-jain-sip-ri-1.2.233.jar and the problem is let say two clients are client A and client B ,

1. If client A and client B are using 3G/4G , then everything is working fine as they both can call each other and can here each others voice properly.

2. If client A is using 3G/4G network and clent B is on public WiFi then both can call each other but only client A can hear voice of Client B , client B cannot hear anything.

I think is something relating to 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" />

Could anyone please help in solving this problem?

Answer 1

The NAT may be too restrictive in the public Wifi that you're using. Did you try on a non public wifi ? Which SIP Server do you use ? Do you use RestComm as Server ?

To be sure a network capture aka wireshark trace would needed (on the client side - you can try https://play.google.com/store/apps/details?id=lv.n3o.shark&hl=fr and on the server side too)

If that's the case (NAT too restrictive, STUN And TURN will need to be implemented on the Android client, planned on the roadmap). Another option if you use RestComm is to create a conferencing application and have both clients call the conferencing application to see if that helps.

Did you try with both clients on different public wifi networks ?