< Previous by Date Date Index Next by Date >
  Thread Index Next in Thread >

[reSIProcate] (another) blacklist issue on resip 1.1


Hi,
We upgraded our application to use resiprocate 1.1 and some of our
automated tests started failing. These were Session Timer tests that
simulated a network failure by shutting down a SIP server in the middle
of a call. The test failures occurred because after it was restarted the
server was unavailable for 32s due to blacklisting (after a 408 with no
response). The error logged is this: 

9171 | 3013118896 | DnsResult.cxx:384 | Numeric result, but this result
is currently blacklisted: [ V4 192.168.20.88:25062 UDP target
domain=192.168.20.88 connectionId=0 ]

>From looking at the code and other posts related to blacklisting we
(hopefully) understand why this is happening, and the tests can be fixed
by adding a 32 second delay in a few places, but we're wondering if
there are other side-effects. For instance, our application is a cluster
of SIP servers (all based on resiprocate) that constantly exchange their
state using multicast, so there may be cases where a
failed-and-then-restarted server reports that it's available but is
actually unreachable for up to 32 seconds. On the other hand, our
application also talks to external servers whose status is unknown to
us, so blacklisting might be useful in those cases. 

While we consider the pros and cons of this, I was wondering if there
were any other options available in release 1.1, or any advice from
someone that's more familiar with what's going on here.
  Regards,
   Tom Joyner