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