Collapse AllExpand All

17.51. NOVC - No override on CO connections Previous topic Parent topic Child topic Next topic

Feature:

"Network-wide knocking/camp-on" feature
"Manual override for 40 seconds" feature
"Emergency override/forced hold" feature

Function:

The NOVC COT parameter can be used to control an incoming override via a line to a busy subscriber conducting a trunk call. The parameter only functions in conjunction with the KNOR COT parameter and is limited to subscribers within a node. It does not work on a network-wide basis.
An override via a line in whose COT the parameters NOVC and KNOR are set is only executed if the subscriber is not busy with a trunk call.
An override via a line in whose COT the parameters NOVC and KNOR are not set is always executed. Even if the subscriber is busy with a trunk call.
The COT parameter KNOR should be set for all outgoing seized lines between the overrider and the override destination and for the last incoming seized line - by means of which the override destination is reached.
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:
KNOR - Knocking/override possible
ZAND Central System Data:
ALLDATA/DATA - "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 subscriber-based features and general, non-device-dependent subscriber 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, 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)