Modify the UI to be Call Flow driven

[t_h_048d3]

The current UI is an improvement on the old PBX consoles of 20 years ago.
We now have menus, mouse and data formating, no need to rely on memory or a manual.
In addition the functions delivered by today's PBX have grown considerably.

In looking at the Epygi UI, I feel the it has grown from a simple list of features. Over time the features have grown to such an extent that now finding the features is a problem ... needing to move in and out of many independent screens is becomming commonplace for normal configuration tasks. This is reflected in the volumous 'how do I' questions and difficult to maintain manual.

A suggestion is to move toward 'call flow objects':
To configure the PBX, the administrator would "draw" the call flow:
example: external > reception > if busy/nans > group, if after hours > voicemail, etc

When the call flow is drawn the configuration happens in the background. The administrator can then set properties for the flow, eg timeouts, sound files, etc.

What is described is not something that will happen in the short term but moving in this direction will be of great benefit to all Epygi administrators.

just an idea after 20+ years PBX management and software development experience!
________
MFLB (http://mflbvaporizer.com)
________
NASH AMBASSADOR HISTORY (http://www.dodge-wiki.com/wiki/Nash_Ambassador)

[KSComs]

The current UI is an improvement on the old PBX consoles of 20 years ago.
We now have menus, mouse and data formating, no need to rely on memory or a manual.
In addition the functions delivered by today's PBX have grown considerably.

In looking at the Epygi UI, I feel the it has grown from a simple list of features. Over time the features have grown to such an extent that now finding the features is a problem ... needing to move in and out of many independent screens is becomming commonplace for normal configuration tasks. This is reflected in the volumous 'how do I' questions and difficult to maintain manual.

A suggestion is to move toward 'call flow objects':
To configure the PBX, the administrator would "draw" the call flow:
example: external > reception > if busy/nans > group, if after hours > voicemail, etc

When the call flow is drawn the configuration happens in the background. The administrator can then set properties for the flow, eg timeouts, sound files, etc.

What is described is not something that will happen in the short term but moving in this direction will be of great benefit to all Epygi administrators.

just an idea after 20+ years PBX management and software development experience!

After 30 years experience within the standard TELEPHONE systems, the Epygi Quadro is far far superior to the MAJOR brands. Siemens, Aria, Samsung, Nec, Panasonic are without a word interestingly tedious to configure for anything that the Epygi Quadro does with a few screens.

Complexity = the other brands

All telephone systems have their idiosyncrasies.. I work with some of the most interesting headaches at times... = loss of hair, late nights etc....

The Epygi is an absolutely great device for its price point.. No other systems can comfortably match it and do what it does so well.

Yes there is always an ideal - but I think in this instance - the Epygi Quadro is far above its class, and even though things can be better it is in its core far better than the others that I have worked on for the same size and featureset.

Regards

Kevin