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

Yealink phones recall after blind transfer when using PJSIP

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Minor
    • Resolution: Out of Date
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Endpoint (Commercial)
    • Labels:
      None
    • Asterisk Version:
      13
    • Distro Version:
      13.0.191.11
    • Distro:
      FreePBX Distro

      Description

      When using PJSIP for extensions with Yealink phones, a blind transfer (say from pressing a BLF)  that goes to voicemail will cause a false recall to ring at the person that did the transfer.

      http://forum.yealink.com/forum/showthread.php?tid=40843

      https://ticket.yealink.com/index.php/bug/46000

      This is not a new issue as can be seen with these posts. People hacked around the issue by killing the packet at the firewall.

      https://community.asterisk.org/t/transfer-recalls-via-refer-notify-events/69764

      https://community.freepbx.org/t/transfered-calls-from-the-operator-are-being-transfered-back-ghost-call/36205

      https://community.freepbx.org/t/blind-transfers-on-yealink-38g-return-completed-calls-with-transfer-failed/40228

      I worked with Yealink support and was instructed to set this in my configuration file.

      ```

      transfer.hang_up_after_success_trans = 3

      ```

       

        Gliffy Diagrams

          Attachments

            Issue Links

              Activity

                People

                • Assignee:
                  Unassigned
                  Reporter:
                  sorvani Jared Busch
                • Votes:
                  1 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.