Online:
Visits:
Stories:
Profile image
Story Views

Now:
Last Hour:
Last 24 Hours:
Total:

If Your Unseen Call Failed – Troubleshooting WebRTC

Saturday, May 31, 2014 11:28
% of readers think this story is Fact. Add your two cents.

(Before It's News)

The new Unseen calling upgrades are a huge breakthrough.  Now, because of the cooperation between Chrome, Opera and Firefox, Unseen users can make audio and video calls of outstanding quality.  One billion people are now enabled to use this great technology.  There are still a few bugs and tweaks you might need to make.

Be sure your mic (and camera for video) and speakers are all working.  Be sure to check the speaker icon in the upper right of the Unseen chat window to be sure it’s not X’d out and click on the speaker to be sure the volume is turned up high enough.  You can still hear the ding-ding, but the volume could be turned down, so check that and turn it up.  Here’s some more:

My Call Failed – how to troubleshoot

Unseen one to one call is peer to peer, that mean the data stream is transferred only between the caller and callee. If it’s not possible to make peer to peer connection, the data stream is automatically relay via our TURN servers (only 8% of chance, in the case of Symmetric NAT).

We support Chrome 29+, Firefox, Opera, Desktop Client and Android (iOS is coming soon). To make audio call, the caller and recipient need to have a microphone, video call requires a camera. If you use browsers, make sure to enable your microphone and camera.
- On Chrome it will ask once at the first time you make a call, it will display “Allow” and “Deny” buttons below the address bar.
- On Firefox it will ask every time you make a call (be sure to chose a correct microphone and camera).
If you hear no sound, after the call is made, please check your speaker and check the volume button on the right top corner of Unseen chat window (is it on with enough volume or not).
If you get the error message “Media permission denied”, it means the recipient do not enable Microphone or Camera (they may not have that).
If you get the error message “Failed to get local SDP” from Android to your friends, you need to check:
- Your Unseen Application need to be at least 1.5.2 above. We have a release 1.5.2 on 05/31/2014 that fix the issue one way calling to Desktop application, Chrome < 35 and Opera.
- You need to restart your Phone after install Unseen Android so it will be able to work correctly with browsers and desktop application.
If you get the error message “No / SSL”, the recipient may not available or can not connect to our server.
If you receive error message “Call sevice is not available” on Android phone, you are not connected to our SIP server. There are some reasons for this:
- First you try to log out and login again, try to make call again.
- If this still happen, you can go to the settings of the App –> Call Settings –> Change the transport protocol to UDP
- If it still not work, your network may block the connection (some mobile network they block UDP 5060, TCP 5060) or your phone version is locked (by blocking TCP 5060 or UDP 5060). You can troubleshoot by use a wifi connection instead of 3G / 4G network. If it still not work, please help us by using your terminal / command line with following command:
telnet ssig.unseen.is 5000
telnet ssig.unseen.is 5060
and give us your screenshot.
Here is our test between Supported browsers, desktop client and Android:calling tests


Source: https://blog.unseen.is/2014/05/31/if-your-unseen-call-failed-troubleshooting-webrtc/

Report abuse

Comments

Your Comments
Question   Razz  Sad   Evil  Exclaim  Smile  Redface  Biggrin  Surprised  Eek   Confused   Cool  LOL   Mad   Twisted  Rolleyes   Wink  Idea  Arrow  Neutral  Cry   Mr. Green

Top Stories
Recent Stories

Register

Newsletter

Email this story
Email this story

If you really want to ban this commenter, please write down the reason:

If you really want to disable all recommended stories, click on OK button. After that, you will be redirect to your options page.