Re: Receiving WS keepalives

Hi Alex,

just did a quick look to the code, but it seems that the "pong" is handled as part of the normal websocket receive logic. So, this would mean you could increase the TCP worker children count.

Also doing a quick analysis regarding the CPU usage of the different kamailio processes should lead to more insight about the individual bottleneck.

Cheers,

Henning

-----Original Message-----
From: Alex Balashov via sr-users <[email protected]> 
Sent: Wednesday, September 24, 2025 3:22 PM
To: Kamailio (SER) - Users Mailing List <[email protected]>
Cc: Alex Balashov <[email protected]>
Subject: [SR-Users] Receiving WS keepalives

As far as I understand it, the keepalive processes in the `websocket` module concern processes dedicated to scheduling outgoing CRLF pings to clients.

What if the clients are initiating the ping, and the WS module responds with a pong? I assume the keepalive process pool does not handle that, but which processes do? Is it the core timer process, or the TLS receiver?

Suspected issue: insufficient resources to respond to an enormous amount of \n pings, which are sent every 2 seconds by every client. Which resources would one increase to help with this?

Cheers,

-- Alex

--
Alex Balashov
Principal Consultant
Evariste Systems LLC
Web: https://evaristesys.com, https://www.csrpswitch.com
Tel: +1-706-510-6800

__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected] To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions -- [email protected]
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the sender!