Joseph,

You will need to go with this to the specific VoIP provider.

In general, echo cancellation and noise cancellation is implemented by software when it comes to VoIP applications. Their implementations vary in quality.

Input devices can also come with their own noise and echo cancellation capabilities – just choose one that offers the quality you are looking for.

perhaps you can assist with my query, you seem to be an expert in these implementations.

When on a phone call, my bluetooth headset’s noise cancellation works a treat, and I can take conference calls with no hassle.

however, when calling via whatsapp, telegram, or google duo, the noise cancellation function seems to not be present.

Where is the restriction here? do you have another web based dialling solution that can still work?

headset is a popular plantronics model. Android phone.

Hi;
PJLIB can be used without the SIP part.
It has very good OS abstraction libraries.

Joe,

You are missing the point. I know VoIP quite well. Have been working in this field for most of my life, and used it for the past 15+ years on a daily basis. Whatsapp’s implementation at that point in time was useless for Israeli customers – their servers were located too far away and calls were relayed by default (at least at the beginning of the call).

To get VoIP working properly there’s a lot more required than just slapping a server or two on the network – the actual way the deployment is placed and the care and attention given to the use case and various scenarios plays a significant role in the quality of experiences users will feel.

The world has been duped by all the vibers, Skype’s, facetimes, whatsapp and so on. You are using the internet… There is no control over packets between endpoints. It’s hit and miss if it works. The sooner you come to terms with this the sooner site’s like this will stop wasting everyone’s time by publishing rubbish abort the pros and cons of something that is fundamentally flawed regardless of what the app is. There is no such thing as a free lunch. If you want a comms app that can be supported and has have a chance of working then you need to pay for a service like Cisco Webex….

I am not a purist. If they built it on the browser with WebRTC, it is most likely that they used the same type of codecs, signaling and network stack for their mobile app. This translates into WebRTC everywhere for Facebook.

“native WebRTC route with Facebook Messenger” is on desktop, and uses the browser infrastructure, isn’t it? But on Android, they may have chosen to distribute minimal size, and cut out whatever possible. For one JavaScript API is of no use there.

Thanks Alex.

It strikes me as weird that they take this route with Whatsapp but the native WebRTC route with Facebook Messenger.

Not sure. I guess Facebook is more concerned at the moment at increasing the engagement time of users than anything else. Getting voice and video chats to there is part of it.

Fippo,

Just for you, I am willing to give the alternative of writing a full length comment and I’ll publish it as a guest post 🙂