[cisco-voip] TOS marking of SCCP on CM 3.3 to CS3

[Ted Nugent]

Thanks and Yes you're right.. that does the trick.
However.. Thats cheating! :-P 
The phone is still marking AF31 and we're just
remapping it on the switch. Sniffer trace don't lie.
:-/

Internet Protocol, Src: 192.168.8.50 (192.168.8.50),
Dst: 10.83.136.111 (10.83.136.111)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x68 (DSCP 0x1a:
Assured Forwarding 31; ECN: 0x00)
    Total Length: 40
    Identification: 0xbcb5 (48309)
    Flags: 0x00
    Fragment offset: 0
    Time to live: 64
    Protocol: TCP (0x06)
    Header checksum: 0x6216 [correct]
    Source: 192.168.8.50 (192.168.8.50)
    Destination: 10.83.136.111 (10.83.136.111)

--- Jake Rybak <jrybak at annese.com> wrote:

> Do not trust DSCP. Trust COS and it will work. Make
> sure the mls qos map
> cos-dscp 0 8 16 24 34 46 48 56
> 
> 
> -----Original Message-----
> From: Ted Nugent [mailto:tednugent69 at yahoo.com] 
> Sent: Thursday, June 22, 2006 19:45
> To: jake rybak
> Cc: ciscovoip Voip
> Subject: Re: [cisco-voip] TOS marking of SCCP on CM
> 3.3 to CS3
> 
> Well at least I'm not smoking crack! Any other
> ideas?
> 
> 
> Internet Protocol, Src: 192.168.8.50 (192.168.8.50),
> Dst: 10.83.136.111 (10.83.136.111)
>     Version: 4
>     Header length: 20 bytes
>     Differentiated Services Field: 0x68 (DSCP 0x1a:
> Assured Forwarding 31; ECN: 0x00)
>         0110 10.. = Differentiated Services
> Codepoint:
> Assured Forwarding 31 (0x1a)
>         .... ..0. = ECN-Capable Transport (ECT): 0
>         .... ...0 = ECN-CE: 0
>     Total Length: 40
>     Identification: 0x7e35 (32309)
>     Flags: 0x00
>         0... = Reserved bit: Not set
>         .0.. = Don't fragment: Not set
>         ..0. = More fragments: Not set
>     Fragment offset: 0
>     Time to live: 64
>     Protocol: TCP (0x06)
>     Header checksum: 0xa096 [correct]
>         Good: True
>         Bad : False
>     Source: 192.168.8.50 (192.168.8.50)
>     Destination: 10.83.136.111 (10.83.136.111)
> 
> 
> 
> --- jake rybak <jrybak at annese.com> wrote:
> 
> > I also been caught not changing mgcp signaling and
> seeing the wrong 
> > traffic hit a policy.map at af31 thinking it was
> sccp.
> > 
> > Ted Nugent wrote:
> > > 3.3(4) doesn't list the DSCP on the phone like
> > 3.3(5)+
> > > but I'm definitely seeing the class-map
> increment
> > AF31
> > > when I hit any keys while a call is active... 
> > > I guess I'll need to pull some sniffer traces to
> confirm this since 
> > > all config appears to be
> > correct.
> > > Probably need to reload the switch just confirm
> > it's
> > > reading QOS correctly.
> > > I was thinking it might be a bug and I guess a
> > sniffer
> > > will confirm it. I welcome any other input and
> > I'll
> > > post back what the capture shows me.
> > >
> > >
> > > --- jake rybak <jrybak at annese.com> wrote:
> > >
> > >   
> > >> I had the same problem or at least I thought.
> The phone would say
> > >> AF31(bug) but the packet captures said cs3. I
> > would
> > >> see them match a
> > >> class-map at af31 on my wan router until I
> > changed
> > >> the cos-dscp mapping.
> > >>
> > >> It was a while ago so I do not recall the exact
> scenario.
> > >>
> > >> Ted Nugent wrote:
> > >>     
> > >>> Thats exactly what I thought too at first...
> so
> > I
> > >>>       
> > >> set
> > >>     
> > >>> the port to trust DSCP and just for grins I
> set
> > >>>       
> > >> the
> > >>     
> > >>> COS-DSCP map back to 24.. same dealio..
> > >>>
> > >>> also the trunk to the gateway is set to trust
> > >>>       
> > >> DSCP...
> > >>     
> > >>>
> > >>> --- jake rybak <jrybak at annese.com> wrote:
> > >>>
> > >>>   
> > >>>       
> > >>>> I would guess it would be your mls qos map
> > >>>>         
> > >> cos-dscp
> > >>     
> > >>>> statement on the switch.
> > >>>>
> > >>>> Ted Nugent wrote:
> > >>>>     
> > >>>>         
> > >>>>> This has been driving me nuts.
> > >>>>> I'm running CM3.3(4)SR2 and I've changed the
> > TOS
> > >>>>>       
> > >>>>>           
> > >>>> Mask
> > >>>>     
> > >>>>         
> > >>>>> (IP TOS BitMask for Comm. between CCM and
> > >>>>>           
> > >> Device*)
> > >>     
> > >>>>>       
> > >>>>>           
> > >>>> to
> > >>>>     
> > >>>>         
> > >>>>> CS3 (0x60). As the param implies it marks
> the
> > >>>>>       
> > >>>>>           
> > >>>> traffic
> > >>>>     
> > >>>>         
> > >>>>> correctly from CM to my remote site endpoint
> > >>>>>       
> > >>>>>           
> > >>>> however
> > >>>>     
> > >>>>         
> > >>>>> the traffic from the endpoint (IP Phone)
> > towards
> > >>>>>       
> > >>>>>           
> > >>>> CM is
> > >>>>     
> > >>>>         
> > >>>>> still at AF31? Short of remarking the
> control
> > >>>>>       
> > >>>>>           
> > >>>> traffic
> > >>>>     
> > >>>>         
> > >>>>> at the switch or upgrading to 4.1 can anyone
> > let
> > >>>>>       
> > >>>>>           
> > >>>> me
> > >>>>     
> > >>>>         
> > >>>>> know how this could be accomplished?
> > >>>>> Thanks Ted
> > >>>>>
> > >>>>>
> > >>>>>
> > >>>>>           
> > >>
> > __________________________________________________
> > >>     
> > >>>>> Do You Yahoo!?
> > >>>>> Tired of spam?  Yahoo! Mail has the best
> spam
> > >>>>>       
> > >>>>>           
> > >>>> protection around
> > >>>>     
> > >>>>         
> > >>>>> http://mail.yahoo.com
> > >>>>>
> > _______________________________________________
> > >>>>> cisco-voip mailing list
> > >>>>> cisco-voip at puck.nether.net
> > >>>>>
> > >>>>>       
> > >>>>>           
> > >>
> >
> https://puck.nether.net/mailman/listinfo/cisco-voip
> > >>     
> 
=== message truncated ===


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com