28 May
2009
28 May
'09
7:24 p.m.
On May 28, 2009 at 22:15, Juha Heinanen <jh(a)tutpro.com> wrote:
Andrei Pelinescu-Onciul writes:
dst_blacklist_init=off if you want it disabled without the possibility
to enable it later ar runtime.
use_dst_blacklist=off, if you want to start with it disabled, but with
the possibility to enable it later at runtime via rpcs
(e.g. $ sercmd cfg.set_int_now core use_dst_blacklist 1 ).
Note however that the blacklist in sr is ip based and not dns based
(I don't know how the blacklist worked in k).
Andrei
It should work as it is. Are you sure you
haven't mispelled it somehow?
Could you send me the output of ser -cf your.cfg ?
sorry, i rechecked and the line sip-router is complaining is the next
one:
rev_dns=no
dns_use_search_list=no
dns_try_ipv6=no
disable_dns_blacklist=yes ********** this one
# sip-router -cf /etc/sip-router/sip-router.cfg
0(8340) : <core> [cfg.y:2915]: parse error in config file, line 231, column 22:
syntax error
0(8340) : <core> [cfg.y:2915]: parse error in config file, line 231, column 22:
unknown config variable
0(8340) : <core> [cfg.y:2912]: parse error in config file, line 231, column 23-25:
ERROR: bad config file (3 errors)
0(8340) DEBUG: <core> [mem/shm_mem.c:261]: shm_mem_destroy
according to cookbook there are these dnsblacklist related variables:
dst_blacklist_expire|dst_blacklist_ttl
dst_blacklist_gc_interval
dst_blacklist_init
dst_blacklist_mem
perhaps one of those can be used to get the same effect as k
disable_dns_blacklist=yes?