[c-nsp] Cisco VoIP and QoS using NBAR

Ravengate isaac at ravengate.net
Thu Jul 7 14:05:19 EDT 2005


Hello,

hmmm... there was this statement in there before:

ip qos dscp cs5 media

under:

dial-peer voice 40 voip
destination-pattern 4..
session target ipv4:192.168.151.1
dtmf-relay cisco-rtp

-------------------------------------

this is a DiffServ thing right?

i removed that because i thought that maybe this statement was altering the 
VoIP packet so that our NBAR class map wasn't recognizing it as RTP VoIP 
traffic.

how would i use the ip qos statement dscp cs5 media to match with an acl?

can i use NBAR and an ACL at the same time?

thanks,
jg



----- Original Message ----- 
From: "Tantsura, Jeff" <jtantsura at ugceurope.com>
To: "'Ravengate'" <isaac at ravengate.net>; <cisco-nsp at puck.nether.net>
Sent: Thursday, July 07, 2005 2:58 AM
Subject: RE: [c-nsp] Cisco VoIP and QoS using NBAR


> Hi,
>
> Why don't you configure under dial-peer statement: ip precedence <x> and
> then match on it?
>
> Jeff
>
> -----Original Message-----
> From: Ravengate [mailto:isaac at ravengate.net]
> Sent: Wednesday, July 06, 2005 7:56 PM
> To: cisco-nsp at puck.nether.net
> Subject: [c-nsp] Cisco VoIP and QoS using NBAR
>
>
> Greetings list.
>
> i am hoping someone can point me in the right direction.
>
> we are using NBAR to classify traffic (Citrix and trying to accomplish the
> same with Cisco VoIP:
>
> dial-peer voice 20 voip
> destination-pattern 2..
> session target ipv4:192.168.152.1
> dtmf-relay cisco-rtp
> !
> dial-peer voice 40 voip
> destination-pattern 4..
> session target ipv4:192.168.151.1
> dtmf-relay cisco-rtp
> !
>
> ------------------------------------------------------
>
> our class maps mark the Citrix traffic just fine but the voice class map
> doesn't seem to be recognizing the VoIP traffic:
>
> class-map match-any Voice_ClassMap
>  match protocol rtp
> class-map match-any Citrix_ClassMap
>  match protocol citrix
> !
> !
>
> we tried both match protocol rtp and match protocol rtp-audio....
>
> Foo-Host#sh policy-map interface serial 1/0.17
> Serial1/0.17: DLCI 17 -
>
>  Service-policy output: RemoteSite_PolicyMap
>
>    Class-map: Voice_ClassMap (match-any)
>      0 packets, 0 bytes
>      5 minute offered rate 0 bps, drop rate 0 bps
>      Match: protocol rtp
>        0 packets, 0 bytes
>        5 minute rate 0 bps
>      Queueing
>        Strict Priority
>        Output Queue: Conversation 24
>        Bandwidth 30 (%)
>        Bandwidth 37 (kbps) Burst 925 (Bytes)
>        (pkts matched/bytes matched) 0/0
>        (total drops/bytes drops) 0/0
>
>    Class-map: Citrix_ClassMap (match-any)
>      1615238 packets, 224636802 bytes
>      5 minute offered rate 0 bps, drop rate 0 bps
>      Match: protocol citrix
>        1615238 packets, 224636802 bytes
>        5 minute rate 0 bps
>      Queueing
>        Output Queue: Conversation 25
>        Bandwidth 40 (%)
>        Bandwidth 49 (kbps) Max Threshold 64 (packets)
>        (pkts matched/bytes matched) 49790/23910678
>        (depth/total drops/no-buffer drops) 0/0/0
>
>    Class-map: class-default (match-any)
>      1135121 packets, 522233684 bytes
>      5 minute offered rate 0 bps, drop rate 0 bps
>      Match: any
>      Queueing
>        Flow Based Fair Queueing
>        Maximum Number of Hashed Queues 16
>        (total queued/total drops/no-buffer drops) 0/101/0
> Foo-Host#
>
> -----------------
>
> any ideas on what we need to do in order to classify the VoIP traffic
> properly?
>
> thanks very much,
> jg
>
>
>
> _______________________________________________
> 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