What is the purpose of the "Device Name" in a UCCX Trigger

[kbeaton]

What is the purpose of the "Device Name" in a UCCX Trigger?
Does it have to match with something else in the system?
Does it show anywhere else?

[Jonathan Schulenberg]

It's the CTI Route Point device name in CUCM. Same thing for the Call Control Group in CCX; it's the CTI Port device name.

[Maren Mahoney]

To add to what @Jonathan Schulenberg said, yes the Device Name for the CTI Route Point in CUCM needs to match the Device Name in UCCX.

Maren

[M02@rt37]

Hello @kbeaton 

The "Device Name" in a UCCX Trigger identifies the associated CTI Route Point in CUCM, ensuring calls to its DN are routed to the UCCX application.

It must match the CTI Route Point's Device Name configured in CUCM to establish proper communication between CUCM and UCCX. This name does not appear in user-facing systems but is essential for routing and application control within the UCCX environment.

[kbeaton]

Can two different triggers on the same Application have the same "Device Name"
I suspect not, but wanted to check

[Jonathan Schulenberg · Accepted solution]

No. CUCM requires uniqueness in device names. The most common format is either CCX<number> or CTIRP<number> for the Trigger and CTIP<number> for the Call Control Group. For example, CCX14045550100 if the number is +14045550100. This is roughly equivalent to SEP<MAC address> of physical phones or CSF<username> of Jabber/Webex App.

[kbeaton]

I have another question, but I'll start a new thread

[Jonathan Schulenberg · Accepted solution]

Alerting Name is shown to the calling party while a call is ringing - before it connects. That's relevant to an inbound Trigger until the Accept step in the AEF script executes, for example.

Display Name (a.k.a., the connected party information) and EPNM are use case dependent. CUCM can select original calling, initial redirecting, and last redirecting party information when choosing what to display/transmit; the Trigger counts as a redirecting party (unless redirector history is lost by the call hitting a Translation Pattern). As a hypothetical example, let's say you set the Trigger's Display & EPNM to what customers think they called (e.g. Cisco TAC +18005532447). The AEF script subsequently performs a Call Redirect  - or maybe the agent manually transfers - the call elsewhere. You'd probably want the transfer target to see either the original calling party or the first redirecting party of the Trigger, not the last redirecting party of the Call Control Group (CTI Port) or the agent DN.

[kbeaton]

Ah, that help! Thanks for all your help!