Hi. Just recently moved to Boost prepaid and tried to extend my ring time by sending **61*101**30# but I was given this message "Call forwarding when no reply for all Basic Services. Connection problem or invalid MMI code"
I'm getting the same error message when trying any code that I try. I tried looking at my Call forwarding options but couldn't due to a "Network or SIM card error" warning when I navigated to my call settings.
My phone is working fine apart from all that but I do get this message onscreen when I make a call "conditional call forwarding active"
My phone is a Samsung Galaxy Note 5 running Android 7.0
@john55 Can you try:
Seriously - This is a public forum, it is monitored, but there is no active official support, and Boost is a seperate company from Telstra, however, they have made agreements for Telstra to provide management of parts of the operation for them as well as provide the network.
Hi. Thanks for trying but no I can't try that code.
The problem I'm having is that I can't enter any codes at all without getting this message
"Call forwarding when no reply for all Basic Services. Connection problem or invalid MMI code"
Hi. I get this voice prompt when I call 101. "The number you have called is not available from this service".
Because I couldn't send my own codes, I had to contact Boost and have them turn voicemail off so that my calls would ring the maximum amount of time and not go to message bank.
When my call ring time expires now, people get a message that my call forwarding is set to an invalid number.
Not a simple problem i think. This all seemed to happen when I move from Internode to Telstra/Boost.
I've just tried resetting my phone to factory defaults with no luck. Same problem exists.
I might try getting a low cost disposable sim from another provider and see if I can at least modify call forwarding settings before putting my Boost sim back in. Sounds crazy but might work.
Well owing to the fact that I've bought a new phone, this issue isn't a problem any more.
For anyone interested, I'm convinced that the problem I was having was due to a firmware issue on my Galaxy Note 5. Other's who had the same problem and who couldn't find a more conventional fix, found that it was their firmware at fault. I wasn't about to start re-flashing my phone's OS so I gave up and upgraded to an S10 :-)