IMS UA for Android

9 03 2009

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:

Read the rest of this entry »



and now MSRP and RTP for Android

20 01 2009

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.



STUN stack for Android SDK 1.0r1

17 11 2008

Hola,

continuing the “season of giving” for Google’s Android, HSC has also ported the popular java stun stack, JSTUN for the android platform. Download it here

 



SIP UA for Android (+stack + RTP) released

29 04 2008

Update: Nov-20-2008: Updated SDK + UA for 1.0 SDK released here. Also released jSTUN port for android here.

 

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 »



Mjsip SIP stack port for Google Android released

2 04 2008

1.jpg

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 :-)



We have SIP working on android!

10 03 2008

 Update: April 2 2008: Source code of stack released here 

1.jpg

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 have taken the GPL’d mjsip SIP stack and our objective is to make it work on android (this is mostly a porting activity). We are not writing our own stack.
  • We are not doing any optimizations, etc. The scope is exactly what I wrote – make mjsip work on android, so developers can use the mjsip APIs to build apps in android.
  • It is a very straighforward ‘take from community (GPL/mjsip), give back to community (post ported code back to GPL/mjsip)’ activity.
  • We are targetting to release the port in a week or so… (as-is – as I mentioned the objective is straighforward -a port of mjsip – if it has bugs when you do funky stuff , fix it yourself when we release it :-) )

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!



A call to report: VoIP ‘geek-talk’ blogs

11 02 2008

1.jpg

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


My presentation at the Internet Telephony on IMS, WiMAX and all things nice

14 09 2007

I spoke at the Internet Telephony conference in Los Angeles last week on IMS, hWiMAX, how they all work together (or not) and what it really means to applications. You can see a copy here



Speaking at Internet Telephony and our latest IMS report

4 09 2007

Hi folks,
My apologies for the lack of postings. It just so happens that Sep/Oct/Nov are the worst three months for travel for me. I have been on the road for most part of this month and will be all over the map till the end of November.If any of you are going to be at the Internet Telephony Conference in LA, I hope to see you there. I will be speaking on Monday about “IMS vs. WiMAX” there. So if you are attending, would be good to meet. On another note, I’ve been speaking and attending at the Internet Telephony show for several years now, and I must say, Rich Tehrani and the team has done a great job over the years in being innovative. For this show, as an example, they have come out with innovative interviews, video clips and press releases which help in advertising both their name and the participating company’s name. Good on you, Rich! I hope other setups pick up a bit on the ideas these folks have implemented.

On another note, we have just released our July-Aug 2007 IMS Tracking report. You can read an executive brief here.



IMS: Ideal Architecture for Quadruple Play for Operators

29 05 2007

The July 2007 IEC publication, titled “Beyond the Quadruple Play: Networking, Convergence, and Customer Delivery” will feature an article I wrote on behalf of my company which talks about why I think IMS is the ideal architecture for such a network.
The download link to the paper is here (Sorry for the indirections, but as I said, I am liberally going to promote my official blog here to – don’t complain – you ain’t paying *grin* )
Abstract:
Broadband IP is a great leveling ground when it comes to converged services being offered by multiple providers. For example, with the availability of Broadband, companies such as Vonage could offer IP based phone replacement solutions threatening the turf of established phone operators. Similarly, Comcast can now suddenly offer Cable VoIP (phone service) and Verizon can now suddenly offer TV services over IP, thereby threatening each in service areas that were traditionally never their turf. Broadband IP has also enabled ‘new kids on the block’ like Skype, Joost and others to offer bundled services that threaten the trillion dollar communications industry as we know it. This is one main reason why carriers are competing to stay alive with “Quadruple Play” blended services that offer Voice, Video, Data and Wireless accessibility into one.
However, providing Quadruple-Play across heterogeneous networks (WiMAX, DSL, Cable, cellular etc.) is a non-trivial task and one needs a robust and well thought out architecture which ensures that services can be provisioned and provided uniformly to subscribers in a way that lends to seamless user experience and operator provisioning/charging and billing.
This paper describes the merit of IMS (IP Multimedia Subsystem) – an over-arching
architecture specification that enables uniformed IP based service delivery over diverse network types (WiFi, DSL,WiMAX, Cellular technologies etc.) as the ideal architecture for operators to deliver Quadplay services to their users.