Ramen

@Rabs did you update the entire application or just specific files? Could you specify what you observe in the CallLogs submodule after the modification? Also, I apologize for the delayed response; I inadvertently overlooked your last message 😓

@Zain I tested and it's working as expected for me and I'm in Canada/Nova Scotia

No worries and always here to help @Rabs though please let me know if you get that done/fixed on 4.3 (so that I can sleep better at night 😅)

@Rabs utilizing the master branch instead of simply updating the library and callLogs would have been a viable alternative. Nonetheless, I would personally refrain from doing so due to the substantial differences between the 4.3.x and master/5.3.x versions. There is a possibility that certain functionalities may have been altered; for example there is new Call Forwarding update coming and when merged new build from master will defiantly break Call Forwarding on 4.3 in voip/SmartPBX

Interesting. I just tested with https://github.com/2600hz/monster-ui/tree/4.3 on my local install and it seems to be working, could you please check which Monster UI package you have in staging as well as share the console logs if any for when those files are changed/the white screen in voip/SmartPBX As per Monster UI documentation node >= 12 & npm. However, my default for development/testing is v14.18.0 and you can follow for investigation on local install Clone repos for Monster UI and voip/SmartPBX with branch 4.3 Change node version to v14.18.0 Install dependencies using npm install Update config.js and you should be able to use the same as your staging environment Make changes to to Monster UI and voip/SmartPBX as per https://github.com/2600hz/monster-ui/blob/2391d035888fe9fcb676bb28c5b5aa8449a35cbc/src/js/vendor/moment.js for moment.js and https://github.com/2600hz/monster-ui-voip/blob/a249edd45e60052b4624efc4020766e647643a83/submodules/callLogs/callLogs.js for callLogs.js Build and launch the web server using gulp If everything worked as expected run gulp build-prod for creating main.js Let me know how that goes/if you need any further assistance 🙂

Hi @davicito welcome to the community! It's great to have you here, especially with your background in Erlang and don't worry too much about being new to telecom concepts and protocols – we all start somewhere, and this community is here to support you. If you ever have any questions or need guidance, feel free to ask. We're a friendly bunch, and we're more than happy to help you dive deep into Kazoo and explore the wonderful world of telecommunications.

@Rabs on way would be to update moment.js library and callLogs.js. You could do that by download monster-ui and monster-ui-voip from GitHub with branch 4.3 after that update moment.js with the changes that are in the PR https://github.com/2600hz/monster-ui/blob/2391d035888fe9fcb676bb28c5b5aa8449a35cbc/src/js/vendor/moment.js for moment.js and https://github.com/2600hz/monster-ui-voip/blob/a249edd45e60052b4624efc4020766e647643a83/submodules/callLogs/callLogs.js for callLogs.js Once that is done run gulp build-prod and copy main.js from /dist/js and callLogs (attaching file to this message in case you have any issues) to the same location where you have the production Monster UI. callLogs.js main.js

Hi @Rabs for Monster UI there was a issue but it was fixed though only against master/Monster UI 5.x releases. The fix PR(s) would be https://github.com/2600hz/monster-ui/pull/1059 and https://github.com/2600hz/monster-ui-voip/pull/485

Hi @Yan Mesa welcome to the community. As a Canadian, it always makes me happy to see companies from here using 2600Hz products.

Hi @Claude Lamothe welcome to our forums and community.

Hi @AsifHaswarey welcome to the community 🙂

Hi @Lidiomar welcome back to the community! It's great to have someone with your level of experience in telecommunications join us. We look forward to seeing your contributions and interactions with everyone 🙂

Hi @omnicap, lets get started indeed and very welcome to the community 🙂

Hi @Fordy very very welcome to the community 🙂

Hi @Ron and you are very welcome here 🙂