
| Key: |
XCF-2579
|
| Type: |
Bug
|
| Status: |
Open
|
| Priority: |
Major
|
| 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-05-21 12:29
Updated: 2008-05-31 08:03
|
|
| Component/s: |
polycom
|
| Affects Version/s: |
3.10.1
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
3.10.1
|
|
|
One or more emergency numbers can be configured on one or both of these sipxconfig screens:
<specific Polycom phone or phonegroup> | Dial Plan
<specific Polycom phone or phonegroup> | <specific Line> | Dial Plan
If more than one number is entered in the Emergency Numbers field on those screens then a comma must be used as the delimiter. Using a comma correctly results in multiple entries for the per/phone settings, and a comma delimited list for the per/line setting. However, if a different delimiter is used (eg a space) then the generated config is incorrect (specifically, only a single, space-delimited entry will be created, which is incorrect for both the per/phone and per/lines settings).
We could address this by having sipxconfig treat any delimiter as a comma. However, the parsing complexity doesn't seem worth the effort. I think it would be sufficient to improve the onscreen help text for the Emergency Numbers parameter (on both the per/phone and per/line Dial Plan screens). Here's the current onscreen help text for the Emergency Numbers field:
This represents the URLs that should be watched for emergency routing. When one of these defined URL is
detected as being dialed by the user, the call will be automatically directed to the defined emergency server.
I suggest that we add another sentence to the text:
This represents the URLs that should be watched for emergency routing. When one of these defined URL is
detected as being dialed by the user, the call will be automatically directed to the defined emergency server.
When entering multiple URLs a comma MUST be used as the delimiter, as in the following example:
911,9911
|
|
Description
|
One or more emergency numbers can be configured on one or both of these sipxconfig screens:
<specific Polycom phone or phonegroup> | Dial Plan
<specific Polycom phone or phonegroup> | <specific Line> | Dial Plan
If more than one number is entered in the Emergency Numbers field on those screens then a comma must be used as the delimiter. Using a comma correctly results in multiple entries for the per/phone settings, and a comma delimited list for the per/line setting. However, if a different delimiter is used (eg a space) then the generated config is incorrect (specifically, only a single, space-delimited entry will be created, which is incorrect for both the per/phone and per/lines settings).
We could address this by having sipxconfig treat any delimiter as a comma. However, the parsing complexity doesn't seem worth the effort. I think it would be sufficient to improve the onscreen help text for the Emergency Numbers parameter (on both the per/phone and per/line Dial Plan screens). Here's the current onscreen help text for the Emergency Numbers field:
This represents the URLs that should be watched for emergency routing. When one of these defined URL is
detected as being dialed by the user, the call will be automatically directed to the defined emergency server.
I suggest that we add another sentence to the text:
This represents the URLs that should be watched for emergency routing. When one of these defined URL is
detected as being dialed by the user, the call will be automatically directed to the defined emergency server.
When entering multiple URLs a comma MUST be used as the delimiter, as in the following example:
911,9911
|
Show » |
| There are no comments yet on this issue.
|
|