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

Key: XCF-1906
Type: Task Task
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Martin Steinmann
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

Consistency for "Transfer to" options

Created: 2007-10-09 20:16   Updated: 2008-08-25 23:38
Component/s: docs
Affects Version/s: 3.9.3
Fix Version/s: 4.2

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
Issue Links:
Related
This issue related to:
XCF-1911 Fields that allow entry of SIP URIs d... Minor Open
 


 Description  « Hide
This is to clarify the "forwarding to an extension, PSTN number or SIP URI" question that keeps coming up. I can spot the following places where we give the admin an opportunity to insert a "forwarding to" number:

1) User call forwarding (user and admin portal)
2) Personal auto-attendant (zero-out extension)
3) Personal auto-attendant (user defined keys 1 through 9)
4) ACD queue overflow extension
5) Auto-attendant Goto Extension
6) Auto-attendant transfer on invalid input
7) Hunt group fallback destination

This issue is to get to a) clarity and b) consistency in terms of what input is allow in these fields. Ideally, all these transfer locations should be any internal number, PSTN numbers, and SIP URIs. Could someone please point out what the current state of affairs is, so that we at least can add the correct help text information?

 All   Comments   Work Log   Change History      Sort Order:
There are no comments yet on this issue.