With latest V13.1, MSS can support “SIP over TLS” now. In some enterprise communication systems, they often requre that SIP/Call signals or messages must be crypted to protect users information. Now it is very easy to do that with this new version.
Please refer to our online document for more details about this feature:
http://www.myvoipapp.com/docs/mss_services/sip-over-tls/index.html
The latest LTS is upgraded from V6.6 to V12 which has been tested and deployed around world by our customers.
V12 has much more features than previous V6.6.x and stable enough to be a new LTS version. Of course, we provide at least one-year supporting service for this new version.
Previous LTS version (V6.6.x) will be kept in supporting list until end of this year (2013).
At the same time, stable version is upgraded to V13. New features will be merged into this version and V12 will not include any new feature or service.
As we know, we can define and use our own IVR-XML file to trigger IVR service in local miniSIPServer. Now we migrate this feature into cloud-mss, that means we can do that in cloud communication in the same way.
In local-MSS, we can save IVR-XML file into local directory. In cloud-mss, something is different. For safety protection, we require customers to send IVR-XML files to our support team (support(a)myvoipapp.com), our guys will upload your own IVR-XML file to your virtual server. Then, once you sign into cloud-mss, please click menu ‘Resource / IVR-XML files’ to take a look.
If your own IVR-XML file has been uploaded into your virtual server, you can configure how to trigger IVR service. In MSS, we can trigger IVR services according to called numbers of calls. It is very easy to configure that, please click menu ‘Services / IVR services’ to take a look.
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!
We are pleasure to announce that local-MSS V11.2 is released and cloud-MSS is upgraded at the same time.
The most important is that all these versions have almost same user experience! As we know, local-MSS has quite different UI with its own web UI and cloud-MSS. Some customers are often confused when they migrate local-MSS to cloud-MSS since they have quite different UI. From now, they have almost same UI and same operations. Please take a look at following figures:
They are almost same, right? Of course, some details are different. We have tried to make them as same as possible to provide unified user experience. Hope you can enjoy it. Take a try please! It is interesting.
At the begining of this year, we upgrade our miniSipPhone to V2 and release it today!
We add some features into MSP V2. For example, some customers are always confused with one-way audio problem. In MSP V2, we configure default STUN process and it can detect NAT automatically. Customers don’t need to configure STUN again.
The new version is as simple as enough, we believe you will find it is so easy to use and hope you can enjoy it!
If you are interesting in it, please visit our website and download it to take a try:
http://www.myvoipapp.com/download/
We are very exciting to release miniSipServer new version 11! This is a great version and can support ‘Gtalk to SIP’ feature now.
What that means? It means you can connect your VoIP network with Gtalk network now. Gtalk users can call to your extensions directly, use your VoIP services, and so on. We bring Gtalk into your enterprise communication system. Funny!
Please refer to our online document for more details:
Some customers will find that their external lines configuration were gone when they sign into their cloud-mss accounts.
What happened to their accounts?
The root reason is that these customers maybe configure wrong external lines information, such as invalid password, then cloud-mss fails to register these external lines to VoIP carriers. cloud-mss will try to register them for lots of times. In this scenario, peer VoIP carriers could treat cloud-mss as a spammer or an attacker, and they will block or filter cloud-mss messages, that could effect other cloud-mss customers.
To avoid that, if cloud-mss always fail to register an external line for lots of times, it will report this external line to background administrator system, and this external line will be deleted automatically.
That’s why you cannot find your external line information. So please double check your information or check with your VoIP providers, then try to configure them again.
Yesterday we got and installed latest Xubuntu/Kubuntu/Ubuntu 12.10, then we installed latest miniSipServer V10.5 on these platforms.
The result is perfect! It is no problem to run MSS without any modification.
In another way, we would like to suggest Xubuntu and Kubuntu. According to our test result, Ubuntu system is very slow, however Xubuntu and Kubuntu are perfect.
As we know, most SIP devices use SIP over UDP by default, however, some SIP servers or communication servers only support SIP over TCP. We have to say that’s really strange. Our customers need work with such devices and we upgrade MSS to V10.5 to support SIP over TCP to fit this requirement.
It is very easy to configure MSS to support this feature. If you are interesting in it, please refer to following document for more details about it:
http://www.myvoipapp.com/docs/mss_services/sip-over-tcp/index.html