Manual Chapter :
Messages received on per-client created
connections
Applies To:
Show Versions
BIG-IP LTM
- 15.1.10, 15.1.9, 15.1.8, 15.1.7, 15.1.6, 15.1.5, 15.1.4, 15.1.3, 15.1.2, 15.1.1, 15.1.0, 15.0.1, 15.0.0, 14.1.5, 14.1.4, 14.1.3, 14.1.2, 14.1.0, 14.0.1, 14.0.0, 13.1.5, 13.1.4, 13.1.3, 13.1.1, 13.1.0
Messages received on per-client created
connections
All messages received on an outgoing connection created using the per-client connection mode,
will automatically be forwarded to the connection that received the request which caused the
outgoing connection to be created. This includes request messages received on this connection.
This is because the connection acts as a direct connection for communication between the original
client and the other device. This routing is done be setting the nexthop of all messages received
to the last hop of the original request message.
For example:
A SIP INVITE request is received on a connection from 10.10.10.21 to 10.10.20.50. This message
gets routed to proxy server 10.20.30.85 using a transport-config that does not configure SNAT and
has a connection-mode of per-client. An outgoing connection will be created from 10.10.10.21 to
10.20.30.85. All messages (whether responses of requests) received on the outgoing connection
will be automatically routed to the SIP endpoint at 10.10.10.21 using the original incoming
connection.
To route a message received on a per-client created connection to another device, the nexthop
field will have to be cleared using the MR::message nexthop none command as follows:
when MR_INGRESS { MR::message nexthop none MR::message route config /Common/other_tc host 10.20.30.40:1234 }
