Skip to main content
The First Step
June 15, 2026
Question

Call forwarding not opening call-pop

  • June 15, 2026
  • 5 replies
  • 123 views

When our admins transfer a call, it does not trigger the call-pop. From digging through our logs, it appears that what is happening is that the transferred call comes in with the extension data, instead of the initial caller data. Is this an issue with my implementation, or a legitimate bug?

    5 replies

    Embbnux
    Employee
    Employee
    June 16, 2026

    Hi ​@tliu Can you share some screenshots about the transferring. And I would like to check which transfer type that you are using, Direct/Blind transfer or Warm/AskFirst transfer?

    tliuThe First StepAuthor
    The First Step
    June 16, 2026

    We are using both types of transfer. What kind of screenshots would be helpful, currently nothing pops at all.

    Embbnux
    Employee
    Employee
    June 16, 2026

    Hi ​@tliu The call screenshots for the callee who received the forwarding calls. And it is appreciated if you can share your app version.

    For direct transfer, it should provide calls with initial caller data. But for ask-first transfer, it is by design to show the extension data as the call connect the extension firstly. Then initial caller info will be changed after transfer completed, but the data is not triggered in new call event to cause the issue.  We need to check how to improve it.

    tliuThe First StepAuthor
    The First Step
    June 22, 2026

    I will provide screenshots tomorrow. Ask-first transfer is the primary version we use. Are there any suggested workarounds we could use?

    Embbnux
    Employee
    Employee
    June 22, 2026

    For ask-first transfer’s pop,it requires some implement in App Connect side to support it. I will share this to team for discussion.