Thanks for the opinion. I originally was not running with "udpping_from_path" (it was disabled). Even with it disabled and only using SIP OPTIONS ping method the following log was generated:

Nov  1 18:58:01 localhost kam_registrar_1[2896]: ERROR: <core> [core/udp_server.c:591]: udp_send(): raw_iphdr_udp4_send(12,0x7f5be79587e6,4,...,212.2.172.228:39808,1500): Network is unreachable(101)
Nov  1 18:58:01 localhost kam_registrar_1[2896]: ERROR: nathelper [nathelper.c:2077]: nh_timer(): udp_send failed

Lets progress this issue assuming I am not using "udpping_from_path" and only using SIP OPTIONS ping method.

I guess what I am asking here is that, if kamailio has a socket defined on the local network, and its $du is on the same network, then, nathelper should be able to send the message. However, in this case, it cannot. It looks like it is trying to work out which interface to send the destination contact (external address: 212.2.172.228) to, but, because we are behind a proxy on a private lan, then kamailio needs to send via the PATH definition, in this case all OPTIONS messages will go out via an address on the local lan.

In my humble opinion, we should not need to define a default gateway so that kamailio can resolve which interface to use (in this case the wrong one (10.6.0.x because the default gateway is a 10.6.0.x address), only for nathelper/registrar to realize that it needs to use the PATH parameter for sending the messages, and only then relay the message.

I'm not sure if I am explaining myself correctly, please let me know if I am not being clear in my explanation and I'll try to explain better.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.