We upgrade web UI for miniSIPServer, including cloud miniSIPServer and local miniSIPServer. The new web UI is quite like GUI of local miniSIPServer. Please refer to the figure below.
We hope users who are familiar with local miniSIPServers can enjoy it and experience the cloud miniSIPServer system quickly.
Recently lots of customers reported that they didn’t receive activation emails when they signed up miniSIPServer cloud accounts. All of them are using free email systems, such as gmail, and so on.
At first we think such systems move our emails to spam boxes, but customers still cannot find them there, so we think our emails are blocked.
We completely understand that. Since lots of email are sent from our cloud system to free email systems, including activation emails, balance notification emails, and so on, some email systems detect us to be a spammer.
It confuses us and we don’t want that, so we decide that our cloud system cannot accept customers use free email addresses to sign up miniSIPServer cloud accounts. We hope our cloud system to be treated as a serious virtual VoIP system, and we hope our custmers can understand that.
Our data center updates us that maintenance is required for one or more of our servers’ physical hosts. The hosts will be rebooted, and a number of critical updates will be installed.
The maintenance schedule in UTC is as follows:
2020-08-07 03:00:00 AM UTC
Important to know:
(1) A 2-hour window is allocated, however, the actual downtime should be around 45 – 60 minutes.
(2) Your virtual server(s) will be cleanly shut down and will remain inaccessible during the maintenance window.
(3) You might reboot your SIP phones/devices to register to virtual server(s) again once the virtual server(s) is(are) back to work.
Please let us know if you have any questions or concerns. Thanks!
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.
Our data center has detected an issue affecting the physical host on which our cloud system resides.
During this emergency maintenance:
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.
V30 is released. The key feature of this version is “media gateway”.
In fact, previous version has media gateway functions too, but these functions were combined in the same core with call-control and service-control tasks. For small size or middle size business, it is no problem to do that. But for huge size business, for example, our cloud-mss system, it could effect performance if media gateway is combined with other tasks.
We decided to separate media gateway module into an independent application. In cloud system, media gateway can be run in separated device. Several call servers can share the same media gateway server.
Since local MSS and cloud MSS have the same core, we merge this function back to V30. The difference is that the media gateway is an independent inner task in local MSS application.
This feature doesn’t require any modification in configuration or GUI. By default, you should not notice this change. We believe new core can be more stabler and more flexible. Hope you can enjoy it!
Some virtual servers in cloud-MSS system have been changed, please pay attention to these items.
Each virtual SIP server will enable STUN feature. For example, if the SIP server address is “1234.s1.minisipserver.com”, its STUN server can also be the same address. That means “1234.s1.minisipserver.com” is also its STUN server address.
Now we suggest “stun.minisipserver.com” by default. It is a simple public STUN server for all virtual SIP servers. Of course, you can still configure your virtual SIP server address as your STUN server.
In voice-mail feature, we need a SMTP server to send emails with attached audio files. Each virtual SIP server can be configured with customers’ own SMTP servers. But we find it could make several problems. For example, most customers try to use Gmail SMTP server. Gmail SMTP server requires that you need enable POP/SMTP firstly, and grand other access. Most customers don’t know how to do that.
So we disable SMTP server configurations. All voice mails will be sent from our own SMTP server. Most important is that you will need check your spam box if you cannot find voice email in ‘inbox’.
Since cloud-mss is online, there are lots of customers ask us about reseller funciton. Thanks for their suggestions. We do some research on this topic and find it could be classified to two types:
(1) Some customers are professional communication providers for enterprises. They often install several cloud-mss servers for their own customers, so it is very useful if they can manage several nodes in one account.
(2) Some cutstomers provide SIP-PBX services for their local subscribers with their own domain names, so they not only want to manage several virtual sip-pbx nodes in one account, but also want to get more discount pricing.
We add ‘reseller’ function into cloud-mss system. It is free to register cloud-mss account and users can create and manage several cloud-mss nodes. Each node can be configured independantly just like common node.
If you are interesting in this topic, please take a try and feel free to contact us if you have any question or suggestion.
Please refer to our online document for more details:
We are migrating cloud-mss servers to a new data centre which can provide more bandwidth and be more stable.
The process will take one or two hours. We have to disconnect all our servers and we are very sorry to stop all customers’ services and thanks for your patient.
We will update this blog if all jobs are finished. Thank you very much.
2013-01-31 UTC 09:18 updated: now, everything is ok!
Today we upgrade cloud-MSS to new version to support offline-IM feature.
In a unified communication environment, it is very common for users to send or receive offline instant messages, specially some customers use cloud-MSS as their internal communication tool.
With this new version, cloud-MSS can support IM as following:
(1) If called party is online, Cloud-MSS will send IM to it immediately.
(2) If called party is offline, Cloud-MSS will save its offline IM. Clou-MSS can store no more than total 10 offline-IM for each local user. Each IM should be less than 200 characters.
(3) If called party is back to online again, Cloud-MSS will send its offline-IM to it automatically.
You don’t need configure anything for this feature, it is so easy to setup a UC system for your business now. Why not take a try? 🙂