Re: [SR-Users] max_contacts does not work as expected

2017-11-29 Thread Gholamreza Sabery
No body has any other ideas?

On Sun, Nov 26, 2017 at 11:49 AM, Gholamreza Sabery 
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 
> wrote:
>
>> Thank you very much Dimitri, good point.
>>
>> On Fri, Nov 17, 2017 at 2:38 PM, Dmitri Savolainen > > 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||e   |
>>> | 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 :
>>>
 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 <
 mico...@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.sab...@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 <
>> mico...@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: 
>>>domain: NULL
>>>   contact: sip:@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: 
>>>reg_id: 0
>>> server_id: 11369
>>> connection_id: -1
>>> keepalive: 1
>>> partition: 14
>>> *** 2. row ***
>>>id: 171296746
>>>  ruid: uloc-2c69-59db6c73-7f2-eb5d92
>>>  username: 
>>>domain: NULL
>>>   contact: sip:@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: 
>>>reg_id: 0
>>> server_id: 11369
>>> 

Re: [SR-Users] max_contacts does not work as expected

2017-11-26 Thread Gholamreza Sabery
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 
wrote:

> Thank you very much Dimitri, good point.
>
> On Fri, Nov 17, 2017 at 2:38 PM, Dmitri Savolainen 
> 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||e   |
>> | 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 :
>>
>>> 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 <
>>> mico...@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  wrote:

> Hello Daniel,
>
> I use a value of 3 for db_mode.
>
> On Wed, Nov 15, 2017 at 11:11 AM, Daniel-Constantin Mierla <
> mico...@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: 
>>domain: NULL
>>   contact: sip:@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: 
>>reg_id: 0
>> server_id: 11369
>> connection_id: -1
>> keepalive: 1
>> partition: 14
>> *** 2. row ***
>>id: 171296746
>>  ruid: uloc-2c69-59db6c73-7f2-eb5d92
>>  username: 
>>domain: NULL
>>   contact: sip:@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: 
>>reg_id: 0
>> server_id: 11369
>> connection_id: -1
>> keepalive: 1
>> partition: 23
>> *** 3. row ***
>>id: 171296747
>>  ruid: uloc-2c69-59db6c73-80f-541d92
>>  username: 
>>

Re: [SR-Users] max_contacts does not work as expected

2017-11-17 Thread Gholamreza Sabery
Thank you very much Dimitri, good point.

On Fri, Nov 17, 2017 at 2:38 PM, Dmitri Savolainen 
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||e   |
> | 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 :
>
>> 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 <
>> mico...@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 
>>> wrote:
>>>
 Hello Daniel,

 I use a value of 3 for db_mode.

 On Wed, Nov 15, 2017 at 11:11 AM, Daniel-Constantin Mierla <
 mico...@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: 
>domain: NULL
>   contact: sip:@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: 
>reg_id: 0
> server_id: 11369
> connection_id: -1
> keepalive: 1
> partition: 14
> *** 2. row ***
>id: 171296746
>  ruid: uloc-2c69-59db6c73-7f2-eb5d92
>  username: 
>domain: NULL
>   contact: sip:@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: 
>reg_id: 0
> server_id: 11369
> connection_id: -1
> keepalive: 1
> partition: 23
> *** 3. row ***
>id: 171296747
>  ruid: uloc-2c69-59db6c73-80f-541d92
>  username: 
>domain: NULL
>   contact: sip:@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: 

Re: [SR-Users] max_contacts does not work as expected

2017-11-17 Thread Dmitri Savolainen
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||e   |
| 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 :

> 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 <
> mico...@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 
>> wrote:
>>
>>> Hello Daniel,
>>>
>>> I use a value of 3 for db_mode.
>>>
>>> On Wed, Nov 15, 2017 at 11:11 AM, Daniel-Constantin Mierla <
>>> mico...@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: 
domain: NULL
   contact: sip:@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: 
reg_id: 0
 server_id: 11369
 connection_id: -1
 keepalive: 1
 partition: 14
 *** 2. row ***
id: 171296746
  ruid: uloc-2c69-59db6c73-7f2-eb5d92
  username: 
domain: NULL
   contact: sip:@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: 
reg_id: 0
 server_id: 11369
 connection_id: -1
 keepalive: 1
 partition: 23
 *** 3. row ***
id: 171296747
  ruid: uloc-2c69-59db6c73-80f-541d92
  username: 
domain: NULL
   contact: sip:@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: 
reg_id: 0
 server_id: 11369
 connection_id: -1
 keepalive: 1
 partition: 15


 ___
 Kamailio (SER) - Users Mailing 
 

