Results tagged “sip connect” from IP Communications and Technology

SIP Forum Ratifies SIPconnect

| | Comments (0)
The SIP Forum has ratified its SIPconnect Recommendation. SIPconnect is a standards-based approach for direct IP interoperability between IP PBXs and VoIP Service Provider Networks.

The SIP Forum lists the following SIPconnect features and benefits:

  • A Ubiquitous Approach. SIPconnect provides a common method for IP peering between SIP-enabled IP PBXs and VoIP service providers
  • Standards Based. SIPconnect leverages existing SIP and related VoIP standards published by the Internet Engineering Task Force (IETF)
  • Customer Cost Savings. Peering lowers service provider infrastructure cost and reduce the need for customer premises gateways
  • Speed to Deployment.  A commonly accepted, standards-based approach reduces the time and effort needed to integrate new products into a service provider network.
  • Richer Feature Support. SIPconnect helps service providers deliver enhanced, personalized services to IP-PBXs and extends rich-media services enabled by IP-PBXs across service provider networks
  • Quality of Service. Methods for handling QoS configuration, echo cancellation, DTMF relay, packetization rates, codec support and fax and data traffic are defined
  • 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.
As I have stated previously, I'm convinced that SIP Trunking will take off in 2008 and it's about time! IP Trunking represents a great opportunity for innovative service providers. And for end users, in addition to the user benefits cited by the SIP Forum, here's a list of benefits from one of my previous posts on the subject:

PRI (via VoIP Gateway) vs IP Trunking

PRI

IP Trunks

Physical connections:

 

Each circuit requires physical connection and costly termination hardware.

Connections are virtual:

 

Number of available  trunks is a function of available bandwidth, not physical termination hardware or circuits.

Scaling up requires the installation of new circuits and additional termination hardware.

Scales up or down easily and quickly (a software configuration change) and can offer automatic and on-demand burst capabilities

Providing sufficient backup circuits to remote sites in an IPT-distributed architecture can negatively impact the ROI.

 

Automatic IP re-routing capabilities allow practical geographic distribution of PSTN connectivity to sites with limited or no network redundancy

Cost is usually per circuit per month

 

A variety of pricing models (i.e. usage based) are likely to emerge, including on-demand capacity.  Relative to PRI circuits and the associated supporting hardware, IP Trunking costs are likely to be significantly lower.

Capacity planning & engineering is critical:

 

Additional capacity must be planned well in advance since considerable lead time may be required for the ordering and installation of new circuits and termination hardware

While capacity planning is still important, adding additional capacity can be as simple as a software change. Additionally, providers are likely to offer burst capabilities.

Only way to accommodate loss of hardware or facility where PRI’s terminate is to build-in excess capacity with associated cost impact.

 

Can be designed to retain PSTN reachability and capacity in the event of the loss of terminating hardware (or even an entire office location) without the need to build in excess capacity

 

Including dispersed locations in most current IP Telephony deployments requires the addition of network redundancy or significant local PSTN connectivity (analogue or ISDN trunks) to ensure that individual locations can function autonomously in the event of a failure. These factors can add substantial Opex and Capex.

Dispersed locations can be connected to the PSTN via an IP connection. Should a network failure occur incoming calls can be automatically rerouted to the isolated location.

Diversity across service providers is usually cost prohibitive.

 

Can accommodate diversity across service providers much like is done today with Internet access via BGP.

 






StumbleUpon ToolbarStumble It! Add to Technorati Favorites
About Me

Tags

My Links