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.
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:
Yesterday we upgraded Cloud-miniSipServer to support hunt-group feature.
HG feature has been supported in local minisipserver for a long time. Lots of small companies use this feature to service their customers. The HG service in cloud-minisipserver is almost same with local-minisipserver, such as same service log, same configurations.
The difference is GUI display. Please refer to following figures.
One is for cloud-minisipserver.
another is for local-minisipserver:
For more details of hunt-group service, please refer to our online document:
We upgrade cloud-miniSipServer to support “Dial plan” features. Customers can use these features to control the calls very flexibly. When you sign in your account, you will get “Dial plan” features in command list at the left side .
And the trial duration of each call for trial accounts has been upgraded from 30 seconds to 60 seconds according to most customers’ requirements.