camel-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <>
Subject Re: Announce: OCS/Lync compatible SIP Producer endpoint
Date Thu, 01 Dec 2011 19:13:53 GMT
Hi Arkadi

Nice to see you at the Java Riga Day.

Congrat on this release. Seems like yet another valuerable Camel component.

You may consider adding a SipeConfiguration class or just
setter/getters on a SipeComponent.
Then people can configure once common configuration, if that makes sense.

Then the endpoint uri could be reduced, as the endpoint will fallback
and inherit the configuration from the SipeComponent.
This is what we do in some of the Camel components.

But this only makes sense if different sipe endpoints, would have
common configuration.

On Sun, Nov 27, 2011 at 8:45 PM, Arkadi Shishlov
<> wrote:
> Hi!
> I'm please to announce the availability of open-source implementation of
> OCS/Lync compatible SIP Producer endpoint.
> The source is licensed under Apache license.
> Thanks to my friends who made this release possible.
> See you at Java Riga Day 2011!
> Some bits of code - thats deals with NTLM signatures are
> modeled from jCIFS (LGPL v2.1+) class of the same name. But similarity ends
> here, so I put the Apache license banner on it. If you think there are
> problems with code licensing - just let me know, and I'll try to find a
> consensus.
> The source can be built standalone or put into Camel tree and built there
> with minor pom modifications. jCIFS library must be installed into local repo:
> mvn install:install-file -Dfile=jcifs-1.3.17.jar -DgroupId=org.samba.jcifs \
>   -DartifactId=jcifs -Dversion=1.3.17 -Dpackaging=jar
> The implementation is fully thread-safe in a sense that SIP state-machine
> is protected by synchronized functions to keep things simple and
> race/deadlock-free, at least for the initial release. It does not mean the
> performance is bad. Not at all! Some highlights includes:
> 1. supports sending of multiple messages to multiple users to multiple
> servers in parallel
> 2. event-driven state machine caches presence information and dialogs
> 3. uses Camel asynchronous processing
> 4. uses EPID and GRUU MS REGISTER extension
> 5. uses enhanced presence MS SUBSCRIBE extension
> 6. works with OCS clustered server pool
> 7. multiple endpoints could be instantiated (on different ports) to
> connect to different OCS/AD domains
> 8. multiple endpoints with different URL-s may share single SIP stack
> (some coding is required to detect incompatible configurations)
> 9. properly calculates SIP request/response NTLM signatures, EPID ->
> +sip.instance magic is also there.
> Tested against OCS 2007R2 and Lync.
> At present, only Producer part is implemented, but it could be easily
> extended in a day or two to provide the Consumer. I just didn't get to
> the business case where the Consumer functionality would be necessary.
> There are still some internal implementation deficiencies, but I believe
> that even in the current state it could be considered for a pre-production
> deployments.
> So, I invite you to review and use the code with a hope that in some near
> future it will land in the official Apache Camel source tree.
> Even though you're not a Camel user, you may find it educating in case you
> wish to know how to develop with JAIN-SIP and/or how inter-operate with
> Microsoft-extended SIP.
> Kudos to Camel, JAIN-JIP, and Pidgin SIPE developers who also made this
> possible!
> Usage example:
> from("jetty:http://localhost:1112/inbound")
>   .setHeader("To", constant("lynctest"))
>   .to("sipe://"
>   + "toUser=lynctest&" // used if not set via To header
>   + ""
>   + "fromUser=lynctest2&"
>   + ""
>   + "fromPort=5066&"
>   + "ip=eth0&"
>   + "authUserName=lynctest2&"
>   + "authPassword=***&"
>   + "authAdDomain=exampledom&"
>   + "transport=tls&"
>   + "debugLog=/tmp/jain-sip-debug.log&"
>   + "presenceList=3500,5000,15500,12500");

Claus Ibsen
Twitter: davsclaus, fusenews
Author of Camel in Action:

View raw message