Tips on working with X-Lite and SailFin
X-Lite configuration is where users commonly make mistakes while using sailfin. Here are some tips that I use while using X-Lite. Remember, this
is not a guide to using X-Lite with any VOIP provider, but these are tips to use X-Lite with a SIP application server like SailFin for trying out
sample applications, testing your sip application etc. Most of these are very simple, but still.....
1. Configuring two X-Lite instances in the same machine
This one is really simple. X-Lite keep some configuration files in the user's home directory. That means, running two X-Lite's with different accounts
in the same machine wouldnt work. So, I create different users in my MacBook and run X-lite on those different accounts from the terminal
window so that preferences dont get overridden. I guess the same would work on any *nix platform.
2. Configuring an account
Lets take an example, where you need to configure a user called firstname.lastname@example.org and want to register the user against the server running
on 127.0.0.1. The configuration would look similar to the one in the picture above. X-Lite would create the sip user name as user@domain (i.e email@example.com).
Now, sailfin is not really running on example.com. So, we have configured the proxy to where sailfin is running (i.e 127.0.0.1). X-Lite will connect to port 5060 (default SIP port)
on 127.0.0.1. If sailfin is running on a different port, configure the proxy as 127.0.0.1:sailfinportnumber (eg: 127.0.0.1:3220).
IMPORTANT: Configure the correct IP address, instead of 127.0.0.1, if sailfin is running in some other machine.
3. Configuring the network topology for a local testing environment
Network topology screen is used for configuring network traversal. But, if you are testing sailfin in a local environment, then, network traversal is not required. So, do not configure the option to discover global address.