Ubuntu 20.04 is the latest LTS (Long Term Support) version, so it is very important for miniSIPServer to support this platform.
Unfortunately, Ubuntu 20.04 has cut Qt4 and all its libraries, so we have to upgrade miniSIPServer to V37 (build 20200424) with Qt5. Now it is perfect to run miniSIPServer on Ubuntu 20.04. Please refer to following figure.
miniSIPServer on Ubuntu 20.04
By the way, miniSIPServer for Windows will stay with Qt4 since we have to support several old Windows systems, such as XP and 7, and so on. In the future, as planed, V38 will say goodbye to Qt4 finally on all platforms.
In normal, cloud miniSIPServer almost has the same services with local miniSIPServer. But for some limitations, there are some different features between them. For example, voice mail service is different.
With local miniSIPServer, each local user or extension can prompt their own audio in voice mail procedure. But with cloud miniSIPServer, each local user can only prompt the unified audio associated with their virtual PBX server. Of course, the default unified audio can be replaced with customer’s own audio file.
Now cloud miniSIPServer is upgraded. In a virtual server, each local user can has its own audio file now. Please refer to following figure. You can see a new item “Personalized voice ID” which can be different for different user.
Personalized audio configuration
Of course, the audio file cannot be uploaded to virtual server by customers themselves. If you want to upload audio files, please send them to our support team, we will upload them to your virtual server manually.
Once the audio files are uploaded, you can manage them by yourself. Please refer to following figure.
Audio files management
In another way, you need follow some rules to create your own audio files, such as the file format and the audio codec, and so on. Please refer to online document for more details.
Deepin is a very popular Linux distributor system in China market. It is very beautiful and easy to use. More and more software have been migrated to this system in China. As we know it is based on Debian system, we think it should be no problem to run miniSIPServer on it directly.
And it is true! Follow the online document, we can install and run miniSIPServer as same as what we do in Debian system.
miniSIPServer in Deepin market
Yes, this system is very beautiful. After install miniSIPServer, you can find it in its software market.
In the end of next month (2020-01-31), we will clear some zombie virtual servers from our cloud system.
If the virtual server has following features, we will define it to be a zombie node and will be cleared in this action.
(1) The virtual server has not be signed in or activated since 2 years ago. If you didn’t sign into your account or virtual server after 2017-01-01, please sign into your account at less one time to avoid that.
(2) And there isn’t any SIP clients register to the virtual server, or there isn’t any SIP calls after 2017-01-01.
Zombie virtual servers waste our resources and are not affair to other customers, so please pay attention to this action and thanks for understanding.
2020-02-13 updated: This task is finished now. In future, we will keep clearing zombie virtual servers without notification. If your virtual server is not signed in or activated in recent 1 year, please pay attention to this.
In miniSIPServer, we can use IVR-XML script to enable our own services, such as automatic-attendant. With previous IVR-XML set, ‘callto’ action will invoke a call to destination and finish the whole IVR process.
But if we want to monitor some events in the call flow, such as we want to check ‘busy’ event and change the IVR flow to a new action, what should we do?
Now V37 is released and a key feature is updated in IVR-XML. We can use ‘monitor-events’ in ‘callto’ action to monitor some events and change the call flow if they are caused.
For example, the ‘callto’ action can be configured as below.
Above zip file is an example of new ‘callto’ action. You can save and unzip it into ‘xml’ sub-directory where miniSIPServer is installed and configure a new record to test it.
We upgraded cloud miniSIPServer system for some key features. The most important feature is “SIP over TLS”.
By default, cloud system opens TCP port 6060 to accept “SIP over TLS” messages. It is used to encrypt SIP messages. This feature is available for all virtual servers without any additional fee or configurations.
Now, SIP phones can connect to cloud miniSIPServer nodes with “SIP over TLS”, but “external line” and “SIP trunk” still can only use “SIP over UDP” to work with voip providers.
This feature can only encrypt SIP messages. If you want to encrypt media streams, such as audio stream and video stream, you need enable SRTP in your SIP phones. By default, media streams are bypass and processed by SIP phones themselves, cloud miniSIPServer will not process these media streams.
Please visit online document “SIP over TLS” for more details.
Debian 10 (Buster) is released. It is a stable and important version and can be deployed in business environment, so we must pay enough attention to this version.
We make some test with miniSIPServer on Debian 10. Now we are proud to announce that it is perfect to run miniSIPServer on the latest Debian system. Please refer to following figure.
miniSIPServer on Debian 10
You can update Debian source list, then download and install miniSIPServer. No more action!
Our data center has detected an issue affecting the physical host on which our cloud system resides.
During this emergency maintenance:
Your virtual server may not be accessible.
No action is required from your end at this time.
We don’t have an ETA on when your virtual server will be brought back to its original state.
Once data center administrators have completed the investigation, we will update this blog with how we plan to proceed from here.
Your patience and understanding is greatly appreciated.
[Tue Apr 9 05:05:15 UTC 2019] updated: Everything is OK now and the service was broken for one hour this time. We will keep watching. If your SIP phones are out of services, please reboot them to take a try. If you still have problem, please update us. Thanks.
Some customers report a crash problem to us. All of them deploy “SIP over TLS” in their VoIP networks. We have upgraded miniSIPServer to latest V35 (build 20190313) with following key modifications.
(1) In the latest miniSIPServer, SSL library has been upgraded to the latest version.
(2) Only TLSv1.2 method is kept, that means SSLv2, SSLv3, TLSv1 and TLSv1.1 are cut. When we did research on customers’ problems, we found some bad guys were trying to use the bug of SSLv3 to hack into MSS. We have to move all these methods out to defend that. In future, we will add other methods, such as TLSv1.3. At this time, we need confirm SIP phones can support TLSv1.2 too if we want to deploy SIP over TLS.
In another way, we refine “SIP over TLS” document to provide a simple demo on how to create certificate files.
