Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-21715

Android - Calling Accounts - Voicemail Deactivation



    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Support
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Zulu (Commercial)
    • Labels:
    • ToDo:


      • Zulu Server: © Sangoma
      • PBX: v14.0.13.28 © Sangoma
      • Zulu UC Android Version 1.1.1 (beta group)
      • Android Phones: OnePlus 6T and Pixel 4 XL

      Description of Problem
      I’ve noticed this issue when I was on my OnePlus 6T since a year ago and have noticed the problem persist onto my Pixel 4 XL for the last 6 months, which tells me this is an issue with Zulu UC app as it’s evident it is not affecting just one type of phone.

      When Zulu is enabled as an additional calling account, the visual voicemail under the Android’s default phone app disappears. Once the visual voicemail is deactivated and then re-enabled, the visual voicemail option will reconnect to the provider and retrieve voicemail and presents the visual voicemail option again under the default android phone app. The issue is, it’s only temporary, and then visual voicemail disappears again.

      If Zulu UC is disabled as an additional calling account, it does not affect the visual voicemail problem; however, you can’t use Zulu UC as a calling account at that point and chat will function, but you get an annoying prompt to enable Zulu UC as a calling account each time you get into the app.

      I’ve noticed that I have other apps that do make calls as well, such as Telegram, Skype, Google Voice but these aren’t listed under Calling Accounts while Zulu UC is. Is Zulu UC different than other types of app that function in a similar fashion?

        Gliffy Diagrams




              • Assignee:
                wkeit S.L
              • Votes:
                0 Vote for this issue
                3 Start watching this issue


                • Created:


                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.