Voip and Echo Problems

Symptom Resolution Note
Title: The user reports echo during a call
Issue: 0.8 Date: September 14, 2001

Compass ID: Author: Converged Solutions Group
Westminster, CO USA
Contents
1 General ........................................................................................................................ 2
2 Terminology ................................................................................................................ 2
2.1 DEFINITY .......................................................................................................... 2
2.2 Remote Diagnostic Tools .................................................................................... 2
2.3 Echo Control ....................................................................................................... 2
2.4 Other Terms......................................................................................................... 3
3 Voice Path Routing ..................................................................................................... 3
3.1 Routing Modes .................................................................................................... 3
3.2 Station Forms ...................................................................................................... 4
4 Echo............................................................................................................................. 4
4.1 Background ......................................................................................................... 4
4.2 Echo Suppression Deployment Rules ................................................................. 7
4.3 Echo Management in Avaya Equipment............................................................. 9
4.4 Delay Measurement Results.............................................................................. 11
4.5 Acoustic Echo on IP Telephones and Voice Path Routing ............................... 11
5 Symptom Resolution Procedure................................................................................ 13
6 Network Configurations............................................................................................ 25
7 References ................................................................................................................. 42
Avaya Communication – Proprietary

Use pursuant to Company Instructions
1 General
This Symptom Resolution Note is applicable to telephone calls involving IP, analog,
DCP, PSTN, soft-phones and speaker telephones.
In this Symptom Resolution Note, the indication DEFINITY is used for the traditional
DEFINITY circuit-switched systems (Prologix, G3si, G3r) and also for products such as
DEFINITY 1 and the IP600, which provide similar features as the traditional DEFINITY
or enhancements thereof.
2 Terminology
2.1 DEFINITY
Prowler Media Processor board (also called MedPro TN2302AP). A

DEFINITY circuit pack which converts voice audio signals between time slot and
VoIP/Ethernet format. Prowler resources are dynamically assigned to a telephone
on a per call basis. The Prowler auto-negotiates its transmission modes by default
(see below for more details on Ethernet auto-negotiation).
C-LAN (TN799 / TN799B / TN799C boards). A DEFINITY circuit pack that
handles the H.323 based signaling protocol between DEFINITY and telephones.
C-LAN resources are statically assigned to a telephone as soon as it is registered
with DEFINITY. The C-LAN supports fixed 10Mbit/s Half-Duplex (see below)
transmission (auto-negotiation may be supported in the future).
2.2 Remote Diagnostic Tools

The following diagnostic commands may be supported in DEFINITY Release R10.
Remote Ping. A ping command executed by a telephone under control of a
remotely located DEFINITY.
Remote Trace-route. A trace-route command executed by a telephone under
control of a remotely located DEFINITY.
2.3 Echo Control

Hybrid. A device that converts between a four-wire internal system PBX or
Central Office switch interface and a two-wire analog telephone line or analog
trunk interface.
Balance Network (or Balance Impedance). A controllable impedance on an
Analog trunk card used for reducing the electronic reflection (electronic echo)
caused by an impedance mismatch between the analog trunk cable and the hybrid
on the trunk card. On the Avaya Analog trunk cards the balance network is
controllable between two values:
o Trunk card cable length < 3000 feet: 600 ohm.
o Trunk card cable length > 3000 feet: 1350 ohm parallel with 210 nf.
2

2.4 Other Terms
LEC. Local Exchange Carrier. A non-long distance telephony service provider.

IXC. Inter-Exchange Carrier. A long distance telephony service provider.
3 Voice Path Routing
3.1 Routing Modes

Three types of voice path routing modes are distinguished in DEFINITY:
Shuffling. The process of passing the voice channel connecting two telephony
endpoints so that the voice does not use any intermediate DEFINITY Prowler
resources.
Hairpinning. The process of passing a voice channel connecting two IP
endpoints so that the voice goes through the Prowler board in IP format, without
having to go through the DEFINITY Time Division Multiplexing (TDM) bus.
Two variants of hairpinning exist:
Shallow Hairpinning. Only the IP and RTP packet headers are changed
as the packet is routed through the Prowler board. This variant requires
that both endpoints be using the same codec.
Deep Hairpinning. Both the IP and RTP packet headers are changed as
the packet is routed through the Prowler board. This variant allows the
endpoints to use different codecs and echo cancellation of the voice signal.
DEFINITY R9 only allows shallow hairpinning. This Symptom Resolution Note
only assumes shallow hairpinning. This may need to be modified in a later
release.
TDM bussing. The process of passing a voice channel through the DEFINITY
Time Division Multiplexing (TDM) bus. This may apply to voice paths between
any combination of IP (soft) telephone, DCP telephone, Analog telephone, PSTN
telephone, and wireless telephone.
As examples, the following voice paths are all considered shuffled:

A voice path between two IP telephones that only treverses an IP network without
intermediate Prowler.
A voice path between two analog telephones on an Avaya R300 system residing
completely within the R300.
A voice path between two telephones on two different Avaya R300 systems,
which are both controlled from a DEFINITY, and which has a voice path via an
IP network not involving any Prowlers.

3.2 Station Forms
For the operation of setting up voice paths between two telephones it is important to
distinguish the act of shuffling/hairpinning/tdm-bussing from the provisionable settings
in DEFINITY on the station screens. The rules that are used to handle calls when station
form setting match or not need to be understood as well:
For each Analog or DCP telephone directly connected to a line card on a
DEFINITY:
o No shuffling or hairpinning can be enabled on the station form.
o TDM bussing is the only routing mode.
For each Analog or DCP telephone connected to a R300:
o Only shuffling can be enabled on the station form.
o If shuffling is enabled on the station form, then the telephone acts as a
virtual IP telephone towards DEFINITY.
For each IP telephone:
o On the DEFINITY station form, shuffling (“IP-direct”) and hairpinning
(ip-hairpin”) can be enabled/disabled independently.
For each IP telephone or an Analog or DCP telephone connected to a R300:
o TDM bussing cannot be set explicitly on the station form as it is the
default routing mode.
o The default routing mode will always be used when shuffling and
hairpinning (hairpinning for an IP telephone only) are disabled on the
station form of the telephone.
o The default voice path routing mode can be overridden by enabling
shuffling and/or enabling hairpinning (hairpinning for an IP telephone
only).
o Matching Rule I: The voice path will only be shuffled/hairpinned if both
telephones involved in a call have shuffling/hairpinning simultaneously
enabled and the network configuration allows this (e.g. two IP telephones
on different connected to Prowlers on different LANs do not allow
shuffled voice path routing).
o Matching Rule II: Any mismatch between the voice path routing mode
setting on the station forms of two telephones involved in a call will cause
the routing mode to drop to the default routing mode, i.e. TDM bus.
o Since any Analog or DCP telephone only supports TDM bus routing, any
call to/from an IP telephone will be TDM bus routed.
4 Echo
4.1 Background
Due to their low delay, echo has mostly been inperceptable in circuit-switched networks.
In general, IP calls experience a much larger delay. Therefore, echo becomes a much
more important issue.
Echo. The phenomenon that a voice signal is reflected back to the speaker at an
audible level such that it interferes with the ability to have a normal conversation
4

