<?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 - tm</title>
 <link>http://www.iptel.org/taxonomy/term/142/0</link>
 <description>Transaction Manager.</description>
 <language>en</language>
<item>
 <title>tm</title>
 <link>http://www.iptel.org/ser/doc/modules/tm</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;
  &lt;p&gt;TM module enables stateful&lt;a href=&quot;glossary#term71&quot; title=&quot;stateful: Proxy or user agent that keeps transaction state in memory while processing SIP messages. Transaction-stateful implementations can associate SIP responses to SIP requests and can absorb retransmissions.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt; processing of SIP transactions&lt;a href=&quot;glossary#term69&quot; title=&quot;transaction: A collection of SIP messages which includes initial SIP request and all associated SIP replies.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt;. The main use of stateful logic, which is costly in terms of memory and CPU, is some services inherently need state. For example, transaction&lt;a href=&quot;glossary#term69&quot; title=&quot;transaction: A collection of SIP messages which includes initial SIP request and all associated SIP replies.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt;-based accounting (module acc) needs to process transaction state as opposed to individual messages, and any kinds of forking&lt;a href=&quot;glossary#term68&quot; title=&quot;forking: A SIP proxy server may send single SIP message to multiple destinations, this process is called &amp;quot;forking&amp;quot;.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt; must be implemented statefully. Other use of stateful processing is it trading CPU caused by retransmission&lt;a href=&quot;glossary#term72&quot; title=&quot;retransmission: SIP messages are often transferred by means of unreliable transport protocols such as UDP. SIP implementations would send SIP request again if receives no reply within a period of time to compensate for possible packet losses that can occur in the network.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt; processing for memory. That makes however only sense if CPU consumption per request is huge. For example, if you want to avoid costly DNS resolution for every retransmission of a request to an unresolvable destination, use stateful mode. Then, only the initial message burdens server by DNS queries, subsequent retransmissions&lt;a href=&quot;glossary#term72&quot; title=&quot;retransmission: SIP messages are often transferred by means of unreliable transport protocols such as UDP. SIP implementations would send SIP request again if receives no reply within a period of time to compensate for possible packet losses that can occur in the network.&quot; class=&quot;glossary-indicator&quot;&gt;i&lt;/a&gt; will be dropped and will not result in more processes blocked by DNS resolution. The price is more memory consumption and higher processing latency.&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;Jiri Kuthan&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/tm">tm</category>
 <pubDate>Sun, 26 Nov 2006 11:22:40 +0100</pubDate>
</item>
<item>
 <title>How the new timer framework works</title>
 <link>http://www.iptel.org/how_the_new_timer_framework_works</link>
 <description> &lt;p&gt;THANKS to Andrei for giving the actual info on the new timer implementation!!&lt;/p&gt;&lt;p&gt;The timers of the tm module can be confusing and normally you don&amp;uml;t have to (or should) tweak timers except the fr_inv_timer (controlling &amp;quot;how long to ring&amp;quot;).&amp;nbsp; The below table is an overview of the timers that can be changed from 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, how they correspond to the timer names in RFC3261 and how/why you would want to change it.&amp;nbsp;&lt;/p&gt;&lt;p&gt;The timers 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; 0.9.x are &lt;a href=&quot;faq/sertimers&quot; target=&quot;_self&quot;&gt;documented in the FAQ&lt;/a&gt;.&lt;/p&gt;&lt;p&gt;In 0.10.x the timer implementation&amp;nbsp;has been completely rewritten. The timers are now controlled in milliseconds and (not in seconds as in 0.9.x), e.g. modparam(&amp;quot;tm&amp;quot;, &amp;quot;fr_timer&amp;quot;, 30000) =&amp;gt; default value of 30s. The timer have a resolution of 1/TIMER_TICKS_HZ. This is&amp;nbsp;default 62.5 ms. Thus, the timer can fire every 62.5 ms.&amp;nbsp; Note that this also is the error interval (they can fire anywhere in a 62.5 ms interval from their &amp;quot;theoretical&amp;quot; expire point).&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/module/tm">tm</category>
 <pubDate>Tue, 17 Oct 2006 09:46:10 +0200</pubDate>
