Abc-F Ip Trunk Group; Sip - Alcatel-Lucent OmniPCX Enterprise Manual

INSTALLATION PROCEDURE FOR VERSION
J1.410.34.c – RELEASE 10.0
1 An increase of the time from beginning to end.
2 Any loss of package means that larger quantity of information is lost, involving a faster
degradation of the voice.
− Jitter buffer.
Up to Release 9.0, the jitter buffer was managed by default in static mode with a buffer depth of
100 ms. As for Release 9.1, the default mode is changed with the use of the dynamic mode
together with a buffer depth of 300 ms. These new settings will help to avoid any packets
accumulation on one side after a jitter burst. They will also allow storing more packets and then
accept a more important jitter.
8.

ABC-F IP TRUNK GROUP

When creating the ABC-F IP trunk group, the Homogeneous network for direct RTP
parameter must be set to Yes if each node of sub-network located behind the ABC-F IP trunk group
is in R9.0 or higher. If one of the nodes of remote sub-network is in version less than R9.0, the
parameter must be set to No.
If the sub-network, located behind the ABC-F IP trunk group, has a QSIG trunk group, the
Homogeneous network for direct RTP parameter must be set to No.
It is not possible to have both on a same node a ABC-F (IP or not) trunk group and a DPNSS trunk
group.
The ongoing communications on an ABC-F IP trunk group are not maintained in case of Call Server
switch-over. This limitation is removed as of Release 9.1.
There is no encryption of the voice and signaling flows between two sub-networks linked by an ABC-
F IP trunk group.
This trunk group doesn't support the transparent fax/modem and cannot be distributed.
Only one ABC-F IP trunk group between two OmniPCX Enterprises. No mixity ABC-F TDM / ABC-F IP
between two sub-networks.
9.

SIP

As of Release 9.0, all standard SIP sets must be declared with the SIP Extension type. Standard
SIP sets are no longer supported with the former "SIP Device" mode (formerly called "External set").
Only items other than standard sets (Nokia sets in Dual mode, Alcatel 4135 conference module, fax,
video, etc.) should remain with the former "SIP Device" mode.
This new mode (Native SIP Call Controller, also named SEPLOS - SIP End Point Level Of Service in
some technical documents) allows to increase strongly the level of service on a SIP set, compared
with the SIP standard (use of many OmniPCX Enterprise prefixes, etc.). Only the sets mentioned in
the SEPLOS "white list" (refer to the technical documentation
White List) will be supported in complete SEPLOS mode. This "white list" is likely to be regularly
expanded further interoperability tests performed in the AAPP framework. The sets not listed in the
Ed. 02 / 22 June 2011
OmniPCX Enterprise
19
REMARKS & RESTRICTIONS
TC1108 Native SIP Call Controller:
APPENDIX 2
TC1449