with another party. Echo is caused by a combination of signal delay and signal
reflection. Multiple echos may be created. The first echo is called the primary
echo, the second echo is called the secondary echo and so forth.
Echo may be created in two ways:

• Acoustically, in the telephone handset, headset, or speaker-phone.
• Electrically, by 2-to-4 wire hybrids, or as cross-talk in wires or adapters, or by an
impedance mismatch between a cable and an analog trunk card.
In general, the perception of echo is call-dependent. The echo problems for calls made
over a Wide Area Network (WAN) are normally much larger compared with calls over a
Local-Area Network (LAN).
In current voice networks many possible combinations of telephones and telephone

networks are possible (see Figure 4 for an impression). These many combinations make
proper echo suppression a challenging task. Notably shuffled IP calls, calls to analog or
IP telephones, telephones connected to fax machines, headsets, and multiple analog
telephones connected to the same switch port are notorious for causing echo.
Due to this large number of possibilities, many different kinds of echo problems may
occur. As an example, because echo is a delay sensitive phenonenon, a call between an IP
telephone and a DCP (or analog) telephone may suddenly cause perceptable echo on the
DCP telephone whereas before any call from another (non-IP) telephone to the DCP
telephone did not experience echo problems (see Figure 1).

IP System or Network
(with delay) IP Telephone, Soft-phone,
IP Telephone DCP/analog/PSTN telephone
Acoustic
Coupling
Returned Echo
Electrical
Coupling
(in set and cord)
This type of echo problem has always been present in voice communication networks:
• short delays of TDM networking in the past has masked the problem
• longer networking delays greatly exacerbate the problem
Figure 1: Acoustic and Electric Echo in caused by IP Systems/Networks
To non-experts it may look like that the DCP telephone is the culprit and thus in fact
always had a low quality whereas really the IP telephone and the extra network delay due
to the IP network are really the cause of the echo problem.
Some concepts that are used to describe echo are:

Echo Return Point. A reflection point causing acoustic or electric echo.
Echo Path Delay. The delay experienced between a signal and an echo returned
from the same signal.
Echo can be suppressed from a voice signal in two ways. One way is by using a process
called echo cancellation:
Echo Cancellation. The process of electronic removal of echo using signal
processing, see Figure 2. A device that performs echo cancellation is called an
echo canceller. A proper implementation of an echo canceller adds a minimal
delay to the signal as it only measures the difference between the original and the
echo return signal and then subtracts the echo form the signal that has the echo
superimposed.
The ability of an echo canceller to remove echo can be characterized by its tail length:
Echo Tail Length. The length, measured in msec, of the sequence of voice
samples that is involved in echo cancellation. The longer the echo tail, the better
echo can be cancelled. The echo tail length of an echo canceller should be longer
than the echo return delay to cancel the echo. If not, the echo passes unattenuated.
6

Another way in which echo can be removed, and which can only be applied when a
conversion is made from a four-wire to two-wire environment by means of a hybrid, it to
use a balance network. The balance network can effectively provide an impedance match
between cable and its hybrid termination.
With respect to the point where echo is observed, two classes of network locations can be
distinguished in the voice path between telephones:
Near-End. A point in the talk-path of a call that is relatively close to where the
echo is generated, before it traverses any large delay incurring network. The near-
end may be close to a hybrid, telephone, speaker-phone, or headset.
Far-End. A point in the talk-path of a call that is relatively far away from the
point where an echo is generated and is located at the other side of a large delay
intervening network, e.g. at the other side of a Wide-Area Network.
4.2 Echo Suppression Deployment Rules

The following design rule should be used for the deployment of Voice over IP (VoIP) in
order to control echo effectively:
Near-End Echo Cancellation Rule. Consistently use near-end echo cancellation

to minimize echo.
This near-end echo cancellation rule should be followed because:

If echo is not properly cancelled, the perception of the echo will become worse as
the delay increases. The echo return delay increases as one moves further away
from the echo return point. When echo is properly removed at the near-end, an
intervening network only causes extra delay.
This rule ensures that echo is cancelled as close as possible to the source of the
echo. Proper far-end echo-cancellation may require a much longer echo
cancellation tail as intervening networks may add substantially more delay. A
longer tail results in additional digital signal processing costs.
Data equipment, such as IP routers, causing a large delay in the voice path may be
endicted for the echo problem while it is not the actual source of the echo.

Basic Rule for echo cancellation: Provide “Near End” Cancellation
Speech Burst
Pt. A
“Reference” Voice
Network
Echo Path Delay
(Time Period Relative to “Reference”
Hybrid between end of speech burst and
May Introduce
Introduces
receipt of end of the Echo Return) Significant
Lossy, 4 wire
Delays
2 Wire Smeared* environment
Version of
Speech Burst Signal Processing Including
Always 4 Wire
Analog in the Delays to Match Arrival
Return Path
Environment
Telephone Time of Echo Return
with respect
Pt. B to Voice
Pt. B Transport
Digital Signal Addition

Echo Return
Echo Canceller
“Near End” Environment
Acoustical Echo Electrical Echo
Figure 2: Cancellation of Hybrid Induced Echo
Another, more specific, design rule for IP Gateways that follows from the above provided
near-end echo cancellation rule is the following echo cancellation rule for gateways:
IP Gateway Echo Cancellation Rule. All IP gateways should be equipped with

on-board echo-cancellation where the echo energy is cancelled in the direction
towards the non-IP network.
Several types of IP gateways can be distinguished:

IP telephones (and Soft-IP-phones). Although often not recognized as such,
these types of telephones convert the analog signal into an IP signal and can
therefore be considered gateways. Echo cancellation should be deployed in an IP
telephone in order to eliminate acoustically induced echo and thereby to adhere to
the near-end echo cancellatio rule. In fact, in a pure IP network, the only sensible
place to deploy near-end echo cancellation is in the IP telephones as the voice
paths in an IP network may be diversely routed, and Ethernet switches and IP
routers should only perform lower layer processing and frame/packet forwarding
functions so as to minimize transit delay.
IP Terminal Adapters. These are analog telephone/Digital telephone to IP signal
convertors normally implemented as line cards in a TDM circuit-switching
system, or IP router. An example of an IP terminal adpater is the R300 system.
Current analog and digital telephones normally do not have on-board echo
cancellers, thus the terminal adapter is the next best closest point to a non-echo
cancelling telephone where a near-end echo canceller can be located.
8

