MYVOIPAPP products blog – Page 4 – Software based SIP-PBX

Customized resource files

2021/01/09 Gilson

Sometimes we need to use customized resource files, such as audio files, special IVR flows, certificate files and so on. With previous versions, all these files are stored in miniSIPServer install directory or its sub directories.

It could be a management problem when trying to uninstall or upgrade miniSIPServer. We have to be very careful to backup our own resource files.

V38 (build 20210108) is released to refine this. Customized resource files are separated to be stored in independent directories which are in application data directory.

For example, customized audio files will be stored in ‘custAnn’ directory. Once miniSIPServer is uninstalled or upgraded, these audio files will be kept without any affection.

Please refer to online document for more details.

Configuration data

2020/11/30 Gilson

Before V38, miniSIPServer stores its configuration data in the install directory. In some scenarios, it could be a problem. For example, if miniSIPServer is installed in disk C on Windows system, it is possible that Windows will reject miniSIPServer to write data into disk C unless the user has the right to do that.

In Linux system, it could have the same problem. By default, miniSIPServer is installed in ‘/opt/sipserver’ directory. If root user started miniSIPServer and created local configuration files in such directory, other users could have no right to read and write the files and fail to start miniSIPServer.

So V38 will store configuration data in user’s own directory. In windows, it is the user’s application data directory. In Linux, it is the user’s HOME directory.

Please refer to online document for more details about this modification.

In another way, when miniSIPServer starts up, it will prompt where its data is stored no matter it is on Windows or Linux.

miniSIPServer on Deepin V20

2020/09/19 Gilson

Perfect! So beautiful!

miniSIPServer is running on Deepin V20 system.

A small thing: UPnP

2020/05/02 Gilson

When deploying a VoIP network, we often have one-way or no-way audio problems. It is caused by private network, for example, some SIP phones or miniSIPServer are behind routers and other SIP devices are in another different network which could be a private network or public network.

To resolve such problem, we often suggest to configure “forwarding ports” in routers manually. If you are familiar with routers, it is easy to do that.

But someone might not know how to do that, or someone might make mistake in router’s configuration. So we add a new feature in miniSIPServer to help that.

It is UPnP (Universal Plug and Play). UPnP can help miniSIPServer to map necessary ports automatically.

Firstly, you need confirm that your router can support UPnP and it has been enabled.

Then, you can click menu “Data – System” in miniSIPServer and enable the item “Enable UPnP to ask router to map ports”. Please refer to following figure.

By default, miniSIPServer will map SIP (over UDP) port and audio ports for relaying audio streams.

In another way, there is a limitation in routers. Most routers limit the number of UPnP ports, for example less than 30 ports. So if you are deploying a miniSIPServer for 50 clients or more, you will still have to configure “forwarding ports” manually.

miniSIPServer on Ubuntu 20.04

2020/04/24 Gilson

Ubuntu 20.04 is the latest LTS (Long Term Support) version, so it is very important for miniSIPServer to support this platform.

Unfortunately, Ubuntu 20.04 has cut Qt4 and all its libraries, so we have to upgrade miniSIPServer to V37 (build 20200424) with Qt5. Now it is perfect to run miniSIPServer on Ubuntu 20.04. Please refer to following figure.

By the way, miniSIPServer for Windows will stay with Qt4 since we have to support several old Windows systems, such as XP and 7, and so on. In the future, as planed, V38 will say goodbye to Qt4 finally on all platforms.

Personalized voice in VM service

2020/02/19 Gilson

In normal, cloud miniSIPServer almost has the same services with local miniSIPServer. But for some limitations, there are some different features between them. For example, voice mail service is different.

With local miniSIPServer, each local user or extension can prompt their own audio in voice mail procedure. But with cloud miniSIPServer, each local user can only prompt the unified audio associated with their virtual PBX server. Of course, the default unified audio can be replaced with customer’s own audio file.

Now cloud miniSIPServer is upgraded. In a virtual server, each local user can has its own audio file now. Please refer to following figure. You can see a new item “Personalized voice ID” which can be different for different user.

Audio ID configuration in local user's configuration — Personalized audio configuration

Of course, the audio file cannot be uploaded to virtual server by customers themselves. If you want to upload audio files, please send them to our support team, we will upload them to your virtual server manually.

Once the audio files are uploaded, you can manage them by yourself. Please refer to following figure.

Audio files and ID management — Audio files management

In another way, you need follow some rules to create your own audio files, such as the file format and the audio codec, and so on. Please refer to online document for more details.

miniSIPServer on Deepin 15.11

2020/01/13 Gilson

Deepin is a very popular Linux distributor system in China market. It is very beautiful and easy to use. More and more software have been migrated to this system in China. As we know it is based on Debian system, we think it should be no problem to run miniSIPServer on it directly.

And it is true! Follow the online document, we can install and run miniSIPServer as same as what we do in Debian system.

Yes, this system is very beautiful. After install miniSIPServer, you can find it in its software market.

And it is very easy to run miniSIPServer.

Please enjoy it!