Never mind, the missing contact was being removed when a REGISTER was received.

In my cfg, I was using:

save("location", "0x04")

The 0x04 flag, of course, causes all existing entries for the AOR to be removed.

Cheers,

Dave.

On 25 Jun 2014, at 10:45 am, David Wilson <dw@zaq.com.au> wrote:

Thanks Daniel,

Rather than changing the kamctl script, I can just run a command like:

    kamctl mi ul_add location <user> <uri> <expires> <q> 0 0 0 0

When I run this and set expires to 0  (as per the comment in kamctl, "expires 0 means persistent contact"),  kamctl ul show shows expires=-1403662437 which siremis shows as 1970-01-01 08:00:00.

Within 20 minutes, the entry is gone and I'm not sure why.  Is the 8:00 (my timezone is UTC+8) causing a check for zero to fail or is there something else I'm missing?

For reference, I'm using db_mode=2 for usrloc.

Regards,

Dave.

On 20 Jun 2014, at 6:00 pm, sr-users-request@lists.sip-router.org wrote:

Date: Fri, 20 Jun 2014 07:38:50 +0200
From: Daniel-Constantin Mierla <miconda@gmail.com>
To: "Kamailio (SER) - Users Mailing List"
<sr-users@lists.sip-router.org>
Subject: Re: [SR-Users] Setting priority (q)  for kamctl ul add

Hello,

On 20/06/14 06:16, David Wilson wrote:

Hi All,

I'm trying to add a permanent usrloc entry via kamctl ul add.

This works, but the created entry has a q value of 1.0 which is higher than I need.

Is there a way to either:

1.  Specify a q value when using kamctl ul add, or

apparently the Q is hardcoded, a way to fix it is to edit kamctl (which 
is a shell script), search for 'ul_add' and update the 1.0 value in that 
command.

2.  Edit the q value of an existing record by using a kamctl command.

Maybe removing and add it it with same other attributes...

Cheers,
Daniel

_______________________________________________
SIP Express Router (SER) and Kamailio (OpenSER) - sr-users mailing list
sr-users@lists.sip-router.org
http://lists.sip-router.org/cgi-bin/mailman/listinfo/sr-users

-- 
Daniel-Constantin Mierla - http://www.asipto.com
http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda