[c-nsp] QoS on ingress

[Heath Jones]

Hi Jay

Essentially you would try to slow down the traffic heading out of your
network that forms part of 2 way communication that waits for
acknowledgements / higher level protocol return traffic.
As an example, by slowing down TCP ACK's heading out, you will affect the
traffic heading back in the link..

Apart from that, there isnt anything you can do to solve it.


Cheers
Heath





On 10 September 2010 19:44, Jay Nakamura <zeusdadog at gmail.com> wrote:

> I can't seem to figure out what to do with my situation, wondering if
> anyone had encountered this.
>
> Situation :
> Router : 1841 IOS 12.4T or 15.0M
> Internet T1, two eth Interfaces
> There are VoIP traffic (SIP & RTP) and general internet traffic
>
> VoIP provider does not tag SIP/RTP with any kind of QoS in IP header.
> (DSCP/IPP)  Internet provider can do QoS based on IPP but since VoIP
> traffic is not marked, it's not useful.
>
> Problem to solve : how to not drop >ingress< VoIP traffic when
> internet traffic is high as much as possible without capping the
> non-VoIP traffic to less than T1 bandwidth.
>
> Caveat : I understand that since it's not getting policed at the
> egress from the provider, any solution is not going to be perfect
>
> I can't limit the traffic on the Eth interface egress because traffic
> can go to either eth interface.
>
> Any thoughts?
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>