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

Key: XCF-1807
Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Unassigned
Reporter: Sangeetha.R.S
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

Give error message when trying to add emergency number same as user ID

Created: 2007-07-26 06:53   Updated: 2008-03-26 02:35
Component/s: dial plan
Affects Version/s: 3.8
Fix Version/s: None

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown
File Attachments: 1. GZip Archive sipx-configuration-sipx-brblab.qantom.int.tar.gz (505 kb)

Environment:
sipxconfig 3.8.0-010588 2007-07-24T17:38:37 eagle.pingtel.com
sipxpbx 3.8.0-010588 2007-07-24T17:50:02 eagle.pingtel.com


 Description  « Hide
Precondition : Add user 200 to the sipxchange.

Steps :
1. Navigate to System->Dialplan->Emergency dial rule.
2. Emergengy dial rule page is displayed.
3. Edit the values as following :
Enabled : Yes
PSTN prefix : 3
Emergency number : 200
4. Add a existing gateway LG_G and click on OK.

Expected : Should give an error message that extension 200 is already being used. And should not allow to add 200 as Emergency number.

Actual : Allows to add 200 as emergency number without any error.

Observation :1. Dial emergency number 200 from user 200 .
Call ID : 28f1ed2-70306e2c-e4fa68f5@176.25.10.181
482 loop detected message is found in the call flow.
2. Dial emergency number 3200 from user 200.
Call ID : bd4c9577-c8cf99b9-9201c866@176.25.10.181
The call is established successfully.

Attachments : sipx-configuration-sipx-brblab.qantom.int.tar.gz

 All   Comments   Work Log   Change History      Sort Order:
Varun A M - 2007-08-27 08:02
Reproduced this issue in :

                  sipxpbx 3.8.0-010689 2007-08-24T00:06:43 eagle.pingtel.com
                   sipxconfig 3.8.0-010689 2007-08-23T23:58:13 eagle.pingtel.com

Prakash PM - 2008-03-26 02:35
Reproduced the issue in :

sipxconfig 3.10.0-012086 2008-03-20T00:03:36 oem-centos5
sipxpbx 3.10.0-012086 2008-03-20T00:17:26 oem-centos5

Issue is still existing.