when a call is forwarded to a off net PSTN number from a Cisco IP Phone. The caller ID shown on the called party's phone shows a DN that hasn't been allocated (this can be different DN and not always the same one) on our callmanager system.
How can I rectify this so it shows the correct caller ID?
We are using CUCM 5.1 and our voice gateway is Cisco 3660 IOS Ver 12.2(6A)
The problem is this. A user places a CFW from their IP Phone to the PSTN.
An incoming call from the PSTN is then CFW via IP Phone to PSTN (users off net handset)The caller ID dispalyed on the users handset will sometimes show the call is coming from our corporate main Circuit ID and other times it will show number coming from our Corporate Circuit but the last three digits are unknow and not part of our Corporate circuit ID.
Eg Corporate Circuit Main ID may be 0812340777 some calls will display this caller ID on the users handset if a call is fowarded from say a cell phone number say 0444999123 the caller ID on the users handset will be shown as 0812340123. it grabs the last 3 digit of the cell phone number. we want the caller ID to show the actual ID of the forwarded call. BTW if you make a call from IP phone to the PSTN caller ID's shown on called party's handset are correct the problem only occurs when calls are PSTN - CFW IP phone - PSTN.
I have noticed under Callmanager configuration Gateway - Call routing information - Outbound calls - Caller ID DN we have for example 0812340XXX in place. I remember when we first had callmanager installed this spot was left blank. I have tried to remove 0812340XXX but when I save it still appears. Do you think this is causing the problem?
SIP traces provide key information in troubleshooting SIP Trunks, SIP
endpoints and other SIP related issues. Even though these traces are in
clear text, these texts can be gibberish unless you understand fully
what they mean. This document attempts to br...
Please find the attached HTML document, download and open it on your PC.
This provides an easy to use form where you simply answer a few
questions and it will render the proper jabber-config.xml file for you
to copy/paste. There is built in logic to verif...
CUCM Database Replication is an area in which Cisco customers and
partners have asked for more in-depth training in being able to properly
assess a replication problem and potentially resolve an issue without
involving TAC. This document discusses the bas...