We often configure miniSIPServer to connect VoIP carriers’ network with external lines. There are lots of VoIP carriers and someone always asks us how to configure external line.
In our step by step document, we give a demo to configure MSS to work with “call centric”. You can refer to this document for more details about VoIP networks and external lines. In another way, we give some more examples in chapter “External lines” of F.A.Q document. Please refer to these documents if you are interesting in it and hope they can be helpful to you.
miniSIPServer can support customers’ own audio files to replace default files. With previous MSS, customers have to backup and restore these files once they want to upgrade MSS.
This is a little trouble. With the new V32, we can resolve it now.
When MSS starts up, it will create a sub directory ‘cust_ann’ in ‘mss_ann’ directory, now all your own audio files can be stored in this directory. When MSS is uninstalled or upgraded, this directory and its files will not be deleted or replaced by default files, and MSS can get audio files from this directory directly when it starts up.
In windows system, it could be “d:/myvoipapp/minisipserver/mss_ann/cust_ann” directory by default. In Linux system, it could be “/opt/sipserver/mss_ann/cust_ann/”.
Please refer to our online document for more details about how to record own audio files.
Maintenance is required for all virtual servers in our cloud system. We will reboot all our servers in 2018-01-19 7:00:00 AM UTC. You can prepare your VoIP networks for this mantenance.
This action affects the underlying infrastructure that your virtual server resides on and will not affect the data stored within your virtual server
During the maintenance window, your virtual server will be cleanly shut down and will be unavailable while we perform the updates. A two-hour window is allocated, however the actual downtime should be much less.
We regret the short notice and the downtime required for this maintenance. However, due to the severity of these vulnerabilities, we have no choice but to take swift and immediate action to ensure the safety and security of our customers. For these reasons, we must adhere to a strict timetable, and will not be able to reschedule or defer this maintenance.
If you experience any issues following the maintenance, please feel free to reach out to us and we will be happy to assist.
“sonetel.com” is a VoIP carrier who can provide local phone numbers. We can add “external line” to work with their servers. According to its description, there are some special items need to be cared:
Sonetel uses email address as SIP account and
It deploys SBC or proxy to process all incoming SIP messages.
Here we give a simplel example to describe how to work with Sonetel. We assume the SIP account is “abc@gmail.com”.
In MSS, please cilck menu “data > external line” to add a record.
Configure Sonetel lline
In “Basic” tab, the line type should be “Connect to peer VoIP server”, the Account should be “abc” and the Domain is “gmail.com”.
By the way, the Password is the password you sign up in Sonetel, not your own email password.
Since all SIP messages are processed by sonetel SBC/Proxy, we need configure “outbound” information in the “Outgoing call” tab. Please refer to following figure.
Sonetel SBC
The Sonetel proxy address is “sip.sonetel.com” which should be described in the email sent by sonetel.
The latest Ubuntu 16.04 was released yesterday. Since it is a LTS version, we downloaded it as soon as possible and made some test in lab.
Some libraries have been upgraded or changed in this version, we need update MSS to fit these modifications. If you want to try miniSIPServer on Ubuntu 16.04, or you want to upgrade your previous Ubuntu to 16.04, you need install latest miniSIPServer V27 (build 20160422) .
Please refer to attached figure, we run the latest MSS on Ubuntu 16.04.
Some customers have several office branches and hope to establish VoIP connections between them. There are several methods to do that. Here we give an example to describe how to establish voip connections between two MSSes with SIP trunk feature.
2. Network topology
The network topology is simple. There are two office branches. Please refer to below figure.
Demo network
Before we setup voip network, it is better to assign extension numbers. Different office numbers will effect how to configure call routing in both MSSes. In above figure, we can see the extensions in office 1 are 1xx, and extension numbers in office 2 are 2xx.
Both MSSes are configured with public IP address. If your MSS is behind NAT or router and you want to provide connection for outsides users, please refer to another document firstly.
Now we give detail configurations for it.
3. Configuration
In below configurations, items should be kept their default values if we don’t configure them obviously.
3.1 MSS1
Please click menu “data – SIP trunk”, then add a record:
SIP trunk ID = 1
Description = to MSS2
Server address = 10.23.x.x
Please click menu “dial plan – analyzed called number” , then add a record for routing 2xx to such SIP trunk.
called number prefix = 2
route type = SIP trunk
SIP trunk ID = 1
3.2 MSS2
It is almost same with MSS1.
Please click menu “data – SIP trunk” to add a record.
SIP trunk ID = 1
Description = to MSS1
Server address = 41.32.x.x
Please click menu “dial plan – analyzed called number” for routing calls to above SIP trunk.
called number prefix = 1
route type = SIP trunk
SIP trunk ID = 1
Main feature of this version is “customized DNS”. It enables miniSIPServer to query DNS result with own asynchronous interfaces and independent DNS servers. That means MSS will not be blocked if there are exceptions in DNS systems.
Please refer to document for more details about this feature:
It is glad to hear that Ubuntu 15.04 is released today. We download the latest 64bit version and install it in virtualbox to test our new miniSIPServer V20 version.
We are very glad that it is no problem to run miniSIPServer V20 on this Ubuntu version. So you can enjoy it yourself if you want to try latest Ubuntu 15.04.
Of course, since 15.04 is not LTS version and is not recommanded to most customers, we suggest you to stay with LTS Ubuntu, such as 12.04 or 14.04.
We just tried windows 10 (tech preview) and find it is better than windows 8.1. And we are glad to find that it is no problem to run MSS on this platform.
run MSS on windows10
So if you are running Windows10， you can still deploy MSS to build your own VoIP system. Easy and funny, enjoy yourself!
