You are here: start » migration » kamailio-tips

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/12/09 09:28]
192.98.100.132 		migration:kamailio-tips [2009/12/10 18:47] (current)
192.98.100.132
Line 5: Line 5:
  
   * **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.   * **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** and Kamailio 3.0 **tcp_persistent_flag** parameter does not exist anymore.  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 91: 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 branch, failure, 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

Trace:

Navigation

Wiki

Other

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