All products of myvoipapp.com
Main feature of this version is “customized DNS”. It enables miniSIPServer to query DNS result with own asynchronous interfaces and independent DNS servers. That means MSS will not be blocked if there are exceptions in DNS systems.
Please refer to document for more details about this feature:
V21 is released today to support a new service: one number, multi-devices.
This service can enable MSS to accept several SIP phones with same local user’s number and authorization. And for incoming calls, all these phones will be ringing at the same time.
“One number” service looks like “ring group” feature. The difference is that “one number” service permits several SIP phones to share same local user profile, but “ring group” service requires SIP phones configured with different user profiles.
Please refer to following document for more details about this feature:
http://www.myvoipapp.com/docs/mss_services/one-number/index.html
By the way, Cloud-MSS has been upgraded to support this feature too.
Hope you can enjoy it!
miniSIPServer.com is now HTTPS enabled. That means all your communication between your browser and our website will be encrypted.
Now you can visit cloud-MSS site with following linker:
Great! Debian 8 is released. We install it in lab and make some test with miniSIPServer V20.
It is quite easy to install and run miniSIPServer on Debian 8. Please refer to attached figure:
It is glad to hear that Ubuntu 15.04 is released today. We download the latest 64bit version and install it in virtualbox to test our new miniSIPServer V20 version.
We are very glad that it is no problem to run miniSIPServer V20 on this Ubuntu version. So you can enjoy it yourself if you want to try latest Ubuntu 15.04.
Of course, since 15.04 is not LTS version and is not recommanded to most customers, we suggest you to stay with LTS Ubuntu, such as 12.04 or 14.04.
Yesterday we released the latest miniSIPServer, V20! This version is focus on following items:
(1) Call park service refined.
In previous version, MSS can accept “unattended transfer” call to park the user’s previous call. This method works in most scenarios, but some SIP devices cannot do that because they don’t have “transfer” button to invoke “unattended transfer” call. For some customers, they are confused on how to invoke such call.
So we decide to refine this service. V20 can accept a new call to park previous call. That means customers can invoke a new call directly to “*70*1” to park their previous calls. That could be easy to understand and do such operation.
(2) openAPI refined.
In V20, we unified openAPI interfaces and inner web management systems. That means they are using the same inner interfaces now. In the openAPI document, we just list several interfaces, in fact openAPI has almost all interfaces now and can work as same as web management system. Customers can design their own web system based on openAPI interfaces.
Of course, we will keep refining openAPI document to make it clear to customers.
Yesterday our data center has a DNS problem. In fact, it seems its DNS system was crashed. It made our servers failed to register all external lines. Then cloud system detected that all external lines were configured with wrong configurations. To avoid sending spam messages to peer sides or peer voip providers, our system will cut all “wrong” configurations automatically.
That’s too BAD news!
We promise this problem will not happen again. All our servers have been upgraded to enable several DNS systems including Google DNS.
We are very sorry for this problem. If your external lines are off, please configure them back manually.
Thank you for your patience and continued support.
V19 is updated to support some new features in external line. We add a new item “maximum simultaneous outgoing call” in “outgoing call” tab.
This new item can limit how many concurrent calls can be processed by the external line. It it is configured to be zero, that mean the line cannot make any outgoing call.
That also means previous item “only permit incoming call” is unnecessary, so we cut this item together.
V19 is released today to provide some features and optimization:
A new embedded HTTP server is designed and implemented in V19 to replace previous server to provide higher performace and better structure.
It is a tradtional PBX service. Please refer to the service document for more details.
V19 is recommended for all new VoIP deployment. Upgrading from all other versions of miniSIPServer is optional.
This is a new bug reported in Linux platform. It is caused by invoking ‘gethostbyname’ function. We check our codes and find it is very lucky that we didn’t use this function.
So it is no problem to keep your MSS running in Linux platform. Of course, it is better to upgrade your Linux system since other applications might have this bug.