This is a snip from the user's mailing list, I'm just adding it to the issue tracker, as it is yet to be confirmed as a bug, only here for tracking pruporses:
``` I have a situation where I have 2 devices registering with the same AOR, I have the registrar module's max_contacts parameter set to 1 and I use the 0x04 flag on the save function.
When I use dmq_usrloc for replication, I can see 2 contacts registered for the AOR on the "client" nodes whereas the node where the actual registration took place only has 1 contact for the AOR. ```
``` It seems to me like another bug, although again I'm not familiar with the module so can't be sure without looking that it is not intended behaviour.
I plan to look later this week when I have some time but in the meantime, you can send me the examples directly if you like. ```
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/265
Hi,
Can you try with https://github.com/kamailio/kamailio/commit/edc25d7373f9560d09a35640ab19741f..., and confirm whether you still observe the same behaviour?
Also make sure max_contacts is set the same on all nodes.
Cheers, Charles
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/265#issuecomment-129016302
Hi,
Is there any chance that edc25d7 will be backported to the 4.3 branch? It would be nice to have it in the upcoming 4.3.2 release.
thanks, Paul
On 9 August 2015 at 03:33, Charles Chance notifications@github.com wrote:
Hi,
Can you try with edc25d7, and confirm whether you still observe the same behaviour?
Also make sure max_contacts is set the same on all nodes.
Cheers, Charles
— Reply to this email directly or view it on GitHub.
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hi,
I'm happy to backport, but it depends whether others see this as a new feature or a bug fix.
Personally I believe it is essential for the originally intended behaviour, but maybe someone else can comment?
Cheers, Charles
Charles Chance Managing Director
t. 0121 285 4400 m. 07932 063 891 On 8 Sep 2015 05:42, "Paul Arnold" paul@barfoo.net wrote:
Hi,
Is there any chance that edc25d7 will be backported to the 4.3 branch? It would be nice to have it in the upcoming 4.3.2 release.
thanks, Paul
On 9 August 2015 at 03:33, Charles Chance notifications@github.com wrote:
Hi,
Can you try with edc25d7, and confirm whether you still observe the same
behaviour?
Also make sure max_contacts is set the same on all nodes.
Cheers, Charles
— Reply to this email directly or view it on GitHub.
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
This is now in 4.3.
Cheers, Charles
On 8 September 2015 at 10:38, Charles Chance charles.chance@sipcentric.com wrote:
Hi,
I'm happy to backport, but it depends whether others see this as a new feature or a bug fix.
Personally I believe it is essential for the originally intended behaviour, but maybe someone else can comment?
Cheers, Charles
Charles Chance Managing Director
t. 0121 285 4400 m. 07932 063 891 On 8 Sep 2015 05:42, "Paul Arnold" paul@barfoo.net wrote:
Hi,
Is there any chance that edc25d7 will be backported to the 4.3 branch? It would be nice to have it in the upcoming 4.3.2 release.
thanks, Paul
On 9 August 2015 at 03:33, Charles Chance notifications@github.com wrote:
Hi,
Can you try with edc25d7, and confirm whether you still observe the
same behaviour?
Also make sure max_contacts is set the same on all nodes.
Cheers, Charles
— Reply to this email directly or view it on GitHub.
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
Hi,
Thanks, I will try this out today and get back to you.
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/265#issuecomment-129394822
Hi,
Do you want to keep this issue open for the save flag 0x04 replace action in dmq_usrloc or do you want to close this one and open a new one for the replace action.
FYI, for anyone else looking at this bug report, the particular issue I was experiencing was resolved by either not specifying a flag to save() or using the 0x01 flag and ensuring max_contacts was set properly.
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/265#issuecomment-130093889
I'm happy to leave it open since the issue is still there if overwriting contacts (that is, passing 0x04 flag to registrar save function).
On 11 August 2015 at 23:16, 00Asgaroth00 notifications@github.com wrote:
Hi,
Do you want to keep this issue open for the save flag 0x04 replace action in dmq_usrloc or do you want to close this one and open a new one for the replace action.
FYI, for anyone else looking at this bug report, the particular issue I was experiencing was resolved by either not specifying a flag to save() or using the 0x01 flag and ensuring max_contacts was set properly.
— Reply to this email directly or view it on GitHub https://github.com/kamailio/kamailio/issues/265#issuecomment-130093889.
sr-dev mailing list sr-dev@lists.sip-router.org http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-dev
I'm happy to leave it open since the issue is still there if overwriting contacts (that is, passing 0x04 flag to registrar save function).
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/265#issuecomment-130101793
Just looking into this now but I am struggling to reproduce the issue - can you confirm you are still seeing it with the 0x04 flag on save() and that all instances are running the most up-to-date version (with delete replication)?
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/265#issuecomment-134342738
I will re-enable the 0x04 flag shortly and get back to you with findings.
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/265#issuecomment-134539846
Hi, I have re-enabled the 0x04 flag now for a while, and I don't see the original behaviour anymore, 0x04 seems to be replacing the contact properly now.
I will leave it running like this for a while and see if I see it crop up again.
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/265#issuecomment-134563205
Closing to keep the tracker with only active issues. Re-open if it pops up again.
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/265#issuecomment-134991139
Closed #265.
--- Reply to this email directly or view it on GitHub: https://github.com/kamailio/kamailio/issues/265#event-392800434
Reopened #265.
Hello,
I can reproduce the issue, with kamailio 4.4.6+jessie from kamailio debian repository: * 0x04 flag is set on save() * old contacts are deleted on the server receiving the REGISTER message * old contacts are not deleted on servers being notified via DMQ
server1 (REGISTER message):
DEBUG: usrloc [ucontact.c:1692]: update_ucontact(): exists callback for type= UL_CONTACT_UPDATE DEBUG: usrloc [ul_callback.h:84]: run_ul_callbacks(): contact=0x7f0096e0b548, callback type 2/15, id 0 entered DEBUG: dmq_usrloc [usrloc_sync.c:578]: dmq_ul_cb_contact(): Callback from usrloc with type=2 DEBUG: dmq_usrloc [usrloc_sync.c:548]: usrloc_dmq_send_contact(): sending serialized data {"action":1,"aor":"+33564093848","ruid":"uloc-5a86b8c5-31e0-2","c":"sip:+33564093848@xxx:41502;ob","received":"","path":"","callid":"ntoWjs3R3WpP9Z5rsi7Npmr2rRGKstls","user_agent":"CSipSimple_porridge-23/r2457","instance":"","expires":1518779539,"cseq":55952,"flags":0,"cflags":0,"q":-1,"last_modified":1518778639,"methods":8159,"reg_id":0} DEBUG: dmq_usrloc [usrloc_sync.c:299]: usrloc_dmq_send(): sending dmq broadcast...
server2 (DMQ recipient):
DEBUG: dmq_usrloc [usrloc_sync.c:327]: usrloc_dmq_handle_msg(): dmq message received from sip:usrloc@172.16.67.15:5060 DEBUG: dmq_usrloc [usrloc_sync.c:429]: usrloc_dmq_handle_msg(): Received DMQ_UPDATE. Update contact info... DEBUG: dmq_usrloc [usrloc_sync.c:64]: add_contact(): aor: +33564093848 DEBUG: dmq_usrloc [usrloc_sync.c:65]: add_contact(): ci->ruid: uloc-5a86b8c5-31e0-2 DEBUG: dmq_usrloc [usrloc_sync.c:66]: add_contact(): aorhash: -1799456359 DEBUG: dmq_usrloc [usrloc_sync.c:72]: add_contact(): Found contact DEBUG: usrloc [ucontact.c:1692]: update_ucontact(): exists callback for type= UL_CONTACT_UPDATE DEBUG: usrloc [ul_callback.h:84]: run_ul_callbacks(): contact=0x7f3900243bd0, callback type 2/15, id 0 entered DEBUG: dmq_usrloc [usrloc_sync.c:578]: dmq_ul_cb_contact(): Callback from usrloc with type=2 DEBUG: dmq_usrloc [usrloc_sync.c:600]: dmq_ul_cb_contact(): Contact received from DMQ... skip DEBUG: usrloc [ucontact.c:1004]: db_update_ucontact_ruid(): ruid:uloc-5a86b8c5-31e0-2 DEBUG: usrloc [ucontact.c:1133]: db_update_ucontact_ruid(): contact:sip:+33564093848@xxx:41502;ob DEBUG: dmq_usrloc [usrloc_sync.c:74]: add_contact(): Release record DEBUG: dmq_usrloc [usrloc_sync.c:76]: add_contact(): Unlock udomain
the recipient receive an UPDATE message only. according to usrloc_sync.c:usrloc_dmq_handle_msg(), UPDATE message add the new contact only (execute add_contact()), but the other one is not deleted
and there is no DMQ_RM message generated from the emitter
Closed #265.
Open a new issue, the item here is for another version. Thanks!
-
00Asgaroth00 -
Charles Chance
-
Charles Chance -
Daniel-Constantin Mierla
-
Guillaume Bour
-
Paul Arnold