Re: [SR-Users] max_contacts does not work as expected

2017-11-16 Thread Gholamreza Sabery
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  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 
> wrote:
>
>> Hello Daniel,
>>
>> I use a value of 3 for db_mode.
>>
>> On Wed, Nov 15, 2017 at 11:11 AM, Daniel-Constantin Mierla <
>> mico...@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: 
>>>domain: NULL
>>>   contact: sip:@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: 
>>>reg_id: 0
>>> server_id: 11369
>>> connection_id: -1
>>> keepalive: 1
>>> partition: 14
>>> *** 2. row ***
>>>id: 171296746
>>>  ruid: uloc-2c69-59db6c73-7f2-eb5d92
>>>  username: 
>>>domain: NULL
>>>   contact: sip:@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: 
>>>reg_id: 0
>>> server_id: 11369
>>> connection_id: -1
>>> keepalive: 1
>>> partition: 23
>>> *** 3. row ***
>>>id: 171296747
>>>  ruid: uloc-2c69-59db6c73-80f-541d92
>>>  username: 
>>>domain: NULL
>>>   contact: sip:@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: 
>>>reg_id: 0
>>> server_id: 11369
>>> connection_id: -1
>>> keepalive: 1
>>> partition: 15
>>>
>>>
>>> ___
>>> Kamailio (SER) - Users Mailing 
>>> Listsr-users@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@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] max_contacts does not work as expected

2017-11-16 Thread Daniel-Constantin Mierla
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
> > wrote:
>
> Hello Daniel,
>
> I use a value of 3 for db_mode.
>
> On Wed, Nov 15, 2017 at 11:11 AM, Daniel-Constantin Mierla
> > 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: 
>>    domain: NULL
>>   contact: sip:@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: 
>>    reg_id: 0
>>     server_id: 11369
>> connection_id: -1
>>     keepalive: 1
>>     partition: 14
>> *** 2. row ***
>>    id: 171296746
>>  ruid: uloc-2c69-59db6c73-7f2-eb5d92
>>  username: 
>>    domain: NULL
>>   contact: sip:@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: 
>>    reg_id: 0
>>     server_id: 11369
>> connection_id: -1
>>     keepalive: 1
>>     partition: 23
>> *** 3. row ***
>>    id: 171296747
>>  ruid: uloc-2c69-59db6c73-80f-541d92
>>  username: 
>>    domain: NULL
>>   contact: sip:@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: 
>>    reg_id: 0
>>     server_id: 11369
>> connection_id: -1
>>     keepalive: 1
>>     partition: 15
>>
>>
>> ___
>> Kamailio (SER) - Users Mailing List
>> sr-users@lists.kamailio.org 
>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>> 
>
> -- 
> Daniel-Constantin Mierla
> www.twitter.com/miconda  -- 
> 

Re: [SR-Users] max_contacts does not work as expected

2017-11-16 Thread Mojtaba
Hello.
In Kamailio when the uac is registerd in new AOR, the other AOR is take
afew minute until expired time is occure.
As you mentioned you set db_mode=3, becuase the database is should be
updated,It may take more time to update.
Be notice that if the two different AOR is exist in kamailio,No more
Rrgister requests is accepted with Kamailio.
With Regards.
Mojtaba Esfandiari.S
On 16 Nov 2017 19:22, "Gholamreza Sabery"  wrote:

> No ideas?
>
> On Wed, Nov 15, 2017 at 3:27 PM, Gholamreza Sabery 
> wrote:
>
>> Hello Daniel,
>>
>> I use a value of 3 for db_mode.
>>
>> On Wed, Nov 15, 2017 at 11:11 AM, Daniel-Constantin Mierla <
>> mico...@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: 
>>>domain: NULL
>>>   contact: sip:@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: 
>>>reg_id: 0
>>> server_id: 11369
>>> connection_id: -1
>>> keepalive: 1
>>> partition: 14
>>> *** 2. row ***
>>>id: 171296746
>>>  ruid: uloc-2c69-59db6c73-7f2-eb5d92
>>>  username: 
>>>domain: NULL
>>>   contact: sip:@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: 
>>>reg_id: 0
>>> server_id: 11369
>>> connection_id: -1
>>> keepalive: 1
>>> partition: 23
>>> *** 3. row ***
>>>id: 171296747
>>>  ruid: uloc-2c69-59db6c73-80f-541d92
>>>  username: 
>>>domain: NULL
>>>   contact: sip:@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: 
>>>reg_id: 0
>>> server_id: 11369
>>> connection_id: -1
>>> keepalive: 1
>>> partition: 15
>>>
>>>
>>> ___
>>> Kamailio (SER) - Users Mailing 
>>> Listsr-users@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
>>>
>>>
>>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] max_contacts does not work as expected

