We have moved to a new Sailfish OS Forum. Please start new discussions there.

[Fixed in] Dialer App not connecting Service Calls [answered]

asked 2014-01-07 15:20:56 +0300

richardski gravatar image

updated 2014-03-19 05:04:29 +0300

MattVogt gravatar image

Currently it is not possible to successfully place a network Service Call - e.g. *100# - from the Dialer App when using the Call Contact option to select a Service Number entry in the People List. This returns an – Invalid phone number - response.

It is possible to dial Service Call type numbers, usually prefixed with a “*”, directly from the number keypad and also from inside the People App so the problem would appear to be with the Dialer App.

Service Calls are frequently used by people with a Pay as you Go service to check credit status and for functions like diverting to voice mail etc. It would be a great help to have Service Call Numbers stored in the People list and usable by the Dialer App.

edit retag flag offensive reopen delete

The question has been closed for the following reason "the question is answered, an answer was accepted" by richardski
close date 2014-11-25 14:59:52.964639


I had trouble 'dialling' the *# numbers when stored in the phone book with inconsistent behaviour and I put it down to there being no signal. When I next have the phone I'll try it - it may be I'd gone in via the dialler but hadn't picked it up that was the source of the problem. I had been pretty sure it was a no signal issue, but it may have been coincidence that when I had signal I went in the working way!

markcoley ( 2014-02-21 00:12:12 +0300 )edit

I can confirm this bug is still there.

richardski ( 2014-02-25 01:57:09 +0300 )edit

OK, have now tried it and it is a bug. I don't understand why the dialler app is checking if the number is valid - surely the better place to check validity is when it is saved in the people app? Or perhaps there is a validity checking algorithm which is present twice, once in a correct form and once in an incorrect form.

Can anyone from Jolla explain how the error is there? Am just curious. Of course, the phone number doesn't have an error, so that is a bug, but that this is only picked up once seems to be another bug/inconsistency.

markcoley ( 2014-02-25 02:00:59 +0300 )edit

It is a tiny bug but annoying for people who have to make service calls to get their credit balance on some PayGo services.

richardski ( 2014-02-25 02:29:04 +0300 )edit

the phone is not up to it's primary function - calling. this is critical bug.

Ragnar Kurm ( 2014-02-25 02:37:06 +0300 )edit

3 Answers

Sort by » oldest newest most voted

answered 2014-02-25 02:42:43 +0300

mjones gravatar image

This bug has been fixed and will be released in a future update. Thanks for your report!

In the meantime, you can call the service number via the contacts application.

edit flag offensive delete publish link more


For me it does not work via contacts not dialer. Thank you for bringing news about not-yet-released fix.

Ragnar Kurm ( 2014-02-25 02:53:17 +0300 )edit

It did not work when selecting a contact via the dialer app, i.e. open dialer -> "Call contact" -> choose service contact. If you open the people app, select the contact and click call, it should work.

mjones ( 2014-02-25 03:43:27 +0300 )edit

Does not work with People app either.

Ragnar Kurm ( 2014-02-25 09:28:00 +0300 )edit

Ragnar, what is the format you are trying to dial?

If it is of *#06# [asterisk][hash][number][hash] format for checking IMEI etc, it wont work from People either. Because for such codes, the output is displayed on the keypress of the last hash. So if u pressed 'call' instead, it will be sent as a request code to the service provider. (and might display 'invalid service request' if not recognized by the operator)

User ( 2014-02-25 15:02:47 +0300 )edit

Thank you for the bug status report and I shall look forward to the new update and will report back:)

richardski ( 2014-03-11 23:19:06 +0300 )edit

answered 2014-02-20 23:51:37 +0300

Ragnar Kurm gravatar image

updated 2014-02-25 02:11:10 +0300

Confirming the bug.

Dialling: 1322 asterisk 605 asterisk 90004327XXX

Answer: The number you called is not in use, please check the number ...

edit flag offensive delete publish link more


Is this an answer? It doesn't make any sense and doesn't seem to address the question above, that of network service codes starting *# and ending in * not being recognised.

markcoley ( 2014-02-25 02:04:03 +0300 )edit

actually i placed asterisks there, but got lost in wysiwyg, I did edit original post.

Ragnar Kurm ( 2014-02-25 02:11:50 +0300 )edit

Aha, that makes more sense, though the answer you wrote sounds as if a voice was telling you the message, which never happens when a network service request is made, as it isn't a proper phone call. However, the other answer here says it has been fixed so we don't need to worry any more.

markcoley ( 2014-02-25 19:47:08 +0300 )edit

Well, for me it is a worry, I tried to call around 6 different automated service numbers. 5 out of 6 were unavailable due to bug. All numbers contain exactly two asterisks and numbers in them, no hash. By calling to the special number I get recorded voice saying "the number is not in use, please check the number ...". In normal circumstances I get answer like "you ordered service x, press key z to confirm" and that's it.

Ragnar Kurm ( 2014-02-25 20:49:07 +0300 )edit

Did some more testing. Service Requests (*#62# etc) seem to be working, only service numbers seem to be affected.

Ragnar Kurm ( 2014-02-28 01:13:40 +0300 )edit

answered 2014-03-22 01:55:06 +0300

richardski gravatar image

Fixed and working since the update to Ver.


edit flag offensive delete publish link more

Question tools



Asked: 2014-01-07 15:20:56 +0300

Seen: 361 times

Last updated: Mar 22 '14