Bug#500512: strange workaround

[John Doe]

Hello,

I also have the problem that in the SIP INVITE message according to wireshark the "Message Body" -> "Connection Information" does show the eth0 IP address instead of the VPN tun0 IP address.

My strange workaround is: Unplug the ethernet cable for eth0 before starting the call. This results in eth0 to be not "RUNNING" anymore according to ifconfig and the "Connection Information" to contain the correct VPN tun0 IP address! Linphone than retries to sent the SIP INVITE messages. So if I now plug in the ethernet cable again, linphone continues to retry to send the SIP INVITE message with the correct "Connection Information" and finally the call is established successfully.

I'm using linphone 3.3.2.