<div dir="ltr">Brandon,<br> Sorry it took over a week to respond to the other request to test a patch.<br><br>In this specific case I don't understand why you just closed 13497 with no fix. It is a real problem... If I have VoIP provider A (let say I use them for domestic calls) and VoIP provider B (which I may use for international calls) and if both are set up with the same username, then it is impossible to configure both these service providers.... you can't have two contexts with the exact same name. Using "username" for the context name is not the right thing to do. A quick fix is to use "trunkname" as I suggested in 13497. This would return to the behavior of GUI v1. As for Voicepulse, if it requires the username as the context, then why not just enter the username into the trunkname field as well? <br>
<br>David<br><br><br><br><div class="gmail_quote">On Mon, Oct 6, 2008 at 4:36 PM, bkruse <span dir="ltr"><<a href="mailto:bkruse@digium.com">bkruse@digium.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
David, I appreciate the help in reporting bugs, however, these things need time.<br>
<br>
I have many higher priority issues in house that I am dealing with, and I am the<br>
only developer currently working on the GUI. I would be happy to review/accept/commit<br>
a patch, but until then you will just have to be patient.<br>
<br>
After all these emails it is still unclear the exact thing that is happening. I believe I know<br>
what it is, and we do this for voicepulse, where we statically link a name to it, however, this<br>
is makes it hard to do incremental numbering on providers (trunk_x), besides, you can use<br>
the username = field to have the channel driver (sip/iax/w/e) match based on that name instead<br>
of the contextual name you are citing.<br>
<br>
Besides, you created another issue that took you over a week to provide feedback to, this doesn't<br>
help development as far as "time" is concerned. I appreciate all the help, however, just making you aware.<br>
<br>
-Brandon<br>
<br>
David Kerr wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><div class="Ih2E3d">
I opened bug 13497 for this issue several weeks ago. It is still sitting in assigned state. Any estimate on when it might get fixed? Its a real problem that the gui forces a certain inflexible naming convention for context that is clearly broken when you have multiple VoIP providers.<br>
<br>
Thanks<br>
David<br>
<br></div><div class="Ih2E3d">
On Tue, Sep 16, 2008 at 11:10 PM, David Kerr <<a href="mailto:David@kerr.net" target="_blank">David@kerr.net</a> <mailto:<a href="mailto:David@kerr.net" target="_blank">David@kerr.net</a>>> wrote:<br>
<br>
Pari,<br>
I changed the pbx.js file as you recommended. This does not<br>
revert back to the "version 1" GUI behavior as I had hoped, rather<br>
it behaves as documented in the bug you cited.... "trunk_1" etc. This breaks service providers that requre asterisk to match the<br>
incoming call with the context name. In the case of the first bug<br>
report that needed to be the username. In the case of my service<br>
provider, it needs to be the trunkname ("vitel-inbound" for<br></div>
<a href="http://vitelity.net" target="_blank">vitelity.net</a> <<a href="http://vitelity.net" target="_blank">http://vitelity.net</a>>).<div class="Ih2E3d"><br>
<br>
Bottom line, you need to revert to GUI version 1 behavior (using<br>
the trunkname) or add a new field for the user to enter a context<br>
name. Generating one automatically isn't going to work with some<br>
service providers.<br>
<br>
David<br>
<br>
<br>
On Tue, Sep 16, 2008 at 5:01 PM, David Kerr <<a href="mailto:David@kerr.net" target="_blank">David@kerr.net</a><br></div><div class="Ih2E3d">
<mailto:<a href="mailto:David@kerr.net" target="_blank">David@kerr.net</a>>> wrote:<br>
<br>
I have opened bug 0013497 at the Digium bug tracker web site<br>
to track this problem.<br>
<br>
Thank you.<br>
<br>
<br>
On Tue, Sep 16, 2008 at 9:09 AM, David Kerr <<a href="mailto:David@kerr.net" target="_blank">David@kerr.net</a><br></div><div class="Ih2E3d">
<mailto:<a href="mailto:David@kerr.net" target="_blank">David@kerr.net</a>>> wrote:<br>
<br>
For some reason I "replied" only to Pari and not the list.<br>
Ooops.<br>
<br>
<br>
---------- Forwarded message ----------<br></div><div class="Ih2E3d">
From: *David Kerr* <<a href="mailto:David@kerr.net" target="_blank">David@kerr.net</a> <mailto:<a href="mailto:David@kerr.net" target="_blank">David@kerr.net</a>>><br>
Date: Tue, Sep 16, 2008 at 9:08 AM<br>
Subject: Re: [asterisk-gui] Context names in the new GUI<br>
To: Pari Nannapaneni <<a href="mailto:pari@digium.com" target="_blank">pari@digium.com</a><br></div><div><div></div><div class="Wj3C7c">
<mailto:<a href="mailto:pari@digium.com" target="_blank">pari@digium.com</a>>><br>
<br>
<br>
Pari,<br>
Thanks for the quick reply... A classic case of fixing<br>
one bug creating another!<br>
<br>
In my opinion the original bug report isn't even a bug, it<br>
is the way that Asterisk is supposed to work. If you need<br>
the username as the context name for incoming calls, then<br>
set the trunkname in the GUI to be the same as the<br>
username. I don't believe that the trunkname was used for<br>
anything other than the context naming anyway (in the<br>
extensions.conf file the "trunkname" was set to "Custom -<br>
whatever-the-user-entered" anyway so not exactly as<br>
entered, the only place it appears as entered is for<br>
Contexts. So the right way to address the problem in<br>
AA50-2113 is to tell the user to enter exactly the same<br>
thing (their username) into both the trunkname and<br>
username fields in the GUI.<br>
<br>
As implemented today, it is broken.... multiple trunks<br>
from different service providers using the same username<br>
cannot be configured. If we must be able to use username<br>
as context names, then it should be an option, not<br>
hardcoded. But why make it an option? why not just add a<br>
field in the GUI for "Context name".... humm, but then<br>
again, how would that be any different from "Trunk name" ?<br>
<br>
I can edit the source as you suggest, which will get me<br>
going again, but I recommend you consider how to implement<br>
a permanent fix.<br>
<br>
Thanks again for the super fast reply.<br>
David.<br>
<br>
<br>
<br>
On Mon, Sep 15, 2008 at 11:39 PM, Pari Nannapaneni<br></div></div><div><div></div><div class="Wj3C7c">
<<a href="mailto:pari@digium.com" target="_blank">pari@digium.com</a> <mailto:<a href="mailto:pari@digium.com" target="_blank">pari@digium.com</a>>> wrote:<br>
<br>
<br>
> Can you explain why this change was made?<br>
<br>
Hi David,<br>
<br>
The change in behavior was because of an issue on our<br>
internal bug tracker.<br>
<br>
AA50-2113 - Creation of Trunks uses name that won't<br>
match on inbound calls<br>
<br>
Description : The convention used to create a new<br>
trunk entry in users.conf, i.e. trunk_1, trunk_2,<br>
trunk_3, etc.,<br>
works okay for outbound calls placed<br>
via that trunk. However, inbound calls fail. When a<br>
call is received,<br>
Asterisk tries to match the inbound<br>
user as "trunk_1" instead of the real username, i.e.<br>
bobjones.<br>
Please modify the creation of new<br>
trunks and the expression of those trunks in<br>
users.conf and extensions.conf<br>
so that they are what the user inputs<br>
into the "username" field when adding or editing a<br>
voip trunk.<br>
So, if I input mdavenport_soft as my<br>
username, then the entry in users.conf would be<br>
[mdavenport_soft] instead of trunk_1,<br>
and everything in the dialplan that<br>
would have said trunk_1 should say "mdavenport_soft"<br>
instead.<br>
<br>
You can easily switch to the old style by<br>
uncommenting a couple of lines in pbx.js,<br>
look for functions addIAXTrunk() and addSIPTrunk()<br>
and change<br>
<br>
--<br>
//var trunk =<br>
astgui_managetrunks.misc.nextAvailableTrunk_x();<br>
var trunk = tr.username ;<br>
<br>
-- TO --<br>
<br>
var trunk =<br>
astgui_managetrunks.misc.nextAvailableTrunk_x();<br>
// var trunk = tr.username ;<br>
--<br>
<br>
May be one day we migh have an option in the gui to<br>
switch between these modes.<br>
<br>
thanks<br>
-Pari<br>
<br>
<br>
<br>
----- Original Message -----<br>
From: "David Kerr" <David@Kerr.net><br>
To: <a href="mailto:asterisk-gui@lists.digium.com" target="_blank">asterisk-gui@lists.digium.com</a><br></div></div><div class="Ih2E3d">
<mailto:<a href="mailto:asterisk-gui@lists.digium.com" target="_blank">asterisk-gui@lists.digium.com</a>><br>
Sent: Monday, September 15, 2008 9:29:39 PM GMT -06:00<br>
US/Canada Central<br>
Subject: [asterisk-gui] Context names in the new GUI<br>
<br>
<br>
<br>
I just started using the new version of the GUI and am<br>
trying to migrate settings from a box that had the old<br>
GUI. I have found that the new GUI uses the username<br>
of a VOIP trunk as the basis for the context names in<br>
users.conf and extensions.conf (any maybe elsewhere<br>
too?). The old GUI used the name of the service<br>
provider as the basis (or whatever you entered as the<br>
name).<br>
<br>
This breaks me... I have multiple VOIP service<br>
providers with the same username, which obvously won't<br></div>
work. In one case ( <a href="http://vitelity.net" target="_blank">vitelity.net</a> <<a href="http://vitelity.net" target="_blank">http://vitelity.net</a>><div class="Ih2E3d"><br>
) they require two contexts be setup in asterisk with<br>
specific naming, one for vitel-inbound, one for<br>
vitel-outbound... both with the same username, but<br>
with different host addresses. In the new GUI I cannot<br>
set this up. If I manually change the context names by<br>
editing users.conf and extensions.conf, then I can no<br>
longer edit the trunk in the GUI.<br>
<br>
Can you explain why this change was made?<br>
<br>
Is there anyway I can change it back to using the<br>
trunk name as the basis for Context naming?<br>
<br>
Thanks<br>
David<br>
<br>
_______________________________________________<br>
--Bandwidth and Colocation Provided by<br>
<a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
<br>
asterisk-gui mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-gui" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-gui</a><br>
<br>
<br>
<br>
<br>
<br>
<br></div>
------------------------------------------------------------------------<div class="Ih2E3d"><br>
<br>
_______________________________________________<br>
--Bandwidth and Colocation Provided by <a href="http://www.api-digital.com--" target="_blank">http://www.api-digital.com--</a><br>
<br>
asterisk-gui mailing list<br>
To UNSUBSCRIBE or update options visit:<br>
<a href="http://lists.digium.com/mailman/listinfo/asterisk-gui" target="_blank">http://lists.digium.com/mailman/listinfo/asterisk-gui</a><br>
</div></blockquote>
<br>
<br>
</blockquote></div><br></div>