Browsed by
Category: Docs & FAQ

MyVoipApp documents and FAQ

why one-way audio problem?

why one-way audio problem?

Almost all of us will meet this problem when we deploy our first VoIP network. We are often confused: why I cannot hear peer guy but he can hear me? why we cannot hear each other?

The root reason is that there is private network and public network. If both sides are in different network, the problem will happen. Please look at below figure which desribe a very simple VoIP network:

One way audio problem network topology

In this simple network, we have two VoIP devices, one is SIP phone whose number is 100, another is SIP client whose number is 101.

SIP phone is in a private network and its private address is 192.168.1.100, and its router is connected to public network with address 8.8.8.8.

SIP client is installed in one PC which is in the public network with address 8.8.4.4.

So when SIP phone makes a call to the SIP client, what will happen?

SIP phone say: Hi, I am 100, my audio address is 192.168.1.100. Please send audio stream to me.

SIP client answers it: ok. I am 101, my audio address is 8.8.4.4. Please send your audio to me.

SIP phone sends audio stream to SIP client. Since “8.8.4.4 ” is a public address, it is no problem for SIP client to receive the audio stream from SIP phone. That means SIP client can hear SIP phone now.

SIP client sends its audio stream to SIP phone “192.168.1.100”. You can see it is a private address and cannot be reached by SIP client which is in public address. SIP client will fail to send its audio stream to SIP phone in fact.

So finally, SIP client can hear SIP phone, but SIP phone cannot hear SIP client. This is a very typical one-way audio problem.

Then, how can we resolve it? To be continue …… 🙂

Can miniSIPServer support G.729, iLBC, GSM audio codec, or video calls, and so on?

Can miniSIPServer support G.729, iLBC, GSM audio codec, or video calls, and so on?

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

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

Why we say that?

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

From this figure, we can see:

(1) miniSIPServer 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 media codecs.

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

That’s right. If miniSIPServer need process audio stream, it can support two audio codecs: G711a (PCMA) and G711u (PCMU).

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 miniSIPServer for these scenarios:

Play audio stream
Why I cannot receive voice mail?

Why I cannot receive voice mail?

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.

how to link fxo gateway?

how to link fxo gateway?

It is a often asked question. In MSS, you can use “external line” to connect to your fxo gateway. In our forum, we give a simple description about how to link to linksys 3102. Maybe you can refer to this document for help.

http://www.myvoipapp.com/forums/viewtopic.php?f=5&t=419

(Sorry, since our forums have been removed, above document cannot be visited. Please refer to online F.A.Q document. Thanks. )

Run miniSipServer on Ubuntu

Run miniSipServer on Ubuntu

2011-12-26 updated:

Please visit following blog for latest message:

http://www.myvoipapp.com/blog/2011/12/26/the-most-easy-to-use-ip-pbx-for-ubuntulinux/

======================================

Since miniSipServer V4.0 is released, it is very easy to deploy VOIP server on Ubuntu now.

The difference between MSS V4.0 (windows) and MSS V4.0 (Linux) is that MSS (linux) doesn’t provide GUI management. It only provide web management. It is still very easy to setup and manage the VOIP network.

First, please download xxx.tar.gz file from our website. In following section, we give example on how to use miniSipServer V4.0 (20 client) :

http://www.myvoipapp.com/download

It is a zip package file, once you have download it, please use following command to unzip it.

tar zxvf mss_v4_u20_i386.tar.gz

After that, you can find a “install.sh” file in the directory. Please run it to install MSS. During the process, some 3rd parties software, such as libmysqlclient, will be installed automatically from Ubuntu software center.

sh install.sh

Then, you can run miniSipServer now:

sudo msscli

When the MSS is running, you can find following information in the command window:

HTTP server is running at port 8080

It means MSS has started HTTP server at TCP port 8080, you can  visit it now to manage your SIP server by using firefox, chrome, IE,etc. For example, you can open local firefox and type following address to visit it:

http://localhost:8080

We have to mention here the default administrator password is blank. So once you login into the web management, the first thing you need do is to set administrator password. Please click “basic configuration / system configuration” to do that.

So easy, right? If you have any questions, please fell free to contact us. We hope you can enjoy it!

sip trunk

sip trunk

In VOIP depolyment, “SIP trunk” is often used to establish a connection with peer sip servers or gateways. For example, in most DID services deployments, SIP trunk is required to send or receive DID calls.

