Collapse AllExpand All

14.3.2. Native SIP Trunking Previous topic Parent topic Child topic Next topic

Native SIP trunks can be used to connect SIP service provider (see Section 3.2.3.1, “SIP Service Provider”) or 3rd party SIP products (e.g. OpenScape Xpressions, Section 3.2.3.3, “Applications”).
3rd Party Native SIP connections can be connected to OpenScape 4000 Gateway using the standard delivered profiles of the Gateway without any Project Specific Release (PSR).
The list of Supported RFCs can be found in the SIP Connectivity chapter of this document. Should the OpenScape 4000 Gateway not conform to any of the published RFCs, then any found issue can be addressed via a Service Ticket.
It is not supported to change the fixed parameters of existing profiles. The recommended profile for 3rd Party SIP applications is “NatTrkEnterprise”, which includes support for SIP Refer. There are dedicated profiles for the 3rd party products MS Teams and Cisco UCM.
The process to request new board profiles, which is mandatory for SIP Service Provider (SSP), can be found here: https://wiki.unify.com/wiki/Collaboration_with_VoIP_Providers_on_Enterprise_Platforms#OpenScape_4000