Calling party number cannot be passed to the PSTN or PBX or it is incorrectly received by the destination user

[TCC_2]

Core Issue

The caller ID can be sent on these port types:

• E1 Channel Associated Signaling (CAS) R2
• Foreign Exchange Station (FXS)
• ISDN

Note: Analog recEive and transMit (E&M) ports do not support caller ID. Foreign Exchange Office (FXO) and T1 CAS Feature Group-D (FGD) do not support sending to the PBX and Public Switched Telephone Network (PSTN).

Resolution

To resolve this issue, ensure that you are using hardware that supports caller ID in the configuration you are attempting. For more background information into caller ID and the situations in which it is passed, refer to Appendix B - Caller ID.

• For skinny and Media Gateway Control Protocol (MGCP) gateways, perform these steps:
  1. Follow the instructions for gathering traces as described in Setting up Cisco CallManager Traces for Cisco Technical Support. Search for the CallingParty= string.
  2. If this field is empty, contact your Telco or PBX vendor.
• For H.323 gateways, perform these steps:
  1. If the trunk is ISDN, issue the debug    isdn q931 command to verify that the calling number is present in the Q.931 SETUP received from the PBX or PSTN.
  2. If the calling party number is not present in the received SETUP, contact your Telco or PBX vendor. If the calling party number is present, further debugging is required to uncover why it is not presented to the phone.
  3. Follow the instructions for gathering traces as described in the Setting Up Cisco CallManager Traces for Cisco Technical Support document. Search for the CallingParty= string. It should contain the calling party number.
  4. If the trunk is not ISDN, refer to Caller ID Name Delivery Issues on Cisco IOS Gateways to gather clues as described in the Verify End-to-End VoIP Signaling (VOIP Call-Leg) section of Troubleshooting and Debugging VoIP Call Basics.