Register interval

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Philippe wrote:
> Hi Benny,
> 
> By examinig the way the client registration is implemented, we found 
> that the tsx_callback function of sip_reg.c file examines all the 
> contacts to determine the expiration interval. According to RFC 3261, 
> this is not correct as only the contact that was registered by the 
> client should be considered. This cause some troubles when others UA 
> have registered the same AOR:
> 
> -          The registration is refreshed too early as the interval taken 
> is the minimum of all the bindings and the expiration parameter of the 
> reg_c callback is incorrect too
> 
> -          The expiration parameter of the reg_c callback indicates a 
> non-null values for the unregister callback, as others bindings remains. 
> This prevents the application or pjsua layer to correctly determine that 
> we are unregistered.
> 
> What is your thinking about this?

Sorry for the late reply. I've just fixed this in 
http://www.pjsip.org/trac/ticket/371.

thanks!
  -benny





[Index of Archives]     [Asterisk Users]     [Asterisk App Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Security]     [Bugtraq]     [Linux]     [Linux OMAP]     [Linux MIPS]     [Linux API]
  Powered by Linux