Browsed by
Tag: sip server

Simple-OEM plan

Simple-OEM plan

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:

http://www.myvoipapp.com/resellers/simple-oem/index.html

How to send instand messages between SIP servers

How to send instand messages between SIP servers

One of our customer has two office branch in different cities and two MSS have been deployed. Following figure describe the network topology:

Network topology

The extensions of MSS1 are 1xx, such as 100,101, and so on.

The extensions of MSS2 are 2xx, such as 200, 201, and so on.

With previous MSS versions, it is no problem to send/receive instant messages between local users. But it cannot send instant messages to the extensions of another SIP server.

So we upgrade MSS to V6.1.5 to support instant messages between SIP servers.

To do that, we need establish SIP trunk between these SIP servers. Once you can make calls to the extensions of another SIP server (MSS), it will be no problem to send instant messages to them.

That means we need configure MSS with (1) peer server configurations, (2) Dial plan configurations which we have described in “how to use SIP trunk” document. Please refer to following document for details of SIP trunk:

http://www.myvoipapp.com/blog/2011/05/02/sip-trunk/

 

Stable versions are upgraded to V3.1.2

Stable versions are upgraded to V3.1.2

In this new version, following features are updated:

1. For FXO external lines, the max simultaneous call is limited to 1 by default.

2. The install package is updated to remove previous installed version automatically when installing the new version in the same directory.

V4.0 is coming ……

V4.0 is coming ……

MSS V4.0 is coming….It is a very important version for our customers. The most important feature of this version is to support Linux!

Yes! It is true! MSS V4.0 can run on Ubuntu/Kubuntu system without WINE now! MSS will be a cross-platform SIP|VOIP server.

The development work is finished and we are still working on system test. We hope to release this version in the end of this month or the beginning of next month.

 

sip trunk

sip trunk

In VOIP depolyment, “SIP trunk” is often used to establish a connection with peer sip servers or gateways. For example, in most DID services deployments, SIP trunk is required to send or receive DID calls.

The difference between “SIP trunk” and “External lines” is that SIP trunk doesn’t require authorization during the call. That means, “external line” is server-to-users mode and “SIP trunk” is a server-to-server mode.

It is very easy to establish SIP trunk in MSS.

For example, we want to establish SIP trunk with peer server whose domain name is “sip.demo.com” and its SIP port is 5060 which is a default SIP UDP port.

step 1: add the server into MSS servers list

Please click menu “data / peer servers” and add a new record with following information:

peer server id=1
description = demo sip server
server address = sip.demo.com
server port  = 5060

step 2: process incoming call

Once we receive incoming calls from peer servers, we want to route them to local users. We can use “dial plan” to do that.

For example, we want the DID incoming calls whose called numbers prefix is “1234” to local users, such as 1234100 to local user 100, 1234101 to local user 101, etc.

Please click menu “dial plan / transition” to configure a number transition:

transition ID = 1
transition type = delete
start position = 0
length = 4

Please click menu “dial plan / analysis called number” to configure a record to route DID numbers to local users:

dial plan = default
called number prefix = 1234
route type = local user
change called number = yes
transition id = 1

step 3: process outgoing call

We want our outgoing calls to be routed to such peer SIP server/gateway. We still need configure “dial plan” to do that.

For example, we want all calls whose called number prefix is “00” should be routed to such SIP server, such as “008613800138000”, etc.

Please click menu “dial plan / analysis called number” to add a new record with following information:

dial plan = default
called number prefix = 00
route type = SIP trunk
peer server ID = 1

 

Can I get a free license?

Can I get a free license?

miniSipServer is free for some communities or persons. Please refer to following description for details.

Community

miniSipServer is free for use by official non-profit organisations and charities (proof of non-profit status is required). There are certain organisations whose purpose is to make the world a better place, and we believe in helping them achieve that.

The free license is designed for organisations which are:

  • non-profit
  • non-government
  • non-academic
  • non-commercial
  • non-political and
  • secular

If your organisation is philanthropic in nature, then you probably qualify.

To apply for a free license, send us (support(a)myvoipapp.com) an email specifying the following information:

  • The registered name of your organization.
  • Your organization’s URL
  • A short description of your organization

Open source

MyVoipApp supports and believes in the Open Source movement. miniSipServer is free for any Open Source project to use.

There are a few requirements for an Open Source license, the main ones being:

  • Established code base
  • Publicly available project website
  • Using an approved open source license
  • Your Confluence instance will be publicly accessible

To apply for an Open Source License, send us (support(a)myvoipapp.com) an email specifying the following information:

  • Project Name
  • Project URL – Your project must have a public URL
  • Project Description – Please outline the goals of your project and its intended users.
  • Confluence Instance URL
  • Open Source License(s) used – Licenses must be on the list of licenses approved by the Open Source Initiative at http://opensource.org/licenses/alphabetical
  • Where can we download your source code?