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.
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:
With latest V13.1, MSS can support “SIP over TLS” now. In some enterprise communication systems, they often requre that SIP/Call signals or messages must be crypted to protect users information. Now it is very easy to do that with this new version.
Please refer to our online document for more details about this feature:
The latest LTS is upgraded from V6.6 to V12 which has been tested and deployed around world by our customers.
V12 has much more features than previous V6.6.x and stable enough to be a new LTS version. Of course, we provide at least one-year supporting service for this new version.
Previous LTS version (V6.6.x) will be kept in supporting list until end of this year (2013).
At the same time, stable version is upgraded to V13. New features will be merged into this version and V12 will not include any new feature or service.
We are very exciting to release miniSipServer new version 11! This is a great version and can support ‘Gtalk to SIP’ feature now.
What that means? It means you can connect your VoIP network with Gtalk network now. Gtalk users can call to your extensions directly, use your VoIP services, and so on. We bring Gtalk into your enterprise communication system. Funny!
Please refer to our online document for more details:
Yesterday we got and installed latest Xubuntu/Kubuntu/Ubuntu 12.10, then we installed latest miniSipServer V10.5 on these platforms.
The result is perfect! It is no problem to run MSS without any modification.
In another way, we would like to suggest Xubuntu and Kubuntu. According to our test result, Ubuntu system is very slow, however Xubuntu and Kubuntu are perfect.
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:
According to our customers’ requirement, we add a new product, 500 clients MSS, to our list. This version can support 500 extensions.
At the same time, we remove 1000 clients product from our public list which means you can still ask this product by sending mail to us. 1000 clients version is quite different with other versions, and it requires more help and support when customers try to deploy it, so we think it is not suitable for small business or SOHO business.
In another way, since Ubuntu LTS has been upgraded to 12.04 version, we upgrade all our work and test environments together, so MSS for linux version is upgraded to fit Ubuntu 12.04. We will not support other Ubuntu versions or linux distributions.
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 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.
