Multiple IPs

List overview All Threads
Download

newer

older

Contacts in 302

onreply_route block not processing...

Oz Mortimer

3 Nov 2017 3 Nov '17

4:56 p.m.

Hi all, I have Kamailio set as an SBC with freeswitch behind - that all works fine. Freeswitch can send calls out VIA Kamailio to external IP address’, but if I try sending a call to another IP hosted by Kamailio the seems to go nowhere… Supplier -> Kamailio -> Customer1 -> Kamailio -> Customer2 The Kamailio server has multiple assigned IPs, which are used to multi-tennant - but I cant for the like of me to get Tennant to tenant calls to work (via freeswitch) Any pointers?

Show replies by date

Alex Balashov

3 Nov 3 Nov

4:59 p.m.

Hi, 1. Do you have a listener (listen=) for all necessary IPs and transports? 2. Outbound interface selection is done either via the 'mhomed' option, https://www.kamailio.org/wiki/cookbooks/5.0.x/core#mhomed or, if it's not doing what you want, by manually steering it via $fs: https://www.kamailio.org/wiki/cookbooks/5.0.x/pseudovariables#fs_-_forced_s… -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/

Oz Mortimer

5:04 p.m.

I have listen commented out - which means it listens on all IPs (doesn’t it?) - do I need to set them explicitly? I did add mhomed=1 on this setup - but the calls went a bit crazy (I didn’t manage to capture quite what was happening). Thoughts?

...

On 3 Nov 2017, at 13:59, Alex Balashov <abalashov(a)evaristesys.com> wrote: Hi, 1. Do you have a listener (listen=) for all necessary IPs and transports? 2. Outbound interface selection is done either via the 'mhomed' option, https://www.kamailio.org/wiki/cookbooks/5.0.x/core#mhomed or, if it's not doing what you want, by manually steering it via $fs: https://www.kamailio.org/wiki/cookbooks/5.0.x/pseudovariables#fs_-_forced_s… -- Alex -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Alex Balashov

5:06 p.m.

On Fri, Nov 03, 2017 at 02:04:37PM +0000, Oz Mortimer wrote:

...

I have listen commented out - which means it listens on all IPs (doesn’t it?) - do I need to set them explicitly?

Try setting them explicitly, so that you can route them explicitly.

...

I did add mhomed=1 on this setup - but the calls went a bit crazy (I didn’t manage to capture quite what was happening).

Oz Mortimer

5:20 p.m.

Ok - did that and got the same error, though this time I looked at what it was; Im /var/log/messages I see - Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> [socket_info.c:1392]: fix_hostname(): could not rev. resolve xxx.xxx.xxx.xxx Although the IP address’ are correct...

...

On 3 Nov 2017, at 14:06, Alex Balashov <abalashov(a)evaristesys.com> wrote: On Fri, Nov 03, 2017 at 02:04:37PM +0000, Oz Mortimer wrote:

I have listen commented out - which means it listens on all IPs (doesn’t it?) - do I need to set them explicitly?

Try setting them explicitly, so that you can route them explicitly.

I did add mhomed=1 on this setup - but the calls went a bit crazy (I didn’t manage to capture quite what was happening).

Unfortunately, without knowing the specific facts, it's hard to speculate. -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Alex Balashov

5:21 p.m.

Are you sure the IP is correct? On November 3, 2017 10:20:17 AM EDT, Oz Mortimer <omortimer(a)gmail.com> wrote:

...

On 3 Nov 2017, at 14:06, Alex Balashov <abalashov(a)evaristesys.com>

wrote:

On Fri, Nov 03, 2017 at 02:04:37PM +0000, Oz Mortimer wrote:

I have listen commented out - which means it listens on all IPs (doesn’t it?) - do I need to set them explicitly?

Try setting them explicitly, so that you can route them explicitly.

I did add mhomed=1 on this setup - but the calls went a bit crazy (I didn’t manage to capture quite what was happening).

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Alex -- Sent via mobile, please forgive typos and brevity.

Oz Mortimer

5:37 p.m.

Yeah 100% So, I figured it might be something with DNS so I set auto_aliases=no but then get the following. Nov 3 14:32:19 IS-56434 kamailio: INFO: <core> [tcp_main.c:4745]: init_tcp(): using epoll_lt as the io watch method (auto detected) Nov 3 14:32:19 IS-56434 /usr/sbin/kamailio[13015]: WARNING: tm [tm.c:845]: mod_init(): WARNING: mod_init: reparse_on_dns_failover is enabled on a multihomed host -- check the readme of tm module! Nov 3 14:32:19 IS-56434 /usr/sbin/kamailio[13015]: INFO: rr [../outbound/api.h:54]: ob_load_api(): Failed to import bind_ob Nov 3 14:32:19 IS-56434 /usr/sbin/kamailio[13015]: INFO: rr [rr_mod.c:160]: mod_init(): outbound module not available Its worth noting all of the IPs are on the same adapter, i.e. eth0, eth0:0, eth0:1 and so on..

...

On 3 Nov 2017, at 14:21, Alex Balashov <abalashov(a)evaristesys.com> wrote: Are you sure the IP is correct? On November 3, 2017 10:20:17 AM EDT, Oz Mortimer <omortimer(a)gmail.com> wrote:

On 3 Nov 2017, at 14:06, Alex Balashov <abalashov(a)evaristesys.com>

wrote:

On Fri, Nov 03, 2017 at 02:04:37PM +0000, Oz Mortimer wrote:

I have listen commented out - which means it listens on all IPs (doesn’t it?) - do I need to set them explicitly?

Try setting them explicitly, so that you can route them explicitly.

I did add mhomed=1 on this setup - but the calls went a bit crazy (I didn’t manage to capture quite what was happening).

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Alex -- Sent via mobile, please forgive typos and brevity. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Oz Mortimer

5:38 p.m.

nb. I only get

...

> fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx

When mhomed=1

...

On 3 Nov 2017, at 14:21, Alex Balashov <abalashov(a)evaristesys.com> wrote: Are you sure the IP is correct? On November 3, 2017 10:20:17 AM EDT, Oz Mortimer <omortimer(a)gmail.com> wrote:

On 3 Nov 2017, at 14:06, Alex Balashov <abalashov(a)evaristesys.com>

wrote:

On Fri, Nov 03, 2017 at 02:04:37PM +0000, Oz Mortimer wrote:

I have listen commented out - which means it listens on all IPs (doesn’t it?) - do I need to set them explicitly?

Try setting them explicitly, so that you can route them explicitly.

I did add mhomed=1 on this setup - but the calls went a bit crazy (I didn’t manage to capture quite what was happening).

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Alex Balashov

5:43 p.m.

I would not be concerned about superficial errors. I am more concerned that the system is attempting to "resolve" an IP address. This would only happen if its format is not deemed to be that if an IP address. On November 3, 2017 10:38:41 AM EDT, Oz Mortimer <omortimer(a)gmail.com> wrote:

...

nb. I only get

> fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx

When mhomed=1

On 3 Nov 2017, at 14:21, Alex Balashov <abalashov(a)evaristesys.com>

wrote:

Are you sure the IP is correct? On November 3, 2017 10:20:17 AM EDT, Oz Mortimer

<omortimer(a)gmail.com> wrote:

> Ok - did that and got the same error, though this time I looked at

what

> it was; > Im /var/log/messages I see - > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> > [socket_info.c:1392]: fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx > > Although the IP address’ are correct... > > >> On 3 Nov 2017, at 14:06, Alex Balashov <abalashov(a)evaristesys.com> > wrote: >> >> On Fri, Nov 03, 2017 at 02:04:37PM +0000, Oz Mortimer wrote: >> >>> I have listen commented out - which means it listens on all IPs >>> (doesn’t it?) - do I need to set them explicitly? >> >> Try setting them explicitly, so that you can route them explicitly. >> >>> I did add mhomed=1 on this setup - but the calls went a bit crazy

> didn’t manage to capture quite what was happening). Unfortunately, without knowing the specific facts, it's hard to speculate. -- Alex Balashov | Principal | Evariste Systems LLC Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Alex -- Sent via mobile, please forgive typos and brevity.

Oz Mortimer

5:51 p.m.

