You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2010/07/14 07:31:52 UTC
[jira] Commented: (CAMEL-2943) A Camel component that implements
the Telecom SIP protocol for Publish/Subscribe capability...
[ https://issues.apache.org/activemq/browse/CAMEL-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60646#action_60646 ]
Claus Ibsen commented on CAMEL-2943:
------------------------------------
Ashwin we will take a look after the dust of the Camel 2.4 release has settled.
Please refrain from committing big changes to the trunk, in case a new 2.4 release has to be cut etc. Its best to only commit bug fixes until the 2.4 is GA.
> 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.