Browsed by
Category: Docs & FAQ

MyVoipApp documents and FAQ

Trigger hunt-group for external lines incoming calls

Trigger hunt-group for external lines incoming calls

Some customers use external lines to connect VoIP providers’ servers. So it is required to trigger hunt-group for all incoming calls from such external lines.

Lets’ assume the external line number/account is ‘123456’, so we just need trigger HG service according to this number.

Please click menu “services / multi-line hunting group / Detection configuration” to add a new record as following:

dial plan = default
called number = 123456 <-- this is the external line number
... ...

Others are same with HG service document:

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

If the external line is configured with auto-attendant or routed to another destination number, what is the result? Don’t worry. HG detection has higher priority than these services, that means HG will be triggered even you configured AA or destination number in external line.

How to change TCP port?

How to change TCP port?

2013-09-23 updated: with latest V14.2, we can configure ‘TCP port’ in MSS. Please refer to following document:

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

——————————————————————-

By default, MSS starts 5060 TCP port to receive or send SIP over TCP messages. 5060 is default TCP port defined by SIP standard. In MSS GUI or web UI, we can only change SIP UDP port.

If we want to change its TCP port, for example, we want to change it to 1234, we need do as following:

(1) In the MSS install directory, please create a text file whose name is ‘mss_var_param.ini’ file.

(2) In this INI file, please add following content:

[sip]
gVarSipTCPPort=1234

(3) Please restart MSS to enable it.

Reports in MSS

Reports in MSS

2020-12-29 updated: Since miniSIPServer has ‘event channel‘ function to provide users’ status and details of each call, customers can use these information to build their own reports, so we cancel these functions from V38.

Most SIP or PBX devices may have some reports to help administrator to check system’s status.

MSS has some reports too. Please click menu “Reports” to show them. MSS has two reports at this time:

(1) Basic call report

(2) Local user report

Both these reports are generated per hour. If there is not any value for each item, then the report will not be generated.

“Local user report” is simple. It only calculates how many local users are online per hour.

“Basic call report” is used to calculate how many calls MSS has been processed in one hour. There are some important items, such as “attempt”, “alert”, and “answer” and so on. It includes total durations and it can help administrator to understand how many calls have been answered and the avarage duration in one hour. If there are too many calls to make MSS heavy work-load, administrator can decide to upgrade MSS.

How to run miniSIPServer on Ubuntu?

How to run miniSIPServer on Ubuntu?

Updated: Now you can visit online document for more details.

If you are using Ubuntu (desktop), it is very easy to run MSS. Just download .deb file from our website and double click such .deb file to install it. Then you can find MSS icon in ‘internet’ or ‘network’ menu group and run it to start MSS.

If you are using Ubuntu (server), something is different. You need do more steps to install and run MSS. We describe details below.

First, you must download .deb file from our website, for example ‘mss_v13_u20.deb’. Then, you can run following command:

sudo dpkg -i mss_v13_u20.deb

At this step, Ubuntu will prompt error that some dependencies must be installed. Don’t warry, please continue following command:

sudo apt-get -f install

Then Ubuntu will try to get and install all necessary dependencies from Ubuntu software center.

In Ubuntu server, you cannot run MSS GUI since X windows is not started. You can run MSS CLI version whose file name is ‘msscli’ and can be found in directory ‘/opt/sipserver’.

So it is very easy to start MSS now:

/opt/sipserver/msscli

To visit and manage MSS system, you need visit its web system whose TCP port is 8080 by default. Please refer to following document:

http://www.myvoipapp.com/docs/mss_services/web_management/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.

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

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.

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

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.