Feature:
"Network-wide override/camp-on" feature
"Manual override for 40 seconds" feature
"Emergency override/forced hold" feature
Function:
The KNOR COT parameter is used to enable "override and camp-on specific features"
throughout the network.
KNOR set: The activation signal for executing the "override/camp-on in network"
function is forwarded to the next node. The activities for executing the feature are
delegated to the partner node.
COT parameter KNOR should be set on all relevant trunk interfaces throughout the network,
in which override/ camp-on should be enabled.
KNOR not set: The activation signal for executing the "override/camp-on in
network" function is not forwarded to the next node. The feature is already rejected
in the
user's own node.
IMPORTANT:
The IBSY (intercept when busy) parameter must not be set on main system
trunks if KNOR (trunk with knocking/override) is set in the remote station.
AMO Interrelationships:
COT Classes of Trunks:
NOVC ... No override on CO connections
ZAND Central System Data:
ALLDATA/ ATA - 'Override' group .... e.g. OVRMST Override in multiple states
FEASU Features in the SWU:
OVR .... A station with override/camp-on authorization can override/camp-on at a busy
station terminal during a call
FRKN .... Free to knock for digital stations
SDAT Administration of station-based features and general, non-device-dependent station
data:
Overrider: OVR .... Knocking override and KN Knocking/call waiting
Knocking override destination: RKNOVR .... Override/camp-on rejection may not be set
COS Classes of Service:
AUTOV .... Automatic override, China
RKOABS .... Reject knocking/override absolute may not be set for the override/knocking
destination
Device types:
Analog networking trunks: For example, SATLPNW, MAINVFSS, SATVFSS, ITT2, ITT4,
ITTIC, MAINEM, SATEM
Digital tie trunk circuits and interface circuits: For example, SOCONN, S2CONN
Protocol variants:
For example, ANALOG, CORNV33, ECMAV2 (CorNet-NQ Issue 2.1 Dec.96 Basic ETSI), PSS1V2
(CorNet-NQ Issue 2.1 Dec.96 Basic ISO/IEC)