You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have freeswitch with an authenticated gateway to a provider, routing calls through an outbound proxy.
There are multiple outbound proxies all under the same FQDN.
Occasionally, I guess when the FQDN ttl expires, the second INVITE with the authentication goes to a different proxy, causing the provider to see an initial attempt from a public ip and the authenticated attempt from a different public ip.
This might make it all more clear:
F.F.F.F is freeswitch
b.b.b.b is proxy 1
c.c.c.c is proxy 2
x.x.x.x is the provider
I have freeswitch with an authenticated gateway to a provider, routing calls through an outbound proxy.
There are multiple outbound proxies all under the same FQDN.
Occasionally, I guess when the FQDN ttl expires, the second INVITE with the authentication goes to a different proxy, causing the provider to see an initial attempt from a public ip and the authenticated attempt from a different public ip.
This might make it all more clear:
F.F.F.F is freeswitch
b.b.b.b is proxy 1
c.c.c.c is proxy 2
x.x.x.x is the provider
Expected behavior
There shouldn't be a dns resolution mid call, the second INVITE should go through the same proxy as the initial INVITE
Package version or git hash
Any thoughts on this?
Thanks
The text was updated successfully, but these errors were encountered: