Fusion Point Code - NEC Univerge sv8500 Manual

[4] Fusion Point Code

Assigning LOC-ID to Fusion Point Code (FPC) is necessary for Bandwidth Control in FCCS network. In
FCCS network, each Node manages Bandwidth Control individually. Each Node assigns LOC-IDs to
FPCs except for its own. So each FPC, which means all equipment or whole locations controlled by an-
other Node, is considered as single location. The figure below shows the configuration. (
figure, data for Node A are shown. Node A assigns LOC-IDs to locations in own FPC on a network ad-
dress/STN basis ( Note 2
Note 1: This figure is a simple image. As a matter of fact in this configuration, other LOC-IDs called "Dummy
Location" should be assigned. Dummy Location is set on a branch point where multiple network routes
branch off. It combines these routes into one and helps you to use Bandwidth Control more flexibly.
For more information about Dummy Location, refer to the Data Programming Manual - Business.
About LOC-ID on a network address/STN basis, refer to "Network Address" and "Station Number" in
Note 2:
this section.
Location ID=200
Node B
Location ID=1
FPC; whole locations other Telephony Server (Node B/C) controls
Location own Telephony Server (Node A) controls
FPC for Node A's own; not assigned to LOC-ID in office data of Node A
CHAPTER 2
), and assigns LOC-IDs to other FPCs.
Peer to Peer Bandwidth Control in FCCS
FPC2
IP Network
(FPC1)
VOL.1-121
IP-RELATED BASIC FEATURE PROGRAMMING
FPC3
Node C
Location ID=0
Node A
) In this
Note 1
Location ID=300