
| Key: |
XCF-1899
|
| Type: |
New Feature
|
| Status: |
Open
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Martin Steinmann
|
| Votes: |
0
|
| Watchers: |
0
|
|
Available Workflow Actions
|
|
If you were logged in you would be able to see more operations.
|
|
|
sipXconfig
Created: 2007-10-08 14:02
Updated: 2008-08-25 23:33
|
|
| Component/s: |
autoattendant
|
| Affects Version/s: |
3.9.3
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
With the introduction of individual zero-out configuration, the meaning of operator has changed. We currently have an action called "Operator" that transfers to the extension with the alias 0 (the default AA by default).
This issues proposes a new AA action called "Group Attendant". The admin can then enter a user group. When hitting the corresponding key, callers will be transferred to the zero-out extension of the group indicated. (If users change the group setting individually on the user portal, the AA still transfers to the default setting for the group. This requires a group setting to be entered for this group and the help text should make that clear.)
|
|
Description
|
With the introduction of individual zero-out configuration, the meaning of operator has changed. We currently have an action called "Operator" that transfers to the extension with the alias 0 (the default AA by default).
This issues proposes a new AA action called "Group Attendant". The admin can then enter a user group. When hitting the corresponding key, callers will be transferred to the zero-out extension of the group indicated. (If users change the group setting individually on the user portal, the AA still transfers to the default setting for the group. This requires a group setting to be entered for this group and the help text should make that clear.) |
Show » |
|