2017-11-16 Thread Gholamreza Sabery
No ideas?

On Wed, Nov 15, 2017 at 3:27 PM, Gholamreza Sabery 
wrote:

> Hello Daniel,
>
> I use a value of 3 for db_mode.
>
> On Wed, Nov 15, 2017 at 11:11 AM, Daniel-Constantin Mierla <
> mico...@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: 
>>domain: NULL
>>   contact: sip:@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: 
>>reg_id: 0
>> server_id: 11369
>> connection_id: -1
>> keepalive: 1
>> partition: 14
>> *** 2. row ***
>>id: 171296746
>>  ruid: uloc-2c69-59db6c73-7f2-eb5d92
>>  username: 
>>domain: NULL
>>   contact: sip:@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: 
>>reg_id: 0
>> server_id: 11369
>> connection_id: -1
>> keepalive: 1
>> partition: 23
>> *** 3. row ***
>>id: 171296747
>>  ruid: uloc-2c69-59db6c73-80f-541d92
>>  username: 
>>domain: NULL
>>   contact: sip:@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: 
>>reg_id: 0
>> server_id: 11369
>> connection_id: -1
>> keepalive: 1
>> partition: 15
>>
>>
>> ___
>> Kamailio (SER) - Users Mailing 
>> Listsr-users@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
>>
>>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] max_contacts does not work as expected

2017-11-15 Thread Gholamreza Sabery
Hello Daniel,

I use a value of 3 for db_mode.

On Wed, Nov 15, 2017 at 11:11 AM, Daniel-Constantin Mierla <
mico...@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: 
>domain: NULL
>   contact: sip:@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: 
>reg_id: 0
> server_id: 11369
> connection_id: -1
> keepalive: 1
> partition: 14
> *** 2. row ***
>id: 171296746
>  ruid: uloc-2c69-59db6c73-7f2-eb5d92
>  username: 
>domain: NULL
>   contact: sip:@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: 
>reg_id: 0
> server_id: 11369
> connection_id: -1
> keepalive: 1
> partition: 23
> *** 3. row ***
>id: 171296747
>  ruid: uloc-2c69-59db6c73-80f-541d92
>  username: 
>domain: NULL
>   contact: sip:@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: 
>reg_id: 0
> server_id: 11369
> connection_id: -1
> keepalive: 1
> partition: 15
>
>
> ___
> Kamailio (SER) - Users Mailing 
> Listsr-users@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
>
>
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


Re: [SR-Users] max_contacts does not work as expected

2017-11-14 Thread Daniel-Constantin Mierla
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: 
>    domain: NULL
>   contact: sip:@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: 
>    reg_id: 0
>     server_id: 11369
> connection_id: -1
>     keepalive: 1
>     partition: 14
> *** 2. row ***
>    id: 171296746
>  ruid: uloc-2c69-59db6c73-7f2-eb5d92
>  username: 
>    domain: NULL
>   contact: sip:@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: 
>    reg_id: 0
>     server_id: 11369
> connection_id: -1
>     keepalive: 1
>     partition: 23
> *** 3. row ***
>    id: 171296747
>  ruid: uloc-2c69-59db6c73-80f-541d92
>  username: 
>    domain: NULL
>   contact: sip:@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: 
>    reg_id: 0
>     server_id: 11369
> connection_id: -1
>     keepalive: 1
>     partition: 15
>
>
> ___
> Kamailio (SER) - Users Mailing List
> sr-users@lists.kamailio.org
> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla
www.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@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users


[SR-Users] max_contacts does not work as expected

2017-11-13 Thread Gholamreza Sabery
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: 
   domain: NULL
  contact: sip:@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: 
   reg_id: 0
server_id: 11369
connection_id: -1
keepalive: 1
partition: 14
*** 2. row ***
   id: 171296746
 ruid: uloc-2c69-59db6c73-7f2-eb5d92
 username: 
   domain: NULL
  contact: sip:@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: 
   reg_id: 0
server_id: 11369
connection_id: -1
keepalive: 1
partition: 23
*** 3. row ***
   id: 171296747
 ruid: uloc-2c69-59db6c73-80f-541d92
 username: 
   domain: NULL
  contact: sip:@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: 
   reg_id: 0
server_id: 11369
connection_id: -1
keepalive: 1
partition: 15
___
Kamailio (SER) - Users Mailing List
sr-users@lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users