OmniPCX Enterprise
INSTALLATION PROCEDURE FOR VERSION
J1.410.34.c – RELEASE 10.0
APPENDIX 1
NEW HARDWARE AND FEATURES
TC1449 8 Ed. 02 / 22 June 2011
The installed country in the MASTER CPU will be the default option, if the user needs extra countries
the next option can be used.
2.3. Features under PCS
If one of the following features has to be implemented on an OmniPCX Enterprise, contact Technical
Support for the deployment.
2.3.1. SIP TLS/sRTP for external SIP Gateway
Before Release 10.0, only IPsec/SRTP protocols are supported to protect UA/NOE communications.
The IPsec protocol protects UA/NOE signaling and the SRTP protocol (one key) protects the sent and
received voice flows.
As of Release 10.0, IPsec/SRTP and TLS/SRTP protocols can be used simultaneously.
As of Release 10.0, TLS/SRTP protocols are supported to protect SIP communications with external
SIP Gateways in ISDN mode.
The TLS protocol protects SIP signaling and the SRTP protocol (two keys: one key is used to encrypt
sent voice flow and an other key is used to encrypt received flows) protects voice flows.
TLS can be used to secure SIP Trunks configured on the OmniPCX Enterprise to a Carrier or Service
Provider network (Public SIP Trunking).
Depending on Carrier/Service Provider capabilities, voice media can also be encrypted using SRTP.
Each Public SIP Trunk can be configured at OmniPCX Enterprise level with TLS&RTP or TLS&SRTP.
The voice media can be end-to-end encrypted (using SRTP) from the IP Touch set in the customer’s
network up to the Carrier’s gateway.
To Next Page
Loading...
Need help?
General
