Skip to main content


Binod P.G is an Architect in the CGBU division of Oracle Corporation. He is the architect of OCCAS and WSC products and also lead SIP Servlet expert group. Previously, at Sun Microsystems, he was an architect of the Project SailFin and a co-specification lead of the Java EE Connector Architecture 1.6 Expert Group . In the past, he was involved in the development of many areas of the glassfish applicaton server, including Java EE Service Engine, Server Startup, Connector 1.5, JDBC, Connection Pool and JMS provider integration. He is also one of the owners of Generic Resource Adapter for JMS project. Prior to joining Sun in 2000, he has worked on a number of server side software technologies including IMS PL/1 programs in IBM Mainframes and internet projects in Microsoft IIS.


binod's blog

SailFin V1: Step by step guide to get started.

Posted by binod on February 10, 2009 at 8:05 AM PST

SailFin V1 is released. This post explains the basic steps by which you can get started with SailFin V1 and write a simple sip application.

Writing your first application router with SailFin

Posted by binod on February 10, 2009 at 6:03 AM PST

When a web server receives an http requests, the server identifies which application need to be run, depending on the context-root of the request. However SIP communication is designed to be between two parties and the message does not contain something like context root to identify the application.

MySQL-SailFin webinar

Posted by binod on January 15, 2009 at 10:55 PM PST

The Service Execution Environment is a key layer of any Service Delivery Platform (SDP), and the application servers and databases are the key components of this layer. MySQL and SailFin (GlassFish) fit in very well into the Service Execution Environment.

SailFin: Record-Route issues with SIP

Posted by binod on December 18, 2008 at 9:06 AM PST

Let me explain this issue, step by step.

What is Record-Route?

SailFin: Join and Replaces support, Part II

Posted by binod on November 20, 2008 at 8:27 AM PST

In the first part of this blog, I explained how a third person Join a call between two parties. This part explains how one party is replaced by another in a call. RFC 3891 specifies Replaces SIP header, that help SIP applications implement this capability.

SailFin: Join and Replaces support, Part I

Posted by binod on November 14, 2008 at 1:32 AM PST

In a typical customer support scenario, a customer support executive (E) might want his manager (M) to join his call with a customer (C). How to achieve that? In SIP world, Join header specified by RFC 3911 helps in handling this situation. It defines a new header named Join, which holds the call-information.

SailFin news: Milestone 6, 289 TCK passed

Posted by binod on November 10, 2008 at 9:07 AM PST

SailFin V1 MS6 is now available. Prasad reports that there were more than 141 bug fixes after MS5 that went into this release.

SailFin: Crucible for Code Review

Posted by binod on September 24, 2008 at 7:43 AM PDT

This time, my work had about 800 lines changes/new lines spanning 16 files and was implementing two RFCs. All that was plain simple java code and not very complicated, but still the worry I always had about presenting the changes to the reviewers (in different geos) came up on my head. It is still my code and not their code.

MD5 Authentication example for converged applications.

Posted by binod on September 21, 2008 at 9:21 PM PDT
In last couple of months, I received many e-mails seeking information on how exactly a converged application can be configured for authentication in SailFin.

SailFin V1 Alpha is available now!

Posted by binod on August 13, 2008 at 12:42 PM PDT

JSR 289 went final less than a month back. And we have the first implementation of JSR 289 at alpha stage available now. SailFin V1 Alpha has been released.