Ok, So sort of progress.. With mhomed=0 the calls arrive at the media server from the IP the call was sent to, With mhomed=1 the calls arrive at the media server from the first registered IP address regardless of which IP the call was sent to. So mhomed is doing the reverse of what I would expect…

...

On 3 Nov 2017, at 14:43, Alex Balashov <abalashov(a)evaristesys.com> wrote: I would not be concerned about superficial errors. I am more concerned that the system is attempting to "resolve" an IP address. This would only happen if its format is not deemed to be that if an IP address. On November 3, 2017 10:38:41 AM EDT, Oz Mortimer <omortimer(a)gmail.com> wrote:

nb. I only get

> fix_hostname(): could not rev. resolve > xxx.xxx.xxx.xxx

When mhomed=1

On 3 Nov 2017, at 14:21, Alex Balashov <abalashov(a)evaristesys.com>

wrote:

Are you sure the IP is correct? On November 3, 2017 10:20:17 AM EDT, Oz Mortimer

<omortimer(a)gmail.com> wrote:

> Ok - did that and got the same error, though this time I looked at

what

>> didn’t manage to capture quite what was happening). > > Unfortunately, without knowing the specific facts, it's hard to > speculate. > > -- > Alex Balashov | Principal | Evariste Systems LLC > > Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) > Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users(a)lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Alex Balashov

6:06 p.m.

That's probably because the mhomed test, as described in the docs, determines that this should be the outbound interface. On November 3, 2017 10:51:06 AM EDT, Oz Mortimer <omortimer(a)gmail.com> wrote:

...

On 3 Nov 2017, at 14:43, Alex Balashov <abalashov(a)evaristesys.com>

wrote:

I would not be concerned about superficial errors. I am more concerned that the system is attempting to "resolve" an IP

address. This would only happen if its format is not deemed to be that if an IP address.

On November 3, 2017 10:38:41 AM EDT, Oz Mortimer

<omortimer(a)gmail.com> wrote:

> nb. I only get >>> fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx > > When mhomed=1 > > > >> On 3 Nov 2017, at 14:21, Alex Balashov <abalashov(a)evaristesys.com> > wrote: >> >> Are you sure the IP is correct? >> >> On November 3, 2017 10:20:17 AM EDT, Oz Mortimer > <omortimer(a)gmail.com> wrote: >>> Ok - did that and got the same error, though this time I looked at > what >>> it was; >>> Im /var/log/messages I see - >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> >>> Although the IP address’ are correct... >>> >>> >>>> On 3 Nov 2017, at 14:06, Alex Balashov

<abalashov(a)evaristesys.com>

>>> wrote: >>>> >>>> On Fri, Nov 03, 2017 at 02:04:37PM +0000, Oz Mortimer wrote: >>>> >>>>> I have listen commented out - which means it listens on all IPs >>>>> (doesn’t it?) - do I need to set them explicitly? >>>> >>>> Try setting them explicitly, so that you can route them

explicitly.

>>>> >>>>> I did add mhomed=1 on this setup - but the calls went a bit

crazy

>>> didn’t manage to capture quite what was happening). >> >> Unfortunately, without knowing the specific facts, it's hard to >> speculate. >> >> -- >> Alex Balashov | Principal | Evariste Systems LLC >> >> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) >> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users(a)lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users(a)lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users -- Alex -- Sent via mobile, please forgive typos and brevity. _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Alex -- Sent via mobile, please forgive typos and brevity.

Alex Balashov

6:28 p.m.

Also, to correct a previous statement: it does seem that Kamailio attempts to resolve the reverse DNS entries of its listeners on boot. That can be disabled via DNS core configuration parameters. It can also be ignored as it's of no concern to this scenario. On November 3, 2017 11:06:57 AM EDT, Alex Balashov <abalashov(a)evaristesys.com> wrote:

...

Ok, So sort of progress.. With mhomed=0 the calls arrive at the media server from the IP the

call

was sent to, With mhomed=1 the calls arrive at the media server from the first registered IP address regardless of which IP the call was sent to. So mhomed is doing the reverse of what I would expect…

On 3 Nov 2017, at 14:43, Alex Balashov <abalashov(a)evaristesys.com>

