Browsed by
Category: Products

All products of myvoipapp.com

Gtalk to SIP

Gtalk to SIP

We are very exciting to release miniSipServer new version 11! This is a great version and can support ‘Gtalk to SIP’ feature now.

What that means? It means you can connect your VoIP network with Gtalk network now. Gtalk users can call to your extensions directly, use your VoIP services, and so on. We bring Gtalk into your enterprise communication system. Funny!

Please refer to our online document for more details:

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

I cannot find my external lines, why?

I cannot find my external lines, why?

Some customers will find that their external lines configuration were gone when they sign into their cloud-mss accounts.

What happened to their accounts?

The root reason is that these customers maybe configure wrong external lines information, such as invalid password, then cloud-mss fails to register these external lines to VoIP carriers. cloud-mss will try to register them for lots of times. In this scenario, peer VoIP carriers could treat cloud-mss as a spammer or an attacker, and they will block or filter cloud-mss messages, that could effect other cloud-mss customers.

To avoid that, if cloud-mss always fail to register an external line for lots of times, it will report this external line to background administrator system, and this external line will be deleted automatically.

That’s why you cannot find your external line information. So please double check your information or check with your VoIP providers, then try to configure them again.

miniSipServer for ubuntu 12.10

miniSipServer for ubuntu 12.10

Yesterday we got and installed latest Xubuntu/Kubuntu/Ubuntu 12.10, then we installed latest miniSipServer V10.5 on these platforms.

The result is perfect! It is no problem to run MSS without any modification.

In another way, we would like to suggest Xubuntu and Kubuntu. According to our test result, Ubuntu system is very slow, however Xubuntu and Kubuntu are perfect.

SIP over TCP

SIP over TCP

As we know, most SIP devices use SIP over UDP by default,  however, some SIP servers or communication servers only support SIP over TCP. We have to say that’s really strange. Our customers need work with such devices and we upgrade MSS to V10.5 to support SIP over TCP to fit this requirement.

It is very easy to configure MSS to support this feature. If you are interesting in it, please refer to following document for more details about it:

http://www.myvoipapp.com/docs/mss_services/sip-over-tcp/index.html

Trigger customerized Python service

Trigger customerized Python service

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

Offline instant messages

Offline instant messages

Today we upgrade cloud-MSS to new version to support offline-IM feature.

In a unified communication environment, it is very common for users to send or receive offline instant messages, specially some customers use cloud-MSS as their internal communication tool.

With this new version, cloud-MSS can support IM as following:

(1) If called party is online, Cloud-MSS will send IM to it immediately.

(2) If called party is offline, Cloud-MSS will save its offline IM. Clou-MSS can store no more than total 10 offline-IM for each local user. Each IM should be less than 200 characters.

(3) If called party is back to online again, Cloud-MSS will send its offline-IM to it automatically.

You don’t need configure anything for this feature, it is so easy to setup a UC system for your business now. Why not take a try? 🙂

Integrated with outlook

Integrated with outlook

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

New 500 clients version and MSS for linux

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!

V10 released and TTS!

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

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.