I have a CUCM 7 system setup with a centralized model. 2 Gateways using FXO on each gateway. The 2 sites are connected via IPSec VPN. When a call comes in from a number that has CallerID blocked, it manifests as "Unknown Number" on the IP Phone. Al phones are 7970G. Then after a brief period of time, the call is dropped. This happens to calls coming in on either gateway, either the local gateway to the CUCM or the remote gateway. The only calls that are dropped are those with the "Unknown Number" all other calls process fine. Is there something in the Service parameters that would affect this? Or a setting on the h.323 gateways? Any suggestions are appreciated.
Its the GW that initiates the call drop 15 secs after it connects by sending h225 RLC with cause41 (temp failure)
Sep 15 20:23:55.194: //1673/F481FAD38AE6/CCAPI/cc_api_call_disconnected:
Cause Value=41, Interface=0x66E0B7FC, Call Id=1673
Reason seems to be that h245 msgs TCS/MSD from GW are not responded by the CCM.
Strange that it happens only for calls with no CLID.
Can u share your GW config ?
Also CCM version and If the checkbox for "Wait for far end TCS" on CUCM H.323 GW config
page is checked or unchecked?
You can hardcode CLID info using following CLI which will be
used for calls when telco does not deliver a name/num:
station-id number 123456
station-id name From Outside
If the issue persists, please grab following for one failed call:
deb vpm sig
deb voip ccapi inout
deb h225 asn1
deb h245 asn1
Pl. run the debugs during low traffic/maintenance as these are pretty verbose.
Hmm...not aware of any existing issue or setting as such but curious
- how long before such call drops ? Is it same duration in all/most cases?
- are u sure its just the calls with unknown number and not other calls with valid CLID?
- any reports of unknown call staying up and not dropping ?
- have u tried spoofing calline name/number (station-id name | number CLI under FXO voice-port) to see the behavior ?
- any debugs or CCM traces collected ?