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

Claus Ibsen commented on CAMEL-2943:
------------------------------------

The maven repo we have listed in our pom.xml should generally use the same id.

So can you lookup an existing component which uses the jboss repo such as 
camel-netty and use the same id as it?
{code}
        <id>sip</id>
{code}

Nexus servers and whatnot requires to use consistent ids.

> 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-20100823.diff, camel-sip-20100823.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.

Reply via email to