wrote:

I would not be concerned about superficial errors. I am more concerned that the system is attempting to "resolve" an IP

address. This would only happen if its format is not deemed to be that if an IP address.

On November 3, 2017 10:38:41 AM EDT, Oz Mortimer

<omortimer(a)gmail.com> wrote: >> nb. I only get >>>> fix_hostname(): could not rev. resolve >>>> xxx.xxx.xxx.xxx >> >> When mhomed=1 >> >> >> >>> On 3 Nov 2017, at 14:21, Alex Balashov <abalashov(a)evaristesys.com> >> wrote: >>> >>> Are you sure the IP is correct? >>> >>> On November 3, 2017 10:20:17 AM EDT, Oz Mortimer >> <omortimer(a)gmail.com> wrote: >>>> Ok - did that and got the same error, though this time I looked

> what >>> it was; >>> Im /var/log/messages I see - >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> Nov 3 14:13:28 IS-56434 kamailio: WARNING: <core> >>> [socket_info.c:1392]: fix_hostname(): could not rev. resolve >>> xxx.xxx.xxx.xxx >>> >>> Although the IP address’ are correct... >>> >>> >>>> On 3 Nov 2017, at 14:06, Alex Balashov

<abalashov(a)evaristesys.com>

explicitly.

>>>> >>>>> I did add mhomed=1 on this setup - but the calls went a bit

crazy

(I >>>> didn’t manage to capture quite what was happening). >>> >>> Unfortunately, without knowing the specific facts, it's hard to >>> speculate. >>> >>> -- >>> Alex Balashov | Principal | Evariste Systems LLC >>> >>> Tel: +1-706-510-6800 / +1-800-250-5920 (toll-free) >>> Web: http://www.evaristesys.com/, http://www.csrpswitch.com/ >>> >>> _______________________________________________ >>> Kamailio (SER) - Users Mailing List >>> sr-users(a)lists.kamailio.org >>> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users >> >> >> _______________________________________________ >> Kamailio (SER) - Users Mailing List >> sr-users(a)lists.kamailio.org >> https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users > > > -- Alex > > -- > Sent via mobile, please forgive typos and brevity. > > _______________________________________________ > Kamailio (SER) - Users Mailing List > sr-users(a)lists.kamailio.org > https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users _______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

-- Alex -- Sent via mobile, please forgive typos and brevity.

Oz Mortimer

6:42 p.m.

Why would it choose a different IP from the one it received on? How do I make it use the correct ip?

...

On 3 Nov 2017, at 15:06, Alex Balashov <abalashov(a)evaristesys.com> wrote: That's probably because the mhomed test, as described in the docs, determines that this should be the outbound interface. On November 3, 2017 10:51:06 AM EDT, Oz Mortimer <omortimer(a)gmail.com> wrote:

On 3 Nov 2017, at 14:43, Alex Balashov <abalashov(a)evaristesys.com>

wrote:

I would not be concerned about superficial errors. I am more concerned that the system is attempting to "resolve" an IP

address. This would only happen if its format is not deemed to be that if an IP address.

On November 3, 2017 10:38:41 AM EDT, Oz Mortimer

<omortimer(a)gmail.com> wrote:

<abalashov(a)evaristesys.com>

explicitly.

>>>> >>>>> I did add mhomed=1 on this setup - but the calls went a bit

crazy

_______________________________________________ Kamailio (SER) - Users Mailing List sr-users(a)lists.kamailio.org https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users

Alex Balashov

6:45 p.m.

Because it determines the proper route based on the method described in the 'mhomed' section of the docs. Your choices are either to let Kamailio do that, or set mhomed=0 and choose the egress interface manually based on your own criteria. You can do this by setting $fs prior to t_relay(), e.g. $fs = 'udp:x.x.x.x:5060'; Bear in mind that this combination of transport, listener and port must correspond exactly to one of the listeners. It sounds like that's what you need to do. -- Alex -- Sent via mobile, please forgive typos and brevity.

2579

days inactive

2579

days old

sr-users@lists.kamailio.org

Manage subscription

13 comments

2 participants

tags (0)

participants (2)

Alex Balashov
Oz Mortimer