Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
Message-ID: <8602004.41811279109272070.JavaMail.jira@thor>
Date: Wed, 14 Jul 2010 08:07:52 -0400 (EDT)
From: "Willem Jiang (JIRA)" <jira@apache.org>
To: camel-dev@activemq.apache.org
Subject: [jira] Commented: (CAMEL-2943) A Camel component that implements
 the Telecom SIP protocol for Publish/Subscribe capability...
In-Reply-To: <19715249.41251279083411858.JavaMail.jira@thor>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit


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

Willem Jiang commented on CAMEL-2943:
-------------------------------------

Hi Ashwin,

I just found there are some jain-sip artifacts in http://download.java.net/maven/2/javax/sip, can you check if you can use them ?

> 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.