I for one would like to see aliases for hunt groups, ACD's and conferences if
it is possible. I would also like to see an ALIAS for voicemail ("101") too.
Currently the methods used can be quite frustrating to make the DID's flow down
to those by creating "phantom users", adding the DID alias and having a
permanent forward set to the internal ACD, hunt group or conference. It simply
makes for a lot of unnecessary data entry, room for error, and seems a
cumbersome way to get to that result.
While it would be nice to have in 4.0, it probably means a DB schema change of
some variety that might wait until a later release to implement. Do you have
the issue number for the generic alias? I couldn't find it.
Thanks,
Tony
>>> Damian Krzeminski <[email protected]> 03/16/09 12:13 PM >>>
Picher, Michael wrote:
> I suppose you could, but if you want to get to the conference server
> internally then you are dialing all of those digits...
Unless you set up custom dial rule...
>
> I just think it would be easier than to have phantoms for yet another
> thing (although I like using them for a lot of my inbound call routing
> because I still can't have a live attendant during the day if calls are
> routed to the AA).
>
> Mike
We already have an issue somewhere to add support for generic aliases. But
I do not see why we cannot add more aliases to conferences.
What about other addressable entities: for now we only have explicit
aliases for users and AA (and even that is hidden in dial plan config).
Should we add explicit aliases for hunt groups, ACD lines etc?
Or just a generic aliasing capability?
D.
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
