| < Previous by Date | Date Index | Next by Date > |
| < Previous in Thread | Thread Index | Next in Thread > |
Right, got that, but because the first record times out, the 2nd one is never tried, thus never added to the whitelist.On Thu, Aug 15, 2013 at 1:43 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:
From the wiki:
- DNS path is whitelisted when we receive any response that doesn't result in a grey list or a black list
By response it is referring to a SIP response (ie: 200, 404, etc.). So once a good path is found, resip will stick to it.ScottOn Thu, Aug 15, 2013 at 2:16 PM, Nathan Stratton <nathan@xxxxxxxxxxxx> wrote:
On Thu, Aug 15, 2013 at 12:44 PM, Scott Godin <sgodin@xxxxxxxxxxxxxxx> wrote:
Hi Nathan,For Whitelisting - what do you mean about knowing all the hosts upfront? I was referring to enabling the resip DNS Whitelisting feature - this doesn't require knowing anything up front.I guess I don't understand how a record would get whitelisted. The DUM would get two records back from the SRV record, and try the first that would be grey listed because of a timeout. It looks like a path is whitelisted when there is a response that does not end in grey or black.I guess I thought that because the 2nd record was never tried, you would need to add them to the whitelist before hand so that on the next request you would try the 2nd host first rather then the first timeout host.--><>
Nathan Stratton Founder, CTO Exario Networks, Inc.
nathan at robotics.net nathan at exarionetworks.com--><>
Nathan Stratton Founder, CTO Exario Networks, Inc.
nathan at robotics.net nathan at exarionetworks.com