Category: Telecom Industry

The Big Question On Avaya’s Acquisition of Radvision – What About The SIP and H.323 Stacks?

Avaya RadvisionWith today's big news in the VoIP / Unified Communications (UC) / telecom space of Avaya's acquisition of Radvision, pretty much all of the coverage has predictably focused on the video angle. While that's certainly important, I have a far bigger question:
What about Radvision's SIP and H.323 stacks?

More specifically -

will Avaya continue to support and promote the strong usage of Radvision stacks by other vendors?

Of all the coverage I've seen so far, only Tom Keating touched on this in his brief post:

They also developed a H.323 stack used in hundreds of VoIP and videoconferencing products before SIP became the dominant VoIP protocol of choice.

Beyond the popular H.323 stack, Radvision's SIP stack has also been used in a good number of products out there - and Radvision also developed stacks for RTP, MGCP and many other VoIP protocols. Just follow the links off of Radvision's developer page at:

http://www.radvision.com/Products/Developer/

to see the wide range of developer solutions they have developed over the years.

For those not familiar with this topic, a "stack" in developer-speak is basically a set of libraries that you can incorporate into your products to enable those products to communicate over a given protocol. So if you want to "SIP-enable" your product, you can license a "stack" from a company like Radvision rather than developing your own stack or using one of the various open source stacks that are out there. Licensing the stack also typically gets you support from the vendor and the ability to request changes/customizations/etc.

Radvision has enabled a good number of companies out there to get into the VoIP world. They have been a supplier of stacks to companies all across the VoIP / UC space.

Now they've been acquired by one of the largest vendors in the VoIP/UC space.

Will Avaya continue to support the widespread usage of Radvision's various stacks by other vendors?

Or will they restrict or reduce the usage? Or increase the costs? If so, what will the other vendor's do?

Can the various vendors using Radvision stacks trust Avaya to continue the developer program? Particularly when they may compete directly against Avaya?

Will there be more attention paid now to other providers of SIP and VoIP stacks?

THAT is the question that I'm most curious about in the midst of this merger...

Other Articles

Some of the pieces worth reading on this topic include:

P.S. Hat tip to Forrester's Henry Dewing, too, for at least recognizing the usage of Radvision's stacks, although he did not ask the question I'm asking here.


If you found this post interesting or useful, please consider either:


Martin Geddes Must-Read Piece On "Peak Telecoms"

The Last Days? (Apocalypse)Martin Geddes doesn't hold back! No longer beholden to corporate overlords (he used to work for BT), he is wonderfully free to say exactly what he believes. And he does....

If you are interested in the future of telecommunications / telephony, you really need to go over and read his piece:

Peak Telecoms

A teaser:

The telco voice and messaging business is on the verge of going into meltdown. As this is where the margins come from, the problem is hard to exaggerate. The drip-drip of links about declining voice and messaging volume and revenue is becoming a small stream. Even mobile telephony is losing ground in competition to asynchronous messaging. Twitter and Facebook message volumes are exploding, and SMS is beginning to sink. Termination and roaming are endangered species, hunted by packs of voracious regulators. There is no way back. When I started writing Telepocalypse back in 2003, the only thing I got wrong was the timing.

Cue the song "It's The End Of The World As We Know It"...

Well done, Martin, well done!

Image credit: gmacorig on Flickr


If you found this post interesting or useful, please consider either:


2nd FCC Workshop on PSTN Transition Streaming Live at 9:30am – Taking Questions Via Email and Twitter

FCC logoToday, December 14, 2011, the US Federal Communications Commission (FCC) is holding the second of two workshops on the transition of the PSTN to new technologies, as I described last week. The workshop will be streamed live today starting at 9:30am US Eastern at:
http://www.fcc.gov/live

The FCC's note about the workshops mentions that people watching live can send in questions to panelists using either of two methods:

  • by e-mailing livequestions@fcc.gov
  • tweeting on Twitter using the hashtag #FCCLIVE
Today's sessions look to be quite interesting and contain quite a range of participants. The full schedule and list of participants is available on the FCC's web site (click on "Expand" in the lower right corner of the page), but here is the brief list:

9:30 a.m. – 9:40 a.m.
Welcome Remarks
by Zachary Katz, Chief Counsel and Senior Legal Advisor, Office of the Chairman, FCC

