<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 07/03/14 07:29, Matthew Jordan wrote:
<blockquote
cite="mid:CAN2PU+5nuHjLKeRu1H9KFeyKoXwJD7yBY8NJc-_HtdByps7GzA@mail.gmail.com"
type="cite">
<div dir="ltr"><br>
<div class="gmail_extra">On Thu, Mar 6, 2014 at 3:22 PM, Paul
Belanger <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:paul.belanger@polybeacon.com" target="_blank">paul.belanger@polybeacon.com</a>></span>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div class="HOEnZb">
<div class="h5">On Thu, Mar 6, 2014 at 3:31 PM, George
Joseph<br>
<<a moz-do-not-send="true"
href="mailto:george.joseph@fairview5.com">george.joseph@fairview5.com</a>>
wrote:<br>
> On Thu, Mar 6, 2014 at 1:22 PM, Scott Griepentrog
<<a moz-do-not-send="true"
href="mailto:sgriepentrog@digium.com">sgriepentrog@digium.com</a>><br>
> wrote:<br>
>><br>
>> First, a smidgen of background:<br>
>><br>
>> The two sorcery options for pjsip.conf
"allow" and "disallow" both accept<br>
>> a list of codecs and set the same table of
codecs in behind the scenes. The<br>
>> difference being of course that the disallow
field inverts the meaning.<br>
>><br>
>> There is some potential confusion here as to
why there is two lists of the<br>
>> exact same codecs (see<br>
>> <a moz-do-not-send="true"
href="https://issues.asterisk.org/jira/browse/ASTERISK-23092"
target="_blank">https://issues.asterisk.org/jira/browse/ASTERISK-23092</a>).
I have a suggested<br>
>> patch (see <a moz-do-not-send="true"
href="https://reviewboard.asterisk.org/r/3193/"
target="_blank">https://reviewboard.asterisk.org/r/3193/</a>)
to make the disallow<br>
>> option disappear in a fashion. You can still
use the disallow option in<br>
>> pjsip.conf, but when viewing the settings
with pjsip show endpoint # only<br>
>> the allow list would appear. This is
accomplished by marking the disallow<br>
>> field as an alias.<br>
>><br>
>> An option to move away from SIP's convention
of allow/disallow and have<br>
>> PJSIP use codecs=ulaw,etc has been suggested
(and is coded in the review).<br>
>> The question then is:<br>
>><br>
>> 1) Do we want to discontinue or alias both
allow & disallow and move to<br>
>> codecs?<br>
>><br>
>><br>
>> 2) If yes, then which version should that be
done in? 12? 13?<br>
><br>
><br>
> My vote...Move to codecs and alias allow/disallow
in 12, discontinue<br>
> allow/disallow in 13.<br>
><br>
>><br>
>> Note that even if codecs is chosen, allow and
disallow continue to work so<br>
>> no existing pjsip.conf is broken.<br>
>><br>
><br>
</div>
</div>
For me to be on-board with the change, we'd have to apply
it to all<br>
channel drives that implement said codecs allow / disallow
logic, so<br>
sip.conf, chan_ooh323.conf, gtalk.conf, h323.conf,
iax.conf,<br>
jingle.conf.<br>
<br>
That way all our documentation / functionality is
consistent among<br>
channel drivers.<br>
<span class="HOEnZb"></span><br>
</blockquote>
</div>
<br>
</div>
<div class="gmail_extra">Yeah... that will never happen.<br>
</div>
<div class="gmail_extra"><br>
</div>
</div>
</blockquote>
I assume this is about the codecs option. If so, why couldn't it be
implemented in all the channel drivers. Surely the "codecs list"
option could be a simple wrapper for "disallow all, allow list".<br>
<br>
Damien Wedhorn<br>
</body>
</html>