The Digium Phone Module for Asterisk or DPMA for short is an Asterisk software module that provides a secure communications channel between D-Series phones and Asterisk. This secure channel is used to ensure an easy installation process and offers direct integration with many Asterisk capabilities, including presence, voicemail, call parking, and call recording. The DPMA is utilized in stand-alone Asterisk systems, in FreePBX systems, and Switchvox systems.
The D-Series telephones possess an embedded root certificate used to encrypt communications between the D-phone and the DPMA. This certificate was created during the initial development of the D-Series phones in 2011 and had a ten-year lifetime.
As a result, the certificate will expire and become invalid on Friday, May 28, 2021, at 4:45 pm Eastern Daylight Time.
The effect of this certificate expiring is that after May 28, any D-phones already in use will experience application loading errors, which affects voicemail, status, parking, and queues. Any new D-phones that are started anew or rebooted will be unable to connect to and provision. The D-phone will attempt to “contact proxy,” and it will never succeed.
However, we do know how to fix it.
Sangoma has produced new versions of DPMA, Proxy, D-Series telephone firmware, and Switchvox mobile softphone that remediate the problem. Administrators (except Switchvox Cloud and PBXact UCC) MUST take action before the expiration date. For Switchvox users on 7.x, the new firmware is included in Switchvox version 7.6.2. For Switchvox users on 6.x or 5.x, the latest releases are 6.8 and 5.12, respectively.
Steps to take…
Sangoma has developed quick to implement and future-proof solutions. Please visit the resource page for complete information on how to resolve the issue.
Since the certification expires on May 28, 2021, this is a time-sensitive issue that requires immediate action to be taken. Please visit the resource page for complete information on how to resolve this issue.
Emotet botnet harvested 4.3 million email addresses. Now the FBI is using Have I Been Pwned to alert the victims
Two weeks ago, I wrote a blog about video calling and starting calls with video. I got a few questions and comments about that, some saying “The future is all video all the time!” while some agreed with my point of view of “That’s not going to happen all the time”. So, let me write a little more about this.
First, in that blog, I did talk about differentiation of use case. In the case of a calendared meeting, where a link can go into your calendar, many meetings we’ve all been on in the last 12 months start this way. You click on the link; you go to the video meeting. You have a nice shirt on but maybe shorts or PJs, not that I’ve done that. But these are internal meetings, or meetings with partners and even key customers, and many people forget this is NOT the entirety of communications in a business. These are simply meetings where 3 years ago, we’d calendar a “conference call”. They are important parts of your communication plan but not the only way to communicate.
People also said, “Hey I use video when I talk through my collaboration client”. Presumably these are to other employees, or to key partners. I remember “in the old days” I’d use Skype to talk to some of my partners in Europe. But you start with presence / instant message and then you move to a call. Many times the call is still voice, and sometimes it’s also video. I guess it depends on the person. But in any of these use case scenarios, you are not leading with video!
What I’m really talking about though is interaction with your customers or prospects. These are people that are going to call your business to schedule an appointment, get a service person to your house, etc. Sure, because of the internet and having web pages, over the last 25 years, there has been less voice interaction / calls with this group. But with this group, a real call control / call routing engine like exists in UC platforms is really required. There are incoming calls that need routing, there are external calls (or texts) that need scheduling. These cannot be done via scheduling a meeting on a calendar. You need a real IVR, you need contact center features, you need voice mail, you need find me / follow me. You get the picture.
To run a business and interact with external customers, a video first platform just won’t cut it.
A Unified Communication system that knows how to handle phone numbers, and texting, and all kinds of call control as is found in a “PBX” is required.
The post You’re “Always” Starting a Call with Video, Really? appeared first on Sangoma.
FBI: Russian hackers are still trying to break into networks, here's how to protect yours from attack
The Linux Foundation's demands to the University of Minnesota for its bad Linux patches security project
WebRTC is…everywhere. WebRTC (Web Real-Time Communication) is a technology that allows Web browsers to stream audio or video media, as well as to exchange useful data between browsers, mobile platforms, and IoT devices without requiring an intermediary such as a server.
The need to connect virtually and to have video conferences and communications via the web has been around for a while. In the past, you had to rely on plug-ins or an installable application on your PC – not just your web browser. This was very inconvenient as users were required to install additional, incompatible apps, and developers had to study complex stacks and protocols to make the magic happen.
Photo: Swedish Prime Minister Tage Erlander uses an Ericsson video to speak with Lennart Hyland, a popular TV show host (1969). Image via Wikipedia.
WebRTC Was Born
Many of WebRTC technology’s underpinnings were first developed by Global IP Solutions (or GIPS), a company founded around 1999 in Sweden. In 2011, GIPS was acquired by Google, and the W3C started to work on a standard for WebRTC (real-time communication). WebTRC specifies a series of APIs for real-time communications (RTC) targeted at browsers. Since 2011, Google and other major players in the web-browser market, such as Mozilla and Opera, have been actively supporting WebRTC.
Today companies trust WebRTC to offer them the leverage they need to deliver the user experience they strive for.
Examples of WebTRC
WebRTC is a set of plugin-free APIs that can be used in both desktop and mobile browsers. WebRTC does not need any native apps for audio and video communication as it allows peer-to-peer communication on the web pages. Some of the top companies like Amazon and Facebook are all leveraging this, but Google Meet (or more accurately, Hangouts) is probably one of the main reasons we have WebRTC today.
Google had their own video conferencing service, working from Gmail, but it needed a plugin. Real-time video just wasn’t there in the browser, which is where and why WebRTC started.
There are so many interesting use cases for WebRTC, but here are a few popular ones you may not have considered:
- Simple collaboration: How many times have you been invited to a meeting, and as soon as you clicked on the link, it asked you to sign up or download an app before you could join the call? It can be frustrating to open an account or download a platform to engage in a business meeting. WebRTC removes this barrier, providing a seamless, non-invasive way to connect and collaborate. Using WebRTC when communicating with colleagues, clients, and business partners is easier, simpler, and more convenient.
- Contextual applications: You can use a third party API like OAuth to pull data from services like Facebook, LinkedIn, and Google. This API type makes it possible for customers to leverage their own social graph data to augment their experience within your websites and applications. You can then couple this data with WebRTC-powered features to enable rich contextual communications. This could enable easy sharing of the person’s Twitter handle, email address, or other public profile information, along with links to their most recent tweets or Facebook posts.
- File sharing: Suppose you want to send a massive file to a colleague while working on a project. Instead of emailing the file or uploading it to a third-party cloud storage system (and waiting several minutes for the transfer to complete), you could send it directly through your web browser using WebRTC’s data channel, with very low-latency and the benefit of full encryption between the two endpoints.
- Embedded endpoints: ATMs. Vending machines. Bus stops. Retail store kiosks. All of these endpoints can be embedded with WebRTC engines. It’s an easy way to connect customers with live agents while they are on-the-go.
- Sales enablement: Websites and applications are key tools for sales enablement. Customers rarely make important purchases on impulse. Decisions are often made after speaking with a sales associate. Providing a website or application with a WebRTC audio or video contact channel is a great way to provide ongoing assistance throughout the purchasing process.
- Emergency response: In some cases, WebRTC is being used to increase public safety. SaferMobility streamlines real-time interactions with authorities by enabling video, audio, and text communications while utilizing location-based awareness. This use of the WebRTC data channel allows responding personnel to have deeper insight and better information by circumventing previously existing communication barriers when responding to emergency calls.
- Patient management: Many health clinics are now using WebRTC based solutions to reduce in-office patient visits. This can be helpful during a pandemic like what we are living right now when doctors can perform check-ups over Web browsers. This allows them to allocate more time to higher priority patients while staying safe. WebRTC is also a great way for clinic staff to communicate with patients in-between visits as all the patient needs is a web browser and a URL.
- Enhanced audience participation: Tap to Speak recently developed a solution that turns smartphones into microphones during live events. The application was designed to improve communication between audience members and presenters, as it eliminates having to pass a traditional microphone around a room.
In summary, pretty much any application that wants to share data or video between peers can use WebRTC. The reason for this massive adoption is that browser to browser communication is significantly cheaper than going through a server (up to 90% cheaper from Video Banking and the Economics of the Retail Business). Furthermore, users will no longer need to rely on dedicated hardware sets and applications to join a meeting and have a video conference call; browsers are always accessible to everyone!
Sangoma Meet a Great Example of Adopting WebTRC
Sangoma Meet was launched in early 2020 in response to the COVID-19 crisis to help everyone stay connected and get through this period. With WebTRC technology behind it, Sangoma Meet allows users to start a video call without downloading a plugin or installing an application. Unlike Zoom or GoToMeeting, where you have to install a plugin or an application, Sangoma Meet is simply using your browser to establish a connection with another peer.
The ease of use and compatibility with common browsers like Chrome, Firefox, Opera makes it a great choice for different industries to adopt in different use cases, as mentioned earlier. Features like multiple participants video conferencing, 1:1 video calls, phone dial-in, screen sharing, recording the meeting (available on V3.0 and above), waiting room (coming soon), local chat, and moderation tools are all running on the web, and users can join the meetings from their mobile devices, laptop or simply from any device which supports web browsers.
Have you tried Sangoma Meet yet? Check out this page and enjoy having a hassle-free call with your friends, family, and colleagues.