Solved Transfer to intercom (*9) fails in v15

Discussion in 'CRM / Helpdesk / App Integration' started by R. Henriksen, Dec 19, 2016.

Thread Status:
Not open for further replies.
  1. R. Henriksen

    Joined:
    Dec 19, 2016
    Messages:
    3
    Likes Received:
    1
    Hi

    We use intercom as a work around to have transferred calls connected instead of alerting/ringing at the transferredToDevice.

    E.g. when we do a retrieve from hold, we use TransferCall(SP0, callID, *9102) to get the call in a connected state at device 102.

    The benefit is that the call does not ring at device 102 and the user does not have to answer the call after retrieve from hold.

    This work around is available in v14, but after upgrading to v15 SP4 it fails. The call does not get connected, but instead is alerting at the transferredToDevice.

    I sit possible to get this feature back in v15?

    Best regards
     
  2. 3cxnub

    Joined:
    Nov 1, 2014
    Messages:
    5
    Likes Received:
    1
    can you intercom to an internal extension, *9102 and then successfully transfer that call to an external number?
     
  3. R. Henriksen

    Joined:
    Dec 19, 2016
    Messages:
    3
    Likes Received:
    1
    Found the problem, my bad.

    The extensions somehow lost the “Can intercom” user right after upgrading.

    After adding the “Can intercom” right to the extension it works perfectly.
     
Thread Status:
Not open for further replies.