Hi Yuriy,

yes, there is nothing between webrtc client SIP.js and kamailio/rtpengine. We have a sip server that sends a call to kamailio that forwards the call to webrtc client. Kamailio is running on plain linux debian EC2 AWS machine (no docker or anything else).

Some calls we get from kamailio in UTF-8 invite messages and other calls we get binary invite messages.

If logs or cfg helps, just let me know.

Thanks

Santos

On Thu, Feb 6, 2020 at 9:29 AM Yuriy Gorlichenko <ovoshlook@gmail.com> wrote:

SIP is a text protocol by default. Binary messages can be here only keepalive messages and etc. So it should not go to application layer of the client as it is a transport layer messages. Are you sure There is no other software between kamailio and client that creates a bridge between client and kamailio?

On Thu, 6 Feb 2020, 12:37 Andre Pires dos Santos, <santos.andrepires@gmail.com> wrote:
Hello guys,

we are new to kamailio so sorry basic or wrong points.

We started using kamailio 5.3.2 and rtpengine as our sip to webrtc solution and SIP.js as webrtc client. We noticed that most of the times webrtc client receives UTF-8 messages. But sometimes webrtc client receives binary messages. When we get binary messages SIP.js cannot parse the message.

I couldn't find how to force kamailio to send only UTF-8 messages. Is it possible?

We have other issues but I think it will be better for the list to break other points in different messages.

Thanks!
Santos
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users