[Freeswitch-users] DNS cache on invite/register

[Marcin Kowalczyk]

Hi,

 I agree they should have shared nonce, but still I think FS should use
same IP for initial and challenged invite unless TTL for domain is not
expired.

Is there a way to force it to such behaviour? I've tried with fs_path but
seems this does not work for challenged invite neither

Somebody posted bug FS-8820 on same case but with different carrier.

Regards

Date: Tue, 19 Jun 2018 14:26:53 -0400
> 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.
>
>
> On Jun 19, 2018, at 12:50 PM, Marcin Kowalczyk <kowalma at gmail.com> wrote:
>
> Hi,
>
> I'm having problem setting-up trunk with provider who does have muliple
> sip-proxies with not shared nonce db.
>
> sip.freeconet.pl resolves to 3 diffrent IP and FS does not cache/remeber
> IP that send back request.
>
> So we have a case
> FS->P1: Invite
> P1 -> FS -> 407 + nonce
> FS does again DNS lookup and
> FS->P2 Invite with nonce from P1
> P2->FS 407
> FS fails call.
>
> Is there a way to force FS to send all messages within dialog to one IP
> only ?
>
> Regards
>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20180620/119f5e20/attachment.html>