Compiling and Installing Yate on Windows

From Yate Documentation
Revision as of 16:13, 10 January 2013 by Dana (Talk | contribs)

Jump to: navigation, search

There are two ways to install Yate under Windows:

  • Download and install Yate from download page following the setup.
  • The other option is to download Yate from SVN and to compile by yourself.

Contents

Installing Yate using executable file

Installing Yate from SVN

Requirements

Compiling Yate on Windows

To compile please build the "YATE" project - it will build the library and all modules without external dependencies. After taking Yate from SVN ( the URL to use is: http://voip.null.ro/svn/yate/trunk), go to windows\ folder from your "Yate" project where you will find YATE.sln that you have to build in your Visual Studio environment.

The "Extra" project holds modules that have external dependencies. You will not be able to build them without installing extra headers and libraries in your Visual Studio environment:

  • h323chan needs PWLib and OpenH323, you can find more about it in page Installing OpenH323 under Windows;
  • gsmcodec needs a GSM 06.10 static library;
  • Qt4Client needs Qt® and its tools (MOC);
  • mysqldb needs MySQL client headers and libraries;
  • pgsqldb needs PostgreSQL client headers and libraries.

Problems

If you build Yate from sources and Visual Studio crashes or hangs beyond cancellation please clean the build and repeat from scratch. Already compiled object files may be good or may be damaged - just stay on the safe side.

NOTE: Compilation may fail because of WinDNS.h included from engine/Resolver.cpp - in this case you have two options:

  • Install a newer WinDNS.h - for example one from Platform SDK 2008 - NAPTR records will be resolved on any Windows version that provides windns.dll
  • Remove the define HAVE_DNS_NAPTR_DATA from the Libyate project - in this case NAPTR can be resolved only on older versions of Windows and only if they provide windns.dll

Please see the notes at the top of engine/Resolver.cpp for more details.

Run Yate as service on Windows

NOTE: Yate can run as service on Windows as you can see in the screenshot below.

Yate windows service.png

Sangoma card

If you are using a Sangoma card don't forget to first install the motherboard drivers, then Sangoma drivers, and then Yate with Sangoma drivers support. You can find a guide about how to install Sangoma on Windows for Yate. Sangoma drivers can be downloaded from http://www.sangoma.com/windows/drivers/A101_A102_API_WANPIPE/.

Configure Yate

Yate can be configured by edit files from directory conf.d. Each file has a .sample termination. You have to create a a new file with the same name but with .conf.
Each parameter in the files have a section that is in brackets. Comment in this files are done by using ;.
More documentation about what those files should contain can be found modules page.
See more information about how to start Yate on windows.

Adding Users

You'll have to edit regfile.conf to add users.
We are going to add 2 users:user 100 with password 001 and user 200 with password 002 like this:

[100]
password=001
[200]
password=002

There is another way of adding users if you wish to use a database, the file to use is register.conf.

SIP Configuration

The file that is used is ysipchan.conf. No configuration is needed in this file because by default Yate will bind with all the network interfaces on your server on port 5060. If other programs use this port then you have to to use another free port and put it in [general] section.

Routing

There is no need to define any routing for registered SIP users on the machine. Yate will know to route calls between the users defined in regfile.conf.

To define routing to other registered users, PSTN, gateways you need to edit regexroute.conf.
To register users in a database you can use register.conf. And then make your route rules in regexroute.conf.
Here you can read more about routing.

Configure phones and test the setup

You have to configure the users from regfile on two SIP phone (you could use a SIP softphone as well) to call Yate Server.

If Yate was running when you written in configuration file reload Yate so that the changes will take place.

Make a call from one phone to the other and check the audio, if you can here the other end then you may have a NAT problem.

More scenarios on how to configure Yate see in How To's section.


See also

Personal tools
Namespaces

Variants
Actions
Preface
Configuration
Administrators
Developers