Hello,
Found an interesting scenario, maybe something could be done here. I have a siptrace module configured like
modparam("siptrace", "duplicate_uri", "sip:<MY_HOMER_SERVER>:9060") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_on", 1) modparam("siptrace", "hep_version", 3) modparam("siptrace", "trace_mode", 1)
When Kamailio is under stress test (sipflood via OPTIONS/TLS), with this settings it transfers all flood to HOMER server.
At some point Kamailio just stops accepting any new TLS connections.
Turning off siptrace solves this issue.
As I got, siptrace module is not changing protocol of the message (means not converting TCP/UDP) or so. Could it be possible, that at some point siptrace "eats" all TCP connections (especially if remote HOMER is down or not answering) which leads Kamailio to stop processing any new connections?
And is it possible to send HEP traffic only via UDP to prevent this?
Yes, sure other option is to trace only "legal" traffic
Hi,
For only UDP, you can try force_send_sock with UDP socket there.
Jurijs
On Wed, Nov 2, 2022 at 5:31 PM Igor Olhovskiy igorolhovskiy@gmail.com wrote:
Hello,
Found an interesting scenario, maybe something could be done here. I have a siptrace module configured like
modparam("siptrace", "duplicate_uri", "sip:<MY_HOMER_SERVER>:9060") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_on", 1) modparam("siptrace", "hep_version", 3) modparam("siptrace", "trace_mode", 1)
When Kamailio is under stress test (sipflood via OPTIONS/TLS), with this settings it transfers all flood to HOMER server.
At some point Kamailio just stops accepting any new TLS connections.
Turning off siptrace solves this issue.
As I got, siptrace module is not changing protocol of the message (means not converting TCP/UDP) or so. Could it be possible, that at some point siptrace "eats" all TCP connections (especially if remote HOMER is down or not answering) which leads Kamailio to stop processing any new connections?
And is it possible to send HEP traffic only via UDP to prevent this?
Yes, sure other option is to trace only "legal" traffic
-- Best regards, Ihor (Igor) __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
That's what I tried first and got:
ERROR: siptrace [siptrace.c:392]: mod_init(): bad send sock address
Le mer. 2 nov. 2022 à 15:58, Jurijs Ivolga jurijs.ivolga@gmail.com a écrit :
Hi,
For only UDP, you can try force_send_sock with UDP socket there.
Jurijs
On Wed, Nov 2, 2022 at 5:31 PM Igor Olhovskiy igorolhovskiy@gmail.com wrote:
Hello,
Found an interesting scenario, maybe something could be done here. I have a siptrace module configured like
modparam("siptrace", "duplicate_uri", "sip:<MY_HOMER_SERVER>:9060") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_on", 1) modparam("siptrace", "hep_version", 3) modparam("siptrace", "trace_mode", 1)
When Kamailio is under stress test (sipflood via OPTIONS/TLS), with this settings it transfers all flood to HOMER server.
At some point Kamailio just stops accepting any new TLS connections.
Turning off siptrace solves this issue.
As I got, siptrace module is not changing protocol of the message (means not converting TCP/UDP) or so. Could it be possible, that at some point siptrace "eats" all TCP connections (especially if remote HOMER is down or not answering) which leads Kamailio to stop processing any new connections?
And is it possible to send HEP traffic only via UDP to prevent this?
Yes, sure other option is to trace only "legal" traffic
-- Best regards, Ihor (Igor) __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
How did you configure force_send_sock?
it should be something like this:
modparam("siptrace", "force_send_sock", "sip:192.168.1.210:5066")
I'm guessing instead of sip, you are putting udp...
Jurijs
On Wed, Nov 2, 2022 at 6:12 PM Igor Olhovskiy igorolhovskiy@gmail.com wrote:
That's what I tried first and got:
ERROR: siptrace [siptrace.c:392]: mod_init(): bad send sock address
Le mer. 2 nov. 2022 à 15:58, Jurijs Ivolga jurijs.ivolga@gmail.com a écrit :
Hi,
For only UDP, you can try force_send_sock with UDP socket there.
Jurijs
On Wed, Nov 2, 2022 at 5:31 PM Igor Olhovskiy igorolhovskiy@gmail.com wrote:
Hello,
Found an interesting scenario, maybe something could be done here. I have a siptrace module configured like
modparam("siptrace", "duplicate_uri", "sip:<MY_HOMER_SERVER>:9060") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_on", 1) modparam("siptrace", "hep_version", 3) modparam("siptrace", "trace_mode", 1)
When Kamailio is under stress test (sipflood via OPTIONS/TLS), with this settings it transfers all flood to HOMER server.
At some point Kamailio just stops accepting any new TLS connections.
Turning off siptrace solves this issue.
As I got, siptrace module is not changing protocol of the message (means not converting TCP/UDP) or so. Could it be possible, that at some point siptrace "eats" all TCP connections (especially if remote HOMER is down or not answering) which leads Kamailio to stop processing any new connections?
And is it possible to send HEP traffic only via UDP to prevent this?
Yes, sure other option is to trace only "legal" traffic
-- Best regards, Ihor (Igor) __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Best regards, Ihor (Igor) __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Hi,
And I think Kamailio supports only UDP for sending out HEP traffic...
Jurijs
On Wed, Nov 2, 2022 at 7:14 PM Jurijs Ivolga jurijs.ivolga@gmail.com wrote:
How did you configure force_send_sock?
it should be something like this:
modparam("siptrace", "force_send_sock", "sip:192.168.1.210:5066")
I'm guessing instead of sip, you are putting udp...
Jurijs
On Wed, Nov 2, 2022 at 6:12 PM Igor Olhovskiy igorolhovskiy@gmail.com wrote:
That's what I tried first and got:
ERROR: siptrace [siptrace.c:392]: mod_init(): bad send sock address
Le mer. 2 nov. 2022 à 15:58, Jurijs Ivolga jurijs.ivolga@gmail.com a écrit :
Hi,
For only UDP, you can try force_send_sock with UDP socket there.
Jurijs
On Wed, Nov 2, 2022 at 5:31 PM Igor Olhovskiy igorolhovskiy@gmail.com wrote:
Hello,
Found an interesting scenario, maybe something could be done here. I have a siptrace module configured like
modparam("siptrace", "duplicate_uri", "sip:<MY_HOMER_SERVER>:9060") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_on", 1) modparam("siptrace", "hep_version", 3) modparam("siptrace", "trace_mode", 1)
When Kamailio is under stress test (sipflood via OPTIONS/TLS), with this settings it transfers all flood to HOMER server.
At some point Kamailio just stops accepting any new TLS connections.
Turning off siptrace solves this issue.
As I got, siptrace module is not changing protocol of the message (means not converting TCP/UDP) or so. Could it be possible, that at some point siptrace "eats" all TCP connections (especially if remote HOMER is down or not answering) which leads Kamailio to stop processing any new connections?
And is it possible to send HEP traffic only via UDP to prevent this?
Yes, sure other option is to trace only "legal" traffic
-- Best regards, Ihor (Igor) __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-- Best regards, Ihor (Igor) __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Jurijs,
That's exactly how I'm trying.
Le 02/11/2022 à 18:14, Jurijs Ivolga a écrit :
How did you configure force_send_sock?
it should be something like this:
modparam("siptrace", "force_send_sock", "sip:192.168.1.210:5066 http://192.168.1.210:5066")
I'm guessing instead of sip, you are putting udp...
Jurijs
On Wed, Nov 2, 2022 at 6:12 PM Igor Olhovskiy igorolhovskiy@gmail.com wrote:
That's what I tried first and got: ERROR: siptrace [siptrace.c:392]: mod_init(): bad send sock address Le mer. 2 nov. 2022 à 15:58, Jurijs Ivolga <jurijs.ivolga@gmail.com> a écrit : Hi, For only UDP, you can try |force_send_sock| with UDP socket there. Jurijs On Wed, Nov 2, 2022 at 5:31 PM Igor Olhovskiy <igorolhovskiy@gmail.com> wrote: Hello, Found an interesting scenario, maybe something could be done here. I have a siptrace module configured like modparam("siptrace", "duplicate_uri", "sip:<MY_HOMER_SERVER>:9060") modparam("siptrace", "hep_mode_on", 1) modparam("siptrace", "trace_to_database", 0) modparam("siptrace", "trace_on", 1) modparam("siptrace", "hep_version", 3) modparam("siptrace", "trace_mode", 1) When Kamailio is under stress test (sipflood via OPTIONS/TLS), with this settings it transfers all flood to HOMER server. At some point Kamailio just stops accepting any new TLS connections. Turning off siptrace solves this issue. As I got, siptrace module is not changing protocol of the message (means not converting TCP/UDP) or so. Could it be possible, that at some point siptrace "eats" all TCP connections (especially if remote HOMER is down or not answering) which leads Kamailio to stop processing any new connections? And is it possible to send HEP traffic only via UDP to prevent this? Yes, sure other option is to trace only "legal" traffic -- Best regards, Ihor (Igor) __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Best regards, Ihor (Igor) __________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
Kamailio - Users Mailing List - Non Commercial Discussions sr-users@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe: https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
-
Igor Olhovskiy -
Ihor Olkhovskyi
-
Jurijs Ivolga