Kazoo 4.3 Konami Listener is not working as expected.

[Vijay]

Hi,

Trying to execute konami metaflow.

Can see in logs that the metaflow is getting posted on a exchange metaflow with routing key metaflow.action.*.

But konami_listener is not able to get the message and process it in handle_metaflow.

Is my understanding right that konami_listener is the starting point for the metaflow to receive and starting processing further and finally post on the queue to ecallmgr.

Please find the kazoo log statements where we can see that message is posted on metaflow exchange

published to metaflow(direct 235B) exchange (routing key metaflow.action.2832-0-1661430168%40172%2E31%2E1%2E138.break) via <0.3746.0>
Nov  7 05:52:39 sandbox 2600hz[20724]: |2832-0-1661430168@172.31.1.138|kz_amqp_worker:737(<0.3429.0>) published message e5365fe8c32e0357 for <0.32072.13>
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|crossbar_bindings:90(<0.32072.13>) folding v2_resource.billing
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|api_util:1098(<0.32072.13>) billing returned accepted
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|api_resource:689(<0.32072.13>) requested resource update validated
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|api_resource:546(<0.32072.13>) run: content_types_accepted
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|crossbar_bindings:90(<0.32072.13>) folding v2_resource.content_types_accepted.channels
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|api_resource:560(<0.32072.13>) checking content type '{<<"application">>,<<"json">>,[]}' against accepted
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|api_resource:608(<0.32072.13>) no content-types accepted, using defaults
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|api_resource:617(<0.32072.13>) cta: [{{<<"application">>,<<"json">>,[]},from_json}]
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|api_resource:776(<0.32072.13>) run: from_json
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|crossbar_bindings:90(<0.32072.13>) folding v2_resource.execute.post.channels
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|api_resource:804(<0.32072.13>) content-type provided is to_json
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|api_util:1707(<0.32072.13>) adding resp header content-type: <<"application/json">>
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|api_resource:255(<0.32072.13>) session finished: normal
Nov  7 05:52:39 sandbox 2600hz[20724]: |9492452f29889f52cd078249cfaebc47|api_resource:268(<0.32072.13>) POST request fulfilled in 20 ms 171K232B mem 5K821B bin

It says post request fulfilled after sometime the initial call is getting over and the metaflow is never invoked by konami.

 

Please let us know If our understanding is correct and what could be the Issue.

Regards,

Vijay

 

 

[Vijay]

Hi mc_,

We have tried posting the metaflow through put request on the channel api.  We made changes in the code konami_listener and kapi_metaflow from 'bind' to 'flow'.

 We could see that metaflow is publised on the queue metaflow.flow.* and reached handle_metaflow method in konami_listener.

But after that we are getting the below error with exit 012. 

Please let us know what is that we are missing. Do we need to make changes for the put to work?

ov 24 10:44:18 sandbox 2600hz[15324]: |4087-0-3147525598@172.31.1.138|kz_amqp_channel:245(<0.3524.0>) published to metaflow(direct 243B) exchange (routing key metaflow.flow.4087-0-3147525598%40172%2E31%2E1%2E138) via <0.4043.0>
Nov 24 10:44:18 sandbox 2600hz[15324]: |4087-0-3147525598@172.31.1.138|kz_amqp_worker:737(<0.3524.0>) published message be95dcdf643ccd2b for <0.27278.0>
Nov 24 10:44:18 sandbox 2600hz[15324]: |8e10344268f8a0e0dca440139f13467d|api_resource:804(<0.27278.0>) content-type provided is to_json
Nov 24 10:44:18 sandbox 2600hz[15324]: |8e10344268f8a0e0dca440139f13467d|api_util:1707(<0.27278.0>) adding resp header content-type: <<"application/json">>
Nov 24 10:44:18 sandbox 2600hz[15324]: |8e10344268f8a0e0dca440139f13467d|api_resource:255(<0.27278.0>) session finished: normal
Nov 24 10:44:18 sandbox 2600hz[15324]: |8e10344268f8a0e0dca440139f13467d|api_resource:268(<0.27278.0>) PUT request fulfilled in 28 ms 403K96B mem 6K229B bin
Nov 24 10:44:18 sandbox 2600hz[15324]: |8e10344268f8a0e0dca440139f13467d|crossbar_bindings:78(<0.27288.0>) pmapping v2_resource.finish_request.PUT.channels
Nov 24 10:44:18 sandbox 2600hz[15324]: |4087-0-3147525598@172.31.1.138|konami_listener:68(<0.27290.0>) inside handle metaflow jobsj value is {[{<<"Call-ID">>,<<"4087-0-3147525598@172.31.1.138">>},{<<"Flow">>,{[{<<"module">>,<<"hangup">>},{<<"data">>,{[]}}]}},{<<"Node">>,<<"kazoo_apps@sandbox.test.com">>},{<<"Msg-ID">>,<<"be95dcdf643ccd2b">>},{<<"Event-Name">>,<<"flow">>},{<<"Event-Category">>,<<"metaflow">>},{<<"App-Version">>,<<"4.0.0">>},{<<"App-Name">>,<<"crossbar">>}]}
Nov 24 10:44:18 sandbox 2600hz[15324]: |0000000000|Undefined:Undefined(emulator) Error in process <0.27290.0> on node 'kazoo_apps@sandbox.test.com' with exit value:#012{function_clause,[{kz_json,get_json_value,[<<"Custom-Channel-Vars">>,undefined,{[]}],[{file,"src/kz_json.erl"},{line,771}]},{kapps_call,from_json,2,[{file,"src/kapps_call.erl"},{line,434}]},{konami_listener,handle_metaflow,2,[{file,"src/konami_listener.erl"},{line,70}]}]}
Nov 24 10:44:24 sandbox 2600hz[15599]: |kz_nodes|kz_amqp_channel:221(<0.4105.0>) published(3e6f2388e6ce397c42f4885f48b83351 1K) to nodes(amqp://guest:guest@127.0.0.1:5672) exchange (routing key ) via <0.4058.0>
Nov 24 10:44:25 sandbox 2600hz[15324]: |knm_port_request_crawler|knm_port_request_crawler:132(<0.27308.0>) port_request crawler completed a full crawl in 3ms.

 

 

Regards,

Vijay

[mc_]

Hi Vijay,

As seen here: https://docs.2600hz.com/dev/applications/crossbar/doc/channels/#put-a-feature-metaflow-on-a-channel

The PUT is not applicable for the open source konami application; it requires the currently closed-source konami-pro. So it is not unexpected that konami cannot handle the request properly.

[Vijay]

Hi mc_,

Thank you very much for the quick confirmation on PUT.

Now we are using POST to invoke the metaflow hangup.

Please let us know is it necessary to have a metaflows on accounts for POST metaflow to work.

Does 'konami_event_listener' bound to a metaflow.action routing when Initial call is from pivot?

 

Regards,
Vijay