I believe you have another thread started with this same question that I have posted some questions to, but I thought I would add some expertise to your config above.
1) For a 512Kbps DSL circuit, there is no way that you can shape peak to 384Kbps on both tunnels! You are, by definition, oversubscribing the DSL circuit.
2) Is all traffic going through these tunnels ONLY, or are you allowing Internet traffic from each site directly as well? Keep in mind that your 512Kbps uplink speed (if that is what you stated) is for ALL traffic, your tunnel(s) AND any local traffic going out the DSL directly. You need to design this and pre-define the bandwidths that you will allocate to each tunnel and also to local Internet traffic. The sum of those bandwidths cannot exceed your provisioned DSL rate.
3) You are on the right track with applying the policy-map to the tunnel interfaces, but you should not be using 'shape peak', you should be using 'shape average' to a bandwidth that is 95% of your tunnel bandwidth and according to your pre-defined design.
4) The configuration is different depending on the design you choose:
a) all traffic utilizing the tunnels only OR
b) voice traffic using the tunnel(s) and all other traffic hitting the DSL/Internet directly OR
c) voice and enterprise data traffic using the tunnel(s) and Internet only traffic using the DSL directly (outside the tunnels)
5) In general, you should shape ALL the traffic leaving the outside DSL interface so as not to exceed the provisioned bandwidth AND you prioritize the voice (and voice signaling) traffic using the tunnel(s) into the parent shaper on the DSL interface.
The permutations get complicated on this, but as long as your config matches your design, all will be well.
Let me know the design you are trying to implement...
