Wojciech Kaminski is a developer and a team leader at Javart Sp. z o.o., a Polish IT consultancy with several companies in the telecommunication industry as customers. He came to the session because he is interested in different telecommunication solutions in general.

“Before coming to JavaOne, I didn’t know about SailFin and hadn’t really had that much to do with SIP either. So that is why I came here, to learn more,” he says. “The talk was really good, and I am definitely going to check out the web sites for more information and try out the product.”

Kaminski thought that the high availability features of SailFin were especially interesting. SailFin incorporates both a load balancer, which makes sure that the processing of incoming messages and notifications are distributed evenly on the application server, and an innovative solution for replicating sessions. By automatically replicating sessions, they can be reinstalled immediately without interruption in case the original session fails.

Kaminski is currently working on a telecommunication project for Nokia Siemens Networks. Before the talk, Kaminski was more familiar with another standard for telecommunication application development called JAIN SLEE (Java APIs for Integrated Networks, Service Logic Execution Environment).

“JAIN SLEE seems to be more a pure telco standard though, while SIP servlet enables convergence more easily, which is a big thing for the telco industry – to bring telecommunication and internet services together,” Kaminski says. “SIP servlet seems to be a more developer-friendly standard as well.” Gronowski was pleased with the outcome of the talk.

“The talk was well received, I think,” he says. “Some attendees asked questions and were engaged in a discussion after the session, so the session sparked some interest. One attendee wondered how to connect and manage several SailFin servers, which is a good question. At Ericsson Research we have a good solution for this called the Composition Execution Engine, and AT&T has an open-source solution called ECharts.”

By Olle Blomberg

ECharts
Ericsson Review article about Ericsson's Composition Execution Engine