On 08/07/2016 01:57 AM, Alex Balashov wrote:
So, I'm guessing the answer to your question is no: the Content-Length
is not accurate, and doesn't reflect the full payload from the combined
length of the SDP stanzas (122 + 149 = 271).
I guess it should be 265, not 271.
--
Alex Balashov | Princi
On 08/07/2016 01:50 AM, Daniel-Constantin Mierla wrote:
tcp being a stream protocol, kamailio is reading the body of sip
messages based on content-lenght header -- can you check and see if the
values for content length are accurate?
The initial INVITE has a Content-Length value of 122, but 116
Hello,
tcp being a stream protocol, kamailio is reading the body of sip
messages based on content-lenght header -- can you check and see if the
values for content length are accurate?
Do you have the parameter tcp_accept_no_cl set?
Cheers,
Daniel
On 06/08/16 00:39, Alex Balashov wrote:
> I'll
We have tried all of your suggestions, but still not getting any light
changes on the watcher.
The basic problem seems to be that the watched phone sends PUBLISH
packets to the server, but the server does not send NOTIFY packets to
the watcher phone.
We are seeing the following error in the logs
