Open Source Messenger App For Android - Real-time Messaging, Voice and Video Calls

mesibo

Last update: Dec 7, 2022

Related tags

Chat & Messaging messenger-app-android

Overview

Mesibo Messenger for Android

Mesibo Messenger is an open-source app with real-time messaging, voice and video call features. This repo contains the source code for Mesibo Messenger App for Android. The GitHub repository for iOS version is here.

Features

One-on-one messaging and Group chat
High quality voice and video calling
Rich messaging (text, picture, video, audio, other files)
Encryption
Location sharing
Message status and typing indicators
Online status (presence) and real-time profile update
Push notifications

Latest versions are also available from Google Play Store OR Apple AppStore

Prebuilt Messenger Apps

If you prefer to try Pre-built messenger apps instead of building it, you can download it from:

Generating OTP for the demo

The messenger App requires a valid phone number and OTP to login. Note that, we do not send OTP for App login. Instead, you can generate OTP for any number from the mesibo console

Note that, all the users are private to your app/account. The demo app can not see or communicate with users from other apps. Also, the demo app uses contact synchronization to find other users of your app and hence ensure to use the correct phone number and other users are in your phone book.

Documentation

The documentation for the messenger is available here - A fully featured WhatsApp clone using mesibo

It describes

Compilation Instructions (Trivial though)
Download backend source code and host it on your server (the default one is located on the mesibo server)
Hosting entire real-time messaging and call server in your premise
Other Customizations and Rebranding

Downloading the Source Code

Clone the Repository (Recommended)

If you have git installed, this is a recommended approach as you can quickly sync and stay up to date with the latest version. This is also a preferred way of downloading the code if you decide to contribute to the project.

To download, open a terminal and issue following commands:

$ mkdir Messenger
$ cd Messenger
$ git clone https://github.com/mesibo/messenger-app-android.git

Download the code as a zip file

You can also download the complete Android Messenger source code as a zip file. Although simple, the downsize of this approach is that you will have to download the complete source code everytime it is updated on the repository.

Stay Up-to-date

Whatever approach you take to download the code, it is important to stay up-to-date with the latest changes, new features, fixes etc. Ensure to Star(*) the project on GitHub to get notified whenever the source code is updated.

Build and Run

Before we dive into building and running a fully featured Messenger for Android, ensure that you've read the following.

Latest Android Studio Installed
An Android Device

Building the code is as simple as:

Launch Android Studio
Open the project from the folder where you have downloaded the code using menu File -> Open
Build using menu Build -> Rebuild Project
It may take a while to build the project for the first time.
Once the build is over, run on the device using menu Run -> Run (app)
That's it, you should see the welcome screen like below.

Login using your phone number and OTP from the mesibo console. You can even start using the app you've just built to communicate with your family and friends.

Key SDKs user in this project

These apps use following Mesibo SDKs.

Mesibo SDK
Mesibo Messaging UI Module
Mesibo Call UI Module

These apps also use following third party libraries/services.

Google Maps and Google Places SDKs for Geolocation integration

Backend

The backend code is here https://github.com/mesibo/messenger-app-backend

Documentation & Tutorials

Mesibo Documentation
Mesibo Get Started Guide.
Tutorial - A fully featured WhatsApp clone using mesibo

Comments

I/MesiboJNI: E(0705-191400-027)(7010): *** BUG *** Create client unix socket failed

With Mesibo STATUS_ONLINE, getting: I/MesiboJNI: E(0705-191400-027)(7010): *** BUG *** Create client unix socket failed

This happends when I call the method: mesibo.sendMessage(messageParams, msgid, message);

Mesibo needs better documentation, also check: https://github.com/mesibo/samples/issues/21

I'm having Issues with android 4.4.2 using mesibo android sdk.

opened by kvnramirez 16

What does Mesibo_onConnectionStatus 20 means?

My App is just closing for the connection status 20.

public void Mesibo_onConnectionStatus(int var1) {
        Log.wtf("DO THIS", " WHEN string FAILS");
        if (var1 == 1) {
            this.updateSubTitle(this.mMesiboUIOptions.onlineIndicationTitle);
        } else if (var1 == 6) {
            this.updateSubTitle(this.mMesiboUIOptions.connectingIndicationTitle);
        } else if (var1 == 8) {
            this.updateSubTitle(this.mMesiboUIOptions.noNetworkIndicationTitle);
        } else if (var1 == 20) {
            this.getActivity().finish();
        } else {
            this.updateSubTitle(this.mMesiboUIOptions.offlineIndicationTitle);
        }
    }

