mesibo / messenger-app-android Goto Github PK

i even changed the url in backend but still the profile picture wont update

Can you explain me how do I get uploadurl and downloadurl? Do I need to implement those URLs in my own server? I can't find documentation about it? Please some help.

Fatal Exception: java.lang.UnsatisfiedLinkError: Native method not found: com.mesibo.api.JNIAPI.set_call_interface:(IJ)V
       at com.mesibo.api.JNIAPI.set_call_interface(SourceFile)
       at com.mesibo.api.Mesibo.setCallInterface + 2632(SourceFile:2632)
       at com.mesibo.calls.MesiboCall.init()
       at com.packagename.Application.mesiboInit + 203(Application.java:203)
       at com.packagename.Application.onCreate + 101(Application.java:101)
       at android.app.Instrumentation.callApplicationOnCreate + 1014(Instrumentation.java:1014)
       at android.app.ActivityThread.handleBindApplication + 4290(ActivityThread.java:4290)
       at android.app.ActivityThread.access$1400 + 143(ActivityThread.java:143)
       at android.app.ActivityThread$H.handleMessage + 1301(ActivityThread.java:1301)
       at android.os.Handler.dispatchMessage + 99(Handler.java:99)
       at android.os.Looper.loop + 137(Looper.java:137)
       at android.app.ActivityThread.main + 4960(ActivityThread.java:4960)
       at java.lang.reflect.Method.invokeNative(Method.java)
       at java.lang.reflect.Method.invoke + 511(Method.java:511)
       at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run + 1038(ZygoteInit.java:1038)
       at com.android.internal.os.ZygoteInit.main + 805(ZygoteInit.java:805)
       at dalvik.system.NativeStart.main(NativeStart.java)

Got this from Firebase crashlytics.
I just enabled proguard with this latest release, do you think proguard would cause this?

I installed the app, entered my phone number and verified it, no issues. Then I try to send messages but they don't arrive. I had to close the app and open it again and then the messages arrived. Any way to fix this?

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.

from 9 September 2019 facebook account kit is deprecated. How to create an alternative?

I installed app on several phones and only 1 contact is showing in the messages while rest of the contacts are not showing

I am trying to chat with some user that is registered as user in the dashboard but:

1. 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.
2. When the message View opens I can send messages because the send button doesn't appear.
   

How can I remove the "Mesibo Video Call" text from her links? Without having to create a new screen.
I tried to make the inheritance of MesiboVideoCallFragment, however whenever the connection is established, I get error and the application closes.

Build failed

ERROR: unable to find valid certification path to requested target
Open File

"open file" take to app level build.gradle Line:
apply from: "https://api.mesibo.com/mesibo.gradle"

Hi,

in the API i can't find anywhere how to customize the encryption method used to send and receive messages. Can you help me ?

I tried to just build the project and it ran into problems already. It can't run on my phone so I had to use the AVD and that went well, except that the first line was already "wrong". Expecting EOP, got plugin: apply plugin: "com.android.application". Got anything to fix this?

Hi,

I am trying to fetch chat list of a user. I was going through API documentation and found this to read session:

Mesibo.ReadDbSession mReadSession = new Mesibo.ReadDbSession(from, 0, null, this);
mReadSession.enableReadReceipt(true);
mReadSession.enableMissedCalls(mShowMissedCalls);
mReadSession.read(100);

But how will it work? What does it return? I have my custom RecyclerView in which I will be showing user chats.

Edit: Probably this code block is to read individual's chats. Anyways I need help to get both. Please suggest.

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?

what exactly is the api op and detail documentation for getting all the active conversations and groups that currently logged in user is involved in?

I'm trying to build android application (by editing whatsapp look a like app) to create it in a way that it login my user (user created in mesibo) and user has access to its conversations, but unfortunately there is no api for getting all the active conversations that user is involved in, please response

The push notification of your WhatsApp clone is not working. Message are only delivered when you open the app. No message notification too, There is also no notification tone.

Is there anyway to change ring tone, message tone etc. I don't see any raw folder at all.

File google-services.json is missing. The Google Services Plugin cannot function without it.
Searched Location:
D:\desctop\dev\android-app-master\app\src\nullnull\google-services.json
D:\desctop\dev\android-app-master\app\src\debug\google-services.json
D:\desctop\dev\android-app-master\app\src\nullnullDebug\google-services.json
D:\desctop\dev\android-app-master\app\src\nullnull\debug\google-services.json
D:\desctop\dev\android-app-master\app\src\debug\nullnull\google-services.json
D:\desctop\dev\android-app-master\app\google-services.json

pls help me

I have already obtaitn my mesibo api key for the android app WHERE do I place it???????

is their any territorial for it_

Cloned the repo,
added own google-services.json in the app folder

built the app using android studio, but sms authentication is not happening,

the sms for is not being received. neither are we able to use the demo phone numbers set in firebase console phone authentication

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'

Hi,
My backend is in NodeJS.
My apps is in React Native. So does your platform support RN Apps?
Also I am looking for HIPPA Compliant solution?
Is your platform HIPPA Compliant??

