[c-nsp] QoS on ingress

Jay Nakamura zeusdadog at gmail.com
Fri Sep 10 15:17:19 EDT 2010

Well, I don't think another T1 will solve the problem.  Someone
watching Hulu or something will just suck the bandwidth down.  I think
what I am hearing is, I just need to suck it up and rate limit
non-VoIP traffic to 1.2mbps or something on ingress and hope that's
enough head room for VoIP to get through while TCP traffic slows down
from the rate-limit.  Of course, if all other traffic is UDP, it may
not do any good.

On Fri, Sep 10, 2010 at 3:14 PM, Heath Jones <hj1980 at gmail.com> wrote:
> Jay I know it might sound ridiculously obvious, but is another T1 out of the
> question?
> 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/

More information about the cisco-nsp mailing list