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

ASF GitHub Bot commented on CAMEL-10321:
----------------------------------------

GitHub user Fabryprog opened a pull request:

    https://github.com/apache/camel/pull/1180

    Camel 10321

    https://issues.apache.org/jira/browse/CAMEL-10321

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/Fabryprog/camel CAMEL-10321

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/camel/pull/1180.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1180
    
----
commit 5a198305600d62a88030d9649a1b9b45517e86a6
Author: Fabrizio Spataro <fabrizio.spat...@bizmate.it>
Date:   2016-09-15T16:08:23Z

    CAMEL-10321, camel-asterisk component (without test and doc)

commit dad6af0e7333e1566fd573d8a0bd18e7aa318fa3
Author: Fabryprog <fabryp...@gmail.com>
Date:   2016-09-16T21:25:59Z

    CAMEL-10321, Asterisk Component: test added

commit ff16f2838d29171c8006e6b427acee48b9b7db96
Author: Fabryprog <fabryp...@gmail.com>
Date:   2016-09-16T22:15:14Z

    CAMEL-10321, Asterisk Component: documentation adoc

commit 9c0d3a1318f3cd88d3abb9f6d35838faa6a7acec
Author: Fabryprog <fabryp...@gmail.com>
Date:   2016-09-16T22:22:46Z

    CAMEL-10321, Asterisk Component: fix rename class

----


> New Component camel-asterisk
> ----------------------------
>
>                 Key: CAMEL-10321
>                 URL: https://issues.apache.org/jira/browse/CAMEL-10321
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Fabrizio Spataro
>
> Hello,
> i wrote a component to send and receive event from an asterisk VOIP server.
> Can i send my PR? Is it compatible with apache camel code license?
> King Regard



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to