IP Trunk Gateways. These are devices that provide the conversion of multiple
voice signals between e.g. a circuit-switched and a Voice over IP format for. An
example is an IP-enabled DEFINITY equipped with a Prowler card providing the
gateway function. These gateways may be implemented as a line-card in a circuit-
switch, in an IP router, or as a separate device between the public circuit-switched
network and an IP network. Ideally, near-end echo cancellers are present in trunk
gateways as well as one can never be assured that echo cancellation is performed
in the networks at either side of the gateway.
Basic Rule for echo cancellation: Provide “Near End” Cancellation
Speech Burst
Pt. A
“Reference” Voice
Network
Echo Path Delay
(Time Period Relative to “Reference” May Introduce
4 wire between end of speech burst and Significant
From Cable receipt of end of the Echo Return)
environment Delays
Signal Processing Including
Always 4 Wire
Delays to Match Arrival
Environment
Time of Echo Return
Speaker/Microphone Set, with respect
Pt. B to Voice
Integrated Headset, or
DCP, IP, or PSTN telephone Pt. B Transport
Digital Signal Addition

Echo Return
Echo Canceller
“Near End” Environment “Far End”

Environment
Acoustical Echo Electrical Echo
Figure 3: Cancellation of Acoustic and Cable Echo
By using the two rules provided above consistently during both the implementation of
Voice over IP network equipment, and network implementation, the quality of the voice
will be assured much better than with a haphazard VoIP network deployment.
One or multiple echo cancellers may be present in the voice path between two
telephones. The order of the operation of multiple echo cancellers in a single voice path is
important for their effectiveness. A canceller with a long tail located close to an echo
return point, will render a canceller with a short tail that is located further away from the
echo return point ineffective with respect to the same echo.
4.3 Echo Management in Avaya Equipment

Avaya’s voice equipment can be used in many different ways, as illustrated in Figure 4.

Echo cancellation and suppression is provided in DEFINITY in the following ways (see
Figure 4):
If implemented on a card, echo cancellation can be turned off or on.
Analog line cards and digital line cards (both for connectivity to telephones) do
not provide echo cancellation.
On analog trunk cards no echo cancellation is provided but the setting of balance
networks can be optimized so as to generate minimal energy reflection.
EI (Extension Interface) cards do not provide echo cancellation.
On a T1/E1 digital trunk card echo cancellation may or may not be present. If
present it is directed toward the external port and has a 96 msec tail length. The
direction of the echo cancellation is provisonable.
On the ATM-EI trunk card echo cancellation is directed towards the external port
and has a 8 msec tail length.
On the Prowler trunk card echo cancellation is directed towards the external port
and has a 16 msec tail length on the initial version. The tail length will be
expanded with future versions of firmware and/or board releases. In the future the
tail length may be settable in a variety of steps.
Intra-Switch
CSS
Inter-Exchange Analog
PSTN
Carrier EI
T1/E1
Digital
XXms
Analog 8ms
Local Exchange
Inter-Switch or Intra-Switch
ATM-EI ATM
Carrier (PSTN) T1/E1
ital o g Digital WAN or
Dig a l A
An D 96ms
LAN
R300 C-HAWK
Xms
32ms 16ms
S-IPSI
IP
16ms
WAN or
IP WAN or LAN Prowler LAN
16ms
Prowler
Digital
headset
C Digital
Electrical Echo*
TDM Bus
Digital
FAX
8411
Analog Acoustical Echo
FAX or
Analog
Digital (DCP) Echo cancellation by

MCK Ext PSTN MCK Ext
removing (cross) the
echo energy in the
*Any Telephone which indicated direction
has a transmitter and
2 Wire Analog Digital(DCP, BRI) IP a receiver also may
have acoustical echo
Figure 4: Overview of DEFINITY Voice Paths and Echo Cancellers
Echo cancellation in other Avaya equipment is provided as follows:

R300:
o Echo cancellation only removes the echo energy in the direction towards
the IP network, not towards the Digital or Analog trunk, and has a 32msec
tail length.
10

C-HAWK:
o Echo cancellation only removes the echo energy in the direction towards
the IP network, not towards the Digital or Analog trunk and has a 16 msec
tail length.
IP Telephones:
o None of the Avaya telephones supports echo cancellation, echo
suppression (not cancelling) is provided for the headset port on an IP
telephone??correct??. A pure IP call can therefore not be echo cancelled.
The following types of calls may not be exposed to any echo cancellation:
An IP telephone to IP telephone voice path without intermediate DEFINITY
equipment (i.e. a shuffled call, see Figure 6A) may not pass any echo
cancellation, unless provided by e.g. an intermediate LEC or IXC PSTN networks
in VoIP gateways.
Depending on the direction of the voice path, an IP telephone to analog telephone
voice path may not experience any echo cancellation (see e.g. Figure 19B) unless
provided by an intermediate PBX gateway (such as a Prowler), a LEC or IXC
PSTN network (see e.g. Figure 37C).
As mentioned, at present, none of the Avaya telephones supports echo cancellation. This
may not be much of a problem as long as circuit-switched equipment with some echo-
cancellation capabilities is present in the voice path. However, the voice path between
two IP telephones could constitute Ethernet switches and IP routers, and no intermediate
DEFINITY circuit-switched equipment at all. This may cause significant echo problems,
hence the need for echo cancellation in future versions of Avaya IP telephones.
4.4 Delay Measurement Results

Using the Agilent VQT for delay measurement, the following delay results were obtained
by Michael Kloberdans for a uni-directional voice path between two IP telephones (the
network delay is less than 1 msec):
Delay (msec)
Voice Path Routing G.711 Codec G.729 Codec
Shuffled 71.7 99.6
TDM-bussed 125.9 180.7
Table 1: Unidirectional Delay Measurement Results
In case of shuffled voice paths, the delay is primarily due to the packetization in the
transmitting IP telephone and the unpacketization in the receiving IP telephone. For TDM
bussed calls (ip-direct) the Prowler adds a significant unpacketization and packetization
delay as well.
4.5 Acoustic Echo on IP Telephones and Voice Path Routing

An acoustic echo return could be generated on an IP telephone, an IP telephone in
speakerphone mode, or on a headset connected to an IP telephone. As mentioned earlier,
11

the current Avaya telephones do not facilitate echo cancellation. However, an echo
suppression facility (not echo cancellation) is provided on the headset port. This section
attempts to create some awareness with respect to the consequences of the absence of
echo cancellation in the IP telephones.
The unidirectional delay numbers provided in Table 1 for shuffling (see e.g. Figure 6) are
as good as equal to the acoustical echo return delay between the IP input and output ports
of the IP telephone, see Figure 5. Thus, if an echo canceller would be provided in the IP
telephone (note that it is not provided at this moment), the echo cancellation would have
to be at least 71.7 msec with a G.711 codec and 99.6 with a G.729 codec to remove
acoustic echoes.
Suppose no echo canceller is provided in the IP telephones and TDM-bussed voice path
routing is deployed (see e.g. Figure 11A and Figure 13A). In order to remove the acoustic
IP telephone echo, the echo cancellation tail on the Prowler should be at least equal to:
125.9 msec with a G.711 codec in the IP telephone and Prowler.
180.7 msec with a G.729 codec in the IP telephone and Prowler.
IP Telephone Codec TDM Bus

