You are halfway there. The packets are marked, but you need an output service policy on the frame relay side. Define a class map to match on the AF33 packets, then define a policy map that gives that class either a set bandwidth or percentage of available. Here is an example:
class-map match-any Web
description Web
match ip dscp af33
!
policy-map Frame
class Web
bandwidth 128
class class-default
fair-queue
random-detect dscp-based
This would assign 128 kb to your Web traffic, and fair queue the rest of the traffic, with WRED.
You will need to then set this as a service policy out on the frame circuit, which is often done with a frame class map, but this will depend on how your frame relay is configured.
map-class frame-relay WAN128
frame-relay adaptive-shaping becn
frame-relay cir 256000
frame-relay bc 16000
frame-relay mincir 128000
service-policy output Frame
!
interface Serial2/1:1.2 point-to-point
bandwidth 256
ip address 10.X.X.X 255.255.255.252
frame-relay class WAN128
To see if it is working:
sh policy-map int s2/1:1.2
It is possible to just use your access list based class to identify the Web traffic through the output service policy, but it is best practice to do it the way you have started; mark packets on ingress, then use DSCP on the output side. This makes it simplier if the traffic traverses multiple routers.
This applies QOS from the remote router back to the local site, but normally you would also configure QOS from the local site to the remote site as well.
Please rate helpful posts.
Dave