CUCM 5 - unable to restrict outbound caller ID

[asim.shahzad]

Hi All,

Customer would like the the ability to restrict of release outbound CLI. Previously they had the 9.@ pattern set to prefix with 141 and and 8. pattern to release CLI. Changed the solution to route out a CUBE instead of MGCP gateway. As 141 not recognized by the SIP carrier I've removed this from 9.@. The fact that it was previously set to prefix with 141 indicates this was an issue previously.

Now if I restrict on the 9.@ RP or on the SIP trunk to CUBE it's not restricting at all. Also tried 'clid restrict' on the dialpeer out to SIP carrier, CLI is still released! Carrier states they support restricting and releasing on their side, all based on how we present.

CUCM System version: 5.1.3.6000-2

Any thoughts please?

Many thanks,

Asim

[nitsinha]

The following doc might be helpful to you

http://www.cisco.com/en/US/products/sw/voicesw/ps556/products_configuration_example09186a0080a87124.shtml

Hope that helps

Regards

Nitesh

PS:Pl rate helpful posts

[thisisshanky]

Try setting it at the gateway level...

Or else i believe you can rewrite the SIP header on the CUBE..

[vandana]

You can try the following:

How to block outgoing ANI:

---Configure a voice translation rule to null the ani:

voice translation-rule 8

rule 1 /^.*/ //

---Invokes voice translation rule

voice translation-profile blockani

translate calling 8

---Invokes the voice translation profile on outgoing dialpeer:

dial-peer voice 84007 pots

translation-profile outgoing blockani

destination-pattern 74007

port 0/1/0:23

forward-digits 4