[asterisk-dev] Asterisk support of SIP Connect 1.1

[Neeharika Allanki]

Hi David,

This is what Paul Belanger- Software developer from Digium replied back with. 

Thanks,
Niharika

-----Original Message-----
From: asterisk-dev-bounces at lists.digium.com [mailto:asterisk-dev-bounces at lists.digium.com] On Behalf Of Paul Belanger
Sent: Friday, August 19, 2011 3:40 PM
To: asterisk-dev at lists.digium.com
Subject: Re: [asterisk-dev] Asterisk support of SIP Connect 1.1

The actual functionality of your patch aside, I added some comments about the merge process.

On 11-08-19 05:01 PM, Neeharika Allanki wrote:
> Hello all,
>
> CableLabs has developed a Reference Implementation (RI) of the SIPconnect1.1 Recommendation (http://www.sipforum.org/sipconnect ) based on Asterisk. SIPconnect1.1 is a newly released specification which has been developed by the SIP Forum, with the cooperation of the vendor and service provider community, to define the interface between a SIP-PBX and a SIP-based Service Provider network. The RI provides a working version of a SIP-PBX and SP-SSE that support a SIP Trunk interface that is compliant with the SIPconnect 1.1 Recommendation.
>
> CableLabs would like to submit this enhancement to Asterisk, so that the SIPconnect1.1-compliant behavior is available to the wider open-source Asterisk community. We have the following questions on the submission process:
>
> 1.       We have built the code against the 1.8.0 version of Asterisk-can the code be submitted in the same version or is there a specific version/branch we need to build against?
>
New features are submitted against trunk (more information below).

> 2.       What is the best way to go about submitting code for review to be included in the main Asterisk trunk. Should we raise a bug and submit the code as a patch? Submit the code to an SVN administrator?
>
If you have already not done so, create a new issue in JIRA[1].  You'll need to sign a contributors agreement[2] then attach your patch to the issue.

Once the issue has been triaged you'll likely need to post your patch to reviewboard[3].

> 3.       What is the overall process and the typical timeframe for having code accepted in Asterisk trunk?
>
1. submit patch
2. have people test it
3. code review
4. have more people test it
5. ???
6. commit to trunk

Honestly, it may take a few weeks or many months to finish the process. 
  Having the community testing your patch would be a good place to start.

[1] https://issues.asterisk.org/jira/
[2] https://issues.asterisk.org/jira/secure/DigiumLicense.jspa
[3] https://reviewboard.asterisk.org/

--
Paul Belanger
Digium, Inc. | Software Developer
twitter: pabelanger | IRC: pabelanger (Freenode) Check us out at: http://digium.com & http://asterisk.org

--
_____________________________________________________________________
-- Bandwidth and Colocation Provided by http://www.api-digital.com --

asterisk-dev mailing list
To UNSUBSCRIBE or update options visit:
   http://lists.digium.com/mailman/listinfo/asterisk-dev