topic Re: Voicemail too quickly in Tech Support

Voicemail too quickly

HarrowBaggie — Tue, 15 Mar 2022 16:48:56 GMT

How do I prolong the amount of time it goes to voicemail when the call is not answered immediately.

As currently I only have about 10 seconds.

S21 ultra.

Re: Voicemail too quickly

gmarkj — Tue, 15 Mar 2022 17:01:17 GMT

There are instructions in the guide below @HarrowBaggie to change the time.

Re: Voicemail too quickly

gmarkj — Tue, 15 Mar 2022 17:02:36 GMT

The section you want is this one:

Divert calls when there is no reply
To activate ** 61 * phone number * 11 * no seconds# SEND

Where it says "no seconds", enter a number between 5 and 30 in a multiple of 5 (so 5, 10, 15, etc)

Re: Voicemail too quickly

HarrowBaggie — Tue, 15 Mar 2022 17:33:53 GMT

I've tried that and it does not work,

I get an error message ,

I have tried

901

+447802091901

And my actual phone number but still get error.

Re: Voicemail too quickly

HarrowBaggie — Tue, 15 Mar 2022 17:38:13 GMT

I get the message

Connection problem or invalid mmi code.

Thanks

Re: Voicemail too quickly

Cleoriff — Tue, 15 Mar 2022 19:46:21 GMT

@HarrowBaggie

Another guide here if it helps

If nothing works then you need to contact O2 to reset your VM account.

Give O2 a call on 202 or 0344 809 0202.

Or you can message O2 on Facebook ( https://o2uk.co/O2CFB) , Twitter ( https://o2uk.co/O2CTW) or Instagram ( https://o2uk.co/O2CIG), hopefully they should be able to help.

Re: Voicemail too quickly

MI5 — Tue, 15 Mar 2022 20:29:46 GMT

@HarrowBaggie

You need to turn off wifi and wifi calling to send mmi codes.

Re: Voicemail too quickly

HarrowBaggie — Tue, 15 Mar 2022 21:19:14 GMT

Thanks all.

I've tried everything.

Wifi, wifi calling off.

5g, lte off, still no joy.

I'll contact customer service tomorrow.

Re: Voicemail too quickly

HarrowBaggie — Tue, 22 Mar 2022 17:48:17 GMT

I logged a call with the help desk, still no solution.

It's definitely an O2 network issue as its the same on my , my wifes and my work phone/sim. So all 3.

The common factor being that all on the O2 network!

I can see why O2 can't fix this, as was fine on my previous network.

I've even tried the help chat, bit no joy too.