[Spce-user] Multiple ATA registrations

[Dave Massey]

Hey sorry I have not been back in touch regarding this issue, I and my whole family got the flu and motivation to get off the couch  has been tough.

I left the system sit unused but operating sorta speak for a pile of days and logged in to check the multiple entries.
I have the ATAs set to 60 seconds REGISTER, and not rebooting them at all, but just letting them run and do their thing the multiple entries stack up again without touching/rebooting the ATA.

 When run the command:
root at sip:~# ngcp-kamctl proxy ul show ddufresne at sip.optionsdsl.ca
Contact:: <sip:ddufresne at 24.102.50.63:49152>;q=;expires=48;flags=0x0;cflags=0x0;socket=<udp:172.16.10.55:5062>;methods=0x129F;user_agent=<OBIHAI/OBi100-1.3.0.2744>;path=<<sip:lb at 172.16.10.55;lr>>

It only shows one entry, great! But the web interface/CSC  show 40  entries that all are identical in expiry time.  I fI hit the trash can, all of them disappear until the ATA sends a new REGISTER, then one entry shows back up, rinse and repeat.  












On 2012-11-15, at 4:47 PM, Skyler <skchopperguy at gmail.com> wrote:

Hey,

 This is actually built-in already. The records should be clearing out automatically based on the expires= .

What do you see with this command:

ngcp-kamctl proxy ul show user at domain

Skyler
> Hi,
> 
> On Thu, Nov 15, 2012 at 12:45 PM, Dave Massey <dave at optionsdsl.ca> wrote:
> Oddly enough it looks normal now. ..  
> 
> Excuse me while I bang my head on the wall. :(
> 
> How do I change the expiry time?
> 
> 
> So just to clarify, all of the old entries from the DB are gone now correct?
> 
>  Registration expiry is submitted to the proxy by the device. You can specify pretty much any time^ you want. There is a caveat in there though. Earlier in the thread, we looked up the default_expires, min_expires and max_expires settings for your proxy. What do these mean and how does this tie together?
> 
>  When a device requests registration, it sends a 'Preferred Expires Time'. Which in your case, is 60 seconds. This means that the device 'advises' it will send another registration request in the next 60 seconds.
> 
>  On the Proxy side, it receives this request for 60 second expiry. It then looks at its own 'min_expires and max_expires' time and measures against the device' request. Then approves or disapproves with an updated expires=. Disapproves?
> 
>  Let's say your proxy min_expires=90, max_expires=3600 and default_expires=3600. Your device requests an expires=4000, well that is more than the max_expires; so the proxy allows registration BUT replies with an updated expires=3600. Basically "Be advised that I am deleting your AOR in 3600 seconds, like it or not".
> 
>  After all that, you really don't need to think about what I just said ;)
> 
>  Your proxy min_expires=60 and max_expires=43200. Meaning you really can choose any expires time you want on the device.. ;)
> 
> 
> Skyler

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20121118/4a896ba8/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2012-11-18 at 7.21.18 PM.png
Type: image/png
Size: 102690 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20121118/4a896ba8/attachment-0002.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screen Shot 2012-11-18 at 7.21.28 PM.png
Type: image/png
Size: 20360 bytes
Desc: not available
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20121118/4a896ba8/attachment-0003.png>