Hello!
In my architecture, SIP SUBSCRIBE messages can reach the Kamailio Presence server in several ways. And I noticed that re-SUBSCRIBEs messages do not update the record_route field in the active_watchers table (MySQL), so subsequent SIP NOTIFY messages do not inherit it and have the routes set of the initial SIP SUBSCRIBE message.
Is there any way to change this behavior?
modparam("presence", "db_url", DBURL) modparam("presence", "subs_db_mode", 3) modparam("presence", "timeout_rm_subs", 0) modparam("presence", "expires_offset", 0) modparam("presence", "max_expires", 1800) modparam("presence", "db_update_period", 30) modparam("presence", "clean_period", 180) modparam("presence", "send_fast_notify", 1) modparam("presence", "pres_htable_size", 32) modparam("presence", "subs_htable_size", 32) modparam("presence", "publ_cache", 0) modparam("presence", "notifier_processes", 0)
# kamailio -v version: kamailio 5.1.2 (x86_64/linux)
Out of curiosity, since 5.1.2 is quite old…
Have you considered a supported branch (5.6, 5.7) or tried the most recent 5.1.10?
The change log for 5.1.x includes:
"presence: update record_route in database"
Regards,
Fred Posner p: +1 (352) 664-3733 contact: https://fred.tel
On Feb 27, 2024, at 4:32 AM, Denys Pozniak via sr-users sr-users@lists.kamailio.org wrote:
Hello!
In my architecture, SIP SUBSCRIBE messages can reach the Kamailio Presence server in several ways. And I noticed that re-SUBSCRIBEs messages do not update the record_route field in the active_watchers table (MySQL), so subsequent SIP NOTIFY messages do not inherit it and have the routes set of the initial SIP SUBSCRIBE message.
Is there any way to change this behavior?
modparam("presence", "db_url", DBURL) modparam("presence", "subs_db_mode", 3) modparam("presence", "timeout_rm_subs", 0) modparam("presence", "expires_offset", 0) modparam("presence", "max_expires", 1800) modparam("presence", "db_update_period", 30) modparam("presence", "clean_period", 180) modparam("presence", "send_fast_notify", 1) modparam("presence", "pres_htable_size", 32) modparam("presence", "subs_htable_size", 32) modparam("presence", "publ_cache", 0) modparam("presence", "notifier_processes", 0)
# kamailio -v version: kamailio 5.1.2 (x86_64/linux) --
BR, Denys Pozniak
Thanks for the information Fred! I tried to find some information in the module description...
Out of curiosity, since 5.1.2 is quite old…
The version is really old, but it works damn stably under high load and I can’t even raise my hand to touch the server.
ср, 28 февр. 2024 г. в 15:44, Fred Posner via sr-users < sr-users@lists.kamailio.org>:
Out of curiosity, since 5.1.2 is quite old…
Have you considered a supported branch (5.6, 5.7) or tried the most recent 5.1.10?
The change log for 5.1.x includes:
"presence: update record_route in database"
Regards,
Fred Posner p: +1 (352) 664-3733 contact: https://fred.tel
On Feb 27, 2024, at 4:32 AM, Denys Pozniak via sr-users <
sr-users@lists.kamailio.org> wrote:
Hello!
In my architecture, SIP SUBSCRIBE messages can reach the Kamailio
Presence server in several ways.
And I noticed that re-SUBSCRIBEs messages do not update the record_route
field in the active_watchers table (MySQL), so subsequent SIP NOTIFY messages do not inherit it and have the routes set of the initial SIP SUBSCRIBE message.
Is there any way to change this behavior?
modparam("presence", "db_url", DBURL) modparam("presence", "subs_db_mode", 3) modparam("presence", "timeout_rm_subs", 0) modparam("presence", "expires_offset", 0) modparam("presence", "max_expires", 1800) modparam("presence", "db_update_period", 30) modparam("presence", "clean_period", 180) modparam("presence", "send_fast_notify", 1) modparam("presence", "pres_htable_size", 32) modparam("presence", "subs_htable_size", 32) modparam("presence", "publ_cache", 0) modparam("presence", "notifier_processes", 0)
# kamailio -v version: kamailio 5.1.2 (x86_64/linux) --
BR, Denys Pozniak
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
Hi there!
I conducted some tests on the new Kamailio 5.7.3 and unfortunately, the problem still exists. Specifically, the problem lies in the fact that the data in the *active_watchers* table and the *record_route* field are only updated with initial Record-Route sets, and ignores any routing set changes for in-dialog re-subscribtions. However, there is a commit on GitHub that should fix this issue, but looks did not: https://github.com/kamailio/kamailio/commit/e52547956462ad53032be95ff5f27017....
I can share sipp scripts for reproducing the problem, along with a set of pcap traces (sip and mysql).
Thanks in advance!
чт, 29 февр. 2024 г. в 12:10, Denys Pozniak denys.pozniak@gmail.com:
Thanks for the information Fred! I tried to find some information in the module description...
Out of curiosity, since 5.1.2 is quite old…
The version is really old, but it works damn stably under high load and I can’t even raise my hand to touch the server.
ср, 28 февр. 2024 г. в 15:44, Fred Posner via sr-users < sr-users@lists.kamailio.org>:
Out of curiosity, since 5.1.2 is quite old…
Have you considered a supported branch (5.6, 5.7) or tried the most recent 5.1.10?
The change log for 5.1.x includes:
"presence: update record_route in database"
Regards,
Fred Posner p: +1 (352) 664-3733 contact: https://fred.tel
On Feb 27, 2024, at 4:32 AM, Denys Pozniak via sr-users <
sr-users@lists.kamailio.org> wrote:
Hello!
In my architecture, SIP SUBSCRIBE messages can reach the Kamailio
Presence server in several ways.
And I noticed that re-SUBSCRIBEs messages do not update the
record_route field in the active_watchers table (MySQL), so subsequent SIP NOTIFY messages do not inherit it and have the routes set of the initial SIP SUBSCRIBE message.
Is there any way to change this behavior?
modparam("presence", "db_url", DBURL) modparam("presence", "subs_db_mode", 3) modparam("presence", "timeout_rm_subs", 0) modparam("presence", "expires_offset", 0) modparam("presence", "max_expires", 1800) modparam("presence", "db_update_period", 30) modparam("presence", "clean_period", 180) modparam("presence", "send_fast_notify", 1) modparam("presence", "pres_htable_size", 32) modparam("presence", "subs_htable_size", 32) modparam("presence", "publ_cache", 0) modparam("presence", "notifier_processes", 0)
# kamailio -v version: kamailio 5.1.2 (x86_64/linux) --
BR, Denys Pozniak
Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
--
BR, Denys Pozniak
Hello Denys,
If you have some sipp scripts to reproduce the issue, creating an issue in our github about it would be probably a good idea.
Cheers,
Henning
From: Denys Pozniak via sr-users sr-users@lists.kamailio.org Sent: Mittwoch, 13. März 2024 13:50 To: Kamailio (SER) - Users Mailing List sr-users@lists.kamailio.org Cc: Fred Posner fred@pgpx.io; Denys Pozniak denys.pozniak@gmail.com Subject: [SR-Users] Re: [Presence] Updating route information for SIP NOTIFY when re-SUBSCRIBE
Hi there! I conducted some tests on the new Kamailio 5.7.3 and unfortunately, the problem still exists. Specifically, the problem lies in the fact that the data in the active_watchers table and the record_route field are only updated with initial Record-Route sets, and ignores any routing set changes for in-dialog re-subscribtions. However, there is a commit on GitHub that should fix this issue, but looks did not: https://github.com/kamailio/kamailio/commit/e52547956462ad53032be95ff5f27017....
I can share sipp scripts for reproducing the problem, along with a set of pcap traces (sip and mysql).
Thanks in advance!
чт, 29 февр. 2024 г. в 12:10, Denys Pozniak <denys.pozniak@gmail.commailto:denys.pozniak@gmail.com>: Thanks for the information Fred! I tried to find some information in the module description...
Out of curiosity, since 5.1.2 is quite old…
The version is really old, but it works damn stably under high load and I can’t even raise my hand to touch the server.
ср, 28 февр. 2024 г. в 15:44, Fred Posner via sr-users <sr-users@lists.kamailio.orgmailto:sr-users@lists.kamailio.org>: Out of curiosity, since 5.1.2 is quite old…
Have you considered a supported branch (5.6, 5.7) or tried the most recent 5.1.10?
The change log for 5.1.x includes:
"presence: update record_route in database"
Regards,
Fred Posner p: +1 (352) 664-3733 contact: https://fred.tel
On Feb 27, 2024, at 4:32 AM, Denys Pozniak via sr-users <sr-users@lists.kamailio.orgmailto:sr-users@lists.kamailio.org> wrote:
Hello!
In my architecture, SIP SUBSCRIBE messages can reach the Kamailio Presence server in several ways. And I noticed that re-SUBSCRIBEs messages do not update the record_route field in the active_watchers table (MySQL), so subsequent SIP NOTIFY messages do not inherit it and have the routes set of the initial SIP SUBSCRIBE message.
Is there any way to change this behavior?
modparam("presence", "db_url", DBURL) modparam("presence", "subs_db_mode", 3) modparam("presence", "timeout_rm_subs", 0) modparam("presence", "expires_offset", 0) modparam("presence", "max_expires", 1800) modparam("presence", "db_update_period", 30) modparam("presence", "clean_period", 180) modparam("presence", "send_fast_notify", 1) modparam("presence", "pres_htable_size", 32) modparam("presence", "subs_htable_size", 32) modparam("presence", "publ_cache", 0) modparam("presence", "notifier_processes", 0)
# kamailio -v version: kamailio 5.1.2 (x86_64/linux) --
BR, Denys Pozniak
__________________________________________________________ Kamailio - Users Mailing List - Non Commercial Discussions To unsubscribe send an email to sr-users-leave@lists.kamailio.orgmailto:sr-users-leave@lists.kamailio.org Important: keep the mailing list in the recipients, do not reply only to the sender! Edit mailing list options or unsubscribe:
--
BR, Denys Pozniak
--
BR, Denys Pozniak
-
Denys Pozniak -
Fred Posner -
Henning Westerholt