simlar / simlar-android Goto Github PK

Reported by Johannes

After simlar is started, the audio-connections via bluetooth (e.g. for playing music) are not working any more.
Seems like the bluetooth audio-device is either disabled or occupaid, allthough the settings for the bluetooth-device are limited to audio - not telephony.

Reproduction

1. Call s.o.
2. S.o. does not pickup call.
3. Press Power Button to suspend your display
4. Wait till call times out
5. Press Power Button again
6. Simlar starts calling s.o., again

Analysis

This bug was introduced by fixing #19.

On Dennis Smartphone it is contact: Lauritzen

when changing the internet connection from 3g to wireless or the other way around, when the app gets disconnected, it should automatically reconnect, when the app is running and detects, that the app is not registered

At the moment our sip traffic is encrypted with TLSv1 AES256-SHA.

According to rfc3261 end of section 26.2.1 other ciphers are allowed.

Forward secrecy would be great and is state of the art.

Our https traffic has already activated strong encryption for the android devices supporting it (I think android >= 3.0).

Reproduce

openssl s_client -CAfile kamailio-selfsigned.pem -connect 78.111.74.200:5061

or to check forward secrecy

openssl s_client -cipher 'ECDH:DH' -connect 78.111.74.200:5061

Reproduction

This was only reproducable on tscharlii's handy and in Ben's "nexus s" vm. Both have Android versions below 3.

1. Open menu and click "Delete my credentials and quit".
2. Open simlar.
3. Click cancel.
4. Repeat opening and canceling a couple of times => editTextPhoneNumber disappears

This only happens on a Huawei Ascend Y300.

The bug exists in linphone, too. See:
http://lists.nongnu.org/archive/html/linphone-developers/2013-11/msg00080.html

I think the following lines from the log file are relevant:

11-20 08:51:16.950  6591  6867 E Linphone: Channel [0x51771010]: error in 
ssl_read().
11-20 08:51:16.950  6591  6867 E Linphone: Receive error on channel 
[0x51771010]
11-20 08:51:16.950  6591  6867 I Linphone: channel 0x51771010: state ERROR
11-20 08:51:16.970  6591  6867 I Linphone: refresher [0x4fb9de70] has channel 
[0x51771010] in state [ERROR], reporting error
11-20 08:51:16.970  6591  6867 I Linphone: Refresher: scheduling next timer in 
500 ms
11-20 08:51:16.970  6591  6867 I Linphone: Register refresher  [503] reason 
[io error] for proxy ...

For example if I (ben) use my SGS2 with a headphone. The person hears an echo.

More cases need to be discovered.

Implementing an option to enable the software echo limiter works around this problem.

We do not want "delete my credentials", "upload Logfile" and "enable debug mode" in public release

The simlar server is effected by a grave openssl security bug. See:
http://heartbleed.com/

Todo:

1. Create new server certificates. This time we use a ca.
2. Update clients.
3. Inform users about downtime till update

My friend wanted to become a tester of simlar. i told him to follow the the steps on wiki/pages/become a tester...
step 1 tells the yuser to send an email at 'devel...' --> that didn't work. An email came back that more or less said this wouldn't exist.
step 3 didn't work eather.

Please rewrite and check all text message in the app

The user should get any feedback when he presses the button indicating the SAS is not the same.

but the phone is online need to check why and solve this

i still wondering if background.png and hang up butten are looking the same in different solutions. my hang up button looks compressed. stripes in background should be closer to each other.
why didn't we use a single png for the phone and a red field for the button. SEPERATED!
why didn't we use a small .png for the background, which we add together to a bigger one?

i think all this is less important at the moment, but somebody has to tell me someday.

Reproduction

1. Start Simlar
2. Pull down the status bar panel
3. Receive a call
4. Status bar panel does not hide

When I register an account after starting the app, I don't receive the verification SMS. It recognizes my country code correctly (+52 for Mexico). I found out that when sending an SMS from Germany to a mexican mobile phone you have to put a "1" in front of the actual phone number like +52 1 5544332211. Tried both with and without "1", no SMS received so far.

in the contacts activity we should show the phone number + contact, so that we can see the difference in the contact list

what is it about? do i need it? may i delete it?...

sometimes the voice quality is kind of bad have to monitor that

Workaround

• mute microphone and play sound

Please implement function.

1. Dennis: docu
2. Ben: functionality
3. Andreas: text

A user first using Simlar, might click on a contact and accidently call s.o. he does not want to call.

In the long term we should implement another activity that opens after clicking on a contact. It may e.g. show the contacts picture and a call history.

Reproduction

1. Start simlar in a vm.
2. Get called.
3. Deny call. => crash

Simlar does not work at Christians home. It works using UMTS or at his moms house. Normal Internet works.

What I have tested so far:

old.server: no network packages comming in

new server:

• new ip, new server, new Rechenzentrum
• Creating an Account over port 6161 works
• Logging in via sip (tls port 5061) does not
• Switched sip port to 443 (still tls, still tcp) => does not work
• Although some packages come through
  ** have to sniff agaian
• Tried decreasing mtu
  ** I do not know if it works in the lxc setup we use. Here is what I did
  ** Guest: /etc/network/interfaces: set mtu to 1100
  ** Host: disabled clamp-mms (temporarily)
  ** Host: set mtu in /etc/lxc/simlar.org.conf

Status:

• I left mtu and port settings at sip.simlar.org, as other locations work. Of course I turned on clamp-mms again.
• I might decide to switch back any time near.
• Christian is on holiday: 20.10. - 26.10.

Conclusion:

• I would like to test a root server.
• It is needed to visit Christian.

Christian WLAN router: dlink di-524
https://www.kabelbw.de/kabelbw/cms/downloads/kabel-bw-di-524-install.pdf [^]

when calling shortly appears a text in the notification bar 'xxx is on the phone'. i would prefer 'you are calling xxx'

We (dominik33 + Ben) think it is ok to remove the notification change completely for the ONGOING_CALL status.

iwould say this isn' really important, but anyway.

we now have the new design where everyone could see quality status easily. when opening the info button ( ---> alertfield with more detail information) you see a second quality status. in this case the noraml quality information isn't changing any more.
all best, d

Please remove the icon in the taskbar.

this needs to be configurable

People tend to close simlar as they expect it use much energy when constanrly running.

Implementing push notifications solves this problem.

ToDos:

• Take care of Dennis build environment. (x)
• Update build environment documentation (x)
  See http://developer.android.com/google/play-services/setup.html

• Connect to sip.simlar.org with a softphone not supporting ZRTP
• Call an account running Simlar