fix MD034/no-bare-urls Bare URL used

README.md

@@ -8,13 +8,13 @@
 
 Initial content was converted from the Dokuwiki at:
 
-- https://www.kamailio.org/wiki/
+- <https://www.kamailio.org/wiki/>
 
 ## Support ##
 
 To update the content, make a pull request at:
 
-- https://github.com/kamailio/kamailio-wiki
+- <https://github.com/kamailio/kamailio-wiki>
 
 The wiki pages are inside the **[docs/](docs/)** folder.
 

docs/alphaindexes/4.1.x/modfunctions.md

@@ -730,16 +730,16 @@
 
 | Name                                     | Module Path | Module Name                                                                                             |
 |------------------------------------------|-------------|---------------------------------------------------------------------------------------------------------|
-| **uac_auth()**                           | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_auth())                     |
-| **uac_reg_lookup(uuid, dst)**            | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_reg_lookup(uuid, dst))      |
-| **uac_reg_request_to(user, mode)**       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_reg_request_to(user, mode)) |
+| **uac_auth()**                           | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_auth)                     |
+| **uac_reg_lookup(uuid, dst)**            | *modules*   | [uac](<http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_reg_lookup>)      |
+| **uac_reg_request_to(user, mode)**       | *modules*   | [uac](<http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_reg_request_to>) |
 | **uac_replace_from(display,uri)**        | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_replace_from)               |
-| **uac_replace_from(uri)**                | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_replace_from(uri))          |
-| **uac_replace_to(display,uri)**          | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_replace_to(display,uri))    |
-| **uac_replace_to(uri)**                  | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_replace_to(uri))            |
-| **uac_req_send()**                       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_req_send())                 |
-| **uac_restore_from()**                   | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_restore_from())             |
-| **uac_restore_to()**                     | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_restore_to())               |
+| **uac_replace_from(uri)**                | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_replace_from)          |
+| **uac_replace_to(display,uri)**          | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_replace_to)    |
+| **uac_replace_to(uri)**                  | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_replace_to)            |
+| **uac_req_send()**                       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_req_send)                 |
+| **uac_restore_from()**                   | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_restore_from)             |
+| **uac_restore_to()**                     | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.1.x/modules/uac.html#uac.f.uac_restore_to)               |
 | **unforce_rtp_proxy()**                  | *modules*   | [rtpproxy](http://www.kamailio.org/docs/modules/4.1.x/modules/rtpproxy.html)                            |
 | **unlock(key)**                          | *modules*   | [cfgutils](http://www.kamailio.org/docs/modules/4.1.x/modules/cfgutils.html#cfgutils.f.unlock)          |
 | **unlock_extra_attrs (group_id, id)**    | *modules*   | [uid_avp_db](http://www.kamailio.org/docs/modules/4.1.x/modules/uid_avp_db.html)                        |

docs/alphaindexes/4.2.x/modfunctions.md

@@ -781,16 +781,16 @@
 
 | Name                                     | Module Path | Module Name                                                                                               |
 |------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------|
-| **uac_auth()**                           | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_auth())                       |
-| **uac_reg_lookup(uuid, dst)**            | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_reg_lookup(uuid, dst))        |
-| **uac_reg_request_to(user, mode)**       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_reg_request_to(user, mode))   |
+| **uac_auth()**                           | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_auth)                       |
+| **uac_reg_lookup(uuid, dst)**            | *modules*   | [uac](<http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_reg_lookup>)        |
+| **uac_reg_request_to(user, mode)**       | *modules*   | [uac](<http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_reg_request_to>)   |
 | **uac_replace_from(display,uri)**        | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_replace_from)                 |
-| **uac_replace_from(uri)**                | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_replace_from(uri))            |
-| **uac_replace_to(display,uri)**          | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_replace_to(display,uri))      |
-| **uac_replace_to(uri)**                  | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_replace_to(uri))              |
-| **uac_req_send()**                       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_req_send())                   |
-| **uac_restore_from()**                   | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_restore_from())               |
-| **uac_restore_to()**                     | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_restore_to())                 |
+| **uac_replace_from(uri)**                | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_replace_from)            |
+| **uac_replace_to(display,uri)**          | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_replace_to)      |
+| **uac_replace_to(uri)**                  | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_replace_to)              |
+| **uac_req_send()**                       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_req_send)                   |
+| **uac_restore_from()**                   | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_restore_from)               |
+| **uac_restore_to()**                     | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.2.x/modules/uac.html#uac.f.uac_restore_to)                 |
 | **unforce_rtp_proxy()**                  | *modules*   | [rtpproxy](http://www.kamailio.org/docs/modules/4.2.x/modules/rtpproxy.html)                              |
 | **unlock(key)**                          | *modules*   | [cfgutils](http://www.kamailio.org/docs/modules/4.2.x/modules/cfgutils.html#cfgutils.f.unlock)            |
 | **unlock_extra_attrs (group_id, id)**    | *modules*   | [uid_avp_db](http://www.kamailio.org/docs/modules/4.2.x/modules/uid_avp_db.html)                          |

docs/alphaindexes/4.3.x/modfunctions.md

@@ -820,16 +820,16 @@
 
 | Name                                     | Module Path | Module Name                                                                                               |
 |------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------|
-| **uac_auth()**                           | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_auth())                       |
-| **uac_reg_lookup(uuid, dst)**            | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_reg_lookup(uuid, dst))        |
-| **uac_reg_request_to(user, mode)**       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_reg_request_to(user, mode))   |
+| **uac_auth()**                           | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_auth)                       |
+| **uac_reg_lookup(uuid, dst)**            | *modules*   | [uac](<http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_reg_lookup>)        |
+| **uac_reg_request_to(user, mode)**       | *modules*   | [uac](<http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_reg_request_to>)   |
 | **uac_replace_from(display,uri)**        | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_replace_from)                 |
-| **uac_replace_from(uri)**                | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_replace_from(uri))            |
-| **uac_replace_to(display,uri)**          | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_replace_to(display,uri))      |
-| **uac_replace_to(uri)**                  | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_replace_to(uri))              |
-| **uac_req_send()**                       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_req_send())                   |
-| **uac_restore_from()**                   | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_restore_from())               |
-| **uac_restore_to()**                     | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_restore_to())                 |
+| **uac_replace_from(uri)**                | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_replace_from)            |
+| **uac_replace_to(display,uri)**          | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_replace_to)      |
+| **uac_replace_to(uri)**                  | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_replace_to)              |
+| **uac_req_send()**                       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_req_send)                   |
+| **uac_restore_from()**                   | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_restore_from)               |
+| **uac_restore_to()**                     | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.3.x/modules/uac.html#uac.f.uac_restore_to)                 |
 | **unforce_rtp_proxy()**                  | *modules*   | [rtpproxy](http://www.kamailio.org/docs/modules/4.3.x/modules/rtpproxy.html)                              |
 | **unlock(key)**                          | *modules*   | [cfgutils](http://www.kamailio.org/docs/modules/4.3.x/modules/cfgutils.html#cfgutils.f.unlock)            |
 | **unlock_extra_attrs (group_id, id)**    | *modules*   | [uid_avp_db](http://www.kamailio.org/docs/modules/4.3.x/modules/uid_avp_db.html)                          |

docs/alphaindexes/4.4.x/modfunctions.md

@@ -859,16 +859,16 @@
 
 | Name                                     | Module Path | Module Name                                                                                               |
 |------------------------------------------|-------------|-----------------------------------------------------------------------------------------------------------|
-| **uac_auth()**                           | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_auth())                       |
-| **uac_reg_lookup(uuid, dst)**            | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_reg_lookup(uuid, dst))        |
-| **uac_reg_request_to(user, mode)**       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_reg_request_to(user, mode))   |
+| **uac_auth()**                           | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_auth)                       |
+| **uac_reg_lookup(uuid, dst)**            | *modules*   | [uac](<http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_reg_lookup>)        |
+| **uac_reg_request_to(user, mode)**       | *modules*   | [uac](<http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_reg_request_to>)   |
 | **uac_replace_from(display,uri)**        | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_replace_from)                 |
-| **uac_replace_from(uri)**                | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_replace_from(uri))            |
-| **uac_replace_to(display,uri)**          | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_replace_to(display,uri))      |
-| **uac_replace_to(uri)**                  | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_replace_to(uri))              |
-| **uac_req_send()**                       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_req_send())                   |
-| **uac_restore_from()**                   | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_restore_from())               |
-| **uac_restore_to()**                     | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_restore_to())                 |
+| **uac_replace_from(uri)**                | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_replace_from)            |
+| **uac_replace_to(display,uri)**          | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_replace_to)      |
+| **uac_replace_to(uri)**                  | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_replace_to)              |
+| **uac_req_send()**                       | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_req_send)                   |
+| **uac_restore_from()**                   | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_restore_from)               |
+| **uac_restore_to()**                     | *modules*   | [uac](http://www.kamailio.org/docs/modules/4.4.x/modules/uac.html#uac.f.uac_restore_to)                 |
 | **unforce_rtp_proxy()**                  | *modules*   | [rtpproxy](http://www.kamailio.org/docs/modules/4.4.x/modules/rtpproxy.html)                              |
 | **unlock(key)**                          | *modules*   | [cfgutils](http://www.kamailio.org/docs/modules/4.4.x/modules/cfgutils.html#cfgutils.f.unlock)            |
 | **unlock_extra_attrs (group_id, id)**    | *modules*   | [uid_avp_db](http://www.kamailio.org/docs/modules/4.4.x/modules/uid_avp_db.html)                          |

docs/alphaindexes/5.0.x/modfunctions.md

@@ -864,17 +864,17 @@
 
 | Name                                     | Module Path   | Module Name                                                                                                   |
 |------------------------------------------|---------------|---------------------------------------------------------------------------------------------------------------|
-| **uac_auth()**                           | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_auth())                       |
-| **uac_reg_lookup(uuid, dst)**            | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_reg_lookup(uuid, dst))        |
-| **uac_reg_request_to(user, mode)**       | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_reg_request_to(user, mode))   |
-| **uac_reg_status(uuid)**                 | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_reg_status(uuid))             |
+| **uac_auth()**                           | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_auth)                       |
+| **uac_reg_lookup(uuid, dst)**            | *src/modules* | [uac](<http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_reg_lookup>)        |
+| **uac_reg_request_to(user, mode)**       | *src/modules* | [uac](<http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_reg_request_to>)   |
+| **uac_reg_status(uuid)**                 | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_reg_status)             |
 | **uac_replace_from(display,uri)**        | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_replace_from)                 |
-| **uac_replace_from(uri)**                | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_replace_from(uri))            |
-| **uac_replace_to(display,uri)**          | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_replace_to(display,uri))      |
-| **uac_replace_to(uri)**                  | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_replace_to(uri))              |
-| **uac_req_send()**                       | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_req_send())                   |
-| **uac_restore_from()**                   | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_restore_from())               |
-| **uac_restore_to()**                     | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_restore_to())                 |
+| **uac_replace_from(uri)**                | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_replace_from)            |
+| **uac_replace_to(display,uri)**          | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_replace_to)      |
+| **uac_replace_to(uri)**                  | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_replace_to)              |
+| **uac_req_send()**                       | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_req_send)                   |
+| **uac_restore_from()**                   | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_restore_from)               |
+| **uac_restore_to()**                     | *src/modules* | [uac](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uac.html#uac.f.uac_restore_to)                 |
 | **unforce_rtp_proxy()**                  | *src/modules* | [rtpproxy](http://www.kamailio.org/docs/modules/5.0.x/src/modules/rtpproxy.html#rtpproxy.f.unforce_rtp_proxy) |
 | **unlock(key)**                          | *src/modules* | [cfgutils](http://www.kamailio.org/docs/modules/5.0.x/src/modules/cfgutils.html#cfgutils.f.unlock)            |
 | **unlock_extra_attrs (group_id, id)**    | *src/modules* | [uid_avp_db](http://www.kamailio.org/docs/modules/5.0.x/src/modules/uid_avp_db.html)                          |

docs/devel/git-access.md

@@ -90,7 +90,7 @@ new code that might not get to **master** branch after all.
 
 - whenever there are patches for modules maintained by other
     developers, it is better to discuss them on
-    [email protected] mailing list before pushing them to
+    <[email protected]> mailing list before pushing them to
     remote repository. The patch can be:
   - submitted as attachment to mailing list
   - uploaded to the tracker at:

docs/devel/irc-meetings/2013blog.md

@@ -2,994 +2,994 @@
 
 ## outstanding issues at this time, if any
 
-\[16:00 - \[16:06\] are missing from my chat client, sorry  
-\[16:06\] \<miconda> the last one was sent to sr-dev, iirc  
-\[16:06\] \<miconda> the minutes  
+\[16:00 - \[16:06\] are missing from my chat client, sorry
+\[16:06\] \<miconda> the last one was sent to sr-dev, iirc
+\[16:06\] \<miconda> the minutes
 \[16:07\] \<miconda> oej: yes, it seems for the last one are only on
-sr-dev (at least not on wiki)  
-\[16:07\] \<miconda> Vicente was sending them  
-\[16:08\] \<miconda> ok … no outstanding issues for now  
-\[16:08\] \<miconda> next topic  
+sr-dev (at least not on wiki)
+\[16:07\] \<miconda> Vicente was sending them
+\[16:08\] \<miconda> ok … no outstanding issues for now
+\[16:08\] \<miconda> next topic
 
 ## roadmap to next major release
 
-\[16:08\] \<miconda> let's do planning for next minor release  
-\[16:08\] \<miconda> and do major release at the end  
+\[16:08\] \<miconda> let's do planning for next minor release
+\[16:08\] \<miconda> and do major release at the end
 \[16:09\] \<miconda> after we see the near future plans for
-development.  
-\[16:09\] \<ZogG_laptop> hello  
-\[16:09\] \<miconda> last minor release was in August 15  
+development.
+\[16:09\] \<ZogG_laptop> hello
+\[16:09\] \<miconda> last minor release was in August 15
 \[16:09\] \<miconda> perhaps we can do one by end of September or so
-(before Astricon)  
-\[16:10\] \<henningw> sounds good  
+(before Astricon)
+\[16:10\] \<henningw> sounds good
 \[16:10\] \<miconda> I haven't looked at patches since 4.0.3, but I
-remember I did a few of them  
-\[16:11\] \<linuxmaniac> one crash is fixed on ua_redirect  
-\[16:11\] \<miconda> linuxmaniac: ok, thanks for it  
-\[16:11\] \<linuxmaniac> miconda: my pleasure :-)  
+remember I did a few of them
+\[16:11\] \<linuxmaniac> one crash is fixed on ua_redirect
+\[16:11\] \<miconda> linuxmaniac: ok, thanks for it
+\[16:11\] \<linuxmaniac> miconda: my pleasure :-)
 \[16:12\] \<ZogG_laptop> oh not shure if patch was sent but there is
-small bug in presence module  
-\[16:12\] \<ZogG_laptop> at least it's still at 4.0.3  
-\[16:12\] \<miconda> ok then -- 4.0.4 by end of September  
-\[16:12\] \<linuxmaniac> \\o/  
-\[16:12\] \<miconda> ZogG_laptop: send it over sr-dev  
-\[16:12\] \<miconda> or put it on the tracker  
-\[16:12\] \<miconda> if already fixed, will be marked as done  
+small bug in presence module
+\[16:12\] \<ZogG_laptop> at least it's still at 4.0.3
+\[16:12\] \<miconda> ok then -- 4.0.4 by end of September
+\[16:12\] \<linuxmaniac> \\o/
+\[16:12\] \<miconda> ZogG_laptop: send it over sr-dev
+\[16:12\] \<miconda> or put it on the tracker
+\[16:12\] \<miconda> if already fixed, will be marked as done
 \[16:13\] \<miconda> what people prefer to do now -- the techical
-(devel) topics or the admin ones?  
-\[16:14\] \<linuxmaniac> tech?  
-\[16:14\] \<miconda> ok  
-\[16:14\] \<miconda> first come first served  
-\[16:14\] \<miconda> technical topics  
+(devel) topics or the admin ones?
+\[16:14\] \<linuxmaniac> tech?
+\[16:14\] \<miconda> ok
+\[16:14\] \<miconda> first come first served
+\[16:14\] \<miconda> technical topics
 
 ## xcap-diff - purpose and testing
 
-\[16:14\] \<miconda> one I wanted to get some input is about xcap-diff  
+\[16:14\] \<miconda> one I wanted to get some input is about xcap-diff
 \[16:15\] \<miconda> as I said during last irc meeting I will try to do
-it before next major release  
+it before next major release
 \[16:15\] \<ZogG_laptop> miconda: not sure if it would be right one. the
 problem that docs states that reginfo_handle_notify() doesn't get any
-parameters while in code it does want one  
+parameters while in code it does want one
 \[16:15\] \<ZogG_laptop> so just changing 1 to zero fixed the error from
-script  
+script
 \[16:15\] \<miconda> ZogG_laptop: maybe is not the right fix, if it
-expects some parameter  
-\[16:16\] \<miconda> but report it and we look at  
-\[16:16\] \<ZogG_laptop> ok thanks  
-\[16:16\] \<ZogG_laptop> i'll do  
-\[16:16\] \<miconda> carstenbock is the developer, iirc  
-\[16:16\] \<carstenbock> That's right, i implemented it.  
-\[16:16\] \<miconda> and I saw some reports on tracker this morning  
+expects some parameter
+\[16:16\] \<miconda> but report it and we look at
+\[16:16\] \<ZogG_laptop> ok thanks
+\[16:16\] \<ZogG_laptop> i'll do
+\[16:16\] \<miconda> carstenbock is the developer, iirc
+\[16:16\] \<carstenbock> That's right, i implemented it.
+\[16:16\] \<miconda> and I saw some reports on tracker this morning
 \[16:16\] \<carstenbock> Haven't looked at the recent bug-reports,
-though.  
-\[16:17\] \<miconda> that ruid is not set for records  
+though.
+\[16:17\] \<miconda> that ruid is not set for records
 \[16:17\] \<carstenbock> Putting the bug on the tracker is the best
-way.  
-\[16:17\] \<miconda> some are already there (regarding reginfo)  
+way.
+\[16:17\] \<miconda> some are already there (regarding reginfo)
 \[16:17\] \<miconda> ok, back to my xcap-diff, maybe pdunkley can
-comment  
+comment
 \[16:18\] \<pdunkley> Definitely in favour of getting xcap-diff
-support.  
+support.
 \[16:18\] \<miconda> from quick check of the specs, looks like the body
 for notifies has to be pretty much the xml chunk that was uploaded with
-put  
-\[16:18\] \<miconda> is it right?  
-\[16:19\] \<pdunkley> Sort-of.  
+put
+\[16:18\] \<miconda> is it right?
+\[16:19\] \<pdunkley> Sort-of.
 \[16:19\] \<miconda> I started to add, pua and presence should be able
-to handle them  
-\[16:19\] \<miconda> the missing part is the publish from xcap-server  
+to handle them
+\[16:19\] \<miconda> the missing part is the publish from xcap-server
 \[16:19\] \<pdunkley> Problem is that NOTIFYs must be throttled, for
-example no-more than one per five second period per dialog.  
+example no-more than one per five second period per dialog.
 \[16:19\] \<pdunkley> So what do you do if there are two changes to the
-document in that period?  
-\[16:19\] \<miconda> pdunkley: everything is sort-of in SIMPLE :-)  
-\[16:19\] \<miconda> throttling is required by specs?  
+document in that period?
+\[16:19\] \<miconda> pdunkley: everything is sort-of in SIMPLE :-)
+\[16:19\] \<miconda> throttling is required by specs?
 \[16:20\] \<pdunkley> And of course, you can only have one NOTIFY
 outstanding at a time, so you can't send the second until you have a
-final response to the first.  
+final response to the first.
 \[16:20\] \<miconda> can we just say at some point, hey, just take the
-full docs  
+full docs
 \[16:20\] \<pdunkley> The base SUBSCRIBE/NOTIFY spec. mandates
-throttling and recommends 5s for presence.  
+throttling and recommends 5s for presence.
 \[16:21\] \<pdunkley> It's up to each specification that defines an
 event-package to say what the throttle rate should be, but the spec.
-does have to say it.  
+does have to say it.
 \[16:21\] \<pdunkley> If the xcap-diff spec. doesn't I'd think it needs
-to be the SUBSCRIBE/NOTIFY default of 5s.  
+to be the SUBSCRIBE/NOTIFY default of 5s.
 \[16:21\] \<pdunkley> I think you can basically say "the doc has changed
-and it is too complicated for a patch - so just get it again".  
+and it is too complicated for a patch - so just get it again".
 \[16:22\] \<pdunkley> That'd be a good starting point for the first
-version.  
+version.
 \[16:22\] \<pdunkley> The presence module already has NOTIFY throttling
 in it, so if you do say "get the whole doc" all of the time it should
-just work (I think).  
+just work (I think).
 \[16:22\] \<miconda> ok, so we can go with kind of workaround, if we
 have many changes within the throttling interval, then just mark it for
-complete refresh?!?  
+complete refresh?!?
 \[16:23\] \<miconda> keeping the list of diffs can get complex
-otherwise  
-\[16:24\] \<pdunkley> I agree.  
-\[16:24\] \<miconda> ok, for now I am fine with this topuc  
-\[16:24\] \<pdunkley> This is the server side of xcap-diff?  
-\[16:24\] \<miconda> yes  
+otherwise
+\[16:24\] \<pdunkley> I agree.
+\[16:24\] \<miconda> ok, for now I am fine with this topuc
+\[16:24\] \<pdunkley> This is the server side of xcap-diff?
+\[16:24\] \<miconda> yes
 \[16:24\] \<pdunkley> So it allows presence servers and UAs to SUBSCRIBE
-to the XCAP server?  
+to the XCAP server?
 \[16:25\] \<pdunkley> Is there any need or desire to do the client side
-of xcap-diff at some point?  
-\[16:25\] \<miconda> yes, do you want a client?  
-\[16:25\] \<miconda> maybe for those implementing sip clients...  
+of xcap-diff at some point?
+\[16:25\] \<miconda> yes, do you want a client?
+\[16:25\] \<miconda> maybe for those implementing sip clients...
 \[16:25\] \<pdunkley> This would mean the presence module and rls
 modules could subscribe to the XCAP server (including a non-Kamailio
-XCAP server) instead of the proprietary  
-internal links.  
+XCAP server) instead of the proprietary
+internal links.
 \[16:26\] \<pdunkley> There is already the XCAP client module in
 Kamailio that can be used when presence/rls and xcap-server don't share
-a DB.  
-\[16:26\] \<miconda> for now my focus is on server  
-\[16:26\] \<pdunkley> OK, just checking.  
+a DB.
+\[16:26\] \<miconda> for now my focus is on server
+\[16:26\] \<pdunkley> OK, just checking.
 \[16:27\] \<pdunkley> Does anyone know of a good (and free) client that
-supports xcap-diff?  
+supports xcap-diff?
 \[16:27\] \<miconda> xcap client is just xcap -- no sip/presence in it,
-which will be required here  
-\[16:27\] \<miconda> so I assume it would have to be a pua_XXX module  
+which will be required here
+\[16:27\] \<miconda> so I assume it would have to be a pua_XXX module
 \[16:27\] \<pdunkley> The only one I know of is Blink. But not sure how
-good the other bits of Blink presence are...  
+good the other bits of Blink presence are...
 \[16:28\] \<miconda> pdunkley: probably not, but I though you will add
-it to your communicator :-)  
-\[16:28\] \<pdunkley> Lol  
+it to your communicator :-)
+\[16:28\] \<pdunkley> Lol
 \[16:28\] \<jh> i have tested sipclients presence and found bugs in it
-that have not been fixed  
+that have not been fixed
 \[16:28\] \<pdunkley> We are quite happily using XMPP in a CUSAX like
-way at the moment.  
-\[16:28\] \<miconda> i am not aware of a good ones, free or not  
-\[16:28\] \<miconda> pdunkley: ok  
+way at the moment.
+\[16:28\] \<miconda> i am not aware of a good ones, free or not
+\[16:28\] \<miconda> pdunkley: ok
 \[16:29\] \<pdunkley> May do SIP presence and XCAP in the future, if
-there is demand for it.  
-\[16:29\] \<miconda> ok, then let's mark this topic done  
-\[16:29\] \<miconda> next one: dialog vs dialog_ng  
+there is demand for it.
+\[16:29\] \<miconda> ok, then let's mark this topic done
+\[16:29\] \<miconda> next one: dialog vs dialog_ng
 
 ## dialog vs. dialog_ng
 
 \[16:29\] \<miconda> I don't see Jason here for getting more details
-about dialog ng  
-\[16:30\] \<miconda> anyone else here using it? (carstenbock)  
-\[16:30\] \<carstenbock> I am a heavy user.  
-\[16:31\] \<oej> so what are the differences?  
+about dialog ng
+\[16:30\] \<miconda> anyone else here using it? (carstenbock)
+\[16:30\] \<carstenbock> I am a heavy user.
+\[16:31\] \<oej> so what are the differences?
 \[16:31\] \<carstenbock> There are some differences between dialog and
 dialog_ng. A big part is actually, that you can tear down calls even
-during setup-phase.  
-\[16:31\] \<oej> What's the plan  
-\[16:31\] \<ZogG_laptop> tear?  
-\[16:31\] \<carstenbock> terminated  
-\[16:31\] \<ZogG_laptop> oh  
-\[16:31\] \<oej> hang up  
+during setup-phase.
+\[16:31\] \<oej> What's the plan
+\[16:31\] \<ZogG_laptop> tear?
+\[16:31\] \<carstenbock> terminated
+\[16:31\] \<ZogG_laptop> oh
+\[16:31\] \<oej> hang up
 \[16:32\] \<carstenbock> e.g. if the network fails during call-setup
 (detected via Diameter-Rx), you can terminate a call if it is not
-connected yet.  
+connected yet.
 \[16:33\] \<miconda> but there were some parts missing from the old
-dialog, or all features of the old dialog are in dialog_ng?  
+dialog, or all features of the old dialog are in dialog_ng?
 \[16:33\] \<carstenbock> That's about the main difference. I think
 another difference is, that the API has a direct function for
-terminating calls.  
+terminating calls.
 \[16:33\] \<carstenbock> What is missing (as with most IMS-modules
-actually), is the database-backend.  
+actually), is the database-backend.
 \[16:34\] \<carstenbock> All information is only in memory at the
-moment.  
-\[16:34\] \<oej> are all the rpc commands there?  
+moment.
+\[16:34\] \<oej> are all the rpc commands there?
 \[16:35\] \<miconda> carstenbock: that's fine, kamailio just keeps
-running  
-\[16:35\] \<miconda> :-)  
-\[16:35\] \<carstenbock> Exactly that's the case... ;-)  
-\[16:35\] \<oej> Who needs to depend on databases then?  
-\[16:35\] \<oej> A new definition of "no-sql"  
+running
+\[16:35\] \<miconda> :-)
+\[16:35\] \<carstenbock> Exactly that's the case... ;-)
+\[16:35\] \<oej> Who needs to depend on databases then?
+\[16:35\] \<oej> A new definition of "no-sql"
 \[16:35\] \<carstenbock> Jason also mentioned, that they implemented a
 lot of the stuff that's was in a wiki page about improvements in the
-dialog module.  
+dialog module.
 \[16:36\] \<carstenbock> I don't know, what they all implemented from
 this page:
-http:*www.kamailio.org/dokuwiki/doku.php/modules-new-design:dialog-module-design  
+http:*<www.kamailio.org/dokuwiki/doku.php/modules-new-design:dialog-module-design>
 \[16:37\] \<miconda> ok, db backend is important -- I will try to catch
