CUPC caller ID on calls from Unity Connection

[kylebrogers]

This is an environment that runs the latest 8.6x versions of CUCM/CUC/Presence

When a call comes into a Call Handler in Unity Connection and the caller dials an extension, the call is directed to the extension and the caller ID correctly shows the originating caller's caller ID.  That all works as desired.

However, there are hundreds of users on the system who have only softphones (CUPC).  When the call comes to the soft phone via a call handler, it instead shows the extension of the port Unity Connection used to connect the call.  I'm assuming this has to do with SIP, though I could be wrong.  Does anyone know a fix for this?

[Sajeel145 · Accepted solution]

Hello Kylebrogers,

In CUCM service parameter (call manager )

---> Display Original calling number on transfer from cisco unity (True)

Sajeel

[kylebrogers]

Sajeel, this is already set where it needs to be because the originating caller's name and number comes through as expected on my SCCP phones. 

On a side note, after testing I've realized that when the call arrives at my CUPC client, it actually shows the caller's name and number.  The problem is with the missed call log.  While the incoming alerting name is correct, the Missed Call log (only on CUPC) lists the extension of the Unity Connection port that handled the call. 

[kylebrogers]

Bump.

Anyone know why this would affect only the Missed Calls log on CUPC?  Inbound alerting shows the originating caller's Caller ID, but the CUPC Missed Call Log shows the Unity Connection CTI Port's Info.  We don't have this issue on physical phones. 

[kylebrogers]

Sajeel, my apologies.  I thought that since the initial caller ID was showing up correctly and it was only the Missed Calls taht were affected that it wouldn't be related to that Service Parameter.  Just for grins, I changed it and sure enough that fixed it.  Any idea why it affects missed calls but not the inbound call alerting? (if not, not big deal.  Just personal curiosity)

[Ayodeji Okanlawon]

Kyle,

I believe this is working as expected. Think of it this way. When phone a calls b and b transfers to c, before the call is connected, phone c will call coming from b, at this point if the call is missed them you will see missed call from b. However when the call is answered, the CLI is updated to be from phone A.

You can simulate a call transfer with IP phones to confirm this






Sent from Cisco Technical Support Android App