System Admin stuck on updates 10.13.66-5

System admin seams to be stuck on updates been sat on the same one for 24hrs and our Sangoma A200 isnt hanging up calls when a caller disconects, if i do a manual upgrade to the next release i am going to break something as the system admin is stuck doing something?

2017-04-11 18:44:12: (10.13.66-19) Processing update
2017-04-11 18:44:12: (10.13.66-19) Now running 10.13.66-4 script
2017-04-11 18:44:12: (10.13.66-4) Starting stage 1
2017-04-11 18:50:28: (10.13.66-4) Stage 1 complete
2017-04-11 18:50:28: (10.13.66-4) Starting stage 2
2017-04-11 18:59:08: (10.13.66-4) Stage 2 complete
2017-04-11 18:59:09: (10.13.66-4) Starting stage 3
2017-04-11 18:59:09: (10.13.66-4) Stage 3 complete
2017-04-11 18:59:09: (10.13.66-4) Starting stage 4
2017-04-11 18:59:12: (10.13.66-4) Stage 4 complete
2017-04-11 18:59:12: (10.13.66-4) Starting stage 5
2017-04-11 18:59:12: (10.13.66-4) Stage 5 complete
2017-04-11 18:59:12: (10.13.66-4) Starting stage 6
2017-04-11 18:59:12: (10.13.66-4) Stage 6 complete
2017-04-11 18:59:13: (10.13.66-4) Upgrade script complete
2017-04-11 18:59:13: (10.13.66-19) Upgrade process successfully completed!
2017-04-11 18:59:13: (10.13.66-19) Requesting updates
2017-04-11 18:59:14: (10.13.66-19) Processing update
2017-04-11 18:59:14: (10.13.66-19) Now running 10.13.66-5 script
2017-04-11 18:59:14: (10.13.66-5) Starting stage 1

Try running

/usr/sbin/sysadmin_update_system --unlock

from the command line and then going back to your updates page

Many thanks for that, it unlocked the the update button.

Tried updating again and now back in the same position, is there a problem with system admin doing upgrades ? cant get past 10.13.66-4

Locate and view the content of the file:

/var/log/pbx/upgrade/10.13.66-5

to examine where the script is stalling, it may be a clue to what is going on. Alternatively, unlock and try your luck again.

Finally got upgraded after a few unlocks.

Is there any know faults with DAHDI settings as my A200 card wont detect a caller hanging up