-= QoS for VoIP... Is this correct or am I doing it wrong =-
I'd like to know if I'm doing QoS correctly between 2 sites (Lincoln and Raleigh). We are doing VoIP (using SIP and RTP) between both sites with the only other protocol being TCP 2633 (i3CLIENT). The i3CLIENT traffic is the desktop software that runs on each users desktop. It tells the users when a call comes in and information about the customer on the phone before the user actually answers the call.
Our network is a frame-relay network. Each site, Raleigh/Lincoln, has 3 T1 circuits with a PVC talking to the upstream end with a CIR of 1536. I chose to do IP CEF per-packet to aggregate the T1s but would prefer to do MLPoFR. My issue is sometimes the users complain of the i3 client running slow. When I do 'show policy-map int xxx' I see that the Voice has no drops but the Trans policy-map is dropping roughly 26% of traffic. I'd like to tweak the Trans (i3CLIENT) stuff to not drop so much BUT insure that the VOICE gets all the bandwidth it needs. I wasn't sure if I needed to create the service policy for a 1536 shape average or 4608 shape average. The only other protocols that flow between these 2 sites is probably ping and SIP.
Should I attempt MLPoFR to cut down on jitter? How would I do it based on my config? According to our users, call quality sounds great but I'm not sure if I'm doing it efficiently or correctly.
The below attachment is from the Raleigh router (The Lincoln router is mirror-image):
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.