TekSIP Route Server System Requirements

  • A Windows system with at least 2 GB of RAM.
  • Microsoft.NET Framework 4.0 Client Profile (Min.)
  • 10 MBytes of disk space for installation.

Installing and Uninstalling

To install TSRServer, extract contents of TSRServer.zip to a temporary directory, run Setup.exe from the distribution. Uninstall previous version if you upgrade from an earlier version

To uninstall TSRServer, double click TSRServer icon at "Add or Remove Programs" from Control Panel.


Click here to download TSRServer.


Please see Installation Manual which can be found in the application directory for configuration details and operation;

  1. Run TekSIP Route Server Manager from Start Menu / Program Files / TekSIP Route Server.
  2. You can define resource records or routes for a particular E.164 number or a prefix in "Routing" tab. Enter a phone number prefix to bottom leftmost textbox and click "Add Route" button. You must edit at least URI entry to commit changes.

    You can have also a default route entry. TekSIP Route Server chooses longest match prefix route. If any match can not be found default route is chosen if exists.
  3. Select IP address to be listened on the settings tab. Logging is optional. TSRServer can cache query results for a period of time defined in Cache Refresh Period parameter. Check if you wish to enable this feature. TSRServer can also perform ENUM queries for undefined number/prefiexes. If you save or apply the configurations changes, they take effect immediately.
  4. You can configure database setting in Settings / Database tab. SQL database and table will be automatically created if your SQL user has enough priviledge.
  5. Number Portability Application

    TekSIP Route Server can be deployed as route server for Local or Mobile Number Portability applications. TekSIP Route Server is located between session border controller which provides interface to interconnecting carriers and end users, and operator’s NGN network. Calls are routed TekSIP Route Server first, and if the number is ported to another operator a SIP 302 response which contains prefix of the host operator of the ported number will be sent to originating SBC.

    If called number is not ported, NP Server will reply with a SIP 302 response which contains prefix of the home operator of the called number will be sent to originating SBC. SBC will route the call to the number specified in Contact header of SIP 302 response.

    Typical SBC configuration is shown below (Cisco):

    dial-peer voice 10 voip
     description -- Outgoing 1 --
     destination-pattern 05T
     session protocol sipv2
     preference 1
     session target ipv4::5060
    dial-peer voice 20 voip
     description -- Outgoing 2 --
    ! for Carriers
    ! destination-pattern T
     destination-pattern .+
     session protocol sipv2
     session target ipv4::5060
    Dial-Peer 10 forwards calls to TekSIP Route Server and Dial Peer 20 routes calls to Softswitch according to the TekSIP Route Server response.

Follow us