</item>
<item>
 <title>What are the different SER timers and how do they relate to RFC3261 timers?</title>
 <link>http://www.iptel.org/faq/sertimers</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/tm">tm</category>
 <pubDate>Fri, 13 Oct 2006 13:10:42 +0200</pubDate>
</item>
<item>
 <title>SER Wishlist</title>
 <link>http://www.iptel.org/ser/wishlist</link>
 <description> &lt;p&gt;This is the page where YOU add your most wanted 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; features or modules! Please feel free to edit this page. &lt;/p&gt;&lt;p&gt;See a &lt;a href=&quot;http://tracker.iptel.org/secure/IssueNavigator.jspa?reset=true&amp;&amp;pid=10000&amp;fixfor=-1&amp;fixfor=10001&amp;status=1&amp;status=3&amp;status=4&amp;sort&quot; target=&quot;_blank&quot;&gt;more detailed list of wishlist items&lt;/a&gt; on the tracker (items on this wishlist will end up in the tracker when they are detailed enough to do actual coding).&lt;/p&gt;&lt;p&gt;New groups can also be added. This wishlist is used for evaluating what to focus on for future releases. &lt;/p&gt;&lt;p&gt;In order to know the general interest of a feature, you can also vote for features. Just add an * in parenthesis behind the feature, and please only add one... &lt;/p&gt; </description>
 <category domain="http://www.iptel.org/ser/accounting_0">accounting</category>
 <category domain="http://www.iptel.org/ser/component/module/acc_db">acc_db</category>
 <category domain="http://www.iptel.org/ser/component/module/acc_radius">acc_radius</category>
 <category domain="http://www.iptel.org/ser/component/module/acc_syslog">acc_syslog</category>
 <category domain="http://www.iptel.org/ser/component/module/auth">auth</category>
 <category domain="http://www.iptel.org/ser/component/module/auth_db">auth_db</category>
 <category domain="http://www.iptel.org/ser/component/module/auth_radius">auth_radius</category>
 <category domain="http://www.iptel.org/ser/component/module/avp">avp</category>
 <category domain="http://www.iptel.org/ser/component/module/avpops">avpops</category>
 <category domain="http://www.iptel.org/ser/component/module/avp_db">avp_db</category>
 <category domain="http://www.iptel.org/ser/component/module/avp_radius">avp_radius</category>
 <category domain="http://www.iptel.org/ser/component_0">Component</category>
 <category domain="http://www.iptel.org/ser/component/core">core</category>
 <category domain="http://www.iptel.org/ser/component/module/cpl_c">cpl-c</category>
 <category domain="http://www.iptel.org/ser/component/module/ctl">ctl</category>
 <category domain="http://www.iptel.org/ser/component/module/dbtext">dbtext</category>
 <category domain="http://www.iptel.org/ser/component/module/dialog">dialog</category>
 <category domain="http://www.iptel.org/ser/component/module/dispatcher">dispatcher</category>
 <category domain="http://www.iptel.org/ser/component/module/diversion">diversion</category>
 <category domain="http://www.iptel.org/ser/component/module/domain">domain</category>
 <category domain="http://www.iptel.org/ser/component/module/enum">enum</category>
 <category domain="http://www.iptel.org/ser/component/module/exec">exec</category>
 <category domain="http://www.iptel.org/ser/accounting/field">field</category>
 <category domain="http://www.iptel.org/ser/component/module/fifo">fifo</category>
 <category domain="http://www.iptel.org/ser/component/module/flatstore">flatstore</category>
 <category domain="http://www.iptel.org/ser/function">function</category>
 <category domain="http://www.iptel.org/ser/component/module/gflags">gflags</category>
 <category domain="http://www.iptel.org/ser/component/module/group">group</category>
 <category domain="http://www.iptel.org/ser/component/module/group_radius">group_radius</category>
 <category domain="http://www.iptel.org/ser/component/module/jabber">jabber</category>
 <category domain="http://www.iptel.org/ser/component/module/lcr">lcr</category>
 <category domain="http://www.iptel.org/ser/component/module/mangler">mangler</category>
 <category domain="http://www.iptel.org/ser/component/module/maxfwd">maxfwd</category>
 <category domain="http://www.iptel.org/ser/component/module/mediaproxy">mediaproxy</category>
 <category domain="http://www.iptel.org/ser/component/memory">memory</category>
 <category domain="http://www.iptel.org/ser/component/module">module</category>
 <category domain="http://www.iptel.org/ser/component/module/msilo">msilo</category>
 <category domain="http://www.iptel.org/ser/component/module/mysql">mysql</category>
 <category domain="http://www.iptel.org/ser/component/module/nathelper">nathelper</category>
 <category domain="http://www.iptel.org/ser/component/module/options">options</category>
 <category domain="http://www.iptel.org/ser/component/module/osp">osp</category>
 <category domain="http://www.iptel.org/ser/component/module/pa">pa</category>
 <category domain="http://www.iptel.org/ser/parameter">parameter</category>
 <category domain="http://www.iptel.org/ser/component/parser">parser</category>
 <category domain="http://www.iptel.org/ser/component/module/pdt">pdt</category>
 <category domain="http://www.iptel.org/ser/component/module/permissions">permissions</category>
 <category domain="http://www.iptel.org/ser/component/module/pike">pike</category>
 <category domain="http://www.iptel.org/ser/component/module/postgres">postgres</category>
 <category domain="http://www.iptel.org/ser/component/module/presence_b2b">presence_b2b</category>
 <category domain="http://www.iptel.org/ser/component/module/print">print</category>
 <category domain="http://www.iptel.org/ser/component/module/ratelimit">ratelimit</category>
 <category domain="http://www.iptel.org/ser/component/module/registrar">registrar</category>
 <category domain="http://www.iptel.org/ser/component/module/rls">rls</category>
 <category domain="http://www.iptel.org/ser/component/module/rr">rr</category>
 <category domain="http://www.iptel.org/ser/component/module/sanity">sanity</category>
 <category domain="http://www.iptel.org/ser/ser_cfg">ser.cfg</category>
 <category domain="http://www.iptel.org/ser/component/module/sl">sl</category>
 <category domain="http://www.iptel.org/ser/component/module/sms">sms</category>
 <category domain="http://www.iptel.org/ser/component/module/speeddial">speeddial</category>
 <category domain="http://www.iptel.org/ser/component/module/textops">textops</category>
 <category domain="http://www.iptel.org/ser/component/module/tls">tls</category>
 <category domain="http://www.iptel.org/ser/component/module/tm">tm</category>
 <category domain="http://www.iptel.org/ser/component/transport">transport</category>
 <category domain="http://www.iptel.org/ser/component/module/uac">uac</category>
 <category domain="http://www.iptel.org/ser/component/module/unixsock">unixsock</category>
 <category domain="http://www.iptel.org/ser/component/module/uri">uri</category>
 <category domain="http://www.iptel.org/ser/component/module/uri_db">uri_db</category>
 <category domain="http://www.iptel.org/ser/component/module/uri_radius">uri_radius</category>
 <category domain="http://www.iptel.org/ser/component/module/usrloc">usrloc</category>
 <category domain="http://www.iptel.org/ser/component/module/xlog">xlog</category>
 <category domain="http://www.iptel.org/ser/component/module/xmlrpc">xmlrpc</category>
 <pubDate>Sun, 23 Apr 2006 15:47:31 +0200</pubDate>
</item>
</channel>
</rss>
