My product uses a server with two network interfaces, one for SIP and one for
management. SIP requests arrive at the server on the SIP interface, where they
are processed by a firewall application, then passed to the SIP container on
the management interface. Similarly, outgoing SIP requests should leave the SIP
container on the management interface, and arrive at the firewall application
on the SIP interface, which then sends the request to the network on the SIP
interface.
Using the Linux ss utility, I can see that the SIP container is opening a
socket on the SIP interface to the firewall application, also on the SIP
interface. This confuses the firewall application, as it identifies the socket
from the container by looking for a far end address that matches the management
interface
Original issue reported on code.google.com by jean.deruelle on 1 May 2015 at 5:26
Original issue reported on code.google.com by
jean.deruelle
on 1 May 2015 at 5:26