LingaringBell
IS-IT--Management
I've been reading about your basic QoS setup for VOIP on cisco IOS and I have a question. In the examples I tend to find they say to use a method similar to this:
For SIP/IAX/IAX2:
!signaling traffic
access-list 101 permit udp any any eq 4569
access-list 101 permit udp any any eq 5036
access-list 101 permit udp any any eq 5060
!
!RTP traffic
access-list 102 permit udp any any range 16384 32767
!
class-map match-all voice-traffic
match access-group 102
!
class-map match-all voice-signaling
match access-group 101
!
policy-map qos-voice
class voice-traffic
priority 240
class voice-signaling
bandwidth 16
class class-defult
fair-queue
!
interface FastEthernet0/0
service-policy output qos-voice
!
interface Serial0/0
rate-limit input 1408000 8000 8000 conform-action transmit exceed-action drop
My question is, why don't we use service-policy on the input interface as well as the output? Thanks.
-Bell
For SIP/IAX/IAX2:
!signaling traffic
access-list 101 permit udp any any eq 4569
access-list 101 permit udp any any eq 5036
access-list 101 permit udp any any eq 5060
!
!RTP traffic
access-list 102 permit udp any any range 16384 32767
!
class-map match-all voice-traffic
match access-group 102
!
class-map match-all voice-signaling
match access-group 101
!
policy-map qos-voice
class voice-traffic
priority 240
class voice-signaling
bandwidth 16
class class-defult
fair-queue
!
interface FastEthernet0/0
service-policy output qos-voice
!
interface Serial0/0
rate-limit input 1408000 8000 8000 conform-action transmit exceed-action drop
My question is, why don't we use service-policy on the input interface as well as the output? Thanks.
-Bell