Browsed by
Tag: voip

Two external lines, how to use specific one by dialing different called number prefix?

Two external lines, how to use specific one by dialing different called number prefix?

Description

One of our customers has two different VoIP accounts, for example (1) 1234 and (2) 5678. It is required to select account “1234” if users dial “9xxxx” numbers and select account “5678” if users dial “8xxxx” numbers. The final numbers should delete these prefix “9” or “8” and “xxxx” should be sent to VoIP providers.

Solution

We can use MSS powerful “dial plan” features to fit this requirement.

By default, MSS uses called number prefix “9” to distinguish outgoing calls to outsides. If there are several external lines and without any special configuration, MSS will select one of them in round-robin for each call. Now what we need do is to configure different called number prefix and select different external line for them.

Step 1: configure number transition

In this step, we need configure a record to delete number prefix “8” or “9” from called numbers. Please click menu “Dial plan / Transition” to add a record illustrated below.

Transition ID = 1
Transition type = delete
Start position = 0
Length = 1

Step 2: add new “Analyze called number” records

According to requirement, we need indicate MSS to analyze called number prefix “8” and “9” to use different specific external line. Please click menu “Dial plan / Analyze called number” to add two records.

Record 1: analyze called number prefix “9”

Dial plan = default
Called number prefix = 9
Route type = external line
Specific external line = 1234 <== use specific external line
Change called number = yes
Transition ID = 1 <== configured in step 1
Re-analyze after transition = no

Record 2: analyze called number prefix “8”

Dial plan = default
Called number prefix = 8
Route type = external line
Specific external line = 5678 <== use specific external line 
Change called number = yes
Transition ID = 1 <== configured in step 1
Re-analyze after transition = no
SIP over TCP

SIP over TCP

As we know, most SIP devices use SIP over UDP by default,  however, some SIP servers or communication servers only support SIP over TCP. We have to say that’s really strange. Our customers need work with such devices and we upgrade MSS to V10.5 to support SIP over TCP to fit this requirement.

It is very easy to configure MSS to support this feature. If you are interesting in it, please refer to following document for more details about it:

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

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

Integrated with outlook

Integrated with outlook

Outlook is a very popular email/contact software for small business. Lots of customers hope to make SIP calls from outlook.

Now we are very pleasure to see that out partner, Gianfranco, has released a software to integrate outlook with miniSipServer. It is very exciting! You can use it to establish a completely unified communication system and it is so easy!

If you are interesting in this, please visit our partner’s website for more details:

www.digi-soft.net

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

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.

How to deploy MSS behind NAT and provide public service

How to deploy MSS behind NAT and provide public service

Some customers often request to deploy MSS behind NAT, but still need provide public service. That means MSS is in private network and some SIP phones/clients are in public network (internet), or MSS need work with public VoIP carriers’ network.

Following figure describes a simple network for this scenario:

Demo network

In this network, we can see

(1) Private network is connected to public network by a router whose public address is 8.8.8.8 and private address is 192.168.1.1

(2) MSS is deployed in private network with private address 192.168.1.2.

(3) Some SIP phones are in the same private network, such as local users 100 and 101. Some SIP phones are in public network, such as local user 102.

It is no problem for local user 100 and 101 to visit MSS since they are in the same network. So the problem is how to make outside local user (102) can visit MSS.

We can resolve it by forwarding some ports in router.

First, in the router, we can configure forwarding UDP port 5060, 10000~20000 to the PC where MSS is installed. Most routers can support this function. Port 5060 is standard SIP port. Ports 10000~20000 are RTP ports to transfer media streams.

Second, we must indicate MSS to work with public address. Please click menu “Data / System / SIP” and fill the  “Main address” with the public address “8.8.8.8”. SIP phones/clients can use this public address to visit MSS.

There is another problem. In above scenario, the router is configured with a fixed public address. In normal, the router could be ADSL router and it maybe has a dynamic IP address. Outside users cannot use the dynamic address to visit MSS. Then, how can we provide public services?

To resolve it, we can use domain name, for example, we can use DynDNS to provide domain name for our MSS. The router must be able to support “Dynamic DNS”. In our example, we assume we get a domain name “sip.dyndns.org” from DynDNS and configure it in our router, then we can use this domain name as another miniSIPServer address. In following figure, we use such domain name as main address, and use the private address as additional address.

SIP configuration
SIP configuration

SIP phones/clients must be able to use domain name as server address or proxy address, so they can configure “sip.dyndns.org” to visit MSS in our scenario and make calls.