<div dir="ltr"><div dir="ltr">Howdy,<div><br></div><div>As Asterisk is an open source project, new capabilities are implemented by many different individuals and organizations, each driven by their own self-interests. We at Digium and Sangoma, who do represent a large share of the development contributions to Asterisk, are happy to take any feature requests under our own consideration. Anyone else could consider this request, too. Speaking only for ourselves, we cannot, at this time, make any commitment to implementing this feature. It is something we have to consider, along with all of the other externally-generated, non-commercial feature requests, and evaluate against our needs and availabilities.<br></div><div><br></div><div>Cheers</div></div></div><br><div class="gmail_quote"><div dir="ltr">On Tue, Jan 15, 2019 at 4:04 PM Michael Maier <<a href="mailto:m1278468@mailbox.org">m1278468@mailbox.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">On 15.01.19 at 20:27 Joshua C. Colp wrote:<br>
> <br>
> <br>
> On Tue, Jan 15, 2019, at 3:23 PM, Michael Maier wrote:<br>
>> Hello!<br>
>><br>
>> Deutsche Telekom introduced sips and srtp. I tested it and it works <br>
>> partly. Partly means: sips is working - but not srtp. srtp doesn't <br>
>> work, because of missing additional<br>
>> headers in the REGISTER and INVITE packages (according an enhancement <br>
>> of RFC 3329).<br>
>><br>
>><br>
>> Example:<br>
>><br>
>> UAC Registrar<br>
>> | |<br>
>> |----(1) REGISTER------------------------------>|<br>
>> | Security-Client: sdes-srtp;mediasec |<br>
>> | Proxy-Require: mediasec |<br>
>> | Require: mediasec |<br>
>> | |<br>
>> |<---(2) 401------------------------------------|<br>
>> | Security-Server: msrp-tls;mediasec |<br>
>> | Security-Server: sdes-srtp;mediasec |<br>
>> | Security-Server: dtls-srtp;mediasec |<br>
>> | |<br>
>> |----(3) REGISTER(with Authorization Header)--->|<br>
>> | Security-Client: sdes-srtp;mediasec |<br>
>> | Proxy-Require: mediasec |<br>
>> | Require: mediasec |<br>
>> | Security-Verify: msrp-tls;mediasec |<br>
>> | Security-Verify: sdes-srtp;mediasec |<br>
>> | Security-Verify: dtls-srtp;mediasec |<br>
>> | |<br>
>> |<---(4) 200 OK---------------------------------|<br>
>> | |<br>
>> | |<br>
>> |----(5) INVITE-------------------------------->|<br>
>> | Security-Verify: msrp-tls;mediasec |<br>
>> | Security-Verify: sdes-srtp;mediasec |<br>
>> | Security-Verify: dtls-srtp;mediasec |<br>
>> | a=3ge2ae:requested |<br>
>> | a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:EpcgtOdT5qd...<br>
>> | |<br>
>> |<---(8) 200 OK---------------------------------|<br>
>> | a=crypto:1 AES_CM_128_HMAC_SHA1_80 inline:lnfakjh2sd1..<br>
>><br>
>><br>
>><br>
>> You can find a complete description here (english language):<br>
>> <a href="https://www.telekom.de/hilfe/downloads/1tr114.pdf" rel="noreferrer" target="_blank">https://www.telekom.de/hilfe/downloads/1tr114.pdf</a><br>
>> The example can be found on page 115.<br>
>><br>
>> They need those mediasec parameters because of there compatibility with <br>
>> the 3GPP standards<br>
>> (<a href="http://www.qtc.jp/3GPP/Specs/33328-920.pdf" rel="noreferrer" target="_blank">http://www.qtc.jp/3GPP/Specs/33328-920.pdf</a>) which would require an <br>
>> additional signaling of the media plane security.<br>
>><br>
>><br>
>> Is this already implemented or did I miss something else?<br>
> <br>
> This is not implemented and I know of noone working on such a thing.<br>
> <br>
<br>
Would you please plan to implement it?<br>
Deutsche Telekom is the biggest player in Germany having 19 millions fixed lines and 25 millions mobile customers.<br>
<br>
<br>
Thanks,<br>
Michael<br>
<br>
-- <br>
_____________________________________________________________________<br>
-- Bandwidth and Colocation Provided by <a href="http://www.api-digital.com" rel="noreferrer" target="_blank">http://www.api-digital.com</a> --<br>
<br>
asterisk-dev mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-dev" rel="noreferrer" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-dev</a></blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><span style="color:rgb(0,0,0);font-family:monospace;font-size:medium">--------------------------------------------------</span><br style="color:rgb(0,0,0);font-family:monospace;font-size:medium"><span style="color:rgb(0,0,0);font-family:monospace;font-size:medium">Malcolm Davenport</span><br style="color:rgb(0,0,0);font-family:monospace;font-size:medium"><span style="color:rgb(0,0,0);font-family:monospace;font-size:medium">Digium - a Sangoma company | Senior Product Manager</span><br style="color:rgb(0,0,0);font-family:monospace;font-size:medium"><span style="color:rgb(0,0,0);font-family:monospace;font-size:medium">445 Jan Davis Drive NW - Huntsville, AL 35806 - US</span><br style="color:rgb(0,0,0);font-family:monospace;font-size:medium"><span style="color:rgb(0,0,0);font-family:monospace;font-size:medium">Tel/Fax: +</span><span style="color:rgb(0,0,0);font-family:monospace;font-size:medium"><a style="color:rgb(0,0,139);text-decoration:none">1 256 428 6252</a></span><br style="color:rgb(0,0,0);font-family:monospace;font-size:medium"><span style="color:rgb(0,0,139);font-family:monospace;font-size:medium"><a href="mailto:malcolmd@sangoma.com" target="_blank">malcolmd@sangoma.com</a></span><br></div></div></div></div></div></div>