01-09-2012 10:55 AM - edited 03-16-2019 08:53 AM
Hello Guys, i am running cucm 8.5 and using the single number reach.when the SNR is used internally it works well.but when a call is placed from the PSTN or cellular provider number, i cannot see the actuall calling number on the cell phone that has been called and is part of a remote destination device profile.Is there a way to display this? i checked with my phone provider and callers ID's can be sent over the PSTN line, so this is not the issue.
thanks in advance.
Solved! Go to Solution.
01-09-2012 11:18 AM
This is a common problem and is usually the telco carrier's fault. CUCM will send the original caller's caller ID on the remote destination call leg. In many cases the carrier restricts the caller ID values you're allowed to send to only the DIDs that terminate on that circuit or trunk group. Sometimes the carrier will give you a way around this restriction if you set the Redirecting DNIS value. CUCM also does this automatically if you have RDNIS enabled (aka Diversion header in SIP).
Run a debug on your gatway and see what the SETUP message for the remote destination call leg looks like. It should show the original caller ID. If it does and your cell phone doesn't display that your carrier has overridden what you sent.
01-09-2012 01:09 PM
Im not sure by reading your post if you are having incoming or outgoing CLID issues. Incoming CLID issues could be a translation pattern on your CUBE or your incoming trunk configuration. Outgoing issues can be a few things one could be that your provider is rewriting the CLID or you are restricting "Calling Name Presentation" on your outgoing calls config for your SIP trunk.
01-09-2012 11:26 PM
Hi
As others have suggesed, you need to work with your service provider on this one. You say you have already verified the 'correct' CLI is going out, so if you are not seeing it on the target mobile phone then it's getting wiped somewhere.
Your SP may not be 'restricting' it, but will likely be validating it in some way. They may require a specific plan/type element, or a specific number format (including/omitting a national dial digit or something for example). See if you can get them to specific exactly what you need to send.
Aaron
01-09-2012 11:18 AM
This is a common problem and is usually the telco carrier's fault. CUCM will send the original caller's caller ID on the remote destination call leg. In many cases the carrier restricts the caller ID values you're allowed to send to only the DIDs that terminate on that circuit or trunk group. Sometimes the carrier will give you a way around this restriction if you set the Redirecting DNIS value. CUCM also does this automatically if you have RDNIS enabled (aka Diversion header in SIP).
Run a debug on your gatway and see what the SETUP message for the remote destination call leg looks like. It should show the original caller ID. If it does and your cell phone doesn't display that your carrier has overridden what you sent.
01-09-2012 11:40 AM
hello Jonathan, well, i checked with the provider who assured me that the caller details are not overriden. a debug on the GW show me the right call ID and remote device info for the called cell phone. any other ideas. i guess i need to find a setting for this on the cucm. thanks anyway
01-09-2012 01:09 PM
Im not sure by reading your post if you are having incoming or outgoing CLID issues. Incoming CLID issues could be a translation pattern on your CUBE or your incoming trunk configuration. Outgoing issues can be a few things one could be that your provider is rewriting the CLID or you are restricting "Calling Name Presentation" on your outgoing calls config for your SIP trunk.
01-09-2012 11:22 PM
Hi Nick, the issue is with outgoing calls. according to the provider, there is no restriction.
01-09-2012 11:26 PM
Hi
As others have suggesed, you need to work with your service provider on this one. You say you have already verified the 'correct' CLI is going out, so if you are not seeing it on the target mobile phone then it's getting wiped somewhere.
Your SP may not be 'restricting' it, but will likely be validating it in some way. They may require a specific plan/type element, or a specific number format (including/omitting a national dial digit or something for example). See if you can get them to specific exactly what you need to send.
Aaron
07-15-2013 08:02 PM
Hello
I am interest in how you resolved internal caller I'd for single number reach. I don't have an issue with External caller to SNR
Sent from Cisco Technical Support Android App
07-17-2013 02:59 AM
Hello,
It was more a ISP provider issue. the ISP was not displaying the Caller ID on outgoing calls.
You should request them to have it displayed for outgoing calls. not always an easy task.
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