Hi, Does your gateway proxy param has a port number? If so, no SRV request is made. Also, it is possible that the DNS request is only done at gateway start and not for subsequent refresh. To check this, can you try to kill the gateway and then restart it? If so, you'll need to open a jira ticket with the full sofia debug logs (sofia loglevel all 9). Out of curiosity, how do you manage to get your incoming calls between the SRV record change and the subsequent outgoing registration to the new server (independently from your issue)? Best Regards, -- Vallimamod Abdullah SIP Solutions vma@sipsolutions.fr .
On 22 Jan 2018, at 10:06, Kai Danielmeier <kai.danielmeier@gmail.com> wrote:
Hi all,
I currently facing a problem with frquent changes in SRV record weight and a freeswitch behavior, which causes some trouble in this regard.
Provider is Deutsche Telekom and for registration the SRV record reg.sip-trunk.telekom.de is used. Due to load balancing this records change frequently during the day. When a change occurs freeswitch send the INVITE requests to the "new" ip gathered from DNS and gets a 403 denied message back from server host. Analyzing the SIP traces I found that freeswitch is only doin DNS requery for INVITE, OPTIONS ping etc., but not for REGISTER messages. REGISTER is always going to the host gathered from the SRV record during gateway start even after expiry. (My first try was to set expiry to minimum allowed by server host, which is 240 seconds and hoping for FS to requery DNS and then register with new server host, but this did not work due to mentioned reasons)
Is this the correct behavior or is this a bug? Is there an option switch somewhere to influence this?
Thanks for a feedback.
Kind regards
Kai Danielmeier