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

Key: SPARK-682
Type: Bug Bug
Status: Closed Closed
Resolution: Fixed
Priority: Major Major
Assignee: Thiago Rocha Camargo
Reporter: Derek DeMoro
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
Spark

Dialing an invalid number is not handled properly by Spark

Created: 12/27/06 10:07 PM   Updated: 05/01/07 04:12 PM
Component/s: Enterprise: SIP
Affects Version/s: 2.5.0
Fix Version/s: 2.5.2

Time Tracking:
Issue & Sub-Tasks
Issue Only
Original Estimate: 3 minutes
Original Estimate - 3 minutes
Remaining Estimate: 3 minutes
Remaining Estimate - 3 minutes
Time Spent: Not Specified
Remaining Estimate - 3 minutes

Issue Links:
Duplicate
 

Support Plan Customer Issue: No
Resolution Date: 05/01/07 04:12 PM
Acceptance Test - Add?: No
Acceptance Test - Entry: Dial an invalid number then you MUST see a message in the dial field.

Sub-Tasks  All   Open   

 Description  « Hide
At the moment, when dialing an invalid number, Spark does not handle the exception thrown. The user should be notified of this change and the state should be changed.

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Thiago Rocha Camargo - 04/17/07 12:41 PM
Spark MUSt show a toaster telling that the dialed number is invalid.

Thiago Rocha Camargo - 04/18/07 10:55 AM
Added a message to the dial field when a invalid number is dialed.

Francisco Vives - 04/24/07 12:03 PM
I called 4442 and 44424545 but I did not see an error

Thiago Rocha Camargo - 05/01/07 04:12 PM
Call Fail Event now triggers Invalid Number notification.