Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
migration:kamailio-tips [2009/06/01 20:17]
87.95.38.116
migration:kamailio-tips [2009/12/10 18:47] (current)
192.98.100.132
Line 4: Line 4:
 ===== TCP Connection Lifetime ===== ===== TCP Connection Lifetime =====
  
-  * **registrar** module in Kamailio has support to set automatically the lifetime of the TCP connection for current processed SIP REGISTER message. +  * **registrar** module in Kamailio 1.5 and earlier had support to set automatically the lifetime of the TCP connection for current processed SIP REGISTER message by defining **tcp_persistent_flag** module parameter and then by setting the flag before save() function was called
-  * in **sip-router** similar functionality can be achieved by setting **tcp_connection_lifetime** config parameters just a bit higher than max registration expire. The lifetime for a TCP connection is automatically extended when a message is going through. In case of hard/soft phones, the connection is closed by client side when they shut down.+  * In **sip-router** and Kamailio 3.0 **tcp_persistent_flag** parameter does not exist anymore.  Similar functionality can be achieved by setting **tcp_connection_lifetime** core config parameter just a bit higher than max registration expire. The lifetime for a TCP connection is automatically extended when a message is going through. In case of hard/soft phones, the connection is closed by client side when they shut down.
  
 ===== Log levels ===== ===== Log levels =====
Line 54: Line 54:
  
 By default, [b]use_dns_failover[/b] is currently "off" Hopefully, the default can be changed to "on" in order to be compatible with Kamailio default. By default, [b]use_dns_failover[/b] is currently "off" Hopefully, the default can be changed to "on" in order to be compatible with Kamailio default.
 +
 +===== Core Functions =====
 +
 +  * [b]append_branch()[/b] - fully Kamailio append_branch() function is now implemented by [b]kex[/b] module and it is named [b]km_append_branch()[/b]. See:
 +    * http://sip-router.org/docbook/sip-router/branch/master/modules_k/kex/kex.html
 +    * note: there is still a core function still called [b]append_branch()[/b], but it is SIP Express Router (SER) compatible.
 +    * [b]km_append_branch()[/b] - as new feature, it accepts now the URI parameter to contain pseudo-variables
  
 ===== Script syntax ===== ===== Script syntax =====
Line 84: Line 91:
   * [b]tm onreply_avp_mode[/b] does not exist   * [b]tm onreply_avp_mode[/b] does not exist
  
-In SIP Router, AVPs that are set in request route are always visible in branch and failure routes. Not confirmed yet if they are visible in onreply_route - the behaviour controlled by this Kamailio parameter.+In SIP Router, AVPs that are set in request route are always visible in branchfailure, and onreply_route.  In other words, SIP Router behaves like Kamailio when onreply_avp_mode is set to value 1.
  
   * [b]tm fr_timer, fr_inv_timer, and contacts_avp[/b] AVP value syntax   * [b]tm fr_timer, fr_inv_timer, and contacts_avp[/b] AVP value syntax
  
 In SIP Router, AVP value of tm module parameters fr_timer, fr_inv_timer, and contacts_avp is currently written without $avp(), for example, "i:705" This is to be fixed. In SIP Router, AVP value of tm module parameters fr_timer, fr_inv_timer, and contacts_avp is currently written without $avp(), for example, "i:705" This is to be fixed.
 +
 +  * [b]tm fr_timer, fr_inv_timer, wt_timer, delete_timer, and unix_tx_timeout[/b] units
 +
 +In SIP Router, time value of the above parameters is given in milliseconds, whereas in Kamailio they are given in seconds (see [[ref_manual:timers|tm timers]] for more details). In order to make migration easier, perhaps a new tm module parameter could be introduced to specify, in which units time values are given.
  
 ===== Module functions ===== ===== Module functions =====
Line 102: Line 113:
   * [b]t_relay()[/b] does not generate internally a negative reply.  Negative reply is can always be generated explicitly from script.  If not done, it is generated implicitly at the end of the script.   * [b]t_relay()[/b] does not generate internally a negative reply.  Negative reply is can always be generated explicitly from script.  If not done, it is generated implicitly at the end of the script.
  
-  * [b]t_was_cancelled()[/b] is replaced by [db]t_is_canceled().+  * [b]t_was_cancelled()[/b] is replaced by [b]t_is_canceled()[/b].
  
 ===== Route blocks ===== ===== Route blocks =====

Navigation

Wiki

Other

QR Code
QR Code migration:kamailio-tips (generated for current page)