[OpenSIPS-Users] We didn't manage to read a full request

Hi Team, Recently checked the log and found a lot of items. DBG:proto_tls:tcp_handle_req: We didn't manage to read a full request Does this mean that there is an incoming message but the server can't read it successfully? What can induce this problem? Thanks! Regards, Jacky

[OpenSIPS-Users] Call-API / 404 Dialog not found

Hi, i am using trunking scenario with Topology hiding  + RTPEngine and it is working fine. Additionally i am trying to setup Call-API to work for outbound dialer app. For now i am using only internal module "cmd/call-api-client/main.go .." to originate call .The call is send to first ddi (ca

Re: [OpenSIPS-Users] [RELEASE] OpenSIPS 3.1.6 and 3.2.3 minor releases

Hello! It is my pleasure to announce a new set of OpenSIPS minor releases: 3.1.6 and 3.2.3! These releases include the fixes of the past couple of months: roughly 40 bugfixes/improvements, touching critical modules such as tls_wolfssl, rtp_relay, dialog, rtpengine, b2b_logic, auth, mid-regis

Re: [OpenSIPS-Users] config 477 for offline message

Hi Bogdan-Andrei, Yes. 0x02 flag works. I knew this but struggled a lot to figure out where to do the t_relay(0x02). It works now and no 477 sent. Thanks! Regards, Jacky Hi, > > Using the 0x02 flag should do the trick . If you enable it, do you still > see the TM sending the 477 reply automatic

Re: [OpenSIPS-Users] We didn't manage to read a full request

On Wed, Oct 20, 2021 at 11:00 AM jacky z wrote: > > Recently checked the log and found a lot of items. > > DBG:proto_tls:tcp_handle_req: We didn't manage to read a full request > > Does this mean that there is an incoming message but the server can't read > it successfully? What can induce this p

Re: [OpenSIPS-Users] We didn't manage to read a full request

Thanks! We found an end point sent an INVITE, but the server did not receive. The time of this message in the opensips log matched the INVITE. Not sure whether the INVITE message failed to be read for whatever reason. Then we checked the server and found a lot of such messages. The server is a stil

Re: [OpenSIPS-Users] We didn't manage to read a full request

We found most of the time, it follows a global (per process) buff and is followed by a per connection buff and then the message is read. Oct 19 13:34:32 sipserver /usr/sbin/opensips[18615]: DBG:proto_tls:tls_read_req: *Using the global ( per process ) buff * Oct 19 13:34:32 sipserver /usr/sbin/ope

Re: [OpenSIPS-Users] We didn't manage to read a full request

On Wed, Oct 20, 2021 at 3:30 PM jacky z wrote: > We found most of the time, it follows a global (per process) buff and is > followed by a per connection buff and then the message is read. > > try to do a tcpdump on that interface/port, then wireshark the pcap, you will see what opensips see eg:

Re: [OpenSIPS-Users] validate_dialog() failing to recognise reinvites

Hi, So the error log is about the "remote contact", but the return code is -1 ?? (which according to doc [1] means invalid cseq). Checking the code, you should have get a -2 ret code in correlation to that log (see [2]). Now, based on the error log, I see that the dialog module retained the

[OpenSIPS-Users] Need some clarification on rtpengine usage .

Hi , I have configured 2 rtpengine in opensips-2.2 as beow . modparam("rtpengine", "rtpengine_sock", "udp:192.168.131.123:22000 udp: 192.168.128.199:22000") My question is , If 1 rtpengine has port outage and give the error as below *" ERROR:rtpengine:rtpe_function_call: proxy replied with error