Looks like your traffic shaping parameters are set up ok on your remote. One issue I see here is that you have no methodology of setting up Queues to service the voice traffic first. If you're showing fragmentation on the frame-relay interface and packets being delayed, there is definetely traffic on it.
My suggestion therefore would be to
1) put voice in a LLQ so it can be serviced before the data, you can treat the other data in 1 queue if you want.
2) put a sniffer on the E1 to dettermine what this other traffic is that you say is not there.
Check for implementing QOS design guide on CCO. Also, check out LLQ. If you have trouble, post a reply and I will send you a sample.
One other thing, Hopefully you're not oversubscribing the CIR at the host side or the remote. The traffic shaping at the remote indicates 128k cir which is fine but you also say that you have a 768 pipe at the host.
I see that Cancun is interface .6 and that you have a frame-relay map class for 512 as well. If so, 2 interfaces essentially one at 512 and the other at 128k would eat up your CIR of 768 at any given time so if you have more remotes, that could be an issue as well.
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...