Click to call not working

[Raj Saini]

Hi,

I am having issue with click to call not working. I have tested it with master, 3.0 and 3.01 and they have the same issue. This is working fine in the v.2..14. If you look at the FS logs below, request for dialplan XML was timed out after three seconds.

2013-09-19 16:54:32.381175 [INFO] mod_dialplan_xml.c:557 Processing Rajbir Saini <1002>->1001 in context context_2
2013-09-19 16:54:32.381175 [DEBUG] switch_core_state_machine.c:489 (loopback/1001-a) State CONSUME_MEDIA
2013-09-19 16:54:32.381175 [DEBUG] mod_loopback.c:662 CHANNEL CONSUME_MEDIA
2013-09-19 16:54:32.381175 [DEBUG] switch_core_state_machine.c:489 (loopback/1001-a) State CONSUME_MEDIA going to sleep
2013-09-19 16:54:32.381175 [DEBUG] kazoo_fetch_agent.c:215 Sending dialplan XML request (34fe0aea-2c0e-47ec-9844-a4f513044984) to ecal...@raj.viithiisys.com <2.1188.0>
2013-09-19 16:54:32.821246 [DEBUG] kazoo_event_stream.c:201 Erlang event stream 0x7f61d40b74a0 client 127.0.0.1:45044
2013-09-19 16:54:35.481244 [NOTICE] kazoo_fetch_agent.c:285 Request for dialplan XML (34fe0aea-2c0e-47ec-9844-a4f513044984) timed-out after 3100ms
2013-09-19 16:54:35.481244 [WARNING] mod_dialplan_xml.c:587 Context context_2 not found
2013-09-19 16:54:35.481244 [INFO] switch_core_state_machine.c:192 No Route, Aborting
2013-09-19 16:54:35.481244 [NOTICE] switch_core_state_machine.c:193 Hangup loopback/1001-b [CS_ROUTING] [NO_ROUTE_DESTINATION]

Kazoo logs shows below that originate request sent to FreeSWITCH and dial plan request was processed after three seconds. It looks to due to this FS hangs up the call. Complete FreeSWITCH here http://pastebin.com/PuWpsz8A and Kazoo logs are here .

Sep 19 16:54:32 raj 2600hz[23957]: |77784831-628b-4463-b343-ddb80a3b204e|ecallmgr_util:412 (<0.5359.0>) building bridge endpoint: [<<"route">>,undefined,undefined,<<"1001">>,<<"loopback/1001/context_2">>]
Sep 19 16:54:32 raj 2600hz[23957]: |77784831-628b-4463-b343-ddb80a3b204e|ecallmgr_originate:519 (<0.5359.0>) executing on frees...@raj.viithiisys.com: {origination_callee_id_number='1001',origination_callee_id_name='1001',origination_caller_id_number='1002',origination_caller_id_name='Rajbir Saini',continue_on_fail='true',ecallmgr_Fetch-ID='dbaffb9e2bda5b62c547ef31f5ecbd37',ecallmgr_Inception='on-net',ecallmgr_Authorizing-Type='device',inherit_codec='false',ecallmgr_Authorizing-ID='cb3e205a1459dbfb4ff836cf309ede12',ecallmgr_Retain-CID='true',sip_auto_answer='true',ecallmgr_Account-ID='cd4207b11f69817cb1abade9addf1e7a',loopback_bowout_on_execute='true',local_var_clobber='true'}[origination_uuid=77784831-628b-4463-b343-ddb80a3b204e]loopback/1001/context_2 'm:^:unset:origination_callee_id_number^unset:origination_callee_id_name^unset:origination_caller_id_number^unset:origination_caller_id_name^unset:continue_on_fail^unset:ecallmgr_Inception^unset:inherit_codec^unset:sip_auto_answer^unset:sip_h_Call-Info^unset:sip_h_Alert-Info^unset:alert_info^unset:sip_invite_params^set:sip_auto_answer=false^transfer:1002 XML context_2' inline
Sep 19 16:54:32 raj 2600hz[23957]: |ecallmgr_call_events|gen_listener:286 (<0.5366.0>) starting new gen_listener proc

============================== dialplan response ========================================

Sep 19 16:54:35 raj 2600hz[23957]: |d8fb30d3-18bf-480c-96ca-63c303b342d2|ecallmgr_fs_route:221 (<0.5392.0>) received affirmative route response for request 34fe0aea-2c0e-47ec-9844-a4f513044984
Sep 19 16:54:35 raj 2600hz[23957]: |d8fb30d3-18bf-480c-96ca-63c303b342d2|ecallmgr_fs_route:224 (<0.5392.0>) sending XML to frees...@raj.viithiisys.com: <document type="freeswitch/xml"><section name="dialplan" description="Route Park Response"><context name="context_2"><extension name="park"><condition><action application="log" data="NOTICE log|${uuid}|ecal...@raj.viithiisys.com won call control"/><action application="export" data="ecallmgr_Ecallmgr-Node=ecal...@raj.viithiisys.com"/><condition field="variable_ecallmgr_Bridge-ID" expression="^$"><action application="export" data="ecallmgr_Bridge-ID=${UUID}"/></condition><action application="set" data="ringback=%(2000,4000,440,480)"/><action application="set" data="transfer_ringback=%(2000,4000,440,480)"/><action application="park"/></condition></extension></context></section></document>
Sep 19 16:54:35 raj 2600hz[23957]: |d8fb30d3-18bf-480c-96ca-63c303b342d2|ecallmgr_fs_route:240 (<0.5392.0>) node frees...@raj.viithiisys.com rejected our route response: baduuid
Sep 19 16:54:35 raj 2600hz[24021]: |00000000000|wh_amqp_channel:150 (<0.277.0>) published to configuration(amqp://guest:gu...@127.0.0.1:5672) exchange (routing key doc_created.account%2Fcd%2F42%2F07b11f69817cb1abade9addf1e7a-201309.cdr.201309-f4f80ecdd7397adca0d9185326cfd6bc) via <0.259.0>


If someone can confirm that it is a bug, I will create a JIRA issue.

Thanks,

Raj

[Raj Saini]

Sorry, I forgot to paste the Kazoo logs. Complete Kazoo logs are here http://pastebin.com/PmRees11

[James Aimonetti]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi Raj,

It certainly looks like a bug. I'm not the most familiar with
FreeSWITCH's mod_loopback, so I'll defer to Darren or Karl to chime
in, but it looks like you've spotted a valid bug.

Thanks for the report; if you can file the ticket in JIRA and update
this thread with the URL, that would be fantastic.

James

- --
James Aimonetti
Lead Systems Architect
"I thought I fixed that"

2600Hz | http://2600hz.com
sip:ja...@2600hz.com
tel:415.886.7905
irc:mc_ @ freenode
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iF4EAREIAAYFAlI7C08ACgkQ54NxaUq7OmAWGwD/UwyZEeLieVPtop4WvjHVjLoF
c/IJ0slMpfCdMinYM3EA/0QLql1f/CEawJg3LhIfyWqODy/6QaKgq6kR4w8lQ5uW
=Nk7k
-----END PGP SIGNATURE-----

[Raj Saini]

Hi James,

I have created https://2600hz.atlassian.net/browse/KAZOO-1404. I will be
glad to help on this if someone one point me to the right direction.

Thanks,

Raj

[Mountain King]

Hi all,

    had this issue was solved? I  encounter this issue witn master 3.21 too.





在 2013年9月19日星期四 UTC+8下午8:20:51，Raj Saini写道：

[Darren Schreiber]

Click to Call has no known bugs in regards to being completely broken right now on v3.22

--
You received this message because you are subscribed to the Google Groups "2600hz-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Mountain King]

I  drawn a conclusion that freeswitch will reproduct 'no route destinaton' bug when clicktocall request bigger than 4 per second by integration testing, and when clicktocall about 1000 requests at 4cps，freeswitch will product about  60 'no route destination' bug.

在 2016年6月30日星期四 UTC+8下午11:33:55，Darren Schreiber写道：

[emnvn]

Dear all,

I still see this bugs on kazoo-3.22-59. Error rate is about 10%, the result that when callee accept the call, then the call will be hangup after 4 seconds. Hangup cause is "NO_ROUTE_DESTINATION"

I don't know what is the root cause.

Thanks.
-------------------------------------
[Kazoo logs]
Dec 16 23:52:57 kazoo-node1 2600hz[6224]: |frees...@kazoo-node1.zentech.io|ecallmgr_fs_route:159 (<0.1149.0>) processing dialplan fetch request c51c186a-c3ea-11e6-a978-e3fdcd64c1ff (call 2631239553-369...@IRISMSC2.iristel.net) from frees...@kazoo-node1.zentech.io
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-369...@IRISMSC2.iristel.net|ts_route_req:24 (<0.21121.1916>) received request c51c186a-c3ea-11e6-a978-e3fdcd64c1ff asking if trunkstore can route this call
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-369...@IRISMSC2.iristel.net|ts_route_req:24 (<0.21132.1916>) received request c51c186a-c3ea-11e6-a978-e3fdcd64c1ff asking if trunkstore can route this call
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-369...@IRISMSC2.iristel.net|ts_route_req:31 (<0.21132.1916>) call with fetch-id c51c186a-c3ea-11e6-a978-e3fdcd64c1ff began from outside the network
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-369...@IRISMSC2.iristel.net|cf_route_req:38 (<0.21131.1916>) received request c51c186a-c3ea-11e6-a978-e3fdcd64c1ff asking if callflows can route this call
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-369...@IRISMSC2.iristel.net|cf_util:636 (<0.21131.1916>) searching for callflow in account%2Ff3%2F1e%2F525c9a3ec439091b2bd0003b9970 to satisfy '+16475599862'
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-369...@IRISMSC2.iristel.net|cf_route_req:95 (<0.21131.1916>) callflow 3b077a04bed5e8edba477d5d7aadd643 in f31e525c9a3ec439091b2bd0003b9970 satisfies request
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-369...@IRISMSC2.iristel.net|cf_route_req:206 (<0.21131.1916>) callflows knows how to route the call! sending park response
Dec 16 23:53:00 kazoo-node1 2600hz[6432]: |2631239553-369...@IRISMSC2.iristel.net|cf_route_req:232 (<0.21131.1916>) callflow didn't received a route win, exiting : timeout
[FS logs]
2016-12-16 23:53:00.893816 [NOTICE] kazoo_fetch_agent.c:286 Request for dialplan XML (c51c186a-c3ea-11e6-a978-e3fdcd64c1ff) timed-out after 3100ms
2631239553-369...@IRISMSC2.iristel.net 2016-12-16 23:53:00.893816 [WARNING] mod_dialplan_xml.c:665 Context context_2 not found

[Luis Azedo]

HI,

you should check your ecallmgr logs for the same call-id

On Wed, Dec 21, 2016 at 6:11 PM, emnvn <ngh...@gmail.com> wrote:

Dear all,

I still see this bugs on kazoo-3.22-59. Error rate is about 10%, the result that when callee accept  the call, then the call will be hangup after 4 seconds. Hangup cause is "NO_ROUTE_DESTINATION"

I don't know what is the root cause.

Thanks.
-------------------------------------
[Kazoo logs]

Dec 16 23:52:57 kazoo-node1 2600hz[6224]: |freeswitch@kazoo-node1.zentech.io|ecallmgr_fs_route:159 (<0.1149.0>) processing dialplan fetch request c51c186a-c3ea-11e6-a978-e3fdcd64c1ff (call 2631239553-3690921165-403475@IRISMSC2.iristel.net) from freeswitch@kazoo-node1.zentech.io
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-3690921165-403475@IRISMSC2.iristel.net|ts_route_req:24 (<0.21121.1916>) received request c51c186a-c3ea-11e6-a978-e3fdcd64c1ff asking if trunkstore can route this call
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-3690921165-403475@IRISMSC2.iristel.net|ts_route_req:24 (<0.21132.1916>) received request c51c186a-c3ea-11e6-a978-e3fdcd64c1ff asking if trunkstore can route this call
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-3690921165-403475@IRISMSC2.iristel.net|ts_route_req:31 (<0.21132.1916>) call with fetch-id c51c186a-c3ea-11e6-a978-e3fdcd64c1ff began from outside the network
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-3690921165-403475@IRISMSC2.iristel.net|cf_route_req:38 (<0.21131.1916>) received request c51c186a-c3ea-11e6-a978-e3fdcd64c1ff asking if callflows can route this call
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-3690921165-403475@IRISMSC2.iristel.net|cf_util:636 (<0.21131.1916>) searching for callflow in account%2Ff3%2F1e%2F525c9a3ec439091b2bd0003b9970 to satisfy '+16475599862'
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-3690921165-403475@IRISMSC2.iristel.net|cf_route_req:95 (<0.21131.1916>) callflow 3b077a04bed5e8edba477d5d7aadd643 in f31e525c9a3ec439091b2bd0003b9970 satisfies request
Dec 16 23:52:57 kazoo-node1 2600hz[6432]: |2631239553-3690921165-403475@IRISMSC2.iristel.net|cf_route_req:206 (<0.21131.1916>) callflows knows how to route the call! sending park response
Dec 16 23:53:00 kazoo-node1 2600hz[6432]: |2631239553-3690921165-403475@IRISMSC2.iristel.net|cf_route_req:232 (<0.21131.1916>) callflow didn't received a route win, exiting : timeout

[FS logs]
2016-12-16 23:53:00.893816 [NOTICE] kazoo_fetch_agent.c:286 Request for dialplan XML (c51c186a-c3ea-11e6-a978-e3fdcd64c1ff) timed-out after 3100ms

2631239553-3690921165-403475@IRISMSC2.iristel.net 2016-12-16 23:53:00.893816 [WARNING] mod_dialplan_xml.c:665 Context context_2 not found

--
You received this message because you are subscribed to the Google Groups "2600hz-dev" group.

To unsubscribe from this group and stop receiving emails from it, send an email to 2600hz-dev+unsubscribe@googlegroups.com.