Thanks

I want to change directory name where all the files are stored, currently, it is hardcoded as <Provided Path>/Mesibo/

Is there any way to update this, if not, could you add this in your Todos.

Thanks

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

What is the function that allows me to get list messages ?

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.

Any plan for supporting androidx

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

I am sorry for adding issues but the tutorials are not as well-explained as I expected. My question is: For android. How Can I use Fragments with Mesibo? Or Do I have to necessarily call the Mesibo Activities with MesiboUI.launch or MesiboUI.launchMessageView? Can't I embed the chats view within a Fragment?

I always receive Mesibo.STATUS_AUTHFAIL | Mesibo.STATUS_STOPPED

I am configuring an application in Kotlin based on this example, but in my Mesibo_onConnectionStatus, I never get Mesibo.STATUS_ONLINE.

the methods "Mesibo.setAccessToken (mesiboUserToken)" and "Mesibo.start ()" return 0 (success)

I have also performed the basic settings:
Mesibo.setDatabase
MesiboCall.init
MediaPicker.setPath

Does anyone know why this is so?

I am trying to add some extra feature like 'Add Friend' at AudioCall Screen

public class CustomMesiboAudioCallFragment extends MesiboAudioCallFragment{ .... }
`mCall = MesiboCall.getInstance();

mCall.init(getApplicationContext());

mCall.setListener(new MesiboCall.MesiboCallListener() {
@OverRide
public boolean MesiboCall_onNotify(int i, Mesibo.UserProfile userProfile, boolean b) {
return false;
}
@OverRide
public MesiboVideoCallFragment MesiboCall_getVideoCallFragment(Mesibo.UserProfile userProfile) {
return null;
}
@OverRide
public MesiboAudioCallFragment MesiboCall_getAudioCallFragment(Mesibo.UserProfile userProfile) {
return new CustomMesiboAudioCallFragment();
}
@OverRide
public Fragment MesiboCall_getIncomingAudioCallFragment(Mesibo.UserProfile userProfile) {
return null;
}
});`

But MesiboCall_getAudioCallFragment is not getting called.
I didn't find any documentation for this as well, could you guys can help here.

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?

Hi,

Following is my code setup:

val api = Mesibo.getInstance()
            api.init(requireContext().applicationContext)
            Mesibo.initCrashHandler(this)

            Mesibo.setPath(Environment.getExternalStorageDirectory().absolutePath)
            Mesibo.addListener(this)
            Mesibo.setAccessToken(mesiboAccessToken)
            Mesibo.setSecureConnection(true)

            Mesibo.start()

In the logs, first I get a status code of 6 which means connecting and afterwards I get 9 which is calling is muted. I don't use calling whatsoever so doesn't matter but I am not getting any status code afterwards. If something is wrong on my end, at least something should happen like failure case. Can you clarify what's wrong?

PS. In the Mesibo dashboard, last seen of the user gets changed to the instance when above code is executed but then that remains static unless I restart the app.

I spent all day trying to understand and make a sample app on my own. But there is not clear API, the sample android project is awfull just a mess of code, spaghetti.

With reference to this issue (#42 (comment)) when will the new code without the account kit be updated?

Is it possible to leave open the source of all Mesibo screens?
We use the PT-BR language, and we are just wanting to translate all texts. I know that Mesibo offers the option of "Create all screens, and use it behind" but we would just like to change the texts.

It's possible?

Mesibo seems to be capable of much more other than sending messages and making video calls... but the code is not clear about it. You should evaluate documenting your code and perhaps writing a step-by-step document on how you built the demo app. As is, it's a mess to follow and understand the capabilities of your service.

What If I have an Android and iOS version of the same app but with different appIds. According to the test I have made, you force a close of the app when the token and appID doesn't match. What can I do in that case? Maybe support for multiple appIds for the same token?

Description

I was chatting with a friend and I made a video in the app and sent it. But I discovered the video didn't deliver. When I clicked on the mark sign to get the video forwarded, it took me back to the chatting page and no video was displayed.

Expected behaviour

After recording the video, I expected the video to be sent to the recipient when I clicked on the mark sign.

Steps to reproduce

First, you need to signup on Mesibo using your mobile number

• Launch the app and connect with a friend using mesibo messenger
• While chatting ,click on the plus sign by the left side below
• Click on the video icon. It will display a page with two options
• Select your video from video recorder.
• Record your video.
• After recording, click on the white check mark to forward the video to your friend you are chatting with, and note what happens.

Video showing the behavior

https://youtu.be/mTcw3iFuqNM

Device used

• Techno spark k7

• Android 7.0 O.S

Is there a way to hide the location button? If you make the MesiboUI repository as open source I could help you guys 👍

how to replace account kit with firebase authentication in mesibo messenger sample android project

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

When I receive a new email, the preview changed but the other elements like the labels in bold, or the badge with the number of messages unread is not rendered. Look this attachments. The first one you can see the other person is typing and after that a message is received but without the other elements I mentioned.

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)

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: mesibo/samples#21

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

App crashed on login, not send OTP