17.14. CFVA - Enable connectivity validation for call forwarding destinations in
network 
Feature:
Check call forwarding and call forwarding no answer destinations for connectivity
during
programming
Function:
When programming an external destination for call forwarding or call forwarding no
answer,
a check is made in the node of the destination to ensure that it can be reached. A
signal
connection (D channel) to the selected FWD or FNA destination is set up for this
purpose.
To ensure that the connectivity check on the FWD or FNA destination is not only carried
out
locally, but also network-wide, the trunk parameter CFVA must be activated on all
outgoing
seized trunks - beginning in the source node and ending in the last transit node before
the
destination node.
IMPORTANT:
Trunk parameter CFVA may only be administered on trunks whose
protocols, including the message elements for the connectivity check, can be transferred
from FWD or FNA targets. For example, the trunk parameters CFVA, FWDN and FNAN
in the OpenScape 4000 must not be set on the network links with external systems without
rerouting function for call forwarding, CORNET with HICOM 100, CorNet NQ with ATM,
Ethernet,
....MUX... in transfer networks and on the system connection due to undefined T reference
point functions (network side).
If the FWD or FNA destination in the remote node can be reached, then the name and
classes
of service of the FWD or FNA destination are made known in the response to the programming
device.
If the signaling line does not reach the FWD or FNA destination because the trunk
parameter
CFVA is not set on an outgoing tie trunk circuit or interface line to be seized, then
the
name and class of service of the selected route is sent to the programming device.
IMPORTANT:
A diversion destination can be reached if the destination to be
checked contains a calling number loden entry, if the class of service FWDBAR (device
cannot
be programmed as destination for call forwarding or call forwarding if no answer)
is
deactivated and if the NOCFW switch is set to "NO" in the central system data of the
destination node. A diversion destination can be reached if the destination to be
checked contains a calling number loden entry, is ready to operate and is not in malicious
call tracing state, if the class of service FWDBAR (device cannot be programmed as
destination for call forwarding or call forwarding if no answer) and do-not-disturb
is not
activated and if the NOCFW switch is set to "YES" in the central system data
of the destination node.
AMO Interrelationships:
ZAND Central system data
|
NOCFW
|
Check the "connectivity" of a FWD or FNA destination when programming
|
COT Classes of Trunk parameter
|
FWDN
|
Enable rerouting for network-wide call forwarding to source node
|
|
FNA:
|
Enable rerouting for network-wide call forwarding to source node
|
COS Classes of Service:
|
NOCFW:
|
No call forwarding. This class of service protects a device from being programmed
as the destination for call forwarding.
|
Device types:
Digital interface circuits and tie trunk circuits
SOCONN, S2CONN
Protocol variants:
Protocols that support a connectivity test for the forwarding destination when programming
an FNA/FWD destination via tie trunk circuits:
|
Protocol variants
|
Brief description
|
|
CORNV2
|
Cornet protocol
|
|
CORNV2R
|
Cornet protocol
|
|
CORNV3
|
Cornet protocol
|
|
CORNV3R
|
Cornet protocol
|
|
CORNV33
|
Cornet protocol
|
|
CORNV33R
|
Cornet protocol
|
|
ECMA1
|
ECMA QSIG V1 protocol
|
|
ECMA1R
|
ECMA QSIG V1 protocol
|
|
ECMAV2
|
CorNet-NQ Issue 2.1 Dec. 96 Basic ETSI
|
|
ECMAV2R
|
QSIG ETSI ETS 300 172 3rd. with SS 2nd.
|
|
PSS1V2
|
CorNet-NQ Issue 2.1 Dec. 96 Basic ISO/IEC
|
|
PSS1V2R
|
QSIG ISO ISO/IEC 11572 2nd. with SS
|