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

 

2 thoughts on “sip trunk

  1. I have installed OnSIP Tapi driver, as I would like to make my calls direct from Outlook. How to configure this, to get it working with miniSipServer.

    1. Hi,

      i am not familiar with OnSIP Tapi driver. If it requires TAPI from SIP server, MSS cannot support it. If it just transfer TAPI to normal SIP messages or process, it should be no different with normal SIP phones or SIP trunks for MSS.

Comments are closed.

Comments are closed.