History | Log In     View a printable version of the current page.  
Issue Details (XML | Word | Printable)

Key: XCF-620
Type: Improvement Improvement
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Walter Gillett
Votes: 0
Watchers: 0
Available Workflow Actions

Resolve
Request Information
Operations

If you were logged in you would be able to see more operations.
sipXconfig

warn user about conflicts between extensions and auto attendant actions

Created: 2005-09-13 20:41   Updated: 2007-11-15 14:05
Component/s: autoattendant
Affects Version/s: None
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Related
 
This issue related to:
XECS-555 Display an error message when hunt gr... Major Closed
XCF-1140 provide a single place to view all as... Minor Open


 Description  « Hide
In the Auto Attendant screen, the admin creates actions triggered by single-digit numbers. When using the Auto Attendant, one should always be able to immediately dial an extension rather than an action. Therefore actions should not use numbers that overlap with the range of internal extensions. For example, if internal extensions are in the range 200-299, then "2" should not be mapped to an action. We should warn the user if they try to do this or perhaps simply exclude such numbers from the popup list of possible action numbers. (This suggestion came from today's review meeting.)

 All   Comments   Work Log   Change History      Sort Order:
Damian Krzeminski - 2005-09-27 14:14
take off 3.0 FCS list

Walter Gillett - 2005-12-01 12:38
I am switching from sipXconfig development to other projects for a while, so will not be working on sipXconfig issues during that time

Lih-Shyng Tzeng - 2006-06-29 16:55
Added this to 3.6 list.

Lih-Shyng Tzeng - 2006-07-02 20:31
Remove this from 3.6 list per Martin's email on 7/1/06.