-up with Jason on mailing lists  
+up with Jason on mailing lists
 \[16:38\] \<miconda> I had in mind to do some cleanup on the matching
-modes of the old dialog  
-\[16:38\] \<miconda> probably I will still do it  
+modes of the old dialog
+\[16:38\] \<miconda> probably I will still do it
 \[16:39\] \<ZogG_laptop> i see there is option to get dialog by cutom
-added key (from module doc — get_dlg_var (dlg, key) )  
+added key (from module doc — get_dlg_var (dlg, key) )
 \[16:39\] \<carstenbock> Regarding matching modes: dialog_ng does only
-matching on SIP-Elements, nothing else.  
+matching on SIP-Elements, nothing else.
 \[16:39\] \<carstenbock> I don't think we have that in dialog_ng
-(yet).  
+(yet).
 \[16:40\] \<miconda> carstenbock: yes, that was my plan as well, plus
-few optimizations for faster matching  
-\[16:40\] \<miconda> I'll see if I have enough time  
-\[16:40\] \<miconda> anything else on the technical side?  
+few optimizations for faster matching
+\[16:40\] \<miconda> I'll see if I have enough time
+\[16:40\] \<miconda> anything else on the technical side?
 \[16:41\] \<miconda> I assume the code restructuring will be postponed,
-doesn;t look like enough time for it  
+doesn;t look like enough time for it
 \[16:41\] \<carstenbock> I can confirm, dialog_ng works excellent (for
-me in my setups)  
-\[16:41\] \<miconda> carstenbock: all our homeworks worked at home :-)  
-\[16:41\] \<miconda> I don't disagree with you, actually  
+me in my setups)
+\[16:41\] \<miconda> carstenbock: all our homeworks worked at home :-)
+\[16:41\] \<miconda> I don't disagree with you, actually
 \[16:42\] \<kolbu> in the old dialog module we still see a stuck dialog
-if a 486 and 200 is received at more or less exactly the same time  
-\[16:42\] \<miconda> just that many features might be missing  
+if a 486 and 200 is received at more or less exactly the same time
+\[16:42\] \<miconda> just that many features might be missing
 \[16:42\] \<ZogG_laptop> so regards that function, does it as well
-support dialog properties?  
-\[16:42\] \<miconda> kolbu: with latest 4.0 branch?  
-\[16:42\] \<kolbu> running 4.0.3 ++  
-\[16:42\] \<kolbu> that is, a few days after 4.0.3  
-\[16:43\] \<miconda> kolbu: what state it hangs on?  
-\[16:43\] \<kolbu> 4  
+support dialog properties?
+\[16:42\] \<miconda> kolbu: with latest 4.0 branch?
+\[16:42\] \<kolbu> running 4.0.3 ++
+\[16:42\] \<kolbu> that is, a few days after 4.0.3
+\[16:43\] \<miconda> kolbu: what state it hangs on?
+\[16:43\] \<kolbu> 4
 \[16:43\] \<ZogG_laptop> e.g. from_tag/caller_contact/etc or it does
-support only custom added ones from set_dlg_var ?  
-\[16:43\] \<iZverg> are read dialogs from db in dialog-ng ?  
+support only custom added ones from set_dlg_var ?
+\[16:43\] \<iZverg> are read dialogs from db in dialog-ng ?
 \[16:43\] \<kolbu> which is good, because then we can close it with the
-dlg_end_dlg fifo  
-\[16:43\] \<iZverg> are read dialogs from db in dialog-ng \_planned\_?  
+dlg_end_dlg fifo
+\[16:43\] \<iZverg> are read dialogs from db in dialog-ng \_planned\_?
 \[16:43\] \<ZogG_laptop> iZverg: afaik no db implantation was made for
-dialog_ng  
-\[16:44\] \<carstenbock> Not yet. That will follow.  
+dialog_ng
+\[16:44\] \<carstenbock> Not yet. That will follow.
 \[16:44\] \<miconda> kolbu: maybe you can open a tracker item and add
-some details there  
+some details there
 \[16:44\] \<carstenbock> DB-Support is definitely planned, but not
-scheduled yet...  
+scheduled yet...
 \[16:45\] \<iZverg> i think in dialog need ability to read dialogs from
-db  
+db
 ===== memcached module ===== \[16:46\] \<iZverg> and memcached multiple
-servers. as i see no developer for memcached now?  
-\[16:46\] \<kolbu> miconda: ok, will do  
+servers. as i see no developer for memcached now?
+\[16:46\] \<kolbu> miconda: ok, will do
 \[16:46\] \* dr wants the memcached module that compiles with
-libmemcached in kamailio 4.0.4 :)  
+libmemcached in kamailio 4.0.4 :)
 \[16:46\] \<miconda> iZverg: memcached module was refactored rather
-recently  
+recently
 \[16:46\] \<kolbu> worth mentioning that the dialog module in 4.0 is
-sooo much more reliable than in 3.3  
-\[16:46\] \<miconda> so there are developers for it  
-\[16:47\] \<miconda> kolbu: ok  
-\[16:47\] \<miconda> dr: I think devel version compiles with that lib  
-\[16:47\] \<miconda> perhaps henningw or cchance can confirm that  
-\[16:47\] \<dr> yes miconda, we've been testing it , it works  
-\[16:47\] \<miconda> ok  
-\[16:47\] \<iZverg> yes, it compiled but only one server supported  
-\[16:48\] \<henningw> the library has support for more server, i think  
+sooo much more reliable than in 3.3
+\[16:46\] \<miconda> so there are developers for it
+\[16:47\] \<miconda> kolbu: ok
+\[16:47\] \<miconda> dr: I think devel version compiles with that lib
+\[16:47\] \<miconda> perhaps henningw or cchance can confirm that
+\[16:47\] \<dr> yes miconda, we've been testing it , it works
+\[16:47\] \<miconda> ok
+\[16:47\] \<iZverg> yes, it compiled but only one server supported
+\[16:48\] \<henningw> the library has support for more server, i think
 \[16:49\] \<henningw> should be not to hard to extend, patches are as
-always welcome :)  
-\[16:49\] \<henningw> the devel version uses the new library  
-\[16:49\] \<henningw> s/new/good library  
-\[16:49\] \<miconda> ok  
-\[16:49\] \<miconda> anything else on technical aspects?  
-\[16:50\] \<miconda> other modules to add/fix/remove?  
+always welcome :)
+\[16:49\] \<henningw> the devel version uses the new library
+\[16:49\] \<henningw> s/new/good library
+\[16:49\] \<miconda> ok
+\[16:49\] \<miconda> anything else on technical aspects?
+\[16:50\] \<miconda> other modules to add/fix/remove?
 ===== presence_dialoginfo module ===== \[16:50\] \<ZogG_laptop> the
-presence one  
-\[16:50\] \<miconda> ZogG_laptop: what you mentioned already, right?  
-\[16:50\] \<ZogG_laptop> nope  
-\[16:51\] \<ZogG_laptop> improvemnet  
+presence one
+\[16:50\] \<miconda> ZogG_laptop: what you mentioned already, right?
+\[16:50\] \<ZogG_laptop> nope
+\[16:51\] \<ZogG_laptop> improvemnet
 \[16:51\] \<ZogG_laptop> there is force_single mode or something like
-that  
-\[16:51\] \<ZogG_laptop> which would send only 1 state in xml  
-\[16:51\] \<ZogG_laptop> early/confirmed/etc  
-\[16:51\] \<ZogG_laptop> it would pick up mostly randomly  
-\[16:52\] \<miconda> you refer to presence_dialoginfo module?  
+that
+\[16:51\] \<ZogG_laptop> which would send only 1 state in xml
+\[16:51\] \<ZogG_laptop> early/confirmed/etc
+\[16:51\] \<ZogG_laptop> it would pick up mostly randomly
+\[16:52\] \<miconda> you refer to presence_dialoginfo module?
 \[16:52\] \<admorten> I've got a bunch of updates to the sca module to
-pull into 4.x and master.  
-\[16:52\] \<ZogG_laptop> leme check  
-\[16:53\] \<ZogG_laptop> miconda: yes  
+pull into 4.x and master.
+\[16:52\] \<ZogG_laptop> leme check
+\[16:53\] \<ZogG_laptop> miconda: yes
 \[16:53\] \<miconda> admorten: ok, you should do it soon so they get
-tested  
-\[16:53\] \<miconda> ZogG_laptop: ok  
-\[16:53\] \<admorten> Will do.  
+tested
+\[16:53\] \<miconda> ZogG_laptop: ok
+\[16:53\] \<admorten> Will do.
 \[16:53\] \<ZogG_laptop> miconda: the priority should be
-early->confirmed->terminated  
+early->confirmed->terminated
 \[16:53\] \<miconda> ZogG_laptop: again, perhaps opening an item on
-tracker will help not forgetting and checking it  
-\[16:54\] \<dr> having working dialog profiles would be nice  
+tracker will help not forgetting and checking it
+\[16:54\] \<dr> having working dialog profiles would be nice
 \[16:54\] \<ZogG_laptop> miconda: ok. i even may try to get patch for
-this one  
-\[16:54\] \<miconda> ZogG_laptop: that is even better, thanks  
+this one
+\[16:54\] \<miconda> ZogG_laptop: that is even better, thanks
 \[16:54\] \<ZogG_laptop> miconda: it would be better though if it would
-be checked before applied  
-\[16:54\] \<miconda> dr: they seem fine, you have troubles with?  
+be checked before applied
+\[16:54\] \<miconda> dr: they seem fine, you have troubles with?
 \[16:55\] \<admorten> Re: our own sca module deployment. We now have
 8345 SCA subscribers, and I've been hearing from a number of other
-places that they're rolling it out.  
-\[16:55\] \<miconda> ZogG_laptop: sure, they will be reviewed  
-\[16:55\] \<miconda> admorten: nice, thanks for sharing the numbers  
-\[16:55\] \<miconda> admorten: is a single sca server?  
-\[16:56\] \<admorten> Yes, at the moment.  
-\[16:56\] \<dr> # set_dlg_profile("caller", "count");  
+places that they're rolling it out.
+\[16:55\] \<miconda> ZogG_laptop: sure, they will be reviewed
+\[16:55\] \<miconda> admorten: nice, thanks for sharing the numbers
+\[16:55\] \<miconda> admorten: is a single sca server?
+\[16:56\] \<admorten> Yes, at the moment.
+\[16:56\] \<dr> # set_dlg_profile("caller", "count");
 \[16:56\] \<dr> ##
-get_profile_size("caller","count","$avp(callcount)");  
+get_profile_size("caller","count","$avp(callcount)");
 \[16:56\] \<dr> ## xlog("L_INFO","number of simultaneous dialogs:
-$avp(callcount)\\n");  
-\[16:56\] \<miconda> not bad then, for handling lots of xml docs  
-\[16:56\] \<dr> i want it to decrement automatically  
+$avp(callcount)\\n");
+\[16:56\] \<miconda> not bad then, for handling lots of xml docs
+\[16:56\] \<dr> i want it to decrement automatically
 \[16:56\] \<admorten> Right. We have a replicated environment for
-failover.  
-\[16:56\] \<dr> it doesn't , it always increments that counter  
-\[16:56\] \<admorten> miconda: SCA doesn't use XML. :)  
-\[16:56\] \<miconda> admorten: ok, that;s different  
+failover.
+\[16:56\] \<dr> it doesn't , it always increments that counter
+\[16:56\] \<admorten> miconda: SCA doesn't use XML. :)
+\[16:56\] \<miconda> admorten: ok, that;s different
 \[16:57\] \<miconda> but you said at some point that does dialog-info as
-well  
-\[16:57\] \<miconda> or I misunderstood?  
-\[16:57\] \<miconda> or you don't use that part...  
-\[16:57\] \<admorten> That'd be BLA, which we struggled with.  
+well
+\[16:57\] \<miconda> or I misunderstood?
+\[16:57\] \<miconda> or you don't use that part...
+\[16:57\] \<admorten> That'd be BLA, which we struggled with.
 \[16:57\] \<kethzer> Need to know how to enable kamailio to send file
-over a NATED network  
-\[16:57\] \<kethzer> any hel  
-\[16:57\] \<kethzer> help???/  
+over a NATED network
+\[16:57\] \<kethzer> any hel
+\[16:57\] \<kethzer> help???/
 \[16:57\] \<admorten> XML bodies would grow massive, then packet
-fragmentation would overwhelm the handsets.  
-\[16:58\] \<admorten> Inconsistent state across the groups.  
+fragmentation would overwhelm the handsets.
+\[16:58\] \<admorten> Inconsistent state across the groups.
 \[16:58\] \<miconda> dr: it will be decremented when the dialog is
-ended/destroyed  
+ended/destroyed
 \[16:58\] \<miconda> kethzer: you have to wait a bit for support
-questions, we are doing development and admin meeting  
+questions, we are doing development and admin meeting
 \[16:58\] \<dr> miconda, that's what I thought too, but this does not
-happen with my script  
+happen with my script
 \[16:59\] \<dr> i had to put the counter in memcache , and increment /
-decrement manually  
-\[16:59\] \<miconda> I do use it in many places, no problem so far...  
-\[16:59\] \<miconda> what version are you using?  
-\[16:59\] \<dr> 4.0.2  
+decrement manually
+\[16:59\] \<miconda> I do use it in many places, no problem so far...
+\[16:59\] \<miconda> what version are you using?
+\[16:59\] \<dr> 4.0.2
 \[17:00\] \<miconda> you should shift to latest in 4.0 branch, there
-were some fixes for negative replies  
-\[17:00\] \<miconda> or do dialog related things just before t_relay()  
+were some fixes for negative replies
+\[17:00\] \<miconda> or do dialog related things just before t_relay()
 \[17:01\] \<ZogG_laptop> dr:are you trying to get total dialogs per
-subscriber?  
+subscriber?
 \[17:01\] \<dr> and http_query() from the utils module , it might need
 some heavy improvements, it returns only the first line from the
-buffer  
-\[17:01\] \<oej> It is documented to only do that :-)  
-\[17:01\] \<dr> ZogG_laptop, no , total number of dialogs  
+buffer
+\[17:01\] \<oej> It is documented to only do that :-)
+\[17:01\] \<dr> ZogG_laptop, no , total number of dialogs
 ===== http modules ===== \[17:02\] \<oej> But yes, we need improvements
-in http_client  
+in http_client
 \[17:02\] \<oej> Sorry, I would say we need a http_client module that
-consolidates all http clients  
-\[17:02\] \<oej> We have several different ones  
+consolidates all http clients
+\[17:02\] \<oej> We have several different ones
 \[17:02\] \<miconda> dr: speaking of that, I think carstenbock did some
-work on http client lately  
-\[17:03\] \<miconda> but iirc, he pushed on a personal branch  
+work on http client lately
+\[17:03\] \<miconda> but iirc, he pushed on a personal branch
 \[17:03\] \<oej> There's one in utils, one in jsonrpc and one in xcap
-client and possibly sip identy  
-\[17:03\] \<oej> From the top of my head. Some use libcurl.  
+client and possibly sip identy
+\[17:03\] \<oej> From the top of my head. Some use libcurl.
 \[17:03\] \<miconda> oej: right, maybe we should pull out http client
-part from all modules and have one that will be reused  
-\[17:04\] \<oej> I think that would be a good thing moving forward.  
-\[17:04\] \<miconda> jsonrpc client uses netstrings, iirc  
-\[17:04\] \<miconda> is not over http  
+part from all modules and have one that will be reused
+\[17:04\] \<oej> I think that would be a good thing moving forward.
+\[17:04\] \<miconda> jsonrpc client uses netstrings, iirc
+\[17:04\] \<miconda> is not over http
 \[17:04\] \<oej> Then we could get IPv6 in every one and solve happy
-eyeballs once.  
+eyeballs once.
 \[17:04\] \<dr> miconda, thx . one more thing: i don't think the dialog
 module works very good with event_route\[tm:local-request\] either .
-$DLG_TIMEOUT is not getting set  
+$DLG_TIMEOUT is not getting set
 \[17:05\] \<miconda> dr: has to be checked, not using it like that so I
-cannot comment now -- open an issue on tracker to have it in mind  
+cannot comment now -- open an issue on tracker to have it in mind
 \[17:05\] \<miconda> carstenbock: any comments on your recent work on
-http cleint?  
-\[17:05\] \<dr> $DLG_lifetime, sorry  
+http cleint?
+\[17:05\] \<dr> $DLG_lifetime, sorry
 \[17:06\] \<miconda> ok, let's move forward (probably carstenbock has
-left a bit)  
-\[17:06\] \<miconda> anything else on tech stuff?  
-\[17:06\] \<jh> how about mediaproxy-ng module?  
+left a bit)
+\[17:06\] \<miconda> anything else on tech stuff?
+\[17:06\] \<jh> how about mediaproxy-ng module?
 \[17:07\] \<admorten> Question about core support for maximum branches.
 We're currently limited by a 32-bit mask to 30 branches. I have some
 early work moving to 64-bit mask for branch tracking. Anyone else
-interested?  
-===== rtpproxy_ng ===== \[17:07\] \<miconda> jh: rtpproxy_ng?  
-\[17:07\] \<miconda> admorten: yes, could be interesting  
+interested?
+===== rtpproxy_ng ===== \[17:07\] \<miconda> jh: rtpproxy_ng?
+\[17:07\] \<miconda> admorten: yes, could be interesting
 \[17:07\] \<ZogG_laptop> miconda:
-https:*github.com/sipwise/mediaproxy-ng  
-\[17:08\] \<miconda> push the patches somewhere for some review  
-\[17:08\] \<jh> yes, ment rtpproxy-ng (naming is confusing)  
-\[17:08\] \<admorten> miconda: OK  
+https:*github.com/sipwise/mediaproxy-ng
+\[17:08\] \<miconda> push the patches somewhere for some review
+\[17:08\] \<jh> yes, ment rtpproxy-ng (naming is confusing)
+\[17:08\] \<admorten> miconda: OK
 \[17:08\] \<miconda> jh: yes, I know, quite confusing in both sides,
-even the external application  
+even the external application
 \[17:08\] \<admorten> I'll put them up on sip-router tracker and post to
-sr-dev when ready.  
+sr-dev when ready.
 \[17:08\] \<jh> there was some bugs found. will those be fixed before
-next release?  
-\[17:09\] \<miconda> probably yes. I don't see Richard here  
+next release?
+\[17:09\] \<miconda> probably yes. I don't see Richard here
 \[17:09\] \<miconda> but I guess sipwise is highly interested to get all
-bugs closed  
-\[17:09\] \<linuxmaniac> miconda: :yes:  
-\[17:09\] \<miconda> linuxmaniac may be able to comment more  
-\[17:09\] \<miconda> I know some were fixed already  
-\[17:10\] \<miconda> hughw: send some patches as well, e  
-\[17:10\] \<miconda> were they done?  
-\[17:10\] \<linuxmaniac> miconda: afaik yes  
+bugs closed
+\[17:09\] \<linuxmaniac> miconda: :yes:
+\[17:09\] \<miconda> linuxmaniac may be able to comment more
+\[17:09\] \<miconda> I know some were fixed already
+\[17:10\] \<miconda> hughw: send some patches as well, e
+\[17:10\] \<miconda> were they done?
+\[17:10\] \<linuxmaniac> miconda: afaik yes
 
 ## http modules
 
 \[17:10\] \<carstenbock> (sorry for the delay: i just added support for
 POST-requests to the http_query() function. Needs a little bit testing,
-but should be okay)  
+but should be okay)
 \[17:10\] \<miconda> rephrasing: hughw sent some patches to
-rtpproxy-ng  
-\[17:10\] \<linuxmaniac> I think they are been merged  
-\[17:10\] \<miconda> linuxmaniac: ok  
+rtpproxy-ng
+\[17:10\] \<linuxmaniac> I think they are been merged
+\[17:10\] \<miconda> linuxmaniac: ok
 \[17:11\] \<miconda> carstenbock: ok, maybe you should merge on master,
-to be easy to test for not-git gurus :D  
-\[17:11\] \<oej> carstenbock: Using curl?  
+to be easy to test for not-git gurus :D
+\[17:11\] \<oej> carstenbock: Using curl?
 \[17:12\] \<miconda> carstenbock: in short, it was a discussion to make
 a single http client module, as there are few other modules implementing
-one internally  
-\[17:12\] \<carstenbock> miconda: Will do that.  
-\[17:12\] \<carstenbock> oej: Yes.  
-\[17:12\] \<oej> carstenbock: Which module is that?  
-\[17:13\] \<carstenbock> oej: utils  
+one internally
+\[17:12\] \<carstenbock> miconda: Will do that.
+\[17:12\] \<carstenbock> oej: Yes.
+\[17:12\] \<oej> carstenbock: Which module is that?
+\[17:13\] \<carstenbock> oej: utils
 \[17:13\] \<miconda> ZogG_laptop: for clarification - the external
 application is named mediaproxy-ng, but the corresponding module in
-kamailio is named rtprpoxy-ng  
+kamailio is named rtprpoxy-ng
 \[17:14\] \<ZogG_laptop> miconda: yeah, thanks, got it from conversation
-above and some google  
-\[17:14\] \<ZogG_laptop> :)  
+above and some google
+\[17:14\] \<ZogG_laptop> :)
 \[17:14\] \<oej> Ok, so we should propably build an improved http get in
 utils, as well as something similar to json that suspends transaction
-and returns in another route  
+and returns in another route
 \[17:15\] \<ZogG_laptop> i think http get/post would be enuf and what
-would be needed are modules to parse responses (json/xml/whateverelse)  
-\[17:17\] \<miconda> ok, done with tech stuff?  
+would be needed are modules to parse responses (json/xml/whateverelse)
+\[17:17\] \<miconda> ok, done with tech stuff?
 
 ## OpenSSL licence exception
 
-\[17:17\] \<linuxmaniac> openSSL exception licence  
-\[17:17\] \<linuxmaniac> license  
-\[17:18\] \<linuxmaniac> oej: no mail from you on the mail list :-P  
-\[17:18\] \<miconda> linuxmaniac: ok, that was the next in list  
-\[17:18\] \<oej> I did brainstorm about it earlier this week  
-\[17:18\] \<oej> :-)  
-\[17:18\] \<miconda> but I thought of it more admin stuff  
-\[17:19\] \<linuxmaniac> miconda: I can wait :)  
-\[17:19\] \<miconda> no, it is on now  
-\[17:19\] \<miconda> let's discuss it  
-\[17:19\] \<miconda> one way is to implement tls module with gnutls  
+\[17:17\] \<linuxmaniac> openSSL exception licence
+\[17:17\] \<linuxmaniac> license
+\[17:18\] \<linuxmaniac> oej: no mail from you on the mail list :-P
+\[17:18\] \<miconda> linuxmaniac: ok, that was the next in list
+\[17:18\] \<oej> I did brainstorm about it earlier this week
+\[17:18\] \<oej> :-)
+\[17:18\] \<miconda> but I thought of it more admin stuff
+\[17:19\] \<linuxmaniac> miconda: I can wait :)
+\[17:19\] \<miconda> no, it is on now
+\[17:19\] \<miconda> let's discuss it
+\[17:19\] \<miconda> one way is to implement tls module with gnutls
 \[17:20\] \<linuxmaniac> I think is "just" a matter add the exception
-clause  
+clause
 \[17:20\] \<oej> carstenbock: How do I set content-type in the post
-data?  
+data?
 \[17:20\] \<miconda> the other one is getting devels to agree with the
-exception  
-\[17:20\] \<miconda> which most of them will do, but many are gone  
-\[17:20\] \<miconda> from the early stage of ser  
+exception
+\[17:20\] \<miconda> which most of them will do, but many are gone
+\[17:20\] \<miconda> from the early stage of ser
 \[17:20\] \<ZogG_laptop> oh, about that. i got kaamilio 4.x crashed with
