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

Posted on May 2, 2012 by 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 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

Speed dialing in cloud IP-PBX

Posted on February 29, 2012 by Gilson

“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:

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

Upload customized audio file

Posted on November 10, 2011 by Gilson

Cloud-MSS is upgraded to support uploading customized audio file.

In auto-attendant or voice-mail features, customers often hope to use their own audio files. It is very easy to replace system audio files in local-MSS. But in cloud-MSS, it has little problem, such as file transferred through internet, etc.

With the new version, customers can upload audio file through HTTP. Of course, the audio file should have the same format same with local-MSS required.

After sign into your cloud-MSS account, please follow the steps described in below figure:

We need mention that please be paitent because cloud-MSS will try to download the audio file from your HTTP URL immediately. It could be slow if the network is not very good.

SIP trunking with user name and password

Posted on September 21, 2011 by Gilson

Some VoIP providers support “SIP trunking” services, most of them require user name and password for authorization.

To work with such SIP trunking, we need configure “external lines” in miniSipServer to establish connection with the VoIP carriers’ server.

In the external line configuration, we can configure peer server address (or domain name) , user name and password for authorization of register process and call process.

Can MSS support G.729, iLBC, GSM audio codec, and so on?

Posted on August 5, 2011 by Gilson

We are often asked this question about audio codec. Some customers want to confirm whether MSS can work well with their SIP phones/clients who can support several audio codecs.

We often answer that it depends on their own SIP phones/clients. MSS, not matter local-MSS or cloud-MSS, doesn’t care audio codec by default.

Why we say that?

Please have a look at following figure which describe a basic media process model of MSS in a normal basic call.

From this figure, we can see:

(1) MSS only controls call signals.

(2) Media stream is processed by the clients themselves.

This model will reduce the work-load of the server since all media streams are bypass server, so it is unnecessary for the server to support several audio codecs.

But in some service scenarios, MSS need play audio to the SIP phones. For example, in auto-attendant or calling card services, MSS need prompt audio announcement and collect user input information. Obviously, MSS is required to support audio codecs in these scenarios.

That’s right. If MSS need process audio stream, it can support three kinds of audio codecs: G711a (PCMA), G711u (PCMU) and GSM.

By the way, after playing audio stream, the final media stream will be processed still in end-to-end model. Please refer to following media model of MSS for these scenarios:

Play audio stream

Why I cannot receive voice mail?

Posted on August 4, 2011 by Gilson

When some customers use miniSipServer cloud ( for local minisipserver, the same) to process their voice mail, but they are often confused why cannot receive voice mail in their email box.

In fact, we have an online document to describe how to use voice mail feature. Please refer to:

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

For MSS cloud, there is a little difference. First, MSS cloud doesn’t support MWI (message waiting indication), so it can only send voice messages to your email address. Sometimes, customers often forget to configure SMTP server information which is necessary for MSS cloud to send your voice mail, or they often forget to cofigure email address of specific extensions.

So let’s describe more details about these. Before this, I assume that you have signin into your MSS cloud account. If not, please sign-up one.

Step 1: configure SMTP server information

smtp configuration in mss cloud system

Please look at the figure. You need click “system information” linker, then fill your SMTP information there. By the way, for Gmail accounts, they are always required to configure secure connection.

If SMTP information are all right, MSS will use it to send voice mail.

Step 2: configure email address of extension

configure email address of extension

Please click “local users” linker and select or add one extension to edit. For voice mail feature, you must configure “eMail address” to make MSS cloud know where the voice mail should be sent to.

Of course, you also need configure “voice mail” service right to this local user / extension.

So after that, for no-answer incoming calls, MSS will prompt the caller party to leave messages and save/mail them to the user’s email address.

MyVoipApp products blog

Software based VOIP server

Category Archives: miniSipServer Cloud