Browsed by
Author: Gilson

MySQL server has gone away

MySQL server has gone away

Yesterday we received a report from a Chinese customer that he has a problem with MySQL and MSS. According to his report, after running for several minutes, MSS lost connection with his MySQL database and the error is “2006, MySQL server has gone away”.

Once connect to MySQL database, MSS will try to ping MySQL every 1.5 hours. By default, the interactive timer in MySQL server is 28800 seconds (8 hours). So we guess that the default timer values have been updated in MySQL. When MSS try to ping MySQL, the connection has gone, MSS failed to connect MySQL.

So we ask customer to check MySQL values with following command in MySQL database:

show variables like '%out%';

We care the result of ‘interactive_timeout’ and  ‘wait_timeout’ values. In such customer’s environment, these values have been changed to 1200 seconds.

We are not sure these values are changed default value by MySQL itself, or changed by some operators in such environment. If you have same problem, please take a check and  change these values to be bigger than 1.5 hours. We suggest you keep the default value which is 28800 seconds.

If we update above parameters, please restart MySQL and MSS in order to use new timer value for their connections.

New LTS version and stable version

New LTS version and stable version

We are pleasure to announce that LTS version is upgraded to V6.6 and new stable version  is V8.

V6 has been deployed around world by lots of customers and has been verified to be a very good version for business deployment. It has more features and services than previous LTS version (V4) and we suggest most customers to upgrade to this new version.

V8 is the latest stable version. We will develop and deploy new features with this version. If you want more exciting services, please try this version. Of course, it is stable enough for business deployment.

We hope you can enjoy our new versions.

UDP 5060 is blocked by ISP, can I use another port?

UDP 5060 is blocked by ISP, can I use another port?

Some cloud-mss customers ask us this problem because the standard SIP port (UDP 5060) is blocked by their ISP in their countries.

So we upgrade cloud-MSS to support several UDP ports: 5060, 6060 and 8080. In the cloud management interface, you can select one of them in “Basic call / System information”. Please refer to following figure for more details:

Cloud-MSS configuration for several SIP ports

If you select a UDP port which is not standard 5060, you must change configurations in SIP phones/clients. Below figure is a demo configuration of xlite since we change the port to 8080.

Xlite configuration with UDP port 8080
MSS V6.5 updated to support “speed-dialing” feature

MSS V6.5 updated to support “speed-dialing” feature

V6.5 has been upgraded to support “speed dialing” feature.

In fact, previous versions can also support “speed dialing” feature by using “dial plan” functions. To do that, customers need make configurations with several tables, it could be difficult. With the new version, we separate a independent table to configure “speed dial” and it is so easy to support it.

Please refer to our document for more details about this feature:

http://www.myvoipapp.com/docs/mss_services/speed-dial/index.html

Trigger different IVR for different incoming calls

Trigger different IVR for different incoming calls

miniSipServer is upgraded to V6.5 to support different IVR for different incoming calls.

It is very easy to configure MSS to do that, please refer to online document:

http://www.myvoipapp.com/docs/mss_services/auto_attendant/index.html#multi-ivr

For example, if we want to trigger different IVR for another external line (such as “1234”), we can configure the “IVR services” with following record:

dial plan = default
Called number = 1234  <--This is the external line name/account
IVR-XML file name = aa2.xml <--your own IVR-XML file
Speed dialing in cloud IP-PBX

Speed dialing in cloud IP-PBX

“Speed dialing”, sometimes it is also named as “abbreviated dialing”, is a tranditional PBX service. It allows the user to invoke a call by pressing a reduced number of keys. This service is particularly useful for phone users who dial certain numbers on a regular basis.

In cloud-miniSipServer, it is very easy to configure this service. Please take a look at following figure:

Speed dial configuration in cloud-pbx

What we need do is just clicking menu “Advance service / Speed dialing” to add some records.

Hunt-group in Cloud IPPBX

Hunt-group in Cloud IPPBX

Yesterday we upgraded Cloud-miniSipServer to support hunt-group feature.

HG feature has been supported in local minisipserver for a long time. Lots of small companies use this feature to service their customers. The HG service in cloud-minisipserver is almost same with local-minisipserver, such as same service log, same configurations.

The difference is GUI display. Please refer to following figures.

One is for cloud-minisipserver.

HG configuration in cloud pbx
HG configuration in cloud pbx

another is for local-minisipserver:

HG configuration in local IP-PBX
HG configuration in local IP-PBX

For more details of hunt-group service, please refer to our online document:

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

Run as windows service

Run as windows service

2018-04-30 updated:

With the latest V32, miniSIPServer will not support this feature. Please try to run miniSIPServer in windows auto-start methods.