ASCOM I62 - Page 72

TD 92675GB
10 January 2011/ Ver. A
Configuration Manual
Ascom i62 VoWiFi Handset
67
Voice only The handset is configured to
use both a gatekeeper and an
IMS2, but has lost contact
with the IMS2.
1) Check the IMS2 address.
Try to ping the IMS2 from
another PC.
2) Remove i62 handset from
DP1. When connected to the
WinPDM via USB on the
Desktop Programmer (DP1),
the handset cannot connect
to the IMS2 and may then
show “Voice only”.
3) If messaging is not used in
the system, verify that the
IMS2 address is configured to
0.0.0.0.
Messaging only The handset is configured to
use both a gatekeeper and an
IMS2 but has lost contact with
the gatekeeper.
1) Check the Gateway
address. Try to ping the
gateway from another
wireless client.
2) Try to send a message. The
idle connection check interval
to the IMS2 is much longer
than to the gateway.
Sometimes when all network
connection is lost the handset
will show “Messaging only”
for quite some time, because
it discovers it has lost
connection to the gateway
much faster than it discovers
loss of connection to the
IMS2. In this case the i62 will
eventually change to “No
access”.
3) If the handset is supposed
to use Gatekeeper discovery,
verify that the configured
Gatekeeper IP address is
0.0.0.0.
4) Check the Endpoint
number and the Endpoint ID.
If both are configured, they
MUST match the Endpoint ID
and Endpoint number
registered in the IP PBX. Clear
the Endpoint ID.
SERVICE NEEDED
Parameters corrupt
Note: This display message is
only shown in English.
Faulty handset. Select the reset option on the
middle soft key. If this is not
available or the problem
persists send the handset for
service.