All products of myvoipapp.com
Today we release latest V15 for miniSIPServer. This version is focus on providing a new service engine which is written in Python script.
That means almost all services are written in Python script files. New service engine is more flexible to fit different services requirements. Some advanced customers even can written their own special services now.
Today we upgrade miniSIPServer V14 to support 64 bits Debian and Ubuntu. That’s a great news for some of our customers.
As we know, in some networks, customers have deployed 64 bits Debian or Ubuntu servers. So when we want to install previous 32 bits miniSIPServer in their servers, it is required to install some additional 32 bits libraries. Of course, it is no problem to do that, but some customers often think it could be unstable for their servers.
So we decide to migrate MSS to 64 bits to fit this requirement. Now it is unnecessary to care about 32 bits problem.
For customers who are using 64 bits Windows, it is unnecessary to care about 32 bits problem. Windows can process them in perfect way, so please keep current versions.
V14.4 is updated to support a new feature in “dial plan” process. This feature is “refine called number”.
“Refine called number” can be used to refine called number before calls are routed to external lines or SIP trunks. It is the last chance to change called number to fit different requirements from peer VoIP servers.
For example, one of our customer has two VOIP accounts. One is from local provider, another is from international provider. These two VoIP providers have different number format requirements, and our customer only want to has one kind of dial plan for both of them. So we can configure “refine called number” to refine the final destination number to fit it. This scenario is illustrated below.
As described above, there are two VoIP accounts, and users need dial “90xxxx” to make outbound calls. “9” is MSS default outgoing call prefix. “0” is required by local VoIP provider. At the same time, the international VoIP provider requires that the number format should be “0086xxxx”.
After compare these number formats, we can find that we only need change prefix “0” to “0086” for international VoIP account.
Please click menu “Data / External line” and select the account to edit, then please click “Outgoing call” tab and configure following item:
Outgoing group ID = 1
We need configure a new record to change preifx “0” to “0086”. Please click menu “Dial plan / Transition” to add a new record:
Transition ID = 1 Transition type = Replace Start position = 0 Length = 1 Replace string = 0086
Please click menu “Dial plan / Refine called number” to add a new record:
Outgoing group ID = 1 <== defined in step 1 Called number prefix = 0 Transition ID = 1 <== defined in step 2
Here we maybe have a problem: the called number prefix is “0”, why? why not analyze “9” prefix? It is because that “9” has been deleted in “analyze called number” procedure and the number has been changed to “0xxxx” before it is sent to external line or SIP trunk, so we should analyze prefix “0” to refine final called number.
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.
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.
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
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
The latest Ubuntu/Kubuntu V13.10 is released. We download and install it immediately in our lab. It is no problem to run miniSIPServer on these systems. But according to our experience and test result, we dont suggest customers to upgrade systems to V13.10 because it is not stable enough for business deployment now.
So if you are running miniSIPServer on Ubuntu/Kubuntu, it is better to keep your current versions and wait for next LTS version V14.04.
miniSIPServer is upgraded to V14.2 now. With latest versions, following key features are included:
(1) For raspberry Pi. As we know, raspberry Pi is a very small PC run on Debian system, MSS can work on this hardware now. It is very helpful for some small business who dont want to maintain a PC hardware and save many cost.
(2) Provide open API. MSS can start web server and provide open HTTP API . 3rd parties can use this interface to intergrate with their own system. At this time, open API set can support: query MSS version; configure or query details of local users.
(3) Routing group. It is a very helpful feature for customers who have lots of external lines or SIP trunks. They can manage these lines or trunks into different groups for different users or for different calls. The workload of group is in round-robin policy.
Hope you can enjoy our new versions! If you have any questions or suggestions, please feel free to contact us. We are always here for you.
Most SIP devices, such SIP phones, can support “call waiting” service themselves. But for some old SIP devices, such as some simple SIP ATA devices, it is required PBX to provide “call waiting” service.
So we upgrade MSS to V13.6 to provide this service. In MSS, we name it as “simple call waiting” service because MSS’ call waiting service only support
(1) put original call into waiting queue if current called party is busy.
(2) reconnect previous calls if current called party is available.
So user cannot press ‘R’ key to switch calls. It is simple and we hope it can fit most customers requirements.
Please refer to our service document for more details:
http://www.myvoipapp.com/docs/mss_services/call-waiting/index.html
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.
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.
12:00AM (EDT): We are very sorry to update that our data center has some connectivity issues, it effects our cloud-mss services. Most customers have to wait our parner to resolve this issue.
We apologize for this issue. We will update this blog accroding to update our status.
updated: Now all things are ok.