Re: [SR-Users] [sr-dev] new module db_kazoo

Hi Daniel, you can check our current code at https://github.com/2600hz/kazoo-kamailio/tree/4.0https://github.com/2600hz/… this is already compatible with master from kamailio (tests running ok). we will start to update the docs when we commit to master and will get it ready before 4.2. specific for kazoo? I mean the object structure, how are the fields name set, from the name of the columns? Is there a >>wrapper to specify the command (e.g., insert, delete, select)? Or maybe you can provide an example of such object... No, the payloads are what you want. here's a sample on how we are using to handle REGISTER messages if ($sht(auth_cache=>$Au) != $null && pv_auth_check("$fd", "$sht(auth_cache=>$Au)", "0", "0")) { xlog("L_INFO", "$ci|log|authenticated $Au via cached SIP creds"); } else { ## RABBITMQ - Credentials fetch ## build the payload 'directory' , 'Event-Name' : 'authn_req', 'Method' : 'REGISTER', 'Auth-Realm' : '" + $fd + "', 'Auth-User' : '" + $fU + "', 'From' : '" + $fu + "', 'To' : '" + $tu +"' }"; $var(amqp_routing_key) = "authn.req." + $(fd{kz.encode}); // kz.encode is a helper function to encode properly to amqp if(kazoo_query("callmgr", $var(amqp_routing_key), $var(amqp_payload_request))) { // kazoo_query publishes and expects answer xlog("L_DBG", "$ci|log|amqp_result = $kzR"); // $kzR is the result payload $var(password) = $(kzR{kz.json,Auth-Password}); // kz.json is a helper to extract values from payload, nested values are permitted // it could be something like $(kzR{kz.json,*Channels[0].switch_url* }) if($var(password) != $null) { if (!pv_auth_check("$fd", "$var(password)", "0", "0")) { we build the payload and publish it to rabbitmq, in this case we wait for a correlated msg to get the result. kazoo_publish -> sends only kazoo_query -> sends and waits for correlated answer here's an example on how we subscribe to a exchange event_route[kazoo:mod-init] { #!ifdef PRESENCE-ROLE $var(payload) = "{ 'exchange' : 'dialoginfo' , 'type' : 'direct', 'queue' : 'BLF-QUEUE-MY_HOSTNAME', 'routing' : 'BLF-MY_HOSTNAME', 'auto_delete' : 0, 'durable' : 1, 'no_ack' : 0, 'wait_for_consumer_ack' : 1 }"; kazoo_subscribe("$var(payload)"); #!endif } and how we react when we get a message event_route[kazoo:consumer-event-presence-update] { xlog("L_INFO", "received $(kzE{kz.json,Event-Package}) update for $(kzE{kz.json,From})"); kazoo_pua_publish($kzE); pres_refresh_watchers("$(kzE{kz.json,From})", "$(kzE{kz.json,Event-Package})", 1); } the event_route name is built from the payload we receive on the subscription kazoo:consumer-event - fixed -presence - taken from parameter amqp_consumer_event_key -update - taken from parameter amqp_consumer_event_subkey amqp_consumer_event_key and amqp_consumer_event_subkey are for now parameters for the module but we want to make by subscription. from the above example we will change it to $var(payload) = "{ *'key' : 'fieldname', 'subkey' : 'fieldname'*, 'exchange' : 'dialoginfo' , 'type' : 'direct', 'queue' : 'BLF-QUEUE-MY_HOSTNAME', 'routing' : 'BLF-MY_HOSTNAME', 'auto_delete' : 0, 'durable' : 1, 'no_ack' : 0, 'wait_for_consumer_ack' : 1 }"; right now, all interaction is made from configuration script. the long term will be to create a bind structure so that other modules can interact directly with it. let me know if that helps Best ------------------------------------------------------------------------ *From:* Daniel-Constantin Mierla [miconda(a)gmail.com] *Sent:* Tuesday, September 09, 2014 4:45 AM *To:* Kamailio (SER) - Development Mailing List; sr-users(a)lists.sip-router.org *Cc:* Engineering *Subject:* Re: [sr-dev] new module db_kazoo Hello, thanks for this contribution! Do you have a link to the module source code or can you send it attached? We need to review a bit and check if everything is in place (e.g., license, documentation). For a better clarification, do the json payloads flowing via AMQP have a structure specific for kazoo? I mean the object structure, how are the fields name set, from the name of the columns? Is there a wrapper to specify the command (e.g., insert, delete, select)? Or maybe you can provide an example of such object... Kazoo is an open source application, therefore the new module has no barrier in getting inside kamailio repository. My questions were related more to see if worth considering a new name. To get it in our git repository, we expect that you or someone else from 2600hz is willing to maintain it for at least one year. You will get write access over ssh to git repository to be able to push the new module and commit to it in the future. I will write a separate email directly to you with the required details for access. Cheers, Daniel On 09/09/14 12:22, Luis Azedo wrote: -- Daniel-Constantin Mierla http://twitter.com/#!/miconda - http://www.linkedin.com/in/miconda Next Kamailio Advanced Trainings 2014 - http://www.asipto.com Sep 22-25, Berlin, Germany