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

Trigger customerized Python service

2012/10/10 Gilson

As you may know, we can implement service logic by using Python script. It is very flexible to fit all kinds of customers’ requirements.

For example, MSS’ calling card service is written in Python script. In some fields, some customers require some different service logic,such as playing audio or not, prompt this or that, and so on. We can update python script file according to their requirement without any modification to MSS core.

But something is not so flexible. For example, the trigger of calling card is fixed in MSS core with previous versions. That means you can only trigger calling card service with called number ‘*300*’ of incoming calls. Some customers don’t like this number, some others want to support more called number to trigger calling card service.

With V10.4 released, we can configure different trigger for python services. In fact, we can trigger a python service according to their dial-plan and destination number in incoming calls. So everything is perfect now! Customers can implement their own service logic, they can trigger their services according to their real requirement. You don’t like ‘*300*’? no problem, just need configure another record!

For more details, please refer to manual document:

http://www.myvoipapp.com/docs/mss_services/manual/index.html#python_services

Integrated with outlook

2012/09/22 Gilson

Outlook is a very popular email/contact software for small business. Lots of customers hope to make SIP calls from outlook.

Now we are very pleasure to see that out partner, Gianfranco, has released a software to integrate outlook with miniSipServer. It is very exciting! You can use it to establish a completely unified communication system and it is so easy!

If you are interesting in this, please visit our partner’s website for more details:

www.digi-soft.net

New 500 clients version and MSS for linux

2012/09/10 Gilson

According to our customers’ requirement, we add a new product, 500 clients MSS, to our list. This version can support 500 extensions.

At the same time, we remove 1000 clients product from our public list which means you can still ask this product by sending mail to us. 1000 clients version is quite different with other versions, and it requires more help and support when customers try to deploy it, so we think it is not suitable for small business or SOHO business.

In another way, since Ubuntu LTS has been upgraded to 12.04 version, we upgrade all our work and test environments together, so MSS for linux version is upgraded to fit Ubuntu 12.04. We will not support other Ubuntu versions or linux distributions.

V10 released and TTS!

2012/07/29 Gilson

MSS V10 is released and supports TTS (Text to speech) feature now. With previous versions, once we want to play announcements, we need use some tools to record audios to create a wav file, then load it to MSS. We think tt is easy but some customers still think it is complex. So TTS is coming.

With TTS feature, you don’t need to create wav files. You just need write your announcement in text, MSS will play it for you. Cool! right? 🙂

Let’s look through XML-IVR of previous MSS ‘auto-attend’ service. We can see we need indicate an audio ID to MSS to play audio.

 <playaudio> 
     <id>0a080001</id>
 </playaudio>

Now, we can change it to following:

 <playaudio> 
     <text>Welcome, please input extension number</text>
 </playaudio>

MSS will play audio “welcome, please input extension number” to caller parties automatically, we don’t need create WAV file and load it to MSS.

Please refer to IVR-XML document for more details.

BTW, V9 is reserved for Cloud-MSS.

MySQL server has gone away

2012/07/12 Gilson

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

2012/06/20 Gilson

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?

2012/05/02 Gilson

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-en — 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 — Xlite configuration with UDP port 8080

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

2012/04/16 Gilson

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

2012/04/06 Gilson

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