Skip to content
HomeSIP Network Operators Conferences (SIPNOC)SIPNOC 2015PresentationsDay Two3. An Examination of the Next Iteration of the SIPconnect Technical Recommendation.

3. An Examination of the Next Iteration of the SIPconnect Technical Recommendation.

[featured_image]
Download
Download is available until [expire_date]
  • Version [version]
  • Download 12
  • File Size 85 KB
  • File Count 1
  • Create Date June 29, 2015
  • Last Updated June 29, 2015

3. An Examination of the Next Iteration of the SIPconnect Technical Recommendation.

Presented by Andrew Hutton, Unify, and Spencer Dawkins, Huawei and the SIP Forum.

The recently formed SIPconnect 2.0 Task Group will produce a SIP Forum SIPconnect 2.0 recommendation that defines a common set of implementation rules for implementers who desire to interface an IP PBX with a SIP-enabled service provider. The recommendation(s) will specify which standards must be supported, provide precise guidance in the areas where the standards leave multiple options, supplement functionality gaps in existing protocols, and identify a baseline set of features that should be common to an IP PBX to service provider interface. Such guidelines will not preclude the implementation of additional SIP functionality and primitives that do not conflict with the common implementation rules of the recommendation(s). For purposes of this task group a SIP-enabled IP PBX is defined as a private, multi-user communications system that supports a clearly-defined baseline set of SIP standards along with other (optional) protocols.

The work will take account of the role SBC’s a both the enterprise IP-PBX side and the service provider side. At a high level, the interface to the service provider utilizes a combination of SIP signaling and media transport using RTP/SRTP. The interface to end-users of the IP PBX can be SIP or any other protocol capable of establishing a voice session (such as WebRTC, H.323, directly connected analog “black phone”, etc.)