[Spce-user] 477 - Unfortunately error on sending to next hop occurred (477/TM)

[Yazar Lwin]

Hi All,
I also checked kamailio.cfg for lb and proxy. Both upd and tcp are
listened. I still can't find why it's happening for outbound in that
particular trunk only. Normally I always find outbound is the most
straight-forward to configure. Please advise if there is any where I need
to look up. This trunk was previously working fine.

On Fri, Mar 20, 2020 at 9:50 AM Yazar Lwin <yarzarlwin at gmail.com> wrote:

> Hi Alex,
>
> Below is route output.
> root at voice-gw01:~# route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use
> Iface
> 0.0.0.0         192.168.102.1   0.0.0.0         UG    0      0        0
> eno1
> 10.1.1.126      10.32.145.1     255.255.255.255 UGH   0      0        0
> eno2.235
> 10.1.6.106      10.32.145.1     255.255.255.255 UGH   0      0        0
> eno2.235
> 10.27.198.64    0.0.0.0         255.255.255.248 U     0      0        0
> eno2.234
> 10.32.145.0     0.0.0.0         255.255.255.248 U     0      0        0
> eno2.235
>
> I still can ping to that IP. And inbound is also working normally from
> that trunk. It's strange. The config is in network.yml and it also
> populated on interfaces on system.
>
>
> root at voice-gw01:~# ping 10.1.1.126
> PING 10.1.1.126 (10.1.1.126) 56(84) bytes of data.
> 64 bytes from 10.1.1.126: icmp_seq=1 ttl=249 time=0.829 ms
> 64 bytes from 10.1.1.126: icmp_seq=2 ttl=249 time=0.781 ms
> 64 bytes from 10.1.1.126: icmp_seq=3 ttl=249 time=0.781 ms
> 64 bytes from 10.1.1.126: icmp_seq=4 ttl=249 time=0.744 ms
>
>
> Below is interface that peer to that IP (10.1.1.126).
>  eno2.235:
>       ip: 10.32.145.2
>       netmask: 255.255.255.248
>       post_up:
>       - route add -host 10.1.1.126 gw 10.32.145.1
>       type:
>       - sip_ext
>
>     eno2.235:0:
>       ip: 10.32.145.5
>       netmask: 255.255.255.248
>       post_up:
>       - route add -host 10.1.6.106 gw 10.32.145.1
>       type:
>       - rtp_Telenor
>
> //interfaces
> eno2.235: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>         inet 10.32.145.2  netmask 255.255.255.248  broadcast 10.32.145.7
>         inet6 fe80::ec4:7aff:fe48:19d5  prefixlen 64  scopeid 0x20<link>
>         ether 0c:c4:7a:48:19:d5  txqueuelen 1000  (Ethernet)
>         RX packets 145541  bytes 26250081 (25.0 MiB)
>         RX errors 0  dropped 0  overruns 0  frame 0
>         TX packets 111792  bytes 25127292 (23.9 MiB)
>         TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
>
> eno2.235:0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
>         inet 10.32.145.5  netmask 255.255.255.248  broadcast 10.32.145.7
>         ether 0c:c4:7a:48:19:d5  txqueuelen 1000  (Ethernet)
>
> On Thu, Mar 19, 2020 at 3:12 PM Alex Lutay <alutay at sipwise.com> wrote:
>
>> Hi,
>>
>> Check your networking.
>> Did network interface or IP 10.1.1.126 gone?
>>
>> On 3/19/20 4:36 AM, Yazar Lwin wrote:
>> ...
>> > (10.1.1.126:5060 <10.1.1.126:5060>), tolen: 16) - err: Network is
>> unreachable (101)
>> ...
>>
>> --
>> Alex Lutay
>>
>> --
>> Spce-user mailing list
>> Spce-user at lists.sipwise.com
>> http://lists.sipwise.com/mailman/listinfo/spce-user_lists.sipwise.com
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.sipwise.com/pipermail/spce-user_lists.sipwise.com/attachments/20200323/c23c3799/attachment-0002.html>