Restrictions - NEC Univerge SV9100 Manual

Issue 2.0





6.1
SV9100 Networking Manual
SV9100 to SV9100 or NEAX PBX (SV9300, SV9500, etc.), IP terminal to IP
terminal via Peer-to-Peer, the IP Terminals' CODEC must match and the packet size
is auto negotiated.
SV9100 to NEAX PBX (SV9300, SV9500, etc.), IP terminal to TDM via Peer-to-
Peer, the IP Terminal's CODEC and packet size (PRG 84-24-XX) need to match the
NEAX PBX CCIS CODEC and packet size settings.
Any calls across CCISoIP (station to station or stations transferring trunks) that use
Quick Transfer to voice mail will require an extra CAP key. The initial call across the
CCISoIP link will use the first CAP key and when the digit 8 is pressed, to perform
the Quick Transfer, a second CAP key is accessed.
Verified Account Codes for Toll calls across a CCIS network will not be restricted
when a trunk access code is added to the number to allow ARS routing through
another K-CCIS T1/IP networked site. This access code (typically a 9) precedes the
dialed "1" which is used by the system to identify a LD call. As a result the call is no
longer considered LD and the account code will not be required.
All IP trunks (SIP, CCIS, or H.323) must be contiguous. If any IP trunks are added to
a system that already has IP trunks installed, and the next set of trunks is not
contiguous, then all IP trunks are moved to a new set of contiguous trunk numbers.

Restrictions

Call Forward Busy No Answer must be disabled for a phone to receive a CCIS

Call Back request.
The UNIVERGE SV9100 can send billing information to a billing center office

(NEAX2000/2400/SV9300), but it cannot receive the billing information as the
billing center office.
Voice Calls – K-CCIS, voice announce is not supported for a forwarded call

across IP K-CCIS to NEAX.
Not all data networks are suitable to support Voice over Internet Protocol (VoIP).

A good VoIP solution requires a low-latency, low jitter and low packet loss
network. Accordingly, a network must be evaluated for latency, packet loss, and
jitter to qualify and determine if it can provide toll-quality speech paths.
The GPZ-IPLE can support up to 256 VoIP resources dependent on the number

of VoIP Channel Licenses installed on the GCD-CP10 which may be configured
to support SIP MLT, 3rd Party SIP Stations and Trunks or IP K-CCIS
Applications.
A GCD-CP10 license is required for IP K-CCIS trunks.

A GCD-CP10 license is required for SIP Clients to include SIP stations and SIP

trunks.
The GPZ-IPLE daughter board may configure VoIP DSP usage criteria with

SV9100 Program 10-19-01 DSP Resources. Each GPZ-IPLE can flag individual
DSP resources as:
IP Ext – IP Extensions (includes SIP MLT Station or 3rd Party SIP Stations)
■
SIP Trk – SIP Trunks
■
5-45