Calls not working on FP4 patch 7.5

System and Apps
21

Thank you very much!

But first , I must catch someone from the support team. :smirking_face::person_raising_hand:

22

So an update from my side.

I have been trying to get in contact with the customer support of Yallo. What an ordeal…

After somewhat unsuccessfully trying to contact them via chat bot / e-mail, I bit the bullet today and gave them a call using their paid (!) support-number from an other phone. They said, that their technicians checked my line, and everything appears to be working. Since I told them, that obviously something is wrong, they will do a re-check and a technician should get in contact with me…

I also tested the following:

  • Inserted my Yallo Sim-Card into a Samsung with Iodé 7.5 - same issue
  • Inserted a different Yallo Sim-Card into my FP4 Iodé 7.5 - same issue
  • Inserted a Swisscom Sim-Card into my FP4 Idoé 7.5 - worked and IMS registred, could make phone calls

So the problem persists.

1 Like
23

Little ad on….

I updated to 7.6 and nothing chanced.

The story coutinues…

1 Like
24

I did some more log analysis with the Swisscom-Sim and the Yallo-Sim for comparison:

  1. Default config with the Yallo-Sim (IMS APN protocol = IPV6): modem repeatedly attempts IMS PDN, network rejects every attempt with PDN_IPV6_CALL_DISALLOWED(0x7f3), infinite retry loop, no registration.
  2. IMS APN protocol changed to IPV4V6: CNE stops requesting IMS network entirely. No attempts at all.
  3. All other APN permutations (delete IMS APN, combine types on Internet APN, etc.): broken.
  4. SIM swap to Swisscom on the same install: works flawlessly — IMS PDN connects with P-CSCFs, calls work.
  5. Interestingly: With the Yallo Sim the preferences menu has a VoLTE toggle, where as with the Swisscom-Sim it is a “Use 4g for Calling” one.

So I’m still not fully convinced, that this a pure Carrier-side issue.

1 Like
25

What if you try IPV4 “only” (not IPV4V6)?

26

yeah also tried that, but didn’t change a thing.

Also Yallo Customer Support wrote this morning saying they did a “network-reset” to re-establish my connection. But now I cannot even send sms anymore or forward my calls.

27

Can you again reset mobile network settings, and check your SIM / APN settings and if all good there then again look at *#*#4636#*#* to see if you are getting registered? Is Yallo not giving anything more than “they reset something”? I mean can they confirm the FP5 is allowed on their network at least (and is not prevented from registering)?

28

In our case, I had to quit the mobile contract. TalkTalk in Switzerland has no customer support — or rather, what they call “support” doesn’t deserve that name. Wow!

Now, finally, I have to find a new contract and still pay for no service… :expressionless_face:

By the way, in my eyes the problem is on both sides: TalkTalk’s (Sunrise’s) incompetence and the IodeOS update…

The story continues… :person_raising_hand:

29

So I had a small breakthrough yesterday. Found a workaround that gets IMS to register on Yallo / Sunrise MVNOs

After a lot of tinkering, two changes to the IMS APN are needed (one alone isn’t enough):

  1. APN protocol: change IPv6 → IPv4. Default IPv6 produces PDN_IPV6_CALL_DISALLOWED(0x7f3) from the Sunrise network on every PDN attempt.

  2. APN type: change ims → ims,cbs (or ims,ia, or various other combinations). With type=ims only, the data manager / CNE never actually requests the IMS PDN. Adding any extra type that doesn’t conflict with another APN unblocks it. In my testing, the working set ends up being pretty much anything except the types already claimed by the Sunrise Internet APN (default, supl) and the MMS APN (mms).

Steps: Settings → SIMs → APNs → IMS → set protocol to IPv4, set type to e.g. ims,cbs → save → reboot.

