V6.5 has been upgraded to support “speed dialing” feature.
In fact, previous versions can also support “speed dialing” feature by using “dial plan” functions. To do that, customers need make configurations with several tables, it could be difficult. With the new version, we separate a independent table to configure “speed dial” and it is so easy to support it.
Please refer to our document for more details about this feature:
http://www.myvoipapp.com/docs/mss_services/speed-dial/index.html
miniSipServer is upgraded to V6.5 to support different IVR for different incoming calls.
It is very easy to configure MSS to do that, please refer to online document:
http://www.myvoipapp.com/docs/mss_services/auto_attendant/index.html#multi-ivr
For example, if we want to trigger different IVR for another external line (such as “1234″), we can configure the “IVR services” with following record:
dial plan = default Called number = 1234 <--This is the external line name/account IVR-XML file name = aa2.xml <--your own IVR-XML file
miniSipServer is upgraded today to support “call recording” feature. This feature can be used to record local user’s audio stream.
Please refer to following service document:
http://www.myvoipapp.com/docs/mss_services/call-recording/index.html
This year, we provide simple-oem plan for our customers.
More and more customers ask us to provide a OEM product to integrate with their products. Then, they could provide a VoIP total solution to their final customers. They also hope to have their own product price, and so on.
This plan is used to fit such requirements. We hope most partners can benefit from our plan.
Please refer to following document for details about this plan:
Some customers often ask us how to run miniSipServer as windows service?
It is a interesting topic. After research, we think it is very reasonable to run miniSipServer as windows service. For example, the server could be reboot for some exception, so administrator hope miniSipServer can auto-start together and GUI is unnecessary once the IP-PBX has been configured successfully.
With the release of version 6.2.1, our customers can run miniSipServer as windows service now.
After install new miniSipServer, we can find a new exe file whose name is ‘msscli.exe’. It is a command line application without GUI interface. In fact, ‘msscli.exe’ has the same SIP server core with ‘mss.exe’ which is the GUI version.
In another way, we need ‘sc.exe’ command to create windows service. ‘sc.exe’ is widows own application.
We assume that miniSipServer is installed in directory ‘d:\myvoipapp\minisipserver’, then we can begin now:
To create a windows service:
sc create minisipserver binPath= "d:\myvoipapp\miniSipServer\msscli.exe" start= auto depend= tcpip
Note: the option name includes equal sign and blank space sign. We can use miniSipServer web management system to administrate MSS. Please refer to following document for details.
http://www.myvoipapp.com/docs/mss_services/web_management/index.html
BTW, If run as windows service, the web management system will always start-up even without administrator password.
To start miniSipServer service:
sc start minisipserver
To stop miniSipServer service:
sc stop minisipserver
To delete miniSipServer service:
sc delete minisipserver
We need mention that you MUST stop and delete miniSipServer service firstly if you want to install or upgrade a new miniSipServer version.
If you have tried miniSipServer on Windows platform, you can find it is so easy to configure or manage a IP-PBX because miniSipServer provides a perfect GUI interface.
You can find it is very easy to do that on Ubuntu/Linux because miniSipServer can support GUI interface on Ubuntu/Linux now! WINE is unnecessary now!
Please visit our download page to download miniSipServer .deb packages according to your requirements:
http://www.myvoipapp.com/download
After you download .deb file from our website, please click (or double-click) it to install MSS. No more actions! So easy, so funny.
After you finish your install, you will find miniSipServer at “Applications / Internet” group.
Following figure is a screenshot of MSS running on Kubuntu:
MSS main windows on Kubuntu
In another way, if you just want to run a command line sip server, you can also go to directory “/opt/sipserver” and find “msscli” which is a command-line miniSipServer and has the same core with GUI-miniSipServer. You can manage and configure it through web interface.
Sometimes, we need limit the call right of some extensions. For example, we want to limit only specific extensions can make out-group calls to outsides, others can only make calls between extensions.
In MSS, we use “call level” feature to do it. By default, we don’t assign “call level” to any called number prefix in “analyze called number” table. That means all extensions can have the same right. To limit extensions, we should indicatedifferent “call level” to the called number prefix and assign relative “call level” right to special extensions, then they will have the right to make such calls.
For example, the default out-group call prefix is “9″. Please click menu “Dial plan / Analyze called number” and edit or add a record whose prefix is “9″ and route type is “external line”. In this configuration, we can select “call level 1″ to this prefix “9″.
Then, please click menu “data / local users” and edit or add a local user. In the pop-up dialog, please click “Basic Call” tab and enable “Call level 1″ to this extension.
After that, the extension has the “call level 1″ right to make calls to outside by dialing “9xxxxx”. For others, since they don’t have “call level 1″ right, their calls will be rejected when they dial “9xxxxx”.
By default, incoming calls from external lines will be routed to local users or auto-attendants.
But in some deployment, customers require that incoming call from external lines should be routed to hunting-group. Then local users can answer the incoming calls in round-robin order.
It is very easy to do that in MSS. Do you remember that we need configure a called number to trigger hunting-group, right? In this table, you only need configure it with external line number.
For example, external line is “1234567″, then in the “hunting group detection” configuration, we only need configure detection called number to be “1234567″ to trigger hunting-group.
miniSipServer V6 is upgraded to V6.1.3. This version can support SIP INFO message to transport DTMF signals.
Some VoIP carriers’ servers or VoIP gateway can only support this INFO message to transport DTMF signals which are very necessary for IVR services, such as auto-attendant.
There are several content type in INFO message to transfer DTMF. MSS can support “application/dtmf-relay” content type.
Now, MSS can support INFO and RFC2833 for DTMF signals.
MSS IVR-XML document is released. This document describes details about MSS IVR-XML, includes structure, XML elements, action definitions, and so on.
We hope this document can help you to understand IVR-XML and write your own IVR process.
Please visit following URL to read the document:
http://www.myvoipapp.com/docs/mss_services/IVR-XML/index.html