Dialing a phone number with a hash (GSM Code)

754 views
Skip to first unread message

Benny Schmid

unread,
Dec 20, 2021, 5:04:35 PM12/20/21
to Automate
Hi all

I just tried to dial a phone number with a hash sign (#) in it. This does not seem to work and instead of dialing a hash sign my phone is trying to dial this as „%23“. Is this a bug or can it be changed? Thanks in advance for your help.

Henrik "The Developer" Lindqvist

unread,
Dec 20, 2021, 8:34:36 PM12/20/21
to Automate
The Dialer app should decode that into an #, it does so on my device. The flow log just displays it encoded, i'll fix that.
What # actually does or even work in the Dialer app, or mobile network, i don't know.
Android doesn't support sending DTMF tones, if that's what you expect the # to do, but i've heard some able to do it by including a comma in the phone number, e.g.: 123,#,4

Benny Schmid

unread,
Dec 21, 2021, 12:41:36 AM12/21/21
to Automate
Hi Henrik

Thanks for your answer. i made a script with „call number“ on a Samsung Galaxy mobile phone. The Number i would like to dial is *#06# and what I see in the log file from automate is that my phone tried to dial *%2306%23
- Flow beginning
- Location at ?
- Call number
- Called *%2306%23
- Stpooed at end
Could this maybe be a result of the german language I am using on my phone?

Benny Schmid

unread,
Dec 21, 2021, 1:16:26 AM12/21/21
to Automate
I tried with the comma but it didn‘t help.

Henrik "The Developer" Lindqvist

unread,
Dec 21, 2021, 2:10:03 PM12/21/21
to Automate
As said, "Called *%2306%23" is just what's logged, the Dialer app should still receive *#06#
System language does not affect URI encoding.

Benny Schmid

unread,
Dec 22, 2021, 11:17:42 AM12/22/21
to Automate
Dear Henrik
Everything works well now. The only thing with dialing numbers: sometimes I get the following error:

java.lang.SecurityException: User call rate limit exceeded, see Settings.

The flow stopps by failure.
Restarting the flow a few times solves the error until it appears again. Is there a possibility to catch this error without having to restart the flow?

Henrik "The Developer" Lindqvist

unread,
Dec 22, 2021, 2:09:33 PM12/22/21
to Automate
You can increase and/or reset the safety limit in setting.

Benny Schmid

unread,
Dec 22, 2021, 3:37:58 PM12/22/21
to Automate
Many thanks, all works well now.
My first flow is fully functional.
Great App!

Reply all
Reply to author
Forward
0 new messages