Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 473
  • Last Modified:

Terrible call quality

-We have a main office with satellite offices.
-The main office has a Nortel switch, with a PRI (coming in from verizon).
-The main office has VPN tunnels to the satelite offices (ASA 5505)
-Every office has Avaya 4610 ip phones.
-The remote sites have Avaya gateways.

The call quality over the tunnel is just horrendous. Cutting out, static, jitter.  Our phones are in a different network than our data, so we did some class-map policies to prioritize the network (see below).

Any ideas?
One of our satellite offices:
 
class-map VOICE
 match access-list voip-traffic
class-map VOICE2
 match dscp ef
class-map inspection_default
 match default-inspection-traffic

Open in new window

0
dissolved
Asked:
dissolved
  • 3
  • 2
1 Solution
 
ehatchellCommented:
What type of network connection do you have between the two sites?  What information do you have on your network statistics (round trip latency, etc)?
Are you using ASA's on both ends for the tunnel?  What model are the GW's and switches?  What else are you running on this network?
0
 
dissolvedAuthor Commented:
Both ends are ASAs. The connection from headquarters------------->internet  is a T1
The connections from remote sites ---------------->internet is dsl

The switches are extreme networks PoE. The only other thing on this network are the user's computers. The sites have probably 10 people each.

Not sure on model of gateways. Just inherited this network. I'll check on round trip
0
 
ehatchellCommented:
Can you verify the DSL speed?  How about stats on the T1... Any detailed historical data available?
0
 
dissolvedAuthor Commented:
768kbps my man

I can pull detailed historical data tomorrow. The ping response time varies greatly. I lowered the aes encryption from 256 to 128. Hoping that helps
0
 
ehatchellCommented:
Ideally, you want round trip latency in the 150ms or less realm at all times... if it varies greatly, I would start with why, and gate your connection to also account for control traffic as applicable on your network.  I think 768k is fair enough for voice, but over the internet it could be spotty as its not controlled.  So, get some monitoring up and going, let's better understand what is traversing your network, how stable it is, and let's even see sans the regular network traffic is we can get it to stabilize for voice as throwing in QoS on a DSL connection that is crap is just throwing time down the drain.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Improve Your Query Performance Tuning

In this FREE six-day email course, you'll learn from Janis Griffin, Database Performance Evangelist. She'll teach 12 steps that you can use to optimize your queries as much as possible and see measurable results in your work. Get started today!

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now