I think you should no finish the app. Maybe a nice toast or something would be better.

opened by danieltigse 8

Issue in Messages sending & receiving and Chat list is not coming

I have set up Mesibo Android App & Backend Setup properly, All things are running smoothly but after I message someone then Message are not sending and recant chats are not coming in the list and chat screen, also group chats message saw delivery but not received by group members. What should I do next?? Bcoz I already Check all my backend error_logs, no issues from there, Also I checked the app side.

To check my Mesibo Consol: [email protected] <- this email is I am using for Mesibo consol This is my backend API URL: https://streitmen.com/Mesibo-App/api.php

also i am facing this error [27-May-2021 16:48:12 UTC] other: implode(): Passing glue string after array is deprecated. Swap the parameters in /home/u791210233/domains/streitmen.com/public_html/Mesibo-App/mysqlidb.php on line 1782

opened by nishantmonapara 6
How can I change text on Audio/Video calling screen?

How can I change text on Audio/Video calling screen? It always says "Mesibo Video call"

As far as, I observed the code, I think we can't do that as the project is using decompiled classes and that "mesibo video call" text is inside that.

Is there any way to change?

opened by rashidafzaal 6

Not possible to run on simulator

I had to modify it in build script like this

  splits {
        abi {
            enable true
            reset()
            include 'x86', 'x86_64', 'armeabi', 'armeabi-v7a', 'mips', 'mips64', 'arm64-v8a'
            universalApk true
        }
    }

but even after successfully run it fails at runtime like this:

02/08 10:26:09: Launching app
$ adb install-multiple -r -t /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/resources/instant-run/debug/resources-x86-debug.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/split-apk/debug/dep/dependencies.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/split-apk/debug/slices/slice_2.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/split-apk/debug/slices/slice_1.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/split-apk/debug/slices/slice_0.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/split-apk/debug/slices/slice_3.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/split-apk/debug/slices/slice_5.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/split-apk/debug/slices/slice_6.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/split-apk/debug/slices/slice_4.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/split-apk/debug/slices/slice_7.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/split-apk/debug/slices/slice_9.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/split-apk/debug/slices/slice_8.apk /Users/renetik/Desktop/messenger-app-android/app/build/intermediates/instant-run-apk/debug/app-x86-debug.apk 
Split APKs installed in 12 s 577 ms
$ adb shell am start -n "org.mesibo.messenger/org.mesibo.messenger.StartUpActivity" -a android.intent.action.MAIN -c android.intent.category.LAUNCHER -D
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Waiting for application to come online: org.mesibo.messenger | org.mesibo.messenger.test
Connecting to org.mesibo.messenger
Capturing and displaying logcat messages from application. This behavior can be disabled in the "Logcat output" section of the "Debugger" settings page.
I/System.out: Debugger has connected
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/chatty: uid=10085(org.mesibo.messenger) identical 3 lines
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/chatty: uid=10085(org.mesibo.messenger) identical 1 line
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
Connected to the target VM, address: 'localhost:8611', transport: 'socket'
I/chatty: uid=10085(org.mesibo.messenger) identical 3 lines
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: waiting for debugger to settle...
I/System.out: debugger has settled (1484)
I/esibo.messenge: The ClassLoaderContext is a special shared library.
W/esibo.messenge: JIT profile information will not be recorded: profile file does not exits.
I/chatty: uid=10085(org.mesibo.messenger) identical 10 lines
W/esibo.messenge: JIT profile information will not be recorded: profile file does not exits.
I/InstantRun: starting instant run server: is main process
W/esibo.messenge: Verification of void com.facebook.FacebookSdk$1.<init>() took 111.736ms
E/esibo.messenge: No implementation found for void com.mesibo.api.JNIAPI.set_security(int) (tried Java_com_mesibo_api_JNIAPI_set_1security and Java_com_mesibo_api_JNIAPI_set_1security__I)
D/AndroidRuntime: Shutting down VM
    
    
    --------- beginning of crash
