sure, i iam also a friend of stability. But srtp and tls are disabled by 
default. To activate you will
still need a --enable-encryption (what i will add later). So the risk to 
breaking something is
minimized. Most stuff is jailed in #ifdef's

But the trueness is... i threatened to put the patch into 1.2 to awaken 
some people to test the
srtp_tls branch and get some feedback on it :)
 
Kristijan

thomas schorpp schrieb:
> Duane at e164 dot org wrote:
>   
>> Kristijan Vrban wrote:
>>     
>>> that's why i wanted to put it into 1.2. As long as it sleeps in my 
>>> private branch, i am the only tester.
>>> My limited tests show:  it  compiles, produced no crash and srtp and tls 
>>> are working.
>>>       
>> I'm happy to give it a go, will compile it up shortly and see how things go.
>>
>>     
>
> i would second that. but for trunk only. risk of breaking stable branch 
> due to "limited tests" is too high.
>
> y
> tom
>
> _______________________________________________
> Callweaver-dev mailing list
> [email protected]
> http://lists.callweaver.org/mailman/listinfo/callweaver-dev
>
>
>   
_______________________________________________
Callweaver-dev mailing list
[email protected]
http://lists.callweaver.org/mailman/listinfo/callweaver-dev

Reply via email to