Announcement

Collapse
No announcement yet.
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Plan accordingly - No TAPI after upgrade to Connect 19.1-SP1 - 22.11.4900.0

    We have done two upgrades to 22.11.4900.0, both from Connect, and both had the No TAPI issue. Had to back up, uninstall & reinstall.

    Everything works with the reinstall but plan for an additional 90 minutes.

    Hopefully it won't hit you.

    ----------------------------------------------------------------------------------------------------

    https://oneview.mitel.com/s/article/...pgrade-to-19-1

    TAPI down after upgrade to 19.1


    Dec 12, 2019•Problem Resolution

    Scenario
    After an upgrade to 19.1, HQ or DVS may show a red TAPI status in diagnostics and monitoring.

    NOTE: Prior to taking steps to fix this issue, please take a snapshot of the server in a broken state. Then, preserve the OVA and snapshot files PRIOR to resolving the problem. Providing the OVA and snapshot to TAC and Engineering will assist us in resolving this issue permanently. Thanks in advance for opening a TAC case with details and the attachments.

    Symptoms
    Auto attendants, voicemail and workgroups may be non-functional.


    Cause


    More Information


    Resolution
    Currently, the only known resolution is to uninstall/reinstall the MiVoice Connect software on the affected systems. https://oneview.mitel.com/s/article/...for-HQ-and-DVS

    NOTE: Prior to taking steps to fix this issue, please take a snapshot of the server in a broken state. Then, preserve the OVA and snapshot files PRIOR to resolving the problem. Providing the OVA and snapshot to TAC and Engineering will assist us in resolving this issue permanently. Thanks in advance for opening a TAC case with details and the attachments.









  • #2
    This happened to me and I lost sleep over this. They should've pulled this build IMO.

    Comment


    • #3
      I wonder if anyone has updated and not run into the issue.

      Comment


      • #4
        We're about to look at upgrading to this one as we're being mandated to use LDAPS - fortunately it looks like it's being delayed for a bit and with any luck we'll be shot of this platform by that point...

        Comment


        • #5
          What build were you on before you upgraded? Was it 14.x or another Connect build?

          Comment


          • #6
            Both were already on Connect, upgrading to be able to use the Mitel phones.

            Comment


            • #7
              We have seen updates without this issue. I have also seen it happen across the board for every build old and new at one point. Truthfully, I think it's likely due to how windows handles patches and updates. They often kill previous patches and updates and replace them with bundles that can skip some of the tiny incremented updates that may have been needed to be included.
              Lance Paddock
              BTX | Business Telephone eXchange
              1(800) 289-0299

              Comment

              Working...
              X