OpenCNAM V1 Deprecation

As many of you know, one of our main products, OpenCNAM (http://www.opencnam.com/), launched a new V2 API earlier this year. We launched our V2 API to help make OpenCNAM a better product for our users.

With our new V2 API we:

  • Added more functionality to our backend.
  • Fixed various inconsistencies in our user-facing API.
  • Made numerous performance improvements to make our API responses faster for our users.
  • Added more (and better quality) telco sources to improve our overall CNAM data quality.
  • Added support for volume pricing (we now offer discounts up to 50m monthly queries, and beyond!).
  • Made numerous improvements to our website, client libraries, and user portal.

Today, we’ve seen more than 95% of our users (and existing application developers) shift their code over from our V1 API to our V2 API, which is why we’re officially announcing that as of September 1, 2013, we are officially shutting down our old V1 API.

What does this mean for you (as an OpenCNAM user)?

If you’re currently using our V1 API (if you see a v1 anywhere in your URL) you’ll need to upgrade your application code and point your code towards our new V2 API by September 1, 2013.

In most cases, you can simply change your URL string from: https://api.opencnam.com/v1/phone/... to https://api.opencnam.com/v2/phone/... — and that’s all!

If you have any questions, concerns, issues, etc. — we’ll be available to help you out with the migration. You can reach us at anytime via our support email: support@opencnam.com.

With our V1 API closing down, we’re going to be doubling our work efforts on OpenCNAM.

In the near future we’re planning to:

  • Release a user account API, which allows you to pragmatically query your OpenCNAM account history (billing, payments, queries, etc.).
  • Add a variety of new telco data sources to further improve our CNAM data quality (we currently offer the best industry-wide CNAM data quality by pulling our data from as many top-level sources as possible).
  • Release a new CNAM storage product, which allows you (as an OpenCNAM user) to set your own CNAM records for phones you control — we’ll handle the CNAM propagation to the public telephone network.

While we’re sad to close down our V1 API, we’re extremely happy to continue to work with the smartest and most awesome customers in the industry, and we’re extremely excited to launch our highly anticipated OpenCNAM features and updates in the coming months.

  • Randall Degges (CTO)

Freeswitch + OpenCNAM


Are you a Freeswitch user who’d like to get Caller ID Name for your PBX? If so, you’re in the right place.

You’ve probably Google’d around for a while, looking for a decent CNAM provider, but only found horrible websites and expensive options.

Not anymore!

We at Telephony Research are happy to announce easy Freeswitch integration with our flagship API company, OpenCNAM. Using Freeswitch’s built-in cidlookup module, you can now easily interface with OpenCNAM to get:

  • High quality CNAM information in the US, Canada, Puerto Rico, and many more places.
  • Cheap CNAM (pricing starts at $.004 per successful query).
  • Easy payment options (single deposits, automatic billing, or bitcoin payments).
  • World class support from our engineering staff.

If you’re a hobbyist user, and your Freeswitch PBX doesn’t do more than few calls per hour, you can get CNAM with us absolutely free, no signup required!

If you’ve been looking for a simple CNAM provider that works well with Freeswitch, give OpenCNAM a try right now :)

You can create an OpenCNAM account here: https://www.opencnam.com/

You can read our Freeswitch integration guide here: https://www.opencnam.com/docs/v2/pbx#freeswitch


Our Solution

Here at Telephony Research, we like to build things.

To be more specific: we like to build telephony services.

To be even more specific, we like to build kick-ass telephony services.

The Problem

The entire telephony world sucks right now. Since the mid 1900s, very little has changed in the telephony landscape.

  • The PSTN is still a huge legacy network controlled by several extremely large corporations.
  • Making phone calls is expensive (1 cent or more, per minute).
  • Getting phone numbers (DIDs) is still not a simple thing (number blocks are assigned to various companies, which typically require you to have voice service with your DID).
  • Caller ID Name is not supported over cellular networks.
  • There is a complete lack of international standards for making phone calls and receiving / sending Caller ID name.
  • International telephony is insanely expensive.
  • VoIP carriers tend to have issues with low quality voice.
  • The industry is plagued with horrible sales practices (sales guys, manual provisioning, etc.).
  • There is a total lack of operational transparency with most telcos, you have no idea what is being done, how things work, or any other data.
  • Most voice traffic is completely un-encrypted, making the entire industry vulnerable to numerous security problems.
  • And MUCH more.

What all these problems really boil down to is lack of openness and talent.

While the web has really taken off, attracting tons of developers and money, telecommunications has remained largely unattractive to programmers. Since many telecommunications protocols are complex, cost a lot of money to work with, and not adequately documented—the telecommunications industry has succeeded in:

  • Keeping new developers out of the industry.
  • Lowering the bar for development talent (thereby decreasing overall product and service quality).
  • Making progress slower and slower as time progresses.

This is completely unacceptable.

My Two Cents

I’m a programmer. When I first got introduced to the telephony world, I was shocked at how hard it was to find:

  • Information on telephony technologies.
  • Getting started information.
  • How the public telephone network works, and what technologies are used.
  • How old the protocols and technologies are that power voice services.
  • How many insane regulations and laws there are which only serve to make the industry worse (in numerous ways) for consumers.

If telephony technologies were simpler and more modern, then instead of keeping new developers away, new developers would be attracted to the industry, and be better equipped to build services, companies, and projects that make users happy.

In almost every industry—if you have more developers working in the field, progress will be quicker, users will be happier, and more wealth will be generated (by all parties).

Our Solution

Our solution to the current problems of the industry is simple: we build services which make telephony simpler and more elegant for developers.

Our hope is that by providing tools that developers can easily build on top of, we’ll:

  • Enable new developers to easily get involved in the industry.
  • Educate developers on how the technologies work, and how they can be improved upon.
  • Encourage competition from new startups.
  • Enable developers to generate better products and services that consumers will love.

To this end, we’re heavily focused on continuous improvement. Every day we work tirelessly to fix bugs, add new features, and reduce complexity in our software—and make the telephony industry just a tad bit better—line by line.

If you’re a developer thinking about getting involved in some new technologies: don’t hesitate! Feel free to shoot us an email: hi@telephonyresearch.com, and get in touch—we’d love to help you out in any way possible.

And if you’re interested in checking out what we’re up to, be sure to:

Let’s do this thing.

Tags: rant