Thanks very much Charles. I'll use this as a template. -Nick
> From: "Church, Charles" <[EMAIL PROTECTED]> > Date: Mon, 21 Jul 2008 16:15:06 -0500 > To: Nick Voth <[EMAIL PROTECTED]>, <[email protected]> > Conversation: [c-nsp] QoS for VoIP to specific proxy > Subject: RE: [c-nsp] QoS for VoIP to specific proxy > > Nick, > > You can use a class-map to match that traffic using an > access-list. If you really want to be specific, you can do a match-all, > and match it to 'protocol' as well. Then define a policy-map that > prioritizes that class to a certain speed. Then attach the output > policy to the interface. I think you can only apply a priority policy > to a physical interface, versus a subint or a virtual one. You can't > enforce prioritization towards you. It's up to the other providers. If > they're respecting IP PREC or DSCP, you're probably all set. Otherwise, > you can control it a bit with input policies to limit non-VoIP traffic > (using shaping), but it's far from an exact science. > > Chuck > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Nick Voth > Sent: Monday, July 21, 2008 4:09 PM > To: [email protected] > Subject: [c-nsp] QoS for VoIP to specific proxy > > > Hello folks, > > Please pardon me asking what I'm sure has been answered before. I've > looked > through the archives and the Cisco site, but I'm still confused about > what I > need to do. > > I have a client who's Cisco 1841 CPE router needs to simply prioritize > SIP > traffic to and from a specific VoIP proxy. > > Let's say the VoIP proxy is 209.120.xxx.xxx > > The customer's current config on their 1841 is below. Can someone give > me an > idea of how I can accomplish this? Remember, I just basically need > priority > queuing of any traffic to and from that VoIP proxy listed above > > Thanks very much for any help! > > -Nick Voth > > ---------Customer's CPE config------------>>>> > interface FastEthernet0/0 > ip address 67.101.xxx.xxx 255.255.255.248 > duplex auto > speed auto > no keepalive > ! > ! > interface Serial0/0/0 > no ip address > encapsulation frame-relay IETF > no ip mroute-cache > service-module t1 timeslots 1-24 > service-module t1 fdl both > frame-relay lmi-type ansi > ! > interface Serial0/0/0.1 point-to-point > frame-relay interface-dlci 16 ppp Virtual-Template1 > ! > interface Virtual-Template1 > ip address negotiated > ppp chap hostname xxxxx > ppp chap password 7 01465656080E535773 > ppp ipcp dns request > ppp ipcp route default > ppp ipcp address accept > ---------- > > > _______________________________________________ > cisco-nsp mailing list [email protected] > https://puck.nether.net/mailman/listinfo/cisco-nsp > archive at http://puck.nether.net/pipermail/cisco-nsp/ _______________________________________________ cisco-nsp mailing list [email protected] https://puck.nether.net/mailman/listinfo/cisco-nsp archive at http://puck.nether.net/pipermail/cisco-nsp/