Result on my FP4 + Yallo: IMS now registers, incoming calls work. Outgoing calls and sms currently fail with a network-side “Access to the number you dialed is barred” voice announcement. I’m not sure yet what causes this — the timing suggests Yallo’s recent “connection reset” left my account in some odd state, but I haven’t confirmed that with them. SMS sending and call forwarding modifications are also broken (#330*PIN# returns generic MMI errors, though *#21# interrogation still works), so something supplementary-services-related is off. Following up.

I’m not giving up on this :smiley:

2 Likes
30

Hi SubCee

You solved it for me!:confetti_ball::tada::confetti_ball::tada::confetti_ball::tada::confetti_ball::tada:

I followed your description and now in and out calling is working on the mobile of.my son!

If is working on the mobile of my daughter, I have to remade the contract…ufff….
Thank you in every case​:+1::handshake::person_raising_hand:

1 Like
31

Did you enter the APN type IMS as an additional APN or changed the default of Yallo?

32

Great to hear of the progress. Its always the APN settings seems to hopefully be the answer here (the mobile phone variant of its always DNS :slight_smile: ).

To the separate APNs for “internet” and “mms”, do they have different APN values? If not, then most common is to have a single APN, just adding the values for the MMSC field for MMS functionality. But if it works with 2 APNs (and you can activate both of them at the same time) then don’t poke a happily sleeping dog!

Lastly, I am surprised to see that MMS is used? I thought us poor 'muricans were the only ones still using MMS so that iPhone users can contact us? (well I know of it being used sparingly in France too I think).

33

I changed the default one…

34

Well the “default” actually returns to three APN. Internet; IMS and MMS.

I have no clue to why we still have MMS to be honest. Maybe if you want to send an image the old fashioned way.

Sadly my calling still won’t work, since my Calls still get barred by the carrier. Getting a hold of Yallo-Support again for this will probably take me another week…

@volker01 just change the default IMS APN to IPv4 and add another APN Type from the list as described in my previous post.

35

Or to use group messages via SMS

36

Resolved: full fix description for future readers

Calls are working again. The complete fix was two-part: an iodéOS-side APN tweak, plus a carrier-side re-provisioning by Yallo (in my case).

Part 1 — iodéOS side (the easily fixable part)

Default iodéOS 7.X ships the Sunrise/Yallo IMS APN with settings that don’t work on this network. Two changes are needed (one alone isn’t enough):

  1. Protocol: change IPv6 → IPv4. Default IPv6 produces PDN_IPV6_CALL_DISALLOWED(0x7f3) from the Sunrise network on every IMS PDN attempt.

  2. Type: change ims → ims,cbs (or any combination including ims plus another type that doesn’t conflict with another APN — i.e. anything except default, supl, mms, which are already claimed by the Sunrise Internet and MMS APNs). With type=ims only, iodéOS 7.5 doesn’t actually request the IMS PDN.

Steps: Settings → SIMs → APNs → IMS → set protocol to IPv4, set type to e.g. ims,cbs → save → reboot.

After this, IMS registers and calls should work again.

Part 2 (optional): Yallo side (the carrier-fixable part)

After the APN fix, my outgoing calls were still blocked at the network with a “Access to the number you dialed is barred” voice announcement, SMS sending didn’t work, and supplementary-services MMI codes returned generic errors. After contacting Yallo customer service a couple of times, they did another reset/re-provisioning on their backend, which restored outgoing calls, SMS, and supplementary services.

Thanks to everyone in this thread for the cross-device test data and @rik for engaging with the diagnostics. Hope the APN workaround above gets you up and running quickly too.

2 Likes
VoLTE unavailable on fairphone 5
Galaxy Note 10+ SM-N975F – microphone not working during cellular calls on iodeOS 7.5
iodéOS 7.5 – VoLTE broken with Sunrise network (Switzerland) – proven carrier-specific, not device-specific
37

:partying_face:

Thank you for the time to write up the solution. I hope this will assist other users having problems with the Sunrise network. I will link them back to your post for reference.