-tls when having reregister or two calls at the same time :(  
-\[17:20\] \* ZogG_laptop was talking about tls  
+tls when having reregister or two calls at the same time :(
+\[17:20\] \* ZogG_laptop was talking about tls
 \[17:21\] \<miconda> also, lot of copyright is by fokus, which was sold
-to tekelec which was recently bought by oracle  
-\[17:21\] \<oej> Oh yeah, let's consult Oracle lawyers  
-\[17:21\] \<linuxmaniac> haha  
-\[17:21\] \<miconda> so we may need to buy a beer to Larry  
+to tekelec which was recently bought by oracle
+\[17:21\] \<oej> Oh yeah, let's consult Oracle lawyers
+\[17:21\] \<linuxmaniac> haha
+\[17:21\] \<miconda> so we may need to buy a beer to Larry
 \[17:21\] \<oej> So the problem here is that the tls module is not part
-of linux distros because of this, right?  
-\[17:21\] \<henningw> hehe  
-\[17:21\] \<miconda> ZogG_laptop: do you have a backtrace?  
+of linux distros because of this, right?
+\[17:21\] \<henningw> hehe
+\[17:21\] \<miconda> ZogG_laptop: do you have a backtrace?
 \[17:21\] \<pdunkley> OpenSSL is used by other modules (for access to
-the randomness and crypto routines).  
+the randomness and crypto routines).
 \[17:22\] \<linuxmaniac> oej: I can't add tls on Debian because of
-that  
+that
 \[17:22\] \<pdunkley> websocket, outbound, auth_ephemeral all link to it
-- BTW I am fine with the exception.  
-\[17:22\] \<oej> Yes, there's a few modules that Debian won't accept  
+- BTW I am fine with the exception.
+\[17:22\] \<oej> Yes, there's a few modules that Debian won't accept
 \[17:22\] \<miconda> linuxmaniac: the question is, all devs have to
-agree?  
-\[17:22\] \<oej> so we can clear those three modules  
+agree?
+\[17:22\] \<oej> so we can clear those three modules
 \[17:22\] \<ZogG_laptop> miconda: no here for sure. but i think i can
-emulate it anytime  
+emulate it anytime
 \[17:22\] \<miconda> linuxmaniac: or only devs to the modules that link
-to openssl?  
+to openssl?
 \[17:23\] \<miconda> because the core doesn't link to openssl, only few
-modules (tls among them)  
+modules (tls among them)
 \[17:23\] \<ZogG_laptop> afaik i just read of some sip lib that switched
-for smaller lib for tls/ssl instead of openssl  
+for smaller lib for tls/ssl instead of openssl
 \[17:23\] \<linuxmaniac> miconda: don't know, but I will say just the
-ones that use openssl  
+ones that use openssl
 \[17:23\] \<miconda> ZogG_laptop: a backtrace would be good and
-eventually the log with debug=3  
+eventually the log with debug=3
 \[17:23\] \<oej> What is the background of the TLS module, was code
-moved from the core to that?  
+moved from the core to that?
 \[17:24\] \<ZogG_laptop> miconda: would try to get one to you thru
-maillist or tracker next week  
-\[17:24\] \<miconda> linuxmaniac: that would be easier  
-\[17:24\] \<pdunkley> Other modules are tls, osp, stun, auth_identity  
-\[17:24\] \<miconda> Andrei reimplemented tls module  
-\[17:24\] \<miconda> nothing from old openser core was used for it  
+maillist or tracker next week
+\[17:24\] \<miconda> linuxmaniac: that would be easier
+\[17:24\] \<pdunkley> Other modules are tls, osp, stun, auth_identity
+\[17:24\] \<miconda> Andrei reimplemented tls module
+\[17:24\] \<miconda> nothing from old openser core was used for it
 \[17:24\] \<miconda> I guess pdunkley has nothing against to agree for
-websocket module  
+websocket module
 \[17:25\] \<pdunkley> Some of the stun stuff is mine, but most has been
 moved from Kamailio core. For my part I am happy with an exception for
-stun too (but the original author will need to confirm as well)  
+stun too (but the original author will need to confirm as well)
 \[17:25\] \<linuxmaniac> miconda: I can try to ask on debian-legal and
-see what they say  
-\[17:25\] \<miconda> stun and auth_identity is from iptel.org guys  
+see what they say
+\[17:25\] \<miconda> stun and auth_identity is from iptel.org guys
 \[17:25\] \<miconda> linuxmaniac: please do it, so we know what we have
-to do  
+to do
 \[17:25\] \<oej> pdunkley has three modules to disclaim, but that should
-be fine  
-\[17:25\] \<linuxmaniac> miconda: noted  
+be fine
+\[17:25\] \<linuxmaniac> miconda: noted
 \[17:25\] \<miconda> linuxmaniac: mention also that we package tls
-module separately  
+module separately
 \[17:26\] \<ZogG_laptop> linphone apprantly switched from openssl to
-https:*polarssl.org/  
-\[17:26\] \<miconda> is not part of other package  
-\[17:26\] \<oej> can we get agreement fron Andrei?  
+https:*polarssl.org/
+\[17:26\] \<miconda> is not part of other package
+\[17:26\] \<oej> can we get agreement fron Andrei?
 \[17:26\] \<linuxmaniac> miconda: I will send you the mail draft before
-send it to them  
+send it to them
 \[17:27\] \<pdunkley> Just checked, I can remove the OpenSSL dependency
-from stun with a trivial code change.  
-\[17:27\] \<linuxmaniac> but anyways we have to add the exception  
-\[17:27\] \<pdunkley> I am happy to disclaim my modules.  
-\[17:27\] \<miconda> oej: probably iptelorg  
+from stun with a trivial code change.
+\[17:27\] \<linuxmaniac> but anyways we have to add the exception
+\[17:27\] \<pdunkley> I am happy to disclaim my modules.
+\[17:27\] \<miconda> oej: probably iptelorg
 \[17:27\] \<pdunkley> That means websocket, stun, outbound, and
-auth_ephemeral are fine.  
+auth_ephemeral are fine.
 \[17:27\] \<miconda> but at least we know the target, I will get in
-touch if it all we need  
-\[17:27\] \<oej> miconda: back to larry  
-\[17:27\] \<pdunkley> Leaves just tls, osp, and auth_identity  
+touch if it all we need
+\[17:27\] \<oej> miconda: back to larry
+\[17:27\] \<pdunkley> Leaves just tls, osp, and auth_identity
 \[17:28\] \<miconda> for osp I can approach the company that developed
-it  
-\[17:28\] \<oej> Transnexus  
+it
+\[17:28\] \<oej> Transnexus
 \[17:28\] \<miconda> although they were not very active, I guess they
-have nothing against  
-\[17:28\] \<miconda> oej: yes  
-\[17:28\] \<miconda> but not sure how many users that module has  
+have nothing against
+\[17:28\] \<miconda> oej: yes
+\[17:28\] \<miconda> but not sure how many users that module has
 \[17:28\] \<oej> Auth_identity was a school, that should possibly be
-fine if we can track someone down  
+fine if we can track someone down
 \[17:28\] \<miconda> afaik, only that company had a solution to work
-with it  
-\[17:29\] \<oej> tls is a tough nut to crack and an important one  
-\[17:29\] \<miconda> yes, tls is the one that needs it most ...  
-\[17:30\] \<miconda> the other important one, websocket, is fine  
-\[17:30\] \<miconda> for stun, I guess we can reimplement it  
-\[17:30\] \<miconda> doesn't look that hard  
-\[17:30\] \<miconda> and is not big  
-\[17:30\] \<miconda> tls has lot of code, on the other hand  
-\[17:30\] \<oej> Yep.  
+with it
+\[17:29\] \<oej> tls is a tough nut to crack and an important one
+\[17:29\] \<miconda> yes, tls is the one that needs it most ...
+\[17:30\] \<miconda> the other important one, websocket, is fine
+\[17:30\] \<miconda> for stun, I guess we can reimplement it
+\[17:30\] \<miconda> doesn't look that hard
+\[17:30\] \<miconda> and is not big
+\[17:30\] \<miconda> tls has lot of code, on the other hand
+\[17:30\] \<oej> Yep.
 \[17:31\] \<ZogG_laptop> ok i'm off. bye and goood luck to every one adn
-thanks for help.  
+thanks for help.
 \[17:31\] \<miconda> but first let's see what linuxmaniac gets from
-debian-legal and then I will see how to approach for tls + stun  
-\[17:31\] \<miconda> ZogG_laptop: thanks for joining!  
-\[17:31\] \<miconda> anything else about openssl exception?  
-\[17:31\] \<linuxmaniac> ok then  
+debian-legal and then I will see how to approach for tls + stun
+\[17:31\] \<miconda> ZogG_laptop: thanks for joining!
+\[17:31\] \<miconda> anything else about openssl exception?
+\[17:31\] \<linuxmaniac> ok then
 \[17:32\] \<ZogG_laptop> and before i go i would paste again — may be
 polarssl can be replacement for openssl as it mentioned on their site
 curl/openvpn and others are using it and afaik linphone switched ot it
-lately  
-\[17:32\] \<ZogG_laptop> bye  
-\[17:32\] \<miconda> thanks, bye  
-===== github clone ===== \[17:32\] \<miconda> next admin stuff: github  
-\[17:32\] \<miconda> Andreas Granig secured kamailio name on github  
+lately
+\[17:32\] \<ZogG_laptop> bye
+\[17:32\] \<miconda> thanks, bye
+===== github clone ===== \[17:32\] \<miconda> next admin stuff: github
+\[17:32\] \<miconda> Andreas Granig secured kamailio name on github
 \[17:33\] \<miconda> pdunkley and few others expressed the willingness
-to maintain a clone of the repo there  
-\[17:33\] \<linuxmaniac> we have a mirror at sipwise  
+to maintain a clone of the repo there
+\[17:33\] \<linuxmaniac> we have a mirror at sipwise
 \[17:33\] \<pdunkley> Github would work best if that was the primary
-repo.  
+repo.
 \[17:34\] \<miconda> so, do we get enough work force to maintain a
-clone  
+clone
 \[17:34\] \<pdunkley> Biggest advantage of Github is fork management
-etc.  
+etc.
 \[17:34\] \<miconda> pdunkley: from Andreas I understood is a matter of
-some scripts to merge back and forth  
+some scripts to merge back and forth
 \[17:34\] \<miconda> but in case of conflicts, someone has to care of
-...  
-\[17:34\] \<pdunkley> Yes.  
-\[17:35\] \<pdunkley> I suppose that is true.  
+...
+\[17:34\] \<pdunkley> Yes.
+\[17:35\] \<pdunkley> I suppose that is true.
 \[17:35\] \<linuxmaniac> pdunkley: but you can fork with no problem
-afaik  
+afaik
 \[17:35\] \<pdunkley> But it needs to be more than a simple clone,
 because if someone forks on Github and makes a push request that is
-accepted, then the repo on Github is updated.  
+accepted, then the repo on Github is updated.
 \[17:35\] \<miconda> the current repo is tied to many scripts and hooks
-around, so it will be quite some work not to keep it anyhow  
-\[17:35\] \<oej> why did we leave sourceforge?  
+around, so it will be quite some work not to keep it anyhow
+\[17:35\] \<oej> why did we leave sourceforge?
 \[17:36\] \<miconda> besides the fact that github started to have issues
-(e.g., availability)  
+(e.g., availability)
 \[17:36\] \<linuxmaniac> pdunkley: the thing is that you have to do git
-am on our repo not github  
+am on our repo not github
 \[17:36\] \<miconda> oej: when we merged the code, we had svn on
-sourceforge and ser was cvs on berlios  
-\[17:36\] \<miconda> we needed root privileges :-)  
-\[17:36\] \<miconda> to make things fit together  
+sourceforge and ser was cvs on berlios
+\[17:36\] \<miconda> we needed root privileges :-)
+\[17:36\] \<miconda> to make things fit together
 \[17:37\] \<henningw> sf.org had also some issues that time (they still
 have). One reason to go for a dedicated git was to have the flexibility
-to merge the repos  
-\[17:37\] \<oej> Right.  
-\[17:37\] \<miconda> pdunkley: will not be a read only clone  
-\[17:37\] \<oej> Will we end up in the same situation with github  
-\[17:37\] \<miconda> github can get updates directly there  
-\[17:37\] \<miconda> the scripts have to do sync both ways  
+to merge the repos
+\[17:37\] \<oej> Right.
+\[17:37\] \<miconda> pdunkley: will not be a read only clone
+\[17:37\] \<oej> Will we end up in the same situation with github
+\[17:37\] \<miconda> github can get updates directly there
+\[17:37\] \<miconda> the scripts have to do sync both ways
 \[17:38\] \<miconda> Andreas said is something they do as well for some
-of their repos  
-\[17:38\] \<linuxmaniac> afaik github is just a mirror for us  
+of their repos
+\[17:38\] \<linuxmaniac> afaik github is just a mirror for us
 \[17:38\] \<pdunkley> I guess the big question is whether enough people
-think that Github provides advantages to the project.  
-\[17:38\] \<linuxmaniac> no changes from github onto our repo  
+think that Github provides advantages to the project.
+\[17:38\] \<linuxmaniac> no changes from github onto our repo
 \[17:39\] \<miconda> linuxmaniac: check sr-dev for Andreas' email on
-this topic  
+this topic
 \[17:39\] \<pdunkley> My thinking is that the Github forking is a
 somewhat nicer model than having developers with lots of branches, and
 allows non-developers to work under source control without it
-automatically affecting the main project.  
+automatically affecting the main project.
 \[17:40\] \<miconda> pdunkley: agree that there could be good benefits.
 on the other hand, not keeping current one as the main one will be tough
-and lot of work  
+and lot of work
 \[17:41\] \<miconda> so, at least have to keep/try both for a while just
-to see if github is good  
+to see if github is good
 \[17:41\] \<linuxmaniac> miconda: "Everytime you push something to the
 internal repo, the github repo gets automatically synced and
-overwritten"  
-\[17:41\] \<linuxmaniac> so no changes from github on our repo  
+overwritten"
+\[17:41\] \<linuxmaniac> so no changes from github on our repo
 \[17:42\] \<miconda> linuxmaniac: "people have the possibility to send
-pull requests and everything"  
-\[17:43\] \<linuxmaniac> miconda: yes  
-\[17:43\] \<linuxmaniac> but no merge is done  
-\[17:43\] \<miconda> so I assumed they are used ...  
+pull requests and everything"
+\[17:43\] \<linuxmaniac> miconda: yes
+\[17:43\] \<linuxmaniac> but no merge is done
+\[17:43\] \<miconda> so I assumed they are used ...
 \[17:43\] \<linuxmaniac> miconda: you have to use git am on the "master"
-repo  
+repo
 \[17:43\] \<pdunkley> linuxmaniac, miconda: but does the internal repo
-get sync'd and overwritten everytime the github repo is changed?  
-\[17:44\] \<linuxmaniac> pdunkley: no changes are done on github  
-\[17:44\] \<linuxmaniac> this is just "read-only"  
-\[17:44\] \<pdunkley> OK. That's my point.  
+get sync'd and overwritten everytime the github repo is changed?
+\[17:44\] \<linuxmaniac> pdunkley: no changes are done on github
+\[17:44\] \<linuxmaniac> this is just "read-only"
+\[17:44\] \<pdunkley> OK. That's my point.
 \[17:44\] \<carstenbock> I am definitely no GIT expert, but the current
 solution "works for me". Are there somewhere a list of what would be
-exactly better if we switch (or create a mirror on) to github?  
+exactly better if we switch (or create a mirror on) to github?
 \[17:44\] \<pdunkley> If we don't make changes on Github, we can't use
-Github push requests etc for merging.  
-\[17:44\] \<pdunkley> So there is no advantage to Github.  
+Github push requests etc for merging.
+\[17:44\] \<pdunkley> So there is no advantage to Github.
 \[17:45\] \<pdunkley> carstenbock: there was a discussion on the mailing
 list. But it boils down to better developer management, and merging plus
-integrated tracker that relates issues to commits.  
+integrated tracker that relates issues to commits.
 \[17:46\] \<linuxmaniac> pdunkley: just a nice web interface and the
-pull-request are received as mails  
-\[17:46\] \<eloycoto> we can use <http://gitlab.org/> in our server  
+pull-request are received as mails
+\[17:46\] \<eloycoto> we can use <http://gitlab.org/> in our server
 \[17:46\] \<miconda> pdunkley: maybe there are tutorials to do sync two
-ways  
-\[17:47\] \<miconda> I thought Andreas said they do merge on both ways  
-\[17:47\] \<miconda> maybe was on some private conversation  
+ways
+\[17:47\] \<miconda> I thought Andreas said they do merge on both ways
+\[17:47\] \<miconda> maybe was on some private conversation
 \[17:48\] \<miconda> but the actual question here: if we can get it two
 ways sync, who is on board to configure it initially and then supervise
-it?  
+it?
 \[17:48\] \<linuxmaniac> miconda: he is just in front of me. No changes
-from github  
-\[17:48\] \<miconda> linuxmaniac: ok  
-\[17:48\] \<miconda> i misunderstood  
+from github
+\[17:48\] \<miconda> linuxmaniac: ok
+\[17:48\] \<miconda> i misunderstood
 \[17:48\] \<pdunkley> I am happy to help with some of this. Not sure
 what time I have over the next couple of months as I am travelling a
-lot.  
-\[17:49\] \<pdunkley> It's conference season :-(  
+lot.
+\[17:49\] \<pdunkley> It's conference season :-(
 \[17:49\] \<miconda> this comes also to another point related to
-administration  
+administration
 ===== technical administration group ===== \[17:50\] \<miconda> building
-a tech admin group  
-\[17:50\] \<miconda> with volunteers  
-\[17:50\] \<miconda> to care of various aspects of the project  
-\[17:50\] \<miconda> including releases, sysadmin work on servers  
+a tech admin group
+\[17:50\] \<miconda> with volunteers
+\[17:50\] \<miconda> to care of various aspects of the project
+\[17:50\] \<miconda> including releases, sysadmin work on servers
 \[17:50\] \<linuxmaniac> miconda: I'm still single, I have some time
-free. haha  
-\[17:50\] \<miconda> typically was me, Henning and Jan  
-\[17:50\] \<miconda> linuxmaniac: great  
-\[17:51\] \<miconda> you are more than welcome to join  
-\[17:51\] \<linuxmaniac> that will be great  
-\[17:51\] \<oej> I can help more with the web site.  
+free. haha
+\[17:50\] \<miconda> typically was me, Henning and Jan
+\[17:50\] \<miconda> linuxmaniac: great
+\[17:51\] \<miconda> you are more than welcome to join
+\[17:51\] \<linuxmaniac> that will be great
+\[17:51\] \<oej> I can help more with the web site.
 \[17:51\] \<qxork> Would love to help out. LOD.com is also interested in
-donating servers, etc.  
+donating servers, etc.
 \[17:52\] \<miconda> also, in this tech admin group, I want to be able
 to take some decissions regarding what software to use when we need
-something new, etc…  
-\[17:52\] \<oej> qxork: I am willing to receive donations! Haha.  
-\[17:52\] \<linuxmaniac> miconda: sounds reasonable  
+something new, etc…
+\[17:52\] \<oej> qxork: I am willing to receive donations! Haha.
+\[17:52\] \<linuxmaniac> miconda: sounds reasonable
 \[17:53\] \<miconda> ok, so here we have linuxmaniac, oej, qxork and
-pdunkley (as volunteered for github stuff)  
-\[17:53\] \<miconda> just as summary  
-\[17:53\] \<miconda> me and Henning will stay in as well  
+pdunkley (as volunteered for github stuff)
+\[17:53\] \<miconda> just as summary
+\[17:53\] \<miconda> me and Henning will stay in as well
 \[17:53\] \<miconda> anyone else interested to join is welcome (after
-some security clearance :-D )  
-\[17:55\] \<miconda> ok then, will ask also on mailing list  
-\[17:55\] \<miconda> happy that we have a core group formed here  
-\[17:55\] \<oej> Darn, does that mean I'm out. The security clearance?  
-\[17:55\] \<oej> Yes, that's progress. Thanks for inviting us Miconda.  
+some security clearance :-D )
+\[17:55\] \<miconda> ok then, will ask also on mailing list
+\[17:55\] \<miconda> happy that we have a core group formed here
+\[17:55\] \<oej> Darn, does that mean I'm out. The security clearance?
+\[17:55\] \<oej> Yes, that's progress. Thanks for inviting us Miconda.
 \[17:55\] \<miconda> web access only doesn't require the high level
-:-)  
-\[17:55\] \<oej> Oh dear. Well, it's a start :-)  
+:-)
+\[17:55\] \<oej> Oh dear. Well, it's a start :-)
 \[17:56\] \<oej> You can ask NSA about me… Obviously they know it all
-now.  
-\[17:56\] \<miconda> :-)  
-\[17:56\] \<miconda> ok, next topic (not to get late here)  
-\[17:56\] \<carstenbock> oej: They have known for years!  
+now.
+\[17:56\] \<miconda> :-)
+\[17:56\] \<miconda> ok, next topic (not to get late here)
+\[17:56\] \<carstenbock> oej: They have known for years!
 ===== Kamailio World 2014 ===== \[17:57\] \<miconda> Kamailio World 2014
 -- I want to know if there are dates that should be avoided from mid
-March to mid May next year  
+March to mid May next year
 \[17:57\] \<miconda> apart of obvious dates for Easter (orthodox and
-catholic)  
+catholic)
 \[17:58\] \<miconda> and other public holidays in Germany (because all
-will be closed)  
+will be closed)
 \[17:58\] \<miconda> anyone aware of conferences, events that we should
-not overlap?  
+not overlap?
 \[17:58\] \<oej> Possibly April Fool's day because no one will believe
-what you say  
-\[17:58\] \<oej> I only see IETF, but that's March 3-7  
+what you say
+\[17:58\] \<oej> I only see IETF, but that's March 3-7
 \[17:58\] \<miconda> the plan is to have it again in Berlin, being easy
-with administration  
-\[17:59\] \<miconda> and good/cheap to reach from EU  
-\[17:59\] \<carstenbock> miconda: That's great! I'm in! :-)  
-\[17:59\] \<oej> Berlin Works fine.  
-\[17:59\] \<miconda> oej: April 1 looks as good candidate, thoug :-)  
+with administration
+\[17:59\] \<miconda> and good/cheap to reach from EU
+\[17:59\] \<carstenbock> miconda: That's great! I'm in! :-)
+\[17:59\] \<oej> Berlin Works fine.
+\[17:59\] \<miconda> oej: April 1 looks as good candidate, thoug :-)
 \[18:00\] \<miconda> anyway, keep in mind and ping me if you discover
-something  
-\[18:00\] \<linuxmaniac> let's see if I can attend :/  
+something
+\[18:00\] \<linuxmaniac> let's see if I can attend :/
 \[18:00\] \<oej> Well, then we can easily release Kamailio 5.0 for
-Windows supporting Lync  
-\[18:00\] \<oej> ..and skype… and… WhatsApp  
+Windows supporting Lync
+\[18:00\] \<oej> ..and skype… and… WhatsApp
 \[18:00\] \<miconda> I'll make some proposals soon, once I see
-availability of locations  
+availability of locations
 \[18:00\] \<pdunkley> If you're going to do a Lync release it should be
-"Kamailio One" like the latest Xbox...  
-\[18:00\] \<linuxmaniac> :)  
+"Kamailio One" like the latest Xbox...
+\[18:00\] \<linuxmaniac> :)
 \[18:01\] \<oej> Scchhh. The marketing dept wanted that to be a
-secret.  
+secret.
 ===== Other world wide events ===== \[18:01\] \<miconda> other world
-wide events?  
-\[18:01\] \<miconda> pdunkley seems already busy  
+wide events?
+\[18:01\] \<miconda> pdunkley seems already busy
 \[18:01\] \<miconda> I will go to Astricon and most probably Fosdem, in
-the near future  
-\[18:02\] \<miconda> although fosdem is next year  
-\[18:02\] \<oej> I will be at ElastixWorld and Voip2day  
-\[18:02\] \<oej> voip2day is in November  
-\[18:02\] \<qxork> Olympics  
+the near future
+\[18:02\] \<miconda> although fosdem is next year
+\[18:02\] \<oej> I will be at ElastixWorld and Voip2day
+\[18:02\] \<oej> voip2day is in November
+\[18:02\] \<qxork> Olympics
 \[18:02\] \<pdunkley> I'm currently planning AstriCon, WebRTC Expo
-(November), DevCon5 (December), and FOSDEM.  
+(November), DevCon5 (December), and FOSDEM.
 \[18:02\] \<miconda> so, if anyone goes to events, add news on the
-website  
-\[18:02\] \<miconda> or ask us if you don't have write access  
+website
+\[18:02\] \<miconda> or ask us if you don't have write access
 \[18:02\] \<pdunkley> Also Telecoms API conference in London in
-November.  
-\[18:02\] \<oej> Where's WebRTC expo?  
-\[18:03\] \<pdunkley> oej: Santa Clara. DevCon5 is in LA.  
-\[18:03\] \<oej> We need URLs folks, send us the URLs  
+November.
+\[18:02\] \<oej> Where's WebRTC expo?
+\[18:03\] \<pdunkley> oej: Santa Clara. DevCon5 is in LA.
+\[18:03\] \<oej> We need URLs folks, send us the URLs
 \[18:03\] \<qxork> I will be at Astricon this year from 2013-10-07 to
-2013-10-10  
+2013-10-10
 \[18:03\] \<pdunkley> Might be some events at Google Campus London
-coming up too.  
+coming up too.
 \[18:03\] \<oej> We should have a pre-FOSDEM meeting. ANy dates set for
-Fosdem?  
-\[18:03\] \<pdunkley> oej: FOSDEM 14 website is up  
-\[18:03\] \<miconda> oej: the rule was first weekend in Feb  
-\[18:04\] \<miconda> I guess they didn't change  
-\[18:04\] \<pdunkley> Telecom APIs: http:*iir-telecoms.com/  
+Fosdem?
+\[18:03\] \<pdunkley> oej: FOSDEM 14 website is up
+\[18:03\] \<miconda> oej: the rule was first weekend in Feb
+\[18:04\] \<miconda> I guess they didn't change
+\[18:04\] \<pdunkley> Telecom APIs: http:*iir-telecoms.com/
 \[18:05\] \<pdunkley> WebRTC Conference:
-http:*www.webrtcworld.com/conference/west/  
+http:*<www.webrtcworld.com/conference/west/>
 \[18:05\] \<pdunkley> DevCon5:
-http:*www.html5report.com/conference/california/  
-\[18:05\] \<linuxmaniac> oej: 1&2 of Feb  
+http:*<www.html5report.com/conference/california/>
+\[18:05\] \<linuxmaniac> oej: 1&2 of Feb
 \[18:05\] \<pdunkley> Someone from Crocodile will be at the Upperside
 WebRTC conference in Paris in December too.
-http:*www.uppersideconferences.com/webrtc2013/webrtc2013intro.html  
-\[18:06\] \<pdunkley> oej: URLs a plenty  
-\[18:06\] \<oej> THank you!  
+http:*<www.uppersideconferences.com/webrtc2013/webrtc2013intro.html>
+\[18:06\] \<pdunkley> oej: URLs a plenty
+\[18:06\] \<oej> THank you!
 \[18:06\] \<miconda> ok, looks like we don't miss many events out there
-:-)  
-\[18:07\] \<miconda> so last on agenda  
-\[18:07\] \<miconda> next major release  
-\[18:07\] \<pdunkley> Actually we miss loads :-)  
-\[18:07\] \<pdunkley> Too many events.  
-\[18:07\] \<miconda> pdunkley: I know  
+:-)
+\[18:07\] \<miconda> so last on agenda
+\[18:07\] \<miconda> next major release
+\[18:07\] \<pdunkley> Actually we miss loads :-)
+\[18:07\] \<pdunkley> Too many events.
+\[18:07\] \<miconda> pdunkley: I know
 \[18:07\] \<pdunkley> Anyone here going to TADS in Thailand (at the same
-time as the November WebRTC conference)?  
+time as the November WebRTC conference)?
 \[18:07\] \<miconda> even in Berlin are like 2-3 per week that look
-interesting  
+interesting
 \[18:07\] \<carstenbock> Exactly: For example FOKUS FUSECO Conference in
-November (<http://www.fuseco-forum.org>), i will be there.  
+November (<http://www.fuseco-forum.org>), i will be there.
 \[18:08\] \<miconda> pdunkley: don't think so, I got an invite, but I
-can't make it, planning for some trainings instead  
+can't make it, planning for some trainings instead
 \[18:08\] \<pdunkley> Must be someone who can find the budget for
-Thailand ;-)  
+Thailand ;-)
 \[18:08\] \<oej> I need to work… Three weeks on the road in October will
-be expensive.  
-\[18:09\] \<miconda> :-) maybe you get donations  
-===== 4.1 release planning ===== \[18:09\] \<miconda> back to 4.1  
-\[18:09\] \<oej> Is that the skype/lync release?  
-\[18:10\] \<miconda> do you think we can freeze by end of september?  
-\[18:10\] \<carstenbock> oej: No that would be Kamailio One.  
-\[18:10\] \<miconda> any big dev plans still for it?  
+be expensive.
+\[18:09\] \<miconda> :-) maybe you get donations
+===== 4.1 release planning ===== \[18:09\] \<miconda> back to 4.1
+\[18:09\] \<oej> Is that the skype/lync release?
+\[18:10\] \<miconda> do you think we can freeze by end of september?
+\[18:10\] \<carstenbock> oej: No that would be Kamailio One.
+\[18:10\] \<miconda> any big dev plans still for it?
 \[18:10\] \<carstenbock> I hope, i get the documentation ready for
-IMS-Charging (Diameter-Ro).  
+IMS-Charging (Diameter-Ro).
 \[18:10\] \<pdunkley> I have some additions I want to make to
 auth_ephemeral over the next couple of weeks. But I am happy with
-websocket, stun, and outbound now.  
+websocket, stun, and outbound now.
 \[18:10\] \<oej> I have some new functionality in snmp to work with. I
-hope to complete it soon.  
-\[18:10\] \<oej> Fighting with net-snmp...  
+hope to complete it soon.
+\[18:10\] \<oej> Fighting with net-snmp...
 \[18:11\] \<kethzer> Any help with Kamailio NAT configuration I am
-unable to send file might be NATED issue  
-\[18:11\] \<kethzer> ?  
+unable to send file might be NATED issue
+\[18:11\] \<kethzer> ?
 \[18:11\] \<carstenbock> kethzer: We are still in the developers
-meeting...  
+meeting...
 \[18:11\] \<oej> kethzer: Please send e-mail to sr-users and you will
-get answers. We're in the middle of a meeting  
+get answers. We're in the middle of a meeting
 \[18:12\] \<miconda> ok, i have one or two modules in mind, but they can
-wait if I don't have the time  
+wait if I don't have the time
 \[18:12\] \<pdunkley> I'd like to address some of the issues with MSRP,
-but I won't have the time.  
-\[18:12\] \<miconda> so, let's plan freezing for end of the month  
-\[18:13\] \<carstenbock> Okay.  
-\[18:13\] \<miconda> if need it, we can prolong a bit  
-\[18:13\] \<miconda> otherwise, is going to be time also for the 4.2  
+but I won't have the time.
+\[18:12\] \<miconda> so, let's plan freezing for end of the month
+\[18:13\] \<carstenbock> Okay.
+\[18:13\] \<miconda> if need it, we can prolong a bit
+\[18:13\] \<miconda> otherwise, is going to be time also for the 4.2
 ===== TLS enchancements ===== \[18:13\] \<pdunkley> oej: have you had
