01-13-2015 03:46 AM - edited 03-17-2019 01:33 AM
Hi,
Have this problem, we are putting prefix 0 on all incomming calls (Calling Party) so users are able to callback directly from the directory on the phone (Recieved Calls etc..) This has been done on a translation pattern that translates all incomming calls. This works fine when calling directly to IP phones. But if we make a call to the CCX and a agent is answering the call they are able to see the prefix in tha CAD agent but not on the phone´s display. Does anybody have an idea why the prefix is missing when the call is from the CCX.?
CCX version 9 and CUCM version 9.1
/David
Solved! Go to Solution.
01-14-2015 12:18 PM
Interesting. The CTI redirect must be causing the call to revert to the Original Calling Party Information. I'm unaware of this behavior but can't proclaim it a defect since I lack documentation to support a definitive answer.
So, how to deal with it? Using the service parameter (or the H.323 gateway-level parameter if applicable) is one option. Another would be to prefix it on the gateway using a translation-rule and -profile before ever sending the call to CUCM.
01-13-2015 09:21 AM
Are you seeing the value without the translated Calling Party Information while the agent phone is Alerting/Ringing or after the call is Connected?
If the former, you won't see the original caller ID here but the CCX CTI Port instead. This is is not avoidable until CCX 10.0 where there is an XML webpage overlay that can be pushed to the phone.
01-14-2015 12:47 AM
Hi Jonathan,
It is after the call is connected that the prefix is missing, alerting / ringing i see the CTI port number.
But i did not know that there was a solution for that as well thanks for info.
I can not find out why the prefix is missing when the call is comming from the CCX, maybe i should do the prefix as a service parameter instead "Incoming Calling Party National Number Prefix - Phone"
01-14-2015 12:18 PM
Interesting. The CTI redirect must be causing the call to revert to the Original Calling Party Information. I'm unaware of this behavior but can't proclaim it a defect since I lack documentation to support a definitive answer.
So, how to deal with it? Using the service parameter (or the H.323 gateway-level parameter if applicable) is one option. Another would be to prefix it on the gateway using a translation-rule and -profile before ever sending the call to CUCM.
04-07-2015 03:03 AM
Thanks. I did a translation rule in the CUBE and that solved it for me.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide