iConverged

So the rumors of many years ago were true. Google finally did release a browser. Naturally, I downloaded it and took it for a test drive. Here is the short of it.

Version reviewed:

Google may be rolling out updates regularly (For example, I suddenly see evident popup blocking), so to put it in context, this is the version I am reviewing

Installation:

The installer is just around 470K to download, but of course that is the ‘pre-installer’. Once you grab the pre-installer, it downloads the rest of the browser from the net. As of now, in its first release, focus seems to be on super simplicity. It does not even ask you where to install it. I am OK with that, but it really does choose a weird location to install it (in Documents and Settings!)

(click on any image to see a full size version)

Read the rest of this entry »

Image credit

Yahoo recently launched Fire-Eagle, which is essentially an ‘open platform’ that allows two simple things:

A) Users can update the system whenever they want with their location

B) Application Developers can access the system whenever they want to know the location of consumers and do anything with it (i.e. serve any application that can make use of that information)

Of course, ‘Users’ can explictly set permissions on who can or cannot view their location.

For a long time, I have wanted to see such an open and simple platform, where ‘executing a service based on location’ is completely independent of ‘the technology used to provide the location’. Because I believe providing individually accessible repositories of data is the key construct to building a hierarchy of innovative products. You collect data, expose it to others so they can transform your data into information. And your information, is data for the next application. So turns the wheel of the Web 2.0 circle. And a location repository is one key missing element to personalize services.

Read the rest of this entry »

(image credit to Engadget)

Ever since iPhone SDK got released, we have seen a lot of requests from customers wanting us to build iPhone apps. Naturally, we have loved to oblige -after all, we love hacking on new platforms.

The biggest problem, however, was not being able to run background applications, which KOed out a lot of neat things one could do, especially for location related apps. At the keynote today at WWDC, Scott Forstall said this:

Read the rest of this entry »

If you are in this emerging ‘applications’ market, and are in the business of building applications for OEMs/ISVs or Service Providers (yes, some Operators actively invest in R&D work), the term ‘Rapid Prototype’ is not new to you. In short, people are always looking at ‘quick and dirty’ demonstration code that shows off a cool concept which they can take to prospective customers as a viable product or service to be rolled out. Customers who ask for this are not sure if that idea will go anywhere, but are willing to test the waters with you (if you are willing). A typical software development organization follows the ‘Build Rome one stone at a time’ model whereas this particular market needs the ‘pre-fab modular home in 1 month’ model and therefore struggles with this particular market. I know of many organizations who  believe this is not an area to be in, because of the limited scope and length of such projects. The problem however, is that they fail to understand that this market is actually very attractive and profitable, but only if you look at it the right way, and approach it the right way. Last week, I was chatting up with a friend on the same issue and was sharing some insights into what one should try and institute to make this model work. He suggested a blog post, so here goes - some common problems, pitfalls and solutions:

Read the rest of this entry »

Hi folks, as promised, HSC released the ported SIP UA including the stack. This is an update to our previous ’stack only’ release. We have overwritten the old release with this new one in our download area. You can get it from here (look for the post titled “SIP UA + Stack for Google Android).

This release includes a short illustrative manual on how to use the SIP client and some things you need to do to configure it (mostly because of the limitation of the android emulator and what it does(not) support as of the current date). We have also included a ported RTP stack with this release. Theoretically, this release is all set for a signalling + media use case. I say theoretically, because it seems the android emulator does not support audio capture, so everytime one tries to start a media conversation, the emulator crashes. Folks @ the android-dev group have confirmed this is currently not supported in the emulator (but works on their actual phone).

Read the rest of this entry »

Update: Apr 29 2008: UA+Stack code released here

Hey folks, HSC released the android ported mjsip stack source code.

Grab it from here. Look for the attachment to the post titled “Ported GNU Mjsip stack for Google Android”

If you see a “PDF” icon under that post, don’t worry, its actually a ZIP with source in it. Our website folks will fix that annoyance soon.

Note that this is a “developer’s release”. It will allow you to start building applications using the mjsip stack on android. It’s not an “automatic solution for long distance calling” (as some blogs reported it) - it is a tool for developers within you to make such applications.

We also have a working SIP UA we ported on top of this stack (which we called ‘SIPDroid’ - no points for being imaginative here). We are yet to release that port - will do so in a short while.

Note that this is just a SIP stack. There is no RTP included. We did some initial experiments with porting open source RTP stacks - seems very simple. We may just do it later, or you do it and add to this effort