-any success with getting your TLS enhancements.  
-\[18:13\] \<miconda> we need new features for that version too  
+any success with getting your TLS enhancements.
+\[18:13\] \<miconda> we need new features for that version too
 \[18:13\] \<oej> I have had no time for TLS. Just applied for funding
-for working with it.  
-\[18:13\] \<oej> Personally I got lost in the code.  
+for working with it.
+\[18:13\] \<oej> Personally I got lost in the code.
 \[18:14\] \<pdunkley> You wanted to be able to set conditions on whether
-to use a new connection when you call t_relay()?  
+to use a new connection when you call t_relay()?
 \[18:14\] \<oej> Yes, after TLS connect I want to inspect certificates
 and decide if we're going to send the message or close the connection
-and fail.  
+and fail.
 \[18:14\] \<pdunkley> Something like if the connection didn't get
 negotiated/validated the way you wanted you could choose not to use
-it.  
+it.
 \[18:15\] \<pdunkley> Ah yes. That was what I suggested the xavp for. I
-remember now.  
-\[18:15\] \<pdunkley> Need to find a friendly TLS module expert :-)  
-\[18:15\] \<oej> Yep.  
+remember now.
+\[18:15\] \<pdunkley> Need to find a friendly TLS module expert :-)
+\[18:15\] \<oej> Yep.
 \[18:15\] \<oej> At some point I would like to add DANE support
-according to the draft I wrote.  
-\[18:16\] \<oej> We do have DNSsec.  
+according to the draft I wrote.
+\[18:16\] \<oej> We do have DNSsec.
 \[18:16\] \<miconda> oej: hmm, you wrote the draft before the code?!?!
-that's not good…  
+that's not good…
 \[18:16\] \<pdunkley> oej: this security stuff will never take off. NSA
-and GCHQ are listening anyway.  
-\[18:16\] \<oej> Yes, we should enable null ciphers by default.  
+and GCHQ are listening anyway.
+\[18:16\] \<oej> Yes, we should enable null ciphers by default.
 \[18:17\] \<oej> I run Kamailio through some TLS tests but could not get
-it to be approved. There's updates needed somewhere.  
-\[18:17\] \<miconda> any official topic to discuss?  
-\[18:17\] \<oej> I am happy to see interest in DMQ  
-\[18:17\] \<miconda> any other official topic to discuss?  
-\[18:18\] \<miconda> oej: yes, glad that cchance jumped in  
-\[18:18\] \<oej> IPv6 support in all modules  
-\[18:18\] \<miconda> we will grant git access  
+it to be approved. There's updates needed somewhere.
+\[18:17\] \<miconda> any official topic to discuss?
+\[18:17\] \<oej> I am happy to see interest in DMQ
+\[18:17\] \<miconda> any other official topic to discuss?
+\[18:18\] \<miconda> oej: yes, glad that cchance jumped in
+\[18:18\] \<oej> IPv6 support in all modules
+\[18:18\] \<miconda> we will grant git access
 \[18:18\] \<oej> Should we try to set that as requirement for the next
-release?  
-\[18:18\] \<miconda> oej: those I use have ipv6  
-\[18:18\] \<oej> Or 4.2 at least  
-\[18:18\] \<miconda> only the provider doesn't have  
+release?
+\[18:18\] \<miconda> oej: those I use have ipv6
+\[18:18\] \<oej> Or 4.2 at least
+\[18:18\] \<miconda> only the provider doesn't have
 \[18:18\] \<oej> I noticed that json was hard coded to the IPv4 legacy
-protocol  
-\[18:19\] \<oej> I haven't reviewed the others.  
+protocol
+\[18:19\] \<oej> I haven't reviewed the others.
 \[18:19\] \<pdunkley> oej: I remember people saying IPv6 was needed
-right now back when I was at university. That was 15 years ago.  
-\[18:19\] \<pdunkley> IPv4 still working for me ;-)  
-\[18:19\] \<oej> 15 years ago I had ping6 working on Windows PCs!  
+right now back when I was at university. That was 15 years ago.
+\[18:19\] \<pdunkley> IPv4 still working for me ;-)
+\[18:19\] \<oej> 15 years ago I had ping6 working on Windows PCs!
 \[18:20\] \<oej> We should at least have that as a requirement for new
-modules  
+modules
 \[18:20\] \<pdunkley> All my Amazon servers are IPv4 only. Think it'll
-take a miracle to get them onto IPv6.  
-\[18:20\] \<oej> Or just a tunnel from sixxs.net  
-\[18:20\] \<carstenbock> IPv6 is quite important.  
-\[18:21\] \<oej> I will set up a Hall of shame list on the wiki.  
-\[18:21\] \<carstenbock> It's a big topic with german ISPs.  
-\[18:21\] \<oej> Cool.  
-\[18:21\] \<carstenbock> Kamailio IMS is IPv6 ready... :-)  
+take a miracle to get them onto IPv6.
+\[18:20\] \<oej> Or just a tunnel from sixxs.net
+\[18:20\] \<carstenbock> IPv6 is quite important.
+\[18:21\] \<oej> I will set up a Hall of shame list on the wiki.
+\[18:21\] \<carstenbock> It's a big topic with german ISPs.
+\[18:21\] \<oej> Cool.
+\[18:21\] \<carstenbock> Kamailio IMS is IPv6 ready... :-)
 \[18:21\] \<pdunkley> oej: need to make sure you tell the Hall of Shame
-entrants you've added them. Might help get them moving :-)  
-\[18:22\] \*\*\* QbY nennt sich jetzt QbY_AFK.  
+entrants you've added them. Might help get them moving :-)
+\[18:22\] \*\*\* QbY nennt sich jetzt QbY_AFK.
 \[18:22\] \<oej> Oh yes, you will know the moment we nail you to that
-wiki.  
+wiki.
 \[18:23\] \<voipjedijoe> Hey QbY how do i check by fault to see if it
-happens before session progress  
-\[18:23\] \<oej> …he said with a dark voice  
+happens before session progress
+\[18:23\] \<oej> …he said with a dark voice
 \[18:23\] \<oej> We're still working on Happy Eyeballs for UDP in the
-SIP Forum IPv6 wg…  
-\[18:23\] \<carstenbock> Any other topics?  
-\[18:23\] \<oej> --none--  
-===== open discussion ===== \[18:24\] \<miconda> ok  
+SIP Forum IPv6 wg…
+\[18:23\] \<carstenbock> Any other topics?
+\[18:23\] \<oej> --none--
+===== open discussion ===== \[18:24\] \<miconda> ok
 \[18:24\] \<miconda> I will follow up with some emails in the next
-days  
+days
 \[18:24\] \<miconda> about releases, and major suggestions here,
-etc...  
+etc...
 \[18:24\] \<carstenbock> miconda: Thanks for the great work & organizing
-everything around Kamailio!  
-\[18:25\] \<miconda> thanks everyone for participating!  
-\[18:25\] \<linuxmaniac> I've to leave, see you guys!  
-\[18:25\] \<miconda> linuxmaniac: married?!?  
-\[18:25\] \<miconda> carstenbock: welcome!  
-\[18:25\] \<oej> thank you everyone!  
-\[18:25\] \<linuxmaniac> miconda: see you next month :-P  
-\[18:25\] \<miconda> :-) will be fun  
-\[18:26\] \<miconda> better beer than in Alicante last winter  
-\[18:26\] \<linuxmaniac> miconda: sure  
-\[18:26\] \<oej> Going to Astricon?  
-\[18:26\] \<qxork> oej: yes  
+everything around Kamailio!
+\[18:25\] \<miconda> thanks everyone for participating!
+\[18:25\] \<linuxmaniac> I've to leave, see you guys!
+\[18:25\] \<miconda> linuxmaniac: married?!?
+\[18:25\] \<miconda> carstenbock: welcome!
+\[18:25\] \<oej> thank you everyone!
+\[18:25\] \<linuxmaniac> miconda: see you next month :-P
+\[18:25\] \<miconda> :-) will be fun
+\[18:26\] \<miconda> better beer than in Alicante last winter
+\[18:26\] \<linuxmaniac> miconda: sure
+\[18:26\] \<oej> Going to Astricon?
+\[18:26\] \<qxork> oej: yes
 \[18:26\] \<miconda> btw, free discussion now, not anymore in
-transcripts :-)  
-\[18:26\] \<linuxmaniac> miconda: some are on me  
-\[18:26\] \<oej> See you there!  
-\[18:26\] \<miconda> oej: yes  
+transcripts :-)
+\[18:26\] \<linuxmaniac> miconda: some are on me
+\[18:26\] \<oej> See you there!
+\[18:26\] \<miconda> oej: yes
 \[18:26\] \<oej> — This chat room is now open for normal
-questions/answers/thoughts/recommendations and SIPpy things  
-\[18:26\] \<miconda> qxork: I think I have some emails to reply  
-\[18:26\] \<qxork> Yeni is staying home this year.  
-\[18:27\] \<miconda> just got my laptop back  
-\[18:27\] \<qxork> home as in, the bakery  
+questions/answers/thoughts/recommendations and SIPpy things
+\[18:26\] \<miconda> qxork: I think I have some emails to reply
+\[18:26\] \<qxork> Yeni is staying home this year.
+\[18:27\] \<miconda> just got my laptop back
+\[18:27\] \<qxork> home as in, the bakery
 \[18:27\] \<pdunkley> So there will be quite a Kamailio gathering at
-AstriCon.  
-\[18:27\] \<qxork> miconda: I hate timemachine, btw  
-\[18:27\] \<pdunkley> oej: I see you're doing a keynote  
-\[18:27\] \<oej> Yep I am. Short one.  
-\[18:27\] \<miconda> qxork: proved to be the hdd cable  
-\[18:27\] \<miconda> so all data is intact  
+AstriCon.
+\[18:27\] \<qxork> miconda: I hate timemachine, btw
+\[18:27\] \<pdunkley> oej: I see you're doing a keynote
+\[18:27\] \<oej> Yep I am. Short one.
+\[18:27\] \<miconda> qxork: proved to be the hdd cable
+\[18:27\] \<miconda> so all data is intact
 \[18:27\] \<voipjedijoe> hey everyone, I am having an issue with
 dispatcher not failing over calls to the next destination when kamailio
-gets back a 503  
-\[18:27\] \<voipjedijoe> any suggestions on how to fix that?  
-\[18:27\] \<oej> qxork: Say hello to Yeni!  
+gets back a 503
+\[18:27\] \<voipjedijoe> any suggestions on how to fix that?
+\[18:27\] \<oej> qxork: Say hello to Yeni!
 \[18:28\] \<miconda> I had backups, but still would have killed lot of
-time to restore  
-\[18:28\] \<qxork> oej: =)  
+time to restore
+\[18:28\] \<qxork> oej: =)
 \[18:28\] \<miconda> voipjedijoe: do you intercept 503 in failure
-route?  
-\[18:28\] \<oej> Ok, dinner time. See you around folks!  
-\[18:28\] \<qxork> Talk with all of you soon!  
-\[18:28\] \<qxork> cheers.  
-\[18:29\] \<voipjedijoe> no at the moment I only intercept on 500s  
+route?
+\[18:28\] \<oej> Ok, dinner time. See you around folks!
+\[18:28\] \<qxork> Talk with all of you soon!
+\[18:28\] \<qxork> cheers.
+\[18:29\] \<voipjedijoe> no at the moment I only intercept on 500s
 \[18:29\] \<voipjedijoe> I need to intercept the 503 but only when it's
 coming from my freeswitch and not sessioned by my vendor via
-freeswitch  
-\[18:29\] \<voipjedijoe> it's an odd problem me thinks  
+freeswitch
+\[18:29\] \<voipjedijoe> it's an odd problem me thinks
 \[18:29\] \<miconda> voipjedijoe: add also 503 in the condition to
-re-route in falure_route  
+re-route in falure_route
 \[18:30\] \<miconda> iirc, 503 should be replaced by 500 when
-forwarding  
-\[18:30\] \<miconda> so you should get 503 only from fs  
-\[18:30\] \<miconda> otherwise is hard to detect  
+forwarding
+\[18:30\] \<miconda> so you should get 503 only from fs
+\[18:30\] \<miconda> otherwise is hard to detect
 \[18:30\] \<miconda> unless fs adds some custom reason phrase or special
-header  
+header
 \[18:31\] \<voipjedijoe> I agree, but what if my vendor sends me a 503
 and I need to session that to my customer. If I add the 503 to my
-reroute condition all 503s would get rerouted  
+reroute condition all 503s would get rerouted
 \[18:31\] \<voipjedijoe> and since in fs I am getting this when I hit
 max sessions or max cpu on freeswitch I don't think I can add a customer
-header  
+header
 \[18:33\] \<miconda> you can use different failure routes for sending to
-freeswitch  
-\[18:33\] \<miconda> you send to customers and then to freeswitch?  
-\[18:33\] \<miconda> or what's the routing logic  
+freeswitch
+\[18:33\] \<miconda> you send to customers and then to freeswitch?
+\[18:33\] \<miconda> or what's the routing logic
 \[18:34\] \<voipjedijoe> invite to kam-lb --> route via dispatcher to
-fs  
+fs
 \[18:34\] \<miconda> kethzer: for the nat problem, you would need to
-send some network traces  
-\[18:34\] \<miconda> so you better use mailing list  
+send some network traces
+\[18:34\] \<miconda> so you better use mailing list
 \[18:35\] \<voipjedijoe> I always get a 100 trying back from freeswitch
-and then if I hit a limit I get a 503 Maximum Calls In Progress.  
-\[18:36\] \<miconda> so when you get other 503?  
+and then if I hit a limit I get a 503 Maximum Calls In Progress.
+\[18:36\] \<miconda> so when you get other 503?
 \[18:36\] \<QbY> voipjedijoe: so, have your invite come handled by
 route_a, set a variable, the moment you see the 100 in the on_reply,
-change that variable..  
+change that variable..
 \[18:36\] \<QbY> if you see a 503, first check that variable, if that
 variable says you haven't seen the 100 then send it to your next
-destination  
-\[18:36\] \<voipjedijoe> I don't know how to do that  
+destination
+\[18:36\] \<voipjedijoe> I don't know how to do that
 \[18:37\] \<voipjedijoe> ok but I get a 100 back from freeswitch all the
-time  
+time
 \[18:37\] \<QbY>
-http:*kamailio.org/dokuwiki/doku.php/pseudovariables:3.1.x  
+http:*kamailio.org/dokuwiki/doku.php/pseudovariables:3.1.x
 \[18:37\] \<QbY> you shouldn't see a 100 if FS is rejecting the call
-because of max sessions  
-\[18:37\] \<voipjedijoe> I am  
+because of max sessions
+\[18:37\] \<voipjedijoe> I am
 \[18:38\] \<voipjedijoe> I currently have one of my fs servers set to a
 max sessions of 2 at the moment, which will allow me 1 complete call.
-Once I fill up that call I get a 503 back after I get a 100  
-\[18:38\] \<voipjedijoe> its xrazy  
-\[18:39\] \* QbY looks at something  
-\[18:39\] \<voipjedijoe> what do you mean?  
+Once I fill up that call I get a 503 back after I get a 100
+\[18:38\] \<voipjedijoe> its xrazy
+\[18:39\] \* QbY looks at something
+\[18:39\] \<voipjedijoe> what do you mean?
 \[18:40\] \<QbY> voipjedijoe: what do you have for
-sip-options-respond-503-on-busy in sofia?  
+sip-options-respond-503-on-busy in sofia?
 \[18:41\] \<QbY>
-http://wiki.freeswitch.org/wiki/Sofia.conf.xml#SIP_Related_options  
+<http://wiki.freeswitch.org/wiki/Sofia.conf.xml#SIP_Related_options>
 \[18:41\] \<voipjedijoe> I looked at this, but it seems to only be for
-option requests  
-\[18:44\] \<voipjedijoe> so I just tested that, and I still get a 503  
-\[18:45\] \<QbY> after getting a 100?  
-\[18:47\] \<voipjedijoe> yep  
-\[18:49\] \<voipjedijoe> I could change it in the c  
-\[18:49\] \<voipjedijoe> but that doesn't seem like the best idea  
+option requests
+\[18:44\] \<voipjedijoe> so I just tested that, and I still get a 503
+\[18:45\] \<QbY> after getting a 100?
+\[18:47\] \<voipjedijoe> yep
+\[18:49\] \<voipjedijoe> I could change it in the c
+\[18:49\] \<voipjedijoe> but that doesn't seem like the best idea

docs/devel/irc-meetings/2014alog.md

@@ -3,127 +3,127 @@
 ## outstanding issues at this time, if any
 
 \[2014-05-14 16:06:41\] \<miconda> apparently is a race for cleaning up
-dialog which goes from initial state to terminated state  
-\[2014-05-14 16:06:44\] \<miconda> reported recentrly  
+dialog which goes from initial state to terminated state
+\[2014-05-14 16:06:44\] \<miconda> reported recentrly
 \[2014-05-14 16:07:04\] \<miconda> i looked a bit, couldn’t reproduce,
-but I expect is under high load  
+but I expect is under high load
 \[2014-05-14 16:07:25\] \<miconda> as a lead now, could be due to
-pre/post-script callbacks  
+pre/post-script callbacks
 \[2014-05-14 16:07:25\] \<abalashov> I also brought up the topic of
 CONFIRMED_NA dialogs getting stuck until dialog_timeout, but with no
-response (that I saw).  
+response (that I saw).
 \[2014-05-14 16:08:06\] \<miconda> abalashov: yes, together with delayed
-release of event route reported by osas  
-\[2014-05-14 16:08:16\] \<miconda> will make a bit of work on dialog  
+release of event route reported by osas
+\[2014-05-14 16:08:16\] \<miconda> will make a bit of work on dialog
 \[2014-05-14 16:08:41\] \<miconda> which might end up in getting rid of
-dependency on tm … which is not that useful, imo  
+dependency on tm … which is not that useful, imo
 \[2014-05-14 16:08:59\] \<miconda> dialog can handle the requests and
-replies by itself  
-\[2014-05-14 16:09:04\] \<miconda> i will see  
+replies by itself
+\[2014-05-14 16:09:04\] \<miconda> i will see
 \[2014-05-14 16:09:15\] \<abalashov> Agree that knowledge of transaction
 state is not really essential to dialog functionality; it's just
-convenient.  
+convenient.
 \[2014-05-14 16:09:35\] \<miconda> it is not exported to dialog api in
-any way  
+any way
 \[2014-05-14 16:09:45\] \<oej> Doesn't other modules that depend on
-dialog depend on transaction state?  
-\[2014-05-14 16:09:48\] \<oej> Like dialog  
+dialog depend on transaction state?
+\[2014-05-14 16:09:48\] \<oej> Like dialog
 \[2014-05-14 16:09:48\] \<miconda> just convenience in matching replies
-some time  
+some time
 \[2014-05-14 16:09:50\] \<abalashov> And can sometimes break things --
 if dialog-altering sequential request comes through but in some way
 improperly (say, no Route set) and TM doesn't trigger the right
-callbacks / doesn't know about the transaction.  
+callbacks / doesn't know about the transaction.
 \[2014-05-14 16:10:15\] \<miconda> oej: what do you mean with ‘Like
-dialog’?  
+dialog’?
 \[2014-05-14 16:10:22\] \<oej>
-<http://kamailio.org/docs/modules/devel/modules/pua_dialoginfo.html>  
-\[2014-05-14 16:10:25\] \<oej> Depends on dialog  
-\[2014-05-14 16:10:35\] \<miconda> ahh, ok, pua_dialoginfo  
+<http://kamailio.org/docs/modules/devel/modules/pua_dialoginfo.html>
+\[2014-05-14 16:10:25\] \<oej> Depends on dialog
+\[2014-05-14 16:10:35\] \<miconda> ahh, ok, pua_dialoginfo
 \[2014-05-14 16:10:43\] \<oej> And dialoginfo shows transaction states
-of the invite trans  
+of the invite trans
 \[2014-05-14 16:10:46\] \<miconda> no, they don’t depend on transaction
-state  
-\[2014-05-14 16:10:56\] \<miconda> only on dialog states  
-\[2014-05-14 16:10:59\] \<oej> according to the spec it does  
+state
+\[2014-05-14 16:10:56\] \<miconda> only on dialog states
+\[2014-05-14 16:10:59\] \<oej> according to the spec it does
 \[2014-05-14 16:11:18\] \<miconda> well, the states are initial,
-ringing, confirmed  
+ringing, confirmed
 \[2014-05-14 16:11:46\] \<osas> dialog relies on tm for getting back
-replies  
+replies
 \[2014-05-14 16:11:46\] \<miconda> which correspond to some of
-transaction states, but in the code, dialog doesn’t propagate tm info  
-\[2014-05-14 16:12:57\] \<osas> no, it doesn't  
+transaction states, but in the code, dialog doesn’t propagate tm info
+\[2014-05-14 16:12:57\] \<osas> no, it doesn't
 \[2014-05-14 16:13:06\] \<abalashov> miconda, it seems I neglected to
 see your reply on the CONFIRMED_NA topic ...
 <http://lists.sip-router.org/pipermail/sr-dev/2014-April/023862.html> --
-sorry for the misapprehension.  
+sorry for the misapprehension.
 \[2014-05-14 16:13:58\] \<abalashov> miconda: The proxy does get BYEs in
 this scenario, but because the dialog is not yet confirmed+established
-they do not result in tearing down the dialog.  
-\[2014-05-14 16:14:11\] \<miconda> abalashov: ok  
+they do not result in tearing down the dialog.
+\[2014-05-14 16:14:11\] \<miconda> abalashov: ok
 \[2014-05-14 16:14:36\] \<abalashov> miconda: This generally happens due
 to 200 OK-CANCEL race, but can also happen due to malformed ACKs and
-whatnot.  
+whatnot.
 \[2014-05-14 16:14:41\] \<miconda> found another one recently, when the
-dialog was not destroyed on timeout if bye failed to be sent  
+dialog was not destroyed on timeout if bye failed to be sent
 \[2014-05-14 16:15:05\] \<miconda> to conclude, dialog needs a bit of
-hammering :-)  
+hammering :-)
 \[2014-05-14 16:15:07\] \<abalashov> Dialog is a very messy piece of the
 proxy, it just happens to be very extremely useful in the applied
-dimension.  
-\[2014-05-14 16:16:30\] \<miconda> other issues?  
+dimension.
+\[2014-05-14 16:16:30\] \<miconda> other issues?
 \[2014-05-14 16:17:30\] \<abalashov> miconda: I hear you on setting the
 dialog timeout to one timer prior to ACK and another after, but maybe
 there should be a separate timeout setting for unconfirmed dialogs? Or
-is that asking too much?  
+is that asking too much?
 \[2014-05-14 16:17:40\] \<abalashov> miconda: It's an extremely common
-problem in high-pace environments due to 200 OK/CANCEL race.  
+problem in high-pace environments due to 200 OK/CANCEL race.
 \[2014-05-14 16:18:17\] \<miconda> abalashov: separate timeout can be
-added indeed  
+added indeed
 \[2014-05-14 16:18:26\] \<abalashov> miconda: I'd be willing to work on
-that.  
+that.
 \[2014-05-14 16:18:36\] \<abalashov> miconda: Problem is it's so
-difficult to simulate a 200 OK/CANCEL race deliberately.  
+difficult to simulate a 200 OK/CANCEL race deliberately.
 \[2014-05-14 16:19:07\] \<abalashov> miconda: I might take the approach
 of sending some bullshit ACK instead. Maybe with the wrong From tag.
 That reliably works, I know from unfortunate personal experience with
-the VOS3000.  
+the VOS3000.
 \[2014-05-14 16:19:20\] \<miconda> abalashov: we will give you a free
-license for devel purposes  
+license for devel purposes
 \[2014-05-14 16:19:21\] \<abalashov> (or rather, wrong To tag,
-actually)  
-\[2014-05-14 16:19:22\] \<miconda> :-)  
+actually)
+\[2014-05-14 16:19:22\] \<miconda> :-)
 \[2014-05-14 16:20:13\] \<linuxmaniac> sorry for asking but what is the
-difference between dialog and dialog_ng?  
+difference between dialog and dialog_ng?
 \[2014-05-14 16:20:26\] \<abalashov> That's a good question. I am
-unclear on this as well.  
-\[2014-05-14 16:20:51\] \<miconda> dialog_ng - dialog = \_ng  
-\[2014-05-14 16:20:59\] \<abalashov> Hah!  
+unclear on this as well.
+\[2014-05-14 16:20:51\] \<miconda> dialog_ng - dialog = \_ng
+\[2014-05-14 16:20:59\] \<abalashov> Hah!
 \[2014-05-14 16:21:09\] \<miconda> \_ng version is an attempt to rework
-dialog  
+dialog
 \[2014-05-14 16:21:11\] \<abalashov> linuxmaniac: In theory it is
 supposed to be a next generation dialog module that deals better with
-spirals and forking.  
+spirals and forking.
 \[2014-05-14 16:21:19\] \<abalashov> linuxmaniac: In practice I am
-unsure as to what the practical difference is at this point.  
-\[2014-05-14 16:21:21\] \<miconda> it was a discussion some time ago  
+unsure as to what the practical difference is at this point.
+\[2014-05-14 16:21:21\] \<miconda> it was a discussion some time ago
 \[2014-05-14 16:21:41\] \<miconda> but apparently dialog_ng doesn’t have
-all features of dialog  
+all features of dialog
 \[2014-05-14 16:21:50\] \<abalashov> Right, so in practice I don't see
-it being so usable.  
+it being so usable.
 \[2014-05-14 16:21:59\] \<miconda> there is a wiki page about the
-discusion on dialog_ng  
-\[2014-05-14 16:22:08\] \<linuxmaniac> but, is anyone working on it?  
+discusion on dialog_ng
+\[2014-05-14 16:22:08\] \<linuxmaniac> but, is anyone working on it?
 \[2014-05-14 16:22:19\] \<carstenbock> We are making heavy use of
-dialog_ng for IMS topics.  
+dialog_ng for IMS topics.
 \[2014-05-14 16:22:22\] \<miconda> and, if i got it right, is mostly ims
-oriented now  
-\[2014-05-14 16:22:26\] \<miconda> the ims devs  
-\[2014-05-14 16:22:32\] \<carstenbock> Here we are!  
+oriented now
+\[2014-05-14 16:22:26\] \<miconda> the ims devs
+\[2014-05-14 16:22:32\] \<carstenbock> Here we are!
 \[2014-05-14 16:22:55\] \<linuxmaniac> any plans to get all the features
-of dialog?  
+of dialog?
 \[2014-05-14 16:23:01\] \<abalashov> Nevertheless, this is likely to be
-confusing to the general public and newbies and so on.  
+confusing to the general public and newbies and so on.
 \[2014-05-14 16:23:01\] \<caruizdiaz> by Jason Penton: "Dialog2 is a
 start at the following:
 <http://www.kamailio.org/dokuwiki/doku.php/modules-new-design:dialog-module-design>
@@ -131,948 +131,948 @@ We needed this functionality for the IMS modules. In IMS a proxy can
 take the same session in both terminating and originating modes (ie 2
 dialogs for the same session). dialog 1 does not support this. Dialog2
 has been tested to at least support the functionality we required and we
-will build  
+will build
 \[2014-05-14 16:23:03\] \<miconda> so carstenbock can say the diff
-between dialog and dialog_ng  
+between dialog and dialog_ng
 \[2014-05-14 16:23:13\] \<caruizdiaz> dialog2 was the original name of
-dialog_ng  
+dialog_ng
 \[2014-05-14 16:23:45\] \<abalashov> My personal reading when I first
 ran into it was, "Oh, it's \_ng, that sounds like some avant garde
 stuff, I don't think I'll use it." But in the case of rtpproxy_ng this