Prowler
IP LAN/WAN (delay assumed to be 0)
Acoustic echo from Codec
handset, headset, or
speakerphone mode
Roundtrip Delay through Phone: Roundtrip Delay through Phone:

71.7 msec with G.711 Codec 125.9 msec with G.711 Codec
99.6 sec with G.729 Codec 180.7 sec with G.729 Codec
Figure 5: Acoustic Echo Return Delays
These minimally required echo cancellation tail numbers do not even take into account
the additional length needed to compensate for the delay of the LAN between the IP
telephone and the Prowler. The minimal needs differ significantly from the currently
provided 16 msec echo cancellation tail on the Prowler. The current 16msec echo
12

cancellers on the Prowler are intended to eliminate echo caused in an Analog, DCP or
PSTN telephone, or somewhere in a LEC/IXC network and not for cancelling acoustic
echo returns caused by an IP telephone.
In summary, thus it can be concluded that:

If the voice path is shuffled or hairpinned, currently no echo cancellation is
provided between the IP telephones.
If the voice path is TDM-bussed, the currently provided echo cancellers on the
Prowler with their 16 msec echo cancellation tail are therefore not sufficient to
remove any acoustic echo from the IP telephone.
Turning a shuffled or hairpinned voice path into a TDM-bussed voice path
does not remove any acoustic echo from the IP telephone since the echo
cancellation tails of the Prowler are not long enough.
5 Symptom Resolution Procedure

In this symptom resolution procedure it is assumed that only one of the parties on a call
experiences echo. The procedure can also be applied to the case where both parties
experience echo.
To diagnoze echo problems properly, ideally some knowledge is available of the type of
call and network equipment in the voice path:
The types of telephones involved in a call.
Local calls verses long distance calls: long distance calls could exacerbate the
perception of echo.
The types and numbers of intermediate networked systems that the voice signal
traverses. Routers and firewalls could substantially add to the voice path delay.
In the resolution procedure described below, the ping command is used to measure
network delay. In general, routers forward these command and their replies at the lowest
priority. Therefore, they cannot accurately measure network delay in congested networks
that prioritize traffic. In the future, the delay and echo-location measurement capabilities
in DEFINITY, the telephones and other Avaya voice equipment migth be upgraded to
with better diagnostic capabilities such as RTCP measurements.
1. Please fill out the Echo Incident Report Form. This will help us to improve
the Avaya product line.
Go to step 2.
2. Has a network assessment ever been done and has the network not been
modified after the assessment?
Y. Ideally, the network should operate within the specifications. Possibly
a high network load may be causing the echo problem. Go to go to
13

step 3 for further analysis.
N. The network may not be compliant with the Avaya’s network
requirements. If the problem cannot be resolved by using the steps
described below, a (re-)assessment may need to be done, go to step 3
for further analysis.
3. Do other calls on the same VLAN/subnet/floor/campus experience the same

problem (see the Call Symptom Resolution Strategy Note for possible
patterns)?
Y. There may be a network problem or (if in the voice path) a DEFINITY
shared resource problem. All possibilities need to be explored, go to
step 4.
N. It looks like a call specific problem. Go to step 4.
The next two steps record some of the items in the Your Information and Far-End
Information in the Echo Incident Report Form.
4. Determine the types of telephones that are involved in the call.
Check this by asking both parties involved in the call what types of telephones
they are using. This could be:
An AT&T/Lucent/Avaya IP, DCP, Analog, or DCP telephone.
An Avaya IP soft-phone running on a pc/laptop used with a:
o Headset.
o A separate microphone and a set of speakers,
o An integrated microphone and set of speakers as in a laptop,
o A separate microphone and an earpiece.
The first three cases are notorious for creating echo problems and can
only be resolved by installing an echo cancelling line card, or by using
higher quality equipment (such as a better headset). Try either of the
two possibilities first. This will likely resolve the echo problem.
A speakerphone that is either part of a desktop telephone or a separate

physical device.
A PSTN telephone.
A wireless telephone.
Other, e.g. a Cisco/Nortel IP telephone.
Go to step 5 if the problem was not resolved.
5. Determine how the telephones are used in the call. This only needs to be
determined if analog/DCP telephones are involved in the call (see Figure 4).
14

Check this by asking both parties involved in the call:
If the telephone is used in speakerphone mode.
What the setting of the audio-level control is (if any). A high setting
may create a high echo return level.
If a telephone is connected to a fax machine.
If a fax machine is connected to a port on the telephone. If this is the
case,
If a headset is used on a DCP telephone.
If multiple analog telephones are connected to the same cable.
If a MCK extender device is used to allow DCP telephones and PCs to
share bandwidth on the same link to a central office.
These cases are notorious for creating echo problems and can only be resolved by
a) reducing the audio-control level, b) by installing an echo cancellation line card,
or c) by using higher quality equipment (such as a better headset). Try these
possibilities first as they will likely resolve the echo problem.
Go to step 6 if the problem was not resolved.
The next step records the Call Information in the Echo Incident Report Form.
6. Get a first impression of the network that the voice path traverses:
Check if the voice path:

Traverses the local in-building/on-campus network, or any wide-area
(circuit-switched/IP/FR/ATM networks (ATM = Asynchronous Transfer
Mode, FR = Frame Relay)).
Traverses a LEC network.
Traverses an IXC long distance network.
Some of this can be verified by asking:

