Those should match what the profile is binding to.
On Nov 30, 2018, at 5:22 AM, Markus Bönke <mbodbg@gmx.net> wrote:
setting the switchname writes the value into sip_registrations.hostname, but in sip_registrations.server_host and sip_registration.orig_server_host is still the ip from eth1 .204. I’ve swapped the IPs, so .210 is now the main IP on eth1. Now I see .210 in all fields.
Thanks and regards
Markus
Am 29.11.2018 um 21:13 schrieb Michael Jerris <mike@jerris.com <mailto:mike@jerris.com>>:
https://freeswitch.org/stash/projects/FS/repos/freeswitch/browse/conf/vanill... <https://freeswitch.org/stash/projects/FS/repos/freeswitch/browse/conf/vanilla/autoload_configs/switch.conf.xml#39>
On Nov 29, 2018, at 8:39 AM, Markus Bönke <mbodbg@gmx.net <mailto:mbodbg@gmx.net>> wrote:
Hello all,
we have a server with 2 external IPs (eth1 .204 and eth1.1 .210 at the end). The sip profile is listening on .210 and clients are sending REGISTER requests to .210. But in table sip_registrations field hostname and orig_server_host there is the IP .204.
Is there a setting to force freeswitch to store the IP where the REGISTER was sent to? Or is there an issue when the IP is configured as second IP on the same interface?
Thanks and regards
Markus