Heres the full
!
class-map match-any VOICE
match protocol rtp
match protocol mgcp
!
!
policy-map QoS
class VOICE
bandwidth percent 25
class class-default
fair-queue
random-detect
!
!
!
Main Topics
Browse All TopicsGood Afternoon,
I was hoping someone could assist me with setting up QoS on my 14 Cisco Routers to support VoIP. I have a 14 site MPLS cloud that passes data and VoIP voice. The pipes to each location are 1.54M (Cisco 2600 Routers), except for the main data center and DR site (Cisco 3745 Routers), which have 12M each.
At times, users experience severe echoing and will have one-way voice degregation (I hear you fine, you can't hear me very well). The phone system I use is not Cisco based, it is made by Sphere Communications it utliizes MCGP. There are several ports they use for call set-up. call control, media streams, etc.
I am utilizing the G.711 protocol, but I believe that users are monoplizing the bandwidth with Internet and email and killing the voice packets. I need to set up QoS on these routers (and perhaps switches - Catalysts and Dell PowerConnect 3424's). I hope someone can lead me in the right direction, as my boss has firmly crawled up my a**.
Thanks!
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.

Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
donmanrobb,
Thank you for your response. I am still confused. I though we had to identify each and every TCP and UDP port that Sphere uses and add them to a group, then assigning the group to a class, then assigning the class to a policy map. Is this it? This seems too simple.
You also mentioned service-policy output and nbar discovery. How do I set these up? Assume I am an idiot, spell it all out for me. I do follow directions well. Thanks!
Cisco's Network Based Application Recognition (NBAR) is a great classification tool that can recognize various protocols by either predefined port numbers or by the application signature depending on the actual protocol. So it really can be that easy, it is used by the match protocol statements in my above example. You could also create an access-list that matches the exact port numbers if you so choose and can add it to the QoS policy by doing the following
class-map VOICE
match ip address <ACL # or name>
The service-policy output <name> is what activates the QoS policy on an interface the reason you would not use service-policy input is that once you receive a packet its too late for QoS to affect it your only option at that point would be to rate-limit the interface.
ip nbar protocol-discovery activates NBAR on the interface so the match protocol works correctly. On newer IOS releases you no longer need the command however adding it has the additional benefit of letting you see what protocols are in use on your network. You can check to see the top offenders on your network by using show ip nbar protocol-discovery stats byte-count top-n 10 where 10 is the top 10 protocols.
I'll be in and out all day so let me know if you need anything explained further.
Who is your MPLS provider and what method are they using to deliver the circuit to you?
Many providers carry mpls over Frame-Relay so you will need to enable FR traffic shaping and apply the policy to DLCI.
If we had a copy of the running config we may be able to better help you with your configuration.
You may want to see if your phone supports G.729 between sites as this will greatly help with your bandwidth usage.
ATX is our MPLS provider. They deliver the pipes as T-1's, no frame relay. Yes, you are correct the phones should use G.729 for WAN calls, and G.711 for internal LAN calls. The phones do use these, I mistyped in my initial question. I think this issue is more of other traffic monoplizing the bandwidth. Attached is the sh run from the router at my main site. It has a 12M pipe, other offices only have 1.54M each.
If you think turning on NBAR would help, I am all for it, but I don't know how. I am at your mercy. Thanks.
It looks like you had a priority-list setup for tcp 1521 and 1526 which is Oracle if I recall correctly as well as the Feasterville LAN on Gig0/1. But it was not added to any interface, did you take it off for troubleshooting? What interface was it on?
priority-list 1 protocol ip high tcp 1521
priority-list 1 protocol ip high tcp 1526
priority-list 1 interface GigabitEthernet0/1 high
priority-queuing is a strict QoS that can starve all other traffic so it should only be used when absolutely necessary.
Is the phone system off 192.168.1.14?
I'll add my QoS idea to your config and repost it for you to have a look at.
hostname FPB_Feast_MPLS
!
boot-start-marker
boot system flash flash:c3825-advipservicesk
boot-end-marker
!
!
no aaa new-model
!
resource policy
!
ip cef
!
!
voice-card 0
no dspfarm
!
!
class-map match-any VOICE
match protocol rtp
match protocol mgcp
!
!
policy-map QoS
class VOICE
bandwidth percent 25
class class-default
fair-queue
random-detect
interface Loopback160
ip address 192.168.160.1 255.255.255.0
!
interface gig0/0
description Connection to Server Replication LAN
ip address 10.10.23.1 255.255.255.0 secondary
ip address 192.168.105.6 255.255.255.248
duplex auto
speed auto
media-type rj45
negotiation auto
ip nbar protocol-discovery
!
interface gig0/1
description Connection to Feasterville LAN
ip address 192.168.80.1 255.255.255.248 secondary
ip address 192.168.1.1 255.255.255.0
duplex auto
speed auto
media-type rj45
negotiation auto
ip nbar protocol-discovery
!
interface hssi1/0
description ATX MPLS VPN 12MB
ip address 10.255.1.2 255.255.255.252
ip route-cache flow
load-interval 30
serial restart-delay 0
no cdp enable
service-policy output QoS
ip nbar protocol-discovery
!
!
!
end
FPB_Feast_MPLS#
WOW, this is exactly what I am looking for! I will put this into my router configs and let you know how it goes. Yes, the previous technician did play around with priority-queueing for our Oracle DB that runs our primary financial software. It is important, almost as important as Voice. No, 192.168.1.14 is the Oracle primary DB. How do you know that rtp and mgcp are the correct protocols? My vendor (Sphere Communications) have a laundry list of TCP and UDP ports that they use for call control and setup. Do I need to identify each one? Or will rtp take care of it?
Most if not all VOIP offerings use RTP as its communication protocol it uses UDP the even ports 16384-32767 so I figured it would be a good guess as you'll probably be more concerned with the voice traffic then the management info. As for MGCP you stated above that the Sphere uses that protocol. The match protocol rtp should take of the matching for you.
Business Accounts
Answer for Membership
by: donmanrobbPosted on 2008-04-20 at 17:12:34ID: 21398047
You can use something like the following on your routers
!
class-map match-any VOICE
match protocol rtp
match protocol mgcp
!
!
You can add your QoS your router interfaces by using
service-policy output QoS
and also add ip nbar protocol-discovery to make NBAR work.
Let me know if you need to setup QoS on your switches as well.