I have noticed that when a call comes in to UCCX the ANI that shows up in CDATA is that of the Unity connection port instead of the outside caller id. I do have the service parameter in call manager that states "Display Original Calling Number on Tranfer from Cisco Unity" set to true. Is there another setting that I missed? The call flow is that the outside caller hits a system call handler in unity connection and then gets transfered to a UCCX queue.
I actually just tested this in the lab the other day. What version of CUCM are you running? In 7.x CUCM you would see the Unity port as the calling number if you had this service parameter enabled. In 8.x CUCM, it is the opposite. I set this parameter to false in the lab as I am running and 8.x CUCM and I then saw the original calling party number.
I am running CUCM and Unity Connection 8.6. I will give this a try and see what happens when setting this to false (which I believe is the default). I believe the reason that I set this to true was because of an issue I was having between unity connection and a SIP trunk not showing the external caller id but the unity connection port. I will test this and let you know the results. Thanks!
I just tested this is my environment and I did not see a change in the ANI in UCCX. It still shows the unity connection port for the ANI whether the setting is set to true or false. However it does affect the caller id that shows up in the SIP trunk to the third party IVR and it needs to be set to true for that to display the external caller id.
I am having a simialr issue when transferring calls from Unity connection to UCCX. The Finesse agents are seeing the original called number, but they are also seeing the voicemail port number which is confusing the CRM lookup utility.
I need to be able to mask the voicemail port and it sounds like you managed to do this.
Can you describe how you set this variable on the Get Call Contact info step on the CCX script?
You can use the Get Call Contact Info step in the script to capture various things such as Calling Number, Original Called Number etc and store the value in a variable (Type String). Once this had been done, simply follow the below post in order to show the same on Finesse Agent Desktop:
IntroductionCUCM Routing RulesDial String implementation PolicyCUCM Routing LogicSIP URI Call Routing Analysis+++ Case Study: 1 ++++++ Case Study: 2 +++Conclusion
Over the last few months, I have had the privilege of working on SI...
Are you getting this error “Installer User Interface Mode Not Supported. The installer cannot run in this UI mode. To specify the interface mode, use the -i command-line option, followed by the UI mode identifier. The value UI mode identifiers...