<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://www.iptel.org">
<channel>
 <title>iptel.org - Component</title>
 <link>http://www.iptel.org/taxonomy/term/152/9</link>
 <description>SER component.</description>
 <language>en</language>
<item>
 <title>eval</title>
 <link>http://www.iptel.org/eval</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-8&quot;&gt;&lt;div class=&quot;flexinode-select-34&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Module status:&lt;/label&gt;&lt;br /&gt;
 Standard
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-35&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Description:&lt;/label&gt;&lt;br /&gt;
  Eval module ===========  Author: tomas.mandys at iptel dot org  The module implements expression evaluation in route script, i.e. enables e.g. addition, concatanation, value items etc. There are two basic types: integer and string. Operation are processed using values on stack and polish notation. Besides the stack there are also register that may be accessed by quick manner in run time, via select or stack manipulation functions, because they are fixed during fixup phase.  This depends on libuuid shared library.  Module parameters: -----------------  declare_register: string;  Declares one register, multiple declaration supported  Example:   modparam(&amp;quot;eval&amp;quot;, &amp;quot;declare_register&amp;quot;, &amp;quot;ax&amp;quot;);   modparam(&amp;quot;eval&amp;quot;, &amp;quot;declare_register&amp;quot;, &amp;quot;bx&amp;quot;);   modparam(&amp;quot;eval&amp;quot;, &amp;quot;declare_register&amp;quot;, &amp;quot;cx&amp;quot;);   modparam(&amp;quot;eval&amp;quot;, &amp;quot;declare_register&amp;quot;, &amp;quot;dx&amp;quot;);  xlbuf_size: int; Default: 4096  Size of buffer for xlib formating.
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser_version/0_10_x">2.0.x</category>
 <category domain="http://www.iptel.org/ser/component/module/eval">eval</category>
 <category domain="http://www.iptel.org/doc/man_page">Man page</category>
 <pubDate>Mon, 11 Feb 2008 17:22:04 +0100</pubDate>
</item>
<item>
 <title>auth_identity</title>
 <link>http://www.iptel.org/auth_identity_0</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-8&quot;&gt;&lt;div class=&quot;flexinode-select-34&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Module status:&lt;/label&gt;&lt;br /&gt;
 Standard
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-35&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Description:&lt;/label&gt;&lt;br /&gt;
  This module contains functions that are used for Enhancements&lt;strong&gt; &lt;/strong&gt;for&lt;strong&gt; &lt;/strong&gt;Authenticated Identity Management in SIP (defined by RFC4474). The purpose of this mechanism is securely identifying originators of SIP requests and providing integrity protection of the message, especially in an interdomain context. 
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser/component/module/auth_identity">auth_identity</category>
 <category domain="http://www.iptel.org/doc/module">Module</category>
 <category domain="http://www.iptel.org/ser_release/2_1_x">2.1.x</category>
 <pubDate>Mon, 10 Dec 2007 15:37:18 +0100</pubDate>
</item>
<item>
 <title>Standard ser.cfg</title>
 <link>http://www.iptel.org/file_standard</link>
 <description> #&lt;br /&gt; # $Id: ser&lt;a href=&quot;glossary/term/244&quot; title=&quot;SER: SIP Express Router, fast and flexible SIP server.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt;.cfg,v 1.42 2007/05/30 12:28:17 tirpi Exp $&lt;br /&gt; #&lt;br /&gt; &lt;br /&gt; # First start SER&lt;a href=&quot;glossary/term/244&quot; title=&quot;SER: SIP Express Router, fast and flexible SIP server.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt; sample config script with:&lt;br /&gt; #&amp;nbsp;&amp;nbsp; database, accounting, authentication, multi-domain support&lt;br /&gt; #&amp;nbsp;&amp;nbsp; PSTN&lt;a href=&quot;glossary#term218&quot; title=&quot;PSTN: Public Switched Telephone Network&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt; GW section, named flags, named routes, global-,&lt;br /&gt; #&amp;nbsp;&amp;nbsp; domain- and user-preferences with AVPs&lt;br /&gt; # Several of these features are only here for demonstration purpose&lt;br /&gt; # what can be achieved with the SER config script language.&lt;br /&gt; #&lt;br /&gt; # If you look for a simpler version with a lot less dependencies&lt;br /&gt; # please refer to the ser-basic.cfg file in your SER distribution. </description>
 <category domain="http://www.iptel.org/ser_version/0_9_x">0.9.x</category>
 <category domain="http://www.iptel.org/doc/book">Book</category>
 <category domain="http://www.iptel.org/news/ser/development">Development</category>
 <category domain="http://www.iptel.org/ser/component/module/domain">domain</category>
 <category domain="http://www.iptel.org/administration/site">Site</category>
 <category domain="http://www.iptel.org/protocol/ssl">SSL</category>
 <category domain="http://www.iptel.org/glossary/sip/stateless">stateless</category>
 <pubDate>Wed, 17 Oct 2007 08:44:53 +0200</pubDate>
