Aastra 470 - Page 249

Operation and Maintenance
249
Aastra 470 ab R3.0
syd-0337/1.5 – R3.0 – 05.2013
Creation of instance on
backup communication
server failed
The backup communication server was unable
to create or modify a user or terminal instance
with the received configuration data.
Note:
This event message is generated by the backup
communication server.
Instance type (0: User,
1: terminal), user number or
terminal ID, date, time
Creation of instance on
backup communication
server successful
The backup communication server was able
(following one or more previous failed
attempts) to create or modify a user or terminal
instance with the received configuration data.
Note:
This event message is generated by the backup
communication server.
Instance type (0: User,
1: terminal), user number or
terminal ID, date, time
CSTA sessions back within the
licence limit
CSTA Sessions licences are now available again. Number of licences, date, time
CTI first party connection
established
The ATPC3 first-party link was (re)established User number, date, time
CTI first party Connection lost The ATPC3 first-party link was interrupted
because the cycle signal is missing.
User number, date, time
CTI third party: connection
established
The ATPC3 third-party link was (re)established Date, time
CTI third party: Connection
lost
The ATPC3 third-party link was interrupted Cause (0: Logoff, 1: missing
cycle signal), date, time
Definitive activation licence is
missing
The initial temporary activation of the commu-
nication server for a certain duration (e.g. 90
days) was started. Following this period, the
communication server switches to restricted
operating mode (see "Restricted operating
mode", page 80).
Date, time
Definitive activation licence
now in place
A licence code with a definitive activation
licence was entered.
Date, time
Dual Homing back within the
licence limit
There are now enough licences available for
registering SIP phones in the Aastra 6700i series
on a backup communication server.
Note:
This event message is generated by the backup
communication server.
Date, time
E-mail successfully sent The system has now successfully sent an e-mail.
Meaning of the parameter values in Tab. 104
Cause/action=0000, e-mail cli-
ent, additional information,
date, time
ESME reachable The LAN connection between the SMSC and
the ESME is now available
IP address, date, time
ESME unobtainable The LAN connection between the SMSC and
the ESME is interrupted
IP address, date, time
Ethernet deactivated due to
overload
The system has detected an overload on the
Ethernet interface. The interface is temporarily
deactivated.
Date, time
Event / error message Trigger condition Details