E/AndroidRuntime: FATAL EXCEPTION: main
    Process: org.mesibo.messenger, PID: 6662
    java.lang.UnsatisfiedLinkError: No implementation found for void com.mesibo.api.JNIAPI.set_security(int) (tried Java_com_mesibo_api_JNIAPI_set_1security and Java_com_mesibo_api_JNIAPI_set_1security__I)
        at com.mesibo.api.JNIAPI.set_security(Native Method)
        at com.mesibo.api.Mesibo.setSecureConnection(SourceFile:1369)
        at org.mesibo.messenger.SampleAPI.init(SampleAPI.java:553)
        at org.mesibo.messenger.MainApplication.onCreate(MainApplication.java:66)
        at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1154)
        at android.app.ActivityThread.handleBindApplication(ActivityThread.java:5871)
        at android.app.ActivityThread.access$1100(ActivityThread.java:199)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1650)
        at android.os.Handler.dispatchMessage(Handler.java:106)
        at android.os.Looper.loop(Looper.java:193)
        at android.app.ActivityThread.main(ActivityThread.java:6669)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:493)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:858)
D/NetworkSecurityConfig: No Network Security Config specified, using platform default
E/esibo.messenge: No implementation found for long com.mesibo.api.JNIAPI.timestamp() (tried Java_com_mesibo_api_JNIAPI_timestamp and Java_com_mesibo_api_JNIAPI_timestamp__)
Disconnected from the target VM, address: 'localhost:8611', transport: 'socket'

opened by renetik 6

WhatsApp clone not working

Hello,

I just went through the tutorial, created an account kit account and after I try logging in I get "A system issue occurred. Please try again". In the debug console I see Invalid or missing region code (de) provided.. I don't know if that helps, but I can't use the sample app right now.

Thanks

opened by btastic 5
Messages and conversations are not stored

When I receive new messages in the message list, I tap on the new message, the message view is opened but there is not messages, it's empty. And when I go back from the message view, the message list is empty.

I am calling Mesibo.setDatabase after Mesibo.setAccessToken

Am I missing something?

opened by danieltigse 5

Error getting file from Downloads folder

Device: Galaxy S8 OS: Android 8 Stacktrace:

java.lang.RuntimeException: Failure delivering result ResultInfo{who=null, request=10005, result=-1, data=Intent { dat=content://com.android.providers.downloads.documents/document/raw:/storage/emulated/0/Download/invoice168314951.pdf flg=0x1 }} to activity {com.fomatmedical.febo/com.mesibo.messaging.MessagingActivity}: java.lang.NumberFormatException: For input string: "raw:/storage/emulated/0/Download/invoice168314951.pdf"
        at android.app.ActivityThread.deliverResults(ActivityThread.java:4489)
        at android.app.ActivityThread.handleSendResult(ActivityThread.java:4532)
        at android.app.ActivityThread.-wrap20(Unknown Source:0)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1752)
        at android.os.Handler.dispatchMessage(Handler.java:105)
        at android.os.Looper.loop(Looper.java:164)
        at android.app.ActivityThread.main(ActivityThread.java:6938)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.Zygote$MethodAndArgsCaller.run(Zygote.java:327)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1374)
     Caused by: java.lang.NumberFormatException: For input string: "raw:/storage/emulated/0/Download/invoice168314951.pdf"
        at java.lang.Long.parseLong(Long.java:590)
        at java.lang.Long.valueOf(Long.java:804)
        at com.mesibo.mediapicker.e.a(SourceFile:296)
        at com.mesibo.mediapicker.MediaPicker.processOnActivityResult(SourceFile:1547)
        at com.mesibo.messaging.MessagingActivity.onActivityResult(MessagingActivity.java:1675)
        at android.app.Activity.dispatchActivityResult(Activity.java:7548)

Occurs when you chose a file from the Downloads section in the file picker

opened by danieltigse 4

Wrong User status inside console

When I look inside the console, I see more than 200 concurrent users which is not correct. I know because I am managing the online users on my server as well.

I think when a user comes online, it gets recorded and if the device gets offline then that user's status does not get updated until he comes online again. And this is adding up concurrent users count inside the console stats.

Let me know the correct reason if I am wrong. If I am correct, Do you have any plans to fix this? Will this affect the free tier limit?

If I have raised the issue at the wrong place, let me know I'll move to correct place.

opened by karan1213 3
Send button not enabled
I am trying to chat with some user that is registered as user in the dashboard but:

When I use this line: MesiboUI.launchMessageView(context, "[email protected]", 0) the Message View doesn't open. But If I send a message from the dashboard and then use the line again the Message View opens.

When the message View opens I can send messages because the send button doesn't appear.
opened by danieltigse 3
Can this app be integrated in my other application?

