SYSTEM CONFIGURATION
System Considerations
3.4.2Central Office Incoming Call (Ring Down)
Each node can specify a terminating node for Ring Down calls using the system data. In this example, Node A and Node D specify Node C and Node E as the terminating node respectively. The terminating node is assigned using the ASYDL command (SYS 1, Index 640). Note that
Note 1: When assigning the data regarding the call termination to ATT, be sure to develop the unified data at each node.
Note 2: Terminating node cannot be assigned differently at each tenant (TN).
Note 3: When the connection routes (C_RT) are all busy, any attempted call via C.O. Line is not connected to the ATT. As a result, the calling party is provided with the Ring Back Tone (RBT), and even when a C_RT later becomes idle, the RBT connection is still maintained and the C.O. call does not terminate to the ATT.
ASYDL - Node A | PSTN |
| PSTN | ASYDL - Node D |
|
|
|
| |
Index 640 |
|
|
| Index 640 |
FPC = 3 (Node C) |
|
|
| FPC = 5 (Node E) |
Node providing ATTCON/DESKCON | Node A | Fusion Network |
| Node providing ATTCON/DESKCON |
|
| |||
| Node D |
| ||
| FPC = 1 |
|
| |
Data Programming (Node A) |
| FPC = 4 | Data Programming (Node D) | |
|
| |||
| Ring Down Call | Node B | Ring Down Call | |
|
| |||
|
|
| ||
| Node C |
| Node E |
|
| FPC = 3 |
|
| |
|
| FPC = 5 |
| |
|
|
|
| |
ASYDL - Node C | Ring Down Call |
|
|
|
| PSTN |
|
| |
|
|
|
| |
Index 640 |
|
|
|
|
FPC = 3 (Node C) |
|
|
| : Node having ATTCON |
|
|
|
| |
|
|
| : Node w/o ATTCON | |
Data Programming (Node C) |
|
|
|
|
Figure 3-18 Ring Down Calls on a Fusion Network
CHAPTER 3 |
Page 26
Revision 3.0
