[Freeswitch-users] Clarification regarding register behavior

[Kai Danielmeier]

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
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freeswitch.org/pipermail/freeswitch-users/attachments/20180122/1e60533e/attachment.html>