Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Dialing an invalid number is not handled properly by Spark

Description

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.

Environment

None
100% Done
Loading...

is duplicated by

Activity

Show:

Thiago Rocha Camargo May 2, 2007 at 4:12 AM

Call Fail Event now triggers Invalid Number notification.

Francisco Vives April 25, 2007 at 12:03 AM

I called 4442 and 44424545 but I did not see an error

Thiago Rocha Camargo April 18, 2007 at 10:55 PM

Added a message to the dial field when a invalid number is dialed.

Thiago Rocha Camargo April 18, 2007 at 12:41 AM

Spark MUSt show a toaster telling that the dialed number is invalid.

Fixed

Details

Priority

Assignee

Reporter

Affects versions

Fix versions

Components

Created December 28, 2006 at 12:07 PM
Updated May 2, 2007 at 4:12 AM
Resolved May 2, 2007 at 4:12 AM