Login Form
RECENT IETF DRAFTS
SIP internet drafts statistics
- 149 SIP related internet drafts (IETF).
- 8 new and updated drafts posted in the last 14 days.
| SIPconnect |
|
|
|
The SIPconnect Technical Recommendation is an industry-wide, standards-based approach to direct IP peering between SIP-enabled IP PBXs and VoIP service provider networks. This website and Forum promotes the SIPconnect initiative, and input for future versions is supplied through this Forum.
BenefitsThe implementation of the SIPconnect standard benefits many participants in the delivery of voice communications. For end users in the small business or large enterprise, SIPconnect eliminates, or greatly reduces, the need for a costly gateway at the end user's site. In addition, new features from the service provider or the IP PBX vendor will be delivered more quickly. For VARs and Interconnects, the SIPconnect compliant service provider will handle the complexity associated with connecting the SIP Trunk to the legacy TDM world. This eliminates the need for a lot of integration and troubleshooting work and allows the partners to focus on other, revenue generating activities. For Equipment and Software Vendors (Application Servers, IP PBX Vendors, SIP Proxies), SIPconnect greatly reduces the time and resources required to verify interoperability in the network. This single item, interoperability, currently drains many man hours from the services and equipment providers that could be better used creating new and more exciting features. This in turns reduces the amount of revenue that could be realized from those new features. The SIP Trunking Service Provider that uses SIPconnect SIP trunks realizes higher revenue streams much more quickly. Network services are rolled out more rapidly, greatly reducing the time to revenue for new services and features. In addition, the service provider can greatly reduce the time and staff required to complete interoperability testing.
HistoryThe SIP Forum began working on SIPconnect subsequent to the initial release of the SIPconnect Interface Specification in February, 2005 based on a proposal submitted by members of the SIPconnect initiative. The SIP Forum created the "IP PBX and Service Provider Interoperability Task Group" on July 15, 2005 to continue this work. The latest step was the launch of the SIPconnect Compliance Program in September 2007. View the announcement here.
For More InformationLearn more about the SIPconnect specification by looking at:
|
SIP SPOKESPERSON
Fergal Glynn is BlueNote Networks' architect and plays a principal role in the architecture, design, and product strategy of the SessionSuite⢠products.



