Closed GoogleCodeExporter closed 9 years ago
Yes probably due to csipsimple.
The speakerphone mode is saved and then restored after a sip call. Maybe an
issue with this process. I've often broken this process since I rewrite a lot
of time this part of my code to fix issues on other devices.
What is strange is that current code seems to be ok regarding this issue (and
i'm not able to reproduce - but on Nexus one/android 2.2).
As code was broken with 0.00-12-05 and less. If you had previously installed
one of this versions it would be good to reboot your phone and test again. It
has maybe keep saved the speakerphone mode on and always restore it as on.
Original comment by r3gis...@gmail.com
on 25 Jul 2010 at 10:32
Yes probably due to csipsimple.
The speakerphone mode is saved and then restored after a sip call. Maybe an
issue with this process. I've often broken this process since I rewrite a lot
of time this part of my code to fix issues on other devices.
What is strange is that current code seems to be ok regarding this issue (and
i'm not able to reproduce - but on Nexus one/android 2.2).
As code was broken with 0.00-12-05 and less. If you had previously installed
one of this versions it would be good to reboot your phone and test again. It
has maybe keep saved the speakerphone mode on and always restore it as on.
Original comment by r3gis...@gmail.com
on 25 Jul 2010 at 10:32
Probably my mistake was to upgrade from version 0.00-12-05 to 0.00-12-06.
After uninstalling 0.00-12-06 and reinstalling it; testing during last two days
everything seems ok.
Sorry for the useless issue.
I hope there is also a solution for issue 38.
Original comment by Gianluca...@gmail.com
on 27 Jul 2010 at 8:55
Great,
No problem, I prefer to have a lot of feedback and each issue is valuable.
For issue 38, I can't reproduce yet it but I recently reproduced another bug
linked to ringback (but the problem was just the opposite : ringback was
ringing even when call is confirmed). So I was confident in the sample code
from the pjsip stack... but seems to be not so stable.
As soon as I'll reproduce it, I'll fix it. But it's not so critical isn't it?
Original comment by r3gis...@gmail.com
on 27 Jul 2010 at 9:22
Is not critical, just a bit boring, if you wait for the callee to answer and
it's not connected or busy.
Original comment by Gianluca...@gmail.com
on 27 Jul 2010 at 9:48
Original issue reported on code.google.com by
Gianluca...@gmail.com
on 25 Jul 2010 at 9:32