For those who attended VON spring, it is likely that they thought it was particularly low key in terms of attendance. I was there, both at the main event and the unconference (which was interesting, especially with Ken’s ‘online’ proposal to his partner Sheryl which was covered using Qik, a company started by Ramu Sunkara - ex head of RTC @ Oracle & a really inspirational guy. Congrats Ken & Sheryl, glad we finally met after reading each other’s blog for a long time - you make a great couple).

But I digress. Back to VON San Jose. The Boston and San Jose VONs have always been very well attended. So I was surprised seeing the attendance. But then again, I thought, maybe I shouldn’t be surprised. And maybe it is also a testament to how well VON has actually worked.

The ‘Hype’ of many technologies like IMS, WiMAX etc. have passed. If you look at the typical exhibitor space of VON, they are OEMs. OEMs build products before they get deployed. They need to publicize. They need to excite people. And that is exactly where VON helps them. When technology is ‘new’, you need forums like VON to spread the word. When technology gets into deployment, people are too busy deploying to actually attend shows and talk about them. This is when the ‘money gets real’. The hooplah is over. And this is exactly in line with what I am seeing in the market. I had posted earlier that we have started seeing a significant rise in people deploying applications over IMS, or, deploying IMS and they are paying money for it (not the build and we will see story).

Read the rest of this entry »

Whoever said mashups must only be ‘web-based’ ? I’ve been tinkering with Adobe AIR for a while now, and I must say, I am really impressed.

What is Adobe AIR? Well, essentially, is a platform which allows us to build applications using ‘Web technologies’ like HTML, CSS, AJAX as well as Flash/Flex, but instead of building a 100% web-based application, we can build a ‘hybrid’ desktop application. Here is why I love what I see :

Read the rest of this entry »

Update: I have now created a sidebar widget titled “Tech Blogs I read” instead of updating this post. Please continue sending me quality tech blogs (with more focus on concepts and less on marketing) as you come across them and refer to the sidebar for updates and not this post - thx.

Total number of ‘market reporting’ VoIP blogs = k+1

where k=number of times you can blink in a day.

However, there are very few blogs that talk about more technology & architecture details and less market details for all things VoIP, SIP, IMS, web 2.0 (with focus on telecom).

So here is a call to unite!

We need a list of what I call ‘geek-talk’ - those that provide more technical insight into how things are.

Here is my list so far. Please update me /comment here with more tech-blogs and I will update this list

Many of these blogs are a mix of techno-marketing, but are written by people who are neck-deep in actually developing/architecting many of the talked about solutions themselves, and hence offer a more detailed insight.

last updated: Apr-30-2008

1. TurnGeek - focus on P2P, SBC, etc.
2. IMS Lantern - IMS architecture related
3. Voice of VoIPSA - VoIP Security
4. IMS Quality - Testing and Monitoring with focus on IMS
5. VoIP Survivor - general voip, with significant focus on their company products
6. TelCAB - IMS B/OSS
7. iConverged - this blog

I recently wrote a paper that investigates how SDP vendors can provide AJAX based telco-aware libraries and mechanisms to interface these libraries with existing telecom application servers. I personally believe that this is a gaping hole in the market. While AJAX libraries have evolved significantly, no one is currently working on adding functionality that makes it telecom aware (in terms of understanding what UI, actions, events are typically associated with telco services) thereby making t he job much harder on developers who are trying to grapple with what it really means to “web 2.0″ their SIP call control app.

Abstract:

With the increasing acceptance of AJAX as a mechanism to deliver real-time user experiences without the need of proprietary local clients and the increasing demand from consumers to have a better user experience with more features, both the Telecom and the Internet world are looking at means to be able to converge their offerings. However, being able to provide converged services is a challenge largely due to the fact that Telecom players already have existing applications they would like to monetize in addition to having limited know-how of Web 2.0 related technologies, whereas the Internet players, while proficient in Web 2.0 technologies have limited understanding of wireline and wireless networks to be able to offer ubiquitous service access. The author believes that middleware SDP providers can help bridge this gap and provide “convergence” building blocks that would allow developers on both sides of the world develop functionality, or integrate existing functionality with ease. Specifically, this paper, proposes the concept of “TelcoAJAX” – a set of building blocks that are aware of telecom primitives and how to represent and interact with users using a browser interface which developers can implement on top of SIP/Presence based applications.

You can download it from here.

(Search for paper titled “A Concept Approach at bringing Legacy Telecom Application Servers to Web 2.0″)