1. ENUM is the primary choice for routing with C7 being the fallback

2. The role of standards

In order to effect change technology must not only exist and operate correctly, but the thought process of how and when to use it must also change. A common language must have a common process and order. It is easy to see that the new way is ENUM first, C7 second. These are significant milestones in the psychology of networking as much as they are in the lifecycle of these entities.

To read the full announcement - http://www.reuters.com/article/pressRelease/idUS198119+06-Aug-2008+MW20080806

Related Entries
• Chatblog with Telcordia - May 12, 2008
• Chatblog with The Voice Peering Fabric - Apr 15, 2008
• VoIP Peering Chatblog - Apr 01, 2008

Gary Richenacker:  Telcordia plays a critical role by providing service providers
the necessary interconnect routing data that identifies the correct service provider
and the appropriate network entry point for them to successfully complete a call.

HN: How has the interconnection and access to that data changed as the world has evolved
from TDM to IP?

GR:  Interconnection functions for both TDM and IP fundamentally remain
the same; that is, service providers need to deliver service sessions from point A
to point B across their networks, as well as requiring connectivity and information
from each other to make that happen.  However, the functions could be implemented
differently based on the latest technologies.  For example, number portability,
which is deployed in TDM, will continue to be a required function in an IP
environment so long as telephone numbers are used as user identifiers.  
 
Routing for IP-enabled services differs from TDM in that it needs not only specify
information on the network gateway for a particular destination number, but also
needs to consider the types of services and quality of service requirements as there
is a greater degree of freedom in terms of how a session can be delivered.
   
HN: Having a greater degree of freedom is certainly a good thing, but it comes with
added complexity as you have noted. With the advent of IP in the voice world what
was once rigid and point-to-point has now become very fluid and any-to-any. Where
the Internet is the prime example of any-to-any, IP peering is that for dynamic, yet
specific routing. What similarities do you see with IP peering in the VoIP world?
 
GR: Peering for IP has been around a long time.  Many of the technical
issues and challenges are understood and are being addressed; however, peering for
VoIP is new and the challenges facing VoIP peering include different signaling
protocols being used, SIP, H.323.  Even if networks use the same protocol, they may
use a different set of vendors. We are aware through testing that these vendors
implement standards differently and therefore there are interoperability issues.
 
Another issue is whether the service providers can peer directly.  Recently we have
seen that service providers can come together but not necessarily peer directly with
one another and they utilize the services of a neutral registry that provides the
routing information.

HN:  Managing different protocols and resolving end-points quickly and accurately
are certainly key components of VoIP Peering. ENUM is playing a role in the
resolution of end-points today for both carriers peering directly and VoIP Peering
service providers to carriers and enterprises. As a result a great deal of reliance
has been placed on ENUM. How do you see ENUM's role evolving? Will it be challenged
by SRV and, or other protocols, or ultimately dominate and become the standard?

GR:  Yes I foresee ENUM's role evolving because as new services or functionality are
added, different protocols such as SRV for messaging and presence, need to be
assessed on how these protocols would enable service providers to offer an
integrated set of services.  To date, there have been many protocols defined but not
all have been successfully deployed because of either technical complications or
commercial considerations.  Since we are in the beginning stages of VoIP and IP
Peering between carriers it is not clear what protocols will dominate.  But it is
clear that service providers will continue to evaluate how to best enable services
that subscribers/end users will want and the role of the network and how to best
deliver those services will continue to evolve.

HN: Taking the customer's needs and wants in to consideration is definetly critical
for anything to be successful, especially in the early stages. VoIP Peering has made
its mark on the voice world and it will certainly be interesting to see how it
continues to evolve. Gary, thank you for Chatblogging!

GR: Hunter, thank you for the opportunity.
 
For those interested in learning more about the Telcordia visit www.telcordia.com,
or contact Nancy Wilczewski at nwilczew@telcordia.com

Related Entries
• Chatblog with The Voice Peering Fabric - Apr 15, 2008
• SIP-CCESSFUL VoIP Peering Standards - Aug 17, 2008
• VoIP Peering Chatblog - Apr 01, 2008

Hunter Newby: Mr. Shrihari Pandit CEO of Stealth Communications, welcome to the VoIP Peering Chatblog. So, what's new with the VPF in 2008?

Shrihari Pandit: When the VPF was launched in 2003 we set out to simplify the interconnect process for voice carriers through the creation of a physical distributed Ethernet network. This provided the foundation in which companies would establish interconnect relationships for the exchange of VoIP traffic, carrying now in excess of 200 billion minutes annually, without the need of running over the public Internet and eliminating the provisioning of dedicated circuits. 

Today, we are now focusing on developing new applications that would reside within the VPF. These applications will focus on assisting organizations to streamline the business and interconnect process even further,enabling them to reallocate more time for the development of new innovation applications and services.

We'll talk more about these exciting developments at our upcoming Voice Peering Forum in San Francisco on June 23-24.

HN: The VPF accomplished a lot between 2003 and 2008. Over that 5 year span the VPF went from 0 mintues over the Fabric to greater than 200 Billion. What do you believe the traffic will be 5 years from now?

SP: We are continuing to see growth of traffic on the VPF. It is our belief that traffic will continue to grow, even at higher growth rates we have yet to see, as voice continues its integration with [Internet Protocol applications.

The vision of communicating purely in the IP domain is shared by many telcos and non-telcos. By moving completely to IP, voice is then easily mashed up into applications thereby enriching our experience with communications... like in Star Trek!

HN: Star Trek! It is interesting that you mention that. Do you look to the visionaries in history, even science fiction history, to guide your developments for future service offerings? 

SP: I'm somewhat a fan of science fiction. It provides inspiration to many of what can be possible in time to come. But since these technologies aren't in reach at the moment, we'll look for direction from the customers, market and current technologies available! With the proliferation of Ethernet, IP and VoIP, the creation of the VPF was possible. Its true success is in the design and simplicity of the business model. To this date, many people find it astonishing how the platform has evolved since its original launch back in October 2003.

HN: There is no doubt that the VPF has amazed many people over the years and I totally agree that simplicity is essential. Given that the VPF has been so successful, what do you believe is the biggest challenge the VPF faces in the near future?

SP: Getting the word out.

HN: Now there is a challenge we all face. Shrihari, it is always a pleasure getting your insights. Thanks for Chatblogging!

SP: Thank you Hunter.

For those interested in learning more about the Voice Peering Fabric visit www.thevpf.com , the Voice Peerng Forum www.voicepeeringforum.com , watch the Voice Peering Forum commercial, or contact Shrihari at spandit@stealth.net

Related Entries
• Chatblog with Telcordia - May 12, 2008
• VoIP Peering Chatblog - Apr 01, 2008
• SIP-CCESSFUL VoIP Peering Standards - Aug 17, 2008

Related Entries
• Chatblog with Telcordia - May 12, 2008
• Chatblog with The Voice Peering Fabric - Apr 15, 2008
• SIP-CCESSFUL VoIP Peering Standards - Aug 17, 2008

Related Entries