Where the call parties are phyically residing.
If the telephone number that was dialed included a LEC or IXC code.
If abbreviated dialing was used. XXXX
Keep this information in mind for the determination below of the potential
network configurations that the voice path may traverse.
Go to step 7.
The next step records the Echo Information in the Echo Incident Report Form.
7. Determine which of the call parties experiences the echo on which telephone:
Ask the parties involved in the call whom experiences the echo (one party or both
15

parties and which type of telephone is used. This provides an indication of the
echo return point and the direction of the echo return signal.
Go to step 8.
8. Get a better impression of the network that the voice path traverses:
Note: At least one of the telephones in the call should be registered with a
DEFINITY. The other telephone may or may not be registered with a DEFINITY.
For instance, a PSTN telephone will not be registered with a DEFINITY.
Check on all of the DEFINITY’s that may be involved in the call the voice path
routing modes that are set:
i. Execute the ‘status station extension # ’ command for the one/both
telephones involved in the call.
ii. Go to page 3 titled “Call Control Signaling”. Under “Audio
Connection Type, if it is marked:
a) “ip-direct”, then it is shuffled.
b) “ip-hairpin” it uses Prowler resources, but the voice path
does not go via the TDM bus. The voice path does not
traverse an echo canceller on the Prowler.
c) “ip-tdm”, then the voice path goes via the TDM bus. The
voice path traverses an echo canceller on the Prowler.
Matt: a), b), c) is incorrect?? I think this needs to be changed (also in other SRN)
---how do I know that if both station forms indicate shuffling that the voice path is
still forced through the TDM bus (e.g. because they terminate on different Prowlers.
Use this information together with the station form matching rules provided in
section 3 to determine the voice path routing type that may be used. Also consult
Table 2 and Table 3 and determine, together with the information obtained in the
previous steps:
The most likely network configuration that the voice path traverses.
If any echo canceller is operating towards the telephone where the
echo is experienced.
If the echo cancellers operate near-end or far-end.
The echo cancellation tail of the echo cancellers operating in the
direction of the telephone where the echo is experienced.
Go to step 9.
Note that not all possible voice path network configuration are illustrated in the figures in
section 6. In particular the following cases where the voice path traverses network
configurations such as:
16

EPN-CCS-EPN switch - LEC/IXC network, and R300-EPN-CCS-EPN -
LEC/IXC network configurations.
All cases of analog trunking and combinations of analog and digital trunking to a
LEC network.
Some cases of calls to the PSTN network.
Voice paths covering Frame Relay networks. These network configurations look
very similar to the ones provided with local/wide-area ATM networks.
These network configurations can easily obtained by enhancing the LEC/IXC figures.
Note that in the figures all the indicated echo cancellers are assumed to be
operational. Although not explicitly mentioned, this should be checked first on the
DEFINITY/R300 pages XXX before any other actions are taken.
Notes:
In the future, the case of IP telephones on CHAWK may need to be added.
The following description has been written under the assumption that the IP
telephone does not provide echo cancellation. This description may have to be
modified in the future after echo cancellation has been added.
Telephones Type of Voice Path Figure Go to Step

Shuffled Figure 6A 9
Hairpinned Figure 8A 9
Single Prowler Figure 11A 10
Dual Prowler Figure 13A 10
IP - IP CCS Figure 18 10
TDM - Bussed PSTN LEC Figure 21 11
PSTN LEC/IXC Figure 29 11
ATM LAN/WAN Figure 32 12
IP LAN/WAN Figure 35 13
IP- Analog Shuffled 14 if echo heard on IP telephone
or
Figure 6B 15 if echo heard on Analog/DCP
IP - DCP Hairpinned 14 if echo heard on IP telephone
Figure 9C 15 if echo heard on Analog/DCP
14 if echo heard on IP telephone
TDM - Bussed Single Prowler Figure 11B 16 if echo heard on Analog/DCP
Dual Prowler Figure 14C 16 if echo heard on Analog/DCP
CCS Figure 19 18 if echo heard on Analog/DCP
Figure 23 20 if echo heard on Analog/DCP
PSTN LEC
Figure 24 18 if echo heard on Analog/DCP
PSTN LEC/IXC Figure 30 20 if echo heard on Analog/DCP
ATM LAN/WAN Figure 33 23 if echo heard on Analog/DCP
17

IP LAN/WAN Figure 37 25 if echo heard on Analog/DCP
Figure 25 26 if echo heard on IP telephone
27 if echo heard on PSTN phone
IP - Public TDM - Bussed PSTN LEC
Figure 26 27 if echo heard on PSTN phone
Table 2: Type of Voice Network Configuration - I
Telephones Type of Voice Path Figure Go to Step

Shuffled Figure 7C 29
Figure 8B 30
Hairpinned
Figure 10 31
Single Prowler Figure 12 30
Figure 30
13B
Analog - 32 if echo heard on top phone
Analog
Figure
14D 30 if echo heard on bottom
or Dual Prowler phone
Analog – DCP 30
or TDM - Figure 15
DCP - DCP Bussed Figure 16 31
Figure 17 31
CCS Figure 20 33
PSTN LEC Figure 27 34
PSTN LEC/IXC Figure 31 34
ATM LAN/WAN Figure 34 35
IP LAN/WAN Figure 38 36
26 if echo heard on
Analog – Public
TDM - Analog/Digital phone
or
Bussed
PSTN LEC Figure 28 37 if echo heard on PSTN
DCP - Public
phone
Table 3: Type of Voice Network Configuration - II
Note: The description below should be refined as soon as the R300 also supports IP
telephones. Then, the first case described under step 9 has more networking options.
9. Because the voice path is Shuffled/Hairpinned it has no echo cancellers in the

voice path cancelling towards the IP telephone where the (acoustic) echo is
experienced.
As described in section 4.5, turning the voice path into TDM-bussed does not help
either to remove the echo. Therefore, there are currently no provisions available to
remove the echo.
18

10. Because the call is TDM bussed, the voice path between the IP telephones goes
through one or two Prowlers. Thus, the voice path to the telephone that
experiences the echo has at least one echo canceller on a Prowler. However, as
explained in section 4.5, the echo cancellation tail of the Prowler is not sufficient
to remove the acoustic echo. Therefore, there are currently no provisions available
to remove the echo.
Note: if the voice path traverses the TDM bus, or CCS only a small delay of up to
several hundreds of microseconds is added to the voice.
through two Prowlers and two T1/E1 cards providing echo cancellation facilities.
As explained in section 4.5:
The echo cancellation tail of the Prowler is not sufficient to remove the
acoustic echo.
The round trip delay from the TDM bus through the acoustic path on
the IP telephone and back to the TDM bus is at least 125.9 msec with a
G.711 codec in the IP telephone and Prowler, and at least 180.7 msec
with a G.729 codec in the IP telephone and Prowler. Without even
taking into account the delays of the IP LAN and the PSTN LEC/IXC,
these round trip delays are too large for the 96 msec echo cancellation
tails of the echo cancellers on the T1/E1 Digital trunk cards to be
effective.
Therefore, there are currently no provisions available to remove the acoustic echo.
through two Prowlers and two ATM EI cards providing echo cancellation
facilities. As explained in section 4.5:
The echo cancellation tail of the Prowler is not sufficient to remove the
acoustic echo.
taking into account the delays of the IP LAN and the PSTN LEC/IXC,
these round trip delays are also too large for the 8 msec echo
cancellation tails of the echo cancellers on the ATM EI trunk cards to
be effective.
19

through four Prowlers in total each providing echo cancellation facilities. As
explained in section 4.5:
The echo cancellation tail of a Prowler (at the left side of the figure) is
not sufficient to remove the acoustic echo from the IP telephone.
taking into account the delays of the IP LAN and the IP LAN/WAN,
these round trip delays are too large for the 16 msec echo cancellation
tails of the echo cancellers on the Prowler trunk cards (at the right side
of the figure) to be effective.
14. It could be that the echo cancellation provided by the R300 is not operational.
--Check with Matt, if there is something better
Escalate the problem to the next Avaya Maintenance Support Tier with all the
information gathered so far (including the Echo Incident Report and the network
configuration determined) since there may be an R300 problem.
15. Because the voice path is Shuffled/Hairpinned it has no echo cancellers in the
voice path cancelling towards the analog telephone where the acoustic echo is
experienced.
As described in section 4.5, turning the voice path into TDM-bussed does not help
either to remove the echo. Therefore, there are currently no provisions available to
remove the echo.
16. Because the call is TDM bussed, the voice path goes through one Prowler. Thus,
the voice path to the telephone that experiences the echo has at least one echo
canceller on a Prowler. However, as explained in section 4.5, the echo
cancellation tail of the Prowler is not sufficient to remove the acoustic echo
caused by the IP telephone. Therefore, there are currently no provisions available
to remove the echo.
17. It could be that the echo cancellation provided by the Prowler is not operational.
configuration determined) since there may be a Prowler problem.
20

