Sounds like a platform issue to me. Why is this hurting you?
Best regards, Byron Campen Hi all,
I have noticed the following TCP/TLS behavior. I have a physical interface (eth0, ip address 192.168.17.144 ). I create a virtual ip address (eth0:1, ip address 192.168.17.155). I start the resiprocate app and add a TCP transport for the virtual 192.168.17.155 interface. I send an INVITE to a remote destination. The problem is that the INVITE message received on the remote has the IP frame src address 192.168.17.144 (and not 192.168.17.155). Note that all the resiprocate log messages as well as the Via header indicate the correct ip address 192.168.17.155. Any thoughts?
I may provide logs and/or wireshark capture if needed.
Best regards,
Dan Tifrea
_______________________________________________ resiprocate-users mailing list
|