NEC Univerge SV9100, Manual

Page: 537 / 766

Issue 2.0
10-50 SV9100 NetLink
5. When the communication servers come up, the Primary System and Secondary
Systems are connected and start working.
6. For database synchronization, wait three minutes (or more).
S
ECTION
17 N
ET
L
INK
M
ULTI
-SIP C
ARRIER

When the Secondary NetLink system calls out using its own SIP Trunk, no
DSPs are used from the Primary system.

The NetLink Nodes which have their own SIP trunks can use Register IDs
independently of each other. A Secondary NetLink system is able to utilize its
own SIP trunks independently to the Primary system.
Conditions

When Programming SIP Trunks on a secondary system only SIP Profile
One can be utilized.

It is possible to set Register ID for trunks that belong to that specific
system. For example, a Register ID set in the Primary system cannot be
assigned to a trunk in the Secondary system. The allocation of the trunk
and Register ID of Program14-12 must be in the same system.

In order to use CPN in a Secondary system, Program 51-19 must be
turned on for those extensions. Once enabled, CPN may be sent on a
per station basis using Program 21-19.

Each NetLink system can use either SIP trunks to a provider or SIP
trunk TIE line mode, but not both.

Once NetLink is established, PCPro or WebPro must be used to change
the system data related to the SIP trunks.

Any SIP trunks that are built in a system before establishing NetLink will
be deleted after establishing NetLink.

SIP trunks are assigned in the order of system set up. System ID's are
needed to assign Program 10-40 data.

Registered SIP trunks can be utilized by any system in the NetLink
network, as long as trunk route programming allows it.

When a Secondary system becomes the primary after fail over, the SIP
trunks will work for the effective license time.