camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ashwin Karpe (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CAMEL-2943) A Camel component that implements the Telecom SIP protocol for Publish/Subscribe capability...
Date Sat, 17 Jul 2010 22:50:52 GMT

    [ https://issues.apache.org/activemq/browse/CAMEL-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60727#action_60727
] 

Ashwin Karpe commented on CAMEL-2943:
-------------------------------------

Hi Hadrian,

I used the OpenXCAP as part of an engagement to prove that the solution works. Unfortunately
OpenXCAP has a GPL License version 2 which is not compatible with the Apache 2 License.

In the absence of this I developed my own presence agent which can be instantiated as an endpoint
by the SIP component and used for Unit and Integration Testing. It works well and can be used
to prove the capability of SIP endpoints doing publish/subscribe.

I have included a unit test with the SIP component that shows this in action.

Hope this helps.

Cheers,

Ashwin...

 

> A Camel component that implements the Telecom SIP protocol for Publish/Subscribe capability...

> -----------------------------------------------------------------------------------------------
>
>                 Key: CAMEL-2943
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-2943
>             Project: Apache Camel
>          Issue Type: New Feature
>            Reporter: Ashwin Karpe
>            Assignee: Ashwin Karpe
>         Attachments: camel-sip-20100714.zip, camel-sip.diff, jain-sip.zip
>
>
> The Telco SIP protocol has operations to perform Publish and Subscribe of Telecom events
via a Presence Agent (similar to a Broker) as an intermediary.
> Develop a Camel SIP Component that can communicate with a Presence Agent (also add a
basic Presence Agent with no persistence). The SIP Component should as a consumer, subscribe
to messages from a Presence Agent and support the SIP protocol handshake and as a Producer
publish messages to a Presence Agent.
> The SIP protocol involves communication over HTTP with specific acknowledgements that
need to cater for different situations. This communication pattern and handshake must be properly
supported.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message