The difference between “SIP trunk” and “External lines” is that SIP trunk doesn’t require authorization during the call. That means, “external line” is server-to-users mode and “SIP trunk” is a server-to-server mode.

It is very easy to establish SIP trunk in MSS.

For example, we want to establish SIP trunk with peer server whose domain name is “sip.demo.com” and its SIP port is 5060 which is a default SIP UDP port.

step 1: add the server into MSS servers list

Please click menu “data / peer servers” and add a new record with following information:

peer server id=1
description = demo sip server
server address = sip.demo.com
server port  = 5060

step 2: process incoming call

Once we receive incoming calls from peer servers, we want to route them to local users. We can use “dial plan” to do that.

For example, we want the DID incoming calls whose called numbers prefix is “1234” to local users, such as 1234100 to local user 100, 1234101 to local user 101, etc.

Please click menu “dial plan / transition” to configure a number transition:

transition ID = 1
transition type = delete
start position = 0
length = 4

Please click menu “dial plan / analysis called number” to configure a record to route DID numbers to local users:

dial plan = default
called number prefix = 1234
route type = local user
change called number = yes
transition id = 1

step 3: process outgoing call

We want our outgoing calls to be routed to such peer SIP server/gateway. We still need configure “dial plan” to do that.

For example, we want all calls whose called number prefix is “00” should be routed to such SIP server, such as “008613800138000”, etc.

Please click menu “dial plan / analysis called number” to add a new record with following information:

dial plan = default
called number prefix = 00
route type = SIP trunk
peer server ID = 1

 

How to upgrade miniSipServer?

How to upgrade miniSipServer?

In different scenario, this question can be different. In fact, this question can be seperated to several questions:

Q1: What we need do when we upgrade MSS?

The most important thing is backup your previous configuration files.If there is any exception during the upgrade, we can roll-back to previous version.

All miniSipServer configuration files are stored in the ‘config’ sub-directory where MSS is installed.So it is very easy to backup the system, what we need do is just copy this sub-directory to anywhere your want.

We can uninstall previous version and install the new version in the same directory.Because the configuration files are kept in the ‘config’ directory, the new version will detect, use and upgrade previous configuration files automatically.

Q2: I am using V2.9, can I upgrade to V2.10 or above?

Yes, of course. By default, it is free to upgrade MSS from low version to higher version since they can share the same license. So just download the latest version and enjoy it.

Q3: I am using 20 clients version, can I upgrade to 50 clients and how?

Since different licenses are used, you need pay the price differentials between these version. Please visit our ‘buy now‘ page to get details.

Once you get the new license, you can uninstall previous version and install new version, then input new license to enable it. The upgrade process is almost same with above description.

Can miniSipServer run on Linux system?

Can miniSipServer run on Linux system?

2011-12-26 updated:

WINE is unnecessary for latest miniSipServer! Please visit following blog for new message:

http://www.myvoipapp.com/blog/2011/12/26/the-most-easy-to-use-ip-pbx-for-ubuntulinux/

===========================================

Linux system becomes more and more popular now, and more and more customers send mail to us to ask whether miniSipServer can run on linux system, specially Ubuntu system.

As we know, miniSipServer is a SIP server designed for Windows system. Since Linux is quite different with Windows, we cannot install and run miniSipServer on Linux directly at current stage. In future, we maybe release native miniSipServer for Ubuntu. (In fact, miniSipServer V4.0 or above can run on Ubuntu without WINE, please refer to following document: http://www.myvoipapp.com/blog/2011/06/01/run-minisipserver-on-ubuntu/)

But now we can run miniSipServer on Ubuntu or other linux systems with “Wine” software. Thanks to “Wine” develop teams’ great work, most windows softwares can run on linux system, including miniSipServer.

The Wine mode is “Linux sysem <–> Wine <–> Windows software”. Please refer to its official websire for more details.

After download and install “Wine” software, it is almost same for us to install and run miniSipServer which we have done on the Windows platform. What we need do is doublt-click the .exe file and install it! Very easy.

Let’s give a simple example on how to install wine and miniSipServer on Ubuntu system:

Step 1: install Wine

In the terminal window, please type the command: sudo apt-get install wine

Step 2: install miniSipServer

Download the latest miniSipServer install file to our Ubuntu system. Double-click the .exe file to install it.

Step 3: run miniSipServer

In the Wine menu, we can see miniSipServer shotcut icon. Just click the icon to run it.

Easy, right? why not try it now? 🙂