-would be incorrect thinking. :-)  
-\[2014-05-14 16:23:59\] \<linuxmaniac> :-)  
-\[2014-05-14 16:24:17\] \<qxork> avant garde  
-\[2014-05-14 16:24:18\] \<linuxmaniac> now we don't have any \_ng  
-\[2014-05-14 16:24:25\] \<abalashov> Yeah, I know.  
+would be incorrect thinking. :-)
+\[2014-05-14 16:23:59\] \<linuxmaniac> :-)
+\[2014-05-14 16:24:17\] \<qxork> avant garde
+\[2014-05-14 16:24:18\] \<linuxmaniac> now we don't have any \_ng
+\[2014-05-14 16:24:25\] \<abalashov> Yeah, I know.
 \[2014-05-14 16:24:34\] \<abalashov> rtpengine_ng - specially for IMS
-:-)  
+:-)
 \[2014-05-14 16:24:45\] \<carstenbock> At the moment the development on
-the dialog_ng module is on "per demand" basis.  
+the dialog_ng module is on "per demand" basis.
 \[2014-05-14 16:24:58\] \<caruizdiaz> AFAIR, the only missing thing in
-dialog_ng, is the full database support  
+dialog_ng, is the full database support
 \[2014-05-14 16:25:15\] \<linuxmaniac> so there is no intension to
-replace dialog with dialog_ng in the long term  
+replace dialog with dialog_ng in the long term
 \[2014-05-14 16:25:30\] \<abalashov> ... contrary to the triumphant
-announcement in the dialog_ng documentation ...  
+announcement in the dialog_ng documentation ...
 \[2014-05-14 16:26:26\] \<linuxmaniac> I'm just asking because it seems
-dialog need some work  
+dialog need some work
 \[2014-05-14 16:26:30\] \<caruizdiaz> maybe in a future. Currently I
-believe it would be impractical to do that.  
-\[2014-05-14 16:26:58\] \<linuxmaniac> OK, moving on  
+believe it would be impractical to do that.
+\[2014-05-14 16:26:58\] \<linuxmaniac> OK, moving on
 \[2014-05-14 16:27:33\] \<abalashov> caruizdiaz: I think the dialog_ng
 module should perhaps be amended to take a more moderate stance, then.
 As it is written now, it states, "El nuevo dialog! Viva la
-revolucion!"  
-\[2014-05-14 16:27:42\] \<abalashov> caruizdiaz: + documentation  
-\[2014-05-14 16:28:03\] \<oej> +7  
+revolucion!"
+\[2014-05-14 16:27:42\] \<abalashov> caruizdiaz: + documentation
+\[2014-05-14 16:28:03\] \<oej> +7
 \[2014-05-14 16:28:48\] \<carstenbock> Maybe an option would be, to
-rename dialog_ng to dialog_ims, to reduce the confusion.  
+rename dialog_ng to dialog_ims, to reduce the confusion.
 \[2014-05-14 16:29:09\] \<carstenbock> (at least as long as it's mostly
-used for IMS)  
+used for IMS)
 \[2014-05-14 16:29:09\] \<caruizdiaz> abalashov: jajajaj, maybe yes, but
 I don't think it is affecting the new comers. I did not read any inquiry
-or doubt about which of them to use.  
-\[2014-05-14 16:29:26\] \<carstenbock> True...  
-\[2014-05-14 16:29:31\] \<miconda> ok, so are we done?  
+or doubt about which of them to use.
+\[2014-05-14 16:29:26\] \<carstenbock> True...
+\[2014-05-14 16:29:31\] \<miconda> ok, so are we done?
 \[2014-05-14 16:29:34\] \<oej> We had it in a release so it's late for
-rename  
-\[2014-05-14 16:29:43\] \<miconda> with dlg vs dlg_ng …  
+rename
+\[2014-05-14 16:29:43\] \<miconda> with dlg vs dlg_ng …
 \[2014-05-14 16:29:46\] \<oej> But improving the docs is a good thing to
-avoid any confusion  
-\[2014-05-14 16:29:52\] \<carstenbock> Okay, agreed.  
-\[2014-05-14 16:30:11\] \<linuxmaniac> done  
+avoid any confusion
+\[2014-05-14 16:29:52\] \<carstenbock> Okay, agreed.
+\[2014-05-14 16:30:11\] \<linuxmaniac> done
 \[2014-05-14 16:30:12\] \<oej> Assigned to carstenbock aka "The IMS
-Guy"  
-\[2014-05-14 16:30:23\] \<carstenbock> Damn!  
-\[2014-05-14 16:30:24\] \<carstenbock> :-)  
-\[2014-05-14 16:30:26\] \<caruizdiaz> :D:D  
-\[2014-05-14 16:30:42\] \<javar> :)  
+Guy"
+\[2014-05-14 16:30:23\] \<carstenbock> Damn!
+\[2014-05-14 16:30:24\] \<carstenbock> :-)
+\[2014-05-14 16:30:26\] \<caruizdiaz> :D:D
+\[2014-05-14 16:30:42\] \<javar> :)
 
 ## major release
 
-\[2014-05-14 16:31:04\] \<miconda> most probably autumn time frame  
+\[2014-05-14 16:31:04\] \<miconda> most probably autumn time frame
 \[2014-05-14 16:31:55\] \<miconda> it fits the development cycle
 interval and I guess summer is not the ideal for testing a frozen
-branch  
+branch
 \[2014-05-14 16:32:26\] \<miconda> perhaps we can decide the date to
-freeze development at the end of summer, via mailing list  
-\[2014-05-14 16:32:39\] \<oej> +1  
-\[2014-05-14 16:32:44\] \<oej> What's new?  
-\[2014-05-14 16:32:51\] \<oej> Event stuff  
+freeze development at the end of summer, via mailing list
+\[2014-05-14 16:32:39\] \<oej> +1
+\[2014-05-14 16:32:44\] \<oej> What's new?
+\[2014-05-14 16:32:51\] \<oej> Event stuff
 \[2014-05-14 16:32:52\] \<miconda> i think there are like 3 new modules
-now  
+now
 \[2014-05-14 16:32:53\] \<abalashov> Will it be Kamailio 5.0? :) Or is
-it time for it to become Kamailio Vista?  
+it time for it to become Kamailio Vista?
 \[2014-05-14 16:33:11\] \<miconda> plus quite a lot in other old
-modules  
-\[2014-05-14 16:33:12\] \<caruizdiaz> :D  
-\[2014-05-14 16:33:20\] \<oej> Kamailio 95  
-\[2014-05-14 16:33:27\] \<oej> Inspired by SAAB 95  
+modules
+\[2014-05-14 16:33:12\] \<caruizdiaz> :D
+\[2014-05-14 16:33:20\] \<oej> Kamailio 95
+\[2014-05-14 16:33:27\] \<oej> Inspired by SAAB 95
 \[2014-05-14 16:33:29\] \<miconda> afaik, there are 3-4 modules to be
-added soon …  
-\[2014-05-14 16:33:30\] \<oej> (of course)  
-\[2014-05-14 16:33:33\] \<oej> What's that?  
-\[2014-05-14 16:33:36\] \<qxork> Kamailio_NG  
+added soon …
+\[2014-05-14 16:33:30\] \<oej> (of course)
+\[2014-05-14 16:33:33\] \<oej> What's that?
+\[2014-05-14 16:33:36\] \<qxork> Kamailio_NG
 \[2014-05-14 16:34:00\] \<miconda> two erlang modules are on github in a
-different repo  
+different repo
 \[2014-05-14 16:34:08\] \<abalashov> Actually, I assume it will be
-Kamailio 4.2. Right?  
+Kamailio 4.2. Right?
 \[2014-05-14 16:34:19\] \<miconda> i discussed with the developer, he
-wants more polishing before incorporating them  
-\[2014-05-14 16:34:32\] \<oej> Erlang? Cool.  
-\[2014-05-14 16:34:45\] \<caruizdiaz> do you have the links?  
+wants more polishing before incorporating them
+\[2014-05-14 16:34:32\] \<oej> Erlang? Cool.
+\[2014-05-14 16:34:45\] \<caruizdiaz> do you have the links?
 \[2014-05-14 16:35:04\] \<miconda> one module by kazoo guys to be
 reviewed and adjusted to be more generic if it is the case (on github as
-well)  
+well)
 \[2014-05-14 16:35:25\] \<miconda> caruizdiaz: searching on github
-should reveal them  
-\[2014-05-14 16:35:28\] \<linuxmaniac> No Go yet?  
-\[2014-05-14 16:35:38\] \<caruizdiaz> ok, tks  
+should reveal them
+\[2014-05-14 16:35:28\] \<linuxmaniac> No Go yet?
+\[2014-05-14 16:35:38\] \<caruizdiaz> ok, tks
 \[2014-05-14 16:35:56\] \<abalashov> linuxmaniac: No indeed, and neither
-Haskell.  
+Haskell.
 \[2014-05-14 16:36:12\] \<miconda> the developer of json modules said at
 some point in time that they refactored, but i haven’t seen any updates
-yet  
+yet
 \[2014-05-14 16:36:40\] \<abalashov> miconda: Has there been any
-movement on the topic of how exactly the evapi should work?  
-\[2014-05-14 16:36:57\] \<miconda> abalashov: “at your will”  
-\[2014-05-14 16:37:03\] \<miconda> no format enforced now  
+movement on the topic of how exactly the evapi should work?
+\[2014-05-14 16:36:57\] \<miconda> abalashov: “at your will”
+\[2014-05-14 16:37:03\] \<miconda> no format enforced now
 \[2014-05-14 16:37:12\] \<abalashov> What about subscriptions and
-filtering?  
+filtering?
 \[2014-05-14 16:38:25\] \<miconda> nothing yet — looks like a busy
-summer for you :-)  
-\[2014-05-14 16:38:34\] \<abalashov> :-)  
+summer for you :-)
+\[2014-05-14 16:38:34\] \<abalashov> :-)
 \[2014-05-14 16:38:53\] \<abalashov> Previously I had done all this with
-uac_req_send().  
-\[2014-05-14 16:38:57\] \<abalashov> This offers a novel approach.  
+uac_req_send().
+\[2014-05-14 16:38:57\] \<abalashov> This offers a novel approach.
 \[2014-05-14 16:39:29\] \<miconda> to conclude, I’m sure there will be
-plenty of new modules by the time of the next major release  
-\[2014-05-14 16:39:38\] \<oej> Cool  
+plenty of new modules by the time of the next major release
+\[2014-05-14 16:39:38\] \<oej> Cool
 \[2014-05-14 16:40:01\] \<miconda> those are what I am aware at this
-time to be on pipeline  
+time to be on pipeline
 \[2014-05-14 16:40:16\] \<abalashov> Are there are any defunct and
-unmaintained modules that should be deprecated?  
+unmaintained modules that should be deprecated?
 \[2014-05-14 16:40:39\] \<abalashov> I have my eye on 'seas', not sure
-what it's status is.  
+what it's status is.
 \[2014-05-14 16:40:41\] \<miconda> and maybe 1-2 more from me … let’s
-see how the time goes  
-\[2014-05-14 16:40:44\] \<abalashov> \*its  
-\[2014-05-14 16:40:54\] \<miconda> seas should work ok  
-\[2014-05-14 16:41:07\] \<stangrze> hi  
+see how the time goes
+\[2014-05-14 16:40:44\] \<abalashov> \*its
+\[2014-05-14 16:40:54\] \<miconda> seas should work ok
+\[2014-05-14 16:41:07\] \<stangrze> hi
 \[2014-05-14 16:41:08\] \<miconda> iirc, some stuff related to tcp was
-missing there  
-\[2014-05-14 16:41:19\] \<miconda> but for udp, should be no problems  
+missing there
+\[2014-05-14 16:41:19\] \<miconda> but for udp, should be no problems
 \[2014-05-14 16:41:58\] \<abalashov> I get lots of questions about
 fleshing out the Kamailio SNMP MIB with something more useful, since
-bellheads love SNMP.  
+bellheads love SNMP.
 \[2014-05-14 16:42:08\] \<miconda> and, being asked up here, it’s going
-to be 4.2.0  
+to be 4.2.0
 \[2014-05-14 16:42:13\] \<abalashov> I always just tell them to wrap
-custom OIDs with kamctl queries.  
+custom OIDs with kamctl queries.
 \[2014-05-14 16:42:38\] \<miconda> 5.0 when we deprecate ipv4 and we
-support ipv6 and ipv9  
-\[2014-05-14 16:42:48\] \<abalashov> aka Kamailio Vista  
+support ipv6 and ipv9
+\[2014-05-14 16:42:48\] \<abalashov> aka Kamailio Vista
 \[2014-05-14 16:43:07\] \<stangrze> erlang module is at
-github.com/stangrze/sip-router-erlang-module  
+github.com/stangrze/sip-router-erlang-module
 \[2014-05-14 16:43:45\] \<miconda> abalashov: should not be hard to add
-to snmpstats, oej did latel several of them  
+to snmpstats, oej did latel several of them
 \[2014-05-14 16:43:59\] \<miconda> stangrze: hello! thanks for the link
-to erlang module  
+to erlang module
 \[2014-05-14 16:44:00\] \<stangrze> its quite usable now, would
-appreciate is someone dares to test it wit dome complex config  
+appreciate is someone dares to test it wit dome complex config
 \[2014-05-14 16:44:01\] \<caruizdiaz> topic suggestion:
-modifying/enhancing the db api to support nosql databases  
+modifying/enhancing the db api to support nosql databases
 \[2014-05-14 16:44:22\] \<miconda> stangrze: i was just going to ask
-abotu the state  
-\[2014-05-14 16:44:25\] \<stangrze> ...some..  
+abotu the state
+\[2014-05-14 16:44:25\] \<stangrze> ...some..
 \[2014-05-14 16:44:49\] \<miconda> stangrze: going to see if I can hunt
-some erlang fans  
+some erlang fans
 \[2014-05-14 16:45:21\] \<miconda> stangrze: perhaps testing will come
-easier for everyone when the module gets into main repo  
+easier for everyone when the module gets into main repo
 \[2014-05-14 16:45:42\] \<stangrze> database interface for srdb1 is
 quite complete, you can use boss_db app to connect to mysql database,
-and it should doo all stuff  
+and it should doo all stuff
 \[2014-05-14 16:46:26\] \<miconda> ok, let’s conclude with major
-release: autumn, decision on date by end of summer  
+release: autumn, decision on date by end of summer
 \[2014-05-14 16:47:14\] \<stangrze> i got busy with broadcom's
 as-feature-event stuff i need for my work, than i'll get back to
-erlang  
-\[2014-05-14 16:47:39\] \<abalashov> stangrze: You mean Broadsoft? :)  
-\[2014-05-14 16:47:53\] \<stangrze> broadsoft, sory ;-)  
+erlang
+\[2014-05-14 16:47:39\] \<abalashov> stangrze: You mean Broadsoft? :)
+\[2014-05-14 16:47:53\] \<stangrze> broadsoft, sory ;-)
 
 ## minor release
 
 \[2014-05-14 16:49:00\] \<miconda> planning one by end of may, early
-june  
-\[2014-05-14 16:49:13\] \<miconda> before starting the holidays season  
+june
+\[2014-05-14 16:49:13\] \<miconda> before starting the holidays season
 \[2014-05-14 16:50:00\] \<miconda> most probably for both latest stable
-branches this time — 4.0 and 4.1  
-\[2014-05-14 16:50:18\] \<miconda> so this was short — I gues …  
+branches this time — 4.0 and 4.1
+\[2014-05-14 16:50:18\] \<miconda> so this was short — I gues …
 \[2014-05-14 16:50:27\] \<miconda> we get back to proposed topics
-later  
+later
 \[2014-05-14 16:50:36\] \<linuxmaniac> jessie will freeze at 6th of
-November 2014  
-\[2014-05-14 16:50:51\] \<miconda> just to finish what we have on wiki  
+November 2014
+\[2014-05-14 16:50:51\] \<miconda> just to finish what we have on wiki
 \[2014-05-14 16:51:07\] \<miconda> linuxmaniac: so we have to do a major
-release before to get it in, right?  
-\[2014-05-14 16:51:14\] \<linuxmaniac> yes  
-\[2014-05-14 16:51:16\] \<oej> I will freeze in october already...  
-\[2014-05-14 16:51:19\] \<miconda> ok  
-\[2014-05-14 16:51:24\] \<miconda> :-)  
-\[2014-05-14 16:51:36\] \<eZz> hello  
+release before to get it in, right?
+\[2014-05-14 16:51:14\] \<linuxmaniac> yes
+\[2014-05-14 16:51:16\] \<oej> I will freeze in october already...
+\[2014-05-14 16:51:19\] \<miconda> ok
+\[2014-05-14 16:51:24\] \<miconda> :-)
+\[2014-05-14 16:51:36\] \<eZz> hello
 \[2014-05-14 16:51:41\] \<linuxmaniac> and afer that long maintain
-work  
-\[2014-05-14 16:51:45\] \<caruizdiaz> xD  
+work
+\[2014-05-14 16:51:45\] \<caruizdiaz> xD
 \[2014-05-14 16:52:01\] \<miconda> next topic: old or forgotten
-patches  
+patches
 \[2014-05-14 16:52:05\] \<linuxmaniac> just security patches for stable
-release  
-\[2014-05-14 16:52:28\] \<linuxmaniac> multipart bodies!!! :-(  
-\[2014-05-14 16:52:32\] \<linuxmaniac> jaja  
+release
+\[2014-05-14 16:52:28\] \<linuxmaniac> multipart bodies!!! :-(
+\[2014-05-14 16:52:32\] \<linuxmaniac> jaja
 \[2014-05-14 16:52:43\] \<abalashov> My patch that deprecates IPv4 and
 non-TLS connections was forgotten. But it's probably best left
-forgotten.  
-\[2014-05-14 16:53:02\] \<miconda> linuxmaniac: should be done soon  
-\[2014-05-14 16:53:15\] \<miconda> the one for textops is more scarry  
-\[2014-05-14 16:53:34\] \<miconda> but will be finished soon  
+forgotten.
+\[2014-05-14 16:53:02\] \<miconda> linuxmaniac: should be done soon
+\[2014-05-14 16:53:15\] \<miconda> the one for textops is more scarry
+\[2014-05-14 16:53:34\] \<miconda> but will be finished soon
 \[2014-05-14 16:53:34\] \<linuxmaniac> yes, and now I'm working on
-dialplan  
-\[2014-05-14 16:53:57\] \<linuxmaniac> this will be even scarier  
+dialplan
+\[2014-05-14 16:53:57\] \<linuxmaniac> this will be even scarier
 \[2014-05-14 16:53:57\] \<miconda> the one for websockets, Peter
-responded on mailing list, as he cannot attend here  
+responded on mailing list, as he cannot attend here
 \[2014-05-14 16:54:48\] \<miconda> my plan for the one on websockets (to
-get rid of libunistring) is to have defines to select one or another …  
+get rid of libunistring) is to have defines to select one or another …
 \[2014-05-14 16:55:07\] \<miconda> in some OSes is hard to get
-libunistring  
-\[2014-05-14 16:55:20\] \<miconda> eZz: hello!  
+libunistring
+\[2014-05-14 16:55:20\] \<miconda> eZz: hello!
 
 ## mirrors
 
-\[2014-05-14 16:55:57\] \<caruizdiaz> +1 to get rid of libunistring  
+\[2014-05-14 16:55:57\] \<caruizdiaz> +1 to get rid of libunistring
 \[2014-05-14 16:56:33\] \<linuxmaniac> I have to say that the Makefiles
 can be improved, I had recently a report because kamailio couldn't build
-without pkg-config  
-\[2014-05-14 16:56:33\] \<miconda> we may get some US-located server  
-\[2014-05-14 16:56:35\] \<oej> What's the alternative to libunistring  
-\[2014-05-14 16:56:51\] \<oej> (sorry, missed "next topic" . MOve on!)  
-\[2014-05-14 16:56:54\] \<miconda> oej: embedded version  
-\[2014-05-14 16:57:04\] \<miconda> oej: no problem …  
+without pkg-config
+\[2014-05-14 16:56:33\] \<miconda> we may get some US-located server
+\[2014-05-14 16:56:35\] \<oej> What's the alternative to libunistring
+\[2014-05-14 16:56:51\] \<oej> (sorry, missed "next topic" . MOve on!)
+\[2014-05-14 16:56:54\] \<miconda> oej: embedded version
+\[2014-05-14 16:57:04\] \<miconda> oej: no problem …
 \[2014-05-14 16:57:32\] \<miconda> oej: there was a patch to replace the
-function used from libunistring with one to be inside the module  
-\[2014-05-14 16:57:39\] \<oej> ok  
+function used from libunistring with one to be inside the module
+\[2014-05-14 16:57:39\] \<oej> ok
 \[2014-05-14 16:57:48\] \<miconda> because it is about conversion from
-utf8 to ascii, or so ...  
+utf8 to ascii, or so ...
 \[2014-05-14 16:57:56\] \<oej> Unicode is not easy, so we need to make
-sure it works properly  
-\[2014-05-14 16:58:18\] \<miconda> don’t remember by heart now exactly  
+sure it works properly
+\[2014-05-14 16:58:18\] \<miconda> don’t remember by heart now exactly
 \[2014-05-14 16:58:37\] \<miconda> but yes, we will keep both options by
-compile time to be able to switch in case of problems  
-\[2014-05-14 16:58:58\] \<oej> Ok, back to "Mirrors"  
-\[2014-05-14 16:59:05\] \<miconda> anything else for old patches?  
-\[2014-05-14 16:59:15\] \<miconda> ok then, back to mirrors  
+compile time to be able to switch in case of problems
+\[2014-05-14 16:58:58\] \<oej> Ok, back to "Mirrors"
+\[2014-05-14 16:59:05\] \<miconda> anything else for old patches?
+\[2014-05-14 16:59:15\] \<miconda> ok then, back to mirrors
 \[2014-05-14 16:59:23\] \<miconda> as said, we may get some US-located
-server  
-\[2014-05-14 16:59:36\] \<miconda> thanks to qxork  
-\[2014-05-14 16:59:45\] \<oej> Thanks Qxork  
-\[2014-05-14 16:59:51\] \<abalashov> Thanks qxork !  
+server
+\[2014-05-14 16:59:36\] \<miconda> thanks to qxork
+\[2014-05-14 16:59:45\] \<oej> Thanks Qxork
+\[2014-05-14 16:59:51\] \<abalashov> Thanks qxork !
 \[2014-05-14 17:00:00\] \<miconda> and I thought of mirroring the debian
-apt repos  
-\[2014-05-14 17:00:01\] \<oej> MIrror of what btw?  
+apt repos
+\[2014-05-14 17:00:01\] \<oej> MIrror of what btw?
 \[2014-05-14 17:00:25\] \<eZz> please tell me when will be a free talk,
-I did not declared any topics  
-\[2014-05-14 17:00:27\] \<miconda> and build a rpm repo  
-\[2014-05-14 17:00:55\] \<miconda> oej: so we get a server (virtual)  
-\[2014-05-14 17:01:00\] \<miconda> and we can use it  
-\[2014-05-14 17:01:23\] \<miconda> we are ok with apt repos  
+I did not declared any topics
+\[2014-05-14 17:00:27\] \<miconda> and build a rpm repo
+\[2014-05-14 17:00:55\] \<miconda> oej: so we get a server (virtual)
+\[2014-05-14 17:01:00\] \<miconda> and we can use it
+\[2014-05-14 17:01:23\] \<miconda> we are ok with apt repos
 \[2014-05-14 17:01:31\] \<miconda> but rpms are on open suse build
-servers  
+servers
 \[2014-05-14 17:01:49\] \<miconda> and doesn’t appear to be easy to get
-via some package manager  
+via some package manager
 \[2014-05-14 17:01:55\] \<linuxmaniac> mika: there is an easy way to
-build rpm too in jenkins?  
+build rpm too in jenkins?
 \[2014-05-14 17:02:17\] \<mika> linuxmaniac: nope, i've a buddy working
-on it, but it needs work  
-\[2014-05-14 17:02:25\] \<linuxmaniac> Ok  
+on it, but it needs work
+\[2014-05-14 17:02:25\] \<linuxmaniac> Ok
 \[2014-05-14 17:02:32\] \<miconda> not being a rpm-base distro user, I
-just thought of cloning the rpms and building a repository out of them  
+just thought of cloning the rpms and building a repository out of them
 \[2014-05-14 17:03:10\] \<mika> clean rpm builds similar to what we do
-with debs would be nice though :) what distris do you have in mind?  
+with debs would be nice though :) what distris do you have in mind?
 \[2014-05-14 17:03:15\] \<miconda> then eventually set a mirror for apt
 repos as well, although I understood from sipwise guys that the current
-one is on amazon, so it is distributed already  
+one is on amazon, so it is distributed already
 \[2014-05-14 17:03:50\] \<linuxmaniac> miconda: been in amazon doesn't
-mean distributed  
+mean distributed
 \[2014-05-14 17:03:50\] \<miconda> mika: now we (I) do for centos,
-redhat, opensuse and fedora  
-\[2014-05-14 17:04:03\] \<miconda> various versions  
-\[2014-05-14 17:04:14\] \<miconda> supported by opensuse build service  
+redhat, opensuse and fedora
+\[2014-05-14 17:04:03\] \<miconda> various versions
+\[2014-05-14 17:04:14\] \<miconda> supported by opensuse build service
 \[2014-05-14 17:04:28\] \<miconda> linuxmaniac: ok, right, wanted to say
-more reliable :-)  
-\[2014-05-14 17:04:30\] \<mika> miconda: alright  
+more reliable :-)
+\[2014-05-14 17:04:30\] \<mika> miconda: alright
 \[2014-05-14 17:04:59\] \<oej> Gotta leave the office, or they will lock
-me in. Have a good meeting!  
+me in. Have a good meeting!
 \[2014-05-14 17:05:20\] \<caruizdiaz> glad that rpm based distros are
-taken into account :)  
-\[2014-05-14 17:05:38\] \<caruizdiaz> bye oej :)  
-\[2014-05-14 17:05:40\] \<eZz> have a great evening, oej!  
+taken into account :)
+\[2014-05-14 17:05:38\] \<caruizdiaz> bye oej :)
+\[2014-05-14 17:05:40\] \<eZz> have a great evening, oej!
 \[2014-05-14 17:06:04\] \<miconda> for reference:
-<https://build.opensuse.org/project/show/home:kamailio:telephony>  
+<https://build.opensuse.org/project/show/home:kamailio:telephony>
 \[2014-05-14 17:06:49\] \<miconda> so my question would have been:
-anyone here knowing to set a yum/whatsoever repository?  
-\[2014-05-14 17:06:52\] \<caruizdiaz> thanks  
+anyone here knowing to set a yum/whatsoever repository?
+\[2014-05-14 17:06:52\] \<caruizdiaz> thanks
 \[2014-05-14 17:07:24\] \<miconda> caruizdiaz: so you wanted to say that
-you can take care of?!?  
+you can take care of?!?
 \[2014-05-14 17:07:56\] \<caruizdiaz> jajaja, I could, but it will take
-me some time to get used to the rpm build system.  
-\[2014-05-14 17:08:02\] \<caruizdiaz> can you wait? ;)  
+me some time to get used to the rpm build system.
+\[2014-05-14 17:08:02\] \<caruizdiaz> can you wait? ;)
 \[2014-05-14 17:08:19\] \<eZz> some years ago I was a maintainer of
-Slackware packages mirror and did it automaticaly  
-\[2014-05-14 17:08:28\] \<miconda> build service is done, that’s easy  
+Slackware packages mirror and did it automaticaly
+\[2014-05-14 17:08:28\] \<miconda> build service is done, that’s easy
 \[2014-05-14 17:08:56\] \<mika> IIRC createrepo should even work on