18. The acoustic echo caused by the IP telephone cannot be removed since there is no
echo canceller present in the voice path from the IP telephone to the Analog/DCP
telephone.
19. The T1/E1 Digital trunk card (at the top of the figure) provides a 96msec echo
canceller that could cancel the acoustic echo caused by the Analog/Digital
telephone or by the Analog line card. It could be that the echo cancellation
provided by the Prowler is not operational.
configuration determined) since there may be a T1/E1 Digital trunk card problem.
20. The T1/E1 Digital trunk card (at the bottom of the figure) provides a 96msec echo
canceller that potentially could cancel the acoustic echo caused by the IP
telephone. However, as explained in section 4.5, the echo cancellation tail of this
echo canceller is not suffient to remove the echo. Therefore, there are currently no
provisions available to remove the echo.
21. The Prowler card provides a 16 msec echo canceller that could cancel the acoustic
echo caused by the Analog/Digital telephone or by the Analog line card. It could
be that the echo cancellation provided by the Prowler is not operational.
22. The ATM EI trunk card (at the bottom of the figure) provides a 8 msec echo
canceller that could cancel the acoustic echo caused by the Analog/Digital
telephone or by the Analog line card. It could be that the echo cancellation
provided by the Prowler is not operational.
configuration determined) since there may be a ATM EI trunk card problem.
23. The ATM EI trunk card (at the top of the figure) provides a 8msec echo canceller
21

that potentially could cancel the acoustic echo caused by the IP telephone.
However, as explained in section 4.5, the echo cancellation tail of this echo
canceller is not suffient to remove the echo. Therefore, there are currently no
24. The Prowler card (at the bottom of the figure) provides a 16 msec echo canceller
that could cancel the acoustic echo caused by the Analog/Digital telephone or by
the Analog line card. It could be that the echo cancellation provided by the
Prowler is not operational.
25. The Prowler card (at the top right side of the figure) provides a 16msec echo
canceller that potentially could cancel the acoustic echo caused by the IP
telephone. However, as explained in section 4.5, the echo cancellation tail of this
echo canceller is not suffient to remove the echo. Therefore, there are currently no
26. The T1/E1 Digital trunk card provides a 96msec echo canceller that potentially
could cancel the acoustic echo caused by the PSTN telephone or the LEC
network. It could be that the echo cancellation provided by the T1/E1 trunk card
is not operational or the LEC network causes a delay beyond 96msec or echoes
with an echo return delay longer than 96msec.
configuration determined) since there may be a T1/E1 trunk card problem. If the
T1/E1 trunk card is not the cause of the problem, then the LEC should be
contacted to reduce the delay, or echo return delay.
27. The acoustic echo caused by the IP telephone or the LEC network cannot be
removed since there is no echo canceller present in the voice path from the IP
telephone to the Analog/DCP telephone.
28. The Prowler card provides a 16msec echo canceller that potentially could cancel
the acoustic echo caused by the PSTN telephone or the LEC network. It could be
that the echo cancellation provided by the Prowler card is not operational or the
LEC network causes a delay beyond 16msec or echoes with an echo return delay
longer than 16msec.
22

configuration determined) since there may be a Prowler card problem. If the
Prowler is not the cause of the problem, then the LEC should be contacted to
reduce the delay, or echo return delay.
29. It seems that the R300 causes an exorbitant delay. Check the operation of the
R300 to determine the problem.
30. It seems that the R300/C-HAWK causes an exorbitant delay or the echo canceller
is not operational because the 32/16msec echo canceller should be sufficient.
Check the operation of the R300/C-HAWK to determine the problem.
31. It seems that the Analog/Digital line card causes an exorbitant delay. Check the
operation of the line card to determine the problem.
32. The Prowler card provides a 16msec echo canceller that should be capable to
cancel the acoustic echo caused by the Analog/Digital telephone at the bottom, or
the electrical echo caused on the Analog line card. It could be that the echo
cancellation provided by the Prowler card is not operational.
configuration determined) since there may be a Prowler card problem. If the
Prowler is not the cause of the problem, then the LEC should be contacted to
reduce the delay, or echo return delay.
33. It seems that the Analog/Digital line card or the EI causes an exorbitant delay.
Check the operation of these card to determine the problem.
23

34. The T1/E1 Digital trunk card provides a 96msec echo canceller that potentially
could cancel the acoustic echo caused by the Analog/Digital telephone, the
Analog line card or the LEC network. It could be that the echo cancellation
provided by the T1/E1 trunk card is not operational or the LEC network causes a
delay beyond 96msec or echoes with an echo return delay longer than 96msec.
--Check with Matt, if there is something better. Could the T1/E1 echo canceller
operation be turned around? This would likely solve the problem. Also check the
other figures for this solution
configuration determined) since there may be a T1/E1 trunk card problem. If the
T1/E1 trunk card is not the cause of the problem, then the LEC should be
contacted to reduce the delay, or echo return delay.
35. The ATM EI Digital trunk card provides a 8msec echo canceller that should be
able to cancel the acoustic echo caused by the Analog/Digital telephone, the
Analog line card or the LEC network. It could be that the echo cancellation
provided by the ATM EI card is not operational. Xxhow to checkxx
36. The Prowler trunk card provides a 16msec echo canceller that should be able to
cancel the acoustic echo caused by the Analog/Digital telephone, the Analog line
card or the LEC network. It could be that the echo cancellation provided by the
Prowler card is not operational. Xxhow to checkxx
37. The acoustic echo caused by the Analog/Digital telephone, the Analog line card,
or the LEC network cannot be removed since there is no echo canceller present in
the voice path from the Analog/Digital telephone to the PSTN telephone.
24

6 Network Configurations
A The telephones
could be on
different LANs
IP LAN/WAN DEFINITY PPN/EPN
16ms
IP
Prowler
IP
TDM Bus
No echo cancellation
R300 or IP LAN/WAN DEFINITY PPN/EPN

C-HAWK
16ms
Two wire Analog 32ms
or
Digital(DCP, BRI) Prowler
IP TDM Bus
Echo cancellation: only echo from the analog or digital telephone
Figure 6: Shuffled Calls
25

C * only for analog telephones
R300 or DEFINITY PPN/EPN
C-HAWK
Two wire Analog * LAN, or

