Very interesting. I am still not able to have an audio call complete. Can
I see your kamailio.cfg, under separate cover? Or sent to the list?
Do you have "method_filtering" in registrar params set to 0 or 1? I had it
set to 1 and by default the JsSIP tryit must not have been sending an Allow
o
Peter,
Thank you. By changing the "method_filtering" modparam to 0 (it was
actually 1), I am now able to make it past this, and the INVITE is
processed over WS transport. However, the audio call is still not
completing.
I am seeing a "180 Ringing" message for a while, followed by a "408 Request
Hi,
New to Kamailio. I have my Kamailio 4.0 server with websocket support, and
the users can register using the JsSIP Tryit sample WebRTC application.
They can do 'chat' feature of JsSIP Tryit using kamailio 4.0 sip over
websockets module.
However, after registration, the users can't place an a
Hi,
New to Kamailio. I have my Kamailio 4.0 server with websocket support, and
the users can register using the JsSIP Tryit sample WebRTC application.
However, after registration, the users can't place an audio call. I see no
ringing on the remote browser. I don't know how to debug this furthe
Hello Peter,
Thank you for the quick reply. Yes, that did the trick. Changing
"tcp_accept_no_cl" to value of no was the resolution.
It seems that the JsSIP Tryit sample code, which I was trying to hack,
doesn't use Content-Length in the header. I wonder if this should be
changed to set the Con
Hi,
Wondering if anyone could please help me debug what is wrong with my
kamailio.cfg for Websockets support. I'm using JsSIP sample application,
and I've compiled Kamailio 4.0 for WS support. My config is borrowed from
link this link [1]. Wondering if anyone can help me debug this. Error is
b
