Jump to content

Tran Thi My Hue

Members
  • Posts

    2
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Dear mc_ and lazedo, I will upgrade my kazoo to 3.22 and freeswitch version then re-test again. Thanks for your suggestion. The following are my logs for the call I faced the issue. kazoo_log1 kazoo_log2
  2. Dear all, My kazoo release version: v3.21.34 , and I faced the following issues: Step 1 : set up callflow 19006612: + First set up play media about 12s + Second go to recording start + Then go to ACDC Queue Step 2 : Dial 19006612 and hangup call within 3s - 5s. Reproduce step 1 and steps 2 many times. Actually Result : Sometimes the callflow succeed stop and do not go to cf_record_call . Sometimes the callflow can not stop and continue go to cf_record_call, cf_acdc_member like an alive call. I traced the log both freewitch and kazoo, then I saw there are two reasons which make the callflow 19006612 still continue even call hangup: Reason 1 : Sometimes Ecallmgr do not received channel_destroy from Freeswitch although Freeswitch already has CS_DESTROY for the call. Reason 2: Sometimes Ecallmgr receives channel_destroy as well from Freeswitch for the call, but callflow cf_play do not get channel_destroy of the call. Kazoo and Rabbitmq are on the same server. Freeswitch is other server. Node of Kazoo/Rabbitmq and node of Freeswitch are in internal network. For these issue, any body can help me in this direction. Thanks.
×
×
  • Create New...