EasyManua.ls Logo

NEC Univerge SV8100 - Chapter 4 Maintenance; Numbering Plan; Operator; Features Not Suitable for this Configuration

NEC Univerge SV8100
150 pages
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Issue 2.00 UNIVERGE SV8100
A - 4 SV8100 System Design Considerations
b. If the trunks are distributed
i Each system with trunks must have the DDI table maintained
ii . No Central SMDR
iiii. In order to avoid a bottle neck in the 128 IPLA resource no more
than 128 trunks at each node.
c. Incoming trunks calls cannot be routed either analogue or DDI to Ring
groups
3.2 Maintenance
a. PC Pro session required for each system
b. Alarm report is separate for each system (each system PCPro, or sent
via email)
c. Moving extension from system to system will be difficult because of
numbering plan limitations
d. All of the data must be duplicated each time there is a change, for
example if a toll restriction number is added it must be added to 10
nodes. Not possible to copy data between the different PC pro
sessions.
3.3 Numbering plan
a. With e.g. 10 Nodes there will need to be 10 independent numbering
plans (5 digit numbering plan).
3.4 Operator
a. The Centralised operator using the DSS Console cannot view the
status of all the extensions due to limited number of
buttons.Centralised BCT operator is not supported via FeatureNet as
OAI and CTI is not supported on FeatureNet
3.5 Features not suitable for this configuration
a. Park Hold : In practice, there will be not enough park hold locations to

Table of Contents

Other manuals for NEC Univerge SV8100

Related product manuals