Getting an error updating from 2.1.1-1 to 2.3.0.-2

› VitalPBX Community Support › General Discussion › Getting an error updating from 2.1.1-1 to 2.3.0.-2

  • Post
    • March 14, 2019 at 3:35 pm
    DannyLarsen
    Participant
    none

    When updating from the gui from 2.1.1-1 to 2.3.0-2

    After clicking for the update, I get a red error

    “Cannot update to the latest version”

    Thanks

    0
Viewing 14 replies - 16 through 29 (of 29 total)
1 2
  • Replies
    • March 14, 2019 at 9:52 pm
    DannyLarsen
    Participant
    none
    Up
    -1
    Down

    I moved my backup to a fresh server and it solved the issue with the CDR not showing up

    However I now see that I cannot save any changes in the System/Misc section

    Such as Time, Notification and Storage

    This issue shows up on the fresh server install and the updated server

    0
    • March 14, 2019 at 9:53 pm
    DannyLarsen
    Participant
    none
    Up
    -1
    Down

    Also the Backup/Restore function won’t take a backup file larger than 150M

    So I had to unzip the Call Recordings and VoiceMail by hand

    Thanks

    0
    • March 14, 2019 at 10:09 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    -1
    Down
    Posted by: DannyLarsen

    I moved my backup to a fresh server and it solved the issue with the CDR not showing up

    However I now see that I cannot save any changes in the System/Misc section

    Such as Time, Notification and Storage

    This issue shows up on the fresh server install and the updated server

    About this issue, I just tried in a clean installation but the only thing that I noticed was that I can’t update the time zone when the NTP is enabled. However, if you disable the NTP, you may update the timezone.

    I didn’t see any other issue on this module.

    0
    • March 14, 2019 at 10:17 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    -1
    Down
    Posted by: DannyLarsen

    Also the Backup/Restore function won’t take a backup file larger than 150M

    So I had to unzip the Call Recordings and VoiceMail by hand

    Thanks

    About this, you may set the maximum upload size in the following file: /etc/php.d/vpbx.ini and then restart the httpd service (systemctl restart httpd). 

    We expect to make the max upload size parameter available from the GUI in the next versions.

    0
    • March 20, 2019 at 8:44 pm
    DannyLarsen
    Participant
    none
    Up
    -1
    Down

    Another issue we are seeing here is associated with voice mail. The mailboxes after the update were disabled but showing enabled in the web gui. I had to do an update on each extensions voice mail then a reload in order to re enable them

    0
    • March 20, 2019 at 8:59 pm
    DannyLarsen
    Participant
    none
    Up
    -1
    Down

    Also Message waiting indication no longer works in V2.3.0-3

    Testing on Yealink T46S and T54S phones which was working previously

    0
    • March 21, 2019 at 8:58 pm
    tonywhelan
    Participant
    Up
    -1
    Down

    On a Yealink T23G, the Missed Call light shows BUT the Message Waiting Indicator light doe snot come on. However if I do a Core Reload the MWI shows and the LCD displays shows there is a New VoiceMail

    However when I access voicemail and delete the message, the Missed Call and MWI lights and the New VoiceMail display on the LCD screen all will not turn off. If I repeat the Core Reload, MWI and New VM message do get cleared, but Missed Call lamp continues to flash.

    Looks like something has become scrambled in the last update?

     

    0
    • March 21, 2019 at 9:11 pm
    tonywhelan
    Participant
    Up
    -1
    Down
    Posted by: tonywhelan

    On a Yealink T23G, the Missed Call light shows BUT the Message Waiting Indicator light doe snot come on. However if I do a Core Reload the MWI shows and the LCD displays shows there is a New VoiceMail

    However when I access voicemail and delete the message, the Missed Call and MWI lights and the New VoiceMail display on the LCD screen all will not turn off. If I repeat the Core Reload, MWI and New VM message do get cleared, but Missed Call lamp continues to flash.

    Looks like something has become scrambled in the last update?

     

    Ah, the Missed Call light is not a problem, I forgot that you have to press the History button to clear it.

     

    0
    • March 21, 2019 at 9:15 pm
    tonywhelan
    Participant
    Up
    -1
    Down

    Just tested this with a different handset – a Grandstream GXP1610 handeset.

    Same problem – the Message Waiting Indicator light does not come on. If I do a Core Reload the MWI shows, and I get stutter dialtone ok. But then I delete the message, the MWI continues to show and stutter dialtone remains.

    0
    • March 21, 2019 at 9:37 pm
    tonywhelan
    Participant
    Up
    -1
    Down

    Just tested the last beta version of VitalPBX (2.2.2-1rc) on a spare machine and the same problem existed on that version – no MWI or stutter dialtone till core reload, can’t clear MWI till do another core reload. Tested with a SNOM300 handset on this one.

    0
    • March 21, 2019 at 10:12 pm
    tonywhelan
    Participant
    Up
    -1
    Down
    Posted by: tonywhelan

    Just tested the last beta version of VitalPBX (2.2.2-1rc) on a spare machine and the same problem existed on that version – no MWI or stutter dialtone till core reload, can’t clear MWI till do another core reload. Tested with a SNOM300 handset on this one.

    On that test machine I just did an update to the latest VitalPBX version, and the problem has disappeared on that machine.

    But my production machine  continues to have the problem, even though it is up-to-date.

    Very confusing.

    0
    • March 21, 2019 at 10:34 pm
    DannyLarsen
    Participant
    none
    Up
    -1
    Down

    Sorry here is another issue I found when adding a fax device

    When applying the changes I get this error

    I did remove the fax module via yum and reinstall,  same issue

    0
    • March 21, 2019 at 10:38 pm
    Jose Miguel Rivera
    Keymaster
    NI
    Up
    -1
    Down

    Just change the owner and group to apache for that file

    0
    • March 22, 2019 at 2:56 pm
    DannyLarsen
    Participant
    none
    Up
    -1
    Down

    The file did not exist, so I created it and changed the ownership

    It is working now

    Thank you

    0
Viewing 14 replies - 16 through 29 (of 29 total)
1 2
  • You must be logged in to reply to this topic.