Can I integrate this app with my other application which already has users How can I do it? how can I use users of that application with it (being synced with mesibo user) any guide for setting my own media server? Really looking forward for support

Regards

opened by haseebehsan 3
Host app on F-Droid
It would be nice if you could also host this app on F-Droid. F-Droid is an alternative play store primarily focused around free and open-source software (FOSS). It hosts a myriad of applications that involve privacy and secure communciations.

In case you're not familiar with F-Droid, I'm leaving these links here for the sake of convenience:

Submitting to F-Droid Quick Start Guide

Setup an F-Droid App Repo
opened by ghost 0
Can't register with phone number

java.lang.nullpointerexception: attempt to invoke virtual method 'boolean java.lang.string.equalsignorecase(java.lang.string)' on a null object reference at org.niloygazi.wirelesschat.sampleapi.parseresponse(sampleapi.java:327) at org.niloygazi.wirelesschat.sampleapi.access$200(sampleapi.java:24) at org.niloygazi.wirelesschat.sampleapi$responsehandler$1.run(sampleapi.java:95) at android.os.handler.handlecallback(handler.java:883) at android.os.handler.dispatchmessage(handler.java:100) at android.os.looper.loop(looper.java:224) at android.app.activitythread.main(activitythread.java:7592) at java.lang.reflect.method.invoke(native method) at com.android.internal.os.runtimeinit$methodandargscaller.run(runtimeinit.java:539) at com.android.internal.os.zygoteinit.main(zygoteinit.java:950)

screenshot of the bug:-

opened by niloygazi4 0
HW NS not supported error for video call

Devices are OnePlus7 and Samsung Galaxy s8 I am using latest version: implementation 'com.mesibo.api:mesibo:1.0.90' implementation 'com.mesibo.api:ui:1.1.32' implementation 'com.mesibo.api:calls:1.0.75'

Getting issue on Samsung Galaxy s8 device while receiving the vedio call.

