NEC Univerge SV9100 Manual page 498

Issue 2.0
SV9100 Networking Manual
With the T-1 CCTA blade is supported in the primary system and/or

secondary systems.
When using Mobile Extension in a NetLink Network, the ISDN/PRI

must be used in the Primary System.
InMail is supported in a NetLink network; however, replication should

be scheduled for non-peak hours of operation.
InMail is supported for centralized voice mail in a KTS to KTS CCIS

network.
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.
Assigned SIP trunk ports will be cleared after establishing NetLink.

The following programs no longer replicate and can be set on a per

system basis: PRG10-23, 10-37, 21-19, 84-13, and 84-14.
When using multiple SIP trunk carriers, programs 10-28, 10-29, 10-

30, and 10-23 will have to be set at each system via WebPro or
PCPro (does not replicate). Program 10-68 can be accessed via
system ID.
When using multiple SIP trunk carriers, Program 51-19 must be

enabled for extensions on a secondary system to use CPN
information from program 21-19.
When using multiple SIP trunk carriers, SIP trunk CODEC setup must

be done from each system (does not replicate).
When using multiple SIP trunk carriers, SIP trunk basic setup must be

done from each system (does not replicate).
Registered SIP trunks can be utilized by any system in the NetLink

network, as long as trunk route programming allows it.
When using InMail in a CCIS or Netlink network, 8-digit extensions

and mailboxes are not supported.
When using Set Relocation, and a terminal is re-located from one

physical system to another physical system, route programming must
be made accordingly for 911 calls.
FoIP (Fax over IP) is supported in a NetLink Network.

For a network to be suitable for VoIP it must pass specific

requirements. To ensure the site meets these requirements, an IP
ready check and a site survey must be completed at each site before
VoIP implementation.
One-way delay must not exceed 100ms

Round Trip delay must not exceed 200ms

Packet loss must not exceed 1%

10-11