At 14:38 15/12/2006, Klaus Darilion wrote:
Jiri Kuthan wrote:
At 16:03 14/12/2006, samuel wrote:
It might be due to a DNS query....whenver a request has to be forwarded to a domain, openSER makes a DNS query to resolv the IP. During this operation, the child processing the request will not answer to further incoming messages.
Hard to say without more input what the cause may be. Indeed common suspects are DNS (or any other blocking operation, such as dataabse) or timers, but again it is hard to say without more input.
If it is DNS or TCP-based blocking, it may be worthwhile trying genuine SER/ottendorf which is having IP blacklisting and DNS cachine in there -- this is indeed something which has been pressing us for a while.
How about the TTL in ser's cache? Does it obey the TTL in the DNS responses? If yes, then there is no beneift over using a "near" resolving bind.
How far it obeys is configurable, dns-ttl is used as default. Mainly though it supports multiple destinations for a DNS name (reliability impact; serial forking) and it is combined with blacklisting, i.e., the IP adresses which prove unavailable are not used.
see http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/doc/dns.txt?rev=HEA... http://cvs.berlios.de/cgi-bin/viewcvs.cgi/ser/sip_router/doc/dst_blacklist.t...
-jiri
-- Jiri Kuthan http://iptel.org/~jiri/