A machine with multiple network adapters may need special configuration for use with BladeWare.  This is because even if you have an adapter with an externally visible IP address, Windows may not use it to communicate wit your remote SIP call server.

In the following example, we have used easily recognizable IP numbers: assume your machine has NIC cards as follows:

Card 1: used for general network purposes, remote control, etc.:




Card 2: to be used for SIP calls:

IP:      101.201.301.401


GATEWAY: 101.201.301.254

Assume also that the IP address of your SIP service is

The Problem

Windows is likely to choose your local IP address to communicate with the SIP service.  It can reach the SIP service, but the SIP service will not be able to reply to the local IP address through Network Address Translation (NAT).  In summary:     -->   REACHABLE

101.201.301.401  -->   REACHABLE  -->      NOT REACHABLE  -->  101.201.301.401   REACHABLE

BladeWare FoIP will therefore not work if Windows has made the outbound connection via the adapter.

The Solution

First, try making the following adjustment to the static routing in Windows.  In a command session (DOS box) enter the commands (of course use your own real IP address numbers):

route add  mask  metric 1

route add  mask  101.201.301.401  metric 9999

in other words:

route add sipserverip mask localip metric 1

route add sipserverip mask visibleip metric 9999

To verify that the change has had the intended effect, try a ping to the SIP server with Wireshark running or do a tracert.

These routes will only remain in effect until the computer is rebooted.  To make them permanent, re-do the commands with a -p option added immediately after the command name:

route -p add sipserverip mask localip metric 1

route -p add sipserverip mask visibleip metric 9999

If you need to adjust routes further, there is a route delete command that can remove routes.