[SR-Users] max_contacts does not work as expected
Dmitri Savolainen
savolainen at erinaco.ru
Mon Dec 4 16:44:47 CET 2017
It seems strange. Colud you show all usrloc/registrar parameters?
2017-11-30 8:27 GMT+03:00 Gholamreza Sabery <gr.sabery at gmail.com>:
> No body has any other ideas?
>
> On Sun, Nov 26, 2017 at 11:49 AM, Gholamreza Sabery <gr.sabery at gmail.com>
> wrote:
>
>> I have tested it. These records are not actually expired. I even found a
>> situation in which a user has 16 different records in the database with the
>> same expiration time and the same received socket address. The records were
>> not expired yet. Is this a bug? Can it lead the system to be attacked?
>>
>>
>> On Fri, Nov 17, 2017 at 8:51 PM, Gholamreza Sabery <gr.sabery at gmail.com>
>> wrote:
>>
>>> Thank you very much Dimitri, good point.
>>>
>>> On Fri, Nov 17, 2017 at 2:38 PM, Dmitri Savolainen <
>>> savolainen at erinaco.ru> wrote:
>>>
>>>> One of them is expired in my mind and wiating for "usrloc"
>>>> "timer_interval" for clearing in DB. Expired contact will ignore while
>>>> calling. Like this
>>>> MariaDB [kamailio_dev]> select username, expires,
>>>> UNIX_TIMESTAMP(expires) - UNIX_TIMESTAMP(now()), user_agent from location
>>>> where username='000*888';
>>>> +----------+---------------------+--------------------------
>>>> -----------------------+--------------------------------+
>>>> | username | expires | UNIX_TIMESTAMP(expires) -
>>>> UNIX_TIMESTAMP(now()) | user_agent |
>>>> +----------+---------------------+--------------------------
>>>> -----------------------+--------------------------------+
>>>> | 000*888 | 2017-11-17 14:24:55 |
>>>> 1260 | Yealink SIP-T46G 28.81.0.25 |
>>>> | 000*888 | 2017-11-17 14:02:02 |
>>>> -113 | CSipSimpl||errrr |
>>>> | 000*888 | 2017-11-17 14:17:42 |
>>>> 827 | Bria Android 3.9.6 build 99409 |
>>>> +----------+---------------------+--------------------------
>>>> -----------------------+--------------------------------+
>>>>
>>>>
>>>> 2017-11-16 21:18 GMT+03:00 Gholamreza Sabery <gr.sabery at gmail.com>:
>>>>
>>>>> Dear Daniel,
>>>>>
>>>>> I can not use db_mode=1 in my setup; but I will try to test it.
>>>>>
>>>>> Regards
>>>>>
>>>>>
>>>>> On Thu, Nov 16, 2017 at 9:23 PM, Daniel-Constantin Mierla <
>>>>> miconda at gmail.com> wrote:
>>>>>
>>>>>> Very busy with the work this week ...
>>>>>>
>>>>>> To see if this a limitation of db only mode or not, can you test with
>>>>>> db_mode=1?
>>>>>>
>>>>>> Cheers,
>>>>>> Daniel
>>>>>>
>>>>>> On 16.11.17 16:51, Gholamreza Sabery wrote:
>>>>>>
>>>>>> No ideas?
>>>>>>
>>>>>> On Wed, Nov 15, 2017 at 3:27 PM, Gholamreza Sabery <
>>>>>> gr.sabery at gmail.com> wrote:
>>>>>>
>>>>>>> Hello Daniel,
>>>>>>>
>>>>>>> I use a value of 3 for db_mode.
>>>>>>>
>>>>>>> On Wed, Nov 15, 2017 at 11:11 AM, Daniel-Constantin Mierla <
>>>>>>> miconda at gmail.com> wrote:
>>>>>>>
>>>>>>>> Hello,
>>>>>>>>
>>>>>>>> what is the value of db_mode parameter for usrloc module?
>>>>>>>>
>>>>>>>> Cheers,
>>>>>>>> Daniel
>>>>>>>>
>>>>>>>> On 15.11.17 06:36, Gholamreza Sabery wrote:
>>>>>>>>
>>>>>>>> I have a Kamailio server that has:
>>>>>>>>
>>>>>>>> modparam("registrar", "max_contacts", 2)
>>>>>>>>
>>>>>>>> But recently I noticed some users have more than two records in the
>>>>>>>> location table. For example one of the users has three different records
>>>>>>>> with nearly the same information. The records are as follows. Is this
>>>>>>>> behavior normal? (I am using Kamailio 4XX).
>>>>>>>>
>>>>>>>> *************************** 1. row ***************************
>>>>>>>> id: 171296745
>>>>>>>> ruid: uloc-2c69-59db6c73-7ca-132d92
>>>>>>>> username: 999999999999
>>>>>>>> domain: NULL
>>>>>>>> contact: sip:999999999999 at 5.106.35.18:10362
>>>>>>>> received: sip:5.106.35.18:10361
>>>>>>>> path: NULL
>>>>>>>> expires: 2017-11-14 08:45:50
>>>>>>>> q: -1.00
>>>>>>>> callid: XpCnmaAhRF
>>>>>>>> cseq: 43
>>>>>>>> last_modified: 2017-11-14 08:44:50
>>>>>>>> flags: 0
>>>>>>>> cflags: 64
>>>>>>>> user_agent: android_1.1.0_samsung_SM-E500H
>>>>>>>> _7b271714c08b942aa821fc756cdd2e890a37069e/1.1.0 (belle-sip/1.4.2)
>>>>>>>> socket: udp:192.168.103.21:5060
>>>>>>>> methods: NULL
>>>>>>>> instance: <urn:uuid:8369ef6e-202b-4844-8928-492a7678c269>
>>>>>>>> reg_id: 0
>>>>>>>> server_id: 11369
>>>>>>>> connection_id: -1
>>>>>>>> keepalive: 1
>>>>>>>> partition: 14
>>>>>>>> *************************** 2. row ***************************
>>>>>>>> id: 171296746
>>>>>>>> ruid: uloc-2c69-59db6c73-7f2-eb5d92
>>>>>>>> username: 999999999999
>>>>>>>> domain: NULL
>>>>>>>> contact: sip:999999999999 at 5.106.35.18:10362
>>>>>>>> received: sip:5.106.35.18:10361
>>>>>>>> path: NULL
>>>>>>>> expires: 2017-11-14 08:45:50
>>>>>>>> q: -1.00
>>>>>>>> callid: BzMKuyJN8C
>>>>>>>> cseq: 50
>>>>>>>> last_modified: 2017-11-14 08:44:50
>>>>>>>> flags: 0
>>>>>>>> cflags: 64
>>>>>>>> user_agent: android_1.1.0_samsung_SM-E500H
>>>>>>>> _7b271714c08b942aa821fc756cdd2e890a37069e/1.1.0 (belle-sip/1.4.2)
>>>>>>>> socket: udp:192.168.103.21:5060
>>>>>>>> methods: NULL
>>>>>>>> instance: <urn:uuid:8369ef6e-202b-4844-8928-492a7678c269>
>>>>>>>> reg_id: 0
>>>>>>>> server_id: 11369
>>>>>>>> connection_id: -1
>>>>>>>> keepalive: 1
>>>>>>>> partition: 23
>>>>>>>> *************************** 3. row ***************************
>>>>>>>> id: 171296747
>>>>>>>> ruid: uloc-2c69-59db6c73-80f-541d92
>>>>>>>> username: 999999999999
>>>>>>>> domain: NULL
>>>>>>>> contact: sip:999999999999 at 5.106.35.18:10362
>>>>>>>> received: sip:5.106.35.18:10361
>>>>>>>> path: NULL
>>>>>>>> expires: 2017-11-14 08:45:50
>>>>>>>> q: -1.00
>>>>>>>> callid: 3p9P4PgZSv
>>>>>>>> cseq: 51
>>>>>>>> last_modified: 2017-11-14 08:44:50
>>>>>>>> flags: 0
>>>>>>>> cflags: 64
>>>>>>>> user_agent: android_1.1.0_samsung_SM-E500H
>>>>>>>> _7b271714c08b942aa821fc756cdd2e890a37069e/1.1.0 (belle-sip/1.4.2)
>>>>>>>> socket: udp:192.168.103.21:5060
>>>>>>>> methods: NULL
>>>>>>>> instance: <urn:uuid:8369ef6e-202b-4844-8928-492a7678c269>
>>>>>>>> reg_id: 0
>>>>>>>> server_id: 11369
>>>>>>>> connection_id: -1
>>>>>>>> keepalive: 1
>>>>>>>> partition: 15
>>>>>>>>
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Kamailio (SER) - Users Mailing Listsr-users at lists.kamailio.orghttps://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
>>>>>>>> Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com
>>>>>>>> Kamailio World Conference - www.kamailioworld.com
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Daniel-Constantin Mierlawww.twitter.com/miconda -- www.linkedin.com/in/miconda
>>>>>> Kamailio Advanced Training, Nov 13-15, 2017, in Berlin - www.asipto.com
>>>>>> Kamailio World Conference - www.kamailioworld.com
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Kamailio (SER) - Users Mailing List
>>>>> sr-users at lists.kamailio.org
>>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> Savolainen Dmitri
>>>>
>>>> _______________________________________________
>>>> Kamailio (SER) - Users Mailing List
>>>> sr-users at lists.kamailio.org
>>>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>>>>
>>>>
>>>
>>
>
> _______________________________________________
> Kamailio (SER) - Users Mailing List
> sr-users at lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
--
Savolainen Dmitri
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.kamailio.org/pipermail/sr-users/attachments/20171204/7be98673/attachment.html>
More information about the sr-users
mailing list