Wrong IP address in SIP Contact field
Issue generated from Tuleap's migration script. Originally submitted by: Alexandre Lision (alision)
I have one laptop connected via Ethernet to a router, and to wifi (different network between Ethernet and wifi).
Ethernet address was 10.10.4.123
Wifi address: 192.168.49.27
I called it from another laptop on the same Wifi network using the Wifi address.
As seen in the wireshark session INVITE is received and answered by a 'Trying' followed by a 'Ringing'.
In the latter, the Contact header is wrong. It contains the ethernet address.
Contact URI sip:10.10.4.123:5060
This address is then used as the destination adress. The caller tries to send ACK to that address and got nothing (the caller is on the wifi network, and does not know about Ethernet network)
It's an uncommon issue, but it shows some flaws in our network interface handling