0.9.x
#
# $Id: seri.cfg,v 1.42 2007/05/30 12:28:17 tirpi Exp $ # # First start SERi sample config script with: # database, accounting, authentication, multi-domain support # PSTNi GW section, named flags, named routes, global-, # domain- and user-preferences with AVPs # Several of these features are only here for demonstration purpose # what can be achieved with the SER config script language. # # If you look for a simpler version with a lot less dependencies # please refer to the ser-basic.cfg file in your SER distribution. There are many ways to good performance for networking-based software. SERi performs with a large number of subscribers on a single server, sufficient for most installations. And using various techniques building a SIP network architecture, you can make SER scale to an unlimited number of subscribers. However, we want SER's core and core modules to be based on sound design principles and architected with performance in mind. These components are used by everybody, from the simplest seri.cfg for proxying large number of call per second to the small "home-grown" setup with a huge ser.cfg executing all kinds of logic for every single message. 0.9.x xlog module backported by Juha The backported modules: 0.9.0 example tables: mysql> select * from gw;
2 rows in set (0.01 sec) mysql> select * from lcr; Sample of ser.cfg # rogerles LCR ser.cfg # # ----------- global configuration parameters ------------------------ # debug=9 # debug level (cmd line: -dddddddddd) # fork=yes log_stderror=yes# (cmd line: -E) check_via=no # (cmd. line: -v) dns=no # (cmd. line: -r) rev_dns=no # (cmd. line: -R) listen=64.201.13.52 port=5060 children=4 # fifo="/tmp/ser_fifo" # # # ------------------ module loading ---------------------------------- # loadmodule "/usr/local/lib/ser/modules/mysql.so" loadmodule "/usr/local/lib/ser/modules/nathelper.so" loadmodule "/usr/local/lib/ser/modules/sl.so" 0.9.0 OSP Module enables SER to use the OSP Peering Protocol for secure Authorization, Routing and Accounting of IP communication sessions. OSP is an ETSI protocol, Technical Specification 101 321. Note!! OSP module has been moved into main modules directory in SER 2.0 Ottendorf (release after 0.9.x) More details on the OSP module from : Download the module from : http://developer.berlios.de/projects/osp-module/ 0.9.x The Swiss Federal Institute of Technology (ETH) has developed some useful modules to SER under the 'ETH World' program which came to an end in 2005. The project has been inspired by the Internet2 SIP.edu initiative. The SERi modules developed were: ldap Moduleldaps Modulesilomail Moduleethz ModuleMore details of the modules and links to download them can be found from the following link : http://www.ethworld.ethz.ch/technologies/sipeth/ser_modules 0.9.x LCR module for 0.9.x with database tables etc. This is the code found in the experimental code tree. Full functioning and mature. Just drop the lcr directory into the modules directory of 0.9.x and make as always. See README.DB for database table. A PHP cli script ip2long is included for converting IP addresses to the the long int required by LCR. 0.9.7-pre4 (probably all 0.9.x) NAThelper patch from Portaone that enables the ping functionality in nathelper to send SIP message (i.e. OPTIONS) instead of 4-byte UDP packets. This is useful for NATs that ignore ping keepalives from the outside as the user agent will answer the OPTIONS packet with OK (or 404 Not found etc dependent on support for OPTIONS). Save the patchfile to modules/nathelper directory, then (having that directory as current) use the command 'patch -p1 < nathelper_ping.patch' OBS! You also need to edit the parser/parse_hostport.c file and remove the #ifdef _OBSOLETED and #endif around the parse_hostport() function. Add this to your seri.cfg to enable OPTIONS messages to the UAs as keepalives: You will see a lot 'No UACi support' warning messages in your log. These are harmless and are caused by replies to the OPTIONS message and SERi detects (correctly) these messages as originated from SER (as UAC). You can remove the warnings by commenting out in modules/tm/t_reply.c in run_failure_handler(): /* failure_route for a local UAC? */ |
Navigation |