2010/7/2 Inca Rose <incar...@gmail.com>: > I dont know if this only happen to me or I'm not using a configuration flag > that is document, but I have a very hard time figuring this out. ... > The problem is that the next REGISTER goes again to 1.2.3.4. > There is no mechanism that nta can remember that 1.2.3.4 is not answering > and put it at the bottom of the list and continue to use 1.2.3.5, the > last one that did respond ? > In other words, how to force the stack to use from now 1.2.3.5 and not > 1.2.3.4 ???
We would need blacklisting/graylisting for the 1.2.3.4. The current code implements graylisting for SRV records (by manipulating their priority, if I recall correctly). However, there is no priority associated with A records, so we would need a different solution. Perhaps a list (or binary tree or hash table or ...) of bad IP addresses/ports/protocols? -- Pekka.Pessi mail at nokia.com ------------------------------------------------------------------------------ This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first _______________________________________________ Sofia-sip-devel mailing list Sofia-sip-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sofia-sip-devel
