5

iOS visual voicemail malfunction

Hi,

 

I’m posting here hoping someone will be able to help me. I encounter a strange behavior with visual voicemail on my iPhone.

 

I’m using an iPhone 12 Pro Max on the latest iOS version (14.5.1) with two SIM cards:

An Orange France eSIM

A Bouygues Telecom physical SIM

Both carrier settings versions are on 46.0

 

When I get a voicemail on the physical SIM card everything is working as expected, but when I get one on the eSIM, as long as NextDNS is enabled I won’t receive the voicemail notification, which is pretty annoying.

I was able to reproduce the same malfunction on two different iPhones with the same configuration. Nothing seems to be blocked in the logs so I can’t understand what’s wrong, especially since everything else (like VoLTE, WiFi Calling etc.) is working great.

 

Thanks you in advance

37 replies

null
    • Indiana_Jones
    • 3 yrs ago
    • Reported - view

    I'm sorry to hear that you're experiencing issues with your visual voicemail on your iPhone. Based on the information you've provided, it seems that NextDNS may be causing the issue with the eSIM voicemail notifications not coming through.

    NextDNS is a DNS filtering service that can block certain websites or services based on user-defined rules. It's possible that NextDNS is blocking the notification for eSIM voicemail, which is why you're not receiving the notification.

    To troubleshoot the issue, you could try disabling NextDNS temporarily and see if the eSIM voicemail notifications come through. If they do, then it's likely that NextDNS is the culprit. You can then try adjusting the NextDNS rules to allow the voicemail notification to come through.

    If disabling NextDNS doesn't resolve the issue, you could also try resetting your network settings on your iPhone. This will reset your Wi-Fi, cellular, and Bluetooth settings to their default values, and may help resolve any network-related issues that could be causing the problem.

    To reset your network settings on your iPhone, go to Settings > General > Reset > Reset Network Settings. You'll need to enter your device passcode to confirm the reset.

    I hope this helps resolve the issue you're experiencing with your eSIM voicemail notifications. If you continue to experience problems, you may want to contact your carrier's support team for further assistance.

    Source: SMSala

      • Tom_King
      • 3 yrs ago
      • Reported - view

      NextDNS thank you. Where in the NextDNS native app client or the NextDNS web app UI can we add to the ignored domains list?

      Maybe I missed that and thought the mobile configuration profile “excluded domains” was the only way to achieve that. 

      • Jaffajim
      • 1 yr ago
      • Reported - view

      I have the same "issue" (EE, UK carrier) and the workaround of adding vvm.ee.co.uk to the exclude list when creating the profile works perfectly. However, it would be extremely beneficial to be able to do this from the app too, for at least one use case:

      I manage my child's iPhone using Apple's usual Parental Controls  functionality. However, while I can add a profile to the phone, my child would be in theory able to remove the profile without any restriction, since there is no way of locking down the relevant VPN menu in the phone.

      With the app, this isn't possible - enabling the passcode for the app means the app cannot be disabled. However, it also means that Visual Voicemail cannot be added  because there is no way to add the excluded domain.

      - Adding the ability to exclude domains in the app could be useful for everyone who does the same thing. Is this possible?

    • underpants_gnome
    • 2 yrs ago
    • Reported - view

    If anyone has the domains to exclude for Verizon or AT&T, please post them.

    • No_Name.1
    • 2 yrs ago
    • Reported - view

    No matter what I do, I get an error message when adding excluded domains on apple.nextdns.io. Attached is a screenshot. If I don't add excluded domains to the profile generator, it downloads fine.

     

    The error says

    {"errors": [ {"code": " internalserverError"}]}

      • No_Name.1
      • 2 yrs ago
      • Reported - view

      No Name can anyone from nextdns help?

    • No_Name.1
    • 2 yrs ago
    • Reported - view

    The config appears to fail (meaning it outputs a .json instead of .mobileconfig) if I include the * symbol, as bobssmith used in his post.   Is that symbol needed to have the voicemail work properly after adding the config?

    e7.vvm.mstore.msg.t-mobile.com
    *.e6.vvm.mstore.msg.t-mobile.com
    *.e4.vvm.mstore.msg.t-mobile.com
    *.e3.vvm.mstore.msg.t-mobile.com
    *.e2.vvm.mstore.msg.t-mobile.com
    *.e1.vvm.mstore.msg.t-mobile.com
    *.e.vvm.mstore.msg.t-mobile.com
    *.e5.vvm.mstore.msg.t-mobile.com
    *.t-mobile.com
    *.msg.t-mobile.com
    *.mstore.msg.t-mobile.com
    *.vvm.mstore.msg.t-mobile.com
     

      • Tom_King
      • 2 yrs ago
      • Reported - view

      No Name I’m not a NextDNS employee , but suggest you might try the same entries without the leading “*.” — it should have the same effect for excluding domains. 
       

      BUT, I’m not sure that’s why you’re getting a .json file. 

    • N_C
    • 2 yrs ago
    • Reported - view

    I’m having the same issue with Visual Voicemail (and presumably some other services I haven’t noticed yet) with Vodafone Australia. I have to disable the NextDNS profile on my iPhone constantly if I want to receive voicemail or even alerts about having received voicemail.

    I can’t seem to find a list of DNS host names to exclude in my iOS configuration profile anywhere. Is there any chance someone can give me a hand?

      • Roland_Fritz
      • 2 yrs ago
      • Reported - view

      See the instructions above of how he found the issue in the logs. It is a bit of a process. You might just be better off with google-fu searching enterprise networking documentation for your carrier or trying just putting their entire domain in the exclude. eg just "t-mobile.com" which will skip NextDNS for every subdomain as well. I wouldn't consider this secure but it might be good enough for your needs.

    • rutij
    • 2 yrs ago
    • Reported - view

    Had the same issues with Orange Belgium, excluded domain vvm.mobistar.be and all working as intended now 👍

    • Richard_Osterreicher
    • 1 yr ago
    • Reported - view

    Hey

    The exeption for Magenta Austria (T-Mobile Austria) is:

    tma.vvm.mone.pan-net.eu

    br, Richard

    • Rameez
    • yesterday
    • Reported - view

    Hi,

    This looks less like a device issue and more like a DNS/network-level interference with carrier services, especially since you mentioned NextDNS is enabled and the issue only affects the eSIM line.

    Visual Voicemail (VVM) and voicemail notifications rely on carrier-specific endpoints and background network calls, not just standard SMS signaling. When using a custom DNS like NextDNS, it can sometimes block or filter those endpoints unintentionally — particularly on eSIM profiles where provisioning can behave slightly differently.

    A few things you can try to isolate and fix the issue:

    1. Temporarily disable NextDNS
       Check if voicemail notifications start working normally on the eSIM
       If yes, then it’s clearly DNS filtering related
    2. Whitelist carrier domains in NextDNS
       Add your operator’s voicemail/VVM domains (Orange/Bouygues)
       These are often not obvious and may require checking logs inside NextDNS
    3. Reset carrier settings / network settings
       Settings - General - Transfer or Reset iPhone - Reset Network Settings
      (this can refresh VVM provisioning)
    4. Check cellular data switching behavior
       Dual SIM setups sometimes route background services differently
       Try setting the eSIM as primary data temporarily
    5. Re-provision Visual Voicemail
       Toggle airplane mode
       Restart device
       Or contact carrier to refresh VVM provisioning

    Why this is happening

    NextDNS may be blocking or delaying requests required for voicemail push/visual voicemail sync. Since SMS/VoLTE works fine, it suggests the issue is limited to IP-based carrier services, not core telephony.

    If disabling NextDNS resolves it, the long-term fix would be adjusting filtering rules rather than changing device settings.

    Let us know what you observe after testing

Login to reply

Content aside

  • 5 Votes
  • yesterdayLast active
  • 37Replies
  • 3211Views
  • 26 Following