[Devel] CVS commitlog: sip-server/modules/registrar README reg_mod.c reg_mod.h save.c sip-server/modules/registrar/doc registrar_user.sgml sip-server/modules/usrloc README dlist.c ucontact.h sip-server/modules/usrloc/doc usrloc_user.sgml ...

Andreas Granig andreas.granig at inode.info
Tue Feb 27 12:01:40 CET 2007


Thank god there is 
http://openser.org/dokuwiki/doku.php/install:1.1.x-to-1.2.x

Hopefully, all the small changes are documented there (hint: the one 
below isn't yet) ;o)

Cheers,
Andreas

Bogdan-Andrei Iancu wrote:
> Hi Juha,
> 
> yes, there is an impact on the script, but very small. The only change is:
>    modparam("registrar", "sip_natping_flag", x )
>    goes into
>    modparam("nathelper","sipping_bflag",x)
> 
> regards,
> bogdan
> 
> Juha Heinanen wrote:
>> Bogdan-Andrei Iancu writes:
>>
>>  >   fixed consistency problem with the NAT flag.  >    - applied 
>> patch from Marcus Hunger - get NAT flag from branch
>>  >   flags and not  >      from the internal usrloc flags in 
>> "get_all_ucontacts".
>>  >    - moved the flag for marking SIP pinging from message flag to
>>  >   branch flag (to  >      be consistent with the nat flag, also 
>> branch flag)
>>  >    - SIP ping flag moved from the registrar to nathelper module. You
>>  >   can use any  >      branch flag to mark the contact for SIP ping 
>> as all branch flags
>>  >   are saved  >      and restored by usrloc. Nathelper module just 
>> needs to know the
>>  >   flag index  >      to identify the contacts.
>>
>> do any of these patches have any effect on openser.cfg scripts or are
>> they just internal fixes?  if there is an effect, it would be nice to
>> have an example on how it was earlier and how it has to be now?
>>
>> -- juha
>>
>>   
> 
> 
> _______________________________________________
> Devel mailing list
> Devel at openser.org
> http://openser.org/cgi-bin/mailman/listinfo/devel


This e-mail is confidential and may well also be legally privileged. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this message from your system. Please do not copy it or use it for any purposes, or disclose its contents to any other person: to do so could be a breach of confidence. Thank you for your cooperation.



More information about the Devel mailing list