</item>
<item>
 <title>Why does my MySQL 5.0.X connection time out when using SER 0.9.X? </title>
 <link>http://www.iptel.org/faq/why_does_my_mysql_5_0_x_connection_time_out_when_using_ser_0_9_x</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-3&quot;&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser/component/module/mysql">mysql</category>
 <pubDate>Thu, 24 May 2007 14:27:24 +0200</pubDate>
</item>
<item>
 <title>tls</title>
 <link>http://www.iptel.org/ser/doc/modules/tls</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-8&quot;&gt;&lt;div class=&quot;flexinode-select-34&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Module status:&lt;/label&gt;&lt;br /&gt;
 Standard-dep
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-35&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Description:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;This module implements the TLS transport for ser&lt;a href=&quot;glossary/term/244&quot; title=&quot;SER: SIP Express Router, fast and flexible SIP server.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt; using the openssl library (&lt;a href=&quot;http://www.openssl.org&quot;&gt;http://www.openssl.org&lt;/a&gt;). To enable the TLS support this module must be loaded and enable_tls=yes must be added to the ser config file.&lt;/p&gt;
 
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-36&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Maintainers:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;Andrei Pelinescu-Onciul&lt;/p&gt;
 
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser_version/0_10_x">2.0.x</category>
 <category domain="http://www.iptel.org/doc/module">Module</category>
 <category domain="http://www.iptel.org/ser/component/module/tls">tls</category>
 <pubDate>Wed, 21 Feb 2007 12:17:33 +0100</pubDate>
</item>
<item>
 <title>Sequential Call Hunting using AVPs</title>
 <link>http://www.iptel.org/howto/sequential_call_hunting_using_avps</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-4&quot;&gt;&lt;div class=&quot;flexinode-textarea-26&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Short description:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;&amp;nbsp;&lt;/p&gt;&lt;p&gt;Call Hunting is a mechanism by which a proxy server trys to place a call to any one number (user) in a list of numbers. The proxy tries each number in sequence until a number answers (200 OK) or all numbers are exhausted. In this example the call will be forwarded to the voice mail mailbox associated with the original called number when all numbers have been exhausted.&lt;br /&gt;&lt;br /&gt;&lt;/p&gt;&lt;p&gt;This&amp;nbsp; example was created for a proxy running SER&lt;a href=&quot;glossary/term/244&quot; title=&quot;SER: SIP Express Router, fast and flexible SIP server.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt;  0.9.x&lt;/p&gt;&lt;p&gt;&amp;nbsp;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-27&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Steps:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;&amp;nbsp;&lt;br /&gt;Setup:&lt;/p&gt;&lt;p&gt;In this example I use MySQL for the data storage. The database also stores registrations, subscriber data and locally defined call feature/call permission flags. To enable the call hunting feature we will need a new table. &lt;/p&gt;&lt;p&gt;MySQL setup:&lt;/p&gt;&lt;p&gt;We create a new table for Single Attribute Multi-value data storage. We&#039;ll call this table &amp;quot;sam&amp;quot;.&lt;/p&gt;&lt;p&gt;#&lt;br /&gt;# Table structure for table &#039;sam&#039; Single Attribute Multi-value&lt;br /&gt;#&lt;br /&gt;&lt;br /&gt;DROP TABLE IF EXISTS `sam`;&lt;br /&gt;CREATE TABLE `sam` (&lt;br /&gt;&amp;nbsp; `uuid` varchar(64) NOT NULL default &#039;&#039;,&lt;br /&gt;&amp;nbsp; `username` varchar(100) NOT NULL default &#039;0&#039;,&lt;br /&gt;&amp;nbsp; `domain` varchar(128) NOT NULL default &#039;&#039;,&lt;br /&gt;&amp;nbsp; `attribute` varchar(32) NOT NULL default &#039;&#039;,&lt;br /&gt;&amp;nbsp; `value` varchar(128) NOT NULL default &#039;&#039;,&lt;br /&gt;&amp;nbsp; `type` int(11) NOT NULL default &#039;0&#039;,&lt;br /&gt;&amp;nbsp; `modified` timestamp NOT NULL default CURRENT_TIMESTAMP on update CURRENT_TIMESTAMP&lt;br /&gt;) ENGINE=MyISAM DEFAULT CHARSET=latin1;&lt;br /&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser/component/module/avp">avp</category>
 <pubDate>Sun, 04 Feb 2007 11:28:36 +0100</pubDate>
</item>
<item>
 <title>LDAP and LDAP authentication modules</title>
 <link>http://www.iptel.org/ldap_and_ldap_authentication_modules</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-7&quot;&gt;&lt;div class=&quot;flexinode-textfield-31&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Applies to version:&lt;/label&gt;&lt;br /&gt;
 SER CVS as off January 18, 2007
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-32&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Description:&lt;/label&gt;&lt;br /&gt;
  Generic LDAP&lt;a href=&quot;glossary#term185&quot; title=&quot;LDAP: Lightweight Directory Access Protocol&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt; module that handles connection to the ldap server and exports a simple API to interact with the server. Also, a LDAP authentication module that uses the API exported from the generic LDAP module.&lt;br /&gt; 
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-33&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Instructions for use:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;Save the patchfile to the directory with the file to patch, then (having that directory as current) use the command &#039;patch -p0 &amp;lt; patchfile.txt&#039;&lt;/p&gt;&lt;p&gt;LDAP&lt;a href=&quot;glossary#term185&quot; title=&quot;LDAP: Lightweight Directory Access Protocol&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt; module configuration:&lt;/p&gt;&lt;p&gt;modparam(&amp;quot;ldap&amp;quot;, &amp;quot;ldap_version&amp;quot;, 3) &amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;= optional, possible values are 1, 2 or 3&lt;br /&gt;&lt;/p&gt;&lt;p&gt;modparam(&amp;quot;ldap&amp;quot;, &amp;quot;ldap_url&amp;quot;, &amp;quot;ldap://localhost:389&amp;quot;)&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; &amp;lt;== optional, defaults to &amp;quot;ldap://localhost&amp;quot;, ldaps connections require ldap_version &amp;gt;= 2&lt;br /&gt;&lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser_version/0_10_x">2.0.x</category>
 <category domain="http://www.iptel.org/ser/component/module">module</category>
 <enclosure url="http://www.iptel.org/files/ldap.patch" length="52046" type="application/octet-stream" />
 <pubDate>Fri, 19 Jan 2007 06:39:45 +0100</pubDate>
</item>
<item>
 <title>xcap</title>
 <link>http://www.iptel.org/ser/doc/modules/xcap</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-8&quot;&gt;&lt;div class=&quot;flexinode-select-34&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Module status:&lt;/label&gt;&lt;br /&gt;
 Standard-dep
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-35&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Description:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;Module for doing XCAP queries.&lt;/p&gt;
&lt;p&gt;This module covers functions called internaly to access XCAP server. These functions were separated into standalone module to allow simple replacing XCAP queries with queries into database or local filesystem or whatever else. Next reason was to protect other modules from linking with libcurl (implements HTTP) or other such stuff.&lt;/p&gt;
 
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser_version/0_10_x">2.0.x</category>
 <category domain="http://www.iptel.org/doc/module">Module</category>
 <category domain="http://www.iptel.org/ser/component/module/xcap">xcap</category>
 <pubDate>Sun, 14 Jan 2007 15:52:26 +0100</pubDate>
</item>
<item>
 <title>uri_radius</title>
 <link>http://www.iptel.org/ser/doc/modules/uri_radius</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-8&quot;&gt;&lt;div class=&quot;flexinode-select-34&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Module status:&lt;/label&gt;&lt;br /&gt;
 Standard-dep
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-35&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Description:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;URI&lt;a href=&quot;glossary#term81&quot; title=&quot;URI: Uniform Resource Identifier. A string representing a resource in the Internet.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt; check using Radius server.&lt;/p&gt;
 
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-36&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Maintainers:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;Juha Heinanen&lt;/p&gt;
 
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser_version/0_10_x">2.0.x</category>
 <category domain="http://www.iptel.org/doc/man_page">Man page</category>
 <category domain="http://www.iptel.org/ser/component/module/uri_radius">uri_radius</category>
 <pubDate>Sun, 14 Jan 2007 15:50:08 +0100</pubDate>
</item>
<item>
 <title>rls</title>
 <link>http://www.iptel.org/ser/doc/modules/rls</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-8&quot;&gt;&lt;div class=&quot;flexinode-select-34&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Module status:&lt;/label&gt;&lt;br /&gt;
 Standard-dep
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-35&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Description:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;Resource lists server is a server which allows subscriptions to lists of users. Its behaviour is defined in [rls] and [sip rls]. As described there, it uses XCAP server for storing data about lists of users. These data can be manipulated in any way by user&#039;s client software.&lt;/p&gt;
 
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser_version/0_10_x">2.0.x</category>
 <category domain="http://www.iptel.org/doc/module">Module</category>
 <category domain="http://www.iptel.org/ser/component/module/rls">rls</category>
 <pubDate>Sun, 14 Jan 2007 15:48:13 +0100</pubDate>
</item>
<item>
 <title>pa</title>
 <link>http://www.iptel.org/ser/doc/modules/pa</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-8&quot;&gt;&lt;div class=&quot;flexinode-select-34&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Module status:&lt;/label&gt;&lt;br /&gt;
 Standard-dep
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-35&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Description:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;This module implements a presence server, i.e. entity that receives SUBSCRIBE requests and sends NOTIFY when presence status of a user changes and allows user to use PUBLISH request for publishing presence status information.&lt;/p&gt;
 
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser_version/0_10_x">2.0.x</category>
 <category domain="http://www.iptel.org/doc/module">Module</category>
 <category domain="http://www.iptel.org/ser/component/module/pa">pa</category>
 <pubDate>Sun, 14 Jan 2007 15:43:55 +0100</pubDate>
</item>
<item>
 <title>osp</title>
 <link>http://www.iptel.org/ser/doc/modules/osp</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-8&quot;&gt;&lt;div class=&quot;flexinode-select-34&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Module status:&lt;/label&gt;&lt;br /&gt;
 Stable
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-35&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Description:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;The osp module enables SER&lt;a href=&quot;glossary/term/244&quot; title=&quot;SER: SIP Express Router, fast and flexible SIP server.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt; to support secure, multi-lateral peering using the OSP standard defined by European Telecommunications Standards Institute (ETSI&lt;a href=&quot;glossary#term173&quot; title=&quot;ETSI: European Telecommunications Standards Institute&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt;) (TS 101 321 V4.1.1). Open Settlement Protocol uses Public Key Infrastructure (PKI) services to enable, secure peering among anonymous peers. OSP is an ETSI standard and enables VOIP networks to exchange billing, Quality of Service (QoS), and routing information. &lt;/p&gt;
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-36&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Maintainers:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;Ullrich Abend&lt;br /&gt;
Di-Shi Sun&lt;/p&gt;
 
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser_version/0_10_x">2.0.x</category>
 <category domain="http://www.iptel.org/doc/module">Module</category>
 <category domain="http://www.iptel.org/ser/component/module/osp">osp</category>
 <pubDate>Sun, 14 Jan 2007 15:40:25 +0100</pubDate>
</item>
<item>
 <title>lcr</title>
 <link>http://www.iptel.org/ser/doc/modules/lcr</link>
 <description>&lt;div class=&quot;flexinode-body flexinode-8&quot;&gt;&lt;div class=&quot;flexinode-select-34&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Module status:&lt;/label&gt;&lt;br /&gt;
 Standard-dep
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-35&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Description:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;Least cost routing (LCR) module implements two related capabilities: &lt;/p&gt;
&lt;p&gt;LCR may sequentially forward requests to one or more gateways using the load_gws and next_gw functions.&lt;br /&gt;
LCR may sequentially forward contacts if they don&#039;t share the the same qvalues. Use the functions load_contacts and next_contacts to access and select a contact.&lt;/p&gt;
 
&lt;/div&gt;
&lt;/div&gt;&lt;div class=&quot;flexinode-textarea-36&quot;&gt;&lt;div class=&quot;form-item&quot;&gt;
 &lt;label&gt;Maintainers:&lt;/label&gt;&lt;br /&gt;
  &lt;p&gt;Juha Heinanen&lt;/p&gt;
 
&lt;/div&gt;
&lt;/div&gt;&lt;/div&gt;</description>
 <category domain="http://www.iptel.org/ser_version/0_10_x">2.0.x</category>
 <category domain="http://www.iptel.org/ser/component/module/lcr">lcr</category>
 <category domain="http://www.iptel.org/doc/module">Module</category>
 <pubDate>Sun, 14 Jan 2007 15:37:21 +0100</pubDate>
</item>
<item>
 <title>Introduction to Selects and Attributes</title>
 <link>http://www.iptel.org/introduction_to_selects_and_attribute_value_pairs_avpairs</link>
 <description> &lt;p&gt;In earlier versions of SER&lt;a href=&quot;glossary/term/244&quot; title=&quot;SER: SIP Express Router, fast and flexible SIP server.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt;, only a very limited amount of information related to the request being processed was available in the routing script. The amount of things that could be done in the script thus was rather limited. Many scenarios required the user to actually write a new module. &lt;/p&gt;&lt;p&gt;In SER 0.9 this situation changed somewhat with the introduction of AVPs. The original concept was to store some information for your users in a database table and load them on demand. The avpops module even allowed to manipulate the information albeit not in a very intuitional way.&lt;/p&gt;&lt;p&gt;For SER&amp;nbsp;2.0 the concept was spiced up a bit. AVPs are now called just &lt;em&gt;attributes &lt;/em&gt;and are available in a more intuitive way. Even more, a new framework was introduced to allow access to all sorts of information from the request and SER&#039;s entrails. The developers decided to call it the &lt;em&gt;select framework&lt;/em&gt;.&lt;/p&gt; </description>
 <category domain="http://www.iptel.org/ser_version/0_10_x">2.0.x</category>
 <category domain="http://www.iptel.org/doc/book">Book</category>
 <category domain="http://www.iptel.org/ser/component/core">core</category>
 <pubDate>Tue, 12 Dec 2006 21:12:56 +0100</pubDate>
</item>
<item>
 <title>Vaclav&#039;s Performance Tests</title>
 <link>http://www.iptel.org/ser/doc/performance/vaclev</link>
 <description> &lt;h2&gt;Ottendorf tests&lt;/h2&gt; &lt;p&gt;&lt;a href=&quot;~vku/performance/ottendorf/&quot;&gt;Here&lt;/a&gt; are some Ottendorf performance tests. The page will be updated according to progress in testing.&lt;br /&gt;&lt;/p&gt;&lt;p&gt;&lt;a target=&quot;_self&quot; href=&quot;~vku/performance/registrar/&quot;&gt;Registrar with database tuning&lt;/a&gt;. (updated on 25th May 2007)&lt;br /&gt;&lt;/p&gt;  &lt;h2&gt;Memory allocation methods&lt;/h2&gt; &lt;p&gt;Many people wonder, why there are non-standard memory allocation methods used within SER&lt;a href=&quot;glossary/term/244&quot; title=&quot;SER: SIP Express Router, fast and flexible SIP server.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt;. I run some tests which show significant difference between standard malloc/free and SER&#039;s allocation methods. (Memory management is one of most critical parts related to SIP performance.)&lt;/p&gt; </description>
 <category domain="http://www.iptel.org/ser_version/0_10_x">2.0.x</category>
 <category domain="http://www.iptel.org/ser/component/core">core</category>
 <pubDate>Sun, 10 Dec 2006 09:33:08 +0100</pubDate>
</item>
</channel>
</rss>
