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

Key: XCF-1441
Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Archana Hegde
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

Gateway is not getting removed from the dialing rule which is enabled

Created: 2007-01-12 04:44   Updated: 2007-11-02 08:39
Component/s: dial plan
Affects Version/s: 3.6
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. GZip Archive sipx-configuration[1].tar.gz (64 kb)

Environment:
sipxconfig 3.6.0 007755 2007-03-13T04:49:57 eagle.pingtel.com
  sipxvxml 3.6.0 007755 2007-03-13T03:42:09 eagle.pingtel.com
  sipxpbx 3.6.0 007755 2007-03-13T05:33:43 eagle.pingtel.com
Issue Links:
Related
 
This issue related to:
XCF-1941 Using the Caller Sensitive Forwarding... Minor Resolved


 Description  « Hide
Pre-condition: International Dialing rule should be enabled (Unmanaged Gateway ' U-7' should be added to International dialing rule)

Steps:
1)Navigate to System-->Dial plans page
2)Go to International dialing rule page
3)Select the added gateway (U-7) checkbox and click on Remove button
4)gives an error "Add at least one gateway before enabling the rule."
At this stage, the operation appears to have completed succesfully - The gateway is removed and the dial plan gets disabled.
5)Click on OK button which intern navigates to Dial Plans main page
6)Now again navigate to International dialing rule page to check whether the gateway has been removed?

Expected result:
The Gateway has been removed from the dial plan

Actual Result:
Gateway U-7 has not been removed from the International dialing rule

Attached file:
snapshot

 All   Comments   Work Log   Change History      Sort Order:
Damian Krzeminski - 2007-01-12 09:41
The net result is confusing and misleading, but at least you do not end up with a rule that is enabled and does not have any gateways. Looks like we are preventing gateway from being deleted *and* we are disabling the rule at the same time. What's more we do not refresh the current page properly. Fixing any of these would make situation better.

Lih-Shyng Tzeng - 2007-04-09 21:54
After consulting with Al, took this off the 3.8 to-fix list.

Workaround for this issue: To remove a gateway from a dial rule, disable the dial rule first.