9:40 a.m. – 10:45 a.m.
Impact of the Transition on the Technology and Economics of the PSTN
Participants include: University of Colorado, Carnegie Mellon, George Washington University, Massachusetts Institute of Technology (MIT), Gillan Associates, SIP Forum

10:45 a.m. – 11:45 p.m.
Policies of the PSTN (e.g., accessibility, reliability, affordability, and public safety)
Participants include: Tufts University, Consumer Federation of America, University of Wisconsin, Neustar

1:00 p.m. – 2:10 p.m.
Implementing the Transition to New Networks
Participants include: Verizon, Comcast, Carnegie Mellon, National Telecommunications and Information Association (NTIA), XO Communications

2:10 p.m. – 3:20 p.m.
Syncing Expectations, Emerging Technologies and the Public Good
Participants include: Georgetown University, University of Michigan, University of Pennsylvania – Wharton, Acme Packet, Panasonic Systems Networks

3:20 p.m. – 4:30 p.m.
Economic Rationales for PSTN Transition
Participants include: Queens College, Indiana University, Syracuse University, Sanford Bernstein, University of Auckland, NZ


If you found this post interesting or useful, please consider either:


What Is The Future of the PSTN? FCC Holding Workshops Dec 6th and 14th

FCC logoWhat is the future of the Public Switched Telephone Network (PSTN)? As we transition away from traditional telecom technologies to a world based on IP communications, what are the policy, technical and economic implications?

As I recently wrote over on CircleID, the United States Federal Communications Commission (FCC) is holding two workshops on this topic of what comes next for the PSTN.

The first workshop, tomorrow, December 6, 2012, will cover "what obstacles and opportunities the transition may create regarding public safety, accessibility, and ubiquitous service".

The second workshop on December 14, 2012, will cover "a wide array of economic, technological, and policy issues that need to be addressed as consumers choose to subscribe to, and rely on, new technologies and services."

The FCC's Public Notice about these PSTN Transition Workshops contains information about how to attend, both in person and via the FCC's live stream at http://www.fcc.gov/live.

The meeting tomorrow will begin at 9:00 am US Eastern time.

If you are in the Washington, DC, area and able to get to these workshops, it may be a great opportunity to join with others in expressing to the FCC a vision for what we want for the post-PSTN communications infrastructure.


If you found this post interesting or useful, please consider either:


An Interesting Historical Timeline of Canadian Telecommunications

Canadian Flag

Last week I was up in Toronto, Ontario, Canada for the Internet Society's ION conference that was a part of the larger Canadian ISP Summit. This was only the first Canadian ISP Summit, but I've heard only excellent reports on the 3-day session and indeed we were extremely pleased by the attendance and engagement in our ION session on Monday. I was unfortunately unable to stay for the rest of the summit, but I saw this link tweeted out and had to check it out:

Historical Timeline of Canadian Telecommunications Achievements (PDF)

It turns out to be a document created for a presentation at the World Telecommunication Standardization Assembly back in 2000 (hence, why the history only goes up to 1999 ;-). I'm assuming someone at the CA ISP Summit referenced this document... thus generating the tweets.

Regardless of the lack of recent info, it's an interesting history of telecom in Canada... and gives an intriguing view into the wiring of a large country. Worth a read for those interested in the history of telecom.

Image credit: dr_opulentfish on Flickr


If you found this post interesting or useful, please consider either:


150 Years Ago Today, the USA Got Wired!

A great article in the San Francisco Examiner today about the completion, 150 years ago today, of the transcontinental telegraph here in the United States:
150 years ago, a primitive Internet united the USA

I think "a primitive Internet" might be a bit of a stretch... but then again I'm one of those network people who think of the "Internet" as a "network of networks"... and this first interconnection was really just creating that initial network!

Nuances aside, it's an enjoyable article to read...

Telegraph

I found this an interesting commentary on the disruption of the communication channels that came before:

Indeed, the Pony Express, which boasted it could deliver a letter from Sacramento to St. Joseph, Mo., in the unheard of time of 10 days when it began operations on April 3, 1860, shut down 19 months later — on the same day the transcontinental telegraph went live.

