Solved Transfer to intercom (*9) fails in v15

Status
Not open for further replies.

R. Henriksen

Forum User
Joined
Dec 19, 2016
Messages
3
Reaction score
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
 
can you intercom to an internal extension, *9102 and then successfully transfer that call to an external number?
 
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.
 
Status
Not open for further replies.

Forum statistics

Threads
112,322
Messages
591,889
Members
165,470
Latest member
Robert Lee