Page 142
VoIP gateway IP400 version 5.01
Symptom
Description
Action
Calls can be set up to a
remote VoIP device,
but no voice connec-
tions are established.
The media chan-
nel can't be set
up as the two
VoIP devices do
not have a com-
mon voice codec.
• Only the media channel is
set up directly between the
two VoIP devices; all sig-
nalling connections are
operated via the gate-
keeper.
• Make sure both VoIP
devices have been cor-
rectly 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 send-
ing (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
page 100).
The gateway loses its
configuration after it
has been disconnected
from the power supply.
The configura-
tion has not been
saved in the non-
volatile memory.
• Save the configuration to
non-volatile memory after
any successful change (see
page 22).
A telephone connected
to
tel1
or
tel2
is work-
ing, but does not have
a dial tone (IP 400
only)
No route has
been defined for
this interface.
• Define at least one valid
route entry for the inter-
face concerned.
The gateway is con-
nected to the network
behind a “firewall” and
the configuration is not
working.
The firewall does
not allow any
access to the
gateway.
• In the firewall, enable the
service tcp/80 (http) for
the gateway.