On 28-10 10:41, Ricardo Martinez wrote:
Jan,
by the way you mean that is mutually exclusive with the :
modparam("registrar","max_expires", 300)
^^ With this one.
or with the :
modparam("registrar","append_branches", 0)
modparam("registrar","desc_time_order", 1)
Thanks.
Ricardo.
-----Mensaje original-----
De: 'Jan Janak' [mailto:jan@iptel.org]
Enviado el: Jueves, 28 de Octubre de 2004 9:28
Para: Ricardo Martinez
CC: Marian Dumitru; 'serusers(a)lists.iptel.org'
Asunto: Re: [Serusers] Question about REGISTER.
Yes, it is independent of the version of the RTP proxy.
Jan.
On 28-10 10:27, Ricardo Martinez wrote:
> Thanks Janak.
> A last question, is also exclusive with mediaproxy?.
>
> Thanks
>
> Ricardo.-
>
> -----Mensaje original-----
> De: Jan Janak [mailto:jan@iptel.org]
> Enviado el: Jueves, 28 de Octubre de 2004 9:22
> Para: Marian Dumitru
> CC: Ricardo Martinez; 'serusers(a)lists.iptel.org'
> Asunto: Re: [Serusers] Question about REGISTER.
>
>
> On 27-10 19:07, Marian Dumitru wrote:
> > Hi Ricardo,
> >
> > I see your problem. What you can do is to set registrar module to use
> > only the most recent registered contact:
> > modparam("registrar","append_branches", 0)
> > modparam("registrar","desc_time_order", 1)
> >
> > Other thing you can do is to limit the registration time
> > modparam("registrar","max_expires", 300)
> >
> > to use this, be sure your SIP clients supports expire modification by
> > server.
>
> Unfortunately this is mutually exclusive with nathelper. Nathelper
> will rewrite the IP in Contact with the source IP of the packet
> carrying the REGISTER message and user agents will not be able to
> match the Contact in 200 OK and thus update the expires value.
>
> This has been fixed in the development version of ser. It does not
> rewrite the IP in Contact anymore, the source IP of the REGISTER
> message is stored separately in the user location database.
>
> Jan.