On Fri, 2010-02-19 at 18:29 -0500, Tony Graziano wrote:
> The following items all are dialable directly from the "inside" by
> internal users:
> Users (lines)
> Auto Attendants
> Hunt Groups
> ACD's
> Conferences, etc.
>
> Is it desirable to also be able to place "aliases" (i.e. DID's) on ALL
> of these same items. While you can assign a alias/DID to an AA via the
> Dial Plan, you cannot assign a alias/DID to a hunt group, ACD or
> conference directly. I'm sure it would be a welcome addition at some
> point.
>
> Is this technically unfeasible?
Not at all.
> Am I correct in assuming an alias is a unique value that cannot be
> extended to more than one user/line?
Yes and no. :-)
The alias as entered through sipXconfig must be unique (a fact that I
just found out this week!), but...
The underlying alias database used by the routing engine in the
registrar can have any number of entries for the same address; this is
how forwarding and hunt groups are actually implemented.
A couple of weeks ago, I started a thread on the users list about how to
simplify sipXecs (thanks to everyone who responded - it was terrific).
In that thread, I asked developers not to post their own lists so that
we could hear clearly what the community said, but of course we all
exchanged our own lists internally (and polled our commercial sales and
support channels). We're in the process of consolidating those lists
and putting together priorities based on them - I think some really good
things will come of this... anyway - here are a couple of related items
from _my_ personal list that are related to your question:
* Find all the reasons that people create 'phantom users' and
remove the need for them (also make sure that it's easy to
figure out that there's no need for them). We have several ways
of routing calls internally, and users have features other
things don't - mostly the underlying mechanisms are the same, so
there's little or no server side work to do for this.
* Simplify the assignment of DID numbers. Right now we don't
treat the inbound numbers as any different from any other
number, but customers (and the phone company) don't think of
them that way. We should have a screen that lets you set what
your inbound numbers are and where they go - no more putting
aliases on things by hand.
Very soon (probably starting next week), we're going to start creating
tracker issues out of that list. Probably only a few will make it into
4.2 (because we _really_ want to get it out to you ASAP), but a lot of
the release after will be driven by them.
_______________________________________________
sipx-dev mailing list [email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
sipXecs IP PBX -- http://www.sipfoundry.org/
