Skip to main content
Brett1685885021
Amplifying the VIBE
Amplifying the VIBE
Jun 19, 2026 7:43 PM UTC

Product Improvement: RingCX Agent Script - Button Configuration Option For Transfers

RingCX > Admin > Agent Scripts > Button > Button Configuration > Actions > Button Action: Call Control / Call Action: Cold Transfer

We had an issue when attempting to use an agent script button to perform a cold transfer to a 10 digit RingEX phone number where the tag configuration of {{model.call.ani}} was not being respected. On the EX side, the transfer recipient would see our main RingEX phone number as opposed to the callers ANI.

After a support ticket was opened for months, a support agent finally stated that we needed to use {{model.call.aniE164}}. This tag does not exist within the pre-defined {{add a tag}} options.

The {{model.call.aniE164}} option needs to be added to the pre-defined {{add a tag}} options as I am sure there are plenty of RingCX customers who have the need to perform warm / cold transfers to the RingEX platform that wish to keep the callers ANI in tact upon transferring.

2 replies

New Participant
Jun 19, 2026 7:53 PM UTC

Hi Brett,

I’ve seen this behavior on some occassions. Have you tried using the {{model.call.dnis}} tag? RCx sometimes mixes the logic around between ANI and DNIS.

Brett1685885021
Amplifying the VIBE
Amplifying the VIBE
Jun 19, 2026 7:57 PM UTC

Hi Brett,

I’ve seen this behavior on some occassions. Have you tried using the {{model.call.dnis}} tag? RCx sometimes mixes the logic around between ANI and DNIS.

{{model.call.aniE164}} did end up working successfully. I did not attempt {{model.call.dnis}} as from my experience RCX always treats the ANI as the caller number / customer number (Even when it probably shouldn't)… 

 

In fact I believe I saw something recently where RingCX is changing their reporting to change the naming of “ANI” to “Customer Number”.