Browsed by
Tag: phone

miniSIPPhone for Linux

miniSIPPhone for Linux

Finally, miniSIPPhone is upgraded to V10. The most important thing is that it can support Linux system now. As same as miniSIPServer, Debian must be V10 (Buster) or higher versions, and Ubuntu must be V18.04 (Bionic Beaver) or higher versions. We are not sure of other distroes.

Both X86_64 (amd64) and AARCH64 (arm64) are supported.

It is quite easy to run SIP phone on Linux system now. Please visit our website to download the latest version:

For example, you download “miniSIPPhone-x86_64.AppImage” and set right to run it with following command:

chmod +x miniSIPPhone-x86_64.AppImage

Then you can directly run miniSIPPhone:

./miniSIPPhone-x86_64.AppImage

If you want to uninstall miniSIPPhone, delete the AppImage file, that’s all.

If you want to deploy FXS gateways,…

If you want to deploy FXS gateways,…

FXS gateways can help to connect traditional phones to VoIP deamon. The common topology is below. 

VoIP deamon <--> miniSIPServer <--> FXS gateway <--> traditional phone

In normal, one FXS gateway connects to one traditional phone, but some FXS gateways can connect to several phones at the same time. We need to pay attention to this scenario.

The FXS gateway need to bind several SIP users accounts since it can connect to several phones. In another way, the gateway uses one URI address (including IP address and port together) to register these SIP accounts to miniSIPServer. That meas several SIP users will connect to miniSIPServer with the same address.

If one of the users is configured with wrong information, and the gateway keeps sending SIP messages to miniSIPServer, it will trigger ‘fail to ban’ feature, then the gateway’s address will be blocked by miniSIPServer. As we said, since the gateway uses one address to register several SIP users to miniSIPServer, other SIP users will have to be blocked together.

In this scenario, we need to stop ‘fail to ban’ for the gateway. We can add the address of the gateway into white list. Please click menu ‘services – IP address black-white list’ to add a record to accept the IP address. For example:

IP address black-white list
Maximum concurrent calls of local user

Maximum concurrent calls of local user

Previous miniSIPServer versions only limit “maximum concurrent outgoing calls”, and didn’t limit the total concurrent calls. Normally, it can fit most requirements since we think SIP phones or SIP clients should be able to limit their incoming calls. In recent days, some customers response that their SIP phones don’t have enough functions and hope miniSIPServer to be able to limit total concurrent calls of each SIP phone. To fit this requirement, we upgrade miniSIPServer to V34. Please refer to following figure.

Maximum concurrent calls
Maximum concurrent calls

You can configure “maximum concurrent calls” to be zero. In this strange scenario, the SIP phone will never receive call and cannot make any outgoing call. It is to be noted that “maximum concurrent outgoing calls” should be smaller than “maximum concurrent calls” because “maximum concurrent calls” limits both outgoing calls and incoming calls together.