Calling feature not working properly!

Hi Support team,

We have integrated cometchat sdk version 2.0.4-beta1 on Android app.
The calling audio/video was working fine up until couple of days ago.
Right now, if a call is initiated to a recipient, the recipient answers the call. After this point, Neither does the caller can see the recipient’s video feed, nor the recipient can see the caller’s feed.
In contrast, a call between android app and the javascript, after call initiated from android app, the javascript sdk shows timeout error.

I would appreciate some quick advice/help as we are at a very time sensitive scenario.
TIA :slightly_smiling_face:

Hello @Kiran_Flappjacks
Can you share with us the region your app is based in.?
Secondly, we would lile to know if the calling stopped working after migration to 2.0.4-beta1 or you were always on 2.0.4-beta1 and calling just randomly stopped working.?
Awaiting Reply

The region is eu.
This issue is random. It was working on 2.0.4-beta1 until a day or 2 ago.

Hi Support team,
Any update on this? As mentioned earlier, its a time sensitive scenario. Hence, trying to get this sorted ASAP.
TIA :slightly_smiling_face:

I have tested the code 15th March and at that time call was working and Video was working. but all of a sudden we tested this today, we could not connect the calls. we are just using Java sample code from your git. I am wondering can we trust video and call services?

Hello @Kiran_Flappjacks @VijayZ,
We’ve identified this issue affecting a few of our customers and have released a patch. This issue was due to SSL handshakes timing out. Please confirm if everything is working as expected. In case you still face the issue, please do let us know and we will be glad to help you out.
Thanks

Hi @aditya.gokula,
I have spent some time testing the call connectivity. I can say that the scenarios have improved. But unfortunately, the consistency levels are poor. I still see timeout errors often. I’m attaching logs below for your reference.

2020-03-27 09:46:10.512 30588-30629/com.random W/System.err: java.net.SocketTimeoutException: failed to connect to ws-eu.cometchat.io/52.50.187.223 (port 80) from /100.80.193.3 (port 45830) after 2000ms
2020-03-27 09:46:10.512 30588-30629/com.random W/System.err:     at libcore.io.IoBridge.connectErrno(IoBridge.java:191)
2020-03-27 09:46:10.512 30588-30629/com.random W/System.err:     at libcore.io.IoBridge.connect(IoBridge.java:135)
2020-03-27 09:46:10.512 30588-30629/com.random W/System.err:     at java.net.PlainSocketImpl.socketConnect(PlainSocketImpl.java:142)
2020-03-27 09:46:10.512 30588-30629/com.random W/System.err:     at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:390)
2020-03-27 09:46:10.512 30588-30629/com.random W/System.err:     at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:230)
2020-03-27 09:46:10.512 30588-30629/com.random W/System.err:     at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:212)
2020-03-27 09:46:10.512 30588-30629/com.random W/System.err:     at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:436)
2020-03-27 09:46:10.512 30588-30629/com.random W/System.err:     at java.net.Socket.connect(Socket.java:621)
2020-03-27 09:46:10.512 30588-30629/com.random W/System.err:     at com.cometchat.pro.core.PingController.ping(PingController.java:88)
2020-03-27 09:46:10.513 30588-30629/com.random W/System.err:     at com.cometchat.pro.core.PingController.access$100(PingController.java:12)
2020-03-27 09:46:10.513 30588-30629/com.random W/System.err:     at com.cometchat.pro.core.PingController$1.run(PingController.java:48)
2020-03-27 09:46:10.513 30588-30629/com.random W/System.err:     at java.util.TimerThread.mainLoop(Timer.java:562)
2020-03-27 09:46:10.513 30588-30629/com.random W/System.err:     at java.util.TimerThread.run(Timer.java:512)


2020-03-27 09:46:16.300 30588-31010/com.random E/JitsiMeetSDK: [JitsiConference.js] An error occurred while trying to terminate P2P Jingle session { reason: 'timeout',
      session: 'JingleSessionPC[p2p=true,initiator=false,sid=a981531319d5]' }

I hope the issues will resolved ASAP. TIA :slightly_smiling_face:

1 Like

Hello @Kiran_Flappjacks
From the logs what I can see is that it shows two different timeouts:

  1. timeout for connecting to our web-sockets server
  2. timeout to connect to our webRTC server.

As mentioned above, there was an issue while connecting to our webRTC server due to the SSL handshakes timing out and the patch for the same has been released already.
From the logs it looks like for this particular scenario, there was a network fluctuation or loss of internet connectivity for a brief span of time leading to connections timing out.
Also, after releasing the patch, we have tested this thoroughly and the issue with calls timing out haven’t been encountered.
It would be of great help, if you could share the complete logs the next time you encounter the timeout issue.
Also, i would suggest trying the same scenario, on a different network just to make sure if this has got nothing to do with ports being blocked or unknown URLs being blocked on certain networks.
As we are unable to encounter this at our end, its extremely difficult to figure out the root cause of this issue. Please provide us with the complete logs on encountering this issue again and we will definitely dig deeper and provide you with a solution at the earliest

1 Like

Hi Support,

Javascript web to Mob App or Web to Web throwing below mentioned error,

ChatRoom.js:1434 Uncaught (in promise) Error: The timeout for the confirmation about leaving the room expired.
at o (ChatRoom.js:1434)
at ChatRoom.js:1422

Hey @aditya.gokula

Yes. Those were 2 different error logs.
I will further test out the calls on different networks as well.
Meanwhile, the above post is on the javascript sdk. We are facing the time out errors on web still.
Can you please look into that as well?
TIA :slightly_smiling_face: