Dial-peer matching question

[cxu21]

We still have a H.323 geteway and the requirement is to allow a single number display its callerID and all other numbers in the same number range have their callerID blocked.

The number 12345678 is the calling number that we would like to display to the external phones. I created a new dial-peer 1127 try to match with answer-address, I thought answer-address take precedence over destination-pattern and all will match this dial-peer, because there is no clid restrict command in this dial-peer, callerID will be displayed.

The Outgoing translation-profile is empty.

But calls still match the 1107 dialpeer. 

Is there a way to make it work?

dial-peer voice 1107 pots
trunkgroup PSTN
description STD calls and Mobiles
translation-profile outgoing Outgoing
preference 1
destination-pattern 00[2-9]........
progress_ind alert enable 8
progress_ind progress enable 8
progress_ind connect enable 8
clid restrict
forward-digits all

dial-peer voice 1127 pots
trunkgroup PSTN
translation-profile outgoing Outgoing
answer-address 12345678
forward-digits all

[Roger Kallberg · Accepted solution]

answer-address is an inbound dial peer matching option and your trying to use it in the outbound direction. Have a look at this document for how call routing in IOS works. Explain Cisco IOS and IOS XE Call Routing 

If you look at debug voip ccapi inout you’ll see that you’re using the new dial peer as the inbound and then the old in the outbound. That’s why you’re restricting the calling number.

To do what you’re set out to do with H.323 as the protocol you’d need to be creative and have two pairs of different inbound and also outbound dial peers. On the inbound you’ll match on calling number and then use a translation rule in the inbound direction to prefix the called number with something, different prefix depending upon restriction of CLID or not, you then use the prefix as the match on the outbound dial peers and remove it with an outbound translation rule. All this would be much easier and simpler to do if you where to use SIP instead of H.323 as then you’ll have many more options for the dial peers than you have now. For example using e164 number maps for the inbound match and DPG to set the outbound dial peer. Eventually you’ll need to make the switch to SIP as H.323 is being deprecated in IOS. The transition is actually quite straightforward, it’s more or less just a matter of setting SIPv2 as the protocol on your voip dial peers and then creating a SIP trunk in CM instead of the H.323 gateway.

[Maren Mahoney]

Are you asking about outbound calls showing the one caller ID with all others masked? If so, a voice translation profile is what you will want to use.

voice translation-rule 1
  rule 1 /98765432/ /&/  [This would be the one you want to allow through]
  rule 2 /.*/ /12345678/ [This is the masked one applied to all other clid]
voice translation-profile mask-outbound-clid
 translate calling 1

And then apply the translation profile to the outgoing dial peer in the outgoing direction.

If that is not the scenario, please let us know what I am missing.

Maren