or WAN (analog, digital, FR, IP)
Digital(DCP, BRI) T1/E1 Digital,
Analog, or Prowler
Two wire Analog * TDM Bus

or
Digital(DCP, BRI)
16ms for Prowler
92ms for T1/E1
0ms for Analog
D * only for analog telephones

C-HAWK
Two wire Analog *

or
Digital(DCP, BRI) T1/E1 Digital,
Analog, or Prowler

or
Digital(DCP, BRI)
Echo cancellation in both directions of the voice path
32ms in R300 NOT Supported

16ms in C-HAWK
Figure 7: Shuffled Calls
A The telephones
could be on
different LANs
16ms
IP
Prowler
IP
TDM Bus
B
* only for analog telephones
C-HAWK
* 16ms
Two wire Analog
or

or
Digital(DCP, BRI)
32ms in R300
16ms in C-HAWK
Figure 8: Hairpinned Calls
26

C

C-HAWK
16ms
Two wire Analog *
or
IP TDM Bus
32ms in R300
16ms in C-HAWK
Figure 9: Hairpinned Calls
DEFINITY PPN/EPN
Analog Line Card

Two wire Analog
TDM Bus
Two wire Analog
DEFINITY PPN/EPN
Dig. Line Card

Digital(DCP, BRI)
TDM Bus
Digital(DCP, BRI)
Figure 10: Analog/Digital Telephone Hairpinned Like Calls
27

A The telephones
could be on
different LANs
16ms
IP
Prowler
16ms
IP
TDM Bus
B * only for analog telephones

C-HAWK
16ms
Two wire Analog *
or
16ms
IP TDM Bus
32ms in R300
16ms in C-HAWK
Figure 11: TDM Bus Calls: Single Prowler

C-HAWK
* 16ms
Two wire Analog
or
16ms

or
Digital(DCP, BRI)
32ms in R300
16ms in C-HAWK
Figure 12: TDM Bus Calls: Single Prowler
28

A IP LAN/WAN DEFINITY PPN/EPN
16ms
IP
The telephones Prowler
could be on
different LANs
16ms
Prowler
IP
TDM Bus

B
R300 or DEFINITY PPN/EPN
C-HAWK
IP LAN/WAN 16ms
Two wire Analog *

or Prowler
Digital(DCP, BRI)
16ms
Prowler
Two wire Analog *

or
Digital(DCP, BRI) TDM Bus
32ms in R300
16ms in C-HAWK Echo cancellation in both directions of the voice path
Figure 13: TDM Bus Calls: Dual Prowlers

C DEFINITY PPN/EPN
R300 or
C-HAWK
IP LAN/WAN 16ms
Two wire Analog *

or Prowler
Digital(DCP, BRI)
32ms in R300 16ms

16ms in C-HAWK Prowler
IP TDM Bus

32ms in R300
16ms in C-HAWK
D * only for analog telephones
DEFINITY PPN/EPN
IP LAN/WAN
16ms
Two wire Analog *
or R300 or
Digital(DCP, BRI)
C-HAWK Prowler
Analog or Dig
Two wire Analog Line card
or
Digital(DCP, BRI) TDM Bus
Echo cancellation in one direction of the voice path
29

E

DEFINITY PPN/EPN
IP LAN/WAN
16ms
Two wire Analog *
or R300 or
Digital(DCP, BRI)
C-HAWK Prowler
16ms
R300 or IP LAN/WAN
C-HAWK Prowler
Two wire Analog *

or TDM Bus
Digital(DCP, BRI)
32ms in R300
16ms in C-HAWK
F DEFINITY PPN/EPN
Analog Line Card
Two wire Analog
Analog Line Card

Two wire Analog
TDM Bus
G
DEFINITY PPN/EPN
Digital Line Card
Digital(DCP, BRI)
Digital Line Card

Digital(DCP, BRI)
TDM Bus
Figure 16: TDM Bus Calls: Dual Line Cards
30

H
DEFINITY PPN/EPN
Analog Line Card
Two wire Analog
Digital Line Card

Digital(DCP, BRI)
TDM Bus
Figure 17: TDM Bus Calls: Dual Line Cards
IP LAN DEFINITY PPN/EPN CCS
16ms
IP
Prowler EI
TDM Bus
IP LAN DEFINITY PPN/EPN
16ms
IP
Prowler EI
TDM Bus
Figure 18: TDM Bus Calls: CCS
31

B
IP LAN DEFINITY PPN/EPN CCS
16ms
IP
Prowler EI
TDM Bus
DEFINITY PPN/EPN
Analog or Dig
Line card
Two wire Analog

or * EI
Digital(DCP, BRI)
TDM Bus
DEFINITY PPN/EPN CCS
Analog or Dig
Line card
Two wire Analog

or * EI
Digital(DCP, BRI)
TDM Bus
DEFINITY PPN/EPN
Analog or Dig
Line card
Two wire Analog

or * EI
Digital(DCP, BRI)
TDM Bus
32

A
IP LAN DEFINITY PPN/EPN PSTN

LEC
16ms 96ms
IP
Prowler T1/E1 Digital
TDM Bus
16ms 96ms
IP
In general, no
echo cancellers
are present in a
LEC network
TDM Bus
Figure 21: TDM Bus Call: PSTN LEC with Digital Trunking

LEC
16ms
IP
Prowler T1/E1 Analog
TDM Bus
16ms
IP
In general, no
echo cancellers
are present in a
LEC network
TDM Bus
Figure 22: TDM Bus Call: PSTN LEC with Analog Trunking
33

C

LEC
16ms 96ms
IP
TDM Bus
DEFINITY PPN/EPN
Analog or Dig
Line card 96ms
Two wire Analog

or * T1/E1 Digital
Digital(DCP, BRI) In general, no
echo cancellers
are present in a
LEC network
TDM Bus
Figure 23: TDM Bus Call: PSTN LEC with Digital Trunking

LEC
16ms
IP
TDM Bus
DEFINITY PPN/EPN
Analog or Dig
Line card
Two wire Analog

or * T1/E1 Analog
echo cancellers
are present in a
LEC network
TDM Bus
Figure 24: TDM Bus Call: PSTN LEC with Analog Trunking
34

E

LEC
16ms 96ms
IP
TDM Bus
PSTN
In general, no
echo cancellers
are present in a
LEC network
Figure 25: TDM Bus Call: PSTN LEC with Digital Trunk

LEC
16ms
IP
TDM Bus
PSTN
In general, no
echo cancellers
are present in a
LEC network
Figure 26: TDM Bus Call: PSTN LEC with Analog Trunk
35

G
DEFINITY PPN/EPN PSTN

LEC
Analog or Dig
Line card 96ms
Two wire Analog

or * T1/E1 Digital
Digital(DCP, BRI)
TDM Bus
DEFINITY PPN/EPN
Analog or Dig
Line card 96ms
Two wire Analog

or * T1/E1 Digital
echo cancellers
are present in a
LEC network
TDM Bus
Figure 27: TDM Bus Call: PSTN LEC
36

H

LEC
Analog or Dig
Line card 96ms
Two wire Analog

or * T1/E1 Digital
Digital(DCP, BRI)
TDM Bus
PSTN
In general, no
echo cancellers
are present in a
LEC network
Figure 28: TDM Bus Call: PSTN LEC
A
In general, no
echo cancellers
are present in a
LEC network
IP LAN DEFINITY PPN/EPN PSTN PSTN

LEC IXC
16ms 96ms
IP
TDM Bus

LEC
16ms 96ms
IP
Prowler T1/E1 Digital Echo cancellers
may or may not
be present in an
IXC network
TDM Bus
Figure 29: TDM Bus Call: PSTN LEC/IXC
37

B
In general, no
echo cancellers
are present in a
LEC network
IP LAN DEFINITY PPN/EPN PSTN PSTN

LEC IXC
16ms 96ms
IP
TDM Bus

LEC
Analog or Dig
Line card 96ms
Two wire Analog

or * T1/E1 Digital Echo cancellers
Digital(DCP, BRI) may or may not
be present in an
IXC network
TDM Bus
C
In general, no
echo cancellers
are present in a
LEC network
DEFINITY PPN/EPN PSTN PSTN

LEC IXC
Analog or Dig
Line card 96ms
Two wire Analog

or * T1/E1 Digital
Digital(DCP, BRI)
TDM Bus

LEC
Analog or Dig
Line card 96ms
Two wire Analog

or * T1/E1 Digital Echo cancellers
Digital(DCP, BRI) may or may not
be present in an
IXC network
TDM Bus
38

A
IP LAN DEFINITY PPN/EPN ATM

LAN or WAN
16ms 8ms
IP
Prowler ATM EI
TDM Bus
16ms 8ms
IP
Prowler ATM EI
In general, no
echo cancellers
are present in an
ATM network
TDM Bus
Figure 32: TDM Bus Call: ATM LAN/WAN
IP LAN DEFINITY PPN/EPN ATM

LAN or WAN
16ms 8ms
IP
Prowler ATM EI
TDM Bus
DEFINITY PPN/EPN
Analog or Dig
Line card 8ms
Two wire Analog

or * ATM EI
echo cancellers
are present in an
ATM network
TDM Bus
39

C
DEFINITY PPN/EPN ATM

LAN or WAN
Analog or Dig
Line card 8ms
Two wire Analog

or * ATM EI
Digital(DCP, BRI)
TDM Bus
DEFINITY PPN/EPN
Analog or Dig
Line card 8ms
Two wire Analog

or * ATM EI
echo cancellers
are present in an
ATM network
TDM Bus
IP LAN DEFINITY PPN/EPN IP

LAN or WAN
16ms 16ms
IP
Prowler Prowler
TDM Bus
16ms 16ms
IP
Prowler Prowler
In general, no
echo cancellers
are present in an
IP network
TDM Bus
Figure 35: TDM Bus Call: IP LAN/WAN
40

B

LAN or WAN
16ms 16ms
IP
Prowler Prowler
TDM Bus
IP
In general, no
echo cancellers
are present in an
IP network

LAN or WAN
16ms 16ms
IP
Prowler Prowler
TDM Bus
DEFINITY PPN/EPN
Analog or Dig
Line card 16ms
Two wire Analog

or * Prowler
echo cancellers
are present in an
IP network
TDM Bus
41

D
DEFINITY PPN/EPN IP
LAN or WAN
Analog or Dig
Line card 16ms
Two wire Analog

or * Prowler
Digital(DCP, BRI)
TDM Bus
DEFINITY PPN/EPN
Analog or Dig
Line card 16ms
Two wire Analog

or * Prowler
echo cancellers
are present in an
IP network
TDM Bus
7 References
DEFINITY Hybrid Networking Echo Control, Working Draft 06/18/01. Doug

Spencer e.a.
IP Telephone FAQ
42


Voip and Echo Problems

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Voip and Echo Problems

Uploaded by

Copyright:

Available Formats

Symptom Resolution Note

Title: The user reports echo during a call

Issue: 0.8 Date: September 14, 2001

Avaya Communication – Proprietary

Prowler Media Processor board (also called MedPro TN2302AP). A

2.2 Remote Diagnostic Tools

2.3 Echo Control

Avaya Communication – Proprietary

LEC. Local Exchange Carrier. A non-long distance telephony service provider.

3 Voice Path Routing

3.1 Routing Modes

As examples, the following voice paths are all considered shuffled:

Avaya Communication – Proprietary

Avaya Communication – Proprietary

Echo may be created in two ways:

In current voice networks many possible combinations of telephones and telephone

Avaya Communication – Proprietary

Figure 1: Acoustic and Electric Echo in caused by IP Systems/Networks

Some concepts that are used to describe echo are:

Avaya Communication – Proprietary

4.2 Echo Suppression Deployment Rules

Near-End Echo Cancellation Rule. Consistently use near-end echo cancellation

This near-end echo cancellation rule should be followed because:

Avaya Communication – Proprietary

Digital Signal Addition

“Near End” Environment

Acoustical Echo Electrical Echo

Figure 2: Cancellation of Hybrid Induced Echo

IP Gateway Echo Cancellation Rule. All IP gateways should be equipped with

Several types of IP gateways can be distinguished:

Avaya Communication – Proprietary

Basic Rule for echo cancellation: Provide “Near End” Cancellation

Digital Signal Addition

“Near End” Environment “Far End”

Acoustical Echo Electrical Echo

Figure 3: Cancellation of Acoustic and Cable Echo

4.3 Echo Management in Avaya Equipment

Avaya Communication – Proprietary

Digital (DCP) Echo cancellation by

Figure 4: Overview of DEFINITY Voice Paths and Echo Cancellers

Echo cancellation in other Avaya equipment is provided as follows:

Avaya Communication – Proprietary

4.4 Delay Measurement Results

4.5 Acoustic Echo on IP Telephones and Voice Path Routing

Avaya Communication – Proprietary

IP Telephone Codec TDM Bus

Roundtrip Delay through Phone: Roundtrip Delay through Phone:

Figure 5: Acoustic Echo Return Delays

Avaya Communication – Proprietary

In summary, thus it can be concluded that:

5 Symptom Resolution Procedure

Avaya Communication – Proprietary

3. Do other calls on the same VLAN/subnet/floor/campus experience the same

4. Determine the types of telephones that are involved in the call.

A speakerphone that is either part of a desktop telephone or a separate

Go to step 5 if the problem was not resolved.

Avaya Communication – Proprietary

Go to step 6 if the problem was not resolved.

Check if the voice path:

Some of this can be verified by asking:

Avaya Communication – Proprietary

Avaya Communication – Proprietary

Telephones Type of Voice Path Figure Go to Step

Avaya Communication – Proprietary