| Key: |
XCF-2494
|
| Type: |
Improvement
|
| Status: |
Open
|
| Priority: |
Minor
|
| Assignee: |
Unassigned
|
| Reporter: |
Michael Haag
|
| Votes: |
0
|
| Watchers: |
0
|
|
Available Workflow Actions
|
|
If you were logged in you would be able to see more operations.
|
|
|
sipXconfig
Created: 2008-04-24 12:41
Updated: 2008-08-25 23:38
|
|
| Component/s: |
dial plan
|
| Affects Version/s: |
3.10.1
|
| Fix Version/s: |
4.2
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
|
it's currently possible to define a dial plan for which both the Dial and Append fields of the resulting call are empty. sipxconfig should not allow that. Here's a comment from Dale (based on problems seen at a customer site (a NYC bank)):
Since an empty user-part is never valid (in sipX usage), we could
have the Config Server check user-configured dial plans to ensure that
the user specifies some non-empty output for number transformations.
|
|
Description
|
it's currently possible to define a dial plan for which both the Dial and Append fields of the resulting call are empty. sipxconfig should not allow that. Here's a comment from Dale (based on problems seen at a customer site (a NYC bank)):
Since an empty user-part is never valid (in sipX usage), we could
have the Config Server check user-configured dial plans to ensure that
the user specifies some non-empty output for number transformations.
|
Show » |
|
dial plans should not allow all 'Resulting Call' fields to be empty 