Browsed by
Category: Products

All products of myvoipapp.com

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 redirect external line incoming call to an hunting-group

How to redirect external line incoming call to an hunting-group

By default, incoming calls from external lines will be routed to local users or auto-attendants.

But in some deployment, customers require that incoming call from external lines should be routed to hunting-group. Then local users can answer the incoming calls in round-robin order.

It is very easy to do that in MSS. Do you remember that we need configure a called number to trigger hunting-group, right? In this table, you only need configure it with external line number.

For example, external line is “1234567”, then in the “hunting group detection” configuration, we only need configure detection called number to be “1234567” to trigger hunting-group.

Upload customized audio file

Upload customized audio file

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:

Add system audio file into cloud-mss

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.

INFO-DTMF

INFO-DTMF

miniSipServer V6 is upgraded to V6.1.3. This version can support SIP INFO message to transport DTMF signals.

Some VoIP carriers’ servers or VoIP gateway can only support this INFO message to transport DTMF signals which are very necessary for IVR services, such as auto-attendant.

There are several content type in INFO message to transfer DTMF. MSS can support “application/dtmf-relay” content type.

Now, MSS can support INFO and RFC2833 for DTMF signals.

V6.1 and IVR XML

V6.1 and IVR XML

MSS stable version is upgraded from V6.0 to V6.1.

In this new version, IVR-XML is supported and we can use XML to write IVR services. It is very easy and funny. We re-write auto-attendant service with IVR-XML, you can see it is very simple. The latest auto-attendant service file can be found in sub-directory ‘xml’ and file name is ‘aa.xml’.

The latest AA document is updated together, please refer to :

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

Most important, it is very easy to setup multi-levels menus in IVR services.

Please take a try and you will like it.

SIP trunking with user name and password

SIP trunking with user name and password

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.

LTS and stable versions upgrade

LTS and stable versions upgrade

Both LTS and stable versions are upgraded. It is very important to our customers to upgrade your system to latest versions.

LTS version is upgraded to V4.0 to replace previous V2.x, more stable, more rich services.

Stable version is upgraded to V6.0. New features will be researched and developed based on this version.

V5.0 version is reserved for cloud-miniSipServer.

Prepaid service in cloud communication

Prepaid service in cloud communication

We are proud to announce that cloud-miniSipServer is upgraded today to support “caller prepaid” feature.

“Caller prepaid” service is an important service in local-MSS and has been deployed around the world. More and more customers use it to build some simple virtual VoIP carriers system with this feature.

Now, we can setup it in cloud communication. “Call prepaid” service in cloud, looks like very exciting, right? We believe this feature will benefit our customers to extend their VoIP business.

It is so easy to be a virtual VoIP carrier, why not take a try? Please visit http://minisipserver.com and sign up an account for free trial.

miniSipServer V3 updated

miniSipServer V3 updated

MSS V3 is updated to build 20110901 to fix a bug in SIP stack to support “Min-Expires” header in SIP messages.

This bug is also fixed in latest MSS V4.