Android Tutorial [B4X] Simple audio call over internet with own TURN/relay server

Hi everyone,

I posted a thread long ago about the audio/video calling over the internet. Here is a simple example of how you can call almost (will discuss below) realtime.

Why only a simple audio calling example while I said that I will post both audio and video calling examples?
While working on this project I realized that a good quality audio/video calling application with all required functionalities needs huge time and effort. Because like whatsapp, google duo if you want faster calling app then you have to compress the audio/video buffer before sending and decompress the audio/video buffer after receiving. This may sound like a simple byte compression job but it isn't. Compressing/decompressing audio/video buffer in realtime and playing requires lots of research about audio/video processing, audio/video codes, how conversion works, and many other things. Thus I decided to post a simple example of how it works for free and will post a full example that will be chargeable. That will have lots of functionalities, check below to know more.

This will work,

1. From Android to Android
2. From Android to iOS
3. From iOS to Android
4. From iOS to iOS

Functionalities:

1. Apps:
   1. List all the connected users and update in realtime
   2. Call any connected users
   3. Check if the user is busy or not
   4. Show custom in-app incoming call screen with accept/reject button
   5. Play ringtone for incoming call
   6. Automatic screen dimming while talking
   7. Call accepted/rejected/ended/busy/offline status
   8. Call timer
   9. Incoming call notification while the app is in the background (Android)
   10. Noise cancellation, Acoustic echo cancellation, Automatic gain control (Android)
2. Server:
   1. Can handle multiple connections simultaneously.
   2. Deliver call requests and status
   3. Broadcast connected user list
   4. Check if the callee is busy or not
   5. Work as a relay server for delivering audio buffers to respective clients

Limitations:

1. Few milliseconds delay in delivering audio buffer (sometimes). Because,
   1. The example apps are processing uncompressed audio buffer (24Kb-30Kb buffer per seconds)
   2. The test server (you can find the IP inside the project) has been configured to limit bandwidth usage for testing purposes.
2. No notifications when the app is closed. I haven't included that because it's a simple example.

How to run:

1. App:
   1. Download latest socket.io client library wrapper (B4A / B4I)
   2. Download, extract and run.
   3. For ios, you need a working developer certificate because it will not work on the simulator.
2. Server: The test server is always up. If you want to test with the test server then just run the app. If you want to run it on your local server, then
   1. Install Node.js
   2. Extract the server code
   3. Open terminal/cmd and navigate to the folder where you have extracted the code
   4. Run npm install (it will take few minutes)
   5. Run node app.js
   6. That's it.

Functionalities that the full example will have,

1. Audio/Video call
2. End to end encryption
3. Switching audio output between speakers/headphone
4. Faster calling even with low internet speed (5-10kbps)
5. Incoming calling screen that will show even when the app is not running.
6. Register a name for your device. So the other users can see who is calling
7. Example of STUN server as default server and fallback to TURN server
8. Example of Socket.IO server along with WebSocket Server
9. *Maybe group calling.

The full example will be chargeable. I haven't decided the amount yet. It will be between $50 - $100.

Though the test server has bandwidth limitations, it can handle more than 100-200 users.

Download the test apk for testing.

 

[José A.]

And where do I put it, do you know anything about this project?
Thank you very much.

 

[omarruben]

Hi everyone,

I posted a thread long ago about the audio/video calling over the internet. Here is a simple example of how you can call almost (will discuss below) realtime.

Why only a simple audio calling example while I said that I will post both audio and video calling examples?
While working on this project I realized that a good quality audio/video calling application with all required functionalities needs huge time and effort. Because like whatsapp, google duo if you want faster calling app then you have to compress the audio/video buffer before sending and decompress the audio/video buffer after receiving. This may sound like a simple byte compression job but it isn't. Compressing/decompressing audio/video buffer in realtime and playing requires lots of research about audio/video processing, audio/video codes, how conversion works, and many other things. Thus I decided to post a simple example of how it works for free and will post a full example that will be chargeable. That will have lots of functionalities, check below to know more.

This will work,

1. From Android to Android
2. From Android to iOS
3. From iOS to Android
4. From iOS to iOS

Functionalities:

