Jim Machi : Industry Insight
Jim Machi

API of the Week: BetterWorks Boosts Business Performance

As digital transformation continues to gain traction, companies are looking for the competitive edge only achievable by integrating leading edge software solutions...

Full Story »

Change: Musical Chairs

This has to be the busiest year ever for musical chairs. People are company hopping like crazy. And companies have been...

Full Story »

Voice Revenue Decline - Scary or Under Control?

In March, Chetan Sharma released a 2015 US Mobile Market update report.  There are many interesting points in this report, but one thing...

Full Story »

Tech Culture Awards Status

One of the most exciting projects we’ve been working on here at TMC is our Tech Culture Awards… This award program...

Full Story »

Brexit Could be Yuuuge for China

A freer people are a happier people In the past eight years world history has changed in an unprecedented way. Just this...

Full Story »

Bitcoin, Blockchain and FinTech to the Brexit Rescue

The One Industry Unaffected by Brexit is RansomwareIt’s undeniable that there is a chance that after seeing Britain leave the EU that...

Full Story »

The Struggle of the Channel Managers

One big struggle of the channel managers is to get agents to sell deeper into accounts. The providers would like more...

Full Story »

"The contact center use case looks like a natural for WebRTC, but how will that work?"

April 24, 2013

“The contact center use case looks like a natural for WebRTC, but how will that work?”

From our company’s viewpoint, implementing many of the WebRTC use cases in the modern contact center is a matter of normalizing the media and signaling streams between systems to interface with the existing service. The telco perspective in this context doesn’t mean exclusively carriers or service providers, but a wider view of enabling WebRTC endpoints to access known communication services or solutions, such as a contact center.

While our on-demand webinar described a click-to-call WebRTC use case that may already be emerging in the market, another use case has cropped up that is a practical application in the area of agent login and soft-clients.  

Impact of the New Video Codec H.265

April 23, 2013

In January, a new video codec called H.265 (also known as High Efficiency Video Coding (HEVC) was approved by the ITU-T.  This is significant for a couple of reasons:

It needs only half the bit rate of the best codec out there today (H.264) to provide the same or similar quality video.  You can even see it in this YouTube video.

"Where do IMS and WebRTC Intersect?"

April 17, 2013

The IP Multimedia Subsystem (IMS) is an architectural framework for delivering IP multimedia services. It is based primarily on SIP as a rich, real-time media session protocol for IP networks, and as such, relies on SIP-based endpoints and soft-clients to register and support subscribers on the services (at least those services that are truly multimedia in nature with HD voice and video interactivity, and not ‘skinnied’ down through gateways to a narrowband voice service).

The care and feeding of SIP client applications that enable the IMS service subscribers represents a considerable effort and cost to carriers for their on-net IMS service subscribers. Extending the IMS service reach with soft-clients to off-net endpoints, meaning those that are on other carriers broadband and mobile networks, presents another set of challenges, including various app store navigations and negotiations.

WebRTC Webinar Q&A #2 "Why WebRTC when we have Skype?"

April 17, 2013


“Why  WebRTC when we have Skype”?”

This is a really good question.   After all, Skype is the dominant real-time communications technology on the web with hundreds of millions of users and isn’t very hard to use. 


LTE / Diameter Interworking (Part 2 of 2)

April 11, 2013

Two days ago, I wrote a blog about Diameter Interworking use cases.  If you are a network operator, are these issues real? Well, they’re real enough that the 3GPP and GSMA have identified elements called Diameter Routing Agent (DRA),  Diameter Edge Agent (DEA), and Diameter Interworking Function (IWF), which is more closely aligned to the interworking described above.

Given that these issues are real, how do you address them?  For starters, operators need a box that connects the carrier LTE/IMS and policy control environment to existing 2G/3G/Wi-Fi and back office environments.

LTE / Diameter Interworking (Part 2 of 2)

April 11, 2013

Two days ago, I wrote a blog about Diameter Interworking use cases.  If you are a network operator, are these issues real? Well, they’re real enough that the 3GPP and GSMA have identified elements called Diameter Routing Agent (DRA),  Diameter Edge Agent (DEA), and Diameter Interworking Function (IWF), which is more closely aligned to the interworking described above.

Given that these issues are real, how do you address them?  For starters, operators need a box that connects the carrier LTE/IMS and policy control environment to existing 2G/3G/Wi-Fi and back office environments.

LTE / Diameter Interworking (Part 1 of 2)

April 9, 2013

Last week, I wrote a blog about Diameter protocol and its application use cases.  Since LTE uses it as a signaling protocol, operators have a need to interwork Diameter with the signaling technologies used in other mobile networks. This has given rise to the Diameter Interworking Gateway function, which moved onto the center stage at Mobile World Congress this year. It’s a critical element to enable the successful rollout of LTE and a seamless user experience across different networks.

WebRTC Webinar Q&A #1 "Is WebRTC 10 years too late?"

April 4, 2013

“Is WebRTC 10 years too late?”

To properly answer this question, one needs to take a position.  One position is to assume that all the VoIP “stuff” that came before Web Real Time Communication (WebRTC) is kind of useless.  But moving to a world where SIP, G.711, and H.264 are the dominant real-time communication protocols and codecs over IP networks is not useless. 

Diameter Use Cases

April 2, 2013

Diameter is the key signaling protocol used in IMS and LTE networks that enable applications running on those networks to authenticate, authorize and charge. In other words, your mobile applications, when running on these networks, are using Diameter protocol in the background to enable you to utilize the many apps on your smartphone or tablet. This includes, for example, a location-based service type of application (such as Foursquare or Yelp), or mobile payment (such as Square), or an Internet purchase (from an app store online retailer like Amazon).

Given the huge amount of smartphones and tablets out there that are either now running on LTE networks are that are expected to be LTE-enabled in the future, I predict that will be a big increase in Diameter signaling traffic.

My Mobile Device History

March 26, 2013


As some of you readers know, I have been an avid Blackberry user for some time. That time has now past.  I am an equal opportunity device person, and have used Motorola, Nokia and Blackberry devices.  It was time for a new one.


Featured Events