All Activity

This quarter our team has been hard at work preparing product updates and apps for Kazoocon. Be sure to secure your tickets and join us in Las Vegas! Partner Spotlight Did you know that agents typically spend close to 10 minutes on a single call? The agent then spends nearly the same amount of time documenting and classifying the calls, writing 100-word summaries, and completing other required actions in the company’s system of record. In this case, note-taking is approximately 50% of the total handle time. CPaaS Acceleration Alliance recently featured a game-changing innovation by Vinix and 2600Hz - one that could redefine how we handle note-taking during calls, saving both time and money. Mark Diaz, the CEO of Vinix, highlighted the challenge of taking notes during a live call. Listening and typing simultaneously is not only arduous but often results in critical information being missed. It's a skill that many call center agents struggle to master effectively. Recognizing this challenge, 2600Hz and Vinix joined forces to devise a groundbreaking solution tailored for outsourced call centers. This innovation harnesses the power of artificial intelligence to transform the note-taking process. By actively listening to conversations, this AI technology can transcribe and analyze spoken language while also gauging sentiment. The result? Precise and valuable notes generated mere seconds after the phone call concludes. Here's a quick rundown of what makes this development so exciting: ▶️It's available today: No long wait on this technology. It is ready today! ▶️ It's easy to deploy: It's designed for effortless integration. ▶️ It provides real benefits to enterprises: It offers tangible benefits to any call center, saving both time and money, while also improving customer experience. Don't miss out on this new AI technology. Vinix and 2600Hz's real-time call transcription and note-taking solution is set to revolutionize how we handle customer calls. Click here to see Diaz's full presentation. Marketing Updates It wouldn’t be a 2600Hz newsletter without some media and press updates. Here are a few highlights from Q3: The clock is ticking! Kazoocon will take place October 23rd-25th at the Palms in Las Vegas. This conference is all about pushing boundaries, having a blast, and creating lifelong connections. Secure your tickets today! A recent press release highlighted our impressive lineup of sponsors for Kazoocon 2023. We are proud sponsors of Cavell Summit | North America! Has cloud communication innovation plateaued? Patrick Sullivan, 2600Hz's Co-CEO, affirmed that the innovation cycle is accelerating. Read more about his response here. Sullivan writes a LinkedIn Article on the ups and downs of kiteboarding and startups. It's been a decade of knowledge, innovation, and connections. Take a trip down memory lane to understand the evolution of Kazoocon and what to expect at Kazoocon 2023! Stay tuned for more announcements and solutions coming soon. Remember to follow us on LinkedIn and Facebook.

Hi @Byron Knott, thanks for joining us!

Here's my obligatory post that I'm required to make.

Today I learned that when installing the USB Dongle + W56H Handset. Even though you register the Handset with the Dongle on the phone and it shows "connected" You need to make 2 changes for the Handset to ring on incoming calls + Give access to outgoing calls. This is based on only 1 account for the phone. (Yealinks can do up to 16 accounts sometimes) You can do this thru the Web Interface (see picture) OR thru Custom Configs - See code below. .CFG file reachable via http:// by the telephone. #!version:1.0.0.1 ### This file is the exported MAC-all.cfg. ### For security, the following parameters with password haven't been display in this file. ###account.1.password = handset.2.dial_out_default_line = 1 handset.2.dial_out_lines = 1 handset.2.incoming_lines = 1 p.s.

Hello community, we have another TWIL installment for you here in the form of a specific softphone setup. Zoiper is a popular softphone with a large user base that many in the Kazooniverse have used with great success on the platform. Those familiar with our hosted platform also know that registering devices of all types to specific zones is a practice that can be helpful for testing or optimising different geographic factors. Here we have a brief guide on how to set your Zoiper softphone up on a specific zone as your needs dictate! In Zoiper, click on the 'gear' button next to the account you are using to open up the settings menu. See below: Once in the settings menu, click on accounts and select the account you wish to modify. Enable “use outbound proxy” and enter the zone you wish the app to register over, as seen below: On zswitch, our hosted platform, these zones are: us-east.p.zswitch.net us-central.p.zswitch.net us-west.p.zswitch.net And voila, your Zoiper softphone will now register specifically over one of those geographic zones!