1. Apps:
   1. List all the connected users and update in realtime
   2. Call any connected users
   3. Check if the user is busy or not
   4. Show custom in-app incoming call screen with accept/reject button
   5. Play ringtone for incoming call
   6. Automatic screen dimming while talking
   7. Call accepted/rejected/ended/busy/offline status
   8. Call timer
   9. Incoming call notification while the app is in the background (Android)
   10. Noise cancellation, Acoustic echo cancellation, Automatic gain control (Android)
2. Server:
   1. Can handle multiple connections simultaneously.
   2. Deliver call requests and status
   3. Broadcast connected user list
   4. Check if the callee is busy or not
   5. Work as a relay server for delivering audio buffers to respective clients

Limitations:

1. Few milliseconds delay in delivering audio buffer (sometimes). Because,
   1. The example apps are processing uncompressed audio buffer (24Kb-30Kb buffer per seconds)
   2. The test server (you can find the IP inside the project) has been configured to limit bandwidth usage for testing purposes.
2. No notifications when the app is closed. I haven't included that because it's a simple example.

How to run:

1. App:
   1. Download latest socket.io client library wrapper (B4A / B4I)
   2. Download, extract and run.
   3. For ios, you need a working developer certificate because it will not work on the simulator.
2. Server: The test server is always up. If you want to test with the test server then just run the app. If you want to run it on your local server, then
   1. Install Node.js
   2. Extract the server code
   3. Open terminal/cmd and navigate to the folder where you have extracted the code
   4. Run npm install (it will take few minutes)
   5. Run node app.js
   6. That's it.

Functionalities that the full example will have,

1. Audio/Video call
2. End to end encryption
3. Switching audio output between speakers/headphone
4. Faster calling even with low internet speed (5-10kbps)
5. Incoming calling screen that will show even when the app is not running.
6. Register a name for your device. So the other users can see who is calling
7. Example of STUN server as default server and fallback to TURN server
8. Example of Socket.IO server along with WebSocket Server
9. *Maybe group calling.

The full example will be chargeable. I haven't decided the amount yet. It will be between $50 - $100.

Though the test server has bandwidth limitations, it can handle more than 100-200 users.

Download the test apk for testing.

do you have an example for B4j? thank you

 

[Biswajit]

do you have an example for B4j? thank you

Don't use this method (socket.io) for VoIP calling. After some research I found that this is very slow compared to webrtc.

 

[Jmu5667]

Is there a full version of this availble to test ? Is source provided with paid version ?

 

[Biswajit]

Is there a full version of this availble to test ? Is source provided with paid version ?

No, actually I haven't continued this project as I was facing many difficulties so now I'm trying this to implement with webrtc. Once done, will post it here.

 

[Jmu5667]

No, actually I haven't continued this project as I was facing many difficulties so now I'm trying this to implement with webrtc. Once done, will post it here.

Ok, how far did you get ?

 

[Ahmet KOÇ]

There was a sound echo problem on the Android device during the call between IOS and Android. I fixed it by changing it like this.

Use this AVAudioSessionCategoryOptionMixWithOthers value instead of the AVAudioSessionCategoryOptionDefaultToSpeaker value.

-(bool) SetAudioSessionInCall:(bool)enable{
    AVAudioSession *audioSession = [AVAudioSession sharedInstance];
    NSError *err = nil;
    BOOL success;
    if(enable){
        success = [audioSession setCategory:AVAudioSessionCategoryPlayAndRecord mode:AVAudioSessionModeVoiceChat options:AVAudioSessionCategoryOptionMixWithOthers error:&err];
    }else{
        success = [audioSession setCategory:AVAudioSessionCategoryPlayback mode:AVAudioSessionModeDefault options:nil error:&err];
    }
    if (success) {
        success = [audioSession setActive:YES error:&err];
    }
    if (!success) [NSException raise:mad:"" format:mad:"Error setting audio session: %@", err];
    return success;
}

 

[fbritop]

Biswajit​

Did you manage to port this App to WebRTC or the project was abandon?

 

[Biswajit]

Biswajit​

Did you manage to port this App to WebRTC or the project was abandon?

Unfortunately, the project was abandoned.