CUCM 7.1.5 - IP Phone 7962, If call is being forwarded to a mobile number, the history of the calls is not seen in the IP phone and on the mobile phone only the PSTN number of the IP Phone is seen, so if there is a missed call in the mobile, we are not able to check who has made the call becuse only IP phone PSTN number is displayed as missed call and who actually called is not know, how do we find that or what options are do we have to enable on the IP Phone and CUCM to get to call forwarded history on the IP phone.
Call histories (received/placed/missed) are currently stored on the observed target. You are not seeing the call history on the IP Phone because the call never alerted on it due to call forwarding. The same occurs if you unplug a phone and make calls to the DN. When you plug that phone back in missed calls will not appear from a device that was unregistered at the time of the call start. This is an architectural issue with UCM. Workaround: You can use Mobile Connect instead of call forwarding. If you use Mobile Connect, the call will ring both destinations simultaneously.
The PSTN circuit is likely filtering the values you are allowed to send for ANI on an outbound call. If you have a PRI this can be observed using 'debug isdn q931'. All you can do is confirm that you are sending the correct information (Mobile Connect will do this for you by default). There is nothing you can do if the carrier is overwriting the information you send, except complain to them. The rules vary by carrier and region. In the US most CLECs will allow you to send anything you want while most ILECs will not.
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...