Description

When Kamailio listening IP address is assigned to a secondary network interface and this card does not use for the default route, then at the L3-network level selected wrong IP address and in the "Recrod-Route" and "Via" headers used correct Kamailio IP.

For example in the attached file, frame 5 and fragments in frames 3,4. invite-from-wrong-ip.pcap.gz

Reproduction

Our use case.

create a new virtual machine with a random IP address in the AWS cloud;
create a new network interface card with a static IP address;
attach a new network interface to a virtual machine, in Linux should be configured only one default route via the first network interface with a dynamic IP address;
start Kamailio daemon with configured listening TCP/socket with the IP address from the secondary IP card.
make a call via Kamailio.

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