Thank you for following up.Regarding my server networking configuration. This is an LXD server where Kamailio and rtpproxy are running on the host and several containers with Asterisk. The Asterisks are running behind of lxdbr0 NAT. This is an example of server configuration:

3: eno1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP group default qlen 1000
    link/ether 0c:c4:7a:92:5c:f4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.0.31/20 brd 192.168.15.255 scope global eno1
       valid_lft forever preferred_lft forever
  4: lxdbr0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP group default qlen 1000
    link/ether fe:5c:a5:12:c9:09 brd ff:ff:ff:ff:ff:ff
    inet 10.159.65.1/24 scope global lxdbr0
       valid_lft forever preferred_lft forever
    inet6 fd42:b153:24b2:77aa::1/64 scope global  
       valid_lft forever preferred_lft forever
    inet6 fe80::248c:4cff:fe69:8ca9/64 scope link  
       valid_lft forever preferred_lft forever
8: veth7JRSU0@if7: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue master lxdbr0 state UP group default qlen 1000
    link/ether fe:7e:6e:b6:39:3a brd ff:ff:ff:ff:ff:ff link-netnsid 1
    inet6 fe80::fc7e:6eff:feb6:393a/64 scope link  
       valid_lft forever preferred_lft forever

So, sometimes I have to define 'listen' parameters. For example, when it is necessary to configure the advertised address.
Anyway, in order to reproduce the problem I define something like this:

listen=udp:10.159.65.1:5060
listen=tcp:10.159.65.1:5060
listen=udp:192.168.0.31:5060
listen=tcp:192.168.0.31:5060

I'll check the latest branch during the next couple of days.
Thank you again.
Leonid

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