Though dramatic, that was a short-term effect. "But the longer-term effect was we connected the nation in real time. ...," says Fischer. "For the first time, businesses could do business nationally. The government could communicate nationally in almost real time."

Well worth a read to understand the challenges that went into the first physical infrastructure for what would become "telecommunications".


If you found this post interesting or useful, please consider either:


Congrats, I think, to Alec Saunders as RIM’s New VP of Developer Relations

Alecsaunders
Congratulations (I think) to my friend Alec Saunders for taking a new role as "VP of Developer Relations and Ecosystem Development" for Research In Motion (RIM), makers of the Blackberry line of mobile devices.

Or perhaps condolences are in order... somehow he has to make developing for the Blackberry sexy again to all the app developers who focus these days on the world of iOS/iPhone/iPad and the Android platform.

Alec certainly has his work cut out for him. As he writes in his post today announcing the news:

Over the last few days I’ve been in San Francisco at the Mobilize conference, and speaking with developers. It’s clear from those conversations that the primary problem we face is lack of support from application developers. My team’s job is to correct that – to win the hearts and minds of mobile developers again.

"Lack of support" probably doesn't go far enough as a statement. Any of a zillion charts will show you Blackberry's rapidly declining marketshare (particularly in the US). iPhones are dramatically outselling Blackberries and Apple is poised to launch iPhone 5 / iOS 5 / iCloud next week, pretty much assuring even more of a boost to the iOS platform and developer ecosystem.

On the Android side, recents stats show twice as many people buying Android devices as iPhones... and today's mega-launch of the Amazon Kindle Fire tablet is going to light an even larger flame under the Android ecosystem.

Plus, add in Microsoft and all they are attempting to do with the Windows Phone platform...

And somehow... in the midst of all of this...

Alec is going to try to get developers excited about developing apps for the Blackberry???

Not just for the Playbook, mind you, but for the traditional Blackberry platforms of "BBOS" and the new QNX platform. As he says in an interview posted on RIM's Blackberry Developer Blog today:

Developer evangelism is all about personal contact, listening, responding, and educating. We’re going to work very closely with the developer community, expand on support and programs that make it easy and rewarding for developers to create apps, be in the midst of developers to understand their needs and secure a great developer experience, and identify and remove the barriers developers face in supporting our platforms and doing business with us.

It's a tough task, made even more challenging by RIM's recent earnings report (or lack thereof), but if anyone has a hope of pulling it off, it's Alec. He's an exceptional communicator, marketer and salesman... and brings both a great technical depth and ability to communicate in "regular" language.

I do seriously wish him all the best! I've been a long-time fan of the Blackberry, even though I myself changed mine in for an iPhone back in 2008 or so. RIM has done some pretty amazing things in the mobile market, but as Gizmodo recently noted ("How RIM Could Save Itself"), RIM tied itself to the enterprise so tightly that it missed out on the rise of smartphones in the consumer space - and the corresponding move of those "consumer" smartphones back into the enterprise.

What will their future look like? Can they win back developers? Can they make the Blackberry ecosystem sexy again? Can it claw its way back into being a player in the smartphone market?

Alec's got a challenge before him - and I look forward to seeing what he'll do!

P.S. Up to join in the challenge? As Alec notes at the bottom of his blog post, he's hiring developer evangelists...


Other notes about Alec's new role:


Image credit: me. Taken at ITEXPO East 2010 in South Beach, Miami :-)

Awesome 1954 Bell System Video – How To Dial Your (Rotary) Phone

Started off this morning getting a great laugh out of this classic 1954 Bell System video tweeted out by Larry Cannell. Amazing to think back to the time when the system was changing from just picking up the phone and speaking with an operator to a new system where you "dialed" the phone.

Really the start of the self-service automation of the phone network that we take for granted today.

Fascinating to see the glimpses, too, of the "internal networks" as they "pulled the fuses" from the manual systems and flipped switches on the dial systems. I love the guys pointing a "Go!" finger at the teams to make the transitions!

Of course, you have to wonder how many young people growing up today in the United States have even seen a true rotary dial phone! (We who used them should write down some of our memories before they are forgotten...)

Anyway, enjoy this window into a different time:


If you found this post interesting or useful, please consider either: