Enhancement - optional notification types for failed registration

[GoogleCodeExporter]

What steps will reproduce the problem?
1. use Sipdroid normally
2. lose registration (can simulate on WiFi by disconnecting AP or router)

What is the expected output?
Would like to be able to set an audible notification (ringtone) or vibrate.
In other words, I'd like the option to tell Sipdroid to alert me when
registration fails using a ringtone or vibrate. (And I'd like it to have a
snooze or cancel option too.)

What do you see instead?
Only a red blinking LED, which will go completely unnoticed if phone is in
pocket or a briefcase. Important incoming calls could be missed. However,
if a ring/vibrate option was available for failed registration, preemptive
action could be taken to avoid missed calls.

What version of the product are you using?
1.2.4 beta
On what operating system?
2.01

Which SIP server are you using?
Gizmo5

Which type of network are you using?
WiFi or 3G

Original issue reported on code.google.com by davidshi...@gmail.com on 28 Dec 2009 at 2:39

[GoogleCodeExporter]

Original comment by pmerl...@googlemail.com on 29 Dec 2009 at 12:09

• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

When my wifi drops (in standby) and I'm on EDGE, Sipdroid vibrates the phone and
pulses the trackball to notify. I would like to disable this completely... I'm 
okay
with Sipdroid losing registration when I'm off wifi. I have arrangements in 
place for
that. I just don't want to confuse this type of notification with the ones that 
I
care about (e.g. email).

So yes, please give us some fine-grained options on this notification.

Original comment by ctros...@gmail.com on 23 Jan 2010 at 1:00

[GoogleCodeExporter]

Addendum: In my case this is a Nexus One which has only one LED colour 
available.

Original comment by ctros...@gmail.com on 23 Jan 2010 at 1:01

[GoogleCodeExporter]

Issue 443 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 3 May 2010 at 6:44

[GoogleCodeExporter]

Issue 1009 has been merged into this issue.

Original comment by pmerl...@googlemail.com on 13 Jan 2012 at 9:47