[SIPForum-discussion] Registration timer

Boris vercher boris.vercher at ilexia.com
Wed Aug 6 07:31:38 UTC 2008


"registration timer /2" Is an industry accepted practice for register
keepalive

 

 

From: sreekant nair [mailto:sreekant_nair at yahoo.com] 
Sent: mardi 5 août 2008 21:30
To: Boris vercher; shakthi_msc at yahoo.com; SIP
Subject: Re: [SIPForum-discussion] Registration timer

 

Very Interesting. 

Is "registration timer /2" specified in any RFC? or just an industry
accepted practice? I could not find any reference in RFC 3261.

Thanks in advance

Regards
Sreekant

 

----- Original Message ----
From: Boris vercher <boris.vercher at ilexia.com>
To: shakthi_msc at yahoo.com; SIP <discussion at sipforum.org>
Sent: Tuesday, August 5, 2008 11:52:28 AM
Subject: Re: [SIPForum-discussion] Registration timer

You have to re register at «  registration timer  / 2 » even if a sip
registrar have to support  “ registration timer  “ + 10s, before clearing
resgistration, if no register keep alive occur.

 

So re registration occurs before “ registration timers expires “. Otherwise
you can be unregistered during 1 or 2s ( for example )

 

When you reregister the timer is reset to the new value.

 

However when an UA send a register with “ registration timer  “, the value
that will be used, will be the timer “ registration expires “ sent back by
registrar. And not the original one sent by UA.

 

Boris 

 

From: discussion-bounces at sipforum.org
[mailto:discussion-bounces at sipforum.org] On Behalf Of Shakthi
Sent: mardi 5 août 2008 14:35
To: SIP
Subject: [SIPForum-discussion] Registration timer

 


During the SIP registration, an re-registration will occur only when the
registration timer expires. My question is, "Will the 'expired timer' from
the cache is cleared for every cycle before the re-registration occurs?"

 

 

 

Thanks in Advance

 

  -Shakthi

 

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://sipforum.org/pipermail/discussion/attachments/20080806/d6c1128d/attachment-0002.html>


More information about the discussion mailing list