IP address authorization

IP address authorization

This feature was merged to the latest V25 (build 20160126).

Some special SIP devices, for example embeded devices in automaticated system, don’t have full SIP capabilities, they can make or receive simple SIP calls without account and password authorization. They even cannot send REGISTER messages to MSS to update their own status.

Yep, we can configure them as “SIP trunk” in MSS. but it will lost several key features, such as ringing-group. In some scenarios, customers hope to ring all such devices together, so we have to treat them as “local users”.

To fit these requirements, we add “IP address authorization” in local user’s configuration. That means MSS will not require SIP phones/devices to register them firstly, and will not check their account and password if their messages are from specific or configured IP addresses. Please refer to below figure for more details.

IP address authorization
IP address authorization

By the way, we update openAPI document according to the latest V25. If you are interesting in it, please refer to openAPI document.

SIP trunk between MSSes

SIP trunk between MSSes

1. Description

Some customers have several office branches and hope to establish VoIP connections between them. There are several methods to do that. Here we give an example to describe how to establish voip connections between two MSSes with SIP trunk feature.

2. Network topology

The network topology is simple. There are two office branches. Please refer to below figure.

Demo network
Demo network

Before we setup voip network, it is better to assign extension numbers. Different office numbers will effect how to configure call routing in both MSSes. In above figure, we can see the extensions in office 1 are 1xx, and extension numbers in office 2 are 2xx.

Both MSSes are configured with public IP address. If your MSS is behind NAT or router and you want to provide connection for outsides users, please refer to another document firstly.

Now we give detail configurations for it.

3. Configuration

In below configurations, items should be kept their default values if we don’t configure them obviously.

3.1 MSS1

Please click menu “data – SIP trunk”, then add a record:

SIP trunk ID = 1
Description = to MSS2
Server address = 10.23.x.x

Please click menu “dial plan – analyzed called number” , then add a record for routing 2xx to such SIP trunk.

called number prefix = 2
route type = SIP trunk
SIP trunk ID = 1

3.2 MSS2

It is almost same with MSS1.

Please click menu “data – SIP trunk” to add a record.

SIP trunk ID = 1
Description = to MSS1
Server address = 41.32.x.x

Please click menu “dial plan – analyzed called number” for routing calls to above SIP trunk.

called number prefix = 1
route type = SIP trunk
SIP trunk ID = 1
Happy New Year!

Happy New Year!

Happy new year! 2016 is coming!

We upgrade the latest LTS version to V24 and the latest stable version to V25. Hope it can be great in the new year!

Enjoy your holiday!

And enjoy our products when you back to work! 🙂

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.

miniSIPServer on Ubuntu 15.10

miniSIPServer on Ubuntu 15.10

It is no problem to run miniSIPServer on latest Ubuntu 15.10 system. Please refer to attached figure.

miniSIPServer on Ubuntu 15.10
miniSIPServer on Ubuntu 15.10

As you know, it is better to stay with previous Ubuntu LTS versions, such as 12.04 and 14.04.

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!