<html><head><meta http-equiv="Content-Type" content="text/html; charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">if they are doing nonces on a shared realm, they should be sharing those nonces across their cluster. If they are not, every time it hits a diff member of the cluster you will get a stale nonce and have to go through that juggle again. This is just a side effect of how sip auth works.<div class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jun 19, 2018, at 12:50 PM, Marcin Kowalczyk <<a href="mailto:kowalma@gmail.com" class="">kowalma@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">Hi,<br class=""><br class=""> I'm having problem setting-up trunk with provider who does have muliple sip-proxies with not shared nonce db. <div class=""><br class=""><a href="http://sip.freeconet.pl/" class="">sip.freeconet.pl</a> resolves to 3 diffrent IP and FS does not cache/remeber IP that send back request. </div><div class=""><br class=""></div><div class="">So we have a case <br class="">FS->P1: Invite<br class="">P1 -> FS -> 407 + nonce<br class="">FS does again DNS lookup and <br class="">FS->P2 Invite with nonce from P1<br class="">P2->FS 407<br class="">FS fails call.<br class=""><br class="">Is there a way to force FS to send all messages within dialog to one IP only ?<br class=""><br class="">Regards<br class=""><br class=""></div></div></blockquote></div><br class=""></div></body></html>