Jump to content

Rabs

Members
  • Posts

    44
  • Joined

  • Last visited

1 Follower

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @Ramen I have followed the above steps and the outcome was not as expected. The calllog submodule does not function with I use PR https://github.com/2600hz/monster-ui-voip/blob/a249edd45e60052b4624efc4020766e647643a83/submodules/callLogs/callLogs.js Is there any other way to fix it with the calllog code block? Also, I have attached the dist folder for you incase if you would like to check it out on your end. dist.tar.gz
  2. @Ramen In that case, I would refrain from doing so and will fall back to 4.3. Thank you so much for your support and prompt response. Much appreciated :)
  3. @Ramen Thank you so much for your detailed instructions. I changed the node version to 14.18.0 and it worked on 4.3. Btw, I was using v16.18.1. Another interesting way I was able to solve the issue was by downloading the master branch of monster-ui, and monster-voip and being successful in building from scratch. Once the building was completed, I replaced the entire monster-ui folder with the latest files and folder from the dist folder and that seems to have worked. It was kinda long path but totally worth it!!
  4. @Ramen Thank you so much for your support and also, Your forward-thinking is much appreciated. I have uploaded your attached file into the respective folders: main.js --> /var/www/html/monster-ui/js/main.js callLogs.js ---> /var/www/html/monster-ui/apps/voip/submodules/callLogs/callLogs.js After that, on my Monster-UI - I pressed Ctrl+R. The result was a blank white screen on the SmartPBX App as per the attached image below. All other apps like Number, Voicemail, Accounts, etc. are working except SmartPBX after replacing the previous files with the new files. If I roll back the changes, SmartPBX will start to work. I also tried to npm install before gulp build-prod (apparently won't work without running npm install first) on 4.3 Github branch and that resulted in an error. Logs are pasted below for your reference. (my OS is Centos 7) could be related to npm version issues. Kindly advise what npm version should I use Yes, I did run into npm install issues with 4.3 branch. npm WARN deprecated core-js@2.6.11: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm ERR! code 1 npm ERR! path /opt/monster-ui/node_modules/node-sass npm ERR! command failed npm ERR! command sh -c -- node scripts/build.js npm ERR! Building: /usr/bin/node /opt/monster-ui/node_modules/node-gyp/bin/node-gyp.js rebuild --verbose --libsass_ext= --libsass_cflags= --libsass_ldflags= --libsass_library= npm ERR! gyp info it worked if it ends with ok npm ERR! gyp verb cli [ npm ERR! gyp verb cli '/usr/bin/node', npm ERR! gyp verb cli '/opt/monster-ui/node_modules/node-gyp/bin/node-gyp.js', npm ERR! gyp verb cli 'rebuild', npm ERR! gyp verb cli '--verbose', npm ERR! gyp verb cli '--libsass_ext=', npm ERR! gyp verb cli '--libsass_cflags=', npm ERR! gyp verb cli '--libsass_ldflags=', npm ERR! gyp verb cli '--libsass_library=' npm ERR! gyp verb cli ] npm ERR! gyp info using node-gyp@3.8.0 npm ERR! gyp info using node@16.18.1 | linux | x64 npm ERR! gyp verb command rebuild [] npm ERR! gyp verb command clean [] npm ERR! gyp verb clean removing "build" directory npm ERR! gyp verb command configure [] npm ERR! gyp verb check python checking for Python executable "/usr/bin/python3" in the PATH npm ERR! gyp verb `which` succeeded /usr/bin/python3 /usr/bin/python3 npm ERR! gyp ERR! configure error npm ERR! gyp ERR! stack Error: Command failed: /usr/bin/python3 -c import sys; print "%s.%s.%s" % sys.version_info[:3]; npm ERR! gyp ERR! stack File "<string>", line 1 npm ERR! gyp ERR! stack import sys; print "%s.%s.%s" % sys.version_info[:3]; npm ERR! gyp ERR! stack ^ npm ERR! gyp ERR! stack SyntaxError: invalid syntax npm ERR! gyp ERR! stack npm ERR! gyp ERR! stack at ChildProcess.exithandler (node:child_process:402:12) npm ERR! gyp ERR! stack at ChildProcess.emit (node:events:513:28) npm ERR! gyp ERR! stack at maybeClose (node:internal/child_process:1100:16) npm ERR! gyp ERR! stack at Process.ChildProcess._handle.onexit (node:internal/child_process:304:5) npm ERR! gyp ERR! System Linux 3.10.0-1160.53.1.el7.x86_64 npm ERR! gyp ERR! command "/usr/bin/node" "/opt/monster-ui/node_modules/node-gyp/bin/node-gyp.js" "rebuild" "--verbose" "--libsass_ext=" "--libsass_cflags=" "--libsass_ldflags=" "--libsass_library=" npm ERR! gyp ERR! cwd /opt/monster-ui/node_modules/node-sass npm ERR! gyp ERR! node -v v16.18.1 npm ERR! gyp ERR! node-gyp -v v3.8.0 npm ERR! gyp ERR! not ok npm ERR! Build failed with error code: 1 npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2023-09-04T02_28_04_035Z-debug-0.log
  5. Thank you @Ramen and @mc_ for your prompt response @Ramen Would you provide any guide/direction on how to manually apply this fix on monster-ui 4.3? Or do I have to manually rebuild monster-ui using 5.X GitHub and would that work on Kazoo 4.3.? Looking forward to your response
  6. Hi @mc_ & Kazoo community, hope everyone is doing well I'm not sure if this is a timezone issue on Kazoo 4.3 or a system time issue but we have a problem with time stamping on our call logs.. All the call logs are one hour ahead. For eg: The account is set to: Australia/Melbourne timezone and the Current time is 12:43 PM 31 Aug 2023. In the Centos 7 system time on which Kazoo 4.3 was installed date is Thu Aug 31 02:43:00 UTC 2023 but in the monster-ui call log it shows 01:43 PM 31 Aug Any idea how this can be fixed? Any help would be appreciated. Thank you
×
×
  • Create New...