I have now connected two of our office branches with a bundle of two T1 configured in MLPPP mode. I have data and voice going across and in normal circumstances everything works just fine but when there is a heavy traffic ( like when the backup is running and pulling data across) the voice part start struggling and employees complain about a goggling in the voice. I have come to the conclusion that there must be something wrong with my configuration for prioritizing the voice packets over data. I really appreciate if anyone could give a look at the attached configuration and comment on current configuration or suggest a different solution.
The policy, itself, basically looks alright, although the bandwidth allocation for voice signaling might be too little.
In execution, you didn't match any voice signaling packets, but since you're running FQ in class-default, you probably don't need a defined class for this traffic.
What is of much concern with your policy stats, is the deep queue within class-default and the number of drops (21%).
What you might try, remove both header compression statements from the multilink interface.