Telecom API's


The Telecom Operators that relied in voice services are dead. And today’s operators fight for their own existence in a world dominated by the Web 2.0 where services can be created, combined in matter of day’s if not hours by limited resources teams. This new playground poses several challenges to telecom forums that have in the last years devised several API’s for enabling developers to plug in to their network. The following table has the particularity of synthesizing what’s going on.

API Strengths Weaknesses
Parlay/OSA Can be implemented in both TDM and IP networks The role and future of parlay services is unclear; Deployed mostly in wireless networks only
Parlay X Broad range of telco APIs with Web API support via Parlay X SIP-based service model is preferred approach for NGN and IMS
SIP-Servlets Defined by 3GPP as the standardized approach in the IMS Application Layer Services utilize SIP protocol with which Web developers have limited experience
JAIN SLEE Protocol Agnostic (therefore supports SIP too); Provides the capability to migrate legacy Intelligent Networks to new platforms Complex service creation environment; Telco development skills required; Limited vendor commitment

This table has been adapted from here

IMHO we are going the way of SIP-Servlets. The reason ? From all of the options it’s the easiest! and that has been the rule of thumb for all the Web2.0 developments.

written by Diogo Gomes