Specifications
TD 92326GB
2009-03-10 / Ver. E
Installation and Operation Manual
VoIP Gateway
164
Appendix B: Troubleshooting
In our experience, some problems occur more frequently than others. These problems are
listed in the table below, which also gives advice on how to solve them.
Symptom Description Action
The VoIP Gateway does not
respond. The “ready”,
“link” and “act.” LEDs are
permanently on.
The VoIP Gateway is
waiting for a firmware
download.
Perform a quick reset by pressing
the Reset button.
The VoIP Gateway does not
respond. “ready” LED is on,
“link” LED is off.
The Ethernet connection
is not working.
Check the Ethernet cabling.
The VoIP Gateway does not
respond. The “ready” and
“link” LEDs are on; the
“act.” LED flashes during
attempted access.
The VoIP Gateway's
configured IP address is
incorrect.
Configure the IP parameters
correctly.
As delivered from the
factory, the VoIP Gateway
does not assign the PC an IP
address.
The DHCP client is active,
once the equipment is
turned on.
Press the Reset button briefly.
Have the PC assigned an IP
address again.
Incoming calls are received
properly, but call back is not
possible from the call list of
the telephones in use.
The “Calling Line ID” is
incomplete, because the
exchange line access
code is missing.
Configure the trunk line access
code for the interface where the
call arrives, see 21.3
Manipulation of a Calling
Number (CLI) on page 146, or
activate the “automatic CLI
correction” see 21.4 Automatic
Correction of all Calling Numbers
on page 146.
Calls can be established to
a remote VoIP device, but
no communication is
possible.
The required bandwidth
for the voice data stream
is not available.
Configure a more efficient
speech coding scheme for the
remote gateway, see Packet size
on page 138.
Calls can be set up to a
remote VoIP device, but no
voice connections can be
established.
The media channel can't
be set up as the two VoIP
devices do not have a
common voice codec.
Make sure that the “exclusive”
checkbox is deactivated, see
19.1.5 Voice Transmission on
page 137.
Calls can be set up to a
remote VoIP device, but no
voice connections are
established.
The media channel can't
be set up as the two VoIP
devices do not have a
common voice codec.
Only the media channel is set up
directly between the two VoIP
devices; all signalling connections
are operated via the gatekeeper.
Make sure both VoIP devices
have been correctly configured
for IP routing, particularly the
subnet mask and standard
gateway.
Calls to a remote telephony
gateway are constantly
rejected.
The gateway does not
support overlapped
sending (single digit
dialling).
Add a hash (#) to the dial prefix
of the route leading to this
gateway in order to force en-bloc
dialling, see 21.12 Enforce en-
bloc dialling on page 150.