Sounds like a weird carrier issue. Does your carrier enable VoLTE on your handset by default?

Sounds like a weird carrier issue. Does your carrier enable VoLTE on your handset by default?

Depends on the phone plan fwik, but yes. At the same time, I think this is carrier specific, as the three other carriers I tested with work fine. Other branded phones work just fine with VoLTE of that carrier. As such, there might be nothing the dev can do, but at least others who come across this issue will know.

Hi,
I have the same issue on my Pixel 7 pro in Poland. We have special number for services starting with 9**. 999, 998 and 997 are also alarm numvers for police etc., but lower numbers like 986,991 are for local services and all cara to those numbers are redirects to nationwide 112 number. I have a regular sim card from Orange and it works correctly when I put it in another phone. It doesn't depend if I'm using volte, vowifi or anything else. Software updates didn't help at all with this problem

Hi, I have the same issue on my Pixel 7 pro in Poland. We have special number for services starting with 9**. 999, 998 and 997 are also alarm numvers for police etc., but lower numbers like 986,991 are for local services and all cara to those numbers are redirects to nationwide 112 number. I have a regular sim card from Orange and it works correctly when I put it in another phone. It doesn't depend if I'm using volte, vowifi or anything else. Software updates didn't help at all with this problem

Try this
System > Reset options > Reset Network Settings (don't delete eSIM btw)

I had same problem with physical SIM on same provider A1 Bulgaria

I had same problem with physical SIM on same provider A1 Bulgaria

Based on the info above, it might just be a carrier configuration problem

I had same problem with physical SIM on same provider A1 Bulgaria

Based on the info above, it might just be a carrier configuration problem

I think the same as both physical and eSIM had same problem

I had same problem with physical SIM on same provider A1 Bulgaria

Based on the info above, it might just be a carrier configuration problem

I think the same as both physical and eSIM had same problem

Update your physical SIM. It has to be one of their 5G series, otherwise the same thing happens.

Card is brand new from yesterday

I had same problem with physical SIM on same provider A1 Bulgaria

Based on the info above, it might just be a carrier configuration problem

I think the same as both physical and eSIM had same problem

Update your physical SIM. It has to be one of their 5G series, otherwise the same thing happens.

There's no need to "update" a SIM card unless it's potentially damaged. It's main role is just to authenticate you to the carrier's network. After that the network will send the carrier configuration file which includes frequencies allowed to connect on

Hi, I have the same issue on my Pixel 7 pro in Poland. We have special number for services starting with 9**. 999, 998 and 997 are also alarm numvers for police etc., but lower numbers like 986,991 are for local services and all cara to those numbers are redirects to nationwide 112 number. I have a regular sim card from Orange and it works correctly when I put it in another phone. It doesn't depend if I'm using volte, vowifi or anything else. Software updates didn't help at all with this problem

Try this System > Reset options > Reset Network Settings (don't delete eSIM btw)

Tried it, but doesn't work :/ I have also made a system reset lately and it didn't work as well

Same problem here.
Google Pixel 8, Android 15, build AP4A.241205.013

I had no problems in the past, but today I was surprised. Any 0700 number ends up with 112.
My wife has Pixel 8 Pro with the latest Android updates too and there isn't such problem. We have tried to switch the SIMs (physical ones) - no issues.
When I put back my SIM into my phone, the problem appeared again.

The workaround - disable VoLTE. Huge credit goes to @smsimeonov!
Surprisingly 8 Pro doesn't have this option.

I am currently in contact with A1 and will explain my findings.

Answer from A1:
If I keep VoLTE disabled, at some point I will lose the access to the voice services, because in EU all 3G networks are being deprecated. I have to keep it enabled and when needed disable it in order to call those special numbers. According to them Pixels are not recommended in Europe and not everyone will have this problem. Wierd, huh.

@fillwithjoy1 This is maybe the case in general, but I know it isn't for this provider. They roll out 5G support based on the CCID of the SIM. Older cards that they have registered before a set date, do not work with 5G. I have confirmation from their support team.

@bossnass At this point, I have received multiple calls from their support, and since we're a corporate user with upwards of a thousand users, we get very good support. They have even asked me to explain some workarounds I've done to get it working lol. To my knowledge, the customer service has recommended this project to at least two other corporate accounts based on my feedback (Which is wild, but this is Bulgaria after all). I know they are not as precise with typical clients of theirs.
From what I've been told, they're testing this out on some phones which report to the cellular systems that they support certain technologies (VoLTE, 5G, additional cellular bands for LTE) and are enabling them per device ID for a period of six months. This has started for the Pixel 6 Pro in mid October. Unfortunately, they cannot choose who goes on their testing CID system, since it is apparently randomized and automated. They will notify me if my SIM gets to that program. But even if it has, by April 2025, it should work for all Pixel 6 Pro's if everything has gone to plan.
So, as an explanation to why the Pixel 8 Pro works, but the plain 8 doesn't - It is very likely to me there are a lot more Pixel 8 Pros and that process with testing has happened for them. Unfortunately, this is how it will be with all new developments on all unsupported phones, at least for this carrier. This is as much as I've been told.

@fillwithjoy1 This is maybe the case in general, but I know it isn't for this provider. They roll out 5G support based on the CCID of the SIM. Older cards that they have registered before a set date, do not work with 5G. I have confirmation from their support team.

@bossnass At this point, I have received multiple calls from their support, and since we're a corporate user with upwards of a thousand users, we get very good support. They have even asked me to explain some workarounds I've done to get it working lol. To my knowledge, the customer service has recommended this project to at least two other corporate accounts based on my feedback (Which is wild, but this is Bulgaria after all). I know they are not as precise with typical clients of theirs. From what I've been told, they're testing this out on some phones which report to the cellular systems that they support certain technologies (VoLTE, 5G, additional cellular bands for LTE) and are enabling them per device ID for a period of six months. This has started for the Pixel 6 Pro in mid October. Unfortunately, they cannot choose who goes on their testing CID system, since it is apparently randomized and automated. They will notify me if my SIM gets to that program. But even if it has, by April 2025, it should work for all Pixel 6 Pro's if everything has gone to plan. So, as an explanation to why the Pixel 8 Pro works, but the plain 8 doesn't - It is very likely to me there are a lot more Pixel 8 Pros and that process with testing has happened for them. Unfortunately, this is how it will be with all new developments on all unsupported phones, at least for this carrier. This is as much as I've been told.

I have noticed that my carrier settings date has pretty different date as opposed to the people around me which are using Pixel phones. Even asked a guy who has Pixel 6. And guess what - no one else seems to have VoLTE setting available. It is just me.

That's very very weird. Pixels don't (generally) contain much proprietary blobs in core system functions - it's (mostly) pure android after all. Either the carriers have messed up with their implementation that it "just works" on some and not on others. I know Samsung devices have different setups since they have workarounds to force backup calling and such.