Uploaded image for project: 'FreePBX'
  1. FreePBX
  2. FREEPBX-21126

ZULU outbound call changed to inbound in second webhook request

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Minor
    • Resolution: Commercial
    • Affects Version/s: None
    • Fix Version/s: None
    • Labels:
      None
    • Bug Tracker:
      Customer Issue
    • ToDo:
    • Asterisk Version:
      13.29.2
    • Distro Version:
      14.0.13.24
    • Distro:
      FreePBX Distro

      Description

      Hello,

      We use CRM for sending webhooks in both directions into our url with no problem. From 2020-01-27 we have problem with it.

      If we make call from Zulu (desktop and mobile too) client, first webhook have direction corect, but second webhook request change direction into inbound.

       

      Here is the 1st request:

      uuid=1580735603.71&direction=outbound&disposition=UNKNOWN&source=1087&destination=09xxxx&recordingfile=&duration=0&calldate=1580735604&timestamp=1580735604&clid=&cnam=&cnum=&type=START&voicemail=&owner=0

      And here is the update of call after hangup.

      uuid=1580735603.71&direction=inbound&source=1087&destination=&duration=0&disposition=MISSED&calldate=1580735603&timestamp=1580735603&contexts%5B0%5D=zulu-from-internal&contexts%5B1%5D=sub-record-check&contexts%5B2%5D=from-trunk-sip-out_vnet&contexts%5B3%5D=from-internal&clid=%22Viktor+Szoke%22+%3C0353700710%3E&cnum=1087&callend=1&type=END&voicemail=&owner=0

      If we do call detail request with GET /admin/api/sangomacrm/rest/calls/:uuid1, call have inbound direction either.

       

      Where is the problem?

      Thank you.

      Viktor

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                zemnet ZemNet
              • Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  NextupJiraPlusStatus

                  Error rendering 'slack.nextup.jira:nextup-jira-plus-status'. Please contact your Jira administrators.