Feature Request: Separate cSIP complimenting automated stress testing and geofencinng app.

[GoogleCodeExporter]

A complimenting app that could be setup optionally for each individual SIP 
account.

It could look like this in the interface...

[Account Name] [Test] [Account Enabled/disabled]
SIPACCOUNT A   [   ]  [ x ]
SIPACCOUNT B   [ x ]  [ x ]
SIPACCOUNT C   [ x ]  [ x ]
SIPACCOUNT D   [   ]  [ x ]

The functionality would be very simple, for every change in environment 
accounts that have the stress test option enabled the accounts would then each 
be individually tested for codec quality, encryption strength, and latency 
maybe even location of the phone itself (eg: geo fencing). And then per the 
users preference whichever they want to take presidency would become the new 
default account used. The test could be per user preference or have a branch 
build with set perimeters. It could have a random time dispersion rate set by 
the user as well.

A manual force button for this would be helpful as well.

These options would best be implemented by sliding bars.

Important factors ?
[Location -A_B-c]
100%[-------------------------|------]-1% Codec quality
100%[--------------|-----------------]-1% Encryption availability
100%[-----|--------------------------]-1% Latency

There are other avenues where this could be taken but i tried to keep it simple.

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

Android 2.1 and 2.2 , does anyone even use 1.x anymore ?

Original issue reported on code.google.com by Djoneslo...@gmail.com on 27 Jul 2010 at 5:30

[GoogleCodeExporter]

Latency could be achieved by a simple random ping to the SIP server.
Call quality using fring 's free API echo service.

Codec and encryption quality and availability on connection.

Sorry about the double post. I'm excited about this request!

Original comment by Djoneslo...@gmail.com on 27 Jul 2010 at 5:35

[GoogleCodeExporter]

Really interesting idea.
I'll keep this in mind. 
As a first analysis, I would say that it could be performed by a third party 
application : 
There is an important part of my work that will be done to provide third party 
application a rich API that could allow such plugins.
But I have to think more about it. 

P.S. : 
"does anyone even use 1.x anymore ?" Unfortunately yes.... a lot of non geek 
that own the first released devices.... about 40% of android users... not 
negligible.

Original comment by r3gis...@gmail.com on 27 Jul 2010 at 7:07

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

[GoogleCodeExporter]

Another thing i didn't mention was the addition of priority accounts, or "home" 
accounts. But then we are traveling down the blind path again...

All in all the best way to get all this done would be to have a simple API for 
enabling and disabling accounts/codecs/encryption. So we don't overthink things.

Original comment by Djoneslo...@gmail.com on 27 Jul 2010 at 9:34