Browsed by
Author: Gilson

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

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

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

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.

Hunt-group in Cloud IPPBX

Hunt-group in Cloud IPPBX

Yesterday we upgraded Cloud-miniSipServer to support hunt-group feature.

HG feature has been supported in local minisipserver for a long time. Lots of small companies use this feature to service their customers. The HG service in cloud-minisipserver is almost same with local-minisipserver, such as same service log, same configurations.

The difference is GUI display. Please refer to following figures.

One is for cloud-minisipserver.

HG configuration in cloud pbx
HG configuration in cloud pbx

another is for local-minisipserver:

HG configuration in local IP-PBX
HG configuration in local IP-PBX

For more details of hunt-group service, please refer to our online document:

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

Run as windows service

Run as windows service

2018-04-30 updated:

With the latest V32, miniSIPServer will not support this feature. Please try to run miniSIPServer in windows auto-start methods.

The most easy-to-use IP-PBX for Ubuntu/Linux

The most easy-to-use IP-PBX for Ubuntu/Linux

If you have tried miniSipServer on Windows platform, you can find it is so easy to configure or manage a IP-PBX because miniSipServer provides a perfect GUI interface.

You can find it is very easy to do that on Ubuntu/Linux because miniSipServer can support GUI interface on Ubuntu/Linux now!  WINE is unnecessary now!

Please visit our download page to download miniSipServer .deb packages according to your requirements:

http://www.myvoipapp.com/download

After you download .deb file from our website, please click (or double-click) it to install MSS. No more actions! So easy, so funny.

After you finish your install, you will find miniSipServer at “Applications / Internet” group.

Following figure is a screenshot of MSS running on Kubuntu:

MSS main windows on Kubuntu

In another way, if you just want to run a command line sip server, you can also go to directory “/opt/sipserver” and find “msscli” which is a command-line miniSipServer and has the same core with GUI-miniSipServer.  You can manage and configure it through web interface.

Block some extensions

Block some extensions

Sometimes, we need limit the call right of some extensions. For example, we want to limit only specific extensions can make out-group calls to outsides, others can only make calls between extensions.

In MSS, we use “call level” feature to do it. By default, we don’t assign “call level” to any called number prefix in “analyze called number” table. That means all extensions can have the same right. To limit extensions, we should indicatedifferent “call level” to the called number prefix and assign relative “call level” right to special extensions, then they will have the right to make such calls.

For example, the default out-group call prefix is “9”. Please click menu “Dial plan /  Analyze called number” and edit or add a record whose prefix is “9” and route type is “external line”. In this configuration, we can select “call level 1” to this prefix “9”.

Then, please click menu “data / local users” and edit or add a local user. In the pop-up dialog, please click “Basic Call” tab and enable “Call level 1” to this extension.

After that, the extension has the “call level 1” right to make calls to outside by dialing “9xxxxx”. For others, since they don’t have “call level 1” right, their calls will be rejected when they dial “9xxxxx”.

How to send instand messages between SIP servers

How to send instand messages between SIP servers

One of our customer has two office branch in different cities and two MSS have been deployed. Following figure describe the network topology:

Network topology

The extensions of MSS1 are 1xx, such as 100,101, and so on.

The extensions of MSS2 are 2xx, such as 200, 201, and so on.

With previous MSS versions, it is no problem to send/receive instant messages between local users. But it cannot send instant messages to the extensions of another SIP server.

So we upgrade MSS to V6.1.5 to support instant messages between SIP servers.

To do that, we need establish SIP trunk between these SIP servers. Once you can make calls to the extensions of another SIP server (MSS), it will be no problem to send instant messages to them.

That means we need configure MSS with (1) peer server configurations, (2) Dial plan configurations which we have described in “how to use SIP trunk” document. Please refer to following document for details of SIP trunk:

http://www.myvoipapp.com/blog/2011/05/02/sip-trunk/