2020-05-20 00:07:22.712 9687-9687/com.digipathy.healthcare E/org.webrtc.Logging: JavaAudioDeviceModule: HW NS not supported 2020-05-20 00:07:22.916 9687-10615/com.digipathy.healthcare E/rtpsender.cc: (line 559): Tried to get DTMF sender from video sender. 2020-05-20 00:07:22.918 9687-10615/com.digipathy.healthcare E/rtpsender.cc: (line 559): Tried to get DTMF sender from video sender. 2020-05-20 00:07:22.921 9687-10615/com.digipathy.healthcare E/rtpsender.cc: (line 559): Tried to get DTMF sender from video sender. 2020-05-20 00:07:33.202 9687-10620/com.digipathy.healthcare E/libEGL: call to OpenGL ES API with no current context (logged once per thread) 2020-05-20 00:07:33.207 9687-10621/com.digipathy.healthcare E/libEGL: call to OpenGL ES API with no current context (logged once per thread) 2020-05-20 00:07:41.591 9687-9687/com.digipathy.healthcare E/JavaAudioDeviceModule: HW NS not supported 2020-05-20 00:07:41.676 9687-10922/com.digipathy.healthcare E/rtpsender.cc: (line 559): Tried to get DTMF sender from video sender. 2020-05-20 00:07:41.676 9687-10922/com.digipathy.healthcare E/rtpsender.cc: (line 559): Tried to get DTMF sender from video sender. 2020-05-20 00:07:41.679 9687-10922/com.digipathy.healthcare E/rtpsender.cc: (line 559): Tried to get DTMF sender from video sender. 2020-05-20 00:07:46.012 9687-10922/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"sdp":"v=0\r\no=- 5266899959990388347 2 IN IP4 127.0.0.1\r\ns=-\r\nt=0 0\r\na=group:BUNDLE 0 1\r\na=msid-semantic: WMS ARDAMS\r\nm=video 9 UDP\/TLS\/RTP\/SAVPF 96 97 98 99 100 101 127 123 125 124\r\nc=IN IP4 0.0.0.0\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=ice-ufrag:o1sR\r\na=ice-pwd:hL8cJ7TM0CXkIYKev7IbZQKG\r\na=ice-options:trickle renomination\r\na=fingerprint:sha-256 D2:85:43:70:A4:1B:85:56:4A:77:D0:66:22:6D:26:A3:67:B3:2C:65:54:78:7E:48:7D:1D:DE:60:7E:67:66:22\r\na=setup:actpass\r\na=mid:0\r\na=extmap:2 urn:ietf:params:rtp-hdrext:toffset\r\na=extmap:3 http:\/\/www.webrtc.org\/experiments\/rtp-hdrext\/abs-send-time\r\na=extmap:4 urn:3gpp:video-orientation\r\na=extmap:5 http:\/\/www.ietf.org\/id\/draft-holmer-rmcat-transport-wide-cc-extensions-01\r\na=extmap:6 http:\/\/www.webrtc.org\/experiments\/rtp-hdrext\/playout-delay\r\na=extmap:7 http:\/\/www.webrtc.org\/experiments\/rtp-hdrext\/video-content-type\r\na=extmap:8 http:\/\/www.webrtc.org\/experiments\/rtp-hdrext\/video-timing\r\na=extmap:10 http:\/\/tools.ietf.org\/html\/draft-ietf-avtext-framemarking-07\r\na=extmap:9 urn:ietf:params:rtp-hdrext:sdes:mid\r\na=sendrecv\r\na=msid:ARDAMS ARDAMSv0\r\na=rtcp-mux\r\na=rtcp-rsize\r\na=rtpmap:96 VP8\/90000\r\na=rtcp-fb:96 goog-remb\r\na=rtcp-fb:96 transport-cc\r\na=rtcp-fb:96 ccm fir\r\na=rtcp-fb:96 nack\r\na=rtcp-fb:96 nack pli\r\na=rtpmap:97 rtx\/90000\r\na=fmtp:97 apt=96\r\na=rtpmap:98 VP9\/90000\r\na=rtcp-fb:98 goog-remb\r\na=rtcp-fb:98 transport-cc\r\na=rtcp-fb:98 ccm fir\r\na=rtcp-fb:98 nack\r\na=rtcp-fb:98 nack pli\r\na=rtpmap:99 rtx\/90000\r\na=fmtp:99 apt=98\r\na=rtpmap:100 H264\/90000\r\na=rtcp-fb:100 goog-remb\r\na=rtcp-fb:100 transport-cc\r\na=rtcp-fb:100 ccm fir\r\na=rtcp-fb:100 nack\r\na=rtcp-fb:100 nack pli\r\na=fmtp:100 level-asymmetry-allowed=1;packetization-mode=1;profile-level-id=42e01f\r\na=rtpmap:101 rtx\/90000\r\na=fmtp:101 apt=100\r\na=rtpmap:127 red\/90000\r\na=rtpmap:123 rtx\/90000\r\na=fmtp:123 apt=127\r\na=rtpmap:125 ulpfec\/90000\r\na=rtpmap:124 flexfec-03\/90000\r\na=rtcp-fb:124 goog-remb\r\na=rtcp-fb:124 transport-cc\r\na=fmtp:124 repair-window=10000000\r\na=ssrc-group:FID 3229622911 1745154725\r\na=ssrc-group:FEC-FR 3229622911 1099394611\r\na=ssrc:3229622911 cname:ie\/HDz18I9hhnd4w\r\na=ssrc:3229622911 msid:ARDAMS ARDAMSv0\r\na=ssrc:3229622911 mslabel:ARDAMS\r\na=ssrc:3229622911 label:ARDAMSv0\r\na=ssrc:1745154725 cname:ie\/HDz18I9hhnd4w\r\na=ssrc:1745154725 msid:ARDAMS ARDAMSv0\r\na=ssrc:1745154725 mslabel:ARDAMS\r\na=ssrc:1745154725 label:ARDAMSv0\r\na=ssrc:1099394611 cname:ie\/HDz18I9hhnd4w\r\na=ssrc:1099394611 msid:ARDAMS ARDAMSv0\r\na=ssrc:1099394611 mslabel:ARDAMS\r\na=ssrc:1099394611 label:ARDAMSv0\r\nm=audio 9 UDP\/TLS\/RTP\/SAVPF 111 103 104 9 102 0 8 106 105 13 110 112 113 126\r\nc=IN IP4 0.0.0.0\r\na=rtcp:9 IN IP4 0.0.0.0\r\na=ice-ufrag:o1sR\r\na=ice-pwd:hL8cJ7TM0CXkIYKev7IbZQKG\r\na=ice-options:trickle renomination\r\na=fingerprint:sha-256 D2:85:43:70:A4:1B:85:56:4A:77:D0:66:22:6D:26:A3:67:B3:2C:65:54:78:7E:48:7D:1D:DE:60:7E:67:66:22\r\na=setup:actpass\r\na=mid:1\r\na=extmap:1 urn:ietf:params:rtp-hdrext:ssrc-audio-level\r\na=extmap:9 urn:ietf:params:rtp-hdrext:sdes:mid\r\na=sendrecv\r\na=msid:ARDAMS ARDAMSa0\r\na=rtcp-mux\r\na=rtpmap:111 opus\/48000\/2\r\na=rtcp-fb:111 transport-cc\r\na=fmtp:111 minptime=10;useinbandfec=1\r\na=rtpmap:103 ISAC\/16000\r\na=rtpmap:104 ISAC\/32000\r\na=rtpmap:9 G722\/8000\r\na=rtpmap:102 ILBC\/8000\r\na=rtpmap:0 PCMU\/8000\r\na=rtpmap:8 PCMA\/8000\r\na=rtpmap:106 CN\/32000\r\na=rtpmap:105 CN\/16000\r\na=rtpmap:13 CN\/8000\r\na=rtpmap:110 telephone-event\/48000\r\na=rtpmap:112 telephone-event\/32000\r\na=rtpmap:113 telephone-event\/16000\r\na=rtpmap:126 telephone-event\/8000\r\na=ssrc:1270607778 cname:ie\/HDz18I9hhnd4w\r\na=ssrc:1270607778 msid:ARDAMS ARDAMSa0\r\na=ssrc:1270607778 mslabel:ARDAMS\r\na=ssrc:1270607778 label:ARDAMSa0\r\n","type":"offer"} 2020-05-20 00:07:46.084 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 11 2020-05-20 00:07:46.084 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 11 2020-05-20 00:07:46.086 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 11 2020-05-20 00:07:46.089 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 13 2020-05-20 00:07:46.089 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 13 2020-05-20 00:07:46.091 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:3984205710 1 udp 2122131711 2402:3a80:cea:b51c::51b3:ed4e 47963 typ host generation 0 ufrag o1sR network-id 4 network-cost 900"} 2020-05-20 00:07:46.091 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 13 2020-05-20 00:07:46.092 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:2833057566 1 udp 2121998079 10.90.180.181 46923 typ host generation 0 ufrag o1sR network-id 3 network-cost 900"} 2020-05-20 00:07:46.095 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:559267639 1 udp 2121940223 ::1 58098 typ host generation 0 ufrag o1sR network-id 2"} 2020-05-20 00:07:46.098 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.098 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:1510613869 1 udp 2121867007 127.0.0.1 39771 typ host generation 0 ufrag o1sR network-id 1"} 2020-05-20 00:07:46.118 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.118 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.118 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.140 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 22 2020-05-20 00:07:46.140 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.140 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 130): TCP bind failed with error 22 2020-05-20 00:07:46.140 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.142 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 22 2020-05-20 00:07:46.142 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.143 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 130): TCP bind failed with error 22 2020-05-20 00:07:46.143 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.147 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 115 2020-05-20 00:07:46.147 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.147 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 130): TCP bind failed with error 13 2020-05-20 00:07:46.147 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.153 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52bad900:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:46.154 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 181): TCP connect failed with error 22 2020-05-20 00:07:46.154 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.165 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:842163049 1 udp 1685790463 1.39.162.20 49753 typ srflx raddr 10.90.180.181 rport 46923 generation 0 ufrag o1sR network-id 3 network-cost 900"} 2020-05-20 00:07:46.169 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.171 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 130): TCP bind failed with error 115 2020-05-20 00:07:46.171 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.171 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 115 2020-05-20 00:07:46.171 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.172 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 130): TCP bind failed with error 115 2020-05-20 00:07:46.173 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.173 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 130): TCP bind failed with error 115 2020-05-20 00:07:46.173 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.173 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 13 2020-05-20 00:07:46.173 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.173 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 13 2020-05-20 00:07:46.173 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.174 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 13 2020-05-20 00:07:46.174 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.174 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 13 2020-05-20 00:07:46.174 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.175 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 130): TCP bind failed with error 13 2020-05-20 00:07:46.175 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.175 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 130): TCP bind failed with error 13 2020-05-20 00:07:46.175 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.179 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 52): UDP bind failed with error 115 2020-05-20 00:07:46.179 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.179 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 130): TCP bind failed with error 13 2020-05-20 00:07:46.179 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.184 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c55700:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:46.187 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c56500:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:46.189 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 181): TCP connect failed with error 22 2020-05-20 00:07:46.189 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.192 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 181): TCP connect failed with error 22 2020-05-20 00:07:46.192 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 341): Failed to create TURN client socket 2020-05-20 00:07:46.192 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 77): TCP bind failed with error 22 2020-05-20 00:07:46.193 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:430101239 1 tcp 1518283007 2402:3a80:cea:b51c::53 9 typ host tcptype active generation 0 ufrag o1sR network-id 7 network-cost 50"} 2020-05-20 00:07:46.194 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 77): TCP bind failed with error 22 2020-05-20 00:07:46.195 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:183835596 1 tcp 1518214911 192.168.43.1 9 typ host tcptype active generation 0 ufrag o1sR network-id 6 network-cost 50"} 2020-05-20 00:07:46.199 9687-10920/com.digipathy.healthcare E/basicpacketsocketfactory.cc: (line 77): TCP bind failed with error 22 2020-05-20 00:07:46.200 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:2347472800 1 tcp 1518086399 2402:3a80:1def:153c::39d9:ddf3 9 typ host tcptype active generation 0 ufrag o1sR network-id 5 network-cost 900"} 2020-05-20 00:07:46.204 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:1876313031 1 tcp 1517960447 ::1 59897 typ host tcptype passive generation 0 ufrag o1sR network-id 2"} 2020-05-20 00:07:46.206 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:344579997 1 tcp 1517887231 127.0.0.1 44069 typ host tcptype passive generation 0 ufrag o1sR network-id 1"} 2020-05-20 00:07:46.348 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.368 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.368 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.373 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:2787059734 1 udp 41755903 64.233.189.86 30108 typ relay raddr 2402:3a80:cea:b51c::51b3:ed4e rport 47963 generation 0 ufrag o1sR network-id 4 network-cost 900"} 2020-05-20 00:07:46.374 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:2787059734 1 udp 41625087 64.233.189.86 30941 typ relay raddr 1.39.162.20 rport 49753 generation 0 ufrag o1sR network-id 3 network-cost 900"} 2020-05-20 00:07:46.403 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52bad900:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:46.419 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.430 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:4231669940 1 udp 1685921535 1.39.173.7 28757 typ srflx raddr 2402:3a80:cea:b51c::51b3:ed4e rport 47963 generation 0 ufrag o1sR network-id 4 network-cost 900"} 2020-05-20 00:07:46.435 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c55700:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:46.438 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c56500:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:46.487 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:2599754389 1 udp 24847359 64.233.189.127 30495 typ relay raddr 1.39.162.20 rport 49765 generation 0 ufrag o1sR network-id 3 network-cost 900"} 2020-05-20 00:07:46.494 9687-10622/com.digipathy.healthcare E/MesiboCallManager: Sending SDP: {"type":"candidate","label":0,"id":"0","candidate":"candidate:3902592230 1 udp 24978175 64.233.189.86 26940 typ relay raddr 2402:3a80:cea:b51c::51b3:ed4e rport 60427 generation 0 ufrag o1sR network-id 4 network-cost 900"} 2020-05-20 00:07:46.849 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.869 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.903 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52bad900:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:46.920 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:46.935 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c55700:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:46.939 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c56500:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:47.851 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:47.872 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:47.873 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:47.904 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52bad900:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:47.920 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:47.936 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c55700:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:47.940 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c56500:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:49.855 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:49.872 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:49.874 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:49.904 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52bad900:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:49.920 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:49.937 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c55700:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:49.942 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c56500:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:53.856 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:53.875 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:53.906 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52bad900:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:53.921 9687-10920/com.digipathy.healthcare E/stunport.cc: (line 551): sendto : [0x00000016] Invalid argument 2020-05-20 00:07:53.938 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c55700:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:53.945 9687-10920/com.digipathy.healthcare E/turnport.cc: (line 807): Port[52c56500:0:1:0:relay:Net[lo:127.0.0.x/8:Loopback:id=1]]: Failed to send TURN message, error: 22 2020-05-20 00:07:57.530 9687-10927/com.digipathy.healthcare E/libEGL: call to OpenGL ES API with no current context (logged once per thread) 2020-05-20 00:07:57.534 9687-10928/com.digipathy.healthcare E/libEGL: call to OpenGL ES API with no current context (logged once per thread)

opened by chetanurmaliya 0