Hi folks, as promised (over and over earlier 
we finally have an initial version of the IMS UA ready for download. The IMS system we used was Open IMS
Grab the IMS UA code from the HSC Open Source webpage here
(look for IMS UA for Google Android Entry)
The test bed looked like this:
Some more goodies from HSC.
MSRP for Android and RTP stack for Android. And yeah, these releases don’t have additional documentation answering stuff like ‘how do I install’. We hope you know that already 
And if you need docs on how to use the stacks, please refer to the original open source efforts.
Get them here.
Folks, my company just released an updated version of the SIP stack and UA (MJSIP) ported for the latest SDK 1.0r1. This is the same SDK that G1 uses. This is an update to this post.
The new SDK changes several things in the UI and well as some APIs. Kudos to the team lead Nitin Khanna (first.last at hsc.com) for continuing the commitment to android.
Grab a copy of the latest version from here.
(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:
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).
Update: April 2 2008: Source code of stack released here
Hey folks. Enjoy this screencast of a working Android enabled SIP Phone (using mjsip) talking to an X-lite phone.
This is an update to the original “We have SIP working on android” post.
Click here to view the screencast
(And here is the wireshark dump for the protocol hungry)
So there you go. It’s real
Code/howtos etc to be posted in a few days
Update: April 2 2008: Source code of stack released here
Update: Mar 17 2008
See here for a screencast
Update: Mar 12 2008
Some other sites linking here seem to be reporting this news with their own verbiage. Lets be specific on what we are doing:
) We (my company) had started an internal project to get SIP working on Android and some smart folks belted out some nifty code to get SIP working on android. We hope to release the ported SIP stack on android pretty soon. We used the GPL’d mjSIP stack and will be releasing the modifications as per GPL, obviously – so other developers have a good SIP API to build apps. This should happen pretty soon. Some time ago, we did a rss-to-presence implementation stub (concept here) over Google Mashup editor. I look forward to seeing the “google-phone” talk SIP to the “google-server” and other cool stuff.
Stay tuned!
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
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″)
Subscribe to feed, or
Get new posts by Email