[Freeswitch-users] Clarification regarding register behavior

[Kai Danielmeier]

Hi,

thanks for your answer. The proxy does not carry any port number. Behavior
is exactly as you described it. SRV and DNS query is just done on gateway
startup and then never again until I kill the gateway and start it up
again. OPTIONS ping running every minute is doing DNS query all the time
and properly handles weight change.

Incoming calls get in fine still as gateway is still registering to the
originally acquired ip during startup. But outgoing invites and options
ping are denied, because they are send to different gateway. So all boils
down to REGISTER not requerying DNS. I will open an issue for this.

Kai

2018-01-23 18:25 GMT+01:00 Vallimamod Abdullah <vma at vallimamod.org>:

> 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 at sipsolutions.fr
> .
>
> > On 22 Jan 2018, at 10:06, Kai Danielmeier <kai.danielmeier at 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
>
>
> _________________________________________________________________________
> Professional FreeSWITCH Consulting Services:
> consulting at freeswitch.org
> http://www.freeswitchsolutions.com
>
> Official FreeSWITCH Sites
> http://www.freeswitch.org
> http://confluence.freeswitch.org
> http://www.cluecon.com
>
> FreeSWITCH-users mailing list
> FreeSWITCH-users at lists.freeswitch.org
> http://lists.freeswitch.org/mailman/listinfo/freeswitch-users
> UNSUBSCRIBE:http://lists.freeswitch.org/mailman/options/freeswitch-users
> http://www.freeswitch.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20180124/ad3ec96b/attachment.html>