-Debian to provide a yum mirror  
+Debian to provide a yum mirror
 \[2014-05-14 17:08:59\] \<caruizdiaz> then it would be repo
-configuration only  
+configuration only
 \[2014-05-14 17:09:00\] \<miconda> needed: a script to download the rpms
-and build a yum/etc repo  
+and build a yum/etc repo
 \[2014-05-14 17:09:42\] \<miconda> ok … let’s get back on this when we
-have the server  
-\[2014-05-14 17:09:54\] \<miconda> will discuss on mailing list  
+have the server
+\[2014-05-14 17:09:54\] \<miconda> will discuss on mailing list
 \[2014-05-14 17:10:01\] \<eZz> btw, checkinstall can create
-rpm/debian/slack/etc else packages  
+rpm/debian/slack/etc else packages
 \[2014-05-14 17:10:31\] \<caruizdiaz> I think peter had done some work
 on this topic for his centos servers. I will catch up with his work and
-see how I can help  
-\[2014-05-14 17:10:43\] \<miconda> ok  
+see how I can help
+\[2014-05-14 17:10:43\] \<miconda> ok
 
 ## world wide events
 
-\[2014-05-14 17:10:53\] \<miconda> next topic: world wide events …  
+\[2014-05-14 17:10:53\] \<miconda> next topic: world wide events …
 \[2014-05-14 17:11:36\] \<miconda> if anyone here is participating to an
 event and approaches something touching kamailio, we can put news, etc…
-on site  
+on site
 \[2014-05-14 17:11:46\] \<carstenbock> I'll add to the docs in the Wiki,
-how to use the SUSE services as a yum-repo...  
+how to use the SUSE services as a yum-repo...
 \[2014-05-14 17:12:17\] \<eZz> I'm working on 2 new modules according to
-security  
+security
 \[2014-05-14 17:12:23\] \<miconda> or if you know an event that should
-be attended, send and email and we will see if anyone can attend  
+be attended, send and email and we will see if anyone can attend
 \[2014-05-14 17:12:43\] \<miconda> eZz: great, wait a bit and we will
-get on that topic  
-\[2014-05-14 17:12:55\] \<eZz> miconda: ok  
+get on that topic
+\[2014-05-14 17:12:55\] \<eZz> miconda: ok
 \[2014-05-14 17:13:40\] \<miconda> to conclude on events — Cluecon and
-Astricon will be on our radar  
-\[2014-05-14 17:14:04\] \<caruizdiaz> what about TADHack?  
+Astricon will be on our radar
+\[2014-05-14 17:14:04\] \<caruizdiaz> what about TADHack?
 \[2014-05-14 17:14:09\] \<miconda> but also smaller events are good,
-those kind of meetups  
+those kind of meetups
 \[2014-05-14 17:14:24\] \<miconda> caruizdiaz: looks interesting,
-overlaps with vacation  
+overlaps with vacation
 \[2014-05-14 17:14:38\] \<miconda> but would be good if anyone can
-participate on site or remote  
-\[2014-05-14 17:14:43\] \<caruizdiaz> it's not vacation in here :D  
+participate on site or remote
+\[2014-05-14 17:14:43\] \<caruizdiaz> it's not vacation in here :D
 \[2014-05-14 17:15:05\] \<miconda> here we done one every 10 years, so
-…  
+…
 \[2014-05-14 17:15:05\] \<caruizdiaz> I think I will. I will let you
-know if so.  
-\[2014-05-14 17:15:06\] \<miconda> :-)  
-\[2014-05-14 17:15:11\] \<miconda> ok  
-\[2014-05-14 17:15:17\] \<qxork> have to run!  
-\[2014-05-14 17:15:32\] \<miconda> next topic: ipv6, security  
+know if so.
+\[2014-05-14 17:15:06\] \<miconda> :-)
+\[2014-05-14 17:15:11\] \<miconda> ok
+\[2014-05-14 17:15:17\] \<qxork> have to run!
+\[2014-05-14 17:15:32\] \<miconda> next topic: ipv6, security
 \[2014-05-14 17:15:43\] \<miconda> oej is gone, so it should be short
-:-)  
-\[2014-05-14 17:15:53\] \<caruizdiaz> xD  
+:-)
+\[2014-05-14 17:15:53\] \<caruizdiaz> xD
 \[2014-05-14 17:16:02\] \<miconda> any experiences with IPv6, any
-issues?  
+issues?
 \[2014-05-14 17:16:16\] \<miconda> not much production from my
-interactions …  
+interactions …
 \[2014-05-14 17:17:06\] \<miconda> anyhow, for new modules dealing with
-ip addresses, ipv6 should be considered from early phase  
+ip addresses, ipv6 should be considered from early phase
 \[2014-05-14 17:17:24\] \<miconda> some providers in germany started to
-shift to ipv6  
+shift to ipv6
 \[2014-05-14 17:17:50\] \<linuxmaniac> miconda: we have some clients
-with ipv6  
+with ipv6
 \[2014-05-14 17:18:03\] \<miconda> to conclude: I am not aware of any
-issue, just wanted to get a round of others’ opinions  
-\[2014-05-14 17:18:23\] \<miconda> linuxmaniac: ok, so it’s working …  
-\[2014-05-14 17:18:37\] \<linuxmaniac> I not aware of any issue  
+issue, just wanted to get a round of others’ opinions
+\[2014-05-14 17:18:23\] \<miconda> linuxmaniac: ok, so it’s working …
+\[2014-05-14 17:18:37\] \<linuxmaniac> I not aware of any issue
 \[2014-05-14 17:18:41\] \<miconda> do you have any figures (estimations)
-of subscribers on ipv6  
-\[2014-05-14 17:18:49\] \<miconda> like order of magnitude  
+of subscribers on ipv6
+\[2014-05-14 17:18:49\] \<miconda> like order of magnitude
 \[2014-05-14 17:18:57\] \<linuxmaniac> not me, but maybe Daniel or
-Andrew  
-\[2014-05-14 17:18:59\] \<miconda> 1000+, 10 000+ …  
-\[2014-05-14 17:19:05\] \<miconda> ok  
+Andrew
+\[2014-05-14 17:18:59\] \<miconda> 1000+, 10 000+ …
+\[2014-05-14 17:19:05\] \<miconda> ok
 
 ## security
 
 \[2014-05-14 17:19:34\] \<carstenbock> We wanted to put IPv6 in a
 customer network, but then we noticed that basically all fibre-modems
 and ISDN boxes in that network did not support IPv6 and it's not on the
-roadmap of the manufacturers :-(  
+roadmap of the manufacturers :-(
 \[2014-05-14 17:19:57\] \<miconda> there is the issue of tls-only listen
-…  
-\[2014-05-14 17:20:06\] \<miconda> that should be fixed soon  
+…
+\[2014-05-14 17:20:06\] \<miconda> that should be fixed soon
 \[2014-05-14 17:20:52\] \<miconda> before the next major release I will
-review to see if anything else needs to be addresses in tls module  
-\[2014-05-14 17:21:05\] \<miconda> now we support up to tlsv1.2, iirc  
-\[2014-05-14 17:21:16\] \<miconda> tls1.3 is out? anyone knows....  
+review to see if anything else needs to be addresses in tls module
+\[2014-05-14 17:21:05\] \<miconda> now we support up to tlsv1.2, iirc
+\[2014-05-14 17:21:16\] \<miconda> tls1.3 is out? anyone knows....
 \[2014-05-14 17:21:44\] \<miconda> eZz: as we are on security, you said
-something about two new modules  
-\[2014-05-14 17:21:48\] \<miconda> can you give more details?  
+something about two new modules
+\[2014-05-14 17:21:48\] \<miconda> can you give more details?
 \[2014-05-14 17:22:56\] \<miconda> eZz: are you around? otherwise we
-came back later to them  
+came back later to them
 \[2014-05-14 17:23:12\] \<miconda> anything else we should do from
-security point of view?  
+security point of view?
 \[2014-05-14 17:23:38\] \<miconda> it was a proposal with an alerts
-mailing list?!? or I am mixing it with something else...  
+mailing list?!? or I am mixing it with something else...
 \[2014-05-14 17:24:53\] \<linuxmaniac> miconda: it will be great for the
-future jessie maintenance a way to know security related problems  
-\[2014-05-14 17:25:37\] \<miconda> linuxmaniac: ok  
+future jessie maintenance a way to know security related problems
+\[2014-05-14 17:25:37\] \<miconda> linuxmaniac: ok
 \[2014-05-14 17:25:50\] \<miconda> perhaps we can discuss it on mailing
-list to get the others involved  
-\[2014-05-14 17:25:56\] \<linuxmaniac> +1  
+list to get the others involved
+\[2014-05-14 17:25:56\] \<linuxmaniac> +1
 
 ## continuous integration
 
-\[2014-05-14 17:26:14\] \<linuxmaniac> \\o/  
-\[2014-05-14 17:26:19\] \<miconda> and now it’s linuxmaniac on stage  
-\[2014-05-14 17:26:28\] \<linuxmaniac> mika... come to rescue me!  
+\[2014-05-14 17:26:14\] \<linuxmaniac> \\o/
+\[2014-05-14 17:26:19\] \<miconda> and now it’s linuxmaniac on stage
+\[2014-05-14 17:26:28\] \<linuxmaniac> mika... come to rescue me!
 \[2014-05-14 17:26:57\] \<linuxmaniac> It will be great to start a
-discussion about it  
-\[2014-05-14 17:27:06\] \<mika> linuxmaniac: :)  
+discussion about it
+\[2014-05-14 17:27:06\] \<mika> linuxmaniac: :)
 \[2014-05-14 17:27:22\] \<linuxmaniac> what are our plans, wishes and
-manpower  
-\[2014-05-14 17:27:52\] \<linuxmaniac> from my part  
+manpower
+\[2014-05-14 17:27:52\] \<linuxmaniac> from my part
 \[2014-05-14 17:28:21\] \<linuxmaniac> I've created the initial jobs for
-static analysis using cppcheck at jenkins  
+static analysis using cppcheck at jenkins
 \[2014-05-14 17:28:42\] \<miconda> linuxmaniac: cppcheck on jenkins
-shows 0  
-\[2014-05-14 17:28:46\] \<miconda> when i checked  
+shows 0
+\[2014-05-14 17:28:46\] \<miconda> when i checked
 \[2014-05-14 17:28:46\] \<mmike\_\> Hello to all. Don't know if anyone
-can hel me.  
+can hel me.
 \[2014-05-14 17:28:59\] \<linuxmaniac> miconda: the are two kinds of
-jobs  
-\[2014-05-14 17:29:00\] \<miconda> was it run?  
+jobs
+\[2014-05-14 17:29:00\] \<miconda> was it run?
 \[2014-05-14 17:29:26\] \<mmike\_\> we use Kamailio in our voip network
-and now we're facing an interoperability problem with a voip provider.  
+and now we're facing an interoperability problem with a voip provider.
 \[2014-05-14 17:29:32\] \<linuxmaniac> cppcheck-full is a complete run
-of everything  
+of everything
 \[2014-05-14 17:29:51\] \<mmike\_\> it requires support to PRACK while
-out voip switch doesn't support it.  
+out voip switch doesn't support it.
 \[2014-05-14 17:29:53\] \<linuxmaniac> but cppcheck is just a check for
-the files changed in last commit  
+the files changed in last commit
 \[2014-05-14 17:30:14\] \<linuxmaniac> s/last commit/from the last
-commit checked/  
-\[2014-05-14 17:30:24\] \<miconda> linuxmaniac: ok  
-\[2014-05-14 17:30:38\] \<linuxmaniac> the full check is quite heavy  
+commit checked/
+\[2014-05-14 17:30:24\] \<miconda> linuxmaniac: ok
+\[2014-05-14 17:30:38\] \<linuxmaniac> the full check is quite heavy
 \[2014-05-14 17:30:44\] \<mmike\_\> Would it be possible to configure
-kamailio to generate the PRACK requests and OK to PRACKs?  
-\[2014-05-14 17:30:46\] \<linuxmaniac> like more than 8 hours  
+kamailio to generate the PRACK requests and OK to PRACKs?
+\[2014-05-14 17:30:46\] \<linuxmaniac> like more than 8 hours
 \[2014-05-14 17:30:46\] \<miconda> so are there thing reported on all
-source?  
-\[2014-05-14 17:31:02\] \<miconda> s/thing/things/  
+source?
+\[2014-05-14 17:31:02\] \<miconda> s/thing/things/
 \[2014-05-14 17:31:18\] \<linuxmaniac>
-<https://kamailio.sipwise.com/view/cppcheck/job/kamailio40-cppcheck-full/1/cppcheckResult/>  
+<https://kamailio.sipwise.com/view/cppcheck/job/kamailio40-cppcheck-full/1/cppcheckResult/>
 \[2014-05-14 17:31:33\] \<linuxmaniac>
-<https://kamailio.sipwise.com/view/cppcheck/job/kamailio41-cppcheck-full/2/cppcheckResult/>  
+<https://kamailio.sipwise.com/view/cppcheck/job/kamailio41-cppcheck-full/2/cppcheckResult/>
 \[2014-05-14 17:31:54\] \<linuxmaniac> I didn't have time to check the
-results yet  
-\[2014-05-14 17:32:20\] \<miconda> ok  
+results yet
+\[2014-05-14 17:32:20\] \<miconda> ok
 \[2014-05-14 17:32:21\] \<linuxmaniac> but Alex did a fast check on some
-and there are some stupid withs  
-\[2014-05-14 17:32:24\] \<miconda> looking over them soon  
-\[2014-05-14 17:32:25\] \<linuxmaniac> things  
+and there are some stupid withs
+\[2014-05-14 17:32:24\] \<miconda> looking over them soon
+\[2014-05-14 17:32:25\] \<linuxmaniac> things
 \[2014-05-14 17:32:41\] \<miconda> btw, you wanted to send allerts to
-mailing list  
+mailing list
 \[2014-05-14 17:32:42\] \<linuxmaniac> for sure there are some false
-positives  
-\[2014-05-14 17:32:44\] \<miconda> that would be good  
+positives
+\[2014-05-14 17:32:44\] \<miconda> that would be good
 \[2014-05-14 17:33:05\] \<miconda> let me know the email address to be
-used for sending alerts and I can allow it to sr-dev  
+used for sending alerts and I can allow it to sr-dev
 \[2014-05-14 17:33:05\] \<linuxmaniac> miconda: yes, I would like to
-send mails when a job fails  
-\[2014-05-14 17:33:22\] \<linuxmaniac> mika: ^  
-\[2014-05-14 17:33:33\] \<eZz> miconda: sorry, I was afk, now here  
-\[2014-05-14 17:33:35\] \<linuxmaniac> miconda: ok  
+send mails when a job fails
+\[2014-05-14 17:33:22\] \<linuxmaniac> mika: ^
+\[2014-05-14 17:33:33\] \<eZz> miconda: sorry, I was afk, now here
+\[2014-05-14 17:33:35\] \<linuxmaniac> miconda: ok
 \[2014-05-14 17:33:51\] \<mika> yeah, np to notify mailing list, i just
-need a mail adr :)  
+need a mail adr :)
 \[2014-05-14 17:34:07\] \<mika> checking what we have as outgoing, a
-sec  
+sec
 \[2014-05-14 17:34:20\] \<linuxmaniac> I plan to trigger the full jobs
-once a mouth  
-\[2014-05-14 17:34:23\] \<linuxmaniac> mounth  
+once a mouth
+\[2014-05-14 17:34:23\] \<linuxmaniac> mounth
 \[2014-05-14 17:34:26\] \<eZz> miconda: please tell me later, when I can
-tell something about those modules  
+tell something about those modules
 \[2014-05-14 17:35:15\] \<linuxmaniac> mika: it should send mails to
-[email protected]  
-\[2014-05-14 17:35:29\] \<linuxmaniac> miconda: correct?  
-\[2014-05-14 17:36:02\] \<linuxmaniac> So, static analysis done, ok?  
-\[2014-05-14 17:36:15\] \<miconda> yes, to ser-dev@…  
-\[2014-05-14 17:36:21\] \<miconda> sr-dev@…  
-\[2014-05-14 17:36:24\] \<mika> alright  
-\[2014-05-14 17:36:46\] \<miconda> linuxmaniac: ok  
+<[email protected]>
+\[2014-05-14 17:35:29\] \<linuxmaniac> miconda: correct?
+\[2014-05-14 17:36:02\] \<linuxmaniac> So, static analysis done, ok?
+\[2014-05-14 17:36:15\] \<miconda> yes, to ser-dev@…
+\[2014-05-14 17:36:21\] \<miconda> sr-dev@…
+\[2014-05-14 17:36:24\] \<mika> alright
+\[2014-05-14 17:36:46\] \<miconda> linuxmaniac: ok
 \[2014-05-14 17:36:49\] \<linuxmaniac> BTW, If you detect false
-positives, please report them to me in order to filter them  
-\[2014-05-14 17:37:07\] \<linuxmaniac> next, functional testing  
+positives, please report them to me in order to filter them
+\[2014-05-14 17:37:07\] \<linuxmaniac> next, functional testing
 \[2014-05-14 17:37:13\] \<miconda> for valgrind, kamailio can be
-compiled with system malloc  
-\[2014-05-14 17:37:23\] \<miconda> instead of pkg_malloc/pkg_free  
-\[2014-05-14 17:37:50\] \<linuxmaniac> miconda: but for shm?  
+compiled with system malloc
+\[2014-05-14 17:37:23\] \<miconda> instead of pkg_malloc/pkg_free
+\[2014-05-14 17:37:50\] \<linuxmaniac> miconda: but for shm?
 \[2014-05-14 17:38:07\] \<linuxmaniac> I think valgrind needs to be
-teached  
+teached
 \[2014-05-14 17:38:28\] \<linuxmaniac> of our \*\_malloc \*\_free
-functions  
-\[2014-05-14 17:38:53\] \<linuxmaniac> doesn't it?  
-\[2014-05-14 17:39:01\] \<miconda> don’t know how  
-\[2014-05-14 17:39:05\] \<miconda> could be possible  
+functions
+\[2014-05-14 17:38:53\] \<linuxmaniac> doesn't it?
+\[2014-05-14 17:39:01\] \<miconda> don’t know how
+\[2014-05-14 17:39:05\] \<miconda> could be possible
 \[2014-05-14 17:39:24\] \<miconda> I was thinking to try to replace
-shm_malloc with pkg malloc  
+shm_malloc with pkg malloc
 \[2014-05-14 17:39:47\] \<linuxmaniac> miconda:
-<http://valgrind.org/docs/manual/mc-manual.html#mc-manual.mempools>  
+<http://valgrind.org/docs/manual/mc-manual.html#mc-manual.mempools>
 \[2014-05-14 17:40:05\] \<linuxmaniac> there is an API to teach valgrind
-of custom allocators  
-\[2014-05-14 17:40:15\] \<miconda> ok  
-\[2014-05-14 17:40:19\] \<miconda> that might be better  
-\[2014-05-14 17:40:30\] \<linuxmaniac> if we can do that...  
+of custom allocators
+\[2014-05-14 17:40:15\] \<miconda> ok
+\[2014-05-14 17:40:19\] \<miconda> that might be better
+\[2014-05-14 17:40:30\] \<linuxmaniac> if we can do that...
 \[2014-05-14 17:40:40\] \<linuxmaniac> we can test all the memory
-allocators  
+allocators
 \[2014-05-14 17:41:04\] \<miconda> because replacing shm with system
-malloc might work only for static analysis, definitely not runtime  
-\[2014-05-14 17:41:26\] \<linuxmaniac> I was aware of the API  
+malloc might work only for static analysis, definitely not runtime
+\[2014-05-14 17:41:26\] \<linuxmaniac> I was aware of the API
 \[2014-05-14 17:41:47\] \<linuxmaniac> so that's why I'm sure we can do
-this  
-\[2014-05-14 17:41:52\] \<miconda> ok  
-\[2014-05-14 17:42:17\] \<miconda> so, now: functional testing …  
+this
+\[2014-05-14 17:41:52\] \<miconda> ok
+\[2014-05-14 17:42:17\] \<miconda> so, now: functional testing …
 \[2014-05-14 17:42:22\] \<linuxmaniac> I tried myself to figure out how
-to do it, but failed  
+to do it, but failed
 \[2014-05-14 17:42:45\] \<linuxmaniac> yes, we need some tests in order
-to be able to do some automatic testing  
+to be able to do some automatic testing
 \[2014-05-14 17:43:27\] \<miconda> is there a framework, or what is your
-proposal?  
+proposal?
 \[2014-05-14 17:43:30\] \<linuxmaniac> In sipwise I've created some
-testings with customs scripts  
+testings with customs scripts
 \[2014-05-14 17:43:43\] \<miconda> can the existing test scripts be
-reused?  
+reused?
 \[2014-05-14 17:43:44\] \<mika> miconda: enabled, mails should be sent
-from [email protected]  
+from <[email protected]>
 \[2014-05-14 17:44:32\] \<linuxmaniac> miconda:
-<https://github.com/sipwise/kamailio-config-tests>  
+<https://github.com/sipwise/kamailio-config-tests>
 \[2014-05-14 17:44:48\] \<linuxmaniac> this is heavily based in our
-platform  
-\[2014-05-14 17:45:11\] \<miconda> mika: ok, I will allow the address  
+platform
+\[2014-05-14 17:45:11\] \<miconda> mika: ok, I will allow the address
 \[2014-05-14 17:45:16\] \<linuxmaniac> But I would like to discuss
-something generic  
+something generic
 \[2014-05-14 17:45:23\] \<mika> miconda: alright, just let me know if
-there are any problems  
-\[2014-05-14 17:45:39\] \<linuxmaniac> mika: thanks :-)  
+there are any problems
+\[2014-05-14 17:45:39\] \<linuxmaniac> mika: thanks :-)
 \[2014-05-14 17:45:58\] \<miconda> linuxmaniac: in current source code
-we have ‘test/unit/\*’  
-\[2014-05-14 17:46:05\] \<miconda> scripts done by Henning a while ago  
+we have ‘test/unit/\*’
+\[2014-05-14 17:46:05\] \<miconda> scripts done by Henning a while ago
 \[2014-05-14 17:46:18\] \<miconda> not sure how actual, not much
-activity with them lately  
+activity with them lately
 \[2014-05-14 17:47:14\] \<linuxmaniac> oej point me to asterisk testing
-framework or something like that  
-\[2014-05-14 17:47:29\] \<miconda> the one from sipwise uses sipp?  
-\[2014-05-14 17:47:36\] \<linuxmaniac> miconda: yes  
-\[2014-05-14 17:48:03\] \<miconda> and is any framework there  
+framework or something like that
+\[2014-05-14 17:47:29\] \<miconda> the one from sipwise uses sipp?
+\[2014-05-14 17:47:36\] \<linuxmaniac> miconda: yes
+\[2014-05-14 17:48:03\] \<miconda> and is any framework there
 \[2014-05-14 17:48:07\] \<linuxmaniac> the idea is: set the subscribers,
-settings, etc...  
-\[2014-05-14 17:48:10\] \<miconda> or something developed inhouse?  
-\[2014-05-14 17:48:18\] \<linuxmaniac> this is done calling our API  
+settings, etc...
+\[2014-05-14 17:48:10\] \<miconda> or something developed inhouse?
+\[2014-05-14 17:48:18\] \<linuxmaniac> this is done calling our API
 \[2014-05-14 17:48:31\] \<stangrze> there is nice collection of sipp
-scripts on github  
+scripts on github
 \[2014-05-14 17:49:01\] \<\_gv\_\> If it's of interest, in Truphone Labs
 we use both sipp and pjsua, triggered by Jenkins. pjsua has a nice
-interface to manage this  
+interface to manage this
 \[2014-05-14 17:49:12\] \<linuxmaniac> and then fire some sipp
-processes, parse the kamailio log, and test the results  
+processes, parse the kamailio log, and test the results
 \[2014-05-14 17:49:43\] \<linuxmaniac> with this we can test the
-kamailio config flow  
-\[2014-05-14 17:49:50\] \<linuxmaniac> var contents  
-\[2014-05-14 17:50:04\] \<linuxmaniac> sip in an out messages  
+kamailio config flow
+\[2014-05-14 17:49:50\] \<linuxmaniac> var contents
+\[2014-05-14 17:50:04\] \<linuxmaniac> sip in an out messages
 \[2014-05-14 17:50:16\] \<miconda> \_gv\_: anything public? expecially
-with pjsua?  
-\[2014-05-14 17:50:36\] \<linuxmaniac> This is really inhouse  
+with pjsua?
+\[2014-05-14 17:50:36\] \<linuxmaniac> This is really inhouse
 \[2014-05-14 17:50:51\] \<miconda> linuxmaniac: yes, I expect this fits
-for a specific config  
+for a specific config
 \[2014-05-14 17:51:07\] \<miconda> but probably we can get something for
-generic parts  
+generic parts
 \[2014-05-14 17:51:22\] \<miconda> eg., authentication, location
-registration and lookup  
+registration and lookup
 \[2014-05-14 17:51:35\] \<\_gv\_\> miconda: not that I'm aware of, but I
-can see what's not sensitive and share  
+can see what's not sensitive and share
 \[2014-05-14 17:51:44\] \<linuxmaniac> miconda: yes, you know about my
-work in debugger in order to be able to check config vars  
-\[2014-05-14 17:51:54\] \<miconda> \_gv\_: ok, thanks  
+work in debugger in order to be able to check config vars
+\[2014-05-14 17:51:54\] \<miconda> \_gv\_: ok, thanks
 \[2014-05-14 17:52:31\] \<linuxmaniac> but that is the issue we need to
-figure out how we want to do this  
+figure out how we want to do this
 \[2014-05-14 17:53:02\] \<miconda> if there is a known/good framework
-that can be reused, we can look at  
+that can be reused, we can look at
 \[2014-05-14 17:53:15\] \<miconda> but I am not familiar with this, so
-suggestions are welcome  
-\[2014-05-14 17:53:18\] \<linuxmaniac> I don't know of any  
+suggestions are welcome
+\[2014-05-14 17:53:18\] \<linuxmaniac> I don't know of any
 \[2014-05-14 17:53:41\] \<miconda> if not, reuse old scripts or what so
-ever can be reused from sipwise thing  
+ever can be reused from sipwise thing
 \[2014-05-14 17:54:09\] \<miconda> the old scripts are shell, calling
-various commands  
+various commands
 \[2014-05-14 17:54:43\] \<miconda> and, iirc, sending emails if they
-fail  
+fail
 \[2014-05-14 17:54:52\] \<miconda> at some point they were enabled on
-devel.kamailio.org  
+devel.kamailio.org
 \[2014-05-14 17:54:54\] \<linuxmaniac> maybe I can write a page in the
-wiki to summarize the proposal/issue  
-\[2014-05-14 17:55:05\] \<miconda> linuxmaniac: that will be very good  
-\[2014-05-14 17:55:15\] \<linuxmaniac> I will try to find the time  
-\[2014-05-14 17:55:37\] \<miconda> linuxmaniac: updatedb; locate time  
-\[2014-05-14 17:55:53\] \<linuxmaniac> :-)  
+wiki to summarize the proposal/issue
+\[2014-05-14 17:55:05\] \<miconda> linuxmaniac: that will be very good
+\[2014-05-14 17:55:15\] \<linuxmaniac> I will try to find the time
+\[2014-05-14 17:55:37\] \<miconda> linuxmaniac: updatedb; locate time
+\[2014-05-14 17:55:53\] \<linuxmaniac> :-)
 \[2014-05-14 17:56:01\] \<miconda> so we continue this via wiki and
-mailing lists  
+mailing lists
 \[2014-05-14 17:56:13\] \<miconda> just don’t foget to get the topic
-there  
+there
 \[2014-05-14 17:56:39\] \<stangrze> python test framework is quite nice,
-would be good fit if we would use pjsip to send/receive messages  
+would be good fit if we would use pjsip to send/receive messages
 \[2014-05-14 17:56:40\] \<miconda> and let’s see if \_gv\_ can plug some
-goodies  
-\[2014-05-14 17:56:44\] \<linuxmaniac> Ack  
+goodies
+\[2014-05-14 17:56:44\] \<linuxmaniac> Ack
 \[2014-05-14 17:57:19\] \<miconda> stangrze: noted. prefering erlang
-over python, but I can leave with for a test framework :-)  
-\[2014-05-14 17:57:43\] \<miconda> eZz: still around?  
-\[2014-05-14 17:57:43\] \<linuxmaniac> I would like python too  
+over python, but I can leave with for a test framework :-)
+\[2014-05-14 17:57:43\] \<miconda> eZz: still around?
+\[2014-05-14 17:57:43\] \<linuxmaniac> I would like python too
 \[2014-05-14 17:57:51\] \<caruizdiaz> libjitsi could also be an option.
-Everyone knows java :D  
-\[2014-05-14 17:57:58\] \<eZz> miconda: yeah  
+Everyone knows java :D
+\[2014-05-14 17:57:58\] \<eZz> miconda: yeah
 \[2014-05-14 17:58:25\] \<stangrze> erlang test frameworks are even
-nicer ;-)  
+nicer ;-)
 
 ## open discussion
 
 \[2014-05-14 17:58:26\] \<miconda> eZz: ok, you can say the details
-about the new module  
-\[2014-05-14 17:58:28\] \<eZz> well  
-\[2014-05-14 17:58:38\] \<miconda> stangrze: I am sure :-)  
+about the new module
+\[2014-05-14 17:58:28\] \<eZz> well
+\[2014-05-14 17:58:38\] \<miconda> stangrze: I am sure :-)
 \[2014-05-14 17:58:50\] \<eZz> I'm working on 2 new modules (basically,
-3 but 2 can be mixed)  
+3 but 2 can be mixed)
 \[2014-05-14 17:58:52\] \<caruizdiaz> erlang and golang are pending
-topics for me. Will learn them this year.  
-\[2014-05-14 17:58:58\] \<eZz> the first one is sec_dnsbl  
-\[2014-05-14 17:59:05\] \<eZz> block list using rbl lists  
+topics for me. Will learn them this year.
+\[2014-05-14 17:58:58\] \<eZz> the first one is sec_dnsbl
+\[2014-05-14 17:59:05\] \<eZz> block list using rbl lists
 \[2014-05-14 17:59:32\] \<eZz> caused a recent atack to my kamailio
-:-)  
+:-)
 \[2014-05-14 17:59:55\] \<eZz> the 2nd is sec_ids, intrussion detect
-system  
+system
 \[2014-05-14 18:00:20\] \<eZz> that is for blocking portscans and
-various malicious attempts to scan peers (e.g. asterisk and so on)  
-\[2014-05-14 18:00:42\] \<linuxmaniac> eZz... fail2ban?  
+various malicious attempts to scan peers (e.g. asterisk and so on)
+\[2014-05-14 18:00:42\] \<linuxmaniac> eZz... fail2ban?
 \[2014-05-14 18:01:19\] \<eZz> for kamailio? yes, a good idea but need
-to create a many rules  
+to create a many rules
 \[2014-05-14 18:01:41\] \<eZz> btw how about a thresholds and attempts
-counting?  
-\[2014-05-14 18:01:41\] \<linuxmaniac> many rules?  
-\[2014-05-14 18:01:49\] \<eZz> I'm using bayessian filters  
+counting?
+\[2014-05-14 18:01:41\] \<linuxmaniac> many rules?
+\[2014-05-14 18:01:49\] \<eZz> I'm using bayessian filters
 \[2014-05-14 18:02:46\] \<eZz> linuxmaniac: I did not found any flexible
-solution to cover it  
-\[2014-05-14 18:02:53\] \<eZz> fail2ban is just an optional  
+solution to cover it
+\[2014-05-14 18:02:53\] \<eZz> fail2ban is just an optional
 \[2014-05-14 18:02:59\] \<miconda> eZz: for the first module you query
-dnsbl and block if coming from such ip?  
-\[2014-05-14 18:03:07\] \<eZz> yes  
-\[2014-05-14 18:03:33\] \<miconda> the second is not clear for me…  
+dnsbl and block if coming from such ip?
+\[2014-05-14 18:03:07\] \<eZz> yes
+\[2014-05-14 18:03:33\] \<miconda> the second is not clear for me…
 \[2014-05-14 18:03:42\] \<eZz> if that IP is listed in public block
-lists  
-\[2014-05-14 18:04:14\] \<miconda> the sec_ids?  
-\[2014-05-14 18:04:44\] \<eZz> no, it is for sec_dnsbl  
-\[2014-05-14 18:04:53\] \<miconda> ok, that is clear  
-\[2014-05-14 18:05:08\] \<miconda> but sec_ids what does exactly?  
+lists
+\[2014-05-14 18:04:14\] \<miconda> the sec_ids?
+\[2014-05-14 18:04:44\] \<eZz> no, it is for sec_dnsbl
+\[2014-05-14 18:04:53\] \<miconda> ok, that is clear
+\[2014-05-14 18:05:08\] \<miconda> but sec_ids what does exactly?
 \[2014-05-14 18:05:34\] \<eZz> if you know there was a such project as
-snort  
+snort
 \[2014-05-14 18:06:22\] \<eZz> it is a ids for linux servers, I'm using
-a database of known attempts to hack the peers  
+a database of known attempts to hack the peers
 \[2014-05-14 18:06:59\] \<miconda> so again, interogating a
-server/database to see if an ip is potentially mallicious or not?  
-\[2014-05-14 18:07:26\] \<eZz> yes, it is using 3rd party database  
+server/database to see if an ip is potentially mallicious or not?
+\[2014-05-14 18:07:26\] \<eZz> yes, it is using 3rd party database
 \[2014-05-14 18:07:39\] \<miconda> eZz: btw, are the module in planning
-phase or kind of done already?  
-\[2014-05-14 18:07:55\] \<eZz> it is in the progress  
-\[2014-05-14 18:08:03\] \<miconda> s/module/modules/  
-\[2014-05-14 18:08:12\] \<miconda> ok  
-\[2014-05-14 18:08:17\] \<eZz> I did not pushed this yet  
-\[2014-05-14 18:08:29\] \<eZz> it is unstable for now  
+phase or kind of done already?
+\[2014-05-14 18:07:55\] \<eZz> it is in the progress
+\[2014-05-14 18:08:03\] \<miconda> s/module/modules/
+\[2014-05-14 18:08:12\] \<miconda> ok
+\[2014-05-14 18:08:17\] \<eZz> I did not pushed this yet
+\[2014-05-14 18:08:29\] \<eZz> it is unstable for now
 \[2014-05-14 18:08:55\] \<eZz> and for dnsbl module it is a problem of
-delays of requests  
+delays of requests
 \[2014-05-14 18:08:59\] \<caruizdiaz> do you have it publicly available
-so we can take a look?  
-\[2014-05-14 18:09:16\] \<eZz> not yes  
-\[2014-05-14 18:09:20\] \<eZz> yet  
-\[2014-05-14 18:09:28\] \<eZz> I'll push them as soon as possible  
-\[2014-05-14 18:09:37\] \<caruizdiaz> that would be great  
-\[2014-05-14 18:09:38\] \<eZz> at least you can test dnsbl  
+so we can take a look?
+\[2014-05-14 18:09:16\] \<eZz> not yes
+\[2014-05-14 18:09:20\] \<eZz> yet
+\[2014-05-14 18:09:28\] \<eZz> I'll push them as soon as possible
+\[2014-05-14 18:09:37\] \<caruizdiaz> that would be great
+\[2014-05-14 18:09:38\] \<eZz> at least you can test dnsbl
 \[2014-05-14 18:10:00\] \<miconda> for dnsbl, there could be some
-caching eventually  
-\[2014-05-14 18:10:08\] \<eZz> yes  
-\[2014-05-14 18:10:16\] \<eZz> it has negative and positive cache  
-\[2014-05-14 18:10:26\] \<miconda> ok  
-\[2014-05-14 18:10:38\] \<eZz> and white/black lists  
+caching eventually
+\[2014-05-14 18:10:08\] \<eZz> yes
+\[2014-05-14 18:10:16\] \<eZz> it has negative and positive cache
+\[2014-05-14 18:10:26\] \<miconda> ok
+\[2014-05-14 18:10:38\] \<eZz> and white/black lists
 \[2014-05-14 18:10:51\] \<miconda> then looking forward to get the first
-versions out there for a deeper look and test  
-\[2014-05-14 18:11:03\] \<eZz> alright :-)  
+versions out there for a deeper look and test
+\[2014-05-14 18:11:03\] \<eZz> alright :-)
 \[2014-05-14 18:11:39\] \<miconda> the last topic, iirc from the
-discussion above: caruizdiaz and some nosql  
+discussion above: caruizdiaz and some nosql
 \[2014-05-14 18:11:40\] \<eZz> well, another plan is to fix docs for
-app_python and minor bugs for app_java  
-\[2014-05-14 18:11:46\] \<eZz> I'm done  
+app_python and minor bugs for app_java
+\[2014-05-14 18:11:46\] \<eZz> I'm done
 \[2014-05-14 18:12:16\] \<miconda> eZz: you can do that directly …
-documentation is important, fixing bugs even more important :-)  
-\[2014-05-14 18:12:31\] \<eZz> yes :-)  
+documentation is important, fixing bugs even more important :-)
+\[2014-05-14 18:12:31\] \<eZz> yes :-)
 \[2014-05-14 18:13:10\] \<miconda> maybe we can run python test framwork
-from app_python, linuxmaniac will love to do that :-)  
+from app_python, linuxmaniac will love to do that :-)
 \[2014-05-14 18:13:14\] \<caruizdiaz> yes, I wanted to ask if there were
-any plans to natively support nosql databases  
-\[2014-05-14 18:13:28\] \<miconda> what do you mean natively?  
+any plans to natively support nosql databases
+\[2014-05-14 18:13:28\] \<miconda> what do you mean natively?
 \[2014-05-14 18:13:48\] \<caruizdiaz> currently, db API is purely SQL
-(aka, SQL DDL and DML)  
+(aka, SQL DDL and DML)
 \[2014-05-14 18:14:19\] \<miconda> well, the sql is in modules like
-db_mysql, db_postgress…  
+db_mysql, db_postgress…
 \[2014-05-14 18:14:20\] \<caruizdiaz> if we want to add, for example,
-mongodb, redis, etc, we have no way of using the current API to do so  
+mongodb, redis, etc, we have no way of using the current API to do so
 \[2014-05-14 18:14:26\] \<stangrze> i think you can connect to couchdb
-using json module  
+using json module
 \[2014-05-14 18:14:40\] \<miconda> but there is also cassandra
-implementation for db api  
-\[2014-05-14 18:14:41\] \<eZz> I'm also using mongodb and redis  
-\[2014-05-14 18:14:47\] \<eZz> and my module is using redis btw  
+implementation for db api
+\[2014-05-14 18:14:41\] \<eZz> I'm also using mongodb and redis
+\[2014-05-14 18:14:47\] \<eZz> and my module is using redis btw
 \[2014-05-14 18:14:49\] \<caruizdiaz> currently, we support cassandra,
-but only because cassandra has CQL, which resembles a poor SQL  
-\[2014-05-14 18:15:12\] \<caruizdiaz> and it is buggy for that reason.  
-\[2014-05-14 18:15:21\] \<miconda> but the db api is structure based  
-\[2014-05-14 18:15:34\] \<miconda> it doesn’t expose any sql  
-\[2014-05-14 18:15:43\] \<caruizdiaz> yes, but it has SQL embedded  
-\[2014-05-14 18:15:43\] \<miconda> plus there is db_berkely  
+but only because cassandra has CQL, which resembles a poor SQL
+\[2014-05-14 18:15:12\] \<caruizdiaz> and it is buggy for that reason.
+\[2014-05-14 18:15:21\] \<miconda> but the db api is structure based
+\[2014-05-14 18:15:34\] \<miconda> it doesn’t expose any sql
+\[2014-05-14 18:15:43\] \<caruizdiaz> yes, but it has SQL embedded
+\[2014-05-14 18:15:43\] \<miconda> plus there is db_berkely
 \[2014-05-14 18:15:58\] \<miconda> caruizdiaz: where is the sql
-embedded?  
+embedded?
 \[2014-05-14 18:16:25\] \<caruizdiaz> usrloc for example: it has some
 plain sql queries that make it impossible to use with a dbms that does
-not support sql  
-\[2014-05-14 18:16:33\] \<eZz> what about hadoop?  
+not support sql
+\[2014-05-14 18:16:33\] \<eZz> what about hadoop?
 \[2014-05-14 18:16:47\] \<miconda> caruizdiaz: iirc, that is for db only
-mode  
-\[2014-05-14 18:17:04\] \<miconda> to get the natted clients  
+mode
+\[2014-05-14 18:17:04\] \<miconda> to get the natted clients
 \[2014-05-14 18:17:40\] \<miconda> anyhow, that is done via db api
-raw_query  
+raw_query
 \[2014-05-14 18:17:55\] \<miconda> which can be made mod param to
-specify the format of the query  
-\[2014-05-14 18:18:14\] \<stangrze> +1 for this  
+specify the format of the query
+\[2014-05-14 18:18:14\] \<stangrze> +1 for this
 \[2014-05-14 18:18:15\] \<caruizdiaz> what do you suggest to support
-nosql databases in the database layer?  
+nosql databases in the database layer?
 \[2014-05-14 18:18:51\] \<miconda> caruizdiaz: not understanding your
-question exactly  
+question exactly
 \[2014-05-14 18:18:52\] \<caruizdiaz> maybe I am confused, but I
-remember seeing SQL in usrloc to load contacts from the database  
-\[2014-05-14 18:19:15\] \<miconda> caruizdiaz: should not be  
+remember seeing SQL in usrloc to load contacts from the database
+\[2014-05-14 18:19:15\] \<miconda> caruizdiaz: should not be
 \[2014-05-14 18:19:41\] \<caruizdiaz> will check that out later, but I
-am 90% sure there is.  
+am 90% sure there is.
 \[2014-05-14 18:19:56\] \<caruizdiaz> let me explain it with an
-example  
+example
 \[2014-05-14 18:20:29\] \<caruizdiaz> If I wanted to add a redis
 database to Kamailio, with the full feature set of including the modules
 that need a database backend, that would be impossible to my
-understanding  
+understanding
 \[2014-05-14 18:21:05\] \<caruizdiaz> and the reason for this is that
-Kamailio is tied to SQL databases.  
+Kamailio is tied to SQL databases.
 \[2014-05-14 18:21:12\] \<linuxmaniac> sure, how can you query a
-nonsql???  
+nonsql???
 \[2014-05-14 18:21:13\] \<miconda> the only one is for db only mode, to
-fetch the natted contacts  
+fetch the natted contacts
 \[2014-05-14 18:21:15\] \<eZz> will be a problems with object mapping
-only  
-\[2014-05-14 18:21:23\] \<eZz> but not with native formats  
+only
+\[2014-05-14 18:21:23\] \<eZz> but not with native formats
 \[2014-05-14 18:21:30\] \<miconda> so it does a custom match on flags
-column, to find those if nat flag set  
+column, to find those if nat flag set
 \[2014-05-14 18:21:53\] \<caruizdiaz> and that's precisely a reason it
-can't be used even with Cassandra  
+can't be used even with Cassandra
 \[2014-05-14 18:22:19\] \<caruizdiaz> because the syntax is incorrect
-for CQL parser  
+for CQL parser
 \[2014-05-14 18:22:25\] \<miconda> caruizdiaz: you have to write a
-connector implementing the api  
-\[2014-05-14 18:22:31\] \<miconda> as i said, there is one for bdb  
-\[2014-05-14 18:22:35\] \<miconda> there is one for db_text  
-\[2014-05-14 18:23:00\] \<miconda> none of them have any sql  
+connector implementing the api
+\[2014-05-14 18:22:31\] \<miconda> as i said, there is one for bdb
+\[2014-05-14 18:22:35\] \<miconda> there is one for db_text
+\[2014-05-14 18:23:00\] \<miconda> none of them have any sql
 \[2014-05-14 18:23:05\] \<caruizdiaz> that was the hint I was looking
-for, thank you :)  
-\[2014-05-14 18:23:23\] \<miconda> the api itself is not for sql  
+for, thank you :)
+\[2014-05-14 18:23:23\] \<miconda> the api itself is not for sql
 \[2014-05-14 18:23:32\] \<caruizdiaz> and what about usrloc (and maybe
-others), do we need to remove that raw sql query?  
+others), do we need to remove that raw sql query?
 \[2014-05-14 18:24:14\] \<miconda> for usrloc can be a mod param to
-specify the query  
+specify the query
 \[2014-05-14 18:24:31\] \<miconda> it is the query to get natted contact
-in db only mode  
+in db only mode
 \[2014-05-14 18:24:47\] \<caruizdiaz> ok, I was not aware of that
-param  
+param
 \[2014-05-14 18:24:50\] \<miconda> and that might not be supported by
-the connector you work with  
-\[2014-05-14 18:24:55\] \<miconda> it is not a param now  
-\[2014-05-14 18:24:58\] \<miconda> but can be added  
+the connector you work with
+\[2014-05-14 18:24:55\] \<miconda> it is not a param now
+\[2014-05-14 18:24:58\] \<miconda> but can be added
 \[2014-05-14 18:25:12\] \<caruizdiaz> but in either case, if we are
 going to be database agnostic, we should fully use the db abstraction
-layer  
+layer
 \[2014-05-14 18:25:39\] \<miconda> right now it is embedded, because it
-was for db sql mode only  
+was for db sql mode only
 \[2014-05-14 18:25:46\] \<stangrze> caruizdiaz: i know what you mean, i
-went through this writing erlang connector  
+went through this writing erlang connector
 \[2014-05-14 18:26:13\] \<miconda> when there will be db nosql only
-mode, then it can extended  
+mode, then it can extended
 \[2014-05-14 18:26:23\] \<caruizdiaz> maybe we could work on this
-together stangrze :)  
+together stangrze :)
 \[2014-05-14 18:26:31\] \<miconda> but db api is not really tied in any
-way to sql  
-\[2014-05-14 18:26:43\] \<miconda> again, you can look at db_berkely  
-\[2014-05-14 18:26:45\] \<caruizdiaz> thank you for the clarification  
-\[2014-05-14 18:26:48\] \<miconda> also db_ldap  
-\[2014-05-14 18:26:53\] \<caruizdiaz> I will, thanks.  
-\[2014-05-14 18:26:56\] \<miconda> but db_ldap is for v2  
+way to sql
+\[2014-05-14 18:26:43\] \<miconda> again, you can look at db_berkely
+\[2014-05-14 18:26:45\] \<caruizdiaz> thank you for the clarification
+\[2014-05-14 18:26:48\] \<miconda> also db_ldap
+\[2014-05-14 18:26:53\] \<caruizdiaz> I will, thanks.
+\[2014-05-14 18:26:56\] \<miconda> but db_ldap is for v2
 \[2014-05-14 18:26:57\] \<stangrze> would be nice if all queries could
-be configurabe parameters, not constructed by c code  
-\[2014-05-14 18:27:02\] \<miconda> perhaps is db2_ldap  
+be configurabe parameters, not constructed by c code
+\[2014-05-14 18:27:02\] \<miconda> perhaps is db2_ldap
 \[2014-05-14 18:27:28\] \<caruizdiaz> it's really important to support
 nosql database since is precisely the kind of databases we use in this
-industry, for performance reasons  
+industry, for performance reasons
 \[2014-05-14 18:27:29\] \<miconda> stangrze: are you aware of any other
-place than usrloc?  
+place than usrloc?
 \[2014-05-14 18:27:31\] \<stangrze> user cuold than use sql stored
-functions in postgresql in examble  
-\[2014-05-14 18:27:38\] \<miconda> where there are embedded queries?  
+functions in postgresql in examble
+\[2014-05-14 18:27:38\] \<miconda> where there are embedded queries?
 \[2014-05-14 18:28:23\] \<miconda> caruizdiaz: db api was added in 2001
-for that reason  
+for that reason
 \[2014-05-14 18:28:24\] \<stangrze> i dont remember that now, there are
-modules which refuses to load if raw_query capability is not provided  
+modules which refuses to load if raw_query capability is not provided
 \[2014-05-14 18:28:36\] \<miconda> and db_berkely is probably 10 years
-old  
+old
 \[2014-05-14 18:28:57\] \<miconda> but in my industry there were no
-nosql big demands  
+nosql big demands
 \[2014-05-14 18:29:08\] \<stangrze> take look how this stuff is done in
-gnugk  
+gnugk
 \[2014-05-14 18:29:08\] \<caruizdiaz> wow, I was in high school 10 years
-ago :D  
-\[2014-05-14 18:29:18\] \<eZz> :)  
+ago :D
+\[2014-05-14 18:29:18\] \<eZz> :)
 \[2014-05-14 18:29:24\] \<miconda> the object model doesn’t fit always
-the purpose  
+the purpose
 \[2014-05-14 18:30:15\] \<miconda> caruizdiaz: apparently only 7 years
-old  
-\[2014-05-14 18:30:29\] \<caruizdiaz> \*only\* :D  
-\[2014-05-14 18:30:43\] \<miconda> contributed by a guy from Cisco …  
+old
+\[2014-05-14 18:30:29\] \<caruizdiaz> \*only\* :D
+\[2014-05-14 18:30:43\] \<miconda> contributed by a guy from Cisco …
 \[2014-05-14 18:30:50\] \<stangrze> caruizdiaz: you may try use my
 db_erlang module and some intermediate code in erlang to connect to
-nosql  
-\[2014-05-14 18:30:58\] \<stangrze> it works with riak  
-\[2014-05-14 18:31:26\] \<miconda> anyhow, to conclude  
+nosql
+\[2014-05-14 18:30:58\] \<stangrze> it works with riak
+\[2014-05-14 18:31:26\] \<miconda> anyhow, to conclude
 \[2014-05-14 18:31:40\] \<miconda> it should work to connect to nosql
-modules with current db api  
+modules with current db api
 \[2014-05-14 18:31:48\] \<miconda> but a connector module has to be
-written  
+written
 \[2014-05-14 18:31:57\] \<caruizdiaz> I already starred your repo
-stangrze ;)  
+stangrze ;)
 \[2014-05-14 18:32:05\] \<miconda> and, if there is need for adjustments
-in the db api, then we can do it, no problem  
-\[2014-05-14 18:32:21\] \<caruizdiaz> cool  
+in the db api, then we can do it, no problem
+\[2014-05-14 18:32:21\] \<caruizdiaz> cool
 \[2014-05-14 18:32:23\] \<miconda> db api evolved over the time … and
-can still be changed with new versions  
+can still be changed with new versions
 \[2014-05-14 18:32:47\] \<miconda> the main problem with nosql is
-defining the objects  
+defining the objects
 \[2014-05-14 18:32:59\] \<miconda> which is not something that can be
-really generic  
+really generic
 \[2014-05-14 18:33:21\] \<miconda> because each company/service/system
-design the object to be optimized for their specific use case  
-\[2014-05-14 18:33:23\] \<caruizdiaz> that's right  
+design the object to be optimized for their specific use case
+\[2014-05-14 18:33:23\] \<caruizdiaz> that's right
 \[2014-05-14 18:33:51\] \<caruizdiaz> there are probably some tables
 that could be exported because of the way there were conceived, but we
-can work on that as well  
-\[2014-05-14 18:34:31\] \<caruizdiaz> they\*  
+can work on that as well
+\[2014-05-14 18:34:31\] \<caruizdiaz> they\*
 \[2014-05-14 18:34:59\] \<stangrze> maybe we could start a srdb3
-library, which would solve those issues  
-\[2014-05-14 18:35:17\] \<caruizdiaz> yes  
+library, which would solve those issues
+\[2014-05-14 18:35:17\] \<caruizdiaz> yes
 \[2014-05-14 18:35:30\] \<stangrze> there is no dierence in approach
-between srdb1 and 2  
+between srdb1 and 2
 \[2014-05-14 18:35:43\] \<miconda> btw, the db_perlvdb might be used as
-well  
+well
 \[2014-05-14 18:35:53\] \<caruizdiaz> this is actually a major software
 design task, and we should start a thread of the mailing list to gather
-some opinions and hints  
-\[2014-05-14 18:36:44\] \<linuxmaniac> +1  
-\[2014-05-14 18:37:20\] \<miconda> ok, anything else?  
-\[2014-05-14 18:37:39\] \<miconda> running over 2h30min by now …  
-\[2014-05-14 18:38:01\] \<stangrze> yes  
+some opinions and hints
+\[2014-05-14 18:36:44\] \<linuxmaniac> +1
+\[2014-05-14 18:37:20\] \<miconda> ok, anything else?
+\[2014-05-14 18:37:39\] \<miconda> running over 2h30min by now …
+\[2014-05-14 18:38:01\] \<stangrze> yes
 \[2014-05-14 18:38:34\] \<miconda> last chance to add something in
-discussion  
+discussion
 \[2014-05-14 18:38:41\] \<stangrze> i'd like someone to suggest me a
-name for that broadsoft as-feature-sync module  
-\[2014-05-14 18:38:57\] \<stangrze> this is generally presence related  
-\[2014-05-14 18:39:11\] \<miconda> isn’t that like sca module?  
-\[2014-05-14 18:39:16\] \<miconda> or something else?  
-\[2014-05-14 18:39:21\] \<linuxmaniac> I have to leave, see you!  
+name for that broadsoft as-feature-sync module
+\[2014-05-14 18:38:57\] \<stangrze> this is generally presence related
+\[2014-05-14 18:39:11\] \<miconda> isn’t that like sca module?
+\[2014-05-14 18:39:16\] \<miconda> or something else?
+\[2014-05-14 18:39:21\] \<linuxmaniac> I have to leave, see you!
 \[2014-05-14 18:39:36\] \<stangrze> its a subscibtion and sync for stuff
-like dnd and callforward  
+like dnd and callforward
 \[2014-05-14 18:39:44\] \<miconda>
-<http://kamailio.org/docs/modules/stable/modules/sca.html>  
-\[2014-05-14 18:39:54\] \<miconda> ok, so not for blinking lamps, etc…  
+<http://kamailio.org/docs/modules/stable/modules/sca.html>
+\[2014-05-14 18:39:54\] \<miconda> ok, so not for blinking lamps, etc…
 \[2014-05-14 18:39:58\] \<stangrze> you can to that on cisco/linksys
-phones  
-\[2014-05-14 18:40:41\] \<caruizdiaz> chau Victor  
-\[2014-05-14 18:41:08\] \<stangrze> this is not sca  
+phones
+\[2014-05-14 18:40:41\] \<caruizdiaz> chau Victor
+\[2014-05-14 18:41:08\] \<stangrze> this is not sca
 \[2014-05-14 18:41:46\] \<miconda> linuxmaniac: thanks for all here,
-have a nice evening!  
+have a nice evening!
 \[2014-05-14 18:42:12\] \<stangrze> it let you set stuff using phone
 gui, and get this propagated to application server, and back after phone
-reboot in ex.  
+reboot in ex.
 \[2014-05-14 18:42:33\] \<miconda> stangrze: from phone to kamailio is
