[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Cbeyond Launches Direct IP Peering Initiative - SIPconnect
FYI: I thought Richard Statsny's blog had some interesting commentary on this, and how it would relate to ENUM. The text of his post is below (URL is http://voipandenum.blogspot.com/2005/02/sipconnect-direct-ip-peering-and-what.html)
Begin Quote:
The SIPconnect Interface Specification launched by Cbeyond Communications in 2004 with support from Avaya, BroadSoft, Centrepoint Technologies, Cisco Systems, and Mitel is a standards-based method of interconnection between IP PBXs and VoIP service provider networks. It specifies a reference architecture, required protocols and features, and implementation rules necessary for seamless peering between IP PBXs and VoIP service providers.
Of course this is a good start to provide IP-based connectivity, but the scope of the architecture is quite limited, namely to the IP-based User-Network-Interface (UNI) between an IP PBX and a VoIP service provider. The achitecture consists of the IP PBX, the Call Control Server (CCS) and the Media Server (MS) of the VoIP Service provider, and a Trunking Gateway (TGW) to the PSTN. So basically a company running an IP PBX may only interface with a VoIP service provider saving the own gateway to the PSTN. All calls out of the IP PBX are routed via the VoIP service provider.
There is an additional element, but only optional (Henry ;-) - the unfamous Session Border Controller (SBC).
What is missing are two major points:
1. How VoIP service providers interconnect (the Network-Network-Interface NNI) and the routing mechanisms to achieve this (e.g. carrier/infrastucture ENUM). But this may be any issue for VoIP service provides only. The SIP Forum Service Providers Working Group is currently looking after these issues.
2. and even more important, the answer to the question why IP PBX need VoIP service providers to peer with each other on the Internet.
At the SIPconnect home page in the FAQ section it is stated under the topic:
How does SIPconnect benefit business users?
Business customers are the end users who will ultimately benefit from direct IP peering.
Businesses that take advantage of SIPconnect where their IP PBX peers directly with their communications service provider eliminate the need for expensive TDM gateways, and increase the efficiency with which they use local access facilities. They also increase their opportunity to purchase enhanced applications from service providers and can more easily extend the functionality of their IP PBX across service provider networks.
I personally understand the term "direct IP peering" in such a way that IP PBX connected to the Internet are peering directly with each other and not with and via VoIP services providers.
The best and simplest way to achieve this is the usage of ENUM to peer directly between IP PBX. This requires only the addition of an ENUM client into the PBX Software and the reachability of the IP PBX via a public SIP URI. Examples are the open source Asterisk and the SIP Express Router (SER) from iptel.org. An animated example scenario is contained in my presentation (slide 10) given at the Domain Pulse event.
This does not prevent IP PBX to use either their own gateways to the PSTN or the IP-based peering as defined by SIPconnect if a E.164 number is not found in ENUM.
The approach is basically the following:
1. An IP PBX is first querying ENUM for the number dialled. If an entry is found in ENUM, the other party (other IP PBX or residential user) is contacted directly.
2. If no entry is found, the call is forwarded to the VoIP service provider.
3. The VoIP service provider first tries to find another VoIP service provder hosting the number dialled, e.g. by querying Infrastructure ENUM. Only of this also fails, the call is routed via the PSTN.
The basic idea is to keep the call on IP for all end-points that can be reached on IP, not only for saving money, but even more important to improve QoS and enable all additional features possible with SIP-SIP communication.
[End Quote]
-----Original Message-----
From: Mark R. Lindsey [mailto:lindsey@e-c-group.com]
Sent: Monday, February 14, 2005 6:46 PM
To: John Todd
Cc: VoIP Peering; Irwin Lazar
Subject: Re: Cbeyond Launches Direct IP Peering Initiative - SIPconnect
Of interest to this discussion -- the SIPConnect spec notes that if
either the service provider (SP) or the PBX refers the signaling or
media off to something else, then the something else has to adhere to
all of the SIPConnect standards. This may be in fact complicate peering
for an SP that wishes to be SIPConnect compliant.
For example, suppose that a service provider is peered with Level3.
Level3 doesn't adhere to the SIPConnect draft; e.g., the spec requires
the use of ten digit (NANPA) numbers, whereas Level3 requires E.164
numbers. If the service provider uses Level3 for PSTN origination such
that, eventually, Level3 sends an INVITE directly to the PBX, then the
SP isn't SIPConnect compliant any more.
A "Session Border Controller" (SBC) of some sort may be required to
normalize the signaling, translations, etc., between the VoIP peers and
the SIPConnect PBXs. But this really just suggests something that's
already obvious -- that not every peer can be directly
302-Moved-Temporarily'd over to just any SIP device. One nice thing
about SIPConnect is that it helps to identify the problem points.
On Feb 14, 2005, at 2:27 PM, John Todd wrote:
> This is a useful initiative. To distill this: it appears that this is
> an effort to create a standard of the standards. In my opinion, the
> use of the word "peering" could be replaced with the word
> "interconnection" without losing any of the meaning or usefulness of
> this initiative. Their concept of "peering" is the delivery of SIP
> VoIP minutes beteween an iPBX and a termination provider (PSTN or
> otherwise.) Importantly, the term "peer" in this context does not
> mean an exchange of routes; it means "successful interconnection and
> delivery of SIP call termination." This is a separate discussion from
> that of the question of how an endpoint knows where to go to reach
> other endpoints - most iPBX platforms are configured in a "static
> default" configuration where there is a single path outbound to the
> PSTN.
>
> We've all been down this semantic road before, haven't we? :-)
>
> As a once-and-future wrangler of SIP interconnections, I can attest
> that this type of effort is a step in the right direction, and I'm
> very interested in seeing if they've built a good recommendation. I
> dug through their web pages, and at the base of all the marketing hype
> was this document:
>
> http://web.memberclicks.com/mcdatafiles/bbattach/48604/
> SIPconnect_Version_1_Draft_2-2-2005.pdf
>
>
> JT
>
>
>
> At 1:20 PM -0500 on 2/14/05, Irwin Lazar wrote:
>> Thought I'd pass this along (and maybe bring the list back to life).
>> It's interesting that this happened outside of both the IETF and the
>> SIP Forum. Any thoughts?
>>
>> irwin
>>
>>
>> ---------------
>>
>> Cbeyond Collaborates with Industry Leaders to Launch IP PBX VoIP
>> Interoperability Initiative
>> Release of New Draft "SIPconnect Interface Specification" Provides
>> Standards-based Direct IP Peering between IP PBXs and VoIP Service
>> Provider Networks
>>
>> Lake Buena VISTA, Fla., February 7, 2005 - Cbeyond and a number of
>> leading IP telephony vendors, including Avaya, BroadSoft, Centrepoint
>> Technologies, Cisco Systems, and Mitel, have developed a draft best
>> practices document to guide interoperability between IP PBXs and VoIP
>> service provider networks. The newly released, publicly available
>> SIPconnect Interface Specification leverages the existing family of
>> Session Initiation Protocol (SIP) and other Voice over IP protocols
>> published by the Internet Engineering Task Force (IETF).
>> The rapid deployment of IP PBXs in business customers and the
>> transition to VoIP by service providers has created an opportunity
>> for direct IP peering between IP PBXs and VoIP-enabled service
>> providers. Direct IP peering between business customers and service
>> providers allows for greater network and cost efficiencies, and
>> provides a higher quality of service and increased features and
>> functionality. Specifically, direct IP peering serves to lower costs
>> for business customers, reduce voice latency, and provide for
>> end-to-end SIP signaling for PSTN termination. End-to-end SIP
>> signaling and a pure IP bearer path lay the foundation for richer
>> communication services than offered by the PSTN today, which are
>> essential to the future of packet-based communications.
>>
>> Driven by Cbeyond's service requirements, SIPconnect fosters direct
>> IP interoperability among businesses with IP PBXs and service
>> providers by providing a consistent, industry standards-based
>> approach to interconnection using SIP and other standard VoIP
>> protocols. Cbeyond is making the document public in order to gain
>> industry-wide approval of the interface and service.
>> Cbeyond Communications and vendors Avaya, BroadSoft, Centrepoint
>> Technologies, Cisco Systems, and Mitel have all indicated their
>> intention to develop products and services that comply with the new
>> draft specification. "Cisco Systems is excited by Cbeyond's plans to
>> deliver a service interconnecting IP-based businesses and VoIP
>> Service Providers via an end-to-end IP infrastructure." stated Vikas
>> Butaney, Director of Product Marketing for Cisco Systems. "This
>> offers future opportunity to extend the VoIP and rich-media services
>> enabled by IP-PBXs within a single enterprise out across the Service
>> Provider network and between enterprises." Cisco Systems has
>> indicated that Cisco Call Manager Express and Cisco AS5000 Gateway
>> products already comply with the requirements of the SIPconnect
>> Interface Specification.
>>
>> Jim Davies, Chief Technology Officer of Mitel, also contributed to
>> the development of SIPconnect. "This initiative is an important step
>> toward clarifying among PBX developers how to build a VoIP interface
>> that will be supported with the same consistency and ubiquity as
>> traditional PSTN services," said Davies. "I believe that the industry
>> as a whole will move rapidly toward the support of SIPconnect on its
>> IP PBX products."
>>
>> "SIPconnect can help accelerate enterprise adoption of advanced IP
>> and SIP-based solutions," stated Carl Baptiste, Vice President of
>> Product Management for Avaya's Converged Systems Division. "A well
>> defined interface between IP PBXs and VoIP service providers will
>> ultimately lead to increased value for our customers." Avaya's
>> Converged Communications SIP Server complies with the current draft
>> of the SIPconnect Interface Specification.
>>
>> BroadSoft currently supports SIPconnect on the BroadWorks application
>> server platform. "We are pleased to team with leading companies like
>> Avaya, Cisco, and Mitel to drive further standardization for VoIP
>> services," stated Scott Hoffpauir, Chief Technology Officer of
>> BroadSoft. "With equipment vendors supporting the SIPconnect
>> specification, enterprises with an IP PBX can get advanced services
>> over the network even if they deployed equipment from multiple
>> vendors."
>>
>> Centrepoint Technologies TalkSwitch IP PBX products are already in
>> compliance with the SIPconnect specification. "SIPconnect defines a
>> clear and consistent architecture that enables IP PBX vendors and
>> service providers to rapidly and cost effectively deploy VoIP
>> services." said Robert Brown, Chief Technology Officer for
>> Centrepoint Technologies. "We are pleased to work with a team of
>> leading companies on the advancement toward standardization of the
>> interface between VoIP enabled networks and IP PBXs."
>>
>> About SIPconnect.
>> The draft SIPconnect Interface Specification launched by Cbeyond
>> Communications with support from vendors Avaya, BroadSoft,
>> Centrepoint Technologies, Cisco Systems, and Mitel is a method of
>> interconnection between IP PBXs and VoIP service provider networks.
>> SIPconnect specifies a reference architecture, required protocols and
>> features, and implementation rules necessary for seamless peering
>> between IP PBXs and VoIP service providers. To join the SIPconnect
>> initiative, and to access the complete SIPconnect Interface
>> Specification and related documentation, visit www.sipconnect.info
>> <http://www.sipconnect.info/><http://www.sipconnect.info/> .
>>
>> ABOUT: BroadSoft, Inc.: www.broadsoft.com
>> <http://www.broadsoft.com><http://www.broadsoft.com>
>> Cbeyond Communications: www.cbeyond.net
>> <http://www.cbeyond.net><http://www.cbeyond.net>
>> Centrepoint Technologies: www.talkswitch.com
>> <http://www.talkswitch.com/><http://www.talkswitch.com/>
>> Cisco Systems, Inc.: www.cisco.com
>> <http://www.cisco.com/><http://www.cisco.com/>
>> Mitel: www.mitel.com <http://www.mitel.com/><http://www.mitel.com/>
>>
>> Cbeyond Communications Announces BeyondVoice with SIPconnect, the
>> First Integrated VoIP and Broadband Internet Service Designed
>> Specifically for Direct IP Peering with IP PBXs
>>
>> ATLANTA, Georgia, February 7, 2005 - Cbeyond Communications, a
>> Managed Services Provider and a leader in Voice over IP (VoIP),
>> announces the enhancement of its BeyondVoice integrated voice and
>> broadband Internet service packages to support direct IP peering with
>> IP PBXs using the SIPconnect Interface Specification. BeyondVoice
>> with SIPconnect allows Cbeyond's small business customers to connect
>> an IP-based key system or PBX directly to Cbeyond's VoIP network via
>> industry-standard SIP protocol without investment in VoIP gateways or
>> the recurring expense of traditional TDM voice services such as
>> analog lines or PRI circuits. Customers can now enjoy the ability to
>> place and receive traditional PSTN calls, and a broad range cost
>> savings, service benefits and enhanced features made possible by a
>> pure VoIP interface.
>> BeyondVoice with SIPconnect starts at $495 per month and supports 1.5
>> Mbps to 4.5 Mbps of symmetric, high quality Internet access and
>> anywhere from 5 to 48 active calls. Breaking the traditional mold of
>> 'telephone lines", using SIPconnect a customer can now purchase their
>> service based on the number of active or simultaneous calls they
>> anticipate making at a given time. In addition, small businesses can
>> now take advantage of Direct Inward Dial (DID); a "big business"
>> feature that gives each employee their own phone number. Direct IP
>> peering between the customer's IP PBX and Cbeyond's VoIP network
>> eliminates the need for the customer to purchase and maintain a VoIP
>> gateway; resulting in an initial and on-going cost savings for the
>> customer.
>>
>> "Cbeyond is proud to offer this first of its kind product
>> specifically designed for interconnecting IP PBXs with a service
>> providers VoIP network," stated Brooks Robinson, Chief Marketing
>> Officer of Cbeyond Communications. "In late 2004 we began seeing more
>> IP PBXs being sold than traditional TDM PBXs. We have developed an
>> integrated package of voice, broadband Internet and enhanced
>> applications tailored specifically to meet the demands of this large
>> and growing market," Robinson said.
>>
>> Building on the benefits of pure IP peering, Cbeyond also plans a
>> series of new enhanced features specifically designed for SIPconnect
>> users. The flagship of these new features is a personalized online
>> communications and management portal that allows individual users of
>> an IP PBX to place and manage real-time calls or customize their
>> Cbeyond service. Each individual user and an overall group
>> administrator will now have the ability to control call features down
>> to an individual user or phone number basis.
>>
>> "The native support of IP PBXs using SIPconnect is an important step
>> to a broad range of new features and capabilities inherent in
>> next-generation communications networks," said Chris Gatch, Chief
>> Technology Officer of Cbeyond." Cbeyond is leading the move toward
>> direct IP peering with customer IP PBXs because it's an essential
>> step in realizing the true potential of VoIP."
>>
>> Cbeyond is using a combination of technology products from Cisco
>> Systems and Broadsoft to deliver BeyondVoice with SIPconnect.
>>
>> About Cbeyond Communications
>> Cbeyond Communications, a privately held, Atlanta-based Managed
>> Services Provider, is the leader in the emerging local voice and
>> broadband services market and manages the world's first 100% Voice
>> over Internet Protocol (VoIP), facilities-based, private, local phone
>> network. Using Voice over Internet Protocol (VoIP) and a
>> Cisco-powered network, Cbeyond delivers to small business customers
>> in Atlanta, Chicago, Dallas-Ft. Worth, Denver and Houston an
>> integrated package of high quality local and long distance telephony
>> services, high-speed Internet access and Internet-based applications
>> for about the same price that small businesses typically pay for
>> local and long distance service alone. For more information on
>> Cbeyond Communications, visit www.cbeyond.net
>> <http://www.cbeyond.net/><http://www.cbeyond.net/> .
>>
>> About SIPconnect.
>> The draft SIPconnect Interface Specification launched by Cbeyond
>> Communications with support from vendors Avaya, BroadSoft,
>> Centrepoint Technologies, Cisco Systems, and Mitel Networks is a
>> method of interconnection between IP PBXs and VoIP service provider
>> networks. SIPconnect specifies a reference architecture, required
>> protocols and features, and implementation rules necessary for
>> seamless peering between IP PBXs and VoIP service providers. To
>> learn how to become part of the SIPconnect initiative, and to access
>> the complete SIPconnect Interface Specification and related
>> documentation, visit www.sipconnect.info
>> <http://www.sipconnect.info/><http://www.sipconnect.info/> .
>>
>> ------ End of Forwarded Message
>
>
> --
> To unsubscribe send a message to voip-peering-request@psg.com with
> the word 'unsubscribe' in a single line as the message text body.
> An archive is at <http://psg.com/lists/voip-peering/>.
--
To unsubscribe send a message to voip-peering-request@psg.com with
the word 'unsubscribe' in a single line as the message text body.
An archive is at <http://psg.com/lists/voip-peering/>.