Browsed by
Category: Releases

Product release messages, including LTS, stable, development versions and patches.

Refined SMTP library

Refined SMTP library

In voice mail feature, MSS need use SMTP library to send emails. Since MSS can embed Python script functions, it is easy to use Python-smtplib to send email. That’s what we done and it works well, we are satisfied with it.

But smtplib is too old ( in python 2.7) to fit some modem SMTP servers’ requirements. It also has a shortage. It is synchronous. That means it can block thread when sending a email, then its performance is poor and cannot fit our requirements in cloud system.

Something is changed, we want MSS to be better, so we develop a new SMTP library to send voice mails. This SMTP library is asynchronous and can work perfectly with most SMTP servers. And, it is written in C/C++ language.

We upgraded MSS V23 and cloud-MSS to replace python-smtplib with this new SMTP library.

Hope you can enjoy latest versions.

By the way, since MSS V23 has been released for several months and we got very better result, we think it is time to release new LTS version which is V24  and new stable version which is V25 in the end of this year or in the beginning of next year.

shared-appearance feature

shared-appearance feature

MSS V23 was released yesterday. The main feature of this version is “shared appearance”. In one number service, the SIP phones can subscribe others’s dialog status, and MSS will notify them with all kinds of busy signals: early, confirmed, terminated, and so on.

Please note that this feature requires SIP phones to have SUBSCRIBE/NOTIFY capabilities. If your phones cannot support these methods, this feature will be discard automatically.

You need configure nothing to enable this feature. So easy, right? Hope you can enjoy it!

conference call in one-number service

conference call in one-number service

We have updated V22 to support a special feature: conference call in one-number service. This feature is used in a classroom scenario:

Some students will be assigned with same number (of course, one number, remember?). Teacher will ask one of them to answer questions. During this process, other guys can pick up the call to join their discussion.

In MSS, the user who want to join call can dial “*74” to do that by default.

When developing this feature, we think about previous “virtual conference room” feature. We believe this feature is too complex to use and few people like it, so we decide to cut it from V22 and abover versions. In future, we will plan to develop a new three parties conference service.

miniSIPServer V21 released!

miniSIPServer V21 released!

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 V20 released!

miniSIPServer V20 released!

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.

 

say goodbye to Gtalk

say goodbye to Gtalk

As you know, MSS can use Gtalk as external line to bridge Gtalk and SIP networks. It is a good idea and we are happy to provide this feature for our customers.

But since Google gives up Gtalk, it seems we have no choice to discard it. We update MSS V18 today to cut Gtalk out.

Gtalk is good, but time to say good bye now. If you are still using this feature, you can keep your MSS at V16 which is LTS version and we will maintain it for at least one year.

webRTC now!

webRTC now!

webRTC is defined in HTML5 to support real-time communication. We spent several months in this technology and release the latest V18 to support it finally!

Now you can connect Chrome to miniSIPServer to work as local user. It is so interesting and hope it can help you to deploy your own VoIP network.

Please refer to following document for more details about webRTC in MSS:

http://www.myvoipapp.com/docs/mss_services/webrtc/index.html

new LTS V16 and new stable V17

new LTS V16 and new stable V17

V16 has been released for several days and response messages from our customers are very exciting, so we decide to upgrade LTS version to V16 since it can support very important feature: IPv6.

At the same time, the latest stable version is upgraded to V17. In this version, something is changed:

Event channel is provided

“Event channel” is based on websocket, and customers’ applications can establish websocket connection to get MSS inner call status. Please refer to online document:

http://www.myvoipapp.com/docs/mss_services/event_channel/index.html

MSS trunk

“MSS trunk” is our private protocol to bypass some ISP blocking. It helps some customers to deploy VoIP network at their sides. At this time, since MSS can support SIP over TLS, we think this feature could be replaced by it, so we decide to remove this feature from V17 and abover versions.

We hope new versions can fit your requirements and benefit your VOIP network. Please enjoy them and update us if you have any suggestion or question.