Closed GoogleCodeExporter closed 9 years ago
are you running a custom rom?
as you are experiencing this problem on two connectors, i guess it's a problem
of the trusted cert. store.
Original comment by f...@ub0r.de
on 9 May 2011 at 5:31
Yes, its a custom rom for my HTC Desire (RCMix S 1.3), with the original Rom
the Connector works very good. Ok, i send a Email to the Costum Rom Developer
with this Problem. Thanks
Original comment by stefan.b...@googlemail.com
on 9 May 2011 at 5:39
I have wiped cache and dalvik and installed the Rom again. WebSMS with
Connector sipgate works fine :) Sorry was my fault. Thanks
Original comment by stefan.b...@googlemail.com
on 9 May 2011 at 8:26
After the phone is rebooted, the Error is back.
Original comment by stefan.b...@googlemail.com
on 9 May 2011 at 9:00
Import cacert root certificate like described here:
http://wiki.cacert.org/ImportRootCert
this seems to solve the certification problems with sipgate
Original comment by robert.b...@googlemail.com
on 10 May 2011 at 6:49
Got the No peer certificate-error with developergarden.com connector (Issue
510).
Importing the cacert root certificate didnt help here...
Original comment by p3rs...@gmail.com
on 11 May 2011 at 4:11
I got the same error on sipgate. i updated from an 2.21 to an 2.3 rom today (on
2.21 it worked). I use Android Revolution HD 5.19 which is a custom rom for HTC
Desire HD Phone. Some hours ago i got an error on o2 connector too but it seems
to work now. Additionally the sipgate app to actually make calls over sipgate
does not work since the update. maybe there is a connection?
Original comment by christop...@gmail.com
on 8 Jun 2011 at 8:04
[deleted comment]
jup, it's a sipgate thing in one moment it works, sometimes a day. Another day
the peercert error without any connector or websms update..
Original comment by christop...@gmail.com
on 28 Jul 2011 at 10:52
is this vstill a problem?
Original comment by f...@ub0r.de
on 5 Dec 2011 at 6:01
No.
Original comment by christop...@gmail.com
on 5 Dec 2011 at 6:25
Original comment by f...@ub0r.de
on 5 Dec 2011 at 7:53
Original issue reported on code.google.com by
stefan.b...@googlemail.com
on 9 May 2011 at 10:34