# Example: Excluding NetLinks from handling a QoS Class of traffic

Using Multi-Link technology and QoS classes, you can exclude VoIP traffic from a satellite connection.

Company B has three Internet connections: ISP A, ISP B, and ISP C, which is a satellite link. Because of the long latency in satellite connections, the administrators do not want any VoIP traffic to be routed through ISP C. They decide to use QoS classes so that VoIP traffic is only routed through ISP A and ISP B.

To do this, the administrators:

1. Create NetLink elements to represent connections to ISP A, ISP B, and ISP C.
2. Place the ISP A, ISP B, and ISP C NetLinks under the correct interfaces in the Routing view.
3. Define a QoS class and assign it to VoIP traffic.
4. Create an Outbound Multi-Link element and add the ISP A, ISP B, and ISP C NetLinks to it.
5. Select the QoS class for the ISP A NetLink and the ISP B NetLink in the Outbound Multi-Link element properties. No QoS class is assigned to ISP C.
6. Define the following NAT rule for outbound load balancing in the Engine Policy:

   Source | Destination | Service | NAT
   --- | --- | --- | ---
   ANY | ANY | ANY | Dynamic load balancing: Multi-Link Element