#303 usrloc:db_mode=2 causes register:max_contacts=1 to fail

1.6.x
closed-invalid
modules (454)
5
2010-08-01
2010-07-27
takeshi
No

I'm testing with r. 7059 to confirm register:max_contacts=1 is always enforced (I'm using save("location", "f"'). If I set usrloc:db_mode=0, it seems to be working fine: I keep two terminal re-registering and I can see the contact of the most recent REGISTER always replaces the previous contact.
However, if I just set usrloc:db_mode=2, then this starts to fail and I can see 2 contacts present in both db and by querying contact info using fifo.
This is easily recreated by using 2 instances of SIPp to simulate 2 terminals.

Discussion

  • takeshi
    takeshi
    2010-07-27

    actual cfg file used for tests

     
    Attachments
    • assigned_to: nobody --> bogdan_iancu
    • status: open --> closed-invalid
     
  • Just tested with the latest 1.6 SVN branch and it worked perfectly with the following cfg:

    modparam("registrar", "max_contacts", 1)
    modparam("registrar", "max_expires", 30)
    modparam("registrar", "min_expires", 30)
    modparam("registrar", "default_expires", 30)

    modparam("usrloc", "db_mode", 2)
    modparam("usrloc", "cseq_delay", 10)
    modparam("usrloc", "use_domain", 1)

    save("location","f");

    I used 2 kphones with the same user to register.
    Regards,
    Bogdan