Media for VoIP Frame Relay

VoIP Frame Relay

We have major voice quality problems with your new Mitel VoIP system across the WAN I have had our WAN provider and Cisco check our configs and they say everything looks good. We are experiencing high amounts of jitter and low amounts of packet lose, jitter is ranging between 60ms - 140ms. We have frame relay with Voice and Data going over the same PVC, I recently read that Cisco recommends put Voice and Data on separate PVCs.

Cisco website states the following

formatting link

A good solution employed by some customers is to use separate PVCs for data and voice. This solution enables the customer to transmit up to port speeds in the data only PVC while maintaining a load at or below CIR on the voice PVC. Some frame providers may not find the solution appropriate depending on the frame switch and its queuing structure. If possible, have the Frame Relay provider prioritize the voice PVC over the data one so that there is not any queuing delay because of the data packets.

We currently have our CIR set at 768 and our WAN provider just told us our true CIR is 128 see config below.

This is our current config and we have the CIR set to 768.

interface Serial0/0.100 point-to-point bandwidth 768 ip address 192.168.1.10 255.255.255.252 frame-relay interface-dlci 100 IETF class VoIP

map-class frame-relay VoIP frame-relay fragment 1600 frame-relay cir 768000 frame-relay bc 300 frame-relay be 0 frame-relay mincir 768000 service-policy output Wan-Policy-768-Frame logging trap debugging access-list 100 permit gre host 192.168.1.10 host 192.168.1.2

How would I configure separate Voice and Data PVC to allow bursting to 768 yet giving the Voice traffic a guaranteed 128 of bandwidth? Would I setup another sub interface for data with another PVC and then set the frame-relay cir to 0 on the data PVC and set the CIR to 128 on the Voice PVC?

Do you think not having our routers currently configured this way is the source of the voice quality problems please give me your thoughts?

Thank You,

Chris