Search this Blog

Sunday, January 2, 2011

Number of Digits for Caller ID Partial Match to 7 does not work?

We are trying to configure some Mobility features, we are facing problem during the incoming call from remote destination to on of the IP phone in the cluster .The caller ID does not appear as if it is originated from the IP Phone unless we added the full remote destination number. To make it clear: We have 2 IP phones

1) ext. 2000

2) ext 3000 and it has Remote Destination 4567890

what we are receiving from the PSTN is 1234567890 so that we configured the service parameter: Matching Caller ID with remote destination to Partial Match and the Number of Digits for Caller ID Partial Match to 7, but it does not work?

Tips:

Have you set "Matching Caller ID with Remote Destination" to partial?? From SRND

Matching Caller ID with Remote Destination (Default value: Complete Match)

#

This parameter specifies whether the caller ID of a configured remote destination is completely matched or partially matched by the system for inbound calls. Based on this setting, the caller ID is completely or partially matched to the destination number configured for each remote destination. If set to Partial Match, this parameter works in conjunction with the Number of Digits for Caller ID Partial Match service parameter to determine how many numbers in the presented caller ID will be matched. Caller ID matching determines whether the system recognizes the remote destination in order to invoke Enterprise Feature Access mid-call features and two-stage dialing as well as Mobile Voice Access.

#

Number of Digits for Caller ID Partial Match (Default value: 10)

#

This parameter determines how many consecutive digits of caller ID will be matched against configured remote destinations. This parameter is used only when the Matching Caller ID with Remote Destination service parameter is set to Partial Match.

From a knowledge forum. What is the purpose of "Number of Digits" service

parameter?

Service Param = Partial Match, 10 digits

(Reset CCM and MVA service)

BR1 GW CLID = 44 020 5943 2785

Change HQ phone 2 remote destination to 11111102059432785

PSTN dials into BR1 phone 2 "04 4793 3002"

BR1 phone 2 show 4402059432785

Based on the above test the remote destination should have been matched but it wasn't. Maybe the number of digits is used to control how many digits is required from the PSTN not which digits to match. Because the PSTN is sending 13 digits CLID the remote destination must match all 13 digits but the remote destination can be equal length or longer. CUCM is configured to allow matching of only 10 digits if the PSTN only sent 10 digits. But what would happen if the PSTN only sent 8 digits but CUCM was configured to partially match 10, would the remote destination still work?

Service Param = Partial Match, 10 digits

BR1 GW CLID = 5943 2785 (reduced to 8 digits)

HQ phone 2 remote destination = +4402059432785

PSTN dials into BR1 phone 2 "04 4793 3002"

BR1 phone 2 show +59432785

Change Service Param = Partial Match, 8 digits

PSTN dials into BR1 phone 2 "04 4793 3002"

BR1 phone 2 show 4002

The answer is no. The number of digits setting is used by CUCM to determine the minimum length the CLID from the PSTN must be to match a remote destination. Each digit from the PSTN must match a digit in the remote destination starting from the right. When CUCM was configured to partially match 10 digits but the PSTN was changed to only send 8 digits a remote destination was not matched even though all digits were matched in the remote destination number and the remote destination number was longer. When the number of digits was changed to 8 the remote destination matched. This setting maybe useful in the event the PSTN sends a different length CLID into different gate.

Citation - This blog post does not reflect original content from the author. Rather it summarizes content that are relevant to the topic from different sources in the web. The sources might include any online discussion boards, forums, websites and others.

No comments :

Post a Comment

 
/* Google Analytics begin ----------------------------------------------- */ /* Google Analytics end ----------------------------------------------- */