Hi Pete,
Try the script_trace() function, to see if the delay comes from the
script level. If not, it means it comes from the TCP layer (maybe
related to the dispatching of TCP cons between workers)
https://www.opensips.org/Documentation/Script-CoreFunctions-3-5#script_trace
BTW, what are the TCP settings for:
https://www.opensips.org/Documentation/Script-CoreParameters-3-5#tcp_parallel_read_on_workers
https://opensips.org/html/docs/modules/3.5.x/proto_tcp.html#idp5528016
Regards,
Bogdan-Andrei Iancu
OpenSIPS Founder and Developer
https://www.opensips-solutions.com
https://www.siphub.com
On 10.04.2025 23:42, Pete Kelly wrote:
Hello all
I am running some OpenSIPS proxies which are talking to each other
exclusively in TCP, however when performing some (mild) load tests I
am seeing some strange behaviour from time to time, which manifests
itself as what looks like OpenSIPS taking a long time to process SIP
requests.
The most obvious issue I am seeing (and confirmed by tcpdump) is when
OpenSIPS receives an invite but may take anything from 2-8 second to
even send the 100 Trying!
e.g.
T 2025/04/10 20:28:10.257283 10.3.0.4:48665 <http://10.3.0.4:48665> ->
10.3.0.12:5080 <http://10.3.0.12:5080> [A] #4826
INVITE sip:... SIP/2.0.
T 2025/04/10 20:28:12.644355 10.3.0.12:5080 <http://10.3.0.12:5080> ->
10.3.0.4:48665 <http://10.3.0.4:48665> [AP] #4955
SIP/2.0 100 Giving it a try.
Is there an obvious route for me to debug this behaviour to try and
see where the bottleneck may lie ? Can I see somewhere if all of the
tcp workers are in use for example and it is waiting for a worker?
Pete
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
_______________________________________________
Users mailing list
Users@lists.opensips.org
http://lists.opensips.org/cgi-bin/mailman/listinfo/users
