DanH

Hello @DonnieSims and welcome! Very glad to have you and your wealth of experience here amongst us. Looking forward to your journey with the open source dabbling, and def don't hesitate to just ask questions around here or Erik in sales if it gets to that point, we're lucky to have a very knowledgeable and helpful community and team!

@Chris Labonne it is of great gratification to know what I do here might constitute any steps towards a better experience for the community, thank you for that, genuinely affirming! Thank you as well for this note on your proposed approach to the TWIL post. Speaking of comfort here as well, I would offer that the nature of the forums is inherently an interactive discourse format, and so to simply "get the ball rolling" with your thoughts and notes as they stand now can be enough of a jumping off point to add to later or get others to start chiming in and such. I mention this because I know it can seem as though the TWIL posts tend to be these complete article-like productions, and that is mostly circumstantial as I have the luxury of having an entire team of wizardly technical support agents meeting and pontificating and codifying knowledge into concise post materials for me, but there is no requirement or expectation that posts from the community in the TWIL forum follow that same format. BTW shout out to @Eric Faulkner and the support team for TWIL materials! I see that you've posted in TWIL and just wanted to reiterate that that's perfect, thank you for your contribution!

Hi @Chris Labonne and sorry about the systemic shift we did catching you in the crossfire like that, unfortunately the platform can be a little limiting at times; hopefully nothing else went awry and you're still able to navigate normally now, but let me know somehow if not. However, I wanted to thank you for taking the time to write a thorough and impressive intro! A hidden benefit of accidental retroactivity I would say maybe?! It's great to know we have folks like yourself amongst us, such a depth of experience and skill is invaluable in our community. As far as publishing the Cisco integration, we actually started a forum for the express purpose of people sharing interesting and useful knowledge of that nature, called the TWIL Knowledge Base (found here: https://forums.2600hz.com/forums/forum/118-twil-knowledge-base/ ), and while I am working with the team to publish things we discover internally, it's designed for all to participate! So if you felt so inclined, I would encourage you to consider posting that there, as such is the kind of communal collaboration and knowledge exchange we are so excited to foster here. Thanks again for posting this intro!

This week the team has explored the technically profound subject of packet captures on softphone devices, and presented a guide on how to set that up with Wireshark. For those unfamiliar, Wireshark is an industry-leading general purpose packet capture system with wide ranging applications, and is particularly beloved in the VoIP world for its ability to help diagnose many call-related issues. It is a powerful platform with a bit of a learning curve, however, so one may want to familiarize themselves with this tool before attempting the below--if you're a Wireshark pro already, any tips or tricks you want to share here are very welcome! Not all softphones have features in place for capturing packets. This method will walk you through capturing packet traffic for softphones such as Bria, Zoiper, etc. Once Wireshark starts, select Capture, then Options. A new wireshark page will now populate for Capture Option. Select Manage Interfaces. From here, you will see a page showing all the different networking devices (ethernet card, wireless card, etc.) that are available on your computer. Select the device you want to capture packets from and deselect the rest, then hit ok. This will take you back to the Capture Options page. As you can see below, I have chosen to display only my Ethernet connection. Now press Start, and Wireshark will start capturing the incoming and outgoing packets from the device you chose above. While Wireshark is running, run Bria and try to recreate the issue you are trying to resolve. To save the resulting capture, click File > Save. Leave the file type as default and save the file.

Hello @xinufje, welcome and glad to have you here with us!

Ciao @Maxv78, ci mancherebbe! È un piacere avere te e le tue domande e prospettive qui, mi piace sapere che KAZOO viene esplorato qui in Italia in questo modo, è davvero un desiderio che ho! Looking forward to the questions and learning more about your exploration, and honestly there is no such thing as too many questions!

This week the team has come up with some helpful information about working with the CSV Onboarding application great mechanism to expedite the creation of new accounts or higher volume updates. Feel free to discuss how you use the CSV Onboarding app and any tips or tricks you might have for it! When using CSV Onboarding to add a device, you will need to specify the brand and model of the device, as well as the family. The family of a supported device can be found using your browser’s Dev Tools. First, navigate to the Devices tab of Smart PBX. Open your Dev Tools by right clicking the page and choosing Inspect. After this in the upper left choose Network, as seen here: Now, select Add Device and choose SIP Phone, but do not select a brand. First, select the second response for phones, the Get request. Now select Response in the upper right of your Dev Tools. From here you will be able to find the families of your devices based on your brand. For this example, I want to find the family corresponding with the Yealink T46U. Click the arrow next to Data, then the brand, and then families. This will show the names of each family within the brand. If you are uncertain as to whether your device is in one of the families, select the arrow next to that family. By selecting the arrow for t4x, I can see each of the models under that family. And there you have it; please definitely also post your questions on this process, and thanks for reading!

Hello Kazooists, this edition is another bit of esoterica for the Yealink folks, but it's an interesting and powerful function when utilized properly! This kind of diagnostic data can help with support and troubleshooting efforts across the board, and is fairly easy to set up. What follows are instructions for setting up packet captures (PCAPs) from a Yealink device UI. To access the web UI for your Yealink phone you will need to enter the IP address for the Yealink device into a web browser. The IP address can be found by pressing the OK button on the phone. The default login credentials for Yealink are admin/2600. Once logged into the Yealink web UI select Settings > Configuration. It should look something like this: Set the PCAP Type to Enhanced and press Start, as seen here: You can now run tests for various issues where packet degradation or loss is suspected. Once your tests are completed click Stop. The new file will appear in your downloads. The created PCAP file can then be examined in software such as Wireshark. These kinds of resources from a primary source like an affected device can be very valuable to a support diagnostic process and can even immediately expose the cause for some issues. If anyone's already been using this method to acquire PCAPs, comments on your experience would be most welcome here!

Hi @dit101 and thanks for joining us, looks like you're already in pretty deep! I hope we all can be a mutual resource for your continued endeavors.

Hi @elkato and welcome! Great to have you and your experience amongst us, looking forward to your questions and your insights along your journey!

Welcome @rdnn and that's amazing! I'm sure many folks are going to be interested in your project here, so please do participate and share as much as you're happy with!

Hello all, back from another pause we've got a nice niche item for our TWIL this week. We have a guide the support team was able to generate around this for ensuring you see the correct caller ID when receiving a forwarded call on a Yealink device. Chime in with your Yealink tips if ya got em'! Yealink devices need to be configured to retain the caller ID of a forwarded call. If you are not seeing the original caller ID when forwarding to Yealink devices, follow these steps on the phone not receiving the correct ID: Navigate to the phone’s web UI by typing its IP address into a browser. From there, select the Advanced tab under Account. See below: At the top of the Advanced page choose the account your phone is under: After this locate the Caller ID Source and update it to Preference. By default this value is FROM: You should now see the correct caller ID when forwarding to a Yealink device.