Collapse AllExpand All

17.25. FWDN - Release rerouting for network-wide call forwarding to source node Previous topic Parent topic Child topic Next topic

Feature:

Network-wide call forwarding (FWD)
Follow-me with network-wide PIN

Function:

The FWDN parameter is used in the COT of a trunk on the one hand to execute network-wide call forwarding and, on the other, to release rerouting for network-wide call forwarding to the source node. This applies to network-wide call forwarding that can arise from an A-B connection or from a consultation line prior to transfer.
If the FWDN parameter is set in the incoming, busy trunk of the called node or in the incoming busy trunk of a transit node, then the update or connection data is forwarded to the next node for execution of call forwarding until a node is found in the network which undertakes the activities for returning call forwarding in a forward direction. This can be either a transit node or the source node.
If the FWDN parameter is not set in the incoming busy trunk of the called node or in the incoming busy trunk of a transit node, then no update or connection data for executing call forwarding is forwarded to the next node. The trunk becomes the return point and takes on the control activity for the subsequent connection setup for network-wide call forwarding to the FWD destination and ensures the forward release of the connection to the B station.
The FWDN parameter should also be set as standard for the outgoing busy trunks that are seized while a connection is being set up between a calling node, a called node and the intermediate transit nodes, provided that the network protocols permit rerouting for call forwarding. This is how rerouting works for call forwarding from node B to node A and vice versa.
IMPORTANT:
Trunk parameter FWDN must not be set on the digital network interface points from a OpenScape 4000 to older Hicom 300 variants and to external systems that do not support this function!
IMPORTANT:
Trunk parameters FWDN, FNAN and CFVA may not be set, for example, in OpenScape 4000 with network couplings 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).

AMO Interrelationships:

COT Classes of Trunks:
FNAN: Enable rerouting for network-wide call forwarding to source node
FWDR: Call deflection to public CO via rerouting (France)
CFVA: Network-wide connectivity test for forwarding destination when programming an FNA/FWD forwarding destination via tie trunk circuits

Device types:

Digital CO trunk circuits, interface circuits and tie trunk circuits
For example, SOCOD, S2COD, SOCONN, S2CONN, etc.
Analog networking interface circuits and tie trunks
For example, MAINEM, SATEM

Protocol variants:

Protocols that support rerouting for call forwarding to the source node in the network:
Protocol variants
Brief description
ANALOG
Protocols for analog trunks
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
EDSGER
EDSS1 protocol for Germany
ETSI
Standard EURO-ISDN