In my opinion, 2600Hz has all the rights to do what every they want with their project. Still, it will be appreciated to be more transparent about this project. Last year (2022), they said that they estimate the V5 will be released at the beginning of 2023. a long time passed until then, so we can get some hints about their attention to the project after all the git repo was not updated for a long time. And yet, of course, I greatly respect 2600Hz for their great project. It's not obvious.

Hello community, we're back with another installment of insightful TWIL knowledge, thanks again to our intrepid support team! This week we get a little deeper than we have so far: we're rolling up our sleeves and playing with APIs in this one, so please be sure you're familiar and comfortable with basic API usage concepts before diving into this one. As a reminder, the Kazoo Academy bootcamp course covers the basics of APIs for Kazoo and some basic concepts in this area (including using Postman), in particular Level 6: Basic APIs, so it might be worth a visit if you need a refresher or an intro into the world of APIs. If you've ever wondered about other possible use cases for the BLF functionality of modern office phones, and you happen to use our wonderful Call Center application, good news! You can set a BLF key to see if a user is Logged out a Queue, Away and Ready. In order to do this, you will need to configure a ‘Presence_ID’ in the Qubicle settings for the user via the API, also the user will need to be a member of a queue in call center. Using Postman you can pull up the users API by using the following path: http://{SERVER}:8000/v1/accounts/{ACCOUNT_ID}/users/{RECIPIENT_ID} Once the API is pulled up, scroll down to the Qubicle section and add: "presence_id": "Value", Value can be anything, but has to be unique to the user. See the below example: Once the Queue Presence ID is added to the user, you can use Advanced Provisioner to add the Queue BLF key by using the Presence ID: The BLF states correspond to the following recipient states: (Green)IDLE: logged out (Flashing Red)RINGING: logged in, but away (Red)ON-A-CALL: logged in, ready And there you have it: a clever use of BLF for a quick visual reference of queue status!

@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

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 😅)

@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 :)

@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

@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!!

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.

Hi everyone I have been diving for some years into Erlang and loved it! Now I am going to maybe have the chance to work with kazoo and ERLANG! I am an independent spanish software engineer with lots of software experiences both in Spain and Netherlands. However, I am new to all telecom concepts and protocols but I will try to grasp it all asap . Looking forward to dive deep into kazoo

You should check the logs tail /var/log/kamailio/kamailio.log Most likely you have regular kamailio started which prevent kazoo-kamailio to start properly. You can try to disable it: systemctl stop kamailio systemctl disable kamailio

Please anyone? Attached screenshot for better understanding.

@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

Dear Community, I am trying to install the Kazoo following the official guide. Everything goes well untill I reach the Kamailio Setup. The Kazoo-kamailio gets installed successfully but shows error when running the status command. Please see below the error and let me know what I am doing wrong? ERROR: connect_unix_sock: connect(/var/run/kamailio//kamailio_ctl): No such file or directory [2]

@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

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

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

1> UTC = calendar:datetime_to_gregorian_seconds({{2023,8,31}, {2,43,00}}). 63860668980 2> Mel = kz_time:adjust_utc_timestamp(UTC, <<"Australia/Melbourne">>). 63860704980 3> calendar:gregorian_seconds_to_datetime(Mel). {{2023,8,31},{12,43,0}} It appears KAZOO at least knows what time it is in Melbourne. KAZOO typically gives the API response in UTC seconds so I would investigate the UI conversion.

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

Hello Baze, Could you please elaborate with some degree of details about the X-CID (for general learning purpose for me)? I seen this https://github.com/sipcapture/homer/issues/601 and apply Sergey Safarov's X-CID on Kazoo 4.3. Should I add this correlation script "somewhere"? Thanks, Victor