webRTC is defined in HTML5 to support real-time communication. We spent several months in this technology and release the latest V18 to support it finally!
Now you can connect Chrome to miniSIPServer to work as local user. It is so interesting and hope it can help you to deploy your own VoIP network.
Please refer to following document for more details about webRTC in MSS:
http://www.myvoipapp.com/docs/mss_services/webrtc/index.html
As we know, IPv6 is next internet protocol. All SIP devices will be migrated to IPv6 since IPv4 network has more and more problems.
Today we release miniSIPServer V16. The big feature of this version is to support IPv6. You can find it is so eay to deploy a voip network over IPv6 with miniSIPServer.
Please refer to following document for more details and enjoy IPv6 now!
http://www.myvoipapp.com/docs/mss_services/ipv6/index.html
And V16 will be next LTS version once we think it is ready for that.
Since cloud-mss is online, there are lots of customers ask us about reseller funciton. Thanks for their suggestions. We do some research on this topic and find it could be classified to two types:
(1) Some customers are professional communication providers for enterprises. They often install several cloud-mss servers for their own customers, so it is very useful if they can manage several nodes in one account.
(2) Some cutstomers provide SIP-PBX services for their local subscribers with their own domain names, so they not only want to manage several virtual sip-pbx nodes in one account, but also want to get more discount pricing.
We add ‘reseller’ function into cloud-mss system. It is free to register cloud-mss account and users can create and manage several cloud-mss nodes. Each node can be configured independantly just like common node.
If you are interesting in this topic, please take a try and feel free to contact us if you have any question or suggestion.
Please refer to our online document for more details:
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.
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
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.
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:
http://www.myvoipapp.com/docs/mss_services/sip-over-tls/index.html
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.