3 Nov
2017
3 Nov
'17
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:
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:
_______________________________________________
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
-- Alex
--
Sent via mobile, please forgive typos and brevity.
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…
at
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>
>>> 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
>>
>>
>> _______________________________________________
>> 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.
_______________________________________________
Kamailio (SER) - Users Mailing List
sr-users(a)lists.kamailio.org
https://lists.kamailio.org/cgi-bin/mailman/listinfo/sr-users