Currently the Configuration->Services page displays all the
individual services (in some order):
ACDServer
CallResolver
CallResolver-Agent
ConfigServer
MediaServer
PageServer
ParkServer
PresenceServer
ResourceListServer
SIPRegistrar
SIPStatus
SipXbridge
sipXivr
SIPXProxy
SipXrelay
(Side Note: We are missing some from this list: Certainly the
conference service, and isn't there a sipxconfig-agent that has
to run on an ACD system?)
Especially given that some of those names are not exactly
admin-friendly, I think it would be good to consider reducing the
number of entries by creating some functional groups that have
related functions. The Services page would then be restricted to
configuring the functional groups on a Server. This not only
makes it easier to understand, but
Here's a strawman list of groups and what they contain (I'm not
crazy about some of these group names; suggestions are
encouraged); they reduce the number from 15 to 6:
Management (always on the master, by definition)
ConfigServer
CallResolver
SIP Router (N per cluster: replicated)
SIPRegistrar
SIPXProxy
SipXrelay
ResourceListServer
CallResolver-Agent
Voicemail (One per cluster)
MediaServer
SIPStatus
Call Distribution (1|N ?)
PageServer
ParkServer
sipXivr
SIP Trunk (N per cluster)
SipXbridge
Call Center (N per cluster)
ACDServer
PresenceServer
Conference Service (N per cluster)
(?)
Some questions to consider:
* Do administrators need to be able to be able to "explode" the
group to see what's inside them even if they cannot control them
individually?
* Does the above grouping create any problems?
_______________________________________________
sipx-dev mailing list
[email protected]
List Archive: http://list.sipfoundry.org/archive/sipx-dev
Unsubscribe: http://list.sipfoundry.org/mailman/listinfo/sipx-dev
