#OPENSER XLOG INSTALL#
#OPENSER XLOG PLUS#

Loadmodule '/usr/local/lib/openser/modules/speeddial.so' Loadmodule '/usr/local/lib/openser/modules/uac.so' Loadmodule '/usr/local/lib/openser/modules/xlog.so' Loadmodule '/usr/local/lib/openser/modules/domain.so' Loadmodule '/usr/local/lib/openser/modules/textops.so' Loadmodule '/usr/local/lib/openser/modules/nathelper.so'

Loadmodule '/usr/local/lib/openser/modules/mediaproxy.so' Loadmodule '/usr/local/lib/openser/modules/uri_db.so' Loadmodule '/usr/local/lib/openser/modules/uri.so' Loadmodule '/usr/local/lib/openser/modules/auth_db.so' Loadmodule '/usr/local/lib/openser/modules/auth.so' Loadmodule '/usr/local/lib/openser/modules/registrar.so' Loadmodule '/usr/local/lib/openser/modules/usrloc.so' Loadmodule '/usr/local/lib/openser/modules/maxfwd.so' Loadmodule '/usr/local/lib/openser/modules/rr.so' Loadmodule '/usr/local/lib/openser/modules/tm.so' Loadmodule '/usr/local/lib/openser/modules/sl.so' Loadmodule '/usr/local/lib/openser/modules/mysql.so' Remember to provide valid database information. In fact, I haven't found a really good reason for OpenSER to need to know about DNS define the FIFOs that OpenSER will use to communicate on. Only enable the looking up of DNS if you really need it. If you really start to scale up your OpenSER instance you will want to bump this value up, but remember each additional thread takes more memory so there is somewhat of a trade off - performance versus memory usage.ĭisabling the looking up up DNS is the most scalable option. 4 seems to be a reasonable default for most systems. The children directive informs OpenSER of how many 'child' threads to keep around to process incoming messages. The next 3 inform OpenSER which interface and tcp/dup ports to listen on. However to start OpenSER using openserctl you will need to set fork=yes and log_stderror=no. By not forking and logging to STDERR one can run openser directly to gather information about an invalid configuration directive or perhaps why a specific module isn't loading as expected. Those three options set the stage for how OpenSER will act and function. The default OpenSER configuration file is /usr/local/etc/openser/openser.cfg

#OPENSER XLOG INSTALL#

The OpenSER make install process should do this for you, but as of v1.1.1 this did not happen for me.įinally we can dive into the configuration of OpenSER. Proxy:# cp openserctl.mysql /usr/local/lib/openser/openserctl/ Next copy the file 'openserctl.mysql' from the scripts directory into /usr/local/lib/openser/openserctl/ directory This will create the 'openser' database, tables and required initial data. Once you have MySQL running you need to find the 'mysqldb.sh' script located in the scripts directory inside of the OpenSER v1.1.1 tarball. You also must setup an instance of MySQL and allow OpenSER to communicate with it (MySQL can very easily run on the same machine) I will use 'openser' as the username and 'valid_pass' as the password. The IP Address for this configuration will be 1.2.3.4, of course you will need to replace this with your own IP address. (The other option being the older RTPProxy method)

#OPENSER XLOG PLUS#

Plus we will overcome most NAT situations that many home and small business level deployments will encounter, using the MediaProxy option. This configuration will utilize the necessary modules and configuration directives of OpenSER to create a SIP Registrar, conditionally detect and route based on the dialed URI (digits). Although v1.2 has been released, I am going to let others find and kill the lingering bugs before diving in myself. I am basing this configuration on OpenSER v1.1.1 which is currently considered the most 'stable' version. However unlike Asterisk, OpenSER requires extensive knowledge of the SIP Protocol and presumes nothing about your configuration or method of deployment. OpenSER is a flexible, mature and stable SIP communications server.

Openser xlog