Closed GoogleCodeExporter closed 9 years ago
I'll investingate. But sounds an issue from sipdroid :
I've read their code and the dialer integration use my previous approach that
modify currently dialed number adding a # and a tag to specify it is or not
pstn call.
Then they split the number with # as separator. The backside of this method is
that it doesn't always handle properly # within the number (at least in their
case if other application that handle phone number doesn't use the same
mechanism).
Can you try with sipdroid not installed? Because for me ussd code is properly
transmitted to gsm when there is only csipsimple prompt.
Original comment by r3gis...@gmail.com
on 10 Jul 2010 at 4:29
Uninstalled SipDroid. Now gives option of 2talk providers (without choice of
app) - I choose GSM. Then same option appears again. I choose GSM again.
Then it tries to dial *101*9 using GSM, which unfortunately doesn't work.
Original comment by kro...@gmail.com
on 10 Jul 2010 at 4:42
Ok, many thanks for the test.
I'll test it again and try to reproduce on my phone.
Original comment by r3gis...@gmail.com
on 10 Jul 2010 at 6:18
2 degrees (my new phone provider) supports USSD so I can test as often as you
need. *100*1# should provide my phone balance. Unregistering or listing
^\*.*\#$ as a cannot filter is a work around, but choosing "Use Mobile" from
the CSIP popup fails spectacularly. Suggest hardcoding or defaulting regex or
similar so choice never appears.
Thanks.
Original comment by kro...@gmail.com
on 14 Aug 2010 at 7:40
Great, with *100*1# I'm able to reproduce the issue :) The trailing # disappear.
OK for workaround, problem is that some sip providers support this kind of ussd
code too.
As I can now reproduce, I hope that I'll be able to fix it soon
Original comment by r3gis...@gmail.com
on 14 Aug 2010 at 8:02
This issue was closed by revision r198.
Original comment by r3gis...@gmail.com
on 14 Aug 2010 at 8:22
0.00-12-11 available on download section to test the fix.
Was due to a big mistake from me... I managed Uri just as string instead of
using the good functions that properly encode uris (and specially the # char
that is considered as the fragment separator).
Original comment by r3gis...@gmail.com
on 14 Aug 2010 at 8:30
Still have the same problem as above when sending ussd *100# to GSM on ver.
Original comment by zs6...@gmail.com
on 28 Sep 2010 at 2:48
@zs6wdl : I assume you are using 0.00-13.
What do you observe exactly? Have you the account/gsm chooser? If yes, is *100#
written in popup title? Then if you choose "Use Mobile" are you redirected to
the native gsm phone app? And if yes what is it trying to dial? Is there any
toaster talking about USSD?
Original comment by r3gis...@gmail.com
on 28 Sep 2010 at 3:06
Hi,
Sorry I did not include all the finer detail, because it still do the same as
described by krolaw, but just for your info I will describe the steps and
results again.
I am using CSipsimple 0.00-13 with Froyorider 2.0 Android 2.2 on a Magic 32A
1. Select the mobile icon on CSipsimple top right corner.
2. Dail *100# and dial button which should give me a popup with my account
balance
3. Popup with selection of IP or mobile, but the top of the popup says "Call
*100"
4. I select "use Mobile"
5. The phone try to dial *100 and then hang up
I hope this is the information you needed.
And by the way, this is the best SIP program on the market. Congratulations!!!
Regards,
Jaques
Original comment by zs6...@gmail.com
on 29 Sep 2010 at 6:23
On my Galaxy I9000 the USSD codes also do not working since some time (*101#),
but I had no idea if this depend on csipsimple...
I have a rooted phone, so where are the settings for csipsimple?
If I can save them and restore later I would try to uninstall the app and check
it out, if this depend on csipsimple.
Original comment by m...@ufritz.de
on 29 Sep 2010 at 10:06
@mail : there is apps that allow to backup restore other apps settings (I use
Astro File manager). Else if you want to do it manually, on most devices it's
on /data/data/com.csipsimple (but I'm not absolutely sure that everything is
there)
@zs6wdl : I asked all those infos because I though that it was fixed since
previously I reproduced the issue reported initially and now I never reproduce
it. (In the popup the title is *100#).
Just a thought, is there another sip application -Sipdroid, Linphone,
GoogleVoice with integration activated- installed on your phone?
If there is some other app with the same bug that I had previously, it's
possible that the other app rewrite the phone number incorrectly (without
encoding # properly) and then pass to CSipSimple the number without the # char.
Original comment by r3gis...@gmail.com
on 29 Sep 2010 at 10:21
I force stop Google voice and the problem was solved. I want to uninstall
Google Voice because I am not using it(not available in South Africa), but the
uninstall button is not available in manage applications for Google Voice.
Original comment by zs6...@gmail.com
on 29 Sep 2010 at 2:01
Indeed, google voice is shipped with phone with "Google" experience inside, and
it's impossible to delete (unless you have root access).
Btw, amazing... a bug on a google app that is not in mine ;)...
However, that's a little bit strange since I've also google voice on my phone
and just like you it's impossible for me to start it since my account can't
login on google voice (it's not available in France too).
I heard that if I go through the login there is an option in google voice to
disable outgoing call integration. But I guess that you are blocked before
accessing any option just like me?
However, even if I have google voice installed I have not the problem. Maybe a
matter of google voice version. What version of google voice is installed on
your phone?
Original comment by r3gis...@gmail.com
on 29 Sep 2010 at 2:20
Google Voice is ver. 0.4.1.26
Yes I am blocked for Google Voice. I have root access but I am not that clever.
Took me 3 days to get my phone rooted!!!
I just want to mention another issue since installing the latest version. You
must redirect this to a new issue or whatever needs to be done if necessary.
Since installing the latest version, when making a call the in-call screen is
displayed - the one with the end call button in the middle. After about 15
seconds the slide buttons are displayed over the other buttons making it
impossible to access the buttons to send like in-call dtmf. To be able to
access the dialpad inside a call I have to press the back button, go into
notifications, select current call and then I have 15 seconds access to the
dialpad again until the sliders are displayed over the buttons again. I thought
it could be the option of using slider controls or not but changing the option
does not seems to make a difference.
Regards
Jaques
Original comment by zs6...@gmail.com
on 29 Sep 2010 at 3:13
As for your last remark : you have just to slide to unlock actually :)
This screen locker is here to avoid your face to make unwanted actions.
I guess that your phone has no proximity sensor since else I use proximity
sensor instead of timers to lock screen.
When timer are used, just slide the right yellow locker icon to the left side
of the screen (just like you do when answering the call).
The option in setting is related only to the answer mode and not the overlay
locker.
So setting use buttons will just change the way you take/decline an incoming
call.
For google voice, I was just thinking about that, but it's a bad idea to
uninstall it, since Google navigation need it to run (there is probably a
dependency with some vocal features).
Just for information, my version of google voice is 0.4.1.261. If you have a
lower version, you should maybe consider update it from the market.
Original comment by r3gis...@gmail.com
on 29 Sep 2010 at 3:27
Ok, the developer wins this round.
Thank you for your help.
Regards,
Jaques
Original comment by zs6...@gmail.com
on 29 Sep 2010 at 8:05
Hi,
I just want to add something that I found regarding the USSD problem. You can
have Google Voice installed and the *100# command will work as described. BUT
as soon as you put the Google Voice Widget on your desktop, even without being
registered with Google Voice or Logged in, the USSD commands does not work on
CSipSimple.
At least that is how I experienced the problem.
Regards,
Jaques
Original comment by zs6...@gmail.com
on 1 Oct 2010 at 9:34
Ok thx Jaques for this remark.
I think that it will helps users in the same case.
Well as for CSipSimple : I close again this issue since seems the reopening was
due to be a problem in google voice.
Original comment by r3gis...@gmail.com
on 7 Oct 2010 at 7:59
Original issue reported on code.google.com by
kro...@gmail.com
on 10 Jul 2010 at 4:16