<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Apr 29, 2013 at 6:09 AM, Olle E. Johansson <span dir="ltr"><<a href="mailto:oej@edvina.net" target="_blank">oej@edvina.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Friends,<br>
<br>
Now that gulp/pimp_my_sip is merged I think it's time to abandon the funny names and find a more long term solution for the channel name and the dial string identifier. I see no reason to deprecate SIP for chan_sip - I would encourage people running both channels while testing and while the new channel driver is getting stable and up to par. Having to switch between them doesn't make sense when you can run one on 5060 and another on 5080 or something similar.<br>
<br>
Just to start the discussion I propose that we rename the driver to chan_sipng<br>
<br>
and that the identifier in the dial strings become SIPNG/xxxx<br>
<br>
/O<br>
--<br><br></blockquote><div><br></div><div style>Totally whacky idea, but why not set a variable in sip.conf in the general section, the 'peer' or whatever section (allow= or use=, maybe) </div><div style><br></div>
<div style>I haven't been following it, but is the end goal to have one sip channel driver all merged together in the end.<br><br></div><div style>Maybe I am way off base, but could and would it make sense for endpoints to negotiate as they would a codec?</div>
<div style><br></div><div style>I would much prefer "fixing" depricated .conf files directly related to the channel driver, such as sip.conf than to have to much around in dialplan when the time comes.</div><div style>
<br></div><div style>Again, I may be talking out of turn, just ideas from my understanding of "What it was, what it is, and what it shall be."</div><div style><br></div><div style>Thanks,</div><div style>Steve T</div>
</div><br></div></div>