-sip?  
+sip?
 \[2014-05-14 18:42:52\] \<miconda> is the classic subscribe/notify used
-around?  
-\[2014-05-14 18:43:02\] \<stangrze> yes,  
+around?
+\[2014-05-14 18:43:02\] \<stangrze> yes,
 \[2014-05-14 18:43:06\] \<stangrze>
-<http://community.polycom.com/polycom/attachments/polycom/VoIP/2233/1/DeviceFeatureKeySynchronizationFD.pdf>  
-\[2014-05-14 18:43:21\] \<stangrze> yes, but somehow spoiled, see spec  
+<http://community.polycom.com/polycom/attachments/polycom/VoIP/2233/1/DeviceFeatureKeySynchronizationFD.pdf>
+\[2014-05-14 18:43:21\] \<stangrze> yes, but somehow spoiled, see spec
 \[2014-05-14 18:43:49\] \<miconda> is it going to reuse presence or pua
-modules in any way?  
-\[2014-05-14 18:43:56\] \<stangrze> yes  
+modules in any way?
+\[2014-05-14 18:43:56\] \<stangrze> yes
 \[2014-05-14 18:43:58\] \<miconda> or is going to be all standalone
-module?  
+module?
 \[2014-05-14 18:44:16\] \<miconda> ok, then you can prefix it with
-presence\_ or pua\_, depending on which one relies on  
-\[2014-05-14 18:44:21\] \<miconda> and then add some suffic  
-\[2014-05-14 18:44:38\] \<miconda> presence_dksf  
+presence\_ or pua\_, depending on which one relies on
+\[2014-05-14 18:44:21\] \<miconda> and then add some suffic
+\[2014-05-14 18:44:38\] \<miconda> presence_dksf
 \[2014-05-14 18:45:03\] \<stangrze> i guessd that, ;-) but
-presence_what? broadsoft? could have trademark issues  
+presence_what? broadsoft? could have trademark issues
 \[2014-05-14 18:45:10\] \<miconda> \_dfks - Device Feature Key
-Synchronization  
-\[2014-05-14 18:45:18\] \<stangrze> ok, cool  
-\[2014-05-14 18:45:21\] \<stangrze> thanks  
-\[2014-05-14 18:45:43\] \<miconda> welcome  
-\[2014-05-14 18:45:59\] \<miconda> is this a planned module?  
-\[2014-05-14 18:46:11\] \<stangrze> i actually have some stuff working  
-\[2014-05-14 18:46:33\] \<miconda> ok  
-\[2014-05-14 18:46:54\] \<miconda> any other topics to discuss?  
+Synchronization
+\[2014-05-14 18:45:18\] \<stangrze> ok, cool
+\[2014-05-14 18:45:21\] \<stangrze> thanks
+\[2014-05-14 18:45:43\] \<miconda> welcome
+\[2014-05-14 18:45:59\] \<miconda> is this a planned module?
+\[2014-05-14 18:46:11\] \<stangrze> i actually have some stuff working
+\[2014-05-14 18:46:33\] \<miconda> ok
+\[2014-05-14 18:46:54\] \<miconda> any other topics to discuss?
 \[2014-05-14 18:46:57\] \<stangrze> using pathed pua, and pua_mi i can
-preload doc for initial subscription, and get that on phone screen  
+preload doc for initial subscription, and get that on phone screen
 \[2014-05-14 18:48:16\] \<stangrze> i thin ther eis an issue in pua, it
 is using some bit flags to mark event types, it is not good for adding
-features  
-\[2014-05-14 18:48:41\] \<stangrze> and more event types  
+features
+\[2014-05-14 18:48:41\] \<stangrze> and more event types
 \[2014-05-14 18:48:53\] \<miconda> stangrze: yes, that has to be
-reworked somehow  
-\[2014-05-14 18:49:18\] \<stangrze> ok, i'm done, thanks  
+reworked somehow
+\[2014-05-14 18:49:18\] \<stangrze> ok, i'm done, thanks
 \[2014-05-14 18:49:43\] \<miconda> welcome! looking forward to all these
-modules  
-\[2014-05-14 18:49:59\] \<miconda> then, we are finished!  
-\[2014-05-14 18:50:06\] \<caruizdiaz> :)  
-\[2014-05-14 18:50:32\] \<miconda> thank everyone!  
+modules
+\[2014-05-14 18:49:59\] \<miconda> then, we are finished!
+\[2014-05-14 18:50:06\] \<caruizdiaz> :)
+\[2014-05-14 18:50:32\] \<miconda> thank everyone!
 \[2014-05-14 18:50:34\] \<caruizdiaz> have you all GMT +x people a nice
-evening :)  
-\[2014-05-14 18:50:47\] \<javar> miconda: thank you!  
-\[2014-05-14 18:50:52\] \<caruizdiaz> thanks to you  
+evening :)
+\[2014-05-14 18:50:47\] \<javar> miconda: thank you!
+\[2014-05-14 18:50:52\] \<caruizdiaz> thanks to you
 \[2014-05-14 18:51:15\] \<miconda> hopefully I have the chat history on,
-so I will publish the relevant discussion on wiki  
+so I will publish the relevant discussion on wiki
 \[2014-05-14 18:51:56\] \<miconda> have a productive day or nice
-evening, depending where you are!  
+evening, depending where you are!
 \[2014-05-14 18:52:17\] \<caruizdiaz> it's the middle of the day here:
-productive day ahead  
-\[2014-05-14 18:54:07\] \<eZz> thanks to all  
-\[2014-05-14 18:54:19\] \<eZz> have a great evening/night!  
-\[2014-05-14 18:54:45\] \<caruizdiaz> bye bye  
-\[2014-05-14 18:55:01\] \<miconda> bye  
+productive day ahead
+\[2014-05-14 18:54:07\] \<eZz> thanks to all
+\[2014-05-14 18:54:19\] \<eZz> have a great evening/night!
+\[2014-05-14 18:54:45\] \<caruizdiaz> bye bye
+\[2014-05-14 18:55:01\] \<miconda> bye

docs/devel/irc-meetings/2015a.md

@@ -82,10 +82,10 @@ to crash or lock up by sending messages to the server process.
 #### Reporting a security Vulnerability
 
 If you believe there's a security vulnerability, please don't use the
-public forums. Send e-mail to [email protected] and the issue will
+public forums. Send e-mail to <[email protected]> and the issue will
 be handled properly.
 
-1. Send an e-mail to [email protected] and include the following
+1. Send an e-mail to <[email protected]> and include the following
     information
 
 <!-- -->
@@ -110,7 +110,7 @@ take the role of Kamailio Security Officers. One of these should manage
 each security incident - which does not mean solving the code issue, but
 managing the process from report to publication and patch release.
 
-#### [email protected]
+#### <[email protected]>
 
 This address should have a PGP key associated, used by the security
 officers.

docs/devel/irc-meetings/2019b.md

@@ -135,7 +135,7 @@ Collaborative Projects:
 
 #### 3.1 server maintenance
 
-- www.kamailio.org Debian OS level fine at the moment
+- <www.kamailio.org> Debian OS level fine at the moment
 - ansible/puppet experiments from Victor
 - to be decided if its ansible or puppet
 
@@ -149,7 +149,7 @@ Collaborative Projects:
 - discussion synchron vs. async communication modes
 - good quality of mailing lists, professional communication
 
-#### www.kamailio.org
+#### <www.kamailio.org>
 
 - current web page a bit cluttered, needs some cleanup
 - discussions for re-design on the meeting

docs/devel/irc-meetings/2020b.md

@@ -100,7 +100,7 @@ are a bit late.
 15:07:03 **@miconda** ok, we should start
 15:07:14 **@joelsdc1** :wave:
 15:07:44 **@miconda** link to wiki with agenda:
-https:*www.kamailio.org/wiki/devel/irc-meetings/2020b
+https:*<www.kamailio.org/wiki/devel/irc-meetings/2020b>
 15:08:25 **@miconda** first, as usual, major or minor issues with
 Kamailio
 15:08:43 **@miconda** anything not reported yet on bug tracker that
@@ -345,7 +345,7 @@ that feeling over the time
 16:10:34 **@henning** we might want to not move anything to github
 16:10:42 **@miconda** and again, it may not be even true
 16:10:59 **@vseva**
-https:*www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works
+https:*<www.jeffgeerling.com/blog/2020/travis-cis-new-pricing-plan-threw-wrench-my-open-source-works>
 16:11:45 **@vseva** everything related to travis-ci is related to tests
 so not essential
 16:12:11 **@vseva** \> \<@henning:matrix.kamailio.dev> we might want to
@@ -397,7 +397,7 @@ very short downtime
 this matrix group and the old irc ...
 16:25:29 **@miconda** but you can always propose new (online/offline)
 tools to use
-16:25:46 **@henning** the day to day maintenance of www.kamailio.org is
+16:25:46 **@henning** the day to day maintenance of <www.kamailio.org> is
 going fine, i usually do it once a week for some minutes
 16:26:08 **@henning** we have some time left until the next debian
 upgrade is necessary ;)
@@ -498,7 +498,7 @@ local-hooking network stack
 in netfilter
 16:51:59 **@mojtaba.esfandiari** oej: absolutely yes
 16:52:29 **@mojtaba.esfandiari** For more information about
-this:https:*www.slideshare.net/mespio/lreproxy-module-for-kamailio-presenation
+this:https:*<www.slideshare.net/mespio/lreproxy-module-for-kamailio-presenation>
 16:52:51 **@henning** i think the focus of rtpengine is more to provide
 a wide range of RTP handling functionality, and the focus of lreproxy
 more on proxy performance and throughput, correct?

docs/devel/irc-meetings/2023a.md

@@ -56,7 +56,7 @@ Kamailio Development Status:
 - open issues (dcm)
 - minor releases for 5.6 and 5.7 branches (dcm)
 - tracker issues review:
-  - https://github.com/kamailio/kamailio/issues/
+  - <https://github.com/kamailio/kamailio/issues/>
 - summary of packaging and distributions
 - summary of using github actions
 
@@ -91,7 +91,7 @@ Collaborative Projects:
 |10:24:24|@miconda:matrix.kamailio.dev|ready to start|
 |10:24:36|@miconda:matrix.kamailio.dev|sorry again for the delay!|
 |10:24:57|@miconda:matrix.kamailio.dev|Hello everybody!|
-|10:25:31|@miconda:matrix.kamailio.dev|a little bit of an agenda at: https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings/2023a.md|
+|10:25:31|@miconda:matrix.kamailio.dev|a little bit of an agenda at: <https://github.com/kamailio/kamailio-wiki/blob/main/docs/devel/irc-meetings/2023a.md>|
 |10:27:42|@miconda:matrix.kamailio.dev|hopefully those interested in the meetings are still around, so, the first topic would be the follow up after the Dusseldorf in-person meeting|
 |10:28:17|@miconda:matrix.kamailio.dev|the most topic debated so far was about obsoleting a group of modules|
 |10:28:40|@miconda:matrix.kamailio.dev|feedback on mailing list showed that some are still used|
@@ -106,7 +106,7 @@ Collaborative Projects:
 |10:32:03|@miconda:matrix.kamailio.dev|ok|
 |10:32:13|@henning:matrix.kamailio.dev||
 |10:33:15|@fred:matrix.lod.com|Trying to remember which modules these were...|
-|10:34:12|@miconda:matrix.kamailio.dev|here is the email announcing them: https://kamailio.org/mailman3/hyperkitty/list/[email protected]/message/56MTKAXALSMBPFCA4KRMUQPJXMU65XLV/|
+|10:34:12|@miconda:matrix.kamailio.dev|here is the email announcing them: <https://kamailio.org/mailman3/hyperkitty/list/[email protected]/message/56MTKAXALSMBPFCA4KRMUQPJXMU65XLV/>|
 |10:34:13|@fred:matrix.lod.com|Found them|
 |10:35:01|@henning:matrix.kamailio.dev|there have been not much feedback on the list|
 |10:35:03|@miconda:matrix.kamailio.dev|with the correction that uri_db was mistakenly added there|
@@ -168,7 +168,7 @@ Collaborative Projects:
 |10:58:24|@miconda:matrix.kamailio.dev|centos 6?!?|
 |11:00:13|@miconda:matrix.kamailio.dev|nex and probably last one from Dusseldorf, more for information ...|
 |11:00:36|@miconda:matrix.kamailio.dev|the addition of pre-commit hooks that could help formatting the code, removing trailing whitespaces, etc ...|
-|11:00:48|@miconda:matrix.kamailio.dev|if you missed the email about it, here it is: https://kamailio.org/mailman3/hyperkitty/list/[email protected]/message/7PSVLEKOMSCDMUYN4VZLIO4ZBRBJXMF6/|
+|11:00:48|@miconda:matrix.kamailio.dev|if you missed the email about it, here it is: <https://kamailio.org/mailman3/hyperkitty/list/[email protected]/message/7PSVLEKOMSCDMUYN4VZLIO4ZBRBJXMF6/>|
 |11:01:04|@miconda:matrix.kamailio.dev|same one was sent to sr-users|
 |11:02:07|@vseva:matrix.kamailio.dev|hope it's helping|
 |11:02:43|@vseva:matrix.kamailio.dev|you can always skip checks with ``SKIP=<name>`` too|
@@ -229,13 +229,13 @@ Collaborative Projects:
 |11:26:46|@fred:matrix.lod.com|even longer =)|
 |11:26:55|@fred:matrix.lod.com|June 2026|
 |11:26:55|@henning:matrix.kamailio.dev||
-|11:27:07|@vseva:matrix.kamailio.dev|https://wiki.debian.org/LTS|
+|11:27:07|@vseva:matrix.kamailio.dev|<https://wiki.debian.org/LTS>|
 |11:27:24|@henning:matrix.kamailio.dev||
 |11:27:48|@vseva:matrix.kamailio.dev|image.png|
 |11:28:34|@vseva:matrix.kamailio.dev|no real rush but I would try to move to bookworm|
-|11:28:39|@devopsec:matrix.org|just a side note, this tool this awesome for checking EOL dates, here is the debian entry https://endoflife.date/debian|
+|11:28:39|@devopsec:matrix.org|just a side note, this tool this awesome for checking EOL dates, here is the debian entry <https://endoflife.date/debian>|
 |11:29:33|@vseva:matrix.kamailio.dev|I think the hard part was already done migrating the mailman|
-|11:29:38|@fred:matrix.lod.com|speaking of fun url's.... https://rtfm.tel/kamailio ;)|
+|11:29:38|@fred:matrix.lod.com|speaking of fun url's.... <https://rtfm.tel/kamailio> ;)|
 |11:30:27|@miconda:matrix.kamailio.dev|yep, hopefully debian 11 to 12 is going to be easier than 10 to 11|
 |11:30:40|@fred:matrix.lod.com|I need to move kama3 to 11|
 |11:30:57|@miconda:matrix.kamailio.dev|removal of python2 brought some headaches with many apps, including unavailability of mailman2|
@@ -278,7 +278,7 @@ Collaborative Projects:
 |11:51:03|@miconda:matrix.kamailio.dev|is LGPL, so probably *BSD guys have nothing againt it, like they usually have against pure GPL software :-)|
 |11:51:39|@miconda:matrix.kamailio.dev|anyhow, I am not familiar with as well, if found useful somewhere, it can be considered of course|
 |11:51:50|@miconda:matrix.kamailio.dev|I think rtpengine uses it extensively ...|
-|11:52:32|@vseva:matrix.kamailio.dev|https://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/devel/glib2/index.html|
+|11:52:32|@vseva:matrix.kamailio.dev|<https://cdn.netbsd.org/pub/pkgsrc/current/pkgsrc/devel/glib2/index.html>|
 |11:52:33|@henning:matrix.kamailio.dev|yes,  its used from rtpengine|
 |11:52:45|@miconda:matrix.kamailio.dev|as there are no major topics I can add here, everyone feel free to propose ... we can aproach in the order of posting ...|
 |11:53:35|@miconda:matrix.kamailio.dev|it's like 1h30min since we started ... time flies quickly ...|
@@ -299,7 +299,7 @@ Collaborative Projects:
 |12:01:38|@miconda:matrix.kamailio.dev|what's new and worth discussing from RTC space|
 |12:01:48|@miconda:matrix.kamailio.dev| * what's new and worth discussing from RTC space?!?|
 |12:02:48|@miconda:matrix.kamailio.dev|noticed some hot debates around Matrix changing the license and requiring CLA, ... Asterisk willing to close mailing lsits ... anything else that I missed?|
-|12:03:43|@miconda:matrix.kamailio.dev|btw, FOSDEM 2024 has again an RTC devroom: https://lists.fosdem.org/pipermail/fosdem/2023q4/003518.html|
+|12:03:43|@miconda:matrix.kamailio.dev|btw, FOSDEM 2024 has again an RTC devroom: <https://lists.fosdem.org/pipermail/fosdem/2023q4/003518.html>|
 |12:03:59|@fred:matrix.lod.com|The matrix change should be fun ;)|
 |12:04:06|@miconda:matrix.kamailio.dev|not sure I can go at this edition, I will try, but I don't know at this moment|
 |12:05:12|@miconda:matrix.kamailio.dev|is matrix now AGPL? or what they changed to? I think I saw it but I forgot  ...|
@@ -310,7 +310,7 @@ Collaborative Projects:
 |12:07:44|@fred:matrix.lod.com|[Matrix announcement](https://element.io/blog/element-to-adopt-agplv3/)|
 |12:09:16|@miconda:matrix.kamailio.dev|we can go back to IRC if matrix derails :-)|
 |12:09:54|@fred:matrix.lod.com|xmpp ;)|
-|12:11:23|@henning:matrix.kamailio.dev|regarding open source support, I've had some discussion about similar topics some weeks ago with the homer guys https://github.com/sipcapture/homer-ui/issues/627|
+|12:11:23|@henning:matrix.kamailio.dev|regarding open source support, I've had some discussion about similar topics some weeks ago with the homer guys <https://github.com/sipcapture/homer-ui/issues/627>|
 |12:12:32|@henning:matrix.kamailio.dev|unfortunately it seems not many companies support their open source development efforts|
 |12:13:57|@henning:matrix.kamailio.dev|they also looking more into moving to homer 10, which would be basically use grafana to do some of the infrastruture stuff|
 |12:15:06|@miconda:matrix.kamailio.dev|is H 10 out? or work in progress (eta in such case)?|

docs/devel/irc-meetings/securityprocedure.md

@@ -13,10 +13,10 @@ to crash or lock up by sending messages to the server process.
 ##### Reporting a security Vulnerability
 
 If you believe there's a security vulnerability, please don't use the
-public forums. Send e-mail to [email protected] and the issue will
+public forums. Send e-mail to <[email protected]> and the issue will
 be handled properly.
 
-1. Send an e-mail to [email protected] and include the following
+1. Send an e-mail to <[email protected]> and include the following
     information
 
 <!-- -->
@@ -40,7 +40,7 @@ take the role of Kamailio Security Officers. One of these should manage
 each security incident - which does not mean solving the code issue, but
 managing the process from report to publication and patch release.
 
-##### [email protected]
+##### <[email protected]>
 
 This address should have a PGP key associated, used by the security
 officers.

docs/features/new-in-5.4.x.md

@@ -118,8 +118,8 @@ statistics
 
 Added new **cfgt.list** and **cfgt.clean** RPC commands
 
-- https://www.kamailio.org/docs/modules/5.4.x/modules/cfgt.html#cfgt.r.list
-- https://www.kamailio.org/docs/modules/5.4.x/modules/cfgt.html#cfgt.r.clean
+- <https://www.kamailio.org/docs/modules/5.4.x/modules/cfgt.html#cfgt.r.list>
+- <https://www.kamailio.org/docs/modules/5.4.x/modules/cfgt.html#cfgt.r.clean>
 - switch from deprecated /var/run to /run
 
 ### corex
@@ -310,11 +310,11 @@ Add new pseudo-variables:
 
 Add **path** value to xavp_rcd location record
 
-- https://www.kamailio.org/docs/modules/5.4.x/modules/registrar.html#registrar.p.xavp_rcd
+- <https://www.kamailio.org/docs/modules/5.4.x/modules/registrar.html#registrar.p.xavp_rcd>
 
 Add **xavp_rcd_mask** parameter to control what values to skip
 
-- https://www.kamailio.org/docs/modules/5.4.x/modules/registrar.html#registrar.p.xavp_rcd_mask
+- <https://www.kamailio.org/docs/modules/5.4.x/modules/registrar.html#registrar.p.xavp_rcd_mask>
 - control what values to add to xavp_rcd via xavp_rcd_mask parameter
 - option to send 423 when expires less than min_expires with the
     min_expires_mode parameter

docs/features/new-in-devel.md

@@ -5,7 +5,7 @@ released in late 2024 or early 2025**.
 
 **Previous devel, current stable, version was 5.8.x (released during the spring of 2024), see what was new in that release at:**
 
-- https://www.kamailio.org/wikidocs/features/new-in-5.8.x/
+- <https://www.kamailio.org/wikidocs/features/new-in-5.8.x/>
 
 *This is a draft of new features added in devel version,
 manually updated, thus not always synchronized with what is new in

docs/index.md

@@ -258,6 +258,6 @@ Old Exports APIs:
 
 📓 The initial content was migrated to github.com from an open wiki portal, where people could contribute
 without any restrictions. Should anyone notice any *illegal* content please email to
-*[email protected]* or open an issue. **kamailio.org** organization is not responsible
+*<[email protected]>* or open an issue. **kamailio.org** organization is not responsible
 for the content contributed by external people and commits to react in a reasonable time when
 such content is reported.

docs/install/3.2.x/git.md

@@ -315,7 +315,7 @@ Now you have the latest Kamailio (OpenSER) devel running on your system.
 ## 12. Time for maintenance service
 
 Notification about GIT commits are sent to the mailing list:
-**[email protected]**. Each commit notification contains the
+**<[email protected]>**. Each commit notification contains the
 reference to the branch where the commit has been done. If the commit
 message contains the lines:
 

docs/install/3.3.x/git.md

@@ -320,7 +320,7 @@ Now you have the latest Kamailio (OpenSER) devel running on your system.
 ## 12. Time for maintenance service
 
 Notification about GIT commits are sent to the mailing list:
-**[email protected]**. Each commit notification contains the
+**<[email protected]>**. Each commit notification contains the
 reference to the branch where the commit has been done. If the commit
 message contains the lines:
 

docs/install/4.0.x/git.md

@@ -318,7 +318,7 @@ Now you have the latest Kamailio devel running on your system.
 ## 12. Time for maintenance service
 
 Notification about GIT commits are sent to the mailing list:
-**[email protected]**. Each commit notification contains the
+**<[email protected]>**. Each commit notification contains the
 reference to the branch where the commit has been done. If the commit
 message contains the lines:
 

docs/install/4.1.x/git.md

@@ -313,7 +313,7 @@ Now you have the latest Kamailio devel running on your system.
 ## 12. Time for maintenance service
 
 Notification about GIT commits are sent to the mailing list:
-**[email protected]**. Each commit notification contains the
+**<[email protected]>**. Each commit notification contains the
 reference to the branch where the commit has been done. If the commit
 message contains the lines:
 

docs/install/4.2.x/git.md

@@ -313,7 +313,7 @@ Now you have the latest Kamailio devel running on your system.
 ## 12. Time for maintenance service
 
 Notification about GIT commits are sent to the mailing list:
-**[email protected]**. Each commit notification contains the
+**<[email protected]>**. Each commit notification contains the
 reference to the branch where the commit has been done. If the commit
 message contains the lines:
 

docs/install/4.3.x/git.md

@@ -320,7 +320,7 @@ Now you have the latest Kamailio devel running on your system.
 ## 12. Time for maintenance service
 
 Notification about GIT commits are sent to the mailing list:
-**[email protected]**. Each commit notification contains the
+**<[email protected]>**. Each commit notification contains the
 reference to the branch where the commit has been done. If the commit
 message contains the lines:
 

docs/install/4.4.x/git.md

@@ -328,7 +328,7 @@ Now you have the latest Kamailio devel running on your system.
 ## 12. Time for maintenance service
 
 Notification about GIT commits are sent to the mailing list:
-**[email protected]**. Each commit notification contains the
+**<[email protected]>**. Each commit notification contains the
 reference to the branch where the commit has been done. If the commit
 message contains the lines:
 

docs/install/devel/git.md

@@ -313,7 +313,7 @@ Now you have the latest Kamailio devel running on your system.
 ## 12. Time for maintenance service
 
 Notification about GIT commits are sent to the mailing list:
-**[email protected]**. Each commit notification contains the
+**<[email protected]>**. Each commit notification contains the
 reference to the branch where the commit has been done. If the commit
 message contains the lines:
 

docs/install/upgrade/5.5.x-to-5.6.0.md

@@ -40,7 +40,7 @@ Following tokens are used to mark the changes:
 
 #### siputils
 
-- removed `ring_insert_callid()` function (see: https://github.com/kamailio/kamailio/issues/2989)
+- removed `ring_insert_callid()` function (see: <https://github.com/kamailio/kamailio/issues/2989>)
 
 #### uac_redirect
 

docs/install/upgrade/5.6.x-to-5.7.0.md

@@ -44,7 +44,7 @@ Following tokens are used to mark the changes:
 ## Core
 
 - INF: new core parameter `return_mode` allows a new mode to evaluate the return codes from functions and routing blocks:
-  - https://www.kamailio.org/wikidocs/cookbooks/devel/core/#return_mode
+  - <https://www.kamailio.org/wikidocs/cookbooks/devel/core/#return_mode>
 
 ### Parameters
 

docs/install/upgrade/5.7.x-to-5.8.0.md

@@ -39,7 +39,7 @@ Following tokens are used to mark the changes:
 
 Archived modules can be found in the repository:
 
-- https://github.com/kamailio/kamailio-archive
+- <https://github.com/kamailio/kamailio-archive>
 
 ### Renamed Modules
 

docs/tutorials/auth/auth_db.md

@@ -1,6 +1,6 @@
 **Note: This document is work in progress and yet unfinished!**
 
-written by Emmanuel Schmidbauer ([email protected])
+written by Emmanuel Schmidbauer (<[email protected]>)
 
 This guide is designed to illustrate how to setup auth_db and usrloc to
 do digest authentication using a database backend. I will be using a

docs/tutorials/dns/dnssec.md

@@ -307,7 +307,7 @@ the web. Among them:
 One way to test is to setup two instances of Kamailio, one serving
 `domainA.com` and the second `domainB.com`.
 
-Then [email protected] can call `[email protected]`. Kamailio instance
+Then <[email protected]> can call `[email protected]`. Kamailio instance
 serving `domainA.com` will do DNS lookup do discover the IP address of
 `domainB.com`
 
@@ -326,7 +326,7 @@ Launch Kamailio with DNSSEC module enabled and try to send a SIP package
 to the domain `www.dnssec-failed.org`. DNS resolving for this domain
 should fail, as it is a test domain which provides an incorrect
 signature. Kamailio should report: "0(70805) INFO: dnssec
-\[dnssec_func.c:145\]: invalid domain www.dnssec-failed.org reason
+\[dnssec_func.c:145\]: invalid domain <www.dnssec-failed.org> reason
 VAL_UNTRUSTED_ANSWER"
 
 ## Remarks

docs/tutorials/getting-started/main.md

@@ -30,7 +30,7 @@ Given the above, a good understanding of SIP is critical to get faster
 familiar with Kamailio, especially with its configuration file routing
 rules.
 
-Session Initiation Protocol (SIP) is specified by IETF (www.ietf.org),
+Session Initiation Protocol (SIP) is specified by IETF (<www.ietf.org>),
 with the core specification in the RFC 3261:
 
 - [https://tools.ietf.org/html/rfc3261](https://tools.ietf.org/html/rfc3261)