<?xml version="1.0" encoding="UTF-8"?>
<feed xmlns="http://www.w3.org/2005/Atom" 
      xmlns:thr="http://purl.org/syndication/thread/1.0">
  <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/enum-aint-gonna-happen.asp" />
  <link rel="self" type="application/atom+xml" href="http://blog.tmcnet.com/blog/tom-keating/atom.xml" />
  <id>tag:blog.tmcnet.com,2013:/blog/tom-keating//4/tag:blog.tmcnet.com,2005:/blog/tom-keating//4.16997-</id>
  <updated>2013-02-22T21:05:50Z</updated>
  <title>Comments for ENUM ain&apos;t gonna happen</title>
  <subtitle>VoIP &amp; Gadgets blog - Latest news in VoIP &amp; gadgets, wireless, mobile phones, reviews, &amp; opinions</subtitle>
  <generator uri="http://www.sixapart.com/movabletype/">Movable Type 4.38</generator>
  <entry>
    <id>tag:blog.tmcnet.com,2005:/blog/tom-keating//4.16997</id>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/enum-aint-gonna-happen.asp" />
    <link rel="service.edit" type="application/atom+xml" href="http://blog.tmcnet.com/mt/mt-atom.cgi/weblog/blog_id=4/entry_id=16997" title="ENUM ain't gonna happen" />
    <published>2005-09-30T13:51:52Z</published>
    <updated>2008-04-10T21:35:23Z</updated>
    <title>ENUM ain&apos;t gonna happen</title>
    <summary> Mr. Blog had some interesting thoughts a couple of days ago.As we near the end of 2005, what is the status of ENUM? The original RFCs were published in 2000 I believe. Is there a single commercial VoIP provider...</summary>
    <author>
      <name>Tom Keating</name>
      <uri>http://blog.tmcnet.com/blog/tom-keating/</uri>
    </author>
    
    <category term="Packet8" />
    
    <category term="VoIP" />
    
    <category term="Vonage" />
    
    <content type="html" xml:lang="en" xml:base="http://blog.tmcnet.com/blog/tom-keating/">
      <![CDATA[<p><img width="200" vspace="20" hspace="10" height="200" border="0" align="right" src="http://blog.tmcnet.com/blog/tom-keating/images/brick-wall.png" /><a href="http://www.toyz.org/mrblog/archives/00000207.html"><br />
Mr. Blog</a> had some interesting thoughts a couple of days ago.<blockquote>As we near the end of 2005, what is the status of ENUM? The original RFCs were published in 2000 I believe.<br />
Is there a single commercial VoIP provider that supports the official e164.arpa ENUM? If they do, they certainly don't promote it or mention it anywhere on their web sites that I can find. Vonage, AT&amp;T CallVantage, Packet8, Broadvoice, SunRocket? Anyone?<br /><br />Of course to support ENUM, they would first have to support interoperable IP to IP calling, by SIP address, or otherwise. Again, few if any of the providers make any mention of this on their site or in their documentation. Some appear to have at least some limited support for placing or receiving calls over IP, but it's difficult to determine if it is intentional and a supported feature or simply a side-effect.<br /><br />The only thing that will change things is consumer demand. As long as we let the providers remain closed walled gardens, they will. <span style="font-weight: bold; color: rgb(255, 0, 0);">So much for the IP revolution.</span><br /></blockquote><br />Hear, Hear, Mr. Blog! I couldn't agree more. Why is ENUM taking so long? Are money and greed the only human inspiration? What about cool innovation for the sake of innovation and not the almighty dollar?  I'm no socalist, but seriously, how much money do Vonage, Packet8, AT&amp;T CallVantage, and all the other providers need that they can't offer ENUM connectivity with competing VoIP providers? <br /><br />Come to think of it, most VoIP subscribers probably have the &quot;unlimited minutes&quot; plan, so the VoIP providers aren't generating any more revenue or doing themselves any favors by having these closed walls. In fact, the VoIP providers themselves have to <span style="font-style: italic;">incur more costs</span> when they terminate to a phone number over the PSTN when they<span style="font-style: italic;"> could have routed the call over IP to their competitor's subscriber</span>. If VoIP provider A simply routed the call to competing VoIP provider B, VoIP Provider B could even charge VoIP provider A a <span style="font-style: italic;">nominal fee</span> for terminating the call to its VoIP subscriber over IP - it's still less expensive than a PSTN termination. Of course, tracking direct IP calls made via an ENUM lookup, specifically the call duration for billing purposes could be tricky. Alternatively, they could just have a mutual agreement to terminate calls to each other's VoIP subscribers at no charge.<br /><br />I don't believe VoIP broadband service has cracked even 10% U.S. marketshare, so in my opinion, the VoIP providers should &quot;band together&quot; and offer free intra-VoIP provider calling. This would be one more feature that could aid in VoIP broadband market penetration. With more competition from cellular companies, cable companies, and especially Triple Play packages, etc. the single-play VoIP providers will need to &quot;band together&quot; sooner rather than later if they want to compete in the near future.<br /><br />Instead, the VoIP providers have chosen to become the closed-wall carriers of the 21st century. </p>]]>
      
    </content>
  </entry>

  <entry>
    <id>tag:blog.tmcnet.com,2005:/blog/tom-keating//4.16997-comment:4273</id>
    <thr:in-reply-to ref="tag:blog.tmcnet.com,2005:/blog/tom-keating//4.16997" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/enum-aint-gonna-happen.asp"/>
    <link rel="alternate" type="text/html" href="http://blog.tmcnet.com/blog/tom-keating/voip/enum-aint-gonna-happen.asp#c4273" />
    <title>Comment from Jim on 2005-12-12</title>
    <author>
        <name>Jim</name>
        <uri></uri>
    </author>
    <content type="html" xml:lang="en" xml:base="">
        <![CDATA[<p>Well, ENUM in the US requires resolution to a difficult problem.  The IP Addressing and DNS information is served by many places throughout the footprint which ENUM should cover.  In order to serve the proper DNS information, you must be able to look at the proper registrar holding the information.  Because there is 19 different countries sharing Country Code (1) this poses a little challenge.  I suggest reading some info on ENUM and you will understand the problem that the Big Bell put us in way back when.</p>]]>
    </content>
    <published>2005-12